Multi-access networking in a wireless communication system

Abstract

Various aspects of the present disclosure relate to a user equipment (UE) for wireless communication. The UE may be configured to, capable of, or operable to receive data traffic comprising a first traffic flow; determine, from a plurality of access networks, a first access network for transmission of at least part of the first traffic flow based at least in part on a first transport requirement for the first traffic flow; and transmit at least part of the first traffic flow over the first access network.

Description

MULTI- ACCESS NETWORKING IN A WIRELESS COMMUNICATION SYSTEMTECHNICAL FIELD

[0001] The present disclosure relates generally to wireless communication, including multi-access networking.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, which may be otherwise knowns as network equipment (NE) supporting wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like)). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0003] As used herein, including in the claims, an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, including in the claims, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is Docket No. SMM920250139-GR-NPdescribed as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] A UE for wireless communication is described. The UE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the UE may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the UE to: receive data traffic comprising a first traffic flow; determine, from a plurality of access networks, a first access network for transmission of at least part of the first traffic flow based at least in part on a first transport requirement for the first traffic flow; and transmit at least part of the first traffic flow over the first access network.

[0005] A method performed or performable by the UE is described herein. The method may comprise: receiving data traffic comprising a first traffic flow; determining, from a plurality of access networks, a first access network for transmission of at least part of the first traffic flow based at least in part on a first transport requirement for the first traffic flow; and transmitting at least part of the first traffic flow over the first access network.

[0006] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: receive data traffic comprising a first traffic flow; determine, from a plurality of access networks, a first access network for transmission of at least part of the first traffic flow based at least in part on a first transport requirement for the first traffic flow; and transmit at least part of the first traffic flow over the first access network.

[0007] A network entity for wireless communication is described. The network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the Docket No. SMM920250139-GR-NPnetwork entity to: transmit, to the UE, a multi-access traffic steering rule comprising an indication to determine a first transport requirement for a first traffic flow of data traffic from an application, wherein at least part of the first traffic flow is transmitted over a first access network from a plurality of access networks based on the first transport requirement.

[0008] A method performed or performable by the network entity is described herein. The method may comprise: transmitting, to the UE, a multi-access traffic steering rule comprising an indication to determine a first transport requirement for a first traffic flow of data traffic from an application, wherein at least part of the first traffic flow is transmitted over a first access network from a plurality of access networks based on the first transport requirement.

[0009] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: transmit, to the UE, a multiaccess traffic steering rule comprising an indication to determine a first transport requirement for a first traffic flow of data traffic from an application, wherein at least part of the first traffic flow is transmitted over a first access network from a plurality of access networks based on the first transport requirement.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0011] Figure 2 illustrates an example of a first Access Traffic Steering, Switching and Splitting (ATSSS) framework in accordance with aspects of the present disclosure.

[0012] Figure 3 illustrates an example of a second ATSSS framework in accordance with aspects of the present disclosure.

[0013] Figure 4 illustrates an example of a process flow for a protocol data unit (PDU) session establishment procedure in accordance with aspects of the present disclosure.Docket No. SMM920250139-GR-NP

[0014] Figure 5 illustrates an example of a UE in accordance with aspects of the present disclosure.

[0015] Figure 6 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0016] Figure 7 illustrates an example of a NE in accordance with aspects of the present disclosure.

[0017] Figure 8 illustrates a flowchart of a method performed by a UE in accordance with aspects of the present disclosure.

[0018] Figure 9 illustrates a flowchart of a method performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0019] A wireless communications system may include one or more network communication devices (e.g., base stations, core network entities, and the like) and one or more user communication devices (e.g., UEs) supporting wireless communication via multi-access connectivity, which may include connectivity to Third-Generation Partnership Project (3GPP) (e.g., 5GNR) and non-3GPP (e.g., Wireless Fidelity (Wi-Fi)) access networks in the wireless communications system. In some cases, one or more of the network communication devices and / or one or more of the user communication devices may be enabled to perform ATSSS to support the wireless communication via the multiaccess connectivity. In some examples, one or more of the network communication devices and / or one or more of the user communication devices may route (e.g., direct) a data traffic flow over a most appropriate access network (e.g., low-latency flows over 3 GPP access network, non-low-latency flows of non-3GPP access network). In some other examples, one or more of the network communication devices and / or one or more of the user communication devices may switch an ongoing data traffic flow from one access network to another (e.g., from non-3GPP access network to 3 GPP access network if the non-3GPP access network connection quality degrades, or the like). In other examples, one or more of the network communication devices and / or one or more of the user communication devicesDocket No. SMM920250139-GR-NPmay spit a single data traffic flow across the multiple access networks simultaneously (e.g., multipath transport using both 3 GPP access network and non-3GPP access network).

[0020] While the current ATSSS framework supports steering, switching, and splitting of data traffic across multiple accesses, it remains limited in its ability to adapt to dynamic network conditions and diverse service requirements. With the continued evolution of wireless communications systems supporting 5Gand radio access technologies beyond 5G, there is a growing need for mechanisms that improve efficiency, reliability, and flexibility in handling data traffic flows and heterogeneous access networks. Examples described herein generally relate to an ATSSS framework for steering which tends to provide improved flexibility for steering traffic flows compared to previous ATSSS frameworks. Some examples described herein relate to the reception of data traffic comprising a traffic flow and determining an access network for transmitting the traffic flow based on a transport requirement.

[0021] Aspects of the present disclosure are described in the context of a wireless communications system. Aspects of the present disclosure are further set forth in the accompanying drawings and the description below. The description set forth herein, in connection with the accompanying drawings, describes example implementations and does not represent all the implementations that may be implemented or that are within the scope of the claims. The detailed description includes specific details for the purpose of providing an understanding of the described implementations. These implementations, however, may be practiced without these specific details. Additionally, the description set forth herein, in connection with the accompanying drawings is provided to enable a person having ordinary skill in the art to make or use the present disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and implementations described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

