Multiple access network with non-integrated aggregation

Abstract

Aspects relate to a multiple access network with non-integrated aggregation. In one aspect, a UE may: communicate with a core network over a 3rd Generation Partnership Project (3GPP) network; sending a request for a protocol data unit (PDU) session to the core network, the request including a request for data aggregation across the 3GPP network and a non-integrated internet protocol (IP) network; and receiving, from the core network, a response granting the requested PDU session, the response including the identification of the core network aggregation entity and the offload percentage. The UE may also: send data to the core network aggregation entity via the non-integrated IP network based on the offload percentage; and transmitting data to the core network aggregation entity via the 3GPP network based on the offload percentage.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to pending Greek Application No. 20220100690, filed on August 16, 2022, which is assigned to the assignee of the present application and is hereby expressly incorporated herein by reference as if fully set forth below and for all purposes. Technical Field

[0003] The technology discussed below relates generally to wireless communications, and more particularly to multiple access networks with non-integrated aggregation. Background Art

[0004] A next generation wireless communication system (e.g., 5GS) may include a 5G core network and a 5G radio access network (RAN) (such as a new radio (NR)-RAN). The NR-RAN supports communication via one or more cells. For example, a wireless communication device such as a user equipment (UE) may access a first cell of a first base station (BS) such as a gNB and / or access a second cell of a second base station.

[0005] The UE may want to access data available via the core network. Traditionally, this is done using a 3GPP access network (e.g., 5G RAN) or a non-3GPP access network (e.g., WiFi). In 5G, the UE can use multiple access networks (e.g., a network that includes both 5G RAN and WiFi) for data transmission, but the challenges of implementing and managing these features still exist. Summary of the invention

[0006] An overview of one or more aspects of the present disclosure is presented below to provide a basic understanding of these aspects. This summary is not an exhaustive overview of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form as a preface to a more detailed description presented later.

[0007] In some examples, a method for wireless communication at a user equipment is disclosed. The method may include: communicating with a core network through a third generation partnership project (3GPP) network; sending a request for a protocol data unit (PDU) session to the core network, the request including a request for data aggregation across the 3GPP network and a non-integrated Internet Protocol (IP) network; receiving a response from the core network granting the requested PDU session, the response including an identification of a core network aggregation entity and an offload percentage; sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage; and sending data to the core network aggregation entity via the 3GPP network based on the offload percentage.

[0008] In some examples, a user equipment may include: a transceiver; and a processor coupled to the transceiver and configured to: communicate with a core network via a 3GPP network; send a request for a PDU session to the core network via the transceiver, the request including a request for data aggregation across the 3GPP network and a non-integrated IP network; receive a response from the core network via the transceiver granting the requested PDU session, the response including an identification of a core network aggregation entity and an offload percentage; send data to the core network aggregation entity via the non-integrated IP network based on the offload percentage via the transceiver; and send data to the core network aggregation entity via the 3GPP network based on the offload percentage via the transceiver.

[0009] In some examples, a user equipment may include: a component for communicating with a core network via a 3GPP network; a component for sending a request for a PDU session to the core network, the request including a request for data aggregation across the 3GPP network and a non-integrated IP network; a component for receiving a response from the core network granting the requested PDU session, the response including an identifier of a core network aggregation entity and an offload percentage; a component for sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage; and a component for sending data to the core network aggregation entity via the 3GPP network based on the offload percentage.

[0010] In some examples, an article for use with a UE includes a computer-readable medium having instructions stored therein, the instructions executable by one or more processors of the UE to: communicate with a core network via a 3GPP network; send a request for a PDU session to the core network, the request including a request for data aggregation across the 3GPP network and a non-integrated IP network; receive a response from the core network granting the requested PDU session, the response including an identification of a core network aggregation entity and an offload percentage; send data to the core network aggregation entity via the non-integrated IP network based on the offload percentage; and send data to the core network aggregation entity via the 3GPP network based on the offload percentage.

[0011] After studying the specific embodiments below, these and other aspects of the present disclosure will become more fully understood. After studying the description of the specific example aspects of the present disclosure below in conjunction with the accompanying drawings, other aspects, features and examples of the present disclosure will be apparent to those of ordinary skill in the art. Although the features of the present disclosure may be discussed below with respect to certain examples and drawings, all examples of the present disclosure may include one or more of the advantageous features discussed herein. In other words, although one or more examples may be discussed as having certain advantageous features, one or more of such features may also be used according to the various examples of the present disclosure discussed herein. In a similar manner, although the example aspects may be discussed below as device, system or method examples, it should be understood that such example aspects may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a schematic illustration of a wireless communication system according to some aspects.

[0013] Figure 2 is a conceptual illustration of an example of a radio access network in accordance with some aspects.

[0014] Figure 3 is a schematic illustration of an example of wireless resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) in accordance with some aspects.

[0015] Figure 4 is a block diagram illustrating an example of a 5G wireless communication system according to some aspects.

[0016] Figure 5 is a diagram illustrating an example of distributed entities in a wireless communication network in accordance with some aspects.

[0017] Figure 6 is a block diagram illustrating an example of a multiple access network configured for access traffic steering, switching, and splitting (ATSSS).

[0018] Figure 7 is a block diagram illustrating an example of a multiple access network configured for non-integrated split / aggregation in accordance with some aspects.

[0019] Figure 8 is a block diagram illustrating an example of a non-integrated split / aggregated multiple access network configured for use in a roaming architecture in accordance with some aspects.

[0020] Fig. 9 is a conceptual illustration of two protocol stacks for a MASQUE agent in accordance with some aspects.

[0021] Fig.10exemplifies a table comparing the characteristics of MPTCP proxy and MASQUE proxy according to some aspects.

[0022] Figure 11 to Figure 12 is a signaling diagram illustrating an example of establishing a protocol data unit (PDU) session with non-integrated aggregation for a multiple access network in accordance with some aspects.

[0023] Fig.13 is a table illustrating parameters in a routing descriptor for non-integrated WiFi aggregation according to some aspects.

[0024] Fig.14 An illustration of parameter definitions for a user equipment (UE) request for a PDU session with non-aggregated aggregation according to some aspects.

[0025] Fig.15 An illustration of a parameter definition for a proxy address of a user plane function (UPF) associated with a protocol data unit (PDU) session with non-integrated aggregation according to some aspects.

[0026] Fig.16 is an illustration of parameter definitions for a core network response to a UE request for a PDU session with non-aggregated aggregation in accordance with some aspects.

[0027] Fig.17 is an illustration of a modified procedure for a non-integrated aggregation (NIA) PDU establishment session in accordance with some aspects.

[0028] Fig.18 is a block diagram illustrating an example of a hardware implementation for user equipment employing a processing system in accordance with some aspects.

[0029] Fig.19 is a flow chart illustrating an example method for communicating using non-integrated aggregation in accordance with some aspects.

[0030] Fig. 20 is a block diagram illustrating an example of a hardware implementation of a network entity employing a processing system according to some aspects.

[0031] Fig.21 is a flow chart illustrating an example method for communicating using non-integrated aggregation in accordance with some aspects. DETAILED DESCRIPTION

[0032] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0033] Although various aspects and examples are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many different arrangements and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, various aspects and / or uses may be generated via integrated chip examples and other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of a wide range of described innovations may occur. Specific implementations may range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, the devices incorporating the described aspects and features may also necessarily include additional components and features for the implementation and implementation of the claimed and described examples. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a variety of devices of different sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, disaggregated arrangements (e.g., base stations and / or UEs), end-user devices, etc.

[0034] Various aspects of the present disclosure relate to a multiple access network with non-integrated aggregation. A UE may: communicate with a core network via a third generation partnership project (3GPP) network; send a request for a protocol data unit (PDU) session to the core network, the request including a request for data aggregation across a 3GPP network and a non-integrated Internet Protocol (IP) network; and receive a response from the core network granting the requested PDU session, the response including an identification of a core network aggregation entity and an offload percentage. The UE may also: send data to the core network aggregation entity via a non-integrated IP network based on the offload percentage; and send data to the core network aggregation entity via a 3GPP network based on the offload percentage.

[0035] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Figure 1 , various aspects of the present disclosure are illustrated with reference to a wireless communication system 100 as an illustrative example and not as a limitation. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be enabled to perform data communications with an external data network 110, such as (but not limited to) the Internet.

[0036] The RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specifications, commonly referred to as 5G. As another example, the RAN 104 may operate under a mix of 5G NR and an evolved universal terrestrial radio access network (eUTRAN) standard, commonly referred to as Long Term Evolution (LTE). 3GPP refers to such a hybrid RAN as the Next Generation RAN or NG-RAN. In another example, the RAN 104 may operate in accordance with both the LTE and 5G NR standards. Of course, many other examples may be utilized within the scope of the present disclosure.

[0037] As illustrated, RAN 104 includes multiple base stations 108. In a broad sense, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, a base station may be referred to as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an eNode B (eNB), a gNode B (gNB), a transmission and reception point (TRP), or some other suitable terminology by those skilled in the art. In some examples, a base station may include two or more TRPs that may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands. In an example where RAN 104 operates according to both LTE and 5G NR standards, one of the base stations in base station 108 may be an LTE base station, and the other base station may be a 5G NR base station.

[0038] The radio access network 104 is also illustrated as supporting wireless communications for multiple mobile devices. The mobile device may be referred to as a user equipment (UE) 106 in the 3GPP standard, but may also be referred to as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology by those skilled in the art. The UE 106 may be a device that provides access to network services to a user. In an example where the RAN 104 operates according to both the LTE and 5G NR standards, the UE 106 may be an evolved universal terrestrial radio access network-new radio dual connectivity (EN-DC) UE that is capable of simultaneously connecting to an LTE base station and an NR base station to receive data packets from both the LTE base station and the NR base station.

[0039] In this article, a mobile device does not necessarily have the ability to move and can be stationary. The term mobile device or mobile device refers to a wide variety of devices and technologies. UE may include multiple hardware structural components whose size, shape, and arrangement facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile devices, cellular (cell) phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smart books, tablet devices, personal digital assistants (PDAs), and a wide variety of embedded systems, for example, corresponding to the Internet of Things (IoT).

[0040] The mobile device may additionally be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device may additionally be a digital home or smart home device (such as home audio, video and / or multimedia equipment), an appliance, a vending machine, a smart lighting device, a home security system, a smart meter, or the like. Tables, etc. The mobile device can additionally be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device that controls electrical power (e.g., a smart grid), lighting, water supply, etc., an industrial automation and enterprise device, a logistics controller and / or agricultural equipment, etc. In addition, the mobile device can provide connected medical or telemedicine support, such as health care at a distance. Telemedicine devices can include telemedicine monitoring devices and telemedicine management devices, whose communications can be given priority or priority access over other types of information, for example, in terms of priority access for the transmission of critical service data and / or related QoS for the transmission of critical service data.

[0041] The wireless communication between RAN 104 and UE 106 may be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) over the air interface may be referred to as downlink (DL) transmissions. In some examples, the term downlink may refer to point-to-multipoint transmissions originating at a base station (e.g., base station 108). Another way to describe this point-to-multipoint transmission scheme may be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as uplink (UL) transmissions. In some examples, the term uplink may refer to point-to-point transmissions originating at a UE (e.g., UE 106).

[0042] In some examples, access to the air interface may be scheduled, where a scheduling entity (e.g., a base station 108) allocates resources for communication between some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UEs). That is, for scheduled communications, multiple UEs 106 (which may be scheduled entities) may utilize resources allocated by a scheduling entity (e.g., a base station 108).

[0043] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE can communicate with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0044] like Figure 1 As illustrated, a scheduling entity (e.g., base station 108) may broadcast downlink traffic 112 to one or more scheduled entities (e.g., UE 106). Broadly speaking, a scheduling entity is a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112 and, in some examples, uplink traffic 116 and / or uplink control information 118 from one or more scheduled entities to the scheduling entity. On the other hand, a scheduled entity is a node or device that receives downlink control information 114, which includes, but is not limited to, scheduling information (e.g., grants), synchronization or timing information, or other control information from another entity in the wireless communication network, such as a scheduling entity.

[0045] In addition, uplink control information 118, downlink control information 114, downlink traffic 112 and / or uplink traffic 116 may be divided into frames, subframes, time slots and / or symbols in time. As used herein, a symbol may refer to a time unit that carries one resource element (RE) per subcarrier in an orthogonal frequency division multiplexing (OFDM) waveform. In some examples, a time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 millisecond (ms). Multiple subframes or time slots may be grouped together to form a single frame or radio frame. In the present disclosure, a frame may refer to a predetermined duration (e.g., 10ms) for wireless transmission, wherein each frame is composed of, for example, 10 subframes of 1ms each. Of course, these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and the various time divisions of waveforms may have any suitable duration.

