Extend MPQUIC protocol support in ATSSS

By extending the MPQUIC protocol and optimizing the MASQUE delivery method, the problems of low efficiency in PDU session management and data transmission in multi-access networks are solved, achieving more efficient data transmission and flexible PDU session management.

CN123125835APending Publication Date: 2026-11-17INTERDIGITAL PATENT HOLDINGS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580027523.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-02-15
Filing Date
2025-02-14
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

The existing QUIC encrypted multiplexing application bearer layer (MASQUE) protocol is difficult to effectively extend and optimize in multi-access environments, resulting in low efficiency of PDU session management and data transmission between 3GPP and non-3GPP access networks.

Method used

By extending the multipath QUIC (MPQUIC) protocol in the wireless transmit/receive unit (WTRU), the establishment of MAPDU sessions and the MASQUE delivery method are realized, a suitable MPQUIC connection is selected, and the access network is selected based on the bootstrapping mode, thereby optimizing the MASQUE delivery configuration to improve data transmission efficiency.

Benefits of technology

It improves data transmission efficiency and reliability in multi-access network environments and enhances the flexibility and efficiency of PDU session management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125835A_ABST
    Figure CN123125835A_ABST
Patent Text Reader

Abstract

Apparatus, methods, and systems for extending MPQUIC protocol support in ATSSS. Some implementations provide apparatus, methods, and systems implemented in WTRU. Application flow establishment is triggered. MA PDU session request is sent. MA PDU session response is received. MASQUE transport method and parameters are determined. MPQUIC connection is selected. CONNECT request corresponding to the selected MASQUE transport method and including the selected MASQUE transport parameters is sent. Establishment of a second branch of the mA PDU session via another access network is triggered. Based on the bootstrapping mode, which access network to use for PDU transmission is determined. PDU is transmitted via the selected access network and the MASQUE transport connection is established. Some implementations provide apparatus, methods, and systems implemented in SMF. MA PDU session request is received from WTRU. Policy rules including MASQUE transport configuration IE are received.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references to related applications This application claims priority and interest in U.S. Provisional Application No. 63 / 553,990, filed February 15, 2024, with the United States Patent and Trademark Office, the entire contents of which are incorporated herein by reference for all applicable purposes as if fully set forth herein in their entirety. Background Technology

[0002] The QUIC Encrypted Multiplexing Application Bearer (MASQUE) protocol can configure and run multiple proxy streams within an HTTP connection, for example, using QUIC HTTP / 3. A Multiple Access Protocol Data Unit (MA PDU) session is a PDU session whose services can be transmitted via 3GPP access, non-3GPP access, or both. Summary of the Invention

[0003] Some implementations provide apparatus, methods, and systems for extending MPQUIC protocol support in ATSSS. Some implementations provide apparatus, methods, and systems implemented in a Wireless Transmit / Receive Unit (WTRU). Application flow establishment is triggered. A MA PDU session request is sent. A MA PDU session response is received. The MASQUE transport method and parameters are determined. An MPQUIC connection is selected. A CONNECT request corresponding to the selected MASQUE transport method and including the selected MASQUE transport parameters is sent. Establishment of a second branch of the MA PDU session via another access network is triggered. Based on the steering mode, the access via which the PDU is sent is determined. The PDU is sent via the selected access and the MASQUE transport connection. Some implementations provide apparatus, methods, and systems implemented in an SMF. A MA PDU session request is received from the WTRU. A policy rule including a MASQUE transport configuration information element (IE) is received. It is determined whether to use the MPQUIC steering function. The MASQUE transport configuration is determined based on the MASQUE transport configuration IE. A message is sent to the UPF, indicating the multi-access rule and including the MASQUE delivery configuration IE. A MA PDU session response is sent to the WTRU, which also includes the MASQUE delivery configuration IE. Attached Figure Description

[0004] A more detailed understanding can be obtained through the following description, given as an example and in conjunction with the accompanying drawings, wherein similar reference numerals in the drawings indicate similar elements, and wherein: Figure 1A This is a system diagram illustrating an exemplary communication system that can implement one or more of the disclosed embodiments; Figure 1B The illustration is based on an embodiment and can be used Figure 1AThe diagram shows a system diagram of an exemplary wireless transmit / receive unit (WTRU) used in a communication system. Figure 1C The illustration is based on an embodiment and can be used Figure 1A The diagram shows an exemplary radio access network (RAN) and an exemplary core network (CN) used within a communication system. Figure 1D The illustration is based on an embodiment and can be used Figure 1A The diagram shows another exemplary RAN and another exemplary CN used within the communication system. Figure 2 This is a block diagram illustrating an exemplary multiple access PDU session (MA PDU session); Figure 3A , 3B 3C is a message sequence diagram illustrating an exemplary procedure for provisioning, establishing, and operating an MA PDU session using the MASQUE delivery method among TCP, UDP, Ethernet, and / or IP with the MPQUIC bootstrap functionality. Figure 4 This is a flowchart illustrating exemplary actions performed by a WTRU; and Figure 5 This is a flowchart illustrating an exemplary action performed by SMF. Detailed Implementation

[0005] The following abbreviations and acronyms are used in this article: 5GS 5G system AF application functions AP application providers API (Application Programming Interface) AS Application Server ATSSS access service guidance, switching, and segmentation DN Data Network DNN Data Network Name Fully Qualified Domain Name (FQDN) GTP-U Universal Tunneling Protocol User Plane HTTP Hypertext Transfer Protocol ID identifier IE Information Elements IP Internet Protocol (IPv4: IP version 4, IPv6: IP version 6) MAR Multi-Access Rules MASQUE QUIC Encrypted Multiplexing Application Host Layer MPQUIC (Multi-path QUIC) MNO mobile network operator MOQ QUIC Media N4 is the interface defined by 3GPP between SMF and UPF. PCC Policy and Fee Control PDU Protocol Data Unit PMF performance management functions PSA UPF PDU Session Anchoring UPF QoE (Quality of Experience) QoS (Quality of Service) QUIC (QUIC protocol, not an abbreviation) RAN (Radio Access Network) RTT round trip time SDF Service Data Flow SMF Session Management Function UDP User Datagram Protocol UE User Equipment UPF User Plane Functions URSP UE routing policy XR Extended Reality.

[0006] The terms Application Server (AS) and Application Function (AF) are used interchangeably herein. In some cases, AS may be an edge application server and / or include an edge application server.

[0007] The Term Information Element (IE) is used in this document to represent one or more parameters. An IE may include one or more other IEs.

[0008] Figure 1A This is a diagram illustrating an exemplary communication system 100 that can implement one or more of the disclosed embodiments. The communication system 100 can be a multiple access system that provides content, such as voice, data, video, messaging, broadcasting, etc., to multiple wireless users. The communication system 100 enables multiple wireless users to access this content through the sharing of system resources (including wireless bandwidth). For example, the communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tail Unique Word Discrete Fourier Transform Spread Spectrum OFDM (ZT-UW-DFT-S-OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Library Multicarrier (FBMC), etc.

[0009] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112. However, it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d can be any type of device configured to operate and / or communicate in a wireless environment. As an example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a station (STA)) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain scenarios), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any WTRU in WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0010] The communication system 100 may also include base station 114a and / or base station 114b. Each of the base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks (such as CN 106, Internet 110, and / or other networks 112). As an example, base stations 114a and 114b may be base transceivers (BTS), NodeBs, eNodeBs (eNBs), home NodeBs, home eNodeBs, next-generation NodeBs (such as gNodeBs (gNBs)), new radio (NR) NodeBs, site controllers, access points, wireless routers, etc. Although base stations 114a and 114b are depicted as single elements, it will be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[0011] Base station 114a may be part of RAN 104, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of a specific geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In embodiments, base station 114a may employ multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0012] Through air interface 116, base stations 114a and 114b can communicate with one or more WTRUs among WTRUs 102a, 102b, 102c, and 102d. Air interface 116 can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Air interface 116 can be established using any suitable radio access technology (RAT).