[0022] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications systemDocket No. SMM920250139-GR-NP100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LIE- A) network. In some other implementations, the wireless communications system 100 may be a New Radio (NR) network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5 G ultra wideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0023] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signalling, transmit signalling) over a Uu interface.

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

[0025] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0026] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

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

[0028] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity Docket No. SMM920250139-GR-NPthat manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

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

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

[0031] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) andDocket No. SMM920250139-GR-NPa normal cyclic prefix. In some implementations, the first numerology (e.g., / r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., / r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0032] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0033] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / r=0, jU=l , / r=2, jU=3, / r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a firstDocket No. SMM920250139-GR-NPnumerology (e.g., / r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

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

[0035] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / r=3), which includes 120 kHz subcarrier spacing.

[0036] Examples described herein relate generally to wireless communications. Some examples described herein relate to an intelligent and dynamic method for distributing data traffic across heterogeneous access networks, such as 5G, future 6G, and Wi-Fi networks.

[0037] The evolution of mobile communication systems, from 5G towards 6G, is characterized by an exponential increase in data traffic and the emergence of new, demanding applications. Services such as interactive Extended Reality (XR), cloud gaming, industrial automation, and holographic telepresence require a combination of ultra-highDocket No. SMM920250139-GR-NPthroughput, ultra-low latency, and exceptionally high reliability. To meet these stringent requirements, modern wireless systems are designed to leverage multiple access technologies simultaneously.

[0038] The 3GPP defined this capability in 5G with the introduction of the ATSSS feature, first specified in Release 16. ATSSS enables a UE to establish a Multi Access Protocol Data Unit (MA PDU) session, which allows a single data session to be served concurrently by both a 3GPP access network (e.g., 5G NR) and a non-3GPP access network (e.g., Wi-Fi).

[0039] The traffic distribution in the 5G ATSSS framework is governed by a set of network-provided policies, known as ATSSS rules in the UE and N4 multi-access policies in the UPF. These rules define how traffic for a given Service Data Flow (SDF) should be handled, specifying one of several predefined steering modes, such as: Active-Standby: Traffic is sent over a primary "active" access, with the "standby" access used only upon failure of the primary; Smallest Delay: Traffic is steered to the access path exhibiting the lowest Round Trip Time (RTT); Load-Balancing: Traffic is split between the two accesses according to a fixed percentage defined in the rule or according to a percentage defined by the UE; Priority-Based: Traffic is sent to a high-priority access until it becomes congested, at which point it may be offloaded to the lower-priority access too; or Redundant: All or part of the traffic is sent to both accesses in order to reduce the packet loss rate and, hence, increase the reliability.

[0040] While this rule-based ATSSS framework provides a foundational mechanism for multi-access operation, its static nature presents a significant bottleneck for the dynamic and complex applications envisioned for the 6G era.