[0046] Typically, base stations 108 may include a backhaul interface for communicating with a backhaul 120 of the wireless communication system. Backhaul 120 may provide a link between base stations 108 and core network 102. Additionally, in some examples, a backhaul network may provide interconnections between respective base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection using any suitable transport network, a virtual network, or the like.

[0047] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other appropriate standard or configuration.

[0048] Reference now Figure 2 , by way of example and not limitation, a schematic illustration of a radio access network (RAN) 200 is provided. In some examples, the RAN 200 may be similar to the ones described above and in Figure 1 is the same as the RAN 104 illustrated in .

[0049] The geographic area covered by the RAN 200 may be divided into cells that may be uniquely identified by user equipment (UE) based on an identity broadcast from an access point or base station. Figure 2 Cells 202, 204, 206, and 208 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. A radio link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by multiple groups of antennas, each of which is responsible for communicating with UEs in a portion of the cell.

[0050] Various base station arrangements can be used. Figure 2 , two base stations 210 and 212 are shown in cells 202 and 204; and base station 214 is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna, or may be connected to an antenna or RRH by a feeder cable. In the illustrated example, cells 202, 204, and 206 may be referred to as macro cells, because base stations 210, 212, and 214 support cells with larger sizes. In addition, base station 218 is shown in cell 208, which may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home Node B, a home eNodeB, etc.), because base station 218 supports a cell with a relatively small range. The cell size setting may be performed according to the system design and component constraints.

[0051] It should be understood that the RAN 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and in Figure 1 The base station / scheduling entity illustrated in is the same.

[0052] Figure 2 Also included is an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter. UAV 220 may be configured to act as a base station, or more specifically, a mobile base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of a mobile base station (such as UAV 220).

[0053] Within the RAN 200, cells may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, and 218 may be configured to provide a signal to the core network 102 (see FIG. 1 ) for all UEs in the respective cells. Figure 1 ) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; and UE 234 may communicate with base station 218. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the base stations described above and in Figure 1 In some examples, UAV 220 (e.g., a quadcopter) may be a mobile network node and may be configured to act as a UE. For example, UAV 220 may operate within cell 202 by communicating with base station 210.

[0054] In another aspect of the RAN 200, sidelink signals may be used between UEs without having to rely on scheduling or control information from a base station. Sidelink communications may be utilized in a device-to-device (D2D) network, a peer-to-peer (P2P) network, a vehicle-to-vehicle (V2V) network, a vehicle-to-everything (V2X) network, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UEs 238, 240, and 242) may communicate with each other using sidelink signals 237 without relaying the communication through a base station. In some examples, UEs 238, 240, and 242 may each act as a scheduling entity or a sender sidelink device and / or a scheduled entity or a receiver sidelink device to schedule resources and communicate sidelink signals 237 therebetween without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) may also communicate sidelink signals 227 via a direct link (sidelink) without routing the communication through base station 212. In this example, base station 212 may allocate resources to UEs 226 and 228 for sidelink communication.

[0055] In the RAN 200, the ability for a UE to communicate while moving (independent of its location) is called mobility. This is usually done in an access and mobility management function (AMF, not shown). Figure 1 The AMF establishes, maintains and releases various physical channels between the UE and the radio access network under the control of the core network 102, where the AMF may include a security context management function (SCMF) that manages the security context of both the control plane and the user plane functionalities and a security anchor function (SEAF) that performs authentication.

[0056] RAN 200 may utilize DL-based mobility or UL-based mobility to implement mobility and handover (i.e., the transfer of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity or at any other time, a UE may monitor various parameters of a signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handover or handover from the serving cell to a neighboring (target) cell. For example, UE 224 (illustrated as a vehicle, but any suitable form of UE may be used) may move from a geographic area corresponding to its serving cell (e.g., cell 202) to a geographic area corresponding to a neighboring cell (e.g., cell 206). When the signal strength or quality from a neighboring cell exceeds the signal strength or quality of the serving cell for a given amount of time, UE 224 may send a report message indicating the condition to its serving base station (e.g., base station 210). In response, UE 224 may receive the handover command, and the UE may proceed with the handover to cell 206 .

[0057] In a network configured for UL-based mobility, the network can select a serving cell for each UE using a UL reference signal from each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast a unified synchronization signal (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 can receive the unified synchronization signal, derive the carrier frequency and time slot timing based on the synchronization signal, and send an uplink pilot or reference signal in response to the derived timing. The uplink pilot signal sent by a UE (e.g., UE 224) can be received concurrently by two or more cells (e.g., base stations 210 and 214 / 216) within the RAN 200. Each of the cells may measure the strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 210 and 214 / 216 and / or a central node within the core network) may determine a serving cell for the UE 224. As the UE 224 moves through the RAN 200, the network may continue to monitor the uplink pilot signal sent by the UE 224. When the signal strength or quality of the pilot signal measured by the neighboring cell exceeds the signal strength or quality measured by the serving cell, the RAN 200 may hand over the UE 224 from the serving cell to the neighboring cell with or without notifying the UE 224.

[0058] Although the synchronization signals transmitted by base stations 210, 212 and 214 / 216 may be uniform, the synchronization signal may not identify a specific cell, but may identify a zone of multiple cells operating on the same frequency and / or using the same timing. Using zones in a 5G network or other next generation communication network implements an uplink-based mobility framework and improves the efficiency of both the UE and the network, because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0059] In various specific implementations, the air interface in the RAN 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum with the help of a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. Although it is still generally necessary to comply with some technical rules to access the unlicensed spectrum, access is generally available to any operator or device. Shared spectrum may fall between licensed spectrum and unlicensed spectrum, where access to the spectrum may require technical rules or restrictions, but the spectrum may still be shared by multiple operators and / or multiple radio access technologies (RATs). For example, a license holder of a portion of a licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties (e.g., with appropriate licensee-determined conditions to obtain access).

[0060] The air interface in the RAN 200 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexing of DL transmissions from the base station 210 to one or more UEs 222 and 224 using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other suitable multiple access schemes. Furthermore, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0061] In addition, the air interface in the RAN 200 may utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which two endpoints can communicate with each other in two directions. Full-duplex means that two endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can transmit information to the other endpoint at a time. Half-duplex emulation is often implemented for wireless links using time division duplex (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at certain times, the channel is dedicated to transmissions in one direction, and at other times, the channel is dedicated to transmissions in another direction, where the direction can change very quickly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation of transmitters and receivers, and suitable interference cancellation techniques. Full-duplex emulation is often implemented for wireless links by utilizing frequency division duplex (FDD) or space division duplex (SDD). In FDD, transmissions in different directions operate at different carrier frequencies. In SDD, transmissions in different directions on a given channel are separated from each other using space division multiplexing (SDM). In other examples, full-duplex communication can be implemented in an unpaired spectrum (e.g., in a single carrier bandwidth), where transmissions in different directions occur in different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to as sub-band full-duplex (SBFD), cross-duplex (xDD), or flexible duplex.

[0062] Reference will be made to the OFDM waveform (an example of which is given in Figure 3 Various aspects of the present disclosure are described in detail with reference to Figure 1 (illustrated schematically in Figure 2). It should be understood by those skilled in the art that various aspects of the present disclosure can be applied to SC-FDMA waveforms in substantially the same manner as described herein below. That is, although some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.

[0063] Reference now Figure 3 , illustrates an expanded view of an example subframe 302 showing an OFDM resource grid. However, as will be readily appreciated by those skilled in the art, the physical (PHY) layer transmission structure for any particular application may differ from the examples described herein, depending on any number of factors. Here, time is in units of OFDM symbols in the horizontal direction; and frequency is in units of subcarriers of a carrier in the vertical direction.

[0064] Resource grid 304 may be used to schematically represent the time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, a corresponding plurality of resource grids 304 may be available for communication. Resource grid 304 is divided into a plurality of resource elements (REs) 306. RE (which is 1 subcarrier × 1 symbol) is the smallest discrete portion of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE may represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB), or more simply a resource block (RB) 308, which may contain any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers (a number independent of the parameter set used). In some examples, depending on the parameter set, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB (such as RB 308) corresponds entirely to communication in a single direction (transmission or reception for a given device).

[0065] A collection of contiguous or non-contiguous resource blocks may be referred to herein as a resource block group (RBG), a subband, or a bandwidth part (BWP). A collection of subbands or BWPs may span the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 306 within one or more subbands or bandwidth parts (BWPs). Thus, a UE typically utilizes only a subset of a resource grid 304. In some examples, an RB may be the smallest resource unit that may be allocated to a UE. Thus, the more RBs scheduled for a UE, and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. The RBs may be scheduled by a scheduling entity such as a base station (e.g., a gNB, eNB, etc.), or may be self-scheduled by a UE implementing D2D sidelink communication.

[0066] In this illustration, RB 308 is shown as occupying less than the entire bandwidth of subframe 302, with some subcarriers illustrated above and below RB 308. In a given implementation, subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308. Furthermore, in this illustration, RB 308 is shown as occupying less than the entire duration of subframe 302, although this is only one possible example.

[0067] Each 1 ms subframe 302 may consist of one or more adjacent time slots. Figure 3In the example shown in , as an illustrative example, a subframe 302 includes four time slots 310. In some examples, a time slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include micro-slots (sometimes referred to as shortened transmit time intervals (TTIs)) with shorter durations (e.g., one to three OFDM symbols). These micro-slots or shortened transmit time intervals (TTIs) may be transmitted in some cases by occupying resources scheduled for ongoing time slot transmissions for the same UE or different UEs. Any number of resource blocks may be utilized within a subframe or time slot.

[0068] An expanded view of one of the time slots 310 illustrates that the time slot 310 includes a control region 312 and a data region 314. In general, the control region 312 may carry control channels, and the data region 314 may carry data channels. Of course, a time slot may contain full DL, full UL, or at least one DL portion and at least one UL portion. Figure 3 The structure illustrated in is merely an example, and different slot structures may be utilized and may include one or more of each of a control region and a data region.

[0069] Although in Figure 3 Although not illustrated in the figure, each RE 306 within the RB 308 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within the RB 308 may also carry pilot signals or reference signals. These pilot signals or reference signals may be provided to a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of control channels and / or data channels within the RB 308.

[0070] In some examples, time slot 310 may be utilized for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications may refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast or groupcast communications are delivered to multiple intended receiving devices. Unicast communications may refer to point-to-point transmissions from one device to a single other device.

[0071] In an example of cellular communication on a cellular carrier via a Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 306 (e.g., within a control region 312) to one or more scheduled entities (e.g., UEs) to carry DL control information including one or more DL control channels (such as a physical downlink control channel (PDCCH)). The PDCCH carries downlink control information (DCI), including but not limited to power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or assignments of REs for DL ​​transmission and UL transmission. The PDCCH may further carry a hybrid automatic repeat request (HARQ) feedback transmission, such as an acknowledgement (ACK) or a negative acknowledgement (NACK). HARQ is a technique known to those of ordinary skill in the art, in which the integrity of a packet transmission may be checked for accuracy at the receiving side, for example, using any appropriate integrity check mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if it is not confirmed, a NACK may be sent. In response to the NACK, the sending device may transmit a HARQ retransmission, which may implement trace combining, incremental redundancy, and the like.

[0072] The base station may also allocate one or more REs 306 (e.g., in the control region 312 or the data region 314) to carry other DL signals, such as a demodulation reference signal (DMRS); a phase tracking reference signal (PT-RS); a channel state information (CSI) reference signal (CSI-RS); and a synchronization signal block (SSB). The SSB may be broadcast at regular intervals based on a periodicity (e.g., 5ms, 10ms, 20ms, 30ms, 80ms, or 130ms). The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may use the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell.

[0073] The PBCH in the SSB may also include a master information block (MIB) containing various system information and parameters for decoding a system information block (SIB). The SIB may be, for example, SystemInformationType 1 (SIB1), which may include various additional (remaining) system information. Together, the MIB and SIB1 provide minimum system information (SI) for initial access. Examples of system information sent in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink parameter set), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell barring indicator, cell reselection indicator, grid offset, and search space for SIB1. Examples of remaining minimum system information (RMSI) sent in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may also send other system information (OSI).

[0074] In an UL transmission, a scheduled entity (e.g., a UE) may utilize one or more REs 306 to a scheduling entity to carry UL control information (UCI) including one or more UL control channels, such as a physical uplink control channel (PUCCH). The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include a sounding reference signal (SRS) and an uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request to the scheduling entity to schedule an uplink transmission. In this document, in response to the SR sent on the UCI, the scheduling entity may send downlink control information (DCI), which may schedule resources for uplink packet transmissions. The UCI may also include HARQ feedback, channel state feedback (CSF) (such as a CSI report), or any other appropriate UCI.