[0013] More specifically, as described above, the communication system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can use Wideband CDMA (WCDMA) to establish the air interface 116. WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​Uplink (UL) Packet Access (HSUPA).

[0014] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as evolved UMTS terrestrial radio access (E-UTRA), which can use Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro) to establish air interface 116.

[0015] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can use NR to establish air interface 116.

[0016] In the embodiments, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, using a dual connectivity (DC) principle, base station 114a and WTRUs 102a, 102b, and 102c can implement both LTE radio access and NR radio access. Therefore, the air interface used by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0017] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., WiFi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, transitional standard 2000 (IS-2000), transitional standard 95 (IS-95), transitional standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0018] Figure 1ABase station 114b can be, for example, a wireless router, a home Node B, a home eNode B, or an access point, and can use any suitable RAT to facilitate wireless connectivity in a local area, such as a commercial location, home, vehicle, campus, industrial facility, air corridor (e.g., used by a drone), road, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technology (such as IEEE 802.11) to establish a wireless local area network (WLAN). In another embodiment, base station 114b and WTRUs 102c, 102d can implement radio technology (such as IEEE 802.15) to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can use a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a pico or femtocell. Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106.

[0019] RAN 104 can communicate with CN 106, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more WTRUs among WTRUs 102a, 102b, 102c, and 102d. Data may have varying Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, etc., and / or perform advanced security functions such as user authentication. Although not explicitly stated... Figure 1A As shown, but will be understood, RAN 104 and / or CN 106 may communicate directly or indirectly with other RANs that use the same RAT as RAN 104 or a different RAT. For example, in addition to connecting to RAN 104, which may use NR radio technology, CN 106 may also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0020] CN 106 can also serve as a gateway for WTRUs 102a, 102b, 102c, and 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a globally interconnected computer network and apparatus system using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 or a different RAT.

[0021] Some or all of the WTRUs 102a, 102b, 102c, and 102d in communication system 100 may include multi-mode capability (e.g., WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers for communicating with different wireless networks on different wireless links). For example, Figure 1A The WTRU 102c shown can be configured to communicate with base station 114a, which can employ cellular-based radio technology, and with base station 114b, which can employ IEEE 802 radio technology.

[0022] Figure 1B This is a system diagram illustrating an exemplary WTRU 102. (See diagram below.) Figure 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other peripheral devices 138, etc. It will be understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

[0023] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), any other type of integrated circuit (IC), a state machine, etc. Processor 118 may perform signal decoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, and transceiver 120 may be coupled to transmitting / receiving element 122. Although... Figure 1B While the processor 118 and transceiver 120 are depicted as separate components, it will be understood that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0024] Transmitting / receiving element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmitting / receiving element 122 may be an antenna configured to transmit and / or receive RF signals. In embodiments, for example, transmitting / receiving element 122 may be a transmitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In another embodiment, transmitting / receiving element 122 may be configured to transmit and / or receive both RF and optical signals. It will be understood that transmitting / receiving element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0025] Although the transmitting / receiving element 122 is in Figure 1B While depicted as a single element, WTRU 102 may include any number of transmit / receive elements 122. More specifically, WTRU 102 may employ MIMO technology. Thus, in one embodiment, WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via air interface 116.

[0026] Transceiver 120 can be configured to modulate signals to be transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 may have multi-mode capability. Therefore, transceiver 120 may include multiple transceivers to enable WTRU 102 to communicate over various RATs (such as, for example, NR and IEEE 802.11).

[0027] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit), and can receive user input data from the speaker / microphone 124, keypad 126, and / or display / touchpad 128. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Additionally, the processor 118 can access information from any type of suitable memory (such as non-removable memory 130 and / or removable memory 132) and store data in said memory. Non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital storage (SD) card, etc. In other embodiments, processor 118 may access information from memory that is not physically located on WTRU 102 (such as on a server or home computer (not shown)) and store the data in said memory.

[0028] The processor 118 may receive power from the power supply 134 and may be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 may be any suitable device for powering the WTRU 102. For example, the power supply 134 may include one or more dry cell battery packs (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0029] Processor 118 may also be coupled to GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of WTRU 102. In addition to or alternative to information from GPS chipset 136, WTRU 102 may receive location information via air interface 116 from base stations (e.g., base stations 114a, 114b) and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be understood that WTRU 102 may acquire location information using any suitable location determination method while remaining consistent with the embodiments.

[0030] The processor 118 may be further coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or videos), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, frequency modulation (FM) radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors. Sensors may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors, geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, humidity sensors, etc.

[0031] WTRU 102 may include a full-duplex radio device for which the transmission and reception of some or all of the signals (e.g., associated with a specific subframe of both UL (e.g., for transmission) and DL (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio device may include an interference management unit to reduce and / or substantially eliminate self-interference via hardware (e.g., a choke) or via signal processing (e.g., a separate processor (not shown) or via processor 118). In an embodiment, WTRU 102 may include a half-duplex radio device for which the transmission and reception of some or all of the signals (e.g., associated with a specific subframe of UL (e.g., for transmission) or DL ​​(e.g., for reception)) may be concurrent and / or simultaneous.

[0032] Figure 1C This is a system diagram illustrating RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with CN 106.

[0033] RAN 104 may include eNode-Bs 160a, 160b, and 160c, but it will be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. Each eNode-B 160a, 160b, and 160c may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, eNode-B 160a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a.

[0034] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, and user scheduling in the UL and / or DL, etc. Figure 1C As shown, eNode-B 160a, 160b, and 160c can communicate with each other via the X2 interface.

[0035] Figure 1C CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (PGW) 166. Although the foregoing elements are depicted as part of CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0036] The MME 162 can be connected to each of the eNode-Bs 162a, 162b, and 162c in RAN 104 via the S1 interface and can be used as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, activating / deactivating bearers, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies (such as GSM and / or WCDMA).

[0037] The SGW 164 can be connected to each of the eNode Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user packets to / from WTRUs 102a, 102b, and 102c. The SGW 164 can also perform other functions, such as anchoring the user plane during inter-eNode B handovers, triggering paging when DL data is available for WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0038] SGW 164 can be connected to PGW 166, which provides WTRU 102a, 102b, 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0039] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRUs 102a, 102b, and 102c with access to a circuit-switched network (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and conventional landline communication devices. For example, CN 106 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server), or can communicate with said IP gateway, which serves as an interface between CN 106 and PSTN 108. Additionally, CN 106 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0040] Although WTRU is Figure 1A-1D While described as a wireless terminal, it is conceivable that in some representative embodiments, such a terminal may use (e.g., temporarily or permanently) a wired communication interface with a communication network.

[0041] In a representative embodiment, the other network 112 may be a WLAN.

[0042] In an Infrastructure Basic Services Set (BSS) mode, a WLAN may have an access point for the BSS and one or more stations (STAs) associated with an AP. The AP may access a Distribution System (DS) or another type of wired / wireless network, or have an interface with a Distribution System (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic originating outside the BSS destined for a STA can be delivered to the AP via it. Traffic originating from a STA destined for a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be transmitted via the AP, for example, where a source STA can send traffic to the AP and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as peer-to-peer traffic. Using Direct Link Establishment (DLS), peer-to-peer traffic can be transmitted between source and destination STAs (e.g., directly between source and destination STAs). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). WLANs using Standalone BSS (IBSS) mode may not have access points (APs), and STAs within the IBSS or using the IBSS (e.g., all STAs within a STA) can communicate directly with each other. IBSS communication mode may sometimes be referred to herein as "ad-hoc" communication mode.

[0043] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel, such as a primary channel. The primary channel can be of fixed width (e.g., a 20 MHz wide bandwidth) or dynamically configured. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, such as in an 802.11 system, carrier-sense multiple access (CSMA / CA) with collision avoidance can be implemented. For CSMA / CA, each STA (including the AP) can sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, that particular STA can back off. In a given BSS, one STA (e.g., only one station) can transmit at any given time.

[0044] For example, a high-throughput (HT) STA can communicate using a 40 MHz wide channel by combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels.