[0041] A limitation of previous ATSSS frameworks relates to the static and coarsegrained approach to traffic management. An ATSSS rule, once delivered to the UE, may statically bind a traffic flow (or an entire application's traffic) to a single, predefined steering mode for the duration of the session or until the network explicitly provides an updated rule. This inflexibility tends to be detrimental for an application with highly dynamic and heterogeneous traffic patterns.Docket No. SMM920250139-GR-NP

[0042] An application (e.g., an advanced application) may not comprise a monolithic data stream. An application may comprise multiple, traffic flows. The traffic flows may be distinct from one another. Each traffic flow may comprise unique and often conflicting transport requirements.

[0043] In some examples described herein, an XR application may generate a low-data-rate, ultra-low-latency control flow for head-tracking and user inputs requiring minimal delay and jitter e.g., to prevent motion sickness. The XR application may require a very-high-throughput data flow for downloading 3D assets and streaming high-resolution video. A static "Smallest Delay" rule may optimize for the control flow but fail to provide sufficient bandwidth for the data flow. A "Load-Balancing" rule may introduce unacceptable delay or jitter to the control flow.

[0044] Some examples described herein may relate to Interactive Video Conferencing. During a conversational phase, a video conference application may be latency-sensitive. However, when a user begins sharing a high-resolution, full-motion screen, the same application may become throughput-sensitive. A single, fixed steering mode may not optimally serve both phases of the application's lifecycle.

[0045] The previous rule-based system of ATSSS frameworks cannot distinguish between different traffic flows and lacks the flexibility to adapt the steering strategy in realtime based on an application's changing context. This tends to lead to suboptimal resource utilization and a compromised Quality of Experience (QoE). This tends to prevent the full potential of multi-access connectivity from being realized.

[0046] Figure 2 illustrates an example of a first ATSSS framework 200 in accordance with aspects of the present disclosure. The first ATSSS framework 200 comprises an ATSSS Scheduler 242 receiving one or more ATSSS rules 240 and traffic of application X 250. The ATSSS Scheduler 242 is connected to a 3GPP Access Network 260 and / or a Non-3GPP Access Network 262. The ATSSS Scheduler 242 may steer the traffic of application X 250 to the 3GPP Access Network 260 and / or the Non-3GPP Access Network 262. Figure 2 illustrates traffic distribution based on the previous ATSSS framework.Docket No. SMM920250139-GR-NP

[0047] In some examples described herein, a ATSSS Rule 240 may comprise “The traffic of Application X should use the smallest delay steering mode”. The ATSSS Scheduler 242 may distribute the traffic of application X based on the steering mode defined in the ATSSS rules 240. The ATSSS Scheduler 242 may be configured to determine an access path metric or an access path condition. The access path metric or access path condition may comprise at least one of: a latency, a throughput, or a jitter of the access path (e.g., 3GPP Access Network 260, non-3GPP Access Network 262).

[0048] The traffic of application X 250 may comprise (e.g., be composed of) multiple traffic flows (e.g. control flows, video flows, etc.). The multiple traffic flows may comprise different transport requirements from one another. The traffic flows may be dynamically generated by the application during runtime and their description is not static or predefined. For example, if the protocols, port numbers or IP addresses in the packet headers of these traffic flows are dynamically selected by the application during runtime, it is not possible to describe these traffic flows in the ATSSS rules. Hence, it is not possible to apply different steering modes to the different traffic flows of application X. The ATSSS Scheduler 242 is limited as it lacks on-device intelligence and cannot adapt to the different transport requirements of the constituent traffic flows of the application traffic.

[0049] Examples described herein generally relate to the integration of on-device Artificial Intelligence (Al) into tan 3GPP ATSSS framework (e.g., first ATSSS framework 200) in a backward-compatible manner. Some examples described herein comprise a steering mode activated by a ATSSS rule. Such examples tend to enable dynamic, per-flow traffic management based on real-time application context.

[0050] Examples described herein generally relate to a method and apparatus for AI-driven, dynamic, and per-flow traffic steering within the ATSSS framework. The examples may comprise a steering mode, referred to as the "intelligent steering mode" that is backward compatible with previous 5G ATSSS architectures.

[0051] Figure 3 illustrates an example of a second ATSSS framework 300 in accordance with aspects of the present disclosure. The second ATSSS framework 300 comprises an ATSSS Scheduler 342 receiving one or more ATSSS rules 340 and traffic of application X 350. The ATSSS Scheduler 342 is connected to a 3GPP Access Network 360 Docket No. SMM920250139-GR-NPand / or a Non-3GPP Access Network 362. The one or more ATSSS rules 340 may comprise “The traffic of Application X should use the intelligent steering mode”.

[0052] The second ATSSS framework 300 further comprises a Traffic Flow Detection and Feature Extraction Block 344 which receives the traffic of application X 350. The Traffic flow detection and Feature Extraction Block 344 identifies traffic flow descriptor and features of each traffic flow (e.g., Traffic flow A 352, Traffic flow B 354 and Traffic flow C 356). The traffic flow descriptor and features of each traffic flow are directed to a Trained Al model 346. The Trained Al model 346 predicts (e.g., determines, identifies) the transport requirements of each traffic flow based of their features e.g., Traffic flow A 352 requires ultra-low latency, Traffic flowB 354 requires ultra-high reliability, and Traffic flow C 356 requires very high throughput.

[0053] The ATSSS Scheduler 342 receives the transport requirements of each traffic flow and distributes the data for each individual traffic flow based on its transport requirements. The ATSSS Scheduler 342 may steer the traffic of application X 350 to an access path e.g., 3GPP Access Network 360 and / or the Non-3GPP Access Network 362. The access path metric or access path condition may comprise at least one of: a latency, a throughput, or a jitter of the access path (e.g., 3GPP Access Network 360, non-3GPP Access Network 362).

[0054] The second ATSSS framework 300 illustrates the components and the functionality of a UE that supports Al-driven ATSSS. As defined in 5G ATSSS, the network provides to UE a list of ATSSS rules 340. In this case, an ATSSS rule 340 is provided that assigns the new "intelligent steering mode" to the traffic of a specific application (e.g., "The traffic of Application X should use the intelligent steering mode"). This ATSSS rule 340 acts as a trigger, activating an on-device Al agent, which comprises the Traffic flow detection and Feature Extraction module 344, the Trained Al Model 346 and an associated ATSSS Scheduler 342, within the UE. Once activated, the on-device Al agent performs the following functions.

[0055] Detection of Traffic Flows and their Features: The Traffic Flow Detection and Feature Extraction Block 344 intercepts the Traffic of Application X (e.g., aggregate traffic) from the target application (e.g., Application X). The Traffic Flow Detection and Docket No. SMM920250139-GR-NPFeature Extraction Block 344 identifies the individual, constituent traffic flows (e.g., Internet Protocol (IP) flows) and, instead of processing the raw data packets, it extracts a set of statistical features for each data flow. These features, which may include packet size distribution, inter-packet arrival times, and flow directionality, create a real-time "fingerprint" of each flow's behaviour. The output of the Traffic Flow Detection and Feature Extraction Block 344 comprises (a) a plurality of traffic descriptors, one for each detected traffic flow and (b) the features associated with each traffic descriptor.

[0056] Prediction of Transport Requirements: The extracted features are then fed into the Trained Al Model 346. This Trained Al Model 346 uses its training to analyze the features and predict the underlying transport requirements for each distinct traffic flow. For example, the model may predict that "Traffic flow A" requires ultra-low latency, "Traffic flow B" requires ultra-high reliability, and "Traffic flow C" requires very-high throughput.

[0057] The Trained Al Model 346 may be developed using supervised machine learning. The process begins by creating a comprehensive, labelled training dataset from a wide variety of applications with known traffic characteristics, such as XR, cloud gaming, and video conferencing. For each traffic flow, the Traffic Flow Detection and Feature Extraction Block 344 generates a statistical fingerprint. This fingerprint, which becomes the input data for the Trained Al Model 346, is a set of features including at least one of: packet size distribution, inter-packet arrival times, flow directionality (uplink / downlink ratio), or traffic burstiness. Each of these feature sets is paired with a label that represents its known transport requirement. For example, a feature set derived from an XR application's head-tracking data stream would be labelled "ultra-low latency," while a feature set from its 3D video download stream would be labelled "very-high throughput." By training on this vast dataset of (feature set, requirement label) pairs, the Trained Al Model 346 learns to accurately predict the transport requirements of new, unseen traffic flows based solely on their real-time statistical features.

[0058] Dynamic, Per-Flow Scheduling: The ATSSS Scheduler 342 receives the traffic descriptors of the detected flows (e.g., Traffic Flow A 352, Traffic Flow B 354, and Traffic Flow C 356) and their respective transport requirements from the Trained Al Model 346. Guided by the "intelligent steering mode" rule, the scheduler then distributes the data forDocket No. SMM920250139-GR-NPeach individual traffic flow across the available 3GPP Access Network 360 and / or the Non-3GPP Access Network 362. This distribution is performed dynamically and is based on matching the requirements of each traffic flow to the real-time metrics or conditions of the available network paths.

[0059] The metrics / conditions are typically obtained by making passive or active measurements on each access type and include metrics such as latency, throughput, reliability, jitter, etc. For example, if the latency measurements on both accesses indicate that the Non-3GPP Access Network 362 currently supports the smaller latency, then the ATSSS scheduler 342 sends all packets of traffic flow A 352 to the Non-3GPP Access Network 362 (since it requires ultra-low latency). Similarly, if the reliability measurements on both accesses indicate that the 3GPP Access Network 360 currently supports the highest reliability, then the ATSSS scheduler 342 sends all packets of Traffic Flow B 354 to the 3GPP Access Network 360 (since it requires ultra-high reliability). If the reliability of one access alone is not sufficient to meet the reliability requirements of Traffic Flow B 354, then the ATSSS Scheduler 342 may send every or some of the packets of Traffic Flow B 354 on both accesses.

[0060] The second ATSSS framework 300 illustrates dynamic scheduling in action for an application. For example, the ATSSS Scheduler 342 may make the following intelligent decisions: Traffic flowB 354, which requires ultra-high reliability, is steered exclusively to the 3GPP Access Network 360, which is determined to be the more stable and reliable access at that moment. Traffic flow A 352, which requires ultra-low latency, is steered exclusively to the Non-3GPP Access Network 362, which could be a high-frequency Wi-Fi access currently offering the lowest delay. Traffic flow C, which requires very-high throughput, is split across both the 3GPP Access Network 360 and Non-3GPP Access Network 362 simultaneously, allowing the UE to aggregate bandwidth and maximize data transfer speed.

[0061] The metrics / conditions of each access path are constantly evaluated (e.g. via period measurements) and their fresh values are used by the ATSSS Scheduler 342 to update its traffic steering decisions. If, for example, the 3GPP Access Network 360 is determined to have the smallest latency, then the ATSSS Scheduler 342 switches allDocket No. SMM920250139-GR-NPpackets of Traffic Flow A 352 from the Non-3GPP Access Network 362 to the 3GPP Access Network 360. This per-flow, intelligent distribution represents a significant advancement over previous ATSSS frameworks (e.g., the first ATSSS framework 200), which apply a single, static steering mode to all traffic flows of Application X.

[0062] The on-device Al model may be implemented in two ways: (a) UE-Specific Al Model: A pre-trained model pre-installed in the UE e.g., by the UE vendor; or (b) Network-Provided Al Model: A model provided by the network operator. This allows the operator to deploy, update, and customize the traffic steering logic for specific services or applications, which tends to offer greater flexibility.

[0063] The second ATSSS Framework 300 illustrates the components and functionality on the UE side, to dynamically distribute the uplink traffic. It will be understood that similar components and functionality may be implemented on the network side, e.g. in a UPF or similar element, to dynamically distribute the downlink traffic.

[0064] Figure 4 illustrates an example of a process flow 400 for a PDU session establishment procedure in accordance with aspects of the present disclosure. Process flow 400 may illustrate an enhanced PDU Session Establishment procedure.

[0065] Figure 4 illustrates an example of a process flow 400 in accordance with aspects of the present disclosure. The process flow 400 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 400 may include UE 410, RAN 415, AMF 420, Session Management Function (SMF) 425, Policy Control Function (PCF) 430 and UPF 435, which may be one or more examples of devices described herein with reference to Figure 1.

[0066] The process flow 400 may be referred to as a procedure, including one or more operations performed by one or more of the UE 410, RAN 415, AMF 420, SMF 425, PCF 430 and UPF 435.

[0067] In the following description of the process flow 400, the operations or signalling performed between one or more of the UE 410, RAN 415, AMF 420, SMF 425, PCF 430 and UPF 435 may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of Docket No. SMM920250139-GR-NPthe UE 410, RAN 415, AMF 420, SMF 425, PCF 430 and UPF 435 may be performed or signalled (e.g., transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 400. Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.

[0068] Process flow 400 enables the functionality of the second ATSSS framework 300 described above in relation to Figure 3. Process flow 400 enhances the UE-Requested MA PDU Session Establishment procedure as defined in 3GPP TS 23.502 V19.4.0. Process flow 400 relates to a 5G Network. However, it should be understood that this process flow 400 may also apply to a 6G network e.g., by replacing the 5G network functions with their equivalent 6G network functions.

[0069] Process flow 400 initiates at step 471. The UE 410 initiates the procedure to establish an MA PDU session by sending (e.g., transmitting, outputting) a PDU SESSION ESTABLISHMENT REQUEST message to the AMF 420. This message comprises an "MA-PDU request" to indicate that an MA PDU session is being requested. The UE 410 includes also a new "Intelligent Steering Supported" indicator within the ATSSS Capabilities information element of the request. This indicator signifies that the UE 410 supports ATSSS rules using the "intelligent steering mode".

[0070] In step 472, the AMF 420 receives (e.g., inputs) the request and selects (e.g., determines, identifies) an SMF 425 according to the existing procedures.

[0071] In step 473a, the AMF 420 forwards (e.g., sends, transmits, outputs) the PDU SESSION ESTABLISHMENT REQUEST message to the selected SMF 425, including the UE's ATSSS Capabilities and the "Intelligent Steering Supported" indication. The AMF 420 also informs the SMF 425 whether the UE is currently registered over both 3 GPP and non-3GPP accesses, e.g., as specified in TS 23.502 V19.4.0.

[0072] In step 473b, the SMF 425 sends (e.g., transmits, outputs) a create Session Management (SM) context response message to the AMF 420.

[0073] In step 474, the SMF 425 requests from the (PCF 430 to retrieve policies for the multi-access session by sending (e.g., transmitting, outputting) to the PCF 430 an SM Docket No. SMM920250139-GR-NPPolicy Control Create Request comprising an indication of the MA-PDU Request and the “Intelligent Steering Supported” indication.

[0074] In step 475, the PCF 430, based on user's subscription, operator policies and the received UE capabilities, provides (e.g., sends, transmits, outputs) PCC rules to the SMF 425 for the requested MA-PDU session. The PCC rules comprise multi-access information that indicate how uplink and downlink traffic on the MA-PDU session may be distributed across the available accesses. For an application designated for Al-driven steering, the PCF 430 provides (e.g., sends, transmits, outputs) a PCC rule with multi-access information indicating that the "intelligent steering mode" should be utilized.

[0075] In step 476, the SMF 425 processes the PCC rules and derives (e.g., determines, identifies, maps) the corresponding ATSSS rules for the UE 410 and the corresponding multi-access N4 rules for the UPF 435. From a PCC rule with multi-access information indicating that the "intelligent steering mode" should be utilized, the SMF 425 creates (e.g., determines, identifies, maps) a corresponding an ATSSS rule and a corresponding multiaccess N4 rule where the Steering Mode parameter is set to "intelligent steering mode."

[0076] In step 477a, the SMF 425 selects (e.g., determines, identifies) a UPF 435 that may support intelligent steering.

[0077] In step 477b, the SMF 425 sends (e.g., transmits, outputs) an N4 Session Request message to the UPF 435 including the derived multi -access N4 rules, which comprises one or more rules with the Steering Mode parameter set to "intelligent steering mode."

[0078] In step 477c, the UPF 435 sets up (e.g., determines, identifies, establishes) the necessary resources for the requested session and responds (e.g., sends, transmits, outputs) with an N4 Session Response message to the SMF 425.

[0079] In steps 478a and 478b, the SMF 425 sends (e.g., transmits, outputs) the PDU SESSION ESTABLISHMENT ACCEPT message to the UE 410 via the AMF 420. This message comprises the created ATSSS rules with an indication that the steering mode is the intelligent steering mode. If the network operator's policy dictates that a specific Al model should be used, the SMF 425 includes a Uniform Resource Locator (URL) within the PDU Docket No. SMM920250139-GR-NPSESSION ESTABLISHMENT ACCEPT message. This URL may point to a secure server from which the Al model may be downloaded. The URL may be included within a Protocol Configuration Options (PCO) information element or within a new information element.

[0080] In step 479, the UE 410 receives (e.g., inputs) the PDU SESSION ESTABLISHMENT ACCEPT message and parses the ATSSS rules provided. Upon detecting an ATSSS rule with the Steering Mode parameter set to "intelligent steering mode," the UE 410 performs the following actions: the UE 410 activates its on-device Al agent (e.g., Al Model and ATSSS Scheduler) for the application specified in the rule's traffic descriptor. If a URL is present (e.g. in the PCO), the UE 410 securely downloads the Al model from the specified location, verifies its integrity, and loads it for use by the Al agent. If the UE 410 has previously downloaded the same Al model, the download process may be skipped.

[0081] In steps 480a and 480b, the user plane resources for the MA PDU session are established over the 3GPP and / or non-3GPP access as per standard procedures. Once established, the UE 410 begins applying the intelligent, per-flow steering logic to the application's traffic. Other traffic on the PDU session (e.g., traffic not assigned to the "intelligent steering mode") may be handled by conventional ATSSS rules and procedures. Similar behaviour may be applied at the UPF 435 for downlink traffic.

[0082] Figure 5 illustrates an example of a UE 500 in accordance with aspects of the present disclosure. The UE 500 may include a processor 502, a memory 504, a controller 506, and a transceiver 508. The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0083] The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or anyDocket No. SMM920250139-GR-NPcombination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

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

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

[0086] In some implementations, the processor 502 and the memory 504 coupled with the processor 502 may be configured to cause the UE 500 to perform one or more of the functions described herein (e.g., executing, by the processor 502, instructions stored in the memory 504). For example, the processor 502 may support wireless communication at the UE 500 in accordance with examples as disclosed herein. The UE 500 may be configured to support a means for receiving data traffic comprising a first traffic flow; determining, from a plurality of access networks, a first access network for transmission of at least part of the first traffic flow based at least in part on a first transport requirement for the first traffic flow; and transmitting at least part of the first traffic flow over the first access network.

[0087] The controller 506 may manage input and output signals for the UE 500. The controller 506 may also manage peripherals not integrated into the UE 500. In some implementations, the controller 506 may utilize an operating system such as iOS®, Docket No. SMM920250139-GR-NPANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 506 may be implemented as part of the processor 502.

[0088] In some implementations, the UE 500 may include at least one transceiver 508. In some other implementations, the UE 500 may have more than one transceiver 508. The transceiver 508 may represent a wireless transceiver. The transceiver 508 may include one or more receiver chains 510, one or more transmitter chains 512, or a combination thereof.

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

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

[0091] Figure 6 illustrates an example of a processor 600 in accordance with aspects of the present disclosure. The processor 600 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 600 may include a controller 602 configured to perform various operations in accordance with examples as described herein. The processor 600 may optionally include at least one Docket No. SMM920250139-GR-NPmemory 604, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 600 may optionally include one or more arithmetic-logic units (ALUs) 606. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0092] The processor 600 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 600) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0093] The controller 602 may be configured to manage and coordinate various operations (e.g., signalling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein. For example, the controller 602 may operate as a control unit of the processor 600, generating control signals that manage the operation of various components of the processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0094] The controller 602 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 604 and determine subsequent instruction(s) to be executed to cause the processor 600 to support various operations in accordance with examples as described herein. The controller 602 may be configured to track memory address of instructions associated with the memory 604. The controller 602 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 602 may be configured to interpret the instruction andDocket No. SMM920250139-GR-NPdetermine control signals to be output to other components of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 602 may be configured to manage flow of data within the processor 600. The controller 602 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 600.

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

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