[0075] In addition to control information, one or more REs 306 (e.g., within the data region 314) may also be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as a physical downlink shared channel (PDSCH) for DL ​​transmissions or a physical uplink shared channel (PUSCH) for UL transmissions. In some examples, one or more REs 306 within the data region 314 may be configured to carry other signals, such as one or more SIBs and DMRS.

[0076] In an example of sidelink communication on a sidelink carrier via a proximity service (ProSe) PC5 interface, a control region 312 of a time slot 310 may include a physical sidelink control channel (PSCCH) including sidelink control information (SCI) sent by an initiating (transmitting) sidelink device (e.g., a transmitting (Tx) V2X device or other Tx UE) toward a set of one or more other receiving sidelink devices (e.g., a receiving (Rx) V2X device or some other Rx UE). A data region 314 of the time slot 310 may include a physical sidelink shared channel (PSSCH) including sidelink data traffic sent by the initiating (transmitting) sidelink device within resources reserved by the transmitting sidelink device on the sidelink carrier via the SCI. Other information may also be sent via various REs 306 within the time slot 310. For example, the HARQ feedback information may be sent from the receiving side link device to the transmitting side link device in a physical sidelink feedback channel (PSFCH) within time slot 310. Additionally, one or more reference signals may be sent within time slot 310, such as a sidelink SSB, a sidelink CSI-RS, a sidelink SRS, and / or a sidelink positioning reference signal (PRS).

[0077] These physical channels described above are typically multiplexed and mapped to transport channels for handling at the medium access control (MAC) layer. Transport channels carry blocks of information called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to the number of information bits, may be a controlled parameter.

[0078] References Figures 1 to 3 The channels or carriers described are not necessarily all channels or carriers that may be utilized between a scheduling entity and a scheduled entity, and one of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic, control, and feedback channels.

[0079] Figure 4 An example of a 5G wireless communication system (5GS) 400 is illustrated. In some examples, the 5GS 400 may be the system described above and described in Figure 1 4. The 5GS 400 includes a user equipment (UE) 402, a next generation radio access network (NG-RAN) 404, and a 5G core network 406. The UE 402 may correspond to a 5G core network 406. Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 7 , Fig. 9 , Fig.11 , Fig.12 , Fig.13 , Fig.14 , Fig.15 and Fig.16 NG-RAN 404 may correspond to any of the UEs or scheduled entities shown in any of the figures in FIG. Figure 1 , Figure 2 , Figure 4 , Figure 5 , Fig. 9 , Fig.11 , Fig.12 , Fig.13 , Fig.14 , Fig.15 and Fig.18 Any of the base stations or scheduling entities shown in any of the figures.

[0080] The core network 406 may include, for example, an access and mobility management function (AMF) 408, a session management function (SMF) 410, and a user plane function (UPF) 412. The AMF 408 and the SMF 410 employ control plane (e.g., non-access stratum (NAS)) signaling to perform various functions related to mobility management and session management of the UE 402. For example, the AMF 408 provides connectivity, mobility management, and authentication of the UE 402, while the SMF 410 provides session management of the UE 402 (e.g., processing signaling related to a protocol data unit (PDU) session between the UE 402 and an external data network (DN) 414). The UPF 412 provides user plane connectivity to route 5G (NR) packets to / from the UE 402 via the NG-RAN 404.

[0081] The core network 406 may also include other functions such as a policy control function (PCF) 416, an authentication server function (AUSF) 418, a unified data management (UDM) 420, a network slice selection function (NSSF) 422, and other functions (not illustrated for simplicity). The PCF 416 provides policy information (e.g., rules) for control plane functions such as network slicing, roaming, and mobility management. In addition, the PCF 416 supports 5G quality of service (QoS) policies, network slicing policies, and other types of policies. The AUSF 418 performs authentication of the UE 402. The UDM 420 facilitates the generation of authentication and key agreement (AKA) credentials, performs user identification, and manages subscription information and UE context. In some examples, the AMF 408 includes a co-location security anchor function (SEAF) that allows re-authentication of the UE 402 when the UE 402 moves between different NG-RANs 404 without having to perform a full authentication process with the AUSF 418. NSSF 422 redirects traffic to network slices. For example, network slices may be defined for different categories of subscribers or use cases, such as smart homes, Internet of Things (IoT), connected cars, smart grids, etc. Each subscriber or use case may receive a unique set of optimized resources and network topologies (e.g., network slices) to meet the requirements of the subscriber or use case (e.g., connectivity, speed, power, and / or capacity requirements).

[0082] In order to establish an NR SA connection to the 5G core network 406 via the NG-RAN 404, the UE 402 may send a registration request and a PDU session establishment request to the 5G core network 406 via the NG-RAN 404. The AMF 408 and the SMF 410 may process the registration request and the PDU session establishment request, and establish a PDU session between the UE 402 and the external DN 414 via the UPF 412. A PDU session may include one or more sessions (e.g., data sessions or data flows) and may be served by multiple UPFs 412 (only one of which is shown for convenience). Examples of data flows include, but are not limited to, Internet Protocol (IP) flows, Ethernet flows, and unstructured data flows.

[0083] In some examples, the RAN may employ a distributed architecture, where the functionality of a network node (e.g., incorporating modem functionality and / or other functionality) may be split between one or more control units and one or more distributed units (which may also be referred to as data units). For example, a network node may include one or more control units, each of which supports multiple distributed units. Each distributed unit may in turn support one or more radio units. The control unit, distributed units, and radio units provide different communication protocol layer functionality and other related functionality.

[0084] The network node may communicate with the core network via a backhaul link and communicate with at least one radio unit via at least one fronthaul link. In some examples, the network node may include at least one control unit and at least one distributed unit communicating via at least one midhaul link.

[0085] In some examples, the control unit is a logical node that hosts a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, a service data adaptation protocol (SDAP) layer, and other control functions. The control unit may also terminate interfaces (e.g., E1 interfaces, E2 interfaces, etc.) to network nodes (e.g., nodes of a core network). In addition, the F1 interface may provide a mechanism for interconnecting control units (e.g., PDCP layer and higher layers) and distributed units (e.g., radio link control (RLC) layer and lower layers). In some aspects, the F1 interface may provide control plane and user plane functions (e.g., interface management, system information management, UE context management, RRC messaging, etc.). For example, the F1 interface may support F1-C on the control plane and F1-U on the user plane. F1AP is an application protocol for F1, which defines signaling procedures for F1 in some examples.

[0086] In some examples, the distributed unit is a logical node that hosts the RLC layer, the medium access control (MAC) layer, and the high physical (PHY) layer based on the lower layer functional split. In some aspects, the distributed unit can control the operation of at least one radio unit. The distributed unit can also terminate the interface (e.g., F1, E2, etc.) to the control unit and / or other network nodes. In some examples, the high PHY layer includes various parts of the PHY processing, such as forward error correction 1 (FEC 1) encoding and decoding, scrambling, modulation, and demodulation.

[0087] In some examples, a radio unit is a logical node that hosts a low PHY layer and radio frequency (RF) processing based on a lower layer functional split. In some examples, a radio unit may be similar to a 3GPP transmit receive point (TRP) or a remote radio head (RRH), while also including a low PHY layer. In some examples, the low PHY layer includes portions of PHY processing such as fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, and physical random access channel (PRACH) extraction and filtering. The radio unit may also include a radio chain for communicating with one or more UEs.

[0088] Figure 5 5 is a diagram illustrating an example of a RAN 500 including distributed entities according to some aspects. The RAN 500 may be similar to Figure 25, because the RAN 500 can be divided into a number of cells (e.g., cell 522), each of which can be served by a corresponding network node (e.g., a control unit, a distributed unit, and a radio unit). The network node can constitute an access point, a base station (BS), an eNB, a gNB, or other nodes that utilize wireless spectrum (e.g., radio frequency (RF) spectrum) and / or other communication links to support access by one or more UEs located in the cell.

[0089] exist Figure 5 In the example of , a control unit (CU) 502 communicates with a core network 504 via a backhaul link, and communicates with a first distributed unit (DU) 506 and a second distributed unit 508 via corresponding midhaul links. The first distributed unit 506 communicates with a first radio unit (RU) 510 and a second radio unit 512 via corresponding fronthaul links. The second distributed unit 508 communicates with a third radio unit 514 via the fronthaul link. The first radio unit 510 communicates with at least one UE 516 via at least one RF access link. The second radio unit 512 communicates with at least one UE 518 via at least one RF access link. The third radio unit 514 communicates with at least one UE 520 via at least one RF access link.

[0090] As discussed above, a UE may want to access available data via a core network. Traditionally, this is done using a 3GPP access network (e.g., 5G RAN) or a non-3GPP access network (e.g., WiFi). In 5G, UEs can use multiple access networks (e.g., a network that includes both 5G RAN and WiFi) for data transmission, but the challenges of implementing and managing these features remain. A technology, Access Service Steering, Switching, and Splitting (ATSSS), was introduced in Release 16 of the 3GPP specification to allow steering, switching, and splitting / aggregation of data services across multiple access networks. ATSSS provides a multiple access protocol data unit (PDU) session for which one or more concurrent accesses (3GPP access (e.g., 5G NR), non-3GPP access (e.g., WiFi)) can be used to serve data services at the UE.

[0091] Figure 66 is a block diagram illustrating an example of a multiple access network 600 configured for access service steering, switching, and splitting (ATSSS). The network 600 includes a user equipment (UE) 602, a 3GPP access node 604, a non-3GPP access node 606 (which includes a non-3GPP interworking function (N3IWF) 607), an AMF 608, an SMF 610, a PCF 612, and a UPF 614 that provides access to a DN 616. Example interfaces (N1, N2, N3, N4, N6, N7, and N11) for communication between the various entities are also shown. In some examples, the UE 602 may correspond to a 3GPP access node 604, a non-3GPP access node 606, and a non-3GPP interworking function (N3IWF) 607. Figure 1 , Figure 2 , Figure 4 and Figure 5 In some examples, the 3GPP access node 604 may correspond to any of the UEs or scheduled entities shown in any of the figures. Figure 1 , Figure 2 , Figure 4 and Figure 5 In some examples, AMF 608 may correspond to any of the base stations, scheduling entities, or DUs shown in any of the figures. Figure 4 , Figure 7 , Figure 8 , Fig.11 and Fig.12 In some examples, SMF 610 may correspond to any of the AMF entities shown in any of the figures in FIG. Figure 4 , Figure 7 , Figure 8 , Fig.11 and Fig.12 In some examples, PCF 612 may correspond to any of the SMF entities shown in any of the figures in FIG. Figure 4 , Figure 7 , Figure 8 , Fig.11 and Fig.12 In some examples, UPF 614 may correspond to the PCF entity shown in any of the figures in Figure 4 , Figure 7 , Figure 8 , Fig.11 and Fig.12 In some examples, DN 616 may correspond to any of the UPF entities shown in any of the figures in FIG. Figure 1 , Figure 2 , Figure 4 , Figure 7 , Figure 8 , Fig.11 and Fig.12 Any one of the DN nodes shown in any of the figures.

[0092] The UE 602 includes 3GPP access functionality (e.g., Multipath Transport Control Protocol (MPTCP)) 618 for communicating with a 3GPP access node 604 and non-3GPP access functionality (e.g., Access Service Steering, Switching, and Splitting Lower Layer (ATSSS-LL)) 620 for communicating with a non-3GPP access node 606. The UPF 614 includes a proxy functionality 622 and a path management function (PMF) 624 for supporting 3GPP access and non-3GPP access. After the PDU session is established, and when user plane resources are present on all access networks, the UE 602 and the UPF 614 may apply network-provided policies and consider local conditions (e.g., network interface availability, signal loss conditions, user preferences, etc.) to decide how to distribute UE traffic across access networks.

[0093] As discussed above, ATSSS functionality allows multiple access PDU sessions for which one or more concurrent accesses (3GPP access (e.g., 5G NR) 604, non-3GPP access (e.g., WiFi) 606 / 607) can be used to serve data traffic at the UE. It turns out that ATSSS has some disadvantages. First, ATSSS requires support for trusted or untrusted connectivity that integrates WiFi to the 5G core network (using a Trusted Non-3GPP Gateway Function (TNGF) in the form of N3IWF 607). Therefore, many operators choose to implement or deploy ATSSS sparingly. Second, the value of implementing N3IWF is questionable, except for supporting voice over Wi-Fi. For example, if a wireless network operator deploys N3IWF for general "Internet access", it will likely face hardware capacity issues because the return on investment is questionable due to orders of magnitude increase in traffic volume (e.g., from 20-50 kilobits per second (Kbps) per UE for Voice over WiFi (VoWiFi) to potentially 100s of megabits per second (Mbps) for Internet traffic). As a result, few operators and other industry professionals have shown interest in designing or deploying ATSSS.