[0045] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining adjacent 20 MHz channels. A 160 MHz channel can be formed by combining eight adjacent 20 MHz channels, or by combining two non-adjacent 80 MHz channels (this can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, data is delivered via a segment resolver, which divides the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed separately on each stream. The streams can be mapped onto two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

[0046] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. In 802.11af and 802.11ah, the channel operating bandwidth and carrier are reduced compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support instrument-type control / machine-type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support) certain and / or limited bandwidths. MTC devices may include batteries with a battery life exceeding a threshold (e.g., to maintain a very long battery life).

[0047] WLAN systems that support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include a channel that can be designated as the primary channel. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by the STA that supports the minimum bandwidth operating mode among all STAs operating in the BSS. In the example of 802.11ah, for STAs that support (e.g., only support) the 1 MHz mode (e.g., MTC type devices), the primary channel may be 1 MHz wide even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Assignment Vector (NAV) settings may depend on the status of the primary channel. If, for example, the primary channel is busy due to a STA (that only supports the 1 MHz operating mode) transmitting to the AP, then all available frequency bands may be considered busy even if most of the available frequency band remains idle.

[0048] In the United States, the available frequency bands for 802.11ah are from 902 MHz to 928 MHz. In South Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. Depending on the country code, the total bandwidth available for 802.11ah is 6 MHz to 26 MHz.

[0049] Figure 1D This is a system diagram illustrating RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR radio technology. RAN 104 can also communicate with CN 106.

[0050] RAN 104 may include gNBs 180a, 180b, and 180c, but it will be understood that RAN 104 may include any number of gNBs while remaining consistent with the embodiments. gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may use beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Therefore, gNB 180a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In embodiments, gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In embodiments, gNBs 180a, 180b, and 180c can implement Coordinated Multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0051] Using transmissions associated with scalable digital theory, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. Using various or scalable length subframes or transmission time intervals (TTIs) (e.g., containing a varying number of OFDM symbols and / or an absolute time of continuously varying length), WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c.

[0052] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without also accessing other RANs (e.g., eNode-Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can use one or more gNBs from gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate with / connect to gNBs 180a, 180b, and 180c, and also communicate with / connect to another RAN, such as eNode-Bs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c and one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-B 160a, 160b, and 160c can be used as mobility anchors for WTRU 102a, 102b, and 102c, and gNB 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRU 102a, 102b, and 102c.

[0053] Each gNB in ​​gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, interoperability between DC, NR, and E-UTRA, routing of user plane data to User Plane Functions (UPF) 184a and 184b, routing of control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other via the Xn interface.

[0054] Figure 1DThe CN 106 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although the foregoing elements are depicted as part of CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0055] AMF 182a and 182b can be connected to one or more gNBs (gNBs) 180a, 180b, and 180c in RAN 104 via the N2 interface and can be used as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c; supporting network slices (e.g., handling different Protocol Data Unit (PDU) sessions with different requirements); selecting specific SMF 183a and 183b; managing registration areas; terminating Non-Access Stratum (NAS) signaling; and mobility management. Network slices can be used by AMF 182a and 182b to customize CN support for WTRU 102a, 102b, and 102c based on the type of services used by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services relying on Ultra Reliable Low Latency (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, and services for MTC access. AMF 182a and 182b can provide control plane functions for switching between RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

[0056] SMF 183a and 183b can be connected to AMF 182a and 182b in CN 106 via the N11 interface. SMF 183a and 183b can also be connected to UPF 184a and 184b in CN 106 via the N4 interface. SMF 183a and 183b can select and control UPF 184a and 184b, and configure the routing of services through UPF 184a and 184b. SMF 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing DL data notifications. PDU session types can be IP-based, non-IP-based, or Ethernet-based.

[0057] UPF 184a and 184b can be connected via the N3 interface to one or more gNBs (gNBs) 180a, 180b, and 180c in RAN 104. This provides WTRU 102a, 102b, and 102c with access to packet-switched networks (such as the Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, and providing mobility anchoring.

[0058] CN 106 can facilitate communication with other networks. For example, CN 106 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server), or may communicate with said IP gateway, which serves as an interface between CN 106 and PSTN 108. Additionally, CN 106 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRUs 102a, 102b, and 102c can be connected to DNs 185a and 185b via UPFs 184a and 184b, through their N3 interfaces and the N6 interface between UPFs 184a and 184b and local DNs 185a and 185b.

[0059] Considering Figure 1A-1D and Figure 1A-1D The corresponding descriptions herein regarding WTRU 102a-d, base station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF183a-b, DN 185a-b, and / or any other device(s) described herein, and / or the functions described herein, may be performed by one or more emulation devices (not shown). An emulation device may be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0060] The simulation device may be designed to perform one or more tests on other devices in a laboratory environment and / or in a carrier network environment. For example, while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network, the one or more simulation devices may perform one or more or all of the functions to test other devices within the communication network. While being temporarily implemented / deployed as part of a wired and / or wireless communication network, the one or more simulation devices may perform one or more or all of the functions. The simulation device may be directly coupled to another device for testing purposes and / or use over-the-air wireless communication to perform the test.

[0061] While not implemented / deployed as part of a wired and / or wireless communication network, the one or more simulation devices may perform the one or more functions (including all functions). For example, the simulation devices may be used in test scenarios in test laboratories and / or non-deployed (e.g., test) wired and / or wireless communication networks to perform testing of one or more components. The one or more simulation devices may be test equipment. Wireless communication via direct RF coupling and / or through an RF circuit system (e.g., the RF circuit system may include one or more antennas) may be used by the simulation devices to transmit and / or receive data.