[0097] The one or more ALUs 606 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 606 may reside within or on a processor chipset (e.g., the processor 600). In some other implementations, the one or more ALUs 606 may reside external to the processor chipset (e.g., the processor 600). One or more ALUs 606 may perform one or moreDocket No. SMM920250139-GR-NPcomputations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 606 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 606 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 606 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 606 to handle conditional operations, comparisons, and bitwise operations.

[0098] The processor 600 may support wireless communication in accordance with examples as disclosed herein. The processor 600 may be configured to support a means for receiving data traffic comprising a first traffic flow; determining, from a plurality of access networks, a first access network for transmission of at least part of the first traffic flow based at least in part on a first transport requirement for the first traffic flow; and transmitting at least part of the first traffic flow over the first access network. The processor 600 may be configured to or operable to support a means for transmitting, to the UE, a multi-access traffic steering rule comprising an indication to determine a first transport requirement for a first traffic flow of data traffic from an application, wherein at least part of the first traffic flow is transmitted over a first access network from a plurality of access networks based on the first transport requirement.

[0099] Figure 7 illustrates an example of a NE 700 in accordance with aspects of the present disclosure. The NE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0100] The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or anyDocket No. SMM920250139-GR-NPcombination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

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

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

[0103] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the NE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the NE 700 in accordance with examples as disclosed herein. The NE 700 may be configured to support a means for transmitting, to the UE, a multi-access traffic steering rule comprising an indication to determine a first transport requirement for a first traffic flow of data traffic from an application, wherein at least part of the first traffic flow is transmitted over a first access network from a plurality of access networks based on the first transport requirement.