[0094] Various aspects of the present disclosure relate to a multi-access network with non-integrated aggregation / splitting. In some examples, the multi-access network does not provide N3IWF support, but implements some ATSSS goals (e.g., traffic aggregation). In some examples, the present disclosure provides a multi-access network without N3IWF, wherein a UE may transmit a request for a (non-integrated aggregation) PDU session, the request including a request for data aggregation across a 3GPP network and a non-3GPP network (e.g., a non-integrated IP network) to obtain an identification and an offload percentage of a core network aggregation entity (e.g., UPF). If the core network grants the request, the UE may: transmit some data to the UPF via the non-integrated IP network based on the offload percentage; and transmit other data to the UPF via the 3GPP network based on the offload percentage. The UE and the UPF may communicate over the non-integrated IP network using an agreed-upon proxy that includes some encryption method, thereby providing a security layer on the non-integrated network, which may otherwise be insecure. The UE and the UPF may communicate over the non-integrated IP network using an IP address determined during PDU session establishment. By using non-integrated aggregated PDU sessions and associated configuration information, in some examples, the present disclosure enables some of the features of ATSSS without providing N3IWF support (e.g., using a non-integrated IP network without interworking functionality). In some examples and stated another way, the non-integrated IP network may be configured to not provide control plane signaling with the core network (e.g., unlike N3IWF).

[0095] In some examples, the non-integrated IP network is configured to not provide a non-3GPP interworking function (N3IWF). The functionality of the N3IWF is defined in clause 6.2.9 of 3GPP TS 23.501 version 16, which states:

[0096] In the case of untrusted non-3GPP access, the functionality of N3IWF includes the following:

[0097] -Support IPsec tunnel establishment with UE: N3IWF terminates the IKEv2 / IPsec protocol with the UE through NWu, and relays the information required to authenticate the UE and authorize the UE to access the 5G core network through N2.

[0098] -Terminate the control plane and user plane to the N2 and N3 interfaces of the 5G core network respectively.

[0099] - Relays uplink and downlink control plane NAS (N1) signalling between the UE and the AMF.

[0100] -Handles N2 signalling from SMF (relayed by AMF) related to PDU sessions and QoS.

[0101] - Establish an IPsec Security Association (IPsec SA) to support PDU session services.

[0102] - Relaying uplink and downlink user plane packets between UE and UPF. This involves:

[0103] - Decapsulate / encapsulate packets transmitted by IPsec and N3 tunnels

[0104] - Implement QoS corresponding to N3 packet markings, taking into account the QoS requirements associated with such markings received via N2

[0105] - N3 user plane packet marking in uplink.

[0106] - Local mobility anchor within untrusted non-3GPP access networks using MOBIKE according to IETF RFC 4555

[57] .

[0107] - Support AMF selection.

[0108] In some examples, the non-integrated IP network is configured not to provide at least one of these N3IWF features. In some examples, the non-integrated IP network is configured not to provide any of these N3IWF features.

[0109] Figure 7 is a block diagram illustrating an example of a multiple access network 700 configured for non-integrated split / aggregation according to some aspects. The network 700 includes a UE 702, a 3GPP access node 704, a non-3GPP access node (e.g., a non-integrated IP network providing WiFi and IP access) 706, an AMF 708, an SMF 710, a PCF 712, and a UPF 714 providing access to a DN 716. Example interfaces (N1, N2, N3, N4, N6, N7, N11, and NX) for communication between the various entities are also shown. In some examples, the UE 702 may correspond to a UE in Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 8 , Fig.11 , Fig.12 and Fig.18 In some examples, the 3GPP access node 704 may correspond to any of the UEs or scheduled entities shown in any of the figures. Figure 1 , Figure 2 , Figure 4 , Figure 5 and Figure 6In some examples, AMF 708 may correspond to any of the access nodes, base stations, scheduling entities, or DUs shown in any of the figures. Figure 4 , Figure 6 , Figure 8 , Fig.11 and Fig.12 In some examples, SMF 710 may correspond to any of the AMF entities shown in any of the figures in FIG. Figure 4 , Figure 6 , Figure 8 , Fig.11 and Fig.12 In some examples, PCF 712 may correspond to any of the SMF entities shown in any of the figures in FIG. Figure 4 , Figure 6 , Figure 8 , Fig.11 and Fig.12 In some examples, UPF 714 may correspond to any of the PCF entities shown in any of the figures in FIG. Figure 4 , Figure 6 , Figure 8 , Fig.11 and Fig.12 In some examples, DN 716 may correspond to any of the UPF entities shown in any of the figures in FIG. Figure 1 , Figure 2 , Figure 4 , Figure 6 , Figure 8 , Fig.11 and Fig.12 Any one of the DN nodes shown in any of the figures.

[0110] UE 702 includes 3GPP access functionality for communicating with 3GPP access node / network 704 and non-3GPP access functionality for communicating with non-3GPP access network (non-integrated IP network via NX) 706. Non-3GPP access network functionality at UE 702 includes support for two proxy functions, namely MPTCP 721 and multipath QUIC (MP-QUIC) 723, for communicating with UPF 714 through non-integrated IP network / NX 706. UPF 714 includes proxy functionality and path management function (PMF) 724 for supporting 3GPP access network and non-3GPP access network (e.g., non-integrated IP network). More specifically, non-3GPP access functionality at UPF 714 includes support for two proxy functions, namely MPTCP 725 and MP-QUIC 727, for communicating with UE 702 through non-integrated IP network / NX 706.