[0062] Some implementations include MPQUIC and / or MASQUE. In some implementations, the QUIC cryptographic multiplexing application bearer layer (MASQUE) protocol facilitates and / or enables the configuration and / or delivery (e.g., tunneling) of multiple proxy streams over an HTTP connection, for example, using QUIC HTTP / 3. In some implementations, the MASQUE service includes: a “CONNECT-UDP” service (e.g., as described in IETF, RFC 9298, “Proxying UDP in HTTP” https: / / datatracker.ietf.org / doc / html / rfc9298, which is incorporated herein as if fully described), for example, enabling and / or facilitating the transport of UDP traffic between a client and a proxy or between two proxies; a “CONNECT-IP” service (e.g., as described in IETF, RFC 9484, “Proxying IP in HTTP”, https: / / datatracker.ietf.org / doc / html / rfc9484, which is incorporated herein as if fully described), for example, enabling and / or facilitating the transport of IP traffic; and a “CONNECT-ETHERNET” service (e.g., as described in IETF, “Proxying Ethernet in HTTP”, ... As described in https: / / datatracker.ietf.org / doc / html / draft-ietf-masque-connect-ethernet-01 (which is incorporated herein as if fully explained), "CONNECT" enables, for example, the transport of Ethernet services and / or facilitates the transport of WebSocket services; "CONNECT," for example, enables, for example, the transport of WebSocket services and / or facilitates the transport of WebSocket services. In some implementations, for TCP services, "CONNECT" and / or methods derived from CONNECT (e.g., potential new CONNECT-TCP methods) may be used, referred to herein as "CONNECT-TCP".

[0063] The term MASQUE delivery method is used herein to specify the delivery method (e.g., protocol) provided by the extended CONNECT, such as CONNECT-UDP, CONNECT-IP, CONNECT-ETHERNET, and CONNECT-TCP. The value of the protocol field in a CONNECT request may correspond to a MASQUE delivery method. Equivalent terms for MASQUE delivery methods include "CONNECT protocol" and "bootstrap protocol". The term CONNECT-X is used herein to specify the CONNECT message corresponding to any MASQUE delivery method.

[0064] In some implementations, to initiate a MASQUE service, the client sends an HTTP CONNECT request to the broker. This HTTP request includes, for example, a method field set to "CONNECT" and a protocol field set to the actual MASQUE delivery method used, such as "connect-udp," "connect-ethernet," or "connect-ip." In some implementations, the broker sends an HTTP response indicating whether the service request was accepted or rejected. In some implementations, the MASQUE service includes forwarding application payloads delivered over the MASQUE connection to endpoints (e.g., UDP servers or endpoints on Ethernet links or IP networks). In some implementations, the application payload is delivered over the MASQUE connection via HTTP datagrams or HTTP streams. In some implementations, the MASQUE broker connection can operate over multipath (e.g., MPQUIC) connections. For example, in some implementations, the application payload delivered over the MASQUE connection can be sent and received by MPQUIC connection endpoints over different access networks.

[0065] Some implementations include ATSSS. In some implementations, the WTRU can perform both 3GPP and non-3GPP access. In some implementations, this capability provides network operators with flexibility in determining which access will be used for Service Data Flows (SDFs). In some implementations, an SDF is a data flow or includes a data flow (e.g., as identified in the 3GPP 5G standard by specific characteristics such as a 5-tuple consisting of the transport protocol, source and destination IP addresses, and port), which is governed by specific quality of service and policy control rules. The terms SDF and data flow are used interchangeably herein.

[0066] Figure 2This is a block diagram illustrating architecture 200, which includes entities and interfaces associated with an exemplary multi-access PDU session (MA PDU session) 250. Architecture 200 includes WTRU 202, UPF 204, AMF 206, SMF 208, PCF 210, and DN 212. In some implementations, WTRU 202 communicates with AMF 206 via a 3GPP N1 interface, as shown in the figure. In some implementations, WTRU 202 communicates via MA PDU session 250, via 3GPP access 214, and / or non-3GPP access 216, for example, as discussed further herein. In some implementations, 3GPP access 214 and non-3GPP access 216 communicate with AMF 206 via a 3GPP N2 interface, as shown in the figure. In some implementations, 3GPP access 214 and non-3GPP access 216 communicate with UPF 204 via the 3GPP N3 interface, as shown in the figure. In some implementations, SMF 208 communicates with UPF 204 via the N4 interface, as shown in the figure. In some implementations, UPF 204 communicates with DN 212 via the 3GPP N6 interface, as shown in the figure. In some implementations, AMF 206 communicates with SMF 208 via the 3GPP N11 interface, as shown in the figure. In some implementations, SMF 208 communicates with PCF 210 via the 3GPP N7 interface, as shown in the figure.

[0067] In some implementations, MA PDU session 202 facilitates and / or allows uplink and / or downlink traffic with WTRU 202 service data streams to be routed, switched, and / or segmented between access points.

[0068] For example, in some implementations, the MA PDU session 250 is a PDU session or includes a PDU session, the services of which can be transmitted via 3GPP access 214, via non-3GPP access 216, or via both 3GPP and non-3GPP accesses 214 and 216. In the context of WTRU 202, the MA PDU session 250 is shown as having both 3GPP and non-3GPP accesses 214 and 216.

[0069] In some implementations, this architecture and similar architectures facilitate and / or allow: service routing (e.g., where an access network is selected for a new data flow and the service is delivered via the selected access network); service handover (e.g., where an ongoing data flow can be moved from one access network to another in a manner that maintains the continuity of the data flow); and / or service segmentation (e.g., where the service of a data flow can be segmented across multiple access networks). In some implementations, some PDUs of a data flow are transmitted via one access (e.g., 3GPP access 214), and other PDUs of the same data flow are transmitted via another access (e.g., non-3GPP access 216).

[0070] In some implementations, service bootstrapping functions (e.g., residing in and / or implemented by a WTRU with ATSSS functionality (such as WTRU 202) and / or residing in and / or implemented by a UPF (such as UPF 204)) can bootstrap, handover, and / or segment MA PDU session services across multiple accesses (such as 3GPP access 214 and non-3GPP access 216). In some implementations, service bootstrapping functions are implemented as hardware and / or software configured to bootstrap services. Some implementations include one or more of three bootstrapping functions. In some implementations, two higher-level bootstrapping functions that operate above the IP layer include MPTCP bootstrapping (which is applicable to TCP services in some implementations) and MPQUIC bootstrapping (which is applicable to UDP services in some implementations). In some implementations, lower-level bootstrapping functions that operate below the IP layer include ATSSS Low Layer Function (ATSSS-LL) (which is applicable to Ethernet and / or IP services in some implementations).

[0071] In some implementations, the bootstrapping pattern determines how service data flows should be distributed across access points. In some implementations, only one bootstrapping pattern can be used for SDF. Exemplary bootstrapping patterns may include one or more of the following: active-standby bootstrapping, minimum latency bootstrapping, load balancing bootstrapping, priority-based bootstrapping, and / or redundant bootstrapping, or any other suitable bootstrapping pattern.

[0072] For example, in some implementations, if an access is available, the active-standby bootstrapping mode will boots the service to that access (e.g., the access may be called the active access), and if the active access becomes unavailable, the service will boots the service to another access (e.g., the access may be called the standby access).

[0073] In some implementations, minimum latency bootstrapping mode bootstraps traffic to the access point with (e.g., determined to have) the minimum (or less) round-trip time (RTT). In some implementations, the WTRU and / or UPF (e.g., WTRU 202 and / or UPF 204) measure the RTT between them to determine which access point has the lowest RTT. In some implementations, minimum latency bootstrapping mode is only applicable to non-guaranteed bit rate (GBR) SDFs.

[0074] In some implementations, load balancing bootstrapping mode segments traffic across more than one (e.g., two) access methods, such as 3GPP access 214 and non-3GPP access 216. In some implementations, traffic is segmented based on a percentage (e.g., a configurable percentage). In some implementations, the WTRU (e.g., WTRU 202) determines (e.g., autonomously) the percentage used for traffic segmentation. In some implementations, the WTRU makes this determination in response to and / or based on an autonomous load balancing indicator provided by the network. In some implementations, load balancing bootstrapping mode applies only to non-GBR SDFs.

[0075] In some implementations, priority-based bootstrapping directs all traffic matching the PCC rule to high-priority access (e.g., as defined in 3GPP standards). In other implementations, priority-based bootstrapping directs all traffic matching the PCC rule to high-priority access until high-priority access is determined to be congested (e.g., there is insufficient capacity on the link for the traffic volume, such that nodes (e.g., RAN nodes for DL ​​or WTRUs for UL) may have to queue and / or drop some PDUs). In some implementations, traffic is sent to low-priority access and / or split between low-priority and high-priority access. In some implementations, priority-based bootstrapping is only applicable to non-GBR SDFs.

[0076] In some implementations, Redundancy Bootstrapping Mode (RSM) facilitates and / or allows WTRUs (e.g., WTRU 202) and / or UPFs (e.g., UPF 204) to replicate services on multiple (e.g., two) access "branches" (e.g., 3GPP access 214 and non-3GPP access 216) of an MA PDU session (e.g., MA PDU session 250). In this context, a branch refers to a portion of the service delivered via a specific access.

[0077] In some implementations, configuration (e.g., additional configuration) may be provided by the network (e.g., SMF) to modify boot mode behavior on WTRUs and / or UPFs (e.g., WTRU 202 and / or UPF 204). For example, in some implementations, WTRU auxiliary indicators facilitate and / or enable WTRUs to determine how to allocate UL traffic in certain situations (e.g., when in low-power mode). In some implementations, if a threshold (RTT or packet loss rate) is reached on an access point, the threshold facilitates and / or enables WTRUs and / or UPFs to reduce usage on that access point. In some implementations, for example, for MPQUIC boot functionality, configuration information elements facilitate and / or enable the delivery of streams or datagrams without reordering and / or the delivery of datagrams with reordering.

[0078] In some implementations, the Performance Management Function (PMF) protocol is implemented between the WTRU and UPF (e.g., WTRU 202 and / or UPF 204) to obtain measurements (e.g., RTT, access availability reports, packet loss rate, etc.), and the switching mode is determined based on these measurements.

[0079] In some implementations, for example, the selection of bootstrap functionality and / or bootstrap mode for the SDF in the MA PDU session is performed by the SMF (e.g., SMF 208) based on MA PDU session control information present in the PCC rules. In some implementations, the MA PDU session control information includes and / or indicates the bootstrap mode and / or functionality. In some implementations, the MA PDU session control information includes and / or indicates the bootstrap mode and / or functionality, and may also include and / or indicate additional configuration parameters, such as those described herein.

[0080] In the current system, ATSSS is supported only for UDP streams (using CONNECT-UDP) using the MPQUIC bootstrap function. Current 5G systems do not support using the MPQUIC bootstrap function with other MASQUE delivery methods for TCP streams (e.g., using CONNECT-TCP), Ethernet (e.g., using CONNECT-ETHERNET), or IP streams (e.g., using CONNECT-IP).

[0081] In the current system, when using the existing ATSSS MPQUIC boot function, and when UPF and WTRU are configured to use the MPQUIC boot function, the MASQUE delivery method cannot be used for WTRU or UPF.

[0082] In some implementations, WTRU can attempt to guess which tunneling mode to use based on the protocol of the application flow. However, in some implementations, this approach may be limited. For example, it may lack flexibility. For instance, in some such solutions, TCP flows will always be transported via CONNECT-TCP, whereas depending on the situation, it might be appropriate to use one of CONNECT-IP, CONNECT-ETHERNET, or CONNECT-TCP. Furthermore, some such solutions may rely on the MPQUIC agent on the UPF always supporting all MASQUE transport methods, even when they are not in use, which can waste network resources and is less secure. For example, it might be preferable to allow WTRU to use only CONNECT-IP on a given MA PDU session, for example, to limit network resource usage (e.g., memory) on the UPF by restricting the protocols supported by the MPQUIC agent for that MA PDU session. In another example, a request made to access a UDP server using CONNECT-UDP could end up being used to access the entire network using CONNECT-IP, leading to security issues. Additionally, some such solutions may lack mechanisms for configuring MASQUE transport methods. For example, MNO / AP may need to further control additional parameters applied to various MASQUE delivery methods, including header compression configuration, FEC, and safety configuration.

[0083] Therefore, some implementations facilitate and / or enable network operators and / or application providers to control the use of MPQUIC bootstrapping functionality for TCP, UDP, Ethernet, and IP flows. Some of these implementations may offer advantages in terms of increased efficiency and / or provide policy control, fine-grained control over MASQUE, and / or security. For example, in terms of efficiency, in some implementations, if multiple flows using TCP, Ethernet, UDP, and IP MASQUE delivery methods are delivered over the same QoS flow and the same PDU session, they can be delivered over the same MPQUIC connection. Regarding policy control, in some implementations, the MNO and / or AP may be able to configure which MASQUE delivery method (e.g., among TCP, IP, Ethernet, and UDP) should be used for a given flow on an MPQUIC-based MA PDU session. In some implementations, the MNO and / or AP may also allow, or alternatively allow, the WTRU (e.g., WTRU 202) to determine, for example, within a set of MASQUE delivery methods, which MASQUE delivery method to use. Regarding fine-grained control over MASQUE, for example, some MASQUE delivery methods can use parameters that improve service aspects such as security, reliability, and network efficiency. Some implementations support controlling these parameters. Regarding security, in some implementations, MASQUE delivery methods and / or any related parameters can be provided to the WTRU and also to the UPF, for example, to enable the execution of permitted MASQUE delivery methods and / or related parameters.

[0084] In some implementations, the MASQUE delivery configuration IE is defined for policy control of the MASQUE delivery method for MA PDU sessions using MPQUIC bootstrapping functionality. In some implementations, the MASQUE delivery configuration IE includes one or more of the following: Bootstrapping Function Protocol (SFP) IE, Allow Bootstrapping Function Protocol (ASFP) IE, UE Control Indication IE, and / or SFP Parameter IE.

[0085] In some implementations, the Bootstrap Function Protocol (SFP) IE may indicate (e.g., it may have a value indicating) UDP, TCP, Ethernet, IP. In some implementations, if the bootstrap function of the MA PDU session control information is "MPQUIC", then the SFP IE instructs the WTRU (e.g., WTRU 202) and the network to use a specific MASQUE delivery method (e.g., CONNECT-UDP, CONNECT-ETHERNET, CONNECT-IP, etc.).

[0086] In some implementations, the Allow Bootstrapping Function Protocol (ASFP) IE may indicate that any MASQUE transport method is allowed or include an indication that any MASQUE transport method is allowed (e.g., it may be "wildcard", indicate "wildcard", or include "wildcard"), or may indicate or include a list of values ​​among UDP, TCP, Ethernet, IP, indicating a set of allowed MASQUE transport methods. In some implementations, if the bootstrapping function of the MA PDU session control information is "MPQUIC", and if the SFP is not provided (e.g., the SFP IE is not received), then the ASFP IE indicates that the WTRU is allowed to select, based on the MASQUE transport method selection algorithm, which MASQUE transport method will be used for the application flow on this PDU session. The terms "provided" and "set" (and the corresponding "not provided" and "not set") are used equivalently in this context to indicate that a specific MASQUE transport configuration IE is provided or present in the message.

[0087] In some implementations, the WTRU control indication IE (also referred to as the "UE control" indication IE) indicates whether the WTRU is permitted to determine the MASQUE delivery method for the flow on this PDU session. In some implementations, this indication can be a true or false value (e.g., binary 0 or 1 or any other suitable true / false indication). In some systems, the WTRU control indication IE may be implemented as a special value of the SFP IE (e.g., "WTRU control").

[0088] In some implementations, the SFP parameter IE indicates the MASQUE delivery method parameter. For example, in some implementations, for the MPQUIC bootstrap function (e.g., if the bootstrap function is indicated as "MPQUIC"), the SFP parameter applies to one or more MASQUE delivery methods, such as those specified in the description of the SFP parameter herein. In some implementations, if the SFP parameter applies, the WTRU and / or UPF (e.g., WTRU 202 and / or UPF 304) can use the SFP parameter to configure the MASQUE delivery method. In some implementations, the SFP parameter IE may indicate a range and / or set of values ​​that are allowed (or not allowed). In this case, in some implementations, the WTRU may select, within the allowed range and / or set (e.g., based on the MASQUE delivery method selection algorithm), which value will be used for the corresponding MASQUE delivery method parameter.

[0089] In some implementations, SFP parameters include parameters applicable to the IP MASQUE delivery method and / or parameters applicable to any MASQUE delivery method. In some implementations, parameters applicable to the IP MASQUE delivery method may include target parameters and / or the IP protocol number. In some implementations, target parameters (e.g., hostname or IP prefix) constrain the IP hosts with which the WTRU (e.g., WTRU202) is allowed to communicate. In some implementations, such parameters may be specified by the WTRU, for example, in a CONNECT-IP request. In some implementations, such parameters may also be used by the UPF (e.g., UPF 204) to enforce IP host constraints on the flow, and may reject the CONNECT-IP request if a suitable target is not specified.

[0090] In some implementations, the IP protocol number (e.g., the "ipproto" parameter, which may have a value indicating TCP, such as "6") constraint can be imposed by the protocol carried by IP packets sent over the connection. In some implementations, this parameter can be specified in the CONNECT-IP request by the WTRU (e.g., WTRU 202). In some implementations, this parameter can also be used by the UPF (e.g., UPF204) to enforce protocol constraints on the flow and to reject the CONNECT-IP request if a suitable protocol number is not specified.

[0091] In some implementations, the parameters applicable to any MASQUE delivery method may include identification of each SFP constraint or preference, FEC scheme and associated parameters, and / or header compression mechanism and profile (and / or any other suitable parameters).

[0092] In some implementations, each SFP constraint or preference may include application ID, access type, protocol, number of flows, etc. In some implementations, this indicates the constraints used, which may be determined by the SMF (e.g., SMF 208) and / or WTRU (e.g., WTRU 202) to determine the appropriate MASQUE delivery method and bootstrapping mode. For example, in some implementations, the TCP MASQUE delivery method may be restricted to or preferred for untrusted non-3GPP access, the UDP MASQUE delivery method may be restricted to the QUIC or RTP protocol, the IP MASQUE delivery method may be constrained to be used with a set of applications listed by ID, and / or the UDP MASQUE delivery method may be restricted to a certain number (e.g., 100) of flows to limit network resource usage. In some implementations, header compression mechanisms and profiles indicate robust header compression (ROHC) RTP / UDP / IP profiles.

[0093] Some implementations include parameters for the “Ethernet” and / or “TCP” MASQUE transport methods. For example, in some implementations, the Ethernet protocol number may be specified in the CONNECT-ETHERNET request, for instance, to restrict the types of services that can be transmitted over Ethernet to those with the specified protocol.

[0094] In some implementations, the MA PDU session control information in a PCC rule may include a MASQUE delivery configuration IE. In some implementations, the MNO may configure the MASQUE delivery configuration IE within the MA PDU session control information. In some implementations, the AP may include the MASQUE delivery configuration IE in API messages destined for the NEF or PCF (e.g., PCF 210). In some implementations, if the MASQUE delivery configuration IE is included in the MA PDU session control information of a PCC rule, the MASQUE delivery configuration IE enables the MNO / AP to control how the MASQUE delivery method is selected and configured.

[0095] In some implementations, ATSSS rules may include a MASQUE transport configuration IE. In some implementations, the SMF (e.g., SMF 208) may configure the MASQUE transport configuration IE in the ATSSS rules, for example, based on PCC rules. In some implementations, if the MASQUE transport configuration IE is included in the ATSSS rules, the MASQUE transport configuration IE may facilitate the network (e.g., the SMF) and / or enable the network (e.g., the SMF) to control how the MASQUE transport method is selected and configured by the WTRU (e.g., WTRU 202).

[0096] In some implementations, the Multiple Access Rule (MAR) may include a MASQUE delivery configuration IE. In some implementations, the SMF (e.g., SMF 208) may configure the MASQUE delivery configuration IE in the MAR, for example, based on PCC rules. In some implementations, if the MASQUE delivery configuration IE is included in the MAR, the MASQUE delivery configuration IE enables the SMF to control how the MASQUE delivery method is selected and / or configured by the UPF (e.g., UPF 204).

[0097] In some implementations, the SMF (e.g., SMF 208) implements the SMF MASQUE delivery method selection algorithm. In some implementations, the SMF receives policy rules corresponding to the SDF on the MA PDU session (e.g., PCC rules including the MASQUE delivery configuration IE). In some implementations, the SMF can select the MPQUIC bootstrapping feature if it is set in the PCC rules. In some implementations, the SMF reads MA PDU session control information from the PCC rules, including, for example, the MASQUE delivery control IE.

[0098] In some implementations, if the SFP IE is set and the ASFP is not set, the SMF (e.g., SMF 208) selects the SFP IE value as the MASQUE delivery method. In some implementations, if the SFP is not set and the ASFP IE is set, the SMF selects the MASQUE delivery method as the WTRU control, for example, by setting the allowed MASQUE delivery methods based on the ASFP. In some implementations, if neither the SFP nor the ASFP is set, the SMF selects the MASQUE delivery method as the WTRU control (also referred to as "UE control"), where all MASQUE delivery methods are allowed.

[0099] In some implementations, if both SFP and ASFP IEs are set, the SMF (e.g., SMF 208) can decide whether to select the SFP IE value as the MASQUE delivery method or select the MASQUE delivery method as WTRU control. In some implementations, the SMF can determine the MASQUE delivery method, for example, using WTRU (e.g., WTRU 202) and / or UPF (e.g., UPF 204) capabilities. For example, in some implementations, if the WTRU does not support WTRU control of MASQUE delivery, the SMF can select the SFP. In some implementations, if the UPF supports only a subset of all MASQUE delivery methods, the SMF can select the MASQUE delivery method as WTRU control and select an ASFP that contains delivery methods that exist both in the ASFPs from the PCC rules and in the list of MASQUE delivery methods supported by the UPF. For example, if the UPF only supports CONNECT-UDP and CONNECT-TCP and the PCC rule includes CONNECT-UDP, CONNECT-TCP, and CONNECT-IP, then the SMF can select an ASFP consisting of CONNECT-UDP and CONNECT-TCP. In some implementations, if both solutions are possible (e.g., if both solutions are equally possible), the SMF can be configured by the MNO to preferentially select the SFP or set the MASQUE delivery method to WTRU control.

[0100] In some implementations, the SMF can use SFP parameters (e.g., per SFP constraint) to select the bootstrapping mode (e.g., if an access is preferred for a certain type of service, the SMF can select an active-standby bootstrapping mode, where the preferred access is the active access). In some implementations, the SMF can use the MASQUE delivery configuration IE from the WTRU (e.g., in a PDU session setup / modification request) to influence the selection of the MASQUE delivery method (e.g., reordering ASFP IEs based on preferences from the WTRU).

[0101] In some implementations, after the SMF (e.g., SMF 208) selects the MASQUE delivery method, the SMF prepares a MAR (for transmission to the UPF) and an ATSSS rule (for transmission to the UE), which includes the selected MASQUE delivery method and any relevant IEs. For example, if the MASQUE delivery method is WTRU controlled, the relevant IE may include ASFP. In some implementations, in all cases, the relevant IE may include SFP parameters.

[0102] In some implementations, the UPF (e.g., UPF 204) implements the execution of the MASQUE transport configuration. In some implementations, the UPF receives a MAR (Masque Transport Information Classifier), which includes the selected MASQUE transport method and the associated MASQUE transport configuration IE. In some implementations, the UPF configures the MPQUIC agent, including configuring one or more MASQUE transport CONNECT-X methods indicated by the MAR (e.g., by the selected SFP or a set of possible values ​​from the ASFP) and using the SFP parameters from the MAR, where applicable. In some implementations, the UPF agent listens for connection requests (e.g., CONNECT-X) from the WTRU and executes the MASQUE transport configuration. For example, in some implementations, the UPF only accepts supported CONNECT-X methods and rejects others (e.g., from this WTRU, on this agent's IP address, and on this port). For example, in some implementations, the UPF checks CONNECT-X parameters (e.g., including target, protocol, SFP constraints) and rejects connection requests that do not conform to these parameters.

[0103] In some implementations, WTRU implements the WTRU MASQUE delivery method selection algorithm. In some implementations, WTRU receives ATSSS rules applied to the application flow, which include the MASQUE delivery configuration IE. An exemplary MASQUE delivery method selection algorithm is described below.

[0104] In some implementations, if the WTRU control indicates the IE to be false and the SFP IE is set, and if the SFP IE is compatible with the application protocol, then WTRU selects SFP as the MASQUE delivery method for the application flow, and the algorithm completes successfully. For example, in some implementations, UDP application flows are compatible with CONNECT-UDP, CONNECT-IP, and CONNECT-ETHERNET, but not with CONNECT-TCP. In some implementations, TCP application flows are compatible with CONNECT-TCP, CONNECT-IP, and CONNECT-ETHERNET, but not with CONNECT-UDP. In some implementations, if the SFM is not compatible with the application protocol, the algorithm completes but fails. In some implementations, if the WTRU control indicates the IE to be false and the SFP IE is not set, the algorithm completes but fails.

[0105] In some implementations, if the WTRU control indicator IE is true and an ASFP IE exists, the WTRU determines the allowed MASQUE delivery methods based on the ASFP IE; alternatively, the WTRU determines that "any" MASQUE delivery method is allowed. In some implementations, the WTRU determines the list of candidate MASQUE delivery methods as follows: In some implementations, if the PDU session type is indicated as an Ethernet session type (e.g., having a value of "Ethernet" or indicating "Ethernet"), the candidate is CONNECT-ETHERNET. In some implementations, if the PDU session type is indicated as an unstructured session type (e.g., having a value of "Unstructured" or indicating "Unstructured"), the algorithm fails (e.g., for unstructured PDU sessions, the network should provide an appropriate MASQUE delivery method). In some implementations, if the PDU session type is not indicated as an unstructured session type (e.g., not having a value of "Unstructured" or indicating "Unstructured"), if the application protocol is TCP, the candidates are CONNECT-TCP and CONNECT-IP; if the application protocol is UDP, the candidates are CONNECT-UDP and CONNECT-IP; and if the application protocol is neither UDP nor TCP but is delivered via IP, the candidate is CONNECT-IP.

[0106] In some implementations, the WTRU can use SFP parameters (e.g., per SFP constraint) to select the MASQUE delivery method. For example, in some implementations, if the "IP" MASQUE delivery method is only permitted for UDP traffic (e.g., if the protocol number (which may be referred to as "ipproto") parameter is set to or includes a value corresponding to UDP), and if the application flow is on another protocol, the WTRU will not include CONNECT-IP in the list of candidates. In some implementations, the WTRU can determine the application flow protocol based on the type of socket opened by the WTRU application. In some implementations, the WTRU can determine the application flow protocol based on configuration or policy (e.g., a service descriptor from the UE routing policy rule). In some implementations, for example, additionally, the WTRU can use an IE from the AS to select the MASQUE delivery method (e.g., a MASQUE delivery configuration IE from the AS). For example, in some implementations, this can be used to reorder candidates based on preferences from the AS.

[0107] In some implementations, WTRU selects a candidate after the candidates are determined. In some implementations, WTRU selects the first allowed candidate (e.g., the first candidate is selected if the "any" MASQUE shipping method is allowed; otherwise, the first candidate included in ASFP is selected). If a candidate is selected, the algorithm completes and succeeds. If no suitable candidate is selected, the algorithm completes but fails.

[0108] If the algorithm fails, the WTRU cannot select the MASQUE delivery method and may, for example, release the PDU session, indicate to the WTRU application that the connection establishment failed, and / or back off to use a non-MA PDU session for the application flow if permitted by the URSP rules. If the algorithm succeeds, the WTRU selects an MPQUIC connection for the application flow with the UPF agent, which corresponds to the QoS flow within the MA PDU session. If such an MPQUIC connection does not exist, the WTRU establishes it. The WTRU creates a new flow within the selected MPQUIC connection and sends a CONNECT-X request to the UPF via this flow, where CONNECT-X corresponds to the selected MASQUE delivery method chosen by the algorithm. The WTRU and UPF continue to establish a MASQUE connection via this MPQUIC flow. The WTRU and UPF then deliver the application flow via the MASQUE connection.

[0109] In some implementations, supporting multiple MASQUE delivery methods does not require establishing additional MPQUIC connections, thus limiting the impact on network resource usage. Multiple application flows can be transmitted on the same MA PDU session, corresponding to multiple PCC rules, each containing a MASQUE delivery control IE. For each application flow, the SMF and UE use the algorithm described herein to determine the MASQUE delivery method. Therefore, multiple MASQUE delivery methods (i.e., multiple CONNECT-X methods) can be used on the same MA PDU session, and if the application flows are transmitted within the same QoS flow (e.g., because they have the same QoS requirements), multiple MASQUE delivery methods can be used over the same MPQUIC connection.

[0110] Some implementations include procedures for establishing new application flows over MPQUIC-based MA-PDU sessions, for example, via MASQUE using TCP, UDP, Ethernet, or IP transport.

[0111] Figure 3A , 3B 3C is a message sequence diagram illustrating an exemplary procedure 300 for provisioning, establishing, and operating an MA PDU session using the MASQUE delivery method among TCP, UDP, Ethernet, and / or IP with the MPQUIC bootstrap functionality. Procedure 300 is described as occurring between WTRU 302, RAN 304, CN 306, and DN 308. CN 306 includes SMF 310, UPF 312, PCF, UDM 314, and NEF 316. DN 308 includes AS and AF 318. In some implementations, such as for... Figure 2 As shown and as for Figure 2 These entities correspond to a portion or all of the architecture described for architecture 200.

[0112] In some implementations, for example via service provider 320, application providers (e.g., through AF) and / or network operators may provide a MASQUE delivery configuration IE in a policy rule. For example, AF 318 may include the MASQUE delivery configuration IE in an API message to NEF 316 or PCF 314 via service provider 320, for example, to configure a policy rule for a given application or flow in 322.

[0113] In some implementations, at 324, the application running on WTRU 302 triggers the establishment of an application session. In some implementations, at 324, WTRU selects a URSP rule and determines, based on that rule, whether to establish or update a MA PDU session for the application flow. In some implementations, WTRU may indicate its capabilities (e.g., support for one or more of CONNECT-TCP, CONNECT-UDP, CONNECT-IP, and CONNECT-ETHERNET, and support for the methods and procedures described herein) in a PDU session establishment / modification request message 326 directed to SMF 310. In some implementations, WTRU may provide a MASQUE delivery configuration IE in the PDU session establishment / modification request message 326 to indicate preferences (e.g., based on WTRU application input).

[0114] In some implementations, after receiving the MA PDU session establishment / modification request message 326, the SMF 310 may use some or all of the parameters from the message to request a policy from the PCF 314 (e.g., in the Npcf_SMPolicyControl_Update request 328), and based on those parameters, the PCF 314 responds using the relevant MASQUE delivery configuration IE (e.g., in policy rule 330).

[0115] In some implementations, at 332, using the SMF MASQUE delivery method selection algorithm, and using the MASQUE delivery configuration IE and / or WTRU capabilities from policy rules and / or PDU session setup / modification requests, the SMF 310 determines whether to use the MPQUIC bootstrapping function and determines the MASQUE delivery configuration, for example, as described herein.

[0116] In some implementations, for example, the SMF 310 configures the UPF 312 by sending an N4 session establishment / modification request 334 that includes a MASQUE shipping configuration IE. In some implementations, the MASQUE shipping configuration IE is the output of the SMF MASQUE shipping method selection algorithm. In some implementations, at 336, the UPF 312 uses the MASQUE shipping configuration IE to configure the MPQUIC agent to enable its execution, for example, as described herein. In some implementations, the UPF 312 sends a response message to the SMF 310 (e.g., via the N4 interface) that includes the IP address and port of the MPQUIC agent.

[0117] In some implementations, SMF 310 sends an MA PDU session establishment / modification accept message 340 to WTRU 302. This message includes the bootstrap function (MPQUIC), boot mode, and MASQUE delivery configuration IE, as well as the IP address and port of the MPQUIC agent. In some implementations, the MASQUE delivery configuration IE is the output of the SMF MASQUE delivery method selection algorithm. In some implementations, at 342, based on the MASQUE delivery configuration IE, for example using the WTRU MASQUE delivery method selection algorithm, WTRU 302 determines the MASQUE delivery method to be used, for example, as described herein.

[0118] In some implementations, WTRU 302 selects an MPQUIC connection (e.g., corresponding to an MA PDU session and QoS flow suitable for the application flow). If such an MPQUIC connection does not exist, WTRU 302 establishes a new MPQUIC connection 344 with UPF 312, for example, using the IP address and port of an MPQUIC proxy.

[0119] In some implementations, WTRU 302 sends a CONNECT-X request 346 (e.g., an HTTP CONNECT-X request) to UPF 312, the request corresponding to the selected MASQUE delivery method and including SFP parameters as specified in the MASQUE delivery configuration IE. UPF 312 performs the MASQUE delivery configuration as described above in 348 (e.g., accepting or rejecting incoming CONNECT-X requests based on UPF 312's configuration) and sends a response message 350 (e.g., an HTTP response). At this point in the exemplary procedure, based on CONNECT-X request 346, execution 348, and response message 350, tunnel session 352 (also referred to herein as the MASQUE delivery connection) is established between WTRU 302 and UPF 312. Application connection 354 between WTRU 302 and AS 318 can be delivered over tunnel session 352.

[0120] In some implementations, WTRU 302 may trigger the establishment 356 of a second branch of the MA PDU session via the second access (e.g., by sending a PDU session establishment request with the same ID as the first PDU session request via the second access, which triggers SMF 310 to reserve network resources for the second branch). During this establishment, similar to the establishment of the first branch (326-340), SMF 310 may re-evaluate the MASQUE transport configuration IE (e.g., if SFP constraints prevent a particular MASQUE transport method from being used on the second access, SMF 310 may modify the SFP).

[0121] In some implementations, at 358, for example, based on a bootstrapping mode, WTRU 302 selects which access to use to send the uplink application PDU. In some implementations, WTRU 302 transmits uplink application PDU 362 via the selected access, which is transported between WTRU 302 and UPF 312 via MASQUE transport connection 360, and then transmitted by UPF 312 to AS 318. In some implementations, AS 318 transmits downlink application PDU 364 to WTRU 302 via UPF 312. At 366, for example, based on a bootstrapping mode, UPF 312 selects which access to use to send downlink application PDU 364. In some implementations, UPF 312 transmits downlink application PDU 364 via the selected access, which is transported between UPF 312 and WTRU 302 via MASQUE transport connection 368.

[0122] Alternatively, in some systems, the AP may provide the MASQUE delivery configuration IE to the WTRU 302, for example, via an application session, to indicate the preferred method and parameters. For example, in some implementations (not shown), the AS may indicate to the WTRU 302 that CONNECT-UDP is the preferred MASQUE delivery method for the media session requested by the WTRU 302 from the AS at the application layer. In some implementations, based on this indication from the AS, the WTRU 302 may include the MASQUE delivery configuration IE in the MA PDU session establishment / modification request 326. In some implementations, after receiving the MA PDU session establishment / modification, the SMF 310 may use them in the SMF MASQUE delivery method selection algorithm, as described above.

[0123] The following are exemplary actions performed by WTRU 302 and SMF 310 for MPQUIC-based MA-PDU sessions. In some implementations, these actions are optimized for a mix of UDP, IP, TCP, and / or Ethernet services (WTRU, SMF). In some implementations, some or all of these actions follow the above procedures or aspects thereof.

[0124] Figure 4 It is a flowchart illustrating the process 400 performed by the WTRU for the provisioning, establishment, and operation of an MA PDU session.

[0125] In some implementations, at 402, the WTRU application triggers the establishment of an application flow. At 404, the WTRU sends an MA PDU session request. At 406, the WTRU receives an MA PDU session response indicating the use of the MPQUIC bootstrapping feature and including the MASQUE delivery configuration IE. At 408, for example, based on the MASQUE delivery configuration IE and the application flow protocol, the WTRU determines the MASQUE delivery method and parameters to be used. The WTRU selects an MPQUIC connection at 410 and sends a CONNECT request at 412, corresponding to the selected MASQUE delivery method and including the selected MASQUE delivery parameters.

[0126] At 414, the WTRU triggers the establishment of the second branch of the MA PDU session via another access network. At 416, the WTRU determines which access to send the PDU via based on the bootstrapping mode, and at 418, sends the PDU via the selected access through the MASQUE transport connection.

[0127] Figure 5 It is a flowchart illustrating the process 500 performed by the SMF for the provisioning, establishment, and operation of an MA PDU session.

[0128] In some implementations, at 502, the SMF receives an MA PDU session request. At 504, the SMF receives a policy rule that includes the MASQUE delivery configuration IE. At 506, the SMF determines to use the MPQUIC bootstrapping function, and at 508, it determines the MASQUE delivery configuration based on the MASQUE delivery configuration IE. At 510, the SMF sends a message to the UPF containing a multi-access rule that includes the MASQUE delivery configuration IE. At 512, the SMF sends an MA PDU session response to the UE, which includes the MASQUE delivery configuration IE.

[0129] Although the features and elements have been described above in specific combinations, those skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. Furthermore, the methods described herein can be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as internal hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROMs and digital versatile discs (DVDs)). A processor associated with the software can be used to implement a radio frequency transceiver for use with a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A method for implementing a Session Management Function (SMF), the method comprising: Receive a Multi-Access Protocol Data Unit (MA PDU) session request from a Wireless Transmit / Receive Unit (WTRU); Receive a message indicating a policy rule, the policy rule including at least one QUIC Encrypted Multiplexed Application Bearer Layer (MASQUE) Delivery Configuration Information Element (IE); The MASQUE shipping configuration is determined based on the at least one MASQUE shipping configuration IE. Send a message indicating multiple access rules and indicating at least one MASQUE transport configuration IE in the at least one MASQUE transport configuration IE; and In response to the MA PDU session request, an MA PDU session response is sent to the WTRU, the MA PDU session response including at least one MASQUE delivery configuration IE from the at least one MASQUE delivery configuration IE.

2. The method of claim 1, wherein the MA PDU session request indicates WTRU capability, and the determination of the MASQUE delivery configuration is based on the WTRU capability.

3. The method of claim 1, wherein the MA PDU session request indicates WTRU support for CONNECT-TCP, CONNECT-UDP, CONNECT-IP and / or CONNECT-ETHERNET delivery methods.

4. The method of claim 1, wherein the MA PDU session request indicates a WTRU preference for CONNECT-TCP, CONNECT-UDP, CONNECT-IP, and / or CONNECT-ETHERNET delivery methods.

5. The method of claim 1, further comprising: Based on the MA PDU session request received from the WTRU, a policy rule request is sent.

6. The method of claim 1, further comprising: The request is sent to the User Plane Function (UPF), and the request to the UPF instructs at least one of the at least one MASQUE delivery configuration IEs.

7. The method of claim 6, further comprising: Receive a response from the UPF, the response from the UPF indicating information about the MPQUIC agent.

8. The method of claim 7, wherein the MA PDU session response indicates information about the MPQUIC agent.

9. The method of claim 7, wherein the MA PDU session response indicates the IP address and / or port of the MPQUIC agent.

10. The method of claim 1, wherein the MA PDU session response indicates a bootstrapping mode.

11. A network apparatus for implementing Session Management Function (SMF), the network apparatus comprising: A circuit system configured to receive a multiple access protocol data unit (MA PDU) session request from a wireless transmit / receive unit (WTRU); A circuit system configured to receive messages, the messages indicating policy rules, the policy rules including at least one QUIC encrypted multiplexed application bearer layer (MASQUE) delivery configuration information element (IE); A circuit system configured to determine the MASQUE transport configuration based on the at least one MASQUE transport configuration IE; A circuit system configured to send a message indicating a multiple access rule and indicating at least one of the at least one MASQUE transport configuration IEs; and A circuit system configured to send an MA PDU session response to the WTRU in response to the MA PDU session request, the MA PDU session response including at least one MASQUE delivery configuration IE from the at least one MASQUE delivery configuration IE.

12. The network apparatus of claim 11, wherein the MA PDU session request indicates WTRU capability, and the circuitry configured to determine the MASQUE delivery configuration is configured to make the determination based on the WTRU capability.

13. The network apparatus of claim 11, wherein the MA PDU session request indicates WTRU support for CONNECT-TCP, CONNECT-UDP, CONNECT-IP and / or CONNECT-ETHERNET delivery methods.

14. The network apparatus of claim 11, wherein the MA PDU session request indicates a WTRU preference for CONNECT-TCP, CONNECT-UDP, CONNECT-IP, and / or CONNECT-ETHERNET delivery methods.

15. The network apparatus of claim 11, further comprising: A circuit system configured to send policy rule requests based on MA PDU session requests received from the WTRU.

16. The network apparatus of claim 11, further comprising: A circuit system configured to send a request to a User Plane Function (UPF), the request to which the UPF instructs at least one of the at least one MASQUE delivery configuration IEs.

17. The network apparatus of claim 16, further comprising: A circuit system configured to receive a response from the UPF, the response from the UPF indicating information about the MPQUIC agent.

18. The network apparatus of claim 17, wherein the MA PDU session response indicates information about the MPQUIC agent.

19. The network apparatus of claim 17, wherein the MA PDU session response indicates the IP address and / or port of the MPQUIC agent.

20. The network apparatus of claim 11, wherein the MA PDU session response indicates a boot mode.