[0104] The controller 706 may manage input and output signals for the NE 700. The controller 706 may also manage peripherals not integrated into the NE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, Docket No. SMM920250139-GR-NPANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.

[0105] In some implementations, the NE 700 may include at least one transceiver 708. In some other implementations, the NE 700 may have more than one transceiver 708. The transceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.

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

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

[0108] Figure 8 illustrates a flowchart of a method 800 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.Docket No. SMM920250139-GR-NP

[0109] At 802, the method 800 may include receiving data traffic comprising a first traffic. The operations of 802 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 802 may be performed by a UE as described with reference to Figure 5.

[0110] At 804, the method 800 may include determining, from a plurality of access networks, a first access network for transmission of at least part of the first traffic flow based at least in part on a first transport requirement for the first traffic flow. The operations of 804 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 804 may be performed by a UE as described with reference to Figure 5.

[0111] At 806, the method 800 may include Transmitting at least part of the first traffic flow over the first access network. The operations of 806 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 806 may be performed a UE as described with reference to Figure 5.

[0112] It should be noted that the method 800 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0113] Figure 9 illustrates a flowchart of a method 900 in accordance with aspects of the present disclosure. The operations of the method 900 may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0114] At 902, the method 900 may include transmitting, to the UE, a multi-access traffic steering rule comprising an indication to determine a first transport requirement for a first traffic flow of data traffic from an application, wherein at least part of the first traffic flow is transmitted over a first access network from a plurality of access networks based on the first transport requirement. The operations of 902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 902 may be performed by a NE as described with reference to Figure 7.Docket No. SMM920250139-GR-NP