[0111] and Figure 6Compared to the multiple access network 600 of FIG. 600 , the multiple access network 700 does not include the N3IWF 607. Instead, the non-3GPP access is provided by a non-integrated IP network 706, which is not integrated into the 3GPP access network and is configured not to provide a non-3GPP interworking function (N3IWF). Therefore, the non-integrated IP network 706 may be an insecure WiFi network. Communications on the non-integrated IP network 706 may be conducted using any one of the common proxies supported at both the UE and the UPF. Each of the proxies may employ encryption to make communications on the inherently insecure non-integrated IP network 706 more secure. In some examples, the IP network 706 may be referred to as a non-integrated network because it does not have access to a core network (e.g., Figure 7 All components except UE 702, 3GPP access 704, IP network 706 and data network 716; see also Figure 4 In some examples, the IP network 706 does not support the interworking functions performed by the N3IWF 607. In some examples, the non-integrated IP network 706 is configured not to provide non-3GPP interworking functions (N3IWF).

[0112] In operation, UE 702 may: establish a connection to the core network; transmit a request for a non-integrated aggregated PDU session having a request for data aggregation across 3GPP network 704 and non-integrated IP network 706; receive a response from the core network that grants the PDU session and includes identification information of a core network aggregation entity (e.g., UPF 714) and an offload percentage. UE 702 may then send data to UPF 714 via non-integrated IP network 706 based on the offload percentage, and may send data to UPF 714 via 3GPP network 704 based on the offload percentage. The identification information of UPF 714 may include at least two network addresses, one for an N3 interface at UPF 714, and one for an NX interface at UPF 714. The identification information may also include a list of agents supported at UPF 714, including at least one agent in common with UE 702. Additional details of multi-access network operations are provided below, including establishing PDU sessions, agents, and other configuration details.

[0113] Regarding the agents at UPF 714 (e.g., MPTCP 725 and MPQUIC 727), they may have two network addresses (e.g., IP addresses), one for the N3 interface (e.g., core network interface) and one for the non-3GPP IP network (NX) interface. In contrast, Figure 6The ATSSS implementation of uses only one network address for the N3 interface. In some examples, the UE may use two network addresses to transmit data over the multiple access network via each of N3 and NX.

[0114] In some examples, the MP-QUIC proxy may also be referred to as a Multiplexed Application Substrate over QUIC Encryption (MASQUE) proxy. In some examples of a MASQUE proxy, the establishment of the MASQUE proxy at the UE 702 and the UPF 714 is performed using only the N3 proxy network address at the UPF 714 over the N3 proxy link. In this case, the MPQUIC protocol itself may then handle the path IP address. In some examples, this is done because the NX interface / link is inherently insecure.

[0115] exist Figure 7 In the new architecture, in the case where UPF 714 uses MPTCP to support an unsecured NX interface, it may be necessary to protect the MPTCP proxy from potential attacks (e.g., third-party services). That is, in some instances, third-party MPTCP services may attempt to misuse the unprotected MPTCP proxy through the NX interface. One possible solution for protecting the MPTCP proxy is to allow only MP_CAPABLE SYN on N3 (e.g., defined by the Internet Engineering Task Force (IETF) and similar Transmission Control Protocol (TCP) defined SYN for establishing connections between devices using TCP, but for multipath TCP). In this case, NX can use only MP_JOIN (e.g., defined by the IETF for multipath TCP and used to identify connections to be joined by new sub-flows), and not allow new MPTCP connections on NX to establish new sub-flows to be allowed on NX. Another and potentially better solution is to allow only MP_CAPABLE SYN on N3, and not allow SYN or even MP_JOIN on NX. To implement this solution, the UE may transmit the UE's NX IP address to the MPTCP proxy via ADD_ADDR on N3 (e.g., defined by IETF for multipath TCP to notify another host of another potential address), and the server itself (UPF 714) then adds the new subpath. In this case, the MPTCP proxy server (at UPF 714) may then reject all subpath requests on NX. Thus, the MPTCP proxy server (at UPF 714) may be better protected. In some examples, once the NX interface link is established, the UE and UPF may use TLS encryption on the NX link to provide some security.

[0116] Figure 8810-H, PCF 812, V-UPF 814-V, and H-UPF 814 providing access to DN 816. Example interfaces (N1, N2, N3, N4, N6, N7, N9, N11, N16, and NX) for communication between various entities are also shown. In some examples, UE 802 may correspond to a 3GPP access node 804, a non-3GPP access node (e.g., a non-integrated IP network providing WiFi and IP access) 806, an AMF 808, a V-SMF 810-V, an H-SMF 810-H, a PCF 812, a V-UPF 814-V, and an H-UPF 814 providing access to a DN 816. Example interfaces (N1, N2, N3, N4, N6, N7, N9, N11, N16, and NX) for communication between various entities are also shown. In some examples, UE 802 may correspond to a 3GPP access node 804, a non-3GPP access node (e.g., a non-integrated IP network providing WiFi and IP access) 806, an AMF 808, a V-SMF 810-V, an H-SMF 810-H, a PCF 812, a V-UPF 814-V, and an H-UPF 814 providing access to a DN 816. Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 7 , Fig.11 , Fig.12 and Fig.18 Any one of the UEs or scheduled entities shown in any of the figures.

[0117] In some examples, 3GPP access node 804 may correspond to Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 and Figure 7 Any of the access nodes, base stations, scheduling entities, or DUs shown in any of the figures in FIG. In some examples, AMF 808 may correspond to Figure 4 , Figure 6 , Figure 7 , Fig.11 and Fig.12 In some examples, V-SMF 810-V and / or H-SMF 810-H may correspond to any of the AMF entities shown in any of the figures in FIG. Figure 4 , Figure 6 , Figure 7 , Fig.11 and Fig.12 In some examples, PCF 812 may correspond to any of the SMF entities shown in any of the figures in FIG. Figure 4 , Figure 6 , Figure 7 , Fig.11 and Fig.12In some examples, V-UPF 814-V and / or H-UPF 814-H may correspond to any of the PCF entities shown in any of the figures in FIG. Figure 4 , Figure 6 , Figure 7 , Fig.11 and Fig.12 In some examples, DN 816 may correspond to any of the UPF entities shown in any of the figures in FIG. Figure 1 , Figure 2 , Figure 4 , Figure 6 , Figure 8 , Fig.11 and Fig.12 Any one of the DN nodes shown in any of the figures. UE 802 includes support for two proxy functions, namely MPTCP 821 and MP-QUIC 823, for communicating with H-UPF 814-H through non-3GPP access network / NX (e.g., non-integrated IP network or NX) 806. H-UPF 814-H also includes support for two proxy functions, namely MPTCP 825 and MP-QUIC 827, for communicating with UE802 through non-integrated IP network / NX 806. In some examples, the MP-QUIC proxy may also be referred to as a Multiplexed Application Substrate over QUIC Encryption (MASQUE) proxy. In operation, in addition to the added components and links that make up the roaming architecture, the multiple access network 800 can be connected to Figure 7 The multiple access network 700 of FIG. 7 operates similarly. Since these components of the roaming architecture and their operation are known, this disclosure will not include further discussion of these components.

[0118] Fig. 9 90 is a conceptual illustration of two protocol stacks for MASQUE proxies according to some aspects. A first protocol stack 902 of the two protocol stacks may support MASQUE using IP (e.g., CONNECT-IP protocol for IP tunneling). A second protocol stack 904 may support MASQUE using UDP (e.g., CONNECT-UDP protocol for UDP tunneling). Both types of MASQUE proxies use MPQUIC encryption to provide security. These MASQUE proxies may be used by any of the UEs and UPFs described herein.

[0119] Fig.101004 and 1006. FIG. 1004 is a table illustrating characteristics of MPTCP proxy 1002 and MASQUE proxy 1004 according to some aspects. Any of these proxy types can be used at any of the UEs described herein or at any of the UPFs. For the MASQUE proxy, either MASQUE using UDP or MASQUE using IP can be used.

[0120] Figure 11 to Figure 12 1 is a signaling diagram 1100 illustrating an example of establishing a protocol data unit (PDU) session with non-integrated aggregation for a multiple access network according to some aspects. The diagram includes a user equipment (UE) 1102, a radio access network (RAN) 1204, CN entities (AMF 1206, UPF 1108, SMF 1110, PCF 1112, UDM 1114), and DN 1116. In some examples, UE 1102 may correspond to Figure 1 , Figure 2 , Figures 4 to 8 , Fig.12 and Fig.18 In some examples, RAN 1104 may correspond to any of the UEs or scheduled entities shown in any of the figures. Figure 1 , Figure 2 , Figures 4 to 8 and Fig.12 In some examples, AMF 1106 may correspond to any of the RAN nodes, CU nodes, or scheduling entities shown in any of the figures. Figure 4 , Figure 6 , Figure 7 , Figure 8 and Fig.12 In some examples, UPF 1108 may correspond to any of the AMF entities shown in any of the figures in Figure 4 , Figure 6 , Figure 7 , Figure 8 and Fig.12 In some examples, SMF 1110 may correspond to any of the UPF entities shown in any of the figures in FIG. Figure 4 , Figure 6 , Figure 7 , Figure 8 and Fig.12 In some examples, PCF 1112 may correspond to any of the SMF entities shown in any of the figures in FIG. Figure 4 , Figure 6 , Figure 7 , Figure 8 and Fig.12In some examples, UDM 1114 may correspond to any of the PCF entities shown in any of the figures in FIG. Figure 4 and Fig.12 In some examples, DN 1116 may correspond to any of the UDM entities shown in any of the figures in FIG. Figure 4 , Figure 6 , Figure 7 , Figure 8 and Fig.12 Any one of the DN nodes shown in any of the figures.

[0121] In some examples, Figure 11 to Figure 12 The PDU establishment procedure may be in accordance with clause 4.3.2.2 of 3GPP TS 25.502 version 16 (which describes, inter alia, UE requested PDU session establishment) and (of 3GPP TS 25.502) Figure 4 .3.2.2.1-1 (which illustrates Figure 11 to Figure 12 However, Figure 11 to Figure 12 The signaling diagram of illustrates a new procedure that builds on and modifies the PDU establishment procedure of clause 4.3.2.2 of 3GPP TS 25.502 version 16.

[0122] exist Fig.11 At #1, UE 1102 transmits a PDU session establishment request to AMF 1106. The request includes an indication or request for: multiple access aggregation across 3GPP networks and non-integrated IP networks, and a list of proxy types supported by the UE. In some examples, the request can be provided as a "NIA PDU Request" in an uplink non-access stratum (NAS) transport (e.g., UL NAS transport) message, and has a list of proxy types supported by the UE (MPTCP, UDP over HTTP3 (H3), IP over H3). In some examples, the "NIU PDU Request" request type in the UL NAS transport message indicates to the network that the PDU session establishment request will establish a new NIA PDU session and that the UPF proxy will aggregate the traffic.

[0123] In some examples, the UE may have established a connection to the core network / AMF 1106 through a 3GPP network. The PDU request may also include other request information specified in clause 4.3.2.2 of 3GPP TS 25.502 version 16. In some examples, the list of supported proxy types includes at least one proxy type supported by the UE. In some examples, the proxy type supported by the at least one UE may include one or more of the following: an MPTCP proxy type (e.g., using TLS encryption), a MASQUE proxy type using UDP, or a MASQUE proxy type using IP. In some examples, the PDU session request may also include an offload percentage requested by the UE, where the offload percentage indicates the percentage of data traffic to be routed via a non-integrated IP network.

[0124] In some examples, the UE may obtain an appropriate offload percentage or other PDU session request parameters based on a UE routing policy (URSP) specified by the core network. In some examples, the URSP may assist the UE in determining which user plane data resources to use for specific data types. In some examples, the URSP may be pre-configured by an operator or original equipment manufacturer (OEM), configured by the core network at registration, or configured by the core network (e.g., by a PLMN or PCF) at some time after registration. In some examples, the URSP includes rules for a given UE application regarding whether the given UE application is allowed to use a non-integrated IP network to perform multiple access aggregation, and in this case, includes an appropriate offload percentage.

[0125] Fig.13 13 is a table 1300 illustrating parameters 1302 in a routing descriptor for non-integrated WiFi aggregation according to some aspects. Fig.13 As shown, parameter 1302 may include a field for the offload percentage and a field indicating that the PCF may modify the parameter. This table may be used in conjunction with URSP rules to specify certain parameters for UE routing selection.

[0126] return Fig.11 And #1, in some examples, the PDU session request is transmitted according to the URSP rules for a given application executing on the UE 1102. In this case, for a given application, it can request more than one PDU session. In some examples, for any one application executing on the UE, the any one application can submit more than one PDU session request, but according to the URSP rules for the application, the offload percentage is the same across all PDU session requests for the application. In some examples, different applications executing on the UE 1102 can submit different PDU session requests and can have different offload percentages.

[0127] As described above, the UE 1102 may transmit a PDU session request along with a requested offload percentage and a list of proxy types supported by the UE.

[0128] Fig.14 An illustration of a parameter definition for a user equipment (UE) request for a PDU session with non-integrated aggregation according to some aspects. The parameter definition is for a non-integrated aggregation (NIA) PDU session request with a protocol control option (PCO). The illustration includes a first table 1402 showing possible parameter configurations for specifying an offload percentage. The illustration also includes a second table 1404 showing possible parameter configurations for specifying a proxy type supported by the UE, the possible parameter configurations including bits for specifying: (1) whether MPTCP aggregation functionality is supported (e.g., MPTCP proxy), (2) whether H3-based UDP aggregation is supported (e.g., MASQUE proxy via UDP), (3) whether H3-based UDP and IP aggregation is supported (e.g., MASQUE proxy via IP), and (4) whether each of (1) and (3) is supported. In some examples, the request for a PDU session may therefore include: the offload percentage requested by the UE, whether the UE supports the MPTCP proxy type, whether the UE supports the MASQUE proxy type using UDP, and / or whether the UE supports the MASQUE proxy type using IP, and any combination of these. Although Tables 1402 and 1404 illustrate one specific implementation for specifying parameters for a UE-requested NIA PDU session, other specific implementations are contemplated herein.

[0129] In some examples, the UE is configured to transmit requests for NIA PDU sessions only over the 3GPP network. In this case, the establishment and configuration of the unsecured non-3GPP network (e.g., non-integrated IP network) is performed only over the secure integrated network (e.g., 3GPP network).

[0130] Back to Fig.11 , and at #2, AMF 1106 may select SMF 1110 to participate in the establishment of the requested PDU session.

[0131] At #3, AMF 1106 transmits a Nsmf_PDUSession_CreateSMContext request to SMF 1110, which includes an indication / request for: multiple access aggregation, and a list of proxy types supported by the UE. In some examples, the request may be transmitted in accordance with clause 4.3.2.2 of 3GPP TS 25.502 version 16. At #3, AMF 1106 notifies SMF 1110 that the request is for a NIA PDU session by including a "NIA PDU Request" indication.

[0132] At #4, SMF 1110 retrieves information via session management subscription data regarding whether the NIA PDU session is allowed.

[0133] At #5, SMF 1110 transmits a Nsmf_PDUSession_CreateSMContext response to AMF 1106.

[0134] At #6, the core network (eg, SMF 1110) may determine whether the PDU session is legitimate via an authentication procedure, and authorize the PDU session based on the authentication.

[0135] At #7a, SMF 1110 may execute the PCF selection procedure to select PCF 1112.

[0136] At #7b, SMF 1110 may perform SM policy association establishment or SMF initiated SM policy association modification. In some examples, if dynamic policy control and charging (PCC) rules are to be used for NIA PDU sessions, SMF 1110 may transmit a "NIA PDU request" indication (e.g., where the indication includes a UE request for aggregation) to PCF 1112 in a SM policy control create message. PCF 1112 may decide whether to allow the NIA PDU session based on operator policy and subscription data. The default PCC rule may include an offload percentage.

[0137] At #8, SMF 1110 selects UPF 1108 for the PDU Session. In some examples, UPF selection (clause 6.3.3.3 of TS 23.501) takes into account the proxy capabilities of the UPF (e.g., selecting a UPF that supports at least one of the proxies supported by the UE).

[0138] At #9, SMF 1110 performs SMF-initiated SM policy association modification according to clause 4.3.2.2.1 of TS 23.502.

[0139] At #10a, SMF 1110 transmits an N4 session establishment / modification request to UPF 1108. In addition, and at #10a, as part of the NIA PDU session request, SMF 1110 also transmits the proxy type to be used and the offload percentage of the NIA PDU session service to UPF via a service data flow (SDF) template.

[0140] At #10b, UPF 1108 transmits an N4 session establishment / modification response to SMF 1110. In addition, and at #10b, UPF 1108 transmits a proxy address to SMF 1110 (eg, a proxy address of UPF 1108 to be used by UE 1102).

[0141] Fig.15 1502 is an illustration of a parameter definition 1500 for a proxy address of a UPF associated with a PDU session with non-integrated aggregation according to some aspects. The parameter includes a UPF proxy address information information element (IE) that includes a specified number of octets for the IE. The IE includes a proxy N3 port, a proxy NX port, a proxy N3 IPv4 address, a proxy N3 IPv6 address, a proxy NX IPv4 address, a proxy NX IPv6 address, and a proxy type, as shown in table 1502. In some examples, in Fig.11 At #10b in , UPF 1108 can use this parameter definition to transmit the proxy address to SMF.

[0142] Return now Fig.12 And at #11, SMF 1110 transmits a Namf_Communication_N1N2MessageTransfer message to AMF 1106. In some examples, for a NIA PDU session, the SMF includes an "NIA PDU session accepted" indication in the Namf_Communication_N1N2MessageTransfer message to AMF 1106, and indicates to AMF 1006 that the N2 SM information included in the message should be transmitted via 3GPP access.

[0143] At #12, AMF 1106 transmits an N2 PDU Session Request (NAS message) to RAN 1104.

[0144] At #13, the RAN 1104 and the UE 1102 perform an AN specific resource establishment (PDU Session Establishment Accept). At #13, the UE 1102 receives a PDU Session Establishment Accept message, which indicates to the UE 1102 that the requested NIA PDU session is successfully established. The message includes the proxy type and address information from the SMF 1110. In some examples, the message may include a NIA Response Policy Control Option (PCO) parameter. In some examples, the message may also include an offload percentage.

[0145] Fig.161600 (e.g., NIA response PCO parameters) for a core network response to a UE request for a PDU session with non-integrated aggregation in accordance with some aspects. Parameter definition 1600 includes table 1602 for proxy IP address type, proxy IP address (e.g., IP address of an N3 or NX link), proxy port, proxy type, and offload percentage. Parameter definition 1600 also includes table 1604, which describes or enumerates various proxy IP address types (e.g., IPv4, IPv6, IPv4v6) that can be used in table 1602. Table 1604 also describes or enumerates proxy types (e.g., MPTCP proxy, UDP proxy over HTTP3, IP proxy over HTTP3) that can be used in table 1602. Table 1604 also specifies that the offload percentage can be a value between 0 and 100. In some examples, UE 1102 Fig.12 The message received in #13 of may implement the message format of parameter definition 1600. Although tables 1602 and 1604 illustrate one specific implementation of parameters for specifying a core network response to a UE-requested NIA PDU session, other specific implementations are contemplated herein.

[0146] return Fig.12 and #13, UE 1102 may receive a response from the core network granting the requested NIA PDU session, the response (e.g., Fig.16 The NIA response PCO parameter 16) includes the identification of the core network aggregation entity (e.g., the UPF selected for the N3 and NX interfaces and its IP address) and the offload percentage.

[0147] In some examples, there is no PMF functionality for NIA PDU sessions.

[0148] At each of #14 to #21, a NIA PDU establishment session may be performed according to clause 4.3.2.2.1 of TS 23.502.

[0149] In some examples, the NIA PDU establishment session procedure can be extended to the home routing roaming case. In some examples, the procedures involving SMF, PCF and UPF are performed by H-SMF using N16 interface, H-PCF, and H-UPF using N9 interface respectively.

[0150] Fig.17is an illustration of a modified procedure 1700 for a non-integrated aggregation (NIA) PDU session establishment according to some aspects. In some examples, the modified procedure 1700 may illustrate and highlight changes to clause 4.3.2.2.1 of TS 23.502 in a PDU session establishment procedure that is used to alternatively provide a non-integrated aggregation (NIA) PDU session establishment described herein. Fig.11 and Fig.12 These changes are described in the discussion of the signaling diagrams for Fig.17 These changes are shown in to highlight them.

[0151] Fig.18 1800 is a block diagram illustrating an example of a hardware implementation of a user equipment employing a processing system according to some aspects. For example, UE 1800 may be a device configured to wirelessly communicate with a base station, such as in Figures 1 to 17 In some implementations, UE 1800 may correspond to Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 8 , Fig.11 and Fig.12 Any one of the UEs or scheduled entities shown in any of the figures.

[0152] According to various aspects of the present disclosure, any combination of elements or any part of elements or elements can be implemented using a processing system 1814. The processing system 1814 may include one or more processors 1804. Examples of processors 1804 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. In various examples, the UE 1800 may be configured to perform any one or more of the functions described herein. That is, the processor 1804 as utilized in the UE 1800 may be used to implement any one or more of the processes and procedures described herein.

[0153] In some examples, the processor 1804 may be implemented via a baseband or modem chip, and in other implementations, the processor 1804 may include several devices distinct and other than a baseband or modem chip (e.g., in scenarios such as those that may work together to implement the examples discussed herein). And as mentioned above, various hardware arrangements and components outside of a baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0154] In this example, the processing system 1814 may be implemented using a bus architecture (which is generally represented by bus 1802). The bus 1802 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1814 and the overall design constraints. The bus 1802 communicatively couples various circuits including one or more processors (which are generally represented by processor 1804), memory 1805, and computer-readable media (which are generally represented by computer-readable media 1806). The bus 1802 may also link various other circuits (such as timing sources, peripherals, voltage regulators, and power management circuits), which are well known in the art and therefore will not be further described. The bus interface 1808 provides an interface between the bus 1802 and the transceiver 1810 and between the bus 1802 and the interface 1830. The transceiver 1810 provides a communication interface or component for communicating with various other devices through a wireless transmission medium. In some examples, the UE may include two or more transceivers 1810. The interface 1830 provides a communication interface or component for communicating with various other devices and equipment (e.g., other devices contained in the same device as the UE or other external devices) through an internal bus or an external transmission medium (such as an Ethernet cable). Depending on the nature of the device, the interface 1830 may include a user interface (e.g., a keypad, a display, a speaker, a microphone, a joystick). Of course, such a user interface is optional and may be omitted in some examples (such as IoT devices).

[0155] The processor 1804 is responsible for managing the bus 1802 and general processing, including executing software stored on the computer-readable medium 1806. The software, when executed by the processor 1804, causes the processing system 1814 to perform various functions described below for any particular device. The computer-readable medium 1806 and the memory 1805 can also be used to store data manipulated by the processor 1804 when executing the software. For example, the memory 1805 may include PDU session information 1815 used by the processor 1804 in cooperation with the transceiver 1810 to send and / or receive data associated with a PDU session or data splitting.

[0156] One or more processors 1804 in the processing system can execute software. Software should be construed broadly to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a computer-readable medium 1806.

[0157] Computer readable medium 1806 may be a non-transitory computer readable medium. Non-transitory computer readable media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 1806 may reside in processing system 1814, be located outside processing system 1814, or be distributed across multiple entities including processing system 1814. Computer readable medium 1806 may be embodied in a computer program product. For example, a computer program product may include a computer readable medium in a packaging material. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure, depending on the specific application and the overall design constraints imposed on the overall system.

[0158] UE 1800 may be configured to perform any one or more of the operations described herein (e.g., as described above in conjunction with Figures 1 to 17 As described and as follows Fig.19 In some aspects of the present disclosure, the processor 1804 as utilized in the UE 1800 may include circuits configured for various functions.

[0159] The processor 1804 may include a communication and processing circuit 1841. The communication and processing circuit 1841 may be configured to communicate (e.g., via an IP network) with a base station (such as a gNB) and / or a core network entity (such as a UPF). The communication and processing circuit 1841 may include one or more hardware components that provide a physical structure that performs various processes related to wireless communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuit 1841 may also include one or more hardware components that provide a physical structure that performs various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. In some examples, the communication and processing circuit 1841 may include two or more transmit / receive chains, each configured to process signals of different RAT (or RAN) types. The communication and processing circuit 1841 may also be configured to execute communication and processing software 1851 included on the computer-readable medium 1806 to implement one or more functions described herein.

[0160] In some implementations where communication involves receiving information, the communication and processing circuitry 1841 may obtain information from a component of the UE 1800 (e.g., from a transceiver 1810 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry 1841 may output the information to another component of the processor 1804, to the memory 1805, or to the bus interface 1808. In some examples, the communication and processing circuitry 1841 may receive one or more of the following: a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1841 may receive information via one or more channels. In some examples, the communication and processing circuitry 1841 may include functionality for components for receiving. In some examples, the communication and processing circuitry 1841 may include functionality for components for decoding.

[0161] In some implementations where communication involves transmitting (e.g., sending) information, the communication and processing circuitry 1841 may obtain the information (e.g., from another component of the processor 1804, the memory 1805, or the bus interface 1808), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuitry 1841 may output the information to the transceiver 1810 (e.g., which transmits the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuitry 1841 may transmit one or more of the following: a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1841 may transmit the information via one or more channels. In some examples, the communication and processing circuitry 1841 may include functionality for components for transmitting (e.g., components for sending). In some examples, the communication and processing circuitry 1841 may include functionality for components for encoding.

[0162] Processor 1804 may include a processor configured to establish communication with a core network via a 3GPP network (eg, in conjunction with Figures 7 to 17 , Fig.19 The communication and processing circuit 1841 may be configured to execute communication and processing software 1852 included on the computer-readable medium 1806 to implement one or more functions described herein.

[0163] The communication and processing circuitry 1841 may include functionality for components for communicating with the core network via the 3GPP network (e.g., as combined with Fig.19 For example, the UE may establish communication with a 3GPP network (eg, a 5G network).

[0164] Processor 1804 may include a processor configured to perform PDU session configuration related operations as discussed herein (e.g., in conjunction with Figures 7 to 17 , Fig.19 The PDU session configuration circuit 1842 may be configured to execute the PDU session configuration software 1852 included on the computer-readable medium 1806 to implement one or more functions described herein.

[0165] The PDU session configuration circuitry 1842 may include functionality for components for sending a request for a PDU session to the core network, the request including a request for data aggregation across the 3GPP network and the non-integrated IP network (e.g., as combined with Fig.11 #1 Fig.14 and / or Fig.19For example, the PDU session configuration circuit 1842 may be configured to send a request for a PDU session to the core network, the request including a request for data aggregation across a 3GPP network (e.g., a 5G network) and a non-integrated IP network (e.g., a WiFi network).

[0166] The PDU session configuration circuit 1842 may include functionality for a component for receiving a response from the core network granting the requested PDU session, the response including an identification of the core network aggregation entity and an offload percentage (e.g., as combined with Fig.12 #13 Fig.16 and / or Fig.19 For example, the PDU session configuration circuit 1842 may be configured to receive a response from the core network granting the requested PDU session, the response including an identification of the core network aggregation entity (eg, a network address of the UPF) and an offload percentage.

[0167] Processor 1804 may include processors configured to perform data splitting / aggregation related operations as discussed herein (e.g., in conjunction with Figures 7 to 17 The data splitting circuit 1843 may be configured to execute the data splitting software 1853 included on the computer readable medium 1806 to implement one or more functions described herein.

[0168] The data splitting circuit 1843 may include functionality for components for sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage (e.g., as combined with Fig.19 For example, the data splitting circuit 1843 may be configured to send data to a core network aggregation entity (eg, UPF) via the non-integrated IP network based on the offload percentage.

[0169] The data splitting circuit 1843 may include functionality for components for sending data to the core network aggregation entity via the 3GPP network based on the offload percentage (e.g., as combined with Fig.19 For example, the data splitting circuit 1843 may be configured to send data to the core network aggregation entity via the 3GPP network (eg, 5G network) based on the offload percentage.

[0170] Fig.19 1 is a flow chart illustrating an example method 1900 for wireless communication according to some aspects of the present disclosure. As described herein, in certain implementations within the scope of the present disclosure, some or all of the illustrated features may be omitted, and some of the illustrated features may not be necessary for implementation of all examples. In some examples, method 1900 may be performed by Fig.18In some examples, the method 1900 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0171] At block 1902, the user equipment may communicate with the core network via the 3GPP network. Fig.18 The communication and processing circuitry 1841 and transceiver 1810 shown and described may provide means for communicating with a core network over a 3GPP network.

[0172] At block 1904, the user equipment may send a request for a PDU session to the core network, the request including a request for data aggregation across the 3GPP network and the non-integrated IP network. Fig.18 The PDU session circuitry 1842 and transceiver 1810 shown and described may provide means for sending a request for a PDU session to a core network, the request including a request for data aggregation across a 3GPP network and a non-integrated IP network.

[0173] At block 1906, the user equipment may receive a response from the core network granting the requested PDU session, the response including an identification of the core network aggregation entity and an offload percentage. Fig.18 The PDU session circuitry 1842 and transceiver 1810 shown and described may provide means for receiving a response from the core network granting the requested PDU session, the response including an identification of the core network aggregation entity and an offload percentage.

[0174] At block 1908, the user equipment may send data to the core network aggregation entity via the non-integrated IP network based on the offload percentage. Fig.18 The data splitting circuit 1843 and transceiver 1810 shown and described may provide means for sending data to a core network aggregation entity via a non-integrated IP network based on an offload percentage.

[0175] At block 1910, the user equipment may send data to the core network aggregation entity via the 3GPP network via the transceiver based on the offload percentage. Fig.18 The data splitting circuit 1843 and transceiver 1810 shown and described may provide means for sending data via the transceiver to a core network aggregation entity via the 3GPP network based on the offload percentage.

[0176] In some examples, the non-integrated IP network includes a WiFi network, and the 3GPP network includes a 5G network.

[0177] In some examples, the core network aggregation entity includes a user plane function (UPF) device.

[0178] In some examples, the UE includes at least one application configured to execute on the UE, the UE is configured to send a request for the PDU session from the at least one application to the core network, and the UE is configured to send data from the at least one application to the core network aggregation entity via the non-integrated IP network based on an offload percentage.

[0179] In some examples, the UE may receive a UE routing policy (URSP), and the UE may send a request for a PDU session to the core network based on the URSP.

[0180] In some examples, the request for a PDU session to the core network also includes indications of a requested offload percentage, whether the UE supports a Multipath Transport Control Protocol (MPTCP) proxy type, whether the UE supports a Multiplexed Application Substrate over QUIC using User Datagram Protocol (UDP) (MASQUE) proxy type, and whether the UE supports a MASQUE proxy type using Internet Protocol (IP).

[0181] In some examples, the response from the core network granting the requested PDU session also includes indications of the granted offload percentage, whether the core network aggregation entity supports the Multipath Transmission Control Protocol (MPTCP) proxy type, whether the core network aggregation entity supports the Multiplexed Application Substrate over QUIC (MAQUE) proxy type using the User Datagram Protocol (UDP), and whether the core network aggregation entity supports the MAQUE proxy type using the Internet Protocol (IP).

[0182] In some examples, the response from the core network granting the requested PDU session also includes a network address of a core network aggregation entity for each of the 3GPP network and the non-integrated IP network, and the response from the core network granting the requested PDU session also includes an indication of the IP address type of the network address of the core network aggregation entity for each of the 3GPP network and the non-integrated IP network.

[0183] In some examples, the UE may send a request for a PDU session to the core network via the 3GPP network (e.g., only via the 3GPP network), and the UE may receive a response from the core network via the 3GPP network (e.g., only via the 3GPP network) granting the requested PDU session.

[0184] In some examples, the non-integrated IP network is configured to not provide a non-3GPP interworking function (N3IWF).

[0185] In some examples, a request for a PDU session to the core network also includes at least one proxy type supported by the UE, a response from the core network granting the requested PDU session includes at least one supported proxy type of the core network aggregation entity, the at least one supported proxy type includes a proxy type supported by the UE, and the UE can use the proxy type supported by both the UE and the core network aggregation entity to send data to the core network aggregation entity via the non-integrated IP network based on an offload percentage.

[0186] In some examples, the response from the core network granting the requested PDU session also includes the network address of the core network aggregation entity of each of the 3GPP network and the non-integrated IP network, and the UE can use a proxy type supported by both the UE and the core network aggregation entity to send data to the core network aggregation entity using the network address of the non-integrated IP network according to the offload percentage.

[0187] In some examples, the proxy types supported by at least one UE include at least one of the following: a Multipath Transmission Control Protocol (MPTCP) proxy type, a Multiplexed Application Substrate over QUIC using User Datagram Protocol (UDP) (MASQUE) proxy type, or a MASQUE proxy type using Internet Protocol (IP), and at least one supported proxy type of the core network aggregation entity includes at least one of the following: an MPTCP proxy type, a MASQUE proxy type using UDP, or a MASQUE proxy type using IP.

[0188] In some examples, at least one supported proxy type includes a Multipath Transport Control Protocol (MPTCP) proxy type, and the UE may send data to the core network aggregation entity via the non-integrated IP network based on an offload percentage using the MPTCP proxy type and encryption provided by Transport Layer Security (TLS).

[0189] In some examples, the offload percentage indicates a percentage of data traffic to be routed via the non-integrated IP network.

[0190] Fig. 20 2014 is a block diagram illustrating an example of a hardware implementation of a network entity 2000 employing a processing system 2014 according to some aspects. In some implementations, the network entity 1800 may correspond to Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 8 , Fig.11 and Fig.12 Any of the UFP entities shown in any of the figures.

[0191] According to various aspects of the present disclosure, the processing system 2014 may be used to implement an element or any part of an element or any combination of elements. The processing system may include one or more processors 2004. The processing system 2014 may be used with Fig.18 The processing system 1814 illustrated in FIG. 1 is substantially the same, including a bus interface 2008, a bus 2002, a memory 2005, a processor 2004, and a computer-readable medium 2006. In addition, the network entity 2000 may include an interface 2030 (e.g., a network interface) that provides means for communicating with at least one other device within the core network and with at least one radio access network.

[0192] The network entity 2000 may be configured to perform any one or more of the operations described herein (eg, as described above in conjunction with Figures 1 to 17 As described and as follows Fig.21 In some aspects of the present disclosure, the processor 2004 as utilized in the network entity 2000 may include circuits configured for various functions.

[0193] Processor 2004 may be configured to generate, schedule, and modify resource assignments or grants of time-frequency resources (e.g., a set of one or more resource elements). For example, processor 2004 may schedule time-frequency resources within multiple time division duplex (TDD) and / or frequency division duplex (FDD) subframes, time slots, and / or mini-slots to carry user data traffic and / or control information to and / or from multiple UEs.

[0194] The processor 2004 may also be configured to schedule resources for transmission of uplink signals. The processor 2004 may be configured to schedule uplink resources that may be used by the UE to send uplink messages (e.g., PUCCH, PUSCH, PRACH opportunities, or RRC messages). In some examples, the processor 2004 may be configured to schedule uplink resources in response to receiving a scheduling request from the UE.

[0195] In some aspects of the present disclosure, the processor 2004 may include a communication and processing circuit 2041. The communication and processing circuit 2004 may be configured to communicate with a UE. The communication and processing circuit 2041 may include one or more hardware components that provide a physical structure that performs various processes related to communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuit 2041 may also include one or more hardware components that provide a physical structure that performs various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. The communication and processing circuit 2041 may also be configured to execute communication and processing software 2051 included on the computer-readable medium 2006 to implement one or more functions described herein.

[0196] In some implementations where communication involves receiving information, the communication and processing circuitry 2041 may obtain information from a component of the network entity 2000 (e.g., from a transceiver 2010 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry 2041 may output the information to another component of the processor 2004, to the memory 2005, or to the bus interface 2008. In some examples, the communication and processing circuitry 2041 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 2041 may receive information via one or more channels. In some examples, the communication and processing circuitry 2041 may include functionality for components for receiving. In some examples, the communication and processing circuitry 2041 may include functionality for components for decoding.

[0197] In some implementations where communication involves transmitting (e.g., sending) information, the communication and processing circuitry 2041 may obtain the information (e.g., from another component of the processor 2004, the memory 2005, or the bus interface 2008), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuitry 2041 may output the information to the transceiver 2010 (e.g., the transceiver sends the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuitry 2041 may transmit one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 2041 may transmit the information via one or more channels. In some examples, the communication and processing circuitry 2041 may include functionality for components for transmitting (e.g., components for sending). In some examples, the communication and processing circuitry 2041 may include functionality for components for encoding.

[0198] Processor 2004 may include a processor configured to perform N4 session establishment related operations as discussed herein (e.g., in conjunction with Figure 11 to Figure 12 and Fig.21 The communication and processing circuit 2041 may be configured to execute communication and processing software 2051 included on the computer readable medium 2006 to implement one or more functions described herein.

[0199] The communication and processing circuitry 2041 may include functionality for components for receiving (eg, from an SMF) an N4 session establishment request with a proxy type and an offload percentage (eg, as combined with Fig.11 #10a and / or Fig.21 as described in box 2102).

[0200] The communication and processing circuitry 2041 may include functionality for components for sending an N4 session establishment response with proxy address information (eg, to an SMF) (eg, as described in conjunction with Fig.11 #10b and / or Fig.21 as described in box 2104).

[0201] Processor 2004 may include a processor configured to perform data splitting / aggregation related operations as discussed herein (e.g., in conjunction with Figures 7 to 17 The data splitting (and aggregation) circuit 2042 may be configured to execute data splitting software 2052 included on the computer-readable medium 2006 to implement one or more functions described herein.

[0202] The data splitting circuit 2042 may include functionality for a component for receiving the first data via the 3GPP network (eg, from the UE) based on the offload percentage (eg, as combined with Fig.21 as described in box 2106).

[0203] The data splitting circuit 2042 may include functionality for a component for receiving the second data via the non-integrated IP network (eg, from the UE) based on the offload percentage (eg, as combined with Fig.21 as described in box 2108).

[0204] Fig.21 2100 is a flowchart illustrating an example method 2100 for communicating using non-integrated aggregation according to some aspects. As described herein, in certain implementations within the scope of the present disclosure, some or all of the illustrated features may be omitted, and some of the illustrated features may not be necessary for implementation of all examples. In some examples, the method 2100 may be performed by Fig. 20 In some examples, the method 2100 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0205] At block 2102, a network entity (eg, UPF) may receive (eg, from an SMF) an N4 session establishment request with proxy type and offload percentage information. Fig. 20 The communication and processing circuitry 2041 shown and described, along with the transceiver 2010, may provide means for receiving an N4 session establishment request (eg, from an SMF) with proxy type and offload percentage information.

[0206] At block 2104, the network entity (eg, UPF) may send (eg, to the SMF) an N4 session establishment response with a proxy address. Fig. 20 The communication and processing circuitry 2041 shown and described, together with the transceiver 2010, may provide means for sending an N4 session establishment response with a proxy address (eg, to an SMF).

[0207] At block 2106, the network entity (eg, UPF) may receive first data via the 3GPP network (eg, from the UE) based on the offload percentage. Fig. 20 The data splitting circuit 2042 shown and described, together with the transceiver 2010, may provide means for receiving first data via the 3GPP network (eg, from a UE) based on the offload percentage.

[0208] At block 2108, the network entity (eg, UPF) may receive second data via the non-integrated IP network (eg, from the UE) based on the offload percentage. Fig. 20 The data splitting circuit 2042 shown and described, together with the transceiver 2010, may provide means for receiving second data via the non-integrated IP network (eg, from a UE) based on the offload percentage.

[0209] In some examples, the UPF may also aggregate the first data and the second data to send to a data network (eg, any one of data networks 716 , 816 , 1116 ).

[0210] In some examples, the UPF (or another core network entity) may also provide the address of the proxy at the UPF to the UE via the 3GPP network or the non-integrated IP network.

[0211] In short, return Figure 7 , for example, by Figure 7 Used on multiple access networks Figure 11 to Figure 12 One problem that has been solved by the method is that the UPF and therefore the proxy on the UPF is selected during the UPF selection process of PDU session establishment, and therefore the URSP rules may not be able to carry the final proxy information. Another way to solve this problem is as follows. The proxy configuration can be done semi-statically. In some examples, a proxy table can be used to specify the proxy type and network address of each of the N3 interface and the NX interface.

[0212] In some examples, the UPF / proxy address mapping table may be (semi-)statically configured at the UE or provided via URSP rules. In some examples, the proxy table may also include a PLMN identifier to enable static configuration for multiple PLMNs. Regarding information about the proxy type and split percentage to be used at the UE, the UE may use URSP rules to obtain this information on a per-application basis. In some examples, and regarding the uplink to UPF split percentage, this may not be required, as the UPF may decide this dynamically based on its load situation.

[0213] Fig.19 and Fig.21 The methods shown in may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein. A summary of several aspects of the disclosure is provided below.

[0214] Aspect 1: A method for wireless communication at a user equipment (UE), the method comprising: communicating with a core network through a third generation partnership project (3GPP) network; sending a request for a protocol data unit (PDU) session to the core network, the request comprising a request for data aggregation across the 3GPP network and a non-integrated Internet Protocol (IP) network; receiving a response from the core network granting the requested PDU session, the response comprising an identifier of a core network aggregation entity and an offload percentage; sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage; and sending data to the core network aggregation entity via the 3GPP network based on the offload percentage.

[0215] Aspect 2: A method according to Aspect 1, wherein the request to the core network for the PDU session also includes at least one proxy type supported by the UE; wherein the response from the core network granting the requested PDU session includes at least one supported proxy type of the core network aggregation entity, and the at least one supported proxy type includes a proxy type supported by the UE; and wherein sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage includes: using a proxy type supported by both the UE and the core network aggregation entity, and sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage.

[0216] Aspect 3: A method according to Aspect 2, wherein the response from the core network granting the requested PDU session also includes the network address of the core network aggregation entity of each of the 3GPP network and the non-integrated IP network; and wherein sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage includes: using a proxy type supported by both the UE and the core network aggregation entity, and sending data to the core network aggregation entity using the network address of the non-integrated IP network according to the offload percentage.

[0217] Aspect 4: A method according to Aspect 2, wherein the proxy types supported by the at least one UE include at least one of the following: a Multipath Transmission Control Protocol (MPTCP) proxy type, a QUIC-based Multiplexed Application Substrate (MASQUE) proxy type using a User Datagram Protocol (UDP), or a MASQUE proxy type using an Internet Protocol (IP); and wherein the at least one supported proxy type of the core network aggregation entity includes at least one of the following: an MPTCP proxy type, a MASQUE proxy type using UDP, or a MASQUE proxy type using IP.

[0218] Aspect 5: A method according to Aspect 2, wherein the at least one supported proxy type includes a Multipath Transmission Control Protocol (MPTCP) proxy type; and wherein sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage includes: using the MPTCP proxy type and encryption provided by the Transport Layer Security Protocol (TLS), and sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage.

[0219] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the non-integrated IP network includes a WiFi network; wherein the 3GPP network includes a 5G network; and wherein the core network aggregation entity includes a user plane function (UPF) device.

[0220] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method further includes executing at least one application on the UE; wherein sending the request for the PDU session to the core network includes: sending the request for the PDU session from the at least one application to the core network; and wherein sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage includes: sending data from the at least one application to the core network aggregation entity via the non-integrated IP network based on the offload percentage.

[0221] Aspect 8: A method according to any one of Aspects 1 to 7, wherein the request to the core network for the protocol data unit (PDU) session also includes an indication of: a requested offload percentage; whether the UE supports a multipath transmission control protocol (MPTCP) proxy type; whether the UE supports a multiplexed application substrate over QUIC (MASQUE) proxy type using a user datagram protocol (UDP); and whether the UE supports a MASQUE proxy type using an Internet Protocol (IP).

[0222] Aspect 9: A method according to any one of Aspects 1 to 8, wherein the response from the core network granting the requested PDU session also includes an indication of: a granted offload percentage; whether the core network aggregation entity supports a Multipath Transmission Control Protocol (MPTCP) proxy type; whether the core network aggregation entity supports a Multiplexed Application Substrate over QUIC (MASQUE) proxy type using a User Datagram Protocol (UDP); and whether the core network aggregation entity supports a MASQUE proxy type using an Internet Protocol (IP).

[0223] Aspect 10: A method according to Aspect 9, wherein the response from the core network granting the requested PDU session also includes: a network address of the core network aggregation entity of each of the 3GPP network and the non-integrated IP network; and an indication of the IP address type of the network address of the core network aggregation entity of each of the 3GPP network and the non-integrated IP network.

[0224] Aspect 11: A method according to any one of Aspects 1 to 10, wherein sending the request for the PDU session to the core network includes: sending the request for the PDU session to the core network via the 3GPP network; and wherein receiving the response from the core network granting the requested PDU session includes: receiving the response from the core network granting the requested PDU session via the 3GPP network.

[0225] Aspect 12: The method according to any one of aspects 1 to 10, wherein the non-integrated IP network is configured not to provide a non-3GPP interworking function (N3IWF).

[0226] Aspect 13: The method according to any one of aspects 1 to 12, wherein the offload percentage indicates a percentage of data traffic to be routed via the non-integrated IP network.

[0227] Aspect 14: A method according to any one of Aspects 1 to 13, wherein the non-integrated IP network comprises a WiFi network; and wherein the 3GPP network comprises a 5G network.

[0228] Aspect 15: A user equipment, comprising: a transceiver configured to communicate with a radio access network; a memory; and a processor coupled to the transceiver and the memory, wherein the processor is configured to perform any one of aspects 1 to 14.

[0229] Aspect 16: An apparatus (eg, UE) configured for wireless communication, the apparatus comprising: at least one component for performing any one of aspects 1 to 14.

[0230] Aspect 17: A non-transitory computer-readable medium storing computer-executable codes, the non-transitory computer-readable medium comprising: codes for causing an apparatus to perform any one of aspects 1 to 14.

[0231] Several aspects of wireless communication networks have been presented with reference to example implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards.

[0232] By way of example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution Data Optimized (EV-DO). Other examples may be implemented within systems employing Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0233] Within the present disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration". Any specific implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior or superior to other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the discussed features, advantages, or modes of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may still be considered to be coupled to each other, even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object, even if the first object has never been in direct physical contact with the second object. The terms "circuit" and "circuitry" are used broadly, and they are intended to include both hardware implementations of electronic devices and conductors (where these electronic devices and conductors, when connected and configured, implement the execution of the functions described in the present disclosure, without limitation on the type of electronic circuits) and software implementations of information and instructions (where these information and instructions, when executed by a processor, implement the execution of the functions described in the present disclosure). As used herein, the term "determine" may include a variety of actions. For example, "determine" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), ascertaining, resolving, selecting, choosing, establishing, receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc.

[0234] Figures 1 to 21 One or more of the illustrated components, steps, features, and / or functions may be rearranged and / or combined into a single component, step, feature, or function, or may be embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 8 , Fig.11 , Fig.12 , Fig.18 and Fig. 20 The apparatus, device and / or component illustrated in any figure in the can be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein can also be effectively implemented in software and / or embedded in hardware.

[0235] It should be understood that the specific order or hierarchy of steps in the methods disclosed herein is illustrative of example processes. It should be understood that the specific order or hierarchy of steps in these methods can be rearranged based on design preferences. The attached method claims present elements of the various steps in a sample order and are not meant to be limited to the specific order or hierarchy presented unless specifically stated herein.

[0236] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the text of the claims, wherein unless explicitly stated otherwise, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. The phrase "at least one" referring to a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are currently or hereafter known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, regardless of whether such disclosures are explicitly recited in the claims, anything disclosed herein is not intended to be disclosed to the public.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: Transceiver; and a processor coupled to the transceiver and configured to: Communicates with the core network via the 3rd Generation Partnership Project (3GPP) network; sending, via the transceiver, to the core network a request for a protocol data unit (PDU) session, the request comprising a request for data aggregation across the 3GPP network and a non-integrated Internet Protocol (IP) network; receiving, via the transceiver, a response from the core network granting the requested PDU session, the response comprising an identification of a core network aggregation entity and an offload percentage; sending, via the transceiver, data to the core network aggregation entity via the non-integrated IP network based on the offload percentage; and Data is sent, via the transceiver, to the core network aggregation entity via the 3GPP network based on the offload percentage.

2. The UE according to claim 1: wherein the request to the core network for the PDU session further includes at least one proxy type supported by the UE; wherein the response from the core network granting the requested PDU session comprises at least one supported proxy type of the core network aggregation entity, the at least one supported proxy type comprising a proxy type supported by the UE; and The processor is further configured to send data to the core network aggregation entity via the non-integrated IP network based on the offload percentage using a proxy type supported by both the UE and the core network aggregation entity.

3. The UE according to claim 2, wherein the response from the core network granting the requested PDU session further includes a network address of the core network aggregation entity of each of the 3GPP network and the non-integrated IP network; and The processor is further configured to: use a proxy type supported by both the UE and the core network aggregation entity, and send data to the core network aggregation entity using a network address of the non-integrated IP network according to the offload percentage.

4. The UE according to claim 2: wherein the proxy type supported by the at least one UE comprises at least one of the following: a Multipath Transport Control Protocol (MPTCP) proxy type, a Multiplexed Application Substrate over QUIC using User Datagram Protocol (UDP) (MASQUE) proxy type, or a MASQUE proxy type using Internet Protocol (IP); and The at least one supported proxy type of the core network aggregation entity comprises at least one of the following: an MPTCP proxy type, a MASQUE proxy type using UDP, or a MASQUE proxy type using IP.

5. The UE according to claim 2: wherein the at least one supported proxy type comprises a Multipath Transmission Control Protocol (MPTCP) proxy type; and The processor is further configured to send data to the core network aggregation entity via the non-integrated IP network based on the offload percentage using the MPTCP proxy type and encryption provided by Transport Layer Security (TLS). 6 . The UE of claim 1 , wherein the offload percentage indicates a percentage of data traffic to be routed via the non-integrated IP network.

7. The UE according to claim 1: wherein the non-integrated IP network comprises a WiFi network; and The 3GPP network includes a 5G network.

8. The UE of claim 1, wherein the core network aggregation entity comprises a user plane function (UPF) device.

9. The UE according to claim 1: wherein the UE comprises at least one application configured to execute on the UE; wherein the processor configured to send the request for the PDU session to the core network is further configured to: send the request for the PDU session from the at least one application to the core network; and Wherein the processor configured to send data to the core network aggregation entity via the non-integrated IP network based on the offload percentage is further configured to send data from the at least one application to the core network aggregation entity via the non-integrated IP network based on the offload percentage.

10. The UE according to claim 1: wherein the processor is further configured to receive a UE routing policy (URSP); and The processor configured to send the request for the PDU session to the core network is further configured to: send the request for the PDU session to the core network based on the URSP.

11. The UE of claim 1 , wherein the request to the core network for the protocol data unit (PDU) session further includes an indication of: The requested uninstall percentage; Whether the UE supports a multipath transmission control protocol (MPTCP) proxy type; whether the UE supports the Multiplexed Application Substrate over QUIC (MASQUE) proxy type using User Datagram Protocol (UDP); and Whether the UE supports the MASQUE proxy type using Internet Protocol (IP).

12. The UE of claim 1 , wherein the response from the core network granting the requested PDU session further includes an indication of: Percentage of offloading granted; whether the core network aggregation entity supports a multipath transmission control protocol (MPTCP) proxy type; whether the core network aggregation entity supports the Multiplexed Application Substrate over QUIC (MASQUE) proxy type using User Datagram Protocol (UDP); and Whether the core network aggregation entity supports the MASQUE proxy type using Internet Protocol (IP).

13. The UE according to claim 12: wherein the response from the core network granting the requested PDU session further includes a network address of the core network aggregation entity of each of the 3GPP network and the non-integrated IP network; and The response from the core network granting the requested PDU session further includes: An indication of an IP address type of the network address of the core network aggregation entity of each of the 3GPP network and the non-integrated IP network.

14. The UE according to claim 1: wherein the processor is configured to: send the request for the PDU session to the core network via the 3GPP network; and The processor is configured to receive the response granting the requested PDU session from the core network via the 3GPP network.

15. The UE of claim 1, wherein the non-integrated IP network is configured not to provide a non-3GPP interworking function (N3IWF).

16. A method for wireless communication at a user equipment (UE), the method comprising: Communicates with the core network via the 3rd Generation Partnership Project (3GPP) network; sending a request for a protocol data unit (PDU) session to the core network, the request comprising a request for data aggregation across the 3GPP network and a non-integrated Internet Protocol (IP) network; receiving a response from the core network granting the requested PDU session, the response including an identification of a core network aggregation entity and an offload percentage; sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage; and Data is sent to the core network aggregation entity via the 3GPP network based on the offload percentage.

17. The method according to claim 16, wherein the request to the core network for the PDU session further includes at least one proxy type supported by the UE; wherein the response from the core network granting the requested PDU session comprises at least one supported proxy type of the core network aggregation entity, the at least one supported proxy type comprising a proxy type supported by the UE; and Wherein sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage comprises: Data is sent to the core network aggregation entity via the non-integrated IP network based on the offload percentage using a proxy type supported by both the UE and the core network aggregation entity.

18. The method according to claim 17, wherein the response from the core network granting the requested PDU session further includes a network address of the core network aggregation entity of each of the 3GPP network and the non-integrated IP network; and Wherein sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage comprises: Using a proxy type supported by both the UE and the core network aggregation entity, and according to the offload percentage, sending data to the core network aggregation entity using a network address of the non-integrated IP network.

19. The method according to claim 17: wherein the proxy type supported by the at least one UE comprises at least one of the following: a Multipath Transport Control Protocol (MPTCP) proxy type, a Multiplexed Application Substrate over QUIC using User Datagram Protocol (UDP) (MASQUE) proxy type, or a MASQUE proxy type using Internet Protocol (IP); and The at least one supported proxy type of the core network aggregation entity comprises at least one of the following: an MPTCP proxy type, a MASQUE proxy type using UDP, or a MASQUE proxy type using IP.

20. The method according to claim 17: wherein the at least one supported proxy type comprises a Multipath Transmission Control Protocol (MPTCP) proxy type; and Wherein sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage comprises: Data is sent to the core network aggregation entity via the non-integrated IP network based on the offload percentage using the MPTCP proxy type and encryption provided by Transport Layer Security (TLS).

21. The method according to claim 16: wherein the non-integrated IP network comprises a WiFi network; wherein the 3GPP network comprises a 5G network; and The core network aggregation entity includes a user plane function (UPF) device.

22. The method according to claim 16, further comprising: executing at least one application on the UE; Wherein sending the request for the PDU session to the core network comprises: sending the request for the PDU session from the at least one application to the core network; and Wherein sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage includes: sending data from the at least one application to the core network aggregation entity via the non-integrated IP network based on the offload percentage.

23. The method according to claim 16: receiving a UE routing policy (URSP); and The sending the request for the PDU session to the core network includes: The request for the PDU session is sent to the core network based on the URSP.

24. The method of claim 16, wherein the request to the core network for the protocol data unit (PDU) session further includes an indication of: The requested uninstall percentage; Whether the UE supports a multipath transmission control protocol (MPTCP) proxy type; whether the UE supports the Multiplexed Application Substrate over QUIC (MASQUE) proxy type using User Datagram Protocol (UDP); and Whether the UE supports the MASQUE proxy type using Internet Protocol (IP).

25. The method of claim 16, wherein the response from the core network granting the requested PDU session further includes an indication of: Percentage of offloading granted; whether the core network aggregation entity supports a multipath transmission control protocol (MPTCP) proxy type; whether the core network aggregation entity supports the Multiplexed Application Substrate over QUIC (MASQUE) proxy type using User Datagram Protocol (UDP); and Whether the core network aggregation entity supports the MASQUE proxy type using Internet Protocol (IP).

26. The method according to claim 25: The response from the core network granting the requested PDU session further includes: a network address of the core network aggregation entity of each of the 3GPP network and the non-integrated IP network; and An indication of an IP address type of the network address of the core network aggregation entity of each of the 3GPP network and the non-integrated IP network.

27. The method according to claim 16: The sending the request for the PDU session to the core network includes: sending the request for the PDU session to the core network via the 3GPP network; and Wherein receiving the response from the core network granting the requested PDU session comprises: receiving the response from the core network granting the requested PDU session via the 3GPP network.

28. The method of claim 16, wherein the non-integrated IP network is configured not to provide a non-3GPP interworking function (N3IWF).

29. A user equipment (UE), the user equipment (UE) comprising: Components for communicating with a core network via a 3rd Generation Partnership Project (3GPP) network; means for sending a request for a protocol data unit (PDU) session to the core network, the request comprising a request for data aggregation across the 3GPP network and a non-integrated Internet Protocol (IP) network; means for receiving a response from the core network granting the requested PDU session, the response comprising an identification of a core network aggregation entity and an offload percentage; means for sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage; as well as means for sending data to the core network aggregation entity via the 3GPP network based on the offload percentage.

30. An article for use with a user equipment (UE), the article comprising: A computer-readable medium having stored therein instructions executable by one or more processors of the UE to: Communicates with the core network via the 3rd Generation Partnership Project (3GPP) network; sending a request for a protocol data unit (PDU) session to the core network, the request comprising a request for data aggregation across the 3GPP network and a non-integrated Internet Protocol (IP) network; receiving a response from the core network granting the requested PDU session, the response including an identification of a core network aggregation entity and an offload percentage; sending data to the core network aggregation entity via the non-integrated IP network based on the offload percentage; and Data is sent to the core network aggregation entity via the 3GPP network based on the offload percentage.

Images