[0115] It should be noted that the method 900 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0116] There is provided herein a UE for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive data traffic comprising a first traffic flow; determine, from a plurality of access networks, a first access network for transmission of at least part of the first traffic flow based at least in part on a first transport requirement for the first traffic flow; and transmit at least part of the first traffic flow over the first access network. Such a UE tends to improve flexibility of the UE to steer the first traffic flow according to the first transport requirement.

[0117] The data traffic may comprise application traffic. The first traffic flow may comprise a first data flow. The first transport requirement may comprise a requirement for at least one of: a latency for the first traffic flow; a reliability for the first traffic flow; or a throughput for the first traffic flow.

[0118] The first access network may be part of an MA PDU. The plurality of access network may be part of MA PDU. Determining the first transport requirement for the first traffic flow may be part of an intelligent steering mode. The data traffic may further comprise a second traffic flow. The second traffic flow may comprise a second data flow. The at least one processor may be further configured to cause the UE to: determine a second transport requirement for the second traffic flow.

[0119] The second transport requirement may comprise a requirement for at least one of: a latency for the second traffic flow; a reliability for the second traffic flow; or a throughput for the second traffic flow. The at least one processor may be further configured to cause the UE to: determine, from the plurality of access networks, a second access network for transmitting at least part of the second traffic flow based on the second transport requirement. The second access network may be the same as the first access network. The second access network may be different to the first access network.Docket No. SMM920250139-GR-NP

[0120] The at least one processor may be further configured to cause the UE to: transmit at least part of the second traffic flow over the second access network. The at least one processor may be further configured to cause the UE to: transmit, to a network entity, a request to establish a MA PDU via the plurality of access networks. The network entity may comprise an SME Transmitting, to the network entity, the request to establish the MA PDU via the plurality of access networks may comprise transmitting, to the network entity via an AMF, the request to establish the MA PDU via the plurality of access networks.

[0121] The at least one processor may be further configured to cause the UE to: receive, from the network entity, a multi-access traffic steering rule comprising an indication to determine the first transport requirement for the first traffic flow. The multiaccess traffic steering rule may comprise an ATSSS rule. The multi-access traffic steering rule may comprise an intelligent steering mode. The multi-access traffic steering rule may further comprise an indication to determine the second transport requirement for the second traffic flow. The multi-access traffic steering rule may comprise an indication to determine transport requirements of traffic flows in the data traffic. The indication to determine transport requirements of traffic flows in the data traffic may comprise an indication for an intelligent steering mode.

[0122] To determine the first transport requirement for the first traffic flow, the at least one processor may be further configured to cause the UE to: determine the first transport requirement for the first traffic flow using a model. The model may be an Al model. The at least one processor may be further configured to cause the UE to: receive the model from the network entity. The model may be pre-installed on the UE. The at least one processor may be further configured to cause the UE to: receive a URL for retrieving the model.

[0123] The at least one processor may be further configured to cause the UE to: transmit the first traffic flow over the first access network and a second access network in response to the first transport requirement. The at least one processor may be further configured to cause the UE to: transmit the first traffic flow over the first access network and the second access network may be in response to the first transport requirement comprising a high throughput requirement.Docket No. SMM920250139-GR-NP

[0124] The first access network may comprise a 3 GPP access network or a non-3GPP access network. The 3GPP access network may comprise at least one of: a 5GNG-RAN or a 6G access network. The non-3GPP access network may comprise a Wi-Fi access network. The second access network may comprise a 3 GPP access network or a non-3GPP access network.

[0125] There is further provided herein a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive data traffic comprising a first traffic flow; determine, from a plurality of access networks, a first access network for transmission of at least part of the first traffic flow based at least in part on a first transport requirement for the first traffic flow; and transmit at least part of the first traffic flow over the first access network. Such a processor tends to improve flexibility of the UE to steer the first traffic flow according to the first transport requirement.

[0126] There is further provided herein a method performed or performable by a UE the method comprising: receiving data traffic comprising a first traffic flow; determining, from a plurality of access networks, a first access network for transmission of at least part of the first traffic flow based at least in part on a first transport requirement for the first traffic flow; and transmitting at least part of the first traffic flow over the first access network. Such a method performed or performable by the UE tends to improve flexibility of the UE to steer the first traffic flow according to the first transport requirement.

[0127] The data traffic may further comprise a second traffic flow. The method may further comprise determining a second transport requirement for the second traffic flow. The method may further comprise determining, from the plurality of access networks, a second access network for transmitting at least part of the second traffic flow based on the second transport requirement.

[0128] The method may further comprise transmitting at least part of the second traffic flow over the second access network. The method may further comprise transmitting, to a network entity, a request to establish a MA PDU via the plurality of access networks. The method may further comprise receiving, from the network entity, a multi-access traffic steering rule comprising an indication to determine the first transport requirement for the Docket No. SMM920250139-GR-NPfirst traffic flow. The indication to determine the first transport requirement for the first traffic flow may comprise a trigger (e.g., command) instructing the UE to determine the first transport requirement for the first traffic flow. The multi-access traffic steering rule may comprise a requirement for the first transport requirement. To determine the first transport requirement for the first traffic flow, the method may further comprise determining the first transport requirement for the first traffic flow using a model. The method may further comprise transmitting the first traffic flow over the first access network and a second access network in response to the first transport requirement. The first access network may comprise a 3 GPP access network or a non-3GPP access network.

[0129] There is further provided herein a method preformed or performable by a network entity, the method comprising: transmitting, to the UE, a multi-access traffic steering rule comprising an indication to determine a first transport requirement for a first traffic flow of data traffic from an application, wherein at least part of the first traffic flow is transmitted over a first access network from a plurality of access networks based on the first transport requirement. Such a method performed or performable by the network entity tends to improve flexibility of the UE to steer the first traffic flow according to the first transport requirement.

[0130] The data traffic may further comprise a second traffic flow. The multi-access traffic steering rule may further comprise an indication to determine the second transport requirement for the second traffic flow. At least part of the second traffic flow may be transmitted over the second access network based on the second transport requirement. The method may further comprise receiving, from the UE, a request to establish an MA PDU via the plurality of access networks. The first access network may comprise a 3GPP access network or a non-3GPP access network.

[0131] Some examples described herein generally relate to an "Intelligent Steering Mode". The intelligent steering mode within the 3 GPP ATSSS framework acts as a trigger for on-device Al, enabling advanced, dynamic traffic management while maintaining full backward compatibility with the existing rule-based architecture.

[0132] Some examples described herein generally relate to an On-Device Al for PerFlow Classification. This relates to the use of an on-device Al model to perform real-time Docket No. SMM920250139-GR-NPinspection and classification of an application's constituent traffic flows based on their distinct and dynamic transport requirements (e.g., latency, reliability, throughput).

[0133] Some examples described herein generally relate to a Dynamic, Per-Flow ATSSS Scheduler. This relates to the implementation of a dynamic ATSSS scheduler in the UE that applies different and optimal steering strategies (e.g., smallest delay, load balancing, redundant transmission) to different flows within the same application based on the Al model's real-time classification and current access path conditions.

[0134] Some examples described herein generally relate to Enhanced Signaling for Al Model Provisioning. This relates to the use of the PDU Session Establishment procedure, including a new UE capability indication for the intelligent steering mode and a mechanism for the network to securely provide a downloadable Al model to the UE via a URL (e.g., in the PCO).

[0135] There is further provided herein a method performed by a UE for managing traffic over multiple access networks, the method comprising: transmitting, to a network, a request to establish a multi -access PDU session; receiving, from the network, an ATSSS rule that assigns an "intelligent steering mode" to traffic associated with an application; in response to receiving said ATSSS rule, activating an Al model on the UE; inspecting, using the Al model, the traffic of the application to identify a plurality of distinct traffic flows within said traffic; classifying, using the Al model, each of the plurality of distinct traffic flows based on their respective transport requirements; and applying (e.g., by an ATSSS scheduler on the UE) a distinct steering strategy to each of the classified traffic flows for distribution across the multiple access networks, wherein the distinct steering strategy for each traffic flow is selected based on its classified transport requirement and real-time conditions of the multiple access networks.

[0136] The transport requirements may comprise at least one of: a latency requirement, a reliability requirement, or a throughput requirement. 3) The distinct steering strategies may comprise at least one of: sending a traffic flow over a single access network selected for having the smallest delay, splitting a traffic flow across at least two access networks, or sending a traffic flow redundantly over at least two access networks. The method may further comprise, prior to receiving the ATSSS rule, transmitting a capability indication to Docket No. SMM920250139-GR-NPthe network within the request to establish the multi-access PDU session, the capability indication indicating that the UE supports the intelligent steering mode.

[0137] The Al model may be a UE-specific model pre-installed / pre-configured on the UE. 6) The method may further comprise receiving, from the network during the establishment of the multi-access PDU session, a URL; and downloading the Al model from the received URL. The URL may be received within the PDU Session Establishment Accept message (e.g., within the PCO information element or within a new information element).

[0138] There is further provided herein a method performed by a network node for managing traffic for a UE, the method comprising: receiving, from the UE, a request to establish a multi-access PDU session; determining that the UE is capable of supporting an intelligent steering mode; generating an ATSSS rule that assigns the intelligent steering mode to traffic of a specific application; and transmitting the ATSSS rule to the UE to cause the UE to activate an on-device Al model for classifying and dynamically steering distinct traffic flows of the specific application.

[0139] The method may further comprise determining that the UE is capable of supporting the intelligent steering mode is based on a capability indication received from the UE in the request to establish the multi-access PDU session. The method may further comprise including a URL for an Al model in a PDU Session Establishment Accept message transmitted to the UE, wherein the URL enables the UE to download the Al model for use with the intelligent steering mode. The network node may comprise an SME

[0140] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0141] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, theDocket No. SMM920250139-GR-NPdisclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein. Docket No. SMM920250139-GR-NP

Claims

CLAIMSWhat is claimed is:

1. A user equipment, UE, for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the UE to:receive data traffic comprising a first traffic flow;determine, from a plurality of access networks, a first access network for transmission of at least part of the first traffic flow based at least in part on a first transport requirement for the first traffic flow; andtransmit at least part of the first traffic flow over the first access network.

2. The UE of claim 1, wherein the data traffic further comprises a second traffic flow.

3. The UE of claim 2, wherein the at least one processor is further configured to cause the UE to:determine, from the plurality of access networks, a second access network for transmission of at least part of the second traffic flow based at least in part on a second transport requirement for the second traffic flow; andtransmit at least part of the second traffic flow over the second access network.

4. The UE of any one of claims 1 to 3, wherein the at least one processor is further configured to cause the UE to:transmit, to a network entity, a request to establish a multi-access protocol data unit, MA PDU, session for the plurality of access networks.

5. The UE of claim 4, wherein the at least one processor is further configured to cause the UE to:receive, from the network entity, a multi-access traffic steering rule comprising an indication to determine the first transport requirement for the first traffic flow.Docket No. SMM920250139-GR-NP6. The UE of any one of claims 1 to 5, wherein the at least one processor is further configured to cause the UE to:determine the first transport requirement for the first traffic flow.

7. The UE of claim 6, wherein to determine the first transport requirement for the first traffic flow, the at least one processor is further configured to cause the UE to:determine the first transport requirement for the first traffic flow using an artificial intelligence model.

8. The UE of any one of claims 1 to 7, wherein the at least one processor is further configured to cause the UE to:transmit the first traffic flow over the first access network and a second access network based at least in part on the first transport requirement.

9. The UE of any one of claims 1 to 8, wherein the first access network is different than a second access network, and wherein one or more of the first access network and the second access network comprise a 3 GPP access network or a non-3GPP access network.

10. A processor for wireless communication, comprising:at least one controller coupled with at least one memory and configured to cause the processor to:receive data traffic comprising a first traffic flow;determine, from a plurality of access networks, a first access network for transmission of at least part of the first traffic flow based at least in part on a first transport requirement for the first traffic flow; andtransmit at least part of the first traffic flow over the first access network.

11. A method performed or performable by a user equipment, UE, the method comprising:receiving data traffic comprising a first traffic flow;Docket No. SMM920250139-GR-NPdetermining, from a plurality of access networks, a first access network for transmission of at least part of the first traffic flow based at least in part on a first transport requirement for the first traffic flow; andtransmitting at least part of the first traffic flow over the first access network.

12. The method of claim 11, wherein the data traffic further comprises a second traffic flow.

13. The method of claim 12, further comprising:determining, from the plurality of access networks, a second access network for transmission of at least part of the second traffic flow based at least in part on a second transport requirement for the second traffic flow; andtransmitting at least part of the second traffic flow over the second access network.

14. The method of any one of claims 11 to 13, further comprising:transmitting, to a network entity, a request to establish a multi-access protocol data unit, MA PDU, session for the plurality of access networks.

15. The method of claim 14, further comprising:receiving, from the network entity, a multi-access traffic steering rule comprising an indication to determine the first transport requirement for the first traffic flow.Docket No. SMM920250139-GR-NP

Images