Multi-steering operations for wireless communications

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may obtain, via a higher layer of the UE, a first set of UE route selection policy (URSP) rules from a first protocol stack of the UE. The higher layer may include a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or a second protocol stack of the UE. The UE may process, via the higher layer of the UE, the data traffic associated with the UE via one or both of the first protocol stack or the second protocol stack of the UE based on the first set of URSP rules and traffic information associated with the data traffic.

Description

MULTI-STEERING OPERATIONS FOR WIRELESS COMMUNICATIONSCROSS REFERENCE

[0001] The present Application for Patent claims the benefit of Greece Patent Application No. 20240100021 by GR1OT et al., entitled “MULTI-STEERING OPERATIONS FOR WIRELESS COMMUNICATIONS,” filed January 1 1, 2024, assigned to the assignee hereof, and expressly incorporated by reference herein.FIELD OF TECHNOLOGY

[0002] The following relates to wireless communication, including multi-steering operations for wireless communications.BACKGROUND

[0003] Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g.. time, frequency, and power). Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE).SUMMARY

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support multi-steering operations for wireless communications. For example, the described techniques provide for a higher layer (also referred to as "‘dualsteer layer”) of a UE, where the higher layer may be distinct from protocol stacks of theUE and manages data traffic for the protocol stacks and over one or multiple access networks. For example, the higher layer may be configured with functionality to manage (e.g.. steer, switch, or aggregate) data traffic for the protocol stacks and over the one or multiple access networks based on UE route selection policies (URSP) rules. Additionally, the UE may be configured to activate (or deactivate) wireless communication over one or multiple protocol stacks based on URSP rules obtained via the higher layer of the UE from the one or multiple access networks.BRIEF DESCRIPTION OF THE DRAWINGS

[0005] FIGs. 1 and 2 show examples of wireless communications systems that support multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure.

[0006] FIGs. 3 through 5 show block diagrams of UEs that support multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure.

[0007] FIGs. 6 and 7 show examples of process flows that support multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure.

[0008] FIGs. 8 and 9 show block diagrams of devices that support multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure.

[0009] FIG. 10 shows a block diagram of a communications manager that supports multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure.

[0010] FIG. 11 shows a diagram of a system including a device that supports multisteering operations for wireless communications in accordance with one or more aspects of the present disclosure.

[0011] FIGs. 12 and 13 show block diagrams of devices that support multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure.

[0012] FIG. 14 shows a block diagram of a communications manager that supports multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure.

[0013] FIG. 15 shows a diagram of a system including a device that supports multisteering operations for wireless communications in accordance with one or more aspects of the present disclosure.

[0014] FIGs. 16 through 20 show flowcharts illustrating methods that support multisteering operations for wireless communications in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION

[0015] Various aspects of the present disclosure relate to a wireless communication device, such as a UE, that may be configured with multiple protocol stacks to support one or multiple wireless services over one or multiple access networks. Particularly, the present disclosure relate relates to a higher layer (also referred to as “dual-steer layer’) that is distinct from the protocol stacks and manages data traffic for the protocol stacks and over the one or multiple access networks. For example, the higher layer may be configured with functionality to manage (e.g., steer, switch, or aggregate) data traffic for the protocol stacks and over the one or multiple access networks based on UE route selection policies (URSP) rules. Additionally, the UE may be configured to activate (or deactivate) wireless communication over one or multiple protocol stacks based on URSP rules obtained via the higher layer of the UE from the one or multiple access networks.

[0016] The UE may be configured to associate a session, such as a protocol data unit (PDU) session, with one or multiple protocol stacks of the UE based on the URSP rules and traffic information associated with the data traffic (e.g., of an application enabled for the UE). For example, the UE may determine to establish (e.g., via a PDU session establishment procedure) a PDU session associated with a single protocol stack or multiple protocol stacks of the UE. The UE may determine the t pe of PDU session to establish based on the application enabled for the UE. Additionally, the UE may be enabled to consolidate (e.g., aggregate) URSP rules received from multiple protocolstacks and apply a priority to each URSP rule in the consolidated URSP rules for managing data traffic over the one or multiple access networks as described herein.

[0017] By enabling the UE with a higher layer (“dual-steer layer”) that is distinct from the protocol stacks and manages data traffic for the protocol stacks and over the one or multiple access networks, the UE may experience improved communication reliability, reduced latency, improved user experience related to reduced processing, and more efficient utilization of communication resources.

[0018] Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to multi-steering operations for wireless communications.

[0019] FIG. 1 shows an example of a wireless communications system 100 that supports multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 105, one or more UEs 115. and a core network 130. In some examples, the wireless communications system 100 may be a LTE network, an LTE-A network, an LTE-A Pro network, an NR network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0020] The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 1 15 may wirelessly communicate via one or more communication links 125 (e.g., a radio frequency (RF) access link). For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which a network entity’ 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs).

[0021] The UEs 1 15 may be dispersed throughout a coverage area 1 10 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various t pes of devices, such as other UEs 115 or network entities 105, as shown in FIG. 1.

[0022] As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g.. any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network ent i ty 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 1 15, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 1 15, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

[0023] In some examples, network entities 105 may communicate with the core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., in accordance with an SI, N2, N3, or other interface protocol). In some examples, network entities 105 may communicate with one another via a backhaul communication link 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via a core network 130). In some examples, network entities 105 may communicatewith one another via a midhaul communication link 162 (e g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol), or any combination thereof. The backhaul communication links 120, midhaul communication links 162. or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link), one or more wireless links (e.g., a radio link, a wireless optical link), among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.

[0024] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, aNodeB, an eNodeB (eNB), a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB). a Home NodeB, a Home eNodeB. or other suitable terminology). In some examples, a network entity 105 (e.g.. a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0025] In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165. a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or morecomponents of the network entities 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU). a virtual DU (VDU), a virtual RU (VRU)).

[0026] The split of functionality between a CU 160. a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), service data adaption protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (LI) (e.g., physical (PHY) layer) or L2 (e g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 1 5 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or more RUs 170). In some cases, a functional split between a CU 160 and a DU 165, or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165. or the RU 170). A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to one or more DUs 165 via a midhaul communication link 162 (e.g., Fl, Fl-c, Fl-u), and a DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may beimplemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that are in communication via such communication links.

[0027] In wireless communications systems (e.g., wireless communications system 100). infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as a donor entity or an IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). The one or more donor network entities 105 (e.g., IAB donors) may be in communication with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). IAB nodes 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs 165 of a coupled IAB donor. An IAB-MT may include an independent set of antennas for relay of communications with UEs 115, or may share the same antennas (e.g., of an RU 170) of an IAB node 104 used for access via the DU 165 of the IAB node 104 (e.g., referred to as virtual IAB-MT (vIAB-MT)). In some examples, the IAB nodes 104 may include DUs 165 that support communication links with additional entities (e.g., IAB nodes 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream). In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of IAB nodes 104) may be configured to operate according to the techniques described herein.

[0028] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support multi-steering operations for wireless communications as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of thedisaggregated RAN architecture (e.g., TAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 180).

[0029] A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the "device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (loT) device, an Internet of Everything (loE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.

[0030] The UEs 115 described herein may be able to communicate with various ty pes of devices, such as other UEs 115 that may sometimes act as relays as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as show n in FIG. 1.

[0031] The UEs 115 and the network entities 105 may wirelessly communicate with one another via one or more communication links 125 (e.g.. an access link) using resources associated with one or more carriers. The term ‘'carrier’’ may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication links 125. For example, a carrier used for a communication link 125 may include a portion of a RF spectrum band (e g., a bandwidth part (BWP)) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD)component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, subentity) of a network entity 105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0032] Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam), and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.

[0033] The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts= l / fmax■seconds, for which fnaxmay represent a supported subcarrier spacing, and Nfmay represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0034] Each frame may include multiple consecutively -numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a framemay be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

[0035] A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a quantity’ of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0036] Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control informationto multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.

[0037] A network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or others). In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.

[0038] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a lower-powered network entity 105 (e.g., a lower-powered base station 140). as compared with a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g.. the UEs 115 in a closed subscriber group (CSG), the UEs 115 associated with users in a home or office). A network entity 105 may support one or multiple cells and may also support communications via the one or more cells using one or multiple component carriers.

[0039] In some examples, a network entity 105 (e g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, the overlapping coverage areas 110 associated with different technologies may be supported by different network entities105. The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0040] The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC). The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of sendees, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0041] In some examples, a UE 115 may be configured to support communicating directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., in accordance with a peer-to-peer (P2P). D2D, or sidelink protocol). In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity7105 (e.g., a base station 140, an RU 170), which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to-many (1:M) system in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, a network entity 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network entity7105.

[0042] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobilityfunctions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one 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)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g.. base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP sendees 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet(s). an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

[0043] The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency7(VHF) portion of the spectrum below 300 MHz.

[0044] The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology7, or NR technology7using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carriersensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0045] A network entity 105 (e g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity', multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity’ 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

[0046] The network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO). for which multiple spatial layers are transmitted to the same receivingdevice, and multiple-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

[0047] Beamforming, which may also be referred to as spatial fdtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

[0048] In the wireless communications system 100, a UE 115 may support managing (e.g., one or more of steering, switching, or aggregating) data traffic over different access networks (also referred to as radio access networks), such as one or more base stations 140, each of which may communicate (e.g., one or more of receive, obtain, transmit, or output) one or more of control information or data to a core network 130. In the case of non-simultaneous wireless communication over the access networks, the UE 115 may be configured to perform (e.g., one or more of receive, obtain, transmit, or output) wireless communication (e.g., data traffic) over each access network separately. Alternatively, in the case of simultaneous wireless communication over the access networks, the UE 115 may be configured to perform (e.g., one or more of receive, obtain, transmit, or output) the wireless communication over one or multiple access networks.

[0049] A UE 115 may be configured with multiple protocol stacks to support one or multiple wireless services over one or multiple access networks, such as one or multiple network entities 105 or base stations 140. A protocol stack may refer to one or moreprotocol layers, which may be ordered in a hierarchical architecture (e.g., structure). In some examples, the UE 115 may be equipped (e.g., configured, provided, installed) with anew higher layer that is distinct from the protocol stacks and manages (e.g.. processes) data traffic for the protocol stacks and over the one or multiple access networks. For example, the new higher layer may be configured with functionality to manage (e.g., one or more of steer, switch, or aggregate) data traffic for the protocol stacks for communicating (e.g., receiving, transmitting, routing, forwarding) over the one or multiple access networks as described herein.

[0050] A protocol stack may include one or more of a first layer (also referred to as Layer 1), a second layer (also referred to as Layer 2), or a third layer (also referred to as Layer 3). Layer 1 may include a physical (PHY) layer, which may perform transmission and reception of data over a channel (e.g., one or more of an uplink control channel, an uplink data channel, a downlink control channel, or a downlink data channel). Layer 2 may include one or more of a medium access control (MAC) layer, a radio link control (RLC) layer, or a packet data convergence protocol (PDCP) layer. The MAC layer may manage access to the channel, perform multiplexing or demultiplexing of data, manage a hybrid automatic repeat request (HARQ) process for the reliability of communicating (e.g., transmitting, receiving, routing, forwarding) data, among other examples. The RLC layer may perform segmentation, reassembly, error correction, and retransmission of data. The PDCP layer may manage compression and encryption of data.Additionally, the PDCP layer may manage integrity protection of data, ensuring that the data is provided (e.g., transmitted, delivered) without being corrupted. Layer 3 may include a radio resource control (RRC) layer, which may manage routing of data, among other examples.

[0051] FIG. 2 show s an example of a wireless communications system 200 that supports multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure. In some examples, the wireless communications system 200 may implement or be implemented by aspects of the wireless communications system 100 as described herein with reference to FIG. 1. For example, the wireless communications system 200 may include a UE 115-a, a base station 140-a, and a base station 140-b, which may be an example of UEs 115 and base stations 140 as described herein with reference to FIG. 1. The wireless communicationssystem 200 may support multiple radio access technologies including 4G LTE, 5G NR, or a combination thereof. For example, one or more of the base station 140-a or the base station 140-b may support one or more of 4G LTE or 5G NR. It should be noted that the wireless communications system 200 may support radio access technologies beyond 5G NR.

[0052] The UE 115-a and the base station 140-a may perform wireless communication (e.g., one or more of receiving, obtaining, transmitting, or outputting one or more of control information or data) via a communication link 125-a, which may be examples of communications links 125 as described herein with reference to FIG. 1. Additionally, or alternatively, the UE 115-a and the base station 140-b may perform wireless communication (e.g., one or more of receiving, obtaining, transmitting, or outputting one or more of control information or data) via a communication link 125-b, which may be examples of communications links 125 as described herein with reference to FIG. 1.

[0053] The UE 115-a may support processing (e.g., one or more of steering, switching, or aggregating) data traffic for different wireless services over different access networks, such as one or more of the base station 140-a or the base station 140-b, each of which may communicate (e.g., one or more of receive, obtain, transmit, or output) one or more of control information or data to a core network 130-a. which may be examples of a core network 130 as described herein with reference to FIG. 1, to support the wireless sendees (e.g., applications enabled for the UE 115-a). For example, the UE 115-a may be enabled or configured to one or more of steer, switch, or aggregate data traffic for a wireless service over one or more access networks, such as one or more of the base station 140-a or the base station 140-b.

[0054] The one or more access networks may provide connectivity to the UE 115-a with the core network 130-a to provide access to the wireless service (e.g., one or more applications enabled for the UE 115-a). The one or more access networks, such as one or more of the base station 140-a may communicate (e.g.. one or more of receive, obtain, transmit, or output) one or more of control information or data with the core network 130-a via a communication link 125-c, or the base station 140-b may communicate (e.g., one or more of receive, obtain, transmit, or output) one or more of control information or data with the core network 130-a via a communication 125-d,which may be examples of communications links 125 as described herein with reference to FIG. 1.

[0055] The UE 115-a may connect to the core network 130-a via the one or more access networks, such as one or more of the base station 140-a or the base station 140-b, and based at least in part on a connection procedure. For example, the UE 115-a may perform a registration procedure, in which the UE 1 15-a may obtain an internet protocol (IP) address, and the core network 130-a may establish a context (e.g., also referred to as UE context) for the UE 115-a, allowing the UE 115-a to communicate with other network entities (e.g., network functions). In response to the UE 115-successfully completing the registration procedure, the UE 115-a may be connected to the core network 130-a. The core network 130-a may manage various functions, such as routing of data for the UE 115-a, among other examples.

[0056] In the example of FIG. 2, the UE 115-a may be equipped with one or multiple subscriber identity module (SIM) cards, which may allow the UE 115-a to register with and connect to the wireless communications system 200. For example, the UE 1 15-a may be equipped with a SIM 202 and a SIM 204, and the UE 115-a may register and connect to one or more of the base station 140-a or the base station 140-b using the SIM 202 or the SIM 204, as well as register and connect to the core network 130-a via one or more of the base station 140-a or the base station 140-b and using one or more of the SIM 202 or the SIM 204. Each of the SIM 202 and the SIM 204 of the UE 115-a may be associated with a subscriber identity, which may include an international mobile subscriber identity' (IMSI) and the mobile subscriber integrated services digital network number (MSISDN).

[0057] The UE 115-a may be equipped (e.g., configured) with multiple protocol stacks to support one or multiple wireless services over one or multiple access networks, such as one or more of the base station 140-a or the base station 140-b. For example, the UE 115-a may be equipped with a protocol stack 205 and a protocol stack 210. It should be noted that the UE 115-a may be equipped with more than two protocol stacks. The protocol stack 205 and the protocol stack 210 may be configured for cellular-related operations (e.g., cellular communication, cellular access, such as 5GNR access) of the UE 115-a. For instance, the protocol stack 205 and the protocol stack 210 may be configured (e.g., correspond) for cellular access operations (e.g., 3GPP access). Each ofthe protocol stack 205 and a protocol stack 210 may include one or more protocol layers, which may be ordered in a hierarchical architecture. Additionally, each of the protocol stack 205 and a protocol stack 210 may include a control plane protocol stack and a user plane protocol stack. For example, the protocol stack 205 (e.g., one or more of a control plane protocol stack and a user plane protocol stack of the protocol stack 205) may include one or more of a NAS-session management (NAS-SM) layer 220, a NAS-mobility management (NAS-MM) layer 225, an RRC layer 230, a PDCP layer 235, an RLC layer 240, a MAC layer 245, or a PHY layer 250. Similarly, the protocol stack 210 (e.g.. one or more of a control plane protocol stack and a user plane protocol stack of the protocol stack 210) may include one or more of a NAS layer 255, an RRC layer 260, a PDCP layer 265, an RLC layer 270, a MAC layer 275, or a PHY layer 280. Additionally, or alternatively, one or more of the protocol stack 205 or the protocol stack 210 may include an SDAP layer.

[0058] In the example of FIG. 2. the UE 115-a may be equipped (e.g., configured) with a higher layer 215 (also referred to as a “dual-steer layer’), which may be distinct from both the protocol stack 205 and the protocol stack 210. Put another way, the higher layer 215 of the UE 115-a may be separate (e.g., unencapsulated) from both the protocol stack 205 and the protocol stack 210, including the different protocol layers within each of the protocol stack 205 and the protocol stack 210. The higher layer 215 of the UE 115-a may reside (e.g., located) above the protocol stack 205 and the protocol stack 210. While the higher layer 215 of the UE 115-a may reside above the protocol stack 205 and the protocol stack 210, the higher layer 215 of the UE 115-a may interface with other layers or components (e.g., hardware, software) above and below the higher layer 215. As such, the higher layer 215 of the UE 115-a may support interoperability with one or more of the different protocol layers within each of the protocol stack 205 and the protocol stack 210.

[0059] The higher layer 215 of the UE 115-a may also include a control plane and a user plane. The control plane of the higher layer 215 of the UE 115-a may manage steering rules (also referred to as “dual-steer rules”) that may be obtained (e.g., received) from a network (e.g., a base station or network entity). The higher layer 215 of the UE 115-a may also be configured with a mechanism (e g., a trigger condition) for the UE 115-a to receive the steering rules, for example, in response to a protocol dataunit (PDU) session establishment by a primary protocol stack, such as the protocol stack 205 of the UE 115 -a. The user plane of the higher layer 215 of the UE 115 -a may support one or more of a hypertext transfer protocol (HTTP) (e.g., HTTP3), a multipath QUIC (MP-QUIC) protocol, user datagram protocol (UDP), or an IP. The higher layer 215 of the UE 115-a may determine to establish at least a quantify of MP-QUIC connections based at least in part on a quantify of qualify of service (QoS) flows associated with both the protocol stack 205 and the protocol stack 210. Put another way, the UE 115-a may establish one MP-QUIC connection per QoS flow. Additionally, or alternatively, the user plane of the higher layer 215 of the UE 115-a may support one or more of a multipath transmission control protocol (MPTCP), a TCP, or an IP. The higher layer 215 of the UE 115-a may coordinate session management functionality for each of the protocol stack 205 or the protocol stack 210, triggering establishment of one or more corresponding PDU sessions by one or more of the protocol stack 205 or the protocol stack 210.

[0060] In accordance with aspects of the present disclosure, the higher layer 215 of the UE 115-a may be configured with one or more functionalities, including one or more of steering, switching, or aggregating data traffic for the UE 115-a, particularly via one or protocol stacks and for one or multiple access networks as described herein. For example, the higher layer 215 of the UE 1 15-a may be configured with a management function (also referred to as a ‘'dual-steer management function (DSMF)” or “dual-stack Management Function (DSMF)’') configured for one or more of steering, switching, or aggregating data traffic over multiple protocol stacks of the UE 115-a. Additionally, or alternatively, the management function of the higher layer 215 of the UE 115-a may be configured to manage (e.g., activate or deactivate) wireless communication over either or both the protocol stack 205 and the protocol stack 210. In some examples, the management function of the higher layer 215 of the UE 115-a may be configured to manage (e.g.. activate or deactivate) wireless communications over one or both the protocol stack 205 or the protocol stack 210, based at least in part on one or more URSP rules. The management function of the higher layer 215 of the UE 115-a may be configured to manage (e.g., activate or deactivate) wireless communication over one or more of the protocol stack 205 or the protocol stack 210 per traffic flow, which may be defined by traffic information. For example, the management function of the higherlayer 215 of the UE 115-a may be configured to manage (e.g., activate or deactivate) wireless communication over one or more of the protocol stack 205 or the protocol stack 210 based at least in part on URSP rules and traffic information (e.g., traffic descriptor(s). traffic characteristics, a destination address, a transport port (e.g.. a transmission control protocol (TCP), user datagram protocol (UDP)), or an application identifier).

[0061] A URSP rule may support establishing and utilizing a PDU session, associated with a corresponding network slice for an application associated with the UE 115-a. The URSP rule may include information mapping data traffic (also referred to ■‘user data traffic’’ herein) to one or more parameters (e.g., an application descriptor, a data network name (DNN), a protocol data unit (PDU) session information, etc.) of the URSP rule. Data traffic may be defined in the URSP rule by traffic information (also referred to as a “traffic descriptor”), which may determine when the URSP rule is applicable. The UE 115-a may determine that a corresponding URSP rule is applicable when the traffic descriptor matches corresponding information of the application. The UE 115-a may, via the higher layer 215, determine, based at least in part on one or more of the traffic descriptor and the one or more parameters, whether (e.g., il) the application associated with the UE 115-a may use an established session (e.g., a PDU session) or whether (e.g., if) the UE 115-a, for example, via the higher layer 215 may trigger a PDU session establishment procedure to establish a PDU session for the application.

[0062] In some examples, the PDU session information may indicate whether the data traffic shall be routed via a PDU session supporting a PDU session type. In some other examples, the PDU session information may indicate whether the data traffic shall be offloaded to a PDU session associated with a different access netw ork and associated with a different access network ty pe. In other examples, the PDU session information may indicate whether the UE 115-a shall establish a PDU session when the URSP rule is applicable. Additionally, the PDU session information may indicate an access network type (e.g., single-access (SA) network type or a multi-access (MA) network ty pe) on which the PDU session should be established.

[0063] The higher layer 215 of the UE 115-a may obtain (e.g., receive) one or more URSP rules from one or both of the protocol stack 205 or the protocol stack 210 of theUE 1 15-a. For example, the UE 115-a may receive, from one or both of the base station 140-a or the base station 140-b, signaling (e.g., packets, messages, frames) cartying one or more corresponding URSP rules via the one or both of the protocol stack 205 or the protocol stack 210 of the UE 115-a. One or both of the base station 140-a or the base station 140-b may obtain (e.g., receive) the one or more corresponding URSP rules for the UE 115-a from the core network 130-a. The UE 115-a may process (e.g., demodulate, decode) the signaling, to identify the one or more corresponding URSP rules associated with one or both of the protocol stack 205 or the protocol stack 210 of the UE 115-a.

[0064] In some examples, when the higher layer 215 of the UE 115-a obtains (e.g., receives) URSP rules from each of the protocol stack 205 and the protocol stack 210 of the UE 115-a, the higher layer 215 of the UE 115-a may consolidate (e.g., aggregate, combine,join) the URSP rules from each of the protocol stack 205 and the protocol stack 210 into a consolidated set of URSP rules. For example, the higher layer 215 of the UE 115-a may obtain URSP rule(s) 292 from the protocol stack 205 and URSP rule(s) 294 from the protocol stack 210 of the UE 115-a, and consolidate the URSP rule(s) 292 and the URSP rule(s) 294 into a consolidated set of URSP rules. In some other examples, when the higher layer 215 of the UE 115-a obtains (e.g., receives) URSP rules from one the protocol stack 205 or the protocol stack 210 of the UE 115-a, the higher layer 215 of the UE 115-a may enable one or more rules to prevent the other protocol stack (e.g., the protocol stack 210 of the UE 115-a) from obtaining URSP rules or using the obtained URSP rules. For example, the higher layer 215 of the UE 115-a may obtain URSP rule(s) 292 from the protocol stack 205 and, in response, prevent the protocol stack 210 of the UE 115-a from receiving the URSP rule(s) 294 or using the received URSP rule(s) 294.

[0065] The core network 130-a may include a unified data repository (UDR). which may store UE information (e.g., subscription information) that may be used by other network entities, such as a policy control function (PCF) of the core network 130-a to manage (e.g., update, remove, modify, adjust, delete, store) URSP rules for the UE 1 15- a. In some examples, the UE information may indicate whether the UE 115-a includes multiple protocol stacks and whether a protocol stack is a primary protocol stack (e.g., the protocol stack 205) or a secondary protocol stack (e.g., the protocol stack 210). Thecore network 130-a may also include a unified data management function (UDM), which may store the UE information. The core network 130-a may also include an access and mobility management function (AMF), which may obtain the UE information from the UDM and output (e.g.. forward, transmit, route) the UE information to the PCF of the core network 130-a. Based at least in part on the UE information, the PCF of the core network 130-a may store and provide (e.g., output, transmit) empty URSP rules for the UE 115-a via one or both of the base station 140-a or the base station 140-b, so that previously stored URSP rules at the UE 115-a are deleted. An empty URSP rule may be a URSP rule in which one or more parameters, such as a traffic descriptor, an application descriptor, a DNN, a PDU session information, etc. do not have a value (e.g., information). Alternatively, based at least in part on the UE information, the PCF of the core network 130-a may store and withhold from providing (e.g.. refrain from outputting or transmitting) any URSP rules to the UE 115-a via one or both of the base station 140-a or the base station 140-b.

[0066] In some other examples, the UE 115-a may transmit control signaling that indicates whether the UE 115-a includes multiple protocol stacks and whether a protocol stack is a primary protocol stack (e.g., the protocol stack 205) or a secondary' protocol stack (e.g., the protocol stack 210). For example, the UE 115-a may transmit, to the core network 130-a (e.g., an AMF of the core network 130-a via one or both of the base station 140-a or the base station 140-b), a UE state indication message that may include an indication (e.g., an information element (IE), field, or the like) of whether a protocol stack is a primary protocol stack (e.g., the protocol stack 205) or a secondary protocol stack (e.g., the protocol stack 210). Based at least in part on the UE state indication message, the PCF of the core network 130-a may store and provide (e.g., output) empty' URSP rules to the UE 115-a via one or both of the base station 140-a or the base station 140-b. Alternatively, based at least in part on the UE state indication message, the PCF of the core network 130-a may withhold from providing (i.e., not provide) any URSP rules to the UE 1 15-a via one or both of the base station 140-a or the base station 140-b. In other examples, the protocol stack 210 of the UE 115-a may be configured to ignore any obtained (e.g., received) URSP rules, such as URSP rule(s) 294.

[0067] The UE 1 15-a may process one or both of the URSP rule(s) 292 for the protocol stack 205 and the URSP rule(s) 294 for the protocol stack 210. Based at least in part on the traffic information (e.g., traffic characteristics, a destination address, a transport port (e.g.. TCP. UDP), or an application identifier) or other information (e.g.. application descriptor, a DNN, a PDU session information, etc.), the UE 115-a may determine to associate (e.g., bind) a connection request (e.g., a PDU session establishment request) for a PDU session (e.g., a PDU session 295-a or a PDU session 295-b) to one or both of the protocol stack 205 or the protocol stack 210 of the UE 115- a. In some examples, the PDU session 295-a associated with the protocol stack 205 or the PDU session 295-b associated with the protocol stack 210 may be a PDU session that does not support routing data traffic over multiple protocol stacks, such as the protocol stack 205 and the protocol stack 210 of the UE 115-a. A PDU session that does not support steering, switching, or aggregating of data traffic over multiple protocol stacks of the UE 115-a may be referred to as a “regular PDU session,’’ while a PDU session that supports steering, switching, or aggregating of data traffic over multiple protocol stacks of the UE 115-a may be referred to as a “dual stack (DS) PDU session” or more generally a “multi-stack (MS) PDU session.”

[0068] In some examples, the UE 115-a may determine, via the higher layer 215. to establish a PDU session associated with a specific PDU session type (e.g., regular PDU session or a DS PDU session) based at least in part on the consolidated set of URSP rules as described herein. In some other examples, the UE 115-a may determine, via the higher layer 215, to establish a PDU session associated with a specific PDU session type (e.g., regular PDU session, a DS PDU session) based at least in part on whether the core network 130-a supports establishing a DS PDU session. In other examples, the UE 115-a may determine, via the higher layer 215, to establish a PDU session associated with a specific PDU session type (e.g., regular PDU session vs. a DS PDU session) based at least in part on whether the PDU session is bound (e.g., linked, associated) to a network slice supporting the DS PDU session.

[0069] In some examples, a URSP rule within the URSP rule(s) 292 may link (e.g., bind) an application or the like (e.g., a traffic classifier (TC) or a service) to a PDU session, provided the PDU session is available (e.g.. an established PDU session) and associated with the protocol stack 205 with no DS-PDU support. In some examples, aURSP rule within the URSP rule(s) 294 may link (e.g., bind) an application or the like (e.g., a TC or a service) to a PDU session, provided the PDU session is available (e.g., an established PDU session) and associated with the protocol stack 210 with no MA- PDU support. In other examples, if both URSP rules, as described above, link (e.g., bind) an application or the like (e.g., a TC or a service) to a PDU session (e.g., a non DS-PDU session) associated with the protocol stack 205 or the protocol stack 210, the higher layer 215 of the UE 115-a may consolidate both URSP rules.

[0070] The higher layer 215 of the UE 115-a may apply a priority to a consolidated URSP rule. For example, the higher layer 215 of the UE 115-a may assign a first priority to the URSP rule within the URSP rule(s) 292, provided the PDU session is available (e.g., an established PDU session). In this example, the protocol stack 205 functions as a primary protocol stack, while the protocol stack 210 functions as a non- primary protocol stack (i.e., secondary protocol stack). Alternatively, the higher layer 215 of the UE 115-a may assign a second priority to the URSP rule within the URSP rule(s) 292 and the URSP rule within the URSP rule(s) 294, provided the PDU sessions are available (e.g., established PDU sessions) and for the same application or the like (e.g., the same TC or service). The URSP rule within the URSP rule(s) 292 and the URSP rule within the URSP rule(s) 294 may be consistent with each other. In some examples, the higher layer 215 of the UE 115-a may obtain exclusively a URSP rule via the protocol stack 205. Alternatively, the higher layer 215 of the UE 115-a may obtain the consolidate URSP rule via the protocol stack 205 and the protocol stack 210.

[0071] The UE 115-a may determine, via the higher layer 215, whether to activate or deactivate the protocol stack 205 or the protocol stack 210 based at least in part on the specific PDU session type, and may transmit or receive the data traffic via one or more of the protocol stack 205 or the protocol stack 210, and based at least in part on steering, routing, or aggregating the data traffic via the protocol stack 205 or the protocol stack 210 of the UE 115-a.

[0072] FIG. 3 shows an example of block diagram 300 of a UE 115-b that supports multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure. In some examples, the UE 115-b may implement or be implemented by aspects of the wireless communications system 100 or the wireless communications system 200 as described herein with reference to FIGs. 1 and 2,respectively. For example, the UE 1 15-b may be an example of UEs 1 15 as described herein with reference to FIGs. 1 and 2, respectively.

[0073] The UE 115-b may be equipped (e.g., configured) with multiple protocol stacks to support one or multiple wireless services over one or multiple access networks as described herein with reference to FIGs. 1 and 2, respectively. For example, the UE 115-b may be equipped with a protocol stack 205-a and a protocol stack 210-a, which may be examples of protocol stacks as described herein with reference to FIGs. 1 and 2, respectively. The protocol stack 205-a may correspond to an IP 305, while the protocol stack 210-a may correspond to an IP 310.

[0074] Additionally, the UE 115-b may be equipped (e.g., configured) with a higher layer 215-a (also referred to as a “dual-steer layer”), which may be an example of higher layer as described herein with reference to FIGs. 1 and 2, respectively. The higher layer 215-a of the UE 115-b may be distinct from both the protocol stack 205-a and the protocol stack 210-a. The higher layer 215-a of the UE 115-b may be configured with a functionality for one or more of steering, switching, or aggregating data traffic over one or more of the protocol stack 205-a or the protocol stack 210-a of the UE 115-b. Additionally, the higher layer 215-a of the UE 115-b may be configured with a functionality for activating or deactivating one or more of the protocol stack 205-a or the protocol stack 210-a of the UE 115-b, as described herein with reference to FIGs. 1 and 2, respectively.

[0075] The higher layer 215-a of the UE 115-b may obtain (e.g., receive) one or more URSP rules from each of the protocol stack 205-a and the protocol stack 210-a of the UE 115-b. For example, the higher layer 215-a of the UE 115-b may obtain one or more URSP rules 292-a from the protocol stack 205-a and one or more URSP rules 294- a from the protocol stack 210-a. In the example of FIG. 2, when the higher layer 215-a of the UE 115-b obtains the one or more URSP rules 292-a from the protocol stack 205- a and the one or more URSP rules 294-a from the protocol stack 210-a, the higher layer 215-a of the UE 115-b may consolidate the URSP rules obtained from the protocol stack 205-a and the protocol stack 210-a into a consolidated set of URSP rules 315 as described herein with reference to FIG. 2.

[0076] FIG. 4 shows an example of block diagram 400 of a UE 1 15-c that supports multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure. In some examples, the UE 115-c may implement or be implemented by aspects of the wireless communications system 100 or the wireless communications system 200 as described herein with reference to FIGs. 1 and 2, respectively. For example, the UE 115-c may be an example of UEs 115 as described herein with reference to FIGs. 1 and 2, respectively.

[0077] The UE 115-c may be equipped (e.g., configured) with multiple protocol stacks to support one or multiple wireless services over one or multiple access networks as described herein with reference to FIGs. 1 and 2, respectively. For example, the UE 115-c may be equipped with a protocol stack 205-b and a protocol stack 210-b, which may be examples of protocol stacks as described herein with reference to FIGs. 1 and 2, respectively. In some examples, the protocol stack 205-b may be a primary protocol stack, while the protocol stack 210-b may be a secondary protocol stack. Each of the protocol stack 205-b and the protocol stack 210-b may be provisioned (or preprovisioned) with separate identifiers, such as subscription permanent identifier (SUPI), international mobile station equipment identifier (IMEI), or the like, and security credentials.

[0078] The UE 115-c may be equipped (e.g., configured, provided, installed) with a higher layer 215-b (also referred to as a “dual-steer layer”), which may be an example of higher layer as described herein with reference to FIGs. 1 and 2, respectively. The higher layer 215-b of the UE 115-c may be distinct from both the protocol stack 205-b and the protocol stack 210-b. The higher layer 215-b of the UE 115-c may be configured with a functionality for one or more of steering, switching, or aggregating data traffic over one or more of the protocol stack 205-b or the protocol stack 210-b of the UE 115-c. Additionally, the higher layer 215-b of the UE 115-c may be configured with a functionality for activating or deactivating one or more of the protocol stack 205- b or the protocol stack 210-b of the UE 115-c, as descnbed herein with reference to FIGs. 1 and 2, respectively.

[0079] The protocol stack 205-b of the UE 115-c may be as a default in an active state, for example, because the protocol stack 205-b is the primary protocol stack of the UE 115-c. However, the protocol stack 210-b of the UE 115-c may be as a default in aninactive state, for example, because the protocol stack 210-b is the secondary protocol stack of the UE 115-c. As described herein with reference to FIGs. 1 and 2, respectively, the primary protocol stack of the UE 115-c may activate the secondary protocol stack of the UE 115-c by switching the secondary protocol stack from the inactive state to an active state. For example, the protocol stack 205 -b of the UE 115-c may activate the protocol stack 210-b of the UE 1 15-c based at least in part on a URSP rule applicable to data traffic associated with one or more applications of the UE 115-c.

[0080] Additionally, or alternatively, the protocol stack 205-b of the UE 115-c may determine to activate or deactivate the protocol stack 210-b of the UE 115-c based at least in part on an application requirement or a URSP rule applicable to data traffic associated with an application of the UE 115-c. Put another way, the UE 115-c may determine to activate or deactivate the protocol stack 210-b of the UE 115-c based at least in part on one or more of a URSP rule applicable to data traffic associated with an application or the application’s requirements. In some examples, activation of the protocol stack 210-b of the UE 115-c may trigger the protocol stack 210-b to perform network selection and registration to the network. The network selection and registration may occur before a PDU session establishment. In other examples, deactivation of the protocol stack 210-b of the UE 115-c may trigger the protocol stack 210-b to deregister with the network from the protocol stack 210-b.

[0081] In the example of FIG. 4, the higher layer 215-b of the UE 115-c may process one or more URSP rules 292-b obtained (e.g., received) from the protocol stack 205-b of the UE 115-c. while ignoring (e.g., not processing) any URSP rules associated with the protocol stack 210-b of the UE 115-c. In some examples, as described herein with reference to FIG. 2, URSP rules may not be provided to the protocol stack 210-b of the UE 115-c.

[0082] FIG. 5 shows an example of block diagram 500 of a UE 115-d that supports multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure. In some examples, the UE 115-d may implement or be implemented by aspects of the wireless communications system 100 or the wireless communications system 200 as described herein with reference to FIGs. 1 and 2, respectively. For example, the UE 115-d may be an example of UEs 115 as described herein with reference to FIGs. 1 and 2, respectively.

[0083] The UE 1 15-d may be equipped (e.g., configured) with multiple protocol stacks to support one or multiple wireless services over one or multiple access networks as described herein with reference to FIGs. 1 and 2, respectively. For example, the UE 115-d may be equipped with a protocol stack 205-c and a protocol stack 210-c. which may be examples of protocol stacks as described herein with reference to FIGs. 1 and 2, respectively.

[0084] The UE 115-d may be equipped (e.g., configured) with a higher layer 215-c, which may be an example of higher layer as described herein with reference to FIGs. 1 and 2, respectively. The higher layer 215-c of the UE 115-d may be distinct from both the protocol stack 205-c and the protocol stack 210-c. The higher layer 215-c of the UE 115-d may be configured with a functionality for one or more of steering, switching, or aggregating data traffic over one or more of the protocol stack 205-c or the protocol stack 210-c of the UE 115-d.

[0085] In some examples, the higher layer 215-c of the UE 115-d may obtain (e.g.. receive) one or more URSP rules from each of the protocol stack 205-c and the protocol stack 210-c of the UE 115-d. For example, the higher layer 215-c of the UE 115-d may obtain one or more URSP rules 292-c from the protocol stack 205-c and one or more URSP rules 294-b from the protocol stack 210-c. When the higher layer 215-c of the UE 115-d obtains the one or more URSP rules 292-c from the protocol stack 205-c and the one or more URSP rules 294-b from the protocol stack 210-c, the higher layer 215-c of the UE 115-d may consolidate the URSP rules obtained from the protocol stack 205-c and the protocol stack 210-c into a consolidated set of URSP rules 502 as described herein with reference to FIGs. 2 and 3, respectively. Additionally, or alternatively, the higher layer 215-c of the UE 115-d may process one or more URSP rules 292-c obtained (e.g., received) from the protocol stack 205-c of the UE 115-d, while ignoring (e.g., not processing) any URSP rules (such as, URSP rules 294-b) associated with the protocol stack 210-c of the UE 115-d. In some examples, as described herein with reference to FIGs. 2 and 4, URSP rules may not be provided to the protocol stack 210-c of the UE 115-d.

[0086] In the example of FIG. 5, the UE 115-d may be capable of establishing one or more PDU session 505, PDU session 510, or PDU session 515. In some examples, the UE 115-d may establish the PDU session 505 based at least in part on at least oneURSP rule of the URSP rules 292-c. The established PDU session 505 may be associated with the protocol stack 205-c and over a first access network. The data traffic of the established PDU session 505 may be associated w ith a first IP. For example, the data traffic of the established PDU session 505 may be routed via the first IP. The established PDU session 505 may be a regular PDU session as described herein with reference to FIG. 2.

[0087] In some other examples, the UE 115-d may, additionally or alternatively, establish the PDU session 510 based at least in part on at least one URSP rule of the URSP rules 294-b. The established PDU session 510 may be associated with the protocol stack 210-c and over a second access network. The data traffic of the established PDU session 510 may be associated with a second IP. For example, the data traffic of the established PDU session 510 may be routed via the first IP. The established PDU session 510 may be a regular PDU session as described herein with reference to FIG. 2.

[0088] In other examples, the UE 115-d may establish the PDU session 515 based at least in part on the consolidated set of URSP rules 502. The established PDU session 515 may be associated with the protocol stack 205-c and the protocol stack 210-c and over one or more of a first access network or a second access network. The established PDU session 515 may be a DS PDU session as described herein with reference to FIG.2. The data traffic of the established PDU session 515 may be associated with a third IP and a fourth IP. For example, the data traffic of the established PDU session 515 may be routed via the protocol stack 205-c over the third IP and via the protocol stack 210-c over the fourth IP. The higher layer 215-c of the UE 115-d may manage (e.g., evaluate, determine, apply) access traffic steering-switching-splitting (ATSSS) rules for the data traffic of the established PDU session 515. The higher layer 215-c of the UE 115-d may also support MP-TCP and MP-QUIC for managing (e.g., routing, transporting, etc.) the data traffic of the established PDU session 515.

[0089] FIG. 6 shows an example of a process flow 600 that supports multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure. The process flow 600 may implement aspects of the wireless communications sy stem 100 and the wireless communications system 200 as described with reference to FIGs. 1 and 2, respectively. The process flow 600 may include a UE1 15-e and a base station 140-c, which may be examples of UEs and base stations as described herein. The UE 115-e may include a protocol stack 205-d, a protocol stack 210-d, and a higher layer 215-d, as described herein with reference to FIGs. 1 through 5. For example, in the example of FIG. 6, the protocol stack 205-d may be a primary protocol stack of the UE 115-e, while the protocol stack 210-d may be a secondary protocol stack of the UE 115-e. Additionally, the process flow 600 may include an AMF 605, a PCF 610, an authentication server function (AUSF) 615, and a UDM 620, which may be examples of network entities or network functions as described herein.

[0090] In the following description of the process flow 600, the operations between the UE 115-e, the base station 140-c, the AMF 605, the PCF 610, the AUSF 615, and the UDM 620 may be transmitted in a different order than the example order shown, or the operations performed by the UE 115-e, the base station 140-c, the AMF 605, the PCF 610. the AUSF 615, and the UDM 620 may be performed in different orders or at different times. Some operations may also be omitted from the process flow 600. and other operations may be added to the process flow 600.

[0091] The UE 115-e may register with a network (e.g., one or more of the base station 140-c, the AMF 605, the PCF 610, the AUSF 615, or the UDM 620) to obtain access to wireless services associated with the network. To register with the network, the UE 115-e may perform a registration procedure, which may include exchange of signaling (e.g., information) with one or more of the base station 140-c, the AMF 605, the PCF 610, the AUSF 615, or the UDM 620. In some examples, the protocol stack 205-d of the UE 115-e may determine to activate or deactivate the protocol stack 210-d of the UE 115-e based at least in part on an application requirement or a URSP rule applicable to data traffic associated with an application of the UE 1 15-e. Put another way, the UE 115-e may determine to activate or deactivate the protocol stack 210-d of the UE 115-e based at least in part on one or more of a URSP rule applicable to data traffic associated with an application or the application's requirements. In some examples, activation of the protocol stack 210-d of the UE 115 -emay trigger the protocol stack 210-d to perform a network selection and registration to the network. The network selection and registration may occur before a PDU session establishment. In other examples, deactivation of the protocol stack 210-d of the UE 115-e may trigger the protocol stack 210-d to deregister with the network from the protocol stack 210-d.

[0092] At 632, the UE 1 15-e may transmit, via the protocol stack 205-d (e.g., a primary protocol stack of the UE 115-e), a registration request message to the base station 140-c. The registration request message may include one or more parameters, such as access network parameters (e.g.. a registration type, a SUCI, a global unique temporary identifier (GUTI), etc.), security parameters (e.g., requested network slice selection assistance information (NSSAI), etc.), PDU session parameters (e.g., a PDU session status), and the like. In some examples, the UE 115-e may include in the registration request message an indication that the protocol stack 205-d corresponds to a primary protocol stack of the UE 115-e. In some other examples, the UE 115-e may not provide any indication of the protocol stack 205-d corresponding to a primary protocol stack of the UE 115-e.

[0093] At 634, the base station 140-c may transmit, to the AMF 605, a registration request message. For example, the base station 140-c may forward, to the AMF 605, the registration request message received from the UE 115-e.

[0094] At 636, in response to the registration request message, one or more of the UE 1 15-e (e.g., the protocol stack 205-d of the UE 115-e), the base station 140-c, or the AMF 605 may perform an authentication and security' procedure. Additionally, at 636, one or more of the PCF 610, the AUSF 615. or the UDM 620 may perform one or more operations associated with the authentication and security procedure and with one or more of the UE 115-e, the base station 140-c, or the AMF 605.

[0095] At 638, the AMF 605 may perform a registration operation to register with the UDM 620 via an exchange of one or more messages (e.g., a Nudm_UECM_Registration).

[0096] In response to the AMF 605 registering with the UDM 620, and the AMF 605 lacking subscription information associated with the UE 115-e, the AMF 605 may, at 640, retrieve the subscription information from the UDM 620 via an exchange of one or more messages (e.g., aNudm_SDM_Get). The subscription information associated with the protocol stack 205-d of the UE 115-e may include an indication of whether steering, switching, or aggregating of data traffic over multiple protocol stacks of the UE 1 15-e (e g., dual steering) is supported (e g., allowed, enabled), and whether it is supported by other protocol stacks of the UE 115-e (e.g., the protocol stack 210-d). Insome examples, the AMF 605 might not have to be notified of an identifier (e.g., a SUPI) associated with the other protocol stacks of the UE 115-e (e.g., the protocol stack 210-d). At 642. the AMF 605 may subscribe to be notified of changes to the subscription information via an exchange one or more messages (e.g., Nudm_SDM_Subscribe) with one or more of the PCF 610, the AUSF 615, or the UDM 620.

[0097] At 644, one or more of the AMF 605 or the PCF 610 may perform an access and mobility (AM) policy association establishment procedure.

[0098] At 646, the AMF 605 may output, to the UE 115-e, a registration accept message. For example, the AMF 605 may transmit, to the base station 140-c. the registration accept message, and the base station 140-c may transmit (e g., forward), to the UE 115-e, the registration accept message. In some examples, the UE 115-e may receive the registration accept message via the protocol stack 205-d of the UE 115-e. The registration accept message may include one or more of a GUTI. a registration area, an allowed NSSAI, or an indication of whether steering, switching, or aggregating of data traffic over multiple protocol stacks of the UE 115-e (e.g., dual steering) is supported (e.g., allowed).

[0099] At 648, one or more of the AMF 605 or the PCF 610 may perform a UE policy association establishment procedure. During the UE policy association establishment procedure, the AMF 605 may obtain one or more URSP rules from the PCF 610. The one or more URSP rules may be extended to indicate a list of sendees, traffic, or applications that are subject to dual steering.

[0100] At 650, the UE 115-e may output (e.g., transmit, provide), to the AMF 605, a registration complete message, which may acknowledge the information in the received registration accept message. In some examples, the UE 115-e may output, via the protocol stack 205-d (e.g., a pnmary protocol stack) to the AMF 605, the registration complete message. For example, the protocol stack 205-d of the UE 115-e may transmit to the base station 140-c the registration complete message, and the base station 140-c may forward (e.g., transmit) the registration complete message to the AMF 605.

[0101] At 652, the UE 115-e may obtain from the AMF 605 an update command (e.g., a UE Configuration Update Command), which may include the one or moreURSP rules. In some examples, the protocol stack 205-d (e.g., a primary protocol stack) of the UE 115-e may obtain the one or more URSP rules from the update command. For example, the protocol stack 205-d (e.g., a primary protocol stack) of the UE 115-e may receive the update command from the base station 140-c, where the base station 140-c forwards the update command received at the base station 140-c from the AMF 605.

[0102] At 654, the protocol stack 205-d of the UE 115-e may provide (e.g., output) the one or more URSP rules to the higher layer 215-d of the UE 115-e, which may perform one or more operations as described herein with reference to FIGs. 1 through 5.

[0103] FIG. 7 shows an example of a process flow 700 that supports multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure. The process flow 700 may implement aspects of the wireless communications system 100 and the wireless communications system 200 as described with reference to FIGs. 1 and 2, respectively. The process flow 700 may include a UE 115-f and a base station 140-d. which may be examples of UEs and base stations as described herein. The UE 115-f may include a protocol stack 205-e, a protocol stack 210-e, and a higher layer 215-e, as described herein with reference to FIGs. 1 through 5. In the example of FIG. 7, the protocol stack 205-e may be a primary protocol stack of the UE 115-f, while the protocol stack 210-e may be a secondary protocol stack of the UE 115-f. Additionally, the process flow 700 may include an AMF 705, a PCF 710, an AUSF 715, and a UDM 720, which may be examples of network entities or network functions as described herein.

[0104] In the following description of the process flow 700, the operations between the UE 115-f, the base station 140-d, the AMF 705, the PCF 710, the AUSF 715. and the UDM 720 may be transmitted in a different order than the example order shown, or the operations performed by the UE 115-f, the base station 140-d, the AMF 705, the PCF 710, the AUSF 715, and the UDM 720 may be performed in different orders or at different times. Some operations may also be omitted from the process flow 700, and other operations may be added to the process flow 700.

[0105] At 732. the higher layer 215-e of the UE 115-f may trigger the protocol stack 210-e of the UE 115-f to initiate a registration procedure. For example, the higher layer 215-e of the UE 115-f may output an indication to the protocol stack 210-e of the UE1 15-f to initiate a registration procedure. In the example of FIG. 7, the protocol stack 205-e of the UE 115-f may have established a DS PDU session prior to the higher layer 215-e of the UE 115-f triggering the protocol stack 210-e of the UE 115-f to initiate the registration procedure. In some examples, the higher layer 215-e of the UE 115-f may trigger the protocol stack 210-e of the UE 115-f to initiate a registration procedure in response to the protocol stack 205-e of the UE 115-f having established a DS PDU session.

[0106] At 734, the UE 115-f may transmit, via the protocol stack 210-e (e.g., a secondary protocol stack of the UE 115-1), a registration request message to the base station 140-d. The registration request message may include one or more parameters, such as access network parameters (e.g., a registration type, a SUCI, a GUTI, etc.), security parameters (e.g., requested NSSAI, etc.), PDU session parameters (e.g., a PDU session status), and the like. In the example of FIG. 7. the requested NSSAI by the protocol stack 210-e of the UE 1 15-f may be consistent with (e.g., the same) the requested NSSAI by the protocol stack 205-e of the UE 1 15-f.

[0107] At 736, the base station 140-d may transmit, to the AMF 705, a registration request message. For example, the base station 140-d may forward, to the AMF 705, the registration request message received from the UE 115-f.

[0108] At 738, in response to the registration request message, one or more of the UE 1 15-f (e.g., the protocol stack 210-e of the UE 1 15-f), the base station 140-d, or the AMF 705 may perform an authentication and security procedure. Additionally, at 736, one or more of the PCF 710, the AUSF 715, or the UDM 720 may perform one or more operations associated with the authentication and security procedure and with one or more of the UE 115-e, the base station 140-c, or the AMF 605.

[0109] At 740, the AMF 705 may perform a registration operation to register with the UDM 720 via an exchange of one or more messages (e.g., a Nudm_UECM_Registration).

[0110] In response to the AMF 705 registering with the UDM 720, and the AMF 705 lacking subscription information associated with the UE 115-f, the AMF 705 may. at 742, retrieve the subscription information from the UDM 720 via an exchange of one or more messages (e.g., aNudm_SDM_Get). For example, the UDM 720 may includein the subscription information associated with the UE 1 15-f that dual steering is supported (e.g., allowed) for the protocol stack 210-e (e.g., SUPI) of the UE 115-f and that the protocol stack 210-e of the UE 115-f corresponds to a secondary protocol stack of the UE 115-f. As such, the subscription information associated with the protocol stack 210-e of the UE 115-f may include an indication of whether steering, switching, or aggregating of data traffic over multiple protocol stacks of the UE 115-f (e.g., dual steering) is supported (e.g., allowed), and whether it is supported by the protocol stack 210-d ofthe UE 115-f.[OHl] At 744, the AMF 705 may subscribe to be notified of changes to the subscription information via an exchange one or more messages (e.g., Nudm_SDM_Subscribe) with one or more of the PCF 710, the AUSF 715, or the UDM 720.

[0112] At 746, one or more of the AMF 705 or the PCF 710 may perform an AM policy association establishment procedure.

[0113] At 748. the AMF 705 may output, to the UE 115-f, a registration accept message. For example, the AMF 705 may transmit, to the base station 140-d, the registration accept message, and the base station 140-d may transmit (e.g., forward), to the UE 115-f, the registration accept message. In some examples, the UE 115-f may receive the registration accept message via the protocol stack 210-e of the UE 115-f. The registration accept message may include one or more of a GUTI, a registration area, an allowed NSSAI, or an indication of whether steering, switching, or aggregating of data traffic over multiple protocol stacks of the UE 115-f (e.g., dual steering) is supported (e.g., allowed). The allowed NSSAI associated with the protocol stack 210-e of the UE 115-f may correspond to or be within a set of allowed NSSAI associated with the protocol stack 205-e of the UE 115-f.

[0114] At 750, one or more of the AMF 705 or the PCF 710 may perform a UE policy association establishment procedure. During the UE policy association establishment procedure, the AMF 705 may not obtain one or more URSP rules from the PCF 710. For example, based at least in part on the subscription information and that the protocol stack 210-e of the UE 115-f (e.g., in UDR) corresponds to a secondary protocol stack of the UE 115-f, the PCF 710 does not provide the URSP rules.

[0115] At 725, the UE 1 15-f may output (e g., transmit, provide), to the AMF 705, a registration complete message, which may acknowledge the information in the received registration accept message. In some examples, the UE 115-f may output, via the protocol stack 210-e (e.g., a secondary protocol stack) to the AMF 705. the registration complete message. For example, the protocol stack 210-e of the UE 115-f may transmit to the base station 140-d the registration complete message, and the base station 140-d may forward (e.g., transmit) the registration complete message to the AMF 705.

[0116] FIG. 8 shows a block diagram 800 of a device 805 that supports multisteering operations for wireless communications in accordance with one or more aspects of the present disclosure. The device 805 may be an example of aspects of a UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communications manager 820. The device 805, or one or more components of the device 805 (e.g., the receiver 810, the transmitter 815. and the communications manager 820). may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0117] The receiver 810 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to multi -steering operations for wireless communications). Information may be passed on to other components of the device 805. The receiver 810 may utilize a single antenna or a set of multiple antennas.

[0118] The transmitter 815 may provide a means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to multi-steering operations for wireless communications). In some examples, the transmitter 815 may be co-located with a receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a set of multiple antennas.

[0119] The communications manager 820, the receiver 810, the transmitter 815, or various combinations thereof or various components thereof may be examples of means for performing various aspects of multi-steering operations for wireless communications as described herein. For example, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0120] In some examples, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a digital signal processor (DSP), a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g.. by one or more processors, individually or collectively, executing instructions stored in the at least one memory).

[0121] Additionally, or alternatively, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functions of the communications manager 820. the receiver 810. the transmitter 815, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0122] In some examples, the communications manager 820 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 810, the transmitter 815, or both. For example, the communications manager 820 may receive informationfrom the receiver 810, send information to the transmitter 815, or be integrated in combination with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0123] The communications manager 820 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for obtaining, via a higher layer of the device 805, a first set of URSP rules from a first protocol stack of a set of protocol stacks of the device 805, where the set of protocol stacks includes at least two protocol stacks including the first protocol stack of the device 805 and a second protocol stack of the device 805, where the first protocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, where the higher layer includes a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack. The communications manager 820 is capable of, configured to, or operable to support a means for processing, via the higher layer of the device 805, the data traffic associated with the device 805 via one or both of the first protocol stack of the device 805 or the second protocol stack of the device 805 based on the first set of URSP rules and traffic information associated with the data traffic.

[0124] By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 (e.g., at least one processor controlling or otherwise coupled with the receiver 810, the transmitter 815, the communications manager 820. or a combination thereof) may support techniques for more efficient utilization of communication resources.

[0125] FIG. 9 shows a block diagram 900 of a device 905 that supports multisteering operations for wireless communications in accordance with one or more aspects of the present disclosure. The device 905 may be an example of aspects of a device 805 or a UE 115 as described herein. The device 905 may include a receiver 910. a transmitter 915, and a communications manager 920. The device 905, or one of more components of the device 905 (e.g., the receiver 910, the transmitter 915, and the communications manager 920), may include at least one processor, which may becoupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0126] The receiver 910 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to multi -steering operations for wireless communications). Information may be passed on to other components of the device 905. The receiver 910 may utilize a single antenna or a set of multiple antennas.

[0127] The transmitter 915 may provide a means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to multi-steering operations for wireless communications). In some examples, the transmitter 915 may be co-located with a receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a set of multiple antennas.

[0128] The device 905, or various components thereof, may be an example of means for performing various aspects of multi-steering operations for wireless communications as described herein. For example, the communications manager 920 may include a higher layer component 925 a data traffic component 930, or any combination thereof. The communications manager 920 may be an example of aspects of a communications manager 820 as described herein. In some examples, the communications manager 920. or various components thereof, may be configured to perform various operations (e.g.. receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0129] The communications manager 920 may support wireless communications in accordance with examples as disclosed herein. The higher layer component 925 iscapable of, configured to, or operable to support a means for obtaining, via a higher layer of the device 905, a first set of URSP rules from a first protocol stack of a set of protocol stacks of the device 905, where the set of protocol stacks includes at least two protocol stacks including the first protocol stack of the device 905 and a second protocol stack of the device 905, where the first protocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, where the higher layer includes a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack. The data traffic component 930 is capable of, configured to. or operable to support a means for processing, via the higher layer of the device 905, the data traffic associated with the device 905 via one or both of the first protocol stack of the device 905 or the second protocol stack of the device 905 based on the first set of URSP rules and traffic information associated with the data traffic.

[0130] FIG. 10 shows a block diagram 1000 of a communications manager 1020 that supports multi -steering operations for wireless communications in accordance with one or more aspects of the present disclosure. The communications manager 1020 may be an example of aspects of a communications manager 820, a communications manager 920, or both, as described herein. The communications manager 1020, or various components thereof, may be an example of means for performing various aspects of multi-steering operations for wireless communications as described herein. For example, the communications manager 1020 may include a higher layer component 1025. a data traffic component 1030, a rule component 1035, an activation component 1040, a session component 1045, a connection component 1050, a registration component 1055, a rule component 1060, an indicator component 1065, an association component 1070, a subscription component 1075, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e g., via one or more buses).

[0131] The communications manager 1020 may support wireless communications in accordance with examples as disclosed herein. The higher layer component 1025 is capable of, configured to, or operable to support a means for obtaining, via a higher layer of the UE, a first set of URSP rules from a first protocol stack of a set of protocolstacks of the UE, where the set of protocol stacks includes at least two protocol stacks including the first protocol stack of the UE and a second protocol stack of the UE, where the first protocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, where the higher layer includes a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack. The data traffic component 1030 is capable of, configured to, or operable to support a means for processing, via the higher layer of the UE, the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE based on the first set of URSP rules and traffic information associated with the data traffic.

[0132] In some examples, the higher layer of the UE is separate from the first protocol stack of the UE and the second protocol stack of the UE. In some examples, the higher layer is different than one or more of a NAS layer, an RRC layer, a PDCP layer, an RLC layer, a MAC layer, or a PHY layer. In some examples, the first protocol stack and the second protocol stack correspond to cellular communications. In some examples, the first protocol stack and the second protocol stack each include a control plane protocol stack and a user plane protocol stack. In some examples, the control plane protocol stack includes one or more of the NAS layer, the RRC layer, the PDCP layer, the RLC layer, the MAC layer, or the PHY layer. In some examples, the user plane protocol stack includes one or more of the PDCP layer, a SDAP layer, the RLC layer, the MAC layer, or the PHY layer.

[0133] In some examples, the rule component 1035 is capable of. configured to, or operable to support a means for receiving one or both of the first set of URSP rules via the first protocol stack of the UE or a second set of URSP rules via the second protocol stack of the UE. In some examples, the data traffic component 1030 is capable of, configured to, or operable to support a means for processing the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE based on one or more of the first set of URSP rules, the second set of URSP rules, or the traffic information associated with the data traffic.

[0134] In some examples, the rule component 1060 is capable of, configured to, or operable to support a means for processing the first set of URSP rules and the second setof URSP rules based on receiving the first set of URSP rules and the second set of URSP rules, where processing the first set of URSP rules and the second set of URSP rules includes aggregating the first set of URSP rules and the second set of URSP rules. In some examples, the data traffic component 1030 is capable of, configured to, or operable to support a means for processing the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE based on one or more of the first set of URSP rules, the second set of URSP rules, the traffic information associated with the data traffic, or the aggregated set of URSP rules.

[0135] In some examples, each URSP rule in the aggregated set of URSP rules corresponds to a priority. In some examples, the aggregated set of URSP rules includes the first set of URSP rules and the second set of URSP rules.

[0136] In some examples, the rule component 1060 is capable of, configured to, or operable to support a means for refraining from processing the second set of URSP rules via the second protocol stack associated with the UE. In some examples, the data traffic component 1030 is capable of, configured to, or operable to support a means for processing the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE in response to refraining from processing the second set of URSP rules and based on the first set of URSP rules and the traffic information associated with the data traffic.

[0137] In some examples, the indicator component 1065 is capable of, configured to, or operable to support a means for outputting, via the second protocol stack of the UE, an indication that the second protocol stack of the UE is a secondary' protocol stack. In some examples, the rule component 1060 is capable of, configured to, or operable to support a means for receiving the second set of URSP rules via the second protocol stack of the UE includes receiving an empty set of URSP rules.

[0138] In some examples, the rule component 1060 is capable of, configured to, or operable to support a means for determining an absence of the second set of URSP rules based on the indication that the second protocol stack of the UE is the secondary protocol stack.

[0139] In some examples, the first set of URSP rules associates a first application with a first PDU session without DS-PDU capability. In some examples, the second setof URSP rules associates a second application with a second PDU session without MA- PDU capability.

[0140] In some examples, the first protocol stack corresponds to one or more of a first SUPI, a first IMEI, or a first set of security credentials. In some examples, the second protocol stack corresponds to one or more of a second SUPI, a second IMEI, or a second set of security’ credentials.

[0141] In some examples, the activation component 1040 is capable of, configured to, or operable to support a means for activating, via the first protocol stack of the UE, the second protocol stack of the UE based on one or more of the first set of URSP rules being applicable for the data traffic, an aggregated set of URSP rules being applicable for the data traffic, a multi -protocol stack capability supported by one or both of the first access network or the second access network for the data traffic, or a (PDU session for the data traffic being associated with a network slice that supports the multi-protocol stack capability. In some examples, the data traffic component 1030 is capable of, configured to, or operable to support a means for processing the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE based on one or more of the first set of URSP rules, the traffic information associated with the data traffic, or activating the second protocol stack associated with the UE.

[0142] In some examples, the session component 1045 is capable of, configured to, or operable to support a means for triggering, via a higher layer of the UE, one or both of the first protocol stack of the UE or the second protocol stack of the UE to perform a PDU session establishment procedure. In some examples, the data traffic component 1030 is capable of. configured to, or operable to support a means for processing the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE is based on one or more of the first set of URSP rules, the traffic information associated with the data traffic, or the PDU session establishment procedure.

[0143] In some examples, the session component 1045 is capable of, configured to, or operable to support a means for transmitting a PDU session establishment request message. In some examples, the session component 1045 is capable of, configured to, oroperable to support a means for receiving a PDU session establishment response message based on the PDU session establishment request message. In some examples, the session component 1045 is capable of, configured to, or operable to support a means for establishing a PDU session for the data traffic based on the PDU session establishment request message and the PDU session establishment request message. In some examples, the data traffic component 1030 is capable of, configured to, or operable to support a means for processing the data traffic associated with the UE via one or both of the first protocol stack or the second protocol stack based on the established PDU session for the data traffic and a set of data traffic routing rules.

[0144] In some examples, the association component 1070 is capable of, configured to, or operable to support a means for associating the PDU session establishment request message with one or both of the first set of URSP rules or the second set of URSP rules. In some examples, the session component 1045 is capable of, configured to, or operable to support a means for establishing the PDU session for the data traffic based on associating the PDU session establishment request message with one or both of the first set of URSP rules, the second set of URSP rules.

[0145] In some examples, the higher layer component 1025 is capable of, configured to, or operable to support a means for determining, via the higher layer of the UE. a quantity of connections based on a quantity of quality of service flows associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE, where the quantity7of connections includes a quantity' of MP-QUIC. In some examples, the connection component 1050 is capable of, configured to, or operable to support a means for establishing the quantity of connections based on the quality of service flows associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE. In some examples, the data traffic component 1030 is capable of, configured to, or operable to support a means for processing the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE based on one or more of the first set of URSP rules, the traffic information associated with the data traffic, or the quantity of connections.

[0146] In some examples, the registration component 1055 is capable of, configured to, or operable to support a means for triggering, via the higher layer of the UE, registration of one or both of the first protocol stack or the second protocol stack. Insome examples, the higher layer component 1025 is capable of, configured to, or operable to support a means for obtaining, via the higher layer of the UE, the first set of URSP rules based on the registration of one or both of the first protocol stack or the second protocol stack.

[0147] In some examples, the subscription component 1075 is capable of, configured to, or operable to support a means for transmitting subscription information that includes a multi -steering mode capability associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE, where the registration of one or both of the first protocol stack or the second protocol stack is based on the subscription information that includes a multi-steering mode capability associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE.

[0148] In some examples, the registration of the second protocol stack occurs in response to an establishment of a DS-PDU session via the first protocol stack of the UE.

[0149] FIG. 11 shows a diagram of a system 1100 including a device 1105 that supports multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure. The device 1 105 may be an example of or include the components of a device 805, a device 905, or a UE 115 as described herein. The device 1105 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115. or any combination thereof. The device 1105 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, at least one memory 1130, code 1135, and at least one processor 1140. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e g., a bus 1145).

[0150] The I / O controller 1110 may manage input and output signals for the device 1105. The I / O controller 1110 may also manage peripherals not integrated into the device 1105. In some cases, the I / O controller 1110 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 1110 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively,the I / O controller 11 10 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I / O controller 1110 may be implemented as part of one or more processors, such as the at least one processor 1140. In some cases, a user may interact with the device 1105 via the I / O controller 1110 or via hardware components controlled by the I / O controller 1110.

[0151] In some cases, the device 1 105 may include a single antenna 1125. However, in some other cases, the device 1105 may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1115 may communicate bi-directionally, via the one or more antennas 1125, wired, or wireless links as described herein. For example, the transceiver 1115 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1115 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1125 for transmission, and to demodulate packets received from the one or more antennas 1125. The transceiver 1115, or the transceiver 1 115 and one or more antennas 1125, may be an example of a transmitter 815, a transmitter 915, a receiver 810, a receiver 910, or any combination thereof or component thereof, as described herein.

[0152] The at least one memory 1130 may include random access memory (RAM) and read-only memory (ROM). The at least one memory 1130 may store computer- readable, computer-executable code 1135 including instructions that, when executed by the at least one processor 1140, cause the device 1105 to perform various functions described herein. The code 1135 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1135 may not be directly executable by the at least one processor 1140 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1130 may contain, among other things, a basic I / O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0153] The at least one processor 1140 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the at leastone processor 1 140 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 1140. The at least one processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting multi-steering operations for wireless communications). For example, the device 1105 or a component of the device 1105 may include at least one processor 1140 and at least one memory 1130 coupled with or to the at least one processor 1140, the at least one processor 1140 and at least one memory 1130 configured to perform various functions described herein. In some examples, the at least one processor 1140 may include multiple processors and the at least one memory 1130 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. In some examples, the at least one processor 1140 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry' (which may include the at least one processor 1140) and memory circuitry (which may include the at least one memory 1130)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1140 or a processing system including the at least one processor 1140 may be configured to. configurable to, or operable to cause the device 1105 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1130 or otherwise, to perform one or more of the functions described herein.

[0154] The communications manager 1120 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1120 is capable of, configured to, or operable to support a means for obtaining, via a higher layer of the device 1105, a first set of URSP rules from a first protocol stack of a set of protocol stacks of the device 1105, where the set of protocol stacksincludes at least two protocol stacks including the first protocol stack of the device 1 105 and a second protocol stack of the device 1105, where the first protocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, where the higher layer includes a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack. The communications manager 1120 is capable of, configured to, or operable to support a means for processing, via the higher layer of the device 1105, the data traffic associated with the device 1105 via one or both of the first protocol stack of the device 1105 or the second protocol stack of the device 1105 based on the first set of URSP rules and traffic information associated with the data traffic.

[0155] By including or configuring the communications manager 1120 in accordance with examples as described herein, the device 1105 may support techniques for more efficient utilization of communication resources and improved utilization of processing capability.

[0156] In some examples, the communications manager 1120 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1115, the one or more antennas 1125, or any combination thereof. Although the communications manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1120 may be supported by or performed by the at least one processor 1140, the at least one memory 1130, the code 1135, or any combination thereof. For example, the code 1135 may include instructions executable by the at least one processor 1140 to cause the device 1105 to perform various aspects of multisteering operations for wireless communications as described herein, or the at least one processor 1140 and the at least one memory 1130 may be otherwise configured to, individually or collectively, perform or support such operations.

[0157] FIG. 12 shows a block diagram 1200 of a device 1205 that supports multisteering operations for wireless communications in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of aspects of a network entity 105 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215. and a communications manager 1220. The device 1205, or one ormore components ofthe device 1205 (e.g., the receiver 1210, the transmitter 1215, and the communications manager 1220), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0158] The receiver 1210 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 1205. In some examples, the receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0159] The transmitter 1215 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1205. For example, the transmitter 1215 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include or be coupled with a modem.

[0160] The communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof or various components thereof may be examples of means for performing various aspects of multi-steering operations for wireless communications as described herein. For example, the communications manager 1220,the receiver 1210, the transmitter 1215, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0161] In some examples, the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).

[0162] Additionally, or alternatively, the communications manager 1220. the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functions of the communications manager 1220, the receiver 1210, the transmitter 1215. or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0163] In some examples, the communications manager 1220 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1210, the transmitter 1215. or both. For example, the communications manager 1220 may receive information from the receiver 1210, send information to the transmitter 1215, or be integrated in combination with the receiver 1210, the transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0164] The communications manager 1220 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1220 is capable of, configured to, or operable to support a means for obtaining, from a second network entity, subscription information associated with a UE. The communications manager 1220 is capable of, configured to, or operable to support a means for obtaining, from a third network entity, one or both of a first set of URSP rules or a second set of URSP rules. The communications manager 1220 is capable of, configured to, or operable to support a means for outputting, to a higher layer of the UE, one or both of the first set of URSP rules to a first protocol stack of a set of protocol stacks of the UE or the second set of URSP rules to a second protocol stack of the set of protocol stacks of the UE, where the subscription information indicates a multi-steering mode capability associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE. where the first protocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, where the higher layer includes a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack.

[0165] By including or configuring the communications manager 1220 in accordance with examples as described herein, the device 1205 (e.g., at least one processor controlling or otherwise coupled with the receiver 1210, the transmitter 1215, the communications manager 1220, or a combination thereof may support techniques for more efficient utilization of communication resources.

[0166] FIG. 13 shows a block diagram 1300 of a device 1305 that supports multisteering operations for wireless communications in accordance with one or more aspects of the present disclosure. The device 1305 may be an example of aspects of a device 1205 or a network entity 105 as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communications manager 1320. The device 1305, or one of more components of the device 1305 (e.g., the receiver 1310, the transmitter 1315, and the communications manager 1320), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0167] The receiver 1310 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 1305. In some examples, the receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1310 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0168] The transmitter 1315 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1305. For example, the transmitter 1315 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1315 and the receiver 1310 may be co-located in a transceiver, which may include or be coupled with a modem.

[0169] The device 1305, or various components thereof, may be an example of means for performing various aspects of multi-steering operations for wireless communications as described herein. For example, the communications manager 1320 may include a subscription component 1325 a rule component 1330, or any combination thereof. The communications manager 1320 may be an example of aspects of a communications manager 1220 as described herein. In some examples, the communications manager 1320, or various components thereof, may be configured to perform various operations (e.g.. receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1310, the transmitter1315, or both. For example, the communications manager 1320 may receive information from the receiver 1310, send information to the transmitter 1315, or be integrated in combination with the receiver 1310, the transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.

[0170] The communications manager 1320 may support wireless communications in accordance with examples as disclosed herein. The subscription component 1325 is capable of, configured to, or operable to support a means for obtaining, from a second network entity, subscription information associated with a UE. The rule component 1330 is capable of, configured to, or operable to support a means for obtaining, from a third network entity, one or both of a first set of URSP rules or a second set of URSP rules. The rule component 1330 is capable of, configured to, or operable to support a means for outputting, to a higher layer of the UE, one or both of the first set of URSP rules to a first protocol stack of a set of protocol stacks of the UE or the second set of URSP rules to a second protocol stack of the set of protocol stacks of the UE, where the subscription information indicates a multi-steering mode capability associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE, where the first protocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, where the higher layer includes a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack.

[0171] FIG. 14 shows a block diagram 1400 of a communications manager 1420 that supports multi -steering operations for wireless communications in accordance with one or more aspects of the present disclosure. The communications manager 1420 may be an example of aspects of a communications manager 1220, a communications manager 1320, or both, as described herein. The communications manager 1420, or various components thereof, may be an example of means for performing various aspects of multi-steering operations for wireless communications as described herein. For example, the communications manager 1420 may include a subscription component 1425 a rule component 1430, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g.. one or more processors, one or morememories), may communicate, directly or indirectly, with one another (e.g., via one or more buses) which may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0172] The communications manager 1420 may support wireless communications in accordance with examples as disclosed herein. The subscription component 1425 is capable of, configured to, or operable to support a means for obtaining, from a second network entity, subscription information associated with a UE. The rule component 1430 is capable of, configured to, or operable to support a means for obtaining, from a third network entity, one or both of a first set of URSP rules or a second set of URSP rules. In some examples, the rule component 1430 is capable of, configured to. or operable to support a means for outputting, to a higher layer of the UE, one or both of the first set of URSP rules to a first protocol stack of a set of protocol stacks of the UE or the second set of URSP rules to a second protocol stack of the set of protocol stacks of the UE, where the subscription information indicates a multi-steering mode capability associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE, where the first protocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, where the higher layer includes a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack.

[0173] FIG. 15 shows a diagram of a system 1500 including a device 1505 that supports multi-steering operations for wireless communications in accordance with one or more aspects of the present disclosure. The device 1505 may be an example of or include the components of a device 1205, a device 1305, or a network entity 105 as described herein. The device 1505 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device 1505 may include components thatsupport outputting and obtaining communications, such as a communications manager 1520, a transceiver 1510, an antenna 1515, at least one memory' 1525, code 1530, and at least one processor 1535. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1540).

[0174] The transceiver 1510 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1510 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1510 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1505 may include one or more antennas 1515, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1510 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1515, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas 1515, from a wired receiver), and to demodulate signals. In some implementations, the transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1515 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1515 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1510 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1510, or the transceiver 1510 and the one or more antennas 1515. or the transceiver 1510 and the one or more antennas 1515 and one or more processors or one or more memory components (e.g., the at least one processor 1535, the at least one memory' 1525, or both), may be included in a chip or chip assembly that is installed in the device 1505. In some examples, the transceiver 1510 may be operable to support communications via one or more communications links(e.g., a communication link 125, a backhaul communication link 120, a midhaul communication link 162, a fronthaul communication link 168).

[0175] The at least one memory 1525 may include RAM, ROM, or any combination thereof. The at least one memory' 1525 may store computer-readable, computerexecutable code 1530 including instructions that, when executed by one or more of the at least one processor 1535, cause the device 1505 to perform various functions described herein. The code 1530 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1530 may not be directly executable by a processor of the at least one processor 1535 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1525 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1535 may include multiple processors and the at least one memory 1525 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 (for example, as part of a processing system).

[0176] The at least one processor 1535 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the at least one processor 1535 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 1535. The at least one processor 1535 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory’ 1525) to cause the device 1505 to perform various functions (e.g., functions or tasks supporting multi-steering operations for wireless communications). For example, the device 1505 or a component of the device 1505 may include at least one processor 1535 and at least one memory' 1525 coupled with one or more of the at least one processor 1535, the at least one processor 1535 and the at least one memory' 1525 configured to perform various functions described herein. The at least oneprocessor 1535 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1530) to perform the functions of the device 1505. The at least one processor 1535 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1505 (such as within one or more of the at least one memory' 1525). In some examples, the at least one processor 1535 may include multiple processors and the at least one memory 1525 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. In some examples, the at least one processor 1535 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1535) and memory circuitry (which may include the at least one memory 1525)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1535 or a processing system including the at least one processor 1535 may be configured to, configurable to, or operable to cause the device 1505 to perform one or more of the functions described herein. Further, as described herein, being "configured to,’' being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1525 or otherwise, to perform one or more of the functions described herein.

[0177] In some examples, a bus 1540 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1540 may support communications associated with a logical channel of a protocol stack (e.g.. between protocol layers of a protocol stack), which may include communications performed within a component of the device 1505, or between different components of the device 1505 that may be co-located or located in different locations (e.g., where the device 1505 may refer to a system in which one or more of the communications manager 1520, the transceiver 1510, the at least one memory 1525, the code 1530, and the at least oneprocessor 1535 may be located in one of the different components or divided between different components).

[0178] In some examples, the communications manager 1520 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communications manager 1520 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1520 may manage communications with other network entities 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other network entities 105. In some examples, the communications manager 1520 may support an X2 interface within an LTE / LTE-A wireless communications network technology to provide communication between network entities 105.

[0179] The communications manager 1520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1520 is capable of, configured to, or operable to support a means for obtaining, from a second network entity, subscription information associated with a UE. The communications manager 1520 is capable of, configured to, or operable to support a means for obtaining, from a third network entity, one or both of a first set of URSP rules or a second set of URSP rules. The communications manager 1520 is capable of. configured to, or operable to support a means for outputting, to a higher layer of the UE, one or both of the first set of URSP rules to a first protocol stack of a set of protocol stacks of the UE or the second set of URSP rules to a second protocol stack of the set of protocol stacks of the UE, where the subscription information indicates a multi-steering mode capability associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE, where the first protocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, where the higher layer includes a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack.

[0180] By including or configuring the communications manager 1520 in accordance with examples as described herein, the device 1505 may support techniques for improved communication reliability, reduced latency, improved user experiencerelated to reduced processing, and more efficient utilization of communication resources.

[0181] In some examples, the communications manager 1520 may be configured to perform various operations (e.g.. receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1510, the one or more antennas 1515 (e g., where applicable), or any combination thereof. Although the communications manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1520 may be supported by or performed by the transceiver 1510, one or more of the at least one processor 1535, one or more of the at least one memory 1525, the code 1530, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1535, the at least one memory 1525, the code 1530, or any combination thereof). For example, the code 1530 may include instructions executable by one or more of the at least one processor 1535 to cause the device 1505 to perform various aspects of multi-steering operations for wireless communications as described herein, or the at least one processor 1535 and the at least one memory 1525 may be otherwise configured to, individually or collectively, perform or support such operations.

[0182] FIG. 16 shows a flowchart illustrating a method 1600 that supports multisteering operations for wireless communications in accordance with one or more aspects of the present disclosure. The operations of the method 1600 may be implemented by a UE or its components as described herein. For example, the operations of the method 1600 may be performed by a UE 115 as described with reference to FIGs. 1 through 11. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0183] At 1605, the method may include obtaining, via a higher layer of the UE, a first set of URSP rules from a first protocol stack of a set of protocol stacks of the UE, where the set of protocol stacks includes at least two protocol stacks including the first protocol stack of the UE and a second protocol stack of the UE, where the first protocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, where the higher layer includes a management function forone or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack. The operations of block 1605 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a higher layer component 1025 as described with reference to FIG. 10.

[0184] At 1610, the method may include processing, via the higher layer of the UE, the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE based on the first set of URSP rules and traffic information associated with the data traffic. The operations of block 1610 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by a data traffic component 1030 as described with reference to FIG. 10.

[0185] FIG. 17 shows a flowchart illustrating a method 1700 that supports multisteering operations for wireless communications in accordance with one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a UE or its components as described herein. For example, the operations of the method 1700 may be performed by a UE 115 as described with reference to FIGs. 1 through 11. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0186] At 1705, the method may include receiving one or both of a first set of URSP rules via a first protocol stack of the UE or a second set of URSP rules via a second protocol stack of the UE. The operations of block 1705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a rule component 1035 as described with reference to FIG. 10.

[0187] At 1710, the method may include obtaining, via a higher layer of the UE, the first set of URSP rules from the first protocol stack of a set of protocol stacks of the UE, where the set of protocol stacks includes at least two protocol stacks including the first protocol stack of the UE and the second protocol stack of the UE, where the first protocol stack corresponds to a first access network and the second protocol stackcorresponds to a second access network, where the higher layer includes a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack. The operations of block 1710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a higher layer component 1025 as described with reference to FIG. 10.

[0188] At 1715, the method may include processing, via the higher layer of the UE, the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE based on one or more of the first set of URSP rules, the second set of URSP rules, or traffic information associated with the data traffic. The operations of block 1715 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by a data traffic component 1030 as described with reference to FIG. 10.

[0189] FIG. 18 shows a flowchart illustrating a method 1800 that supports multisteering operations for wireless communications in accordance with one or more aspects of the present disclosure. The operations of the method 1800 may be implemented by a UE or its components as described herein. For example, the operations of the method 1800 may be performed by a UE 115 as described with reference to FIGs. 1 through 11. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0190] At 1805, the method may include receiving one or both of a first set of URSP rules via a first protocol stack of the UE or a second set of URSP rules via a second protocol stack of the UE. The operations of block 1805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed by a rule component 1035 as described with reference to FIG. 10.

[0191] At 1810, the method may include obtaining , via a higher layer of the UE. the first set of URSP rules from the first protocol stack of a set of protocol stacks of the UE, where the set of protocol stacks includes at least two protocol stacks including the first protocol stack of the UE and the second protocol stack of the UE, where the firstprotocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, where the higher layer includes a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack. The operations of block 1810 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by a higher layer component 1025 as described with reference to FIG. 10.

[0192] At 1815, the method may include processing the first set of URSP rules and the second set of URSP rules based on receiving the first set of URSP rules and the second set of URSP rules, where processing the first set of URSP rules and the second set of URSP rules includes aggregating the first set of URSP rules and the second set of URSP rules. The operations of block 1815 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed by a rule component 1060 as described with reference to FIG. 10.

[0193] At 1820, the method may include processing , via the higher layer of the UE, the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE is based on one or more of the first set of URSP rules, the second set of URSP rules, the traffic information associated with the data traffic, or the aggregated set of URSP rules. The operations of block 1820 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed by a data traffic component 1030 as described with reference to FIG. 10.

[0194] FIG. 19 shows a flowchart illustrating a method 1900 that supports multisteering operations for wireless communications in accordance with one or more aspects of the present disclosure. The operations of the method 1900 may be implemented by a UE or its components as described herein. For example, the operations of the method 1900 may be performed by a UE 115 as described with reference to FIGs. 1 through 11. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0195] At 1905, the method may include receiving one or both of a first set of URSP rules via a first protocol stack of the UE or a second set of URSP rules via a second protocol stack of the UE. The operations of block 1905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed by a rule component 1035 as described with reference to FIG. 10.

[0196] At 1910, the method may include obtaining, via a higher layer of the UE, the first set of URSP rules from the first protocol stack of a set of protocol stacks of the UE, where the set of protocol stacks includes at least two protocol stacks including the first protocol stack of the UE and the second protocol stack of the UE, where the first protocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, where the higher layer includes a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack. The operations of block 1910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed by a higher layer component 1025 as described with reference to FIG. 10.

[0197] At 1915, the method may include refraining from processing the second set of URSP rules via the second protocol stack associated with the UE. The operations of block 1915 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed by a rule component 1060 as described with reference to FIG. 10.

[0198] At 1920, the method may include processing, via the higher layer of the UE, the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE in response to refraining from processing the second set of URSP rules and based on the first set of URSP rules and the traffic information associated with the data traffic. The operations of block 1920 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed by a data traffic component 1030 as described with reference to FIG. 10.

[0199] FIG. 20 shows a flowchart illustrating a method 2000 that supports multisteering operations for wireless communications in accordance with one or more aspects of the present disclosure. The operations of the method 2000 may be implemented by a network entity or its components as described herein. For example, the operations of the method 2000 may be performed by a network entity as described with reference to FIGs. 1 through 7 and 12 through 15. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

[0200] At 2005, the method may include obtaining, from a second network entity, subscription information associated with a UE. The operations of block 2005 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed by a subscription component 1425 as described with reference to FIG. 14.

[0201] At 2010, the method may include obtaining, from a third network entity, one or both of a first set of URSP rules or a second set of URSP rules. The operations of block 2010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed by a rule component 1430 as described with reference to FIG. 14.

[0202] At 2015, the method may include outputting, to a higher layer of the UE, one or both of the first set of URSP rules to a first protocol stack of a set of protocol stacks of the UE or the second set of URSP rules to a second protocol stack of the set of protocol stacks of the UE, where the subscription information indicates a multi-steering mode capability associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE, where the first protocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, where the higher layer includes a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack. The operations of block 2015 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed by a rule component 1430 as described with reference to FIG. 14.

[0203] It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

[0204] The following provides an overview of aspects of the present disclosure:

[0205] Aspect 1 : A method for wireless communications at a UE, comprising: obtaining, via a higher layer of the UE, a first set of URSP rules from a first protocol stack of a set of protocol stacks of the UE, wherein the set of protocol stacks comprises at least two protocol stacks comprising the first protocol stack of the UE and a second protocol stack of the UE. wherein the first protocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, wherein the higher layer comprises a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack; and processing, via the higher layer of the UE, the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE based at least in part on the first set of URSP rules and traffic information associated with the data traffic.

[0206] Aspect 2: The method of aspect 1, wherein the higher layer of the UE is separate from the first protocol stack of the UE and the second protocol stack of the UE, the higher layer is different than one or more of a NAS layer, an RRC layer, a PDCP layer, an RLC layer, a MAC layer, or a PHY layer, the first protocol stack and the second protocol stack correspond to cellular communications, the first protocol stack and the second protocol stack each comprising a control plane protocol stack and a user plane protocol stack, the control plane protocol stack comprising one or more of the NAS layer, the RRC layer, the PDCP layer, the RLC layer, the MAC layer, or the PFIY layer, or the user plane protocol stack comprising one or more of the PDCP layer, an SDAP layer, the RLC layer, the MAC layer, or the PHY layer.

[0207] Aspect 3: The method of any of aspects 1 through 2. further comprising: receiving one or both of the first set of URSP rules via the first protocol stack of the UE or a second set of URSP rules via the second protocol stack of the UE, wherein processing the data traffic associated with the UE via one or both of the first protocolstack of the UE or the second protocol stack of the UE is based at least in part on one or more of the first set of URSP rules, the second set of URSP rules, or the traffic information associated with the data traffic.

[0208] Aspect 4: The method of aspect 3, further comprising: processing the first set of URSP rules and the second set of URSP rules based at least in part on receiving the first set of URSP rules and the second set of URSP rules, wherein processing the first set of URSP rules and the second set of URSP rules includes aggregating the first set of URSP rules and the second set of URSP rules, wherein processing the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE is based at least in part on one or more of the first set of URSP rules, the second set of URSP rules, the traffic information associated with the data traffic, or the aggregated set of URSP rules.

[0209] Aspect 5: The method of aspect 4, wherein each URSP rule in the aggregated set of URSP rules corresponds to a priority-, and the aggregated set of URSP rules comprises the first set of URSP rules and the second set of URSP rules.

[0210] Aspect 6: The method of any of aspects 3 through 5, further comprising: refraining from processing the second set of URSP rules via the second protocol stack associated with the UE, wherein processing the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE is in response to refraining from processing the second set of URSP rules and based at least in part on the first set of URSP rules and the traffic information associated with the data traffic.

[0211] Aspect 7: The method of any of aspects 3 through 6, further comprising: outputting, via the second protocol stack of the UE, an indication that the second protocol stack of the UE is a secondary protocol stack, wherein receiving the second set of URSP rules via the second protocol stack of the UE comprises receiving an empty- set of URSP rules.

[0212] Aspect 8: The method of aspect 7, further comprising: determining an absence of the second set of URSP rules based at least in part on the indication that the second protocol stack of the UE is the secondary protocol stack.

[0213] Aspect 9: The method of any of aspects 3 through 8, wherein the first set of URSP rules associates a first application with a first PDU session without DS-PDU capability, and the second set of URSP rules associates a second application with a second PDU session without MA-PDU capability.

[0214] Aspect 10: The method of any of aspects 1 through 9, wherein the first protocol stack corresponds to one or more of a first SUPI, a first IMEI, or a first set of security' credentials, and the second protocol stack corresponds to one or more of a second SUPI, a second IMEI, or a second set of security credentials.

[0215] Aspect 11 : The method of any of aspects 1 through 10, further comprising: activating, via the first protocol stack of the UE. the second protocol stack of the UE based at least in part on one or more of the first set of URSP rules being applicable for the data traffic, an aggregated set of URSP rules being applicable for the data traffic, a multi-protocol stack capability supported by one or both of the first access network or the second access network for the data traffic, or a PDU session for the data traffic being associated with a network slice that supports the multi-protocol stack capability, wherein processing the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE is based at least in part on one or more of the first set of URSP rules, the traffic information associated with the data traffic, or activating the second protocol stack associated with the UE.

[0216] Aspect 12: The method of any of aspects 1 through 11, further comprising: triggering, via a higher layer of the UE, one or both of the first protocol stack of the UE or the second protocol stack of the UE to perform a PDU session establishment procedure, wherein processing the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE is based at least in part on one or more of the first set of URSP rules, the traffic information associated with the data traffic, or the PDU session establishment procedure.

[0217] Aspect 13: The method of any of aspects 1 through 12, further comprising: transmitting a PDU session establishment request message; receiving a PDU session establishment response message based at least in part on the PDU session establishment request message; and establishing a PDU session for the data traffic based at least in part on the PDU session establishment request message and the PDU sessionestablishment request message, wherein processing the data traffic associated with the UE via one or both of the first protocol stack or the second protocol stack is based at least in part on the established PDU session for the data traffic and a set of data traffic routing rules.

[0218] Aspect 14: The method of aspect 13. further comprising: associating the PDU session establishment request message with one or both of the first set of URSP rules or the second set of URSP rules, wherein establishing the PDU session for the data traffic is based at least in part on associating the PDU session establishment request message with one or both of the first set of URSP rules, the second set of URSP rules.

[0219] Aspect 15: The method of any of aspects 1 through 14, further comprising: determining, via the higher layer of the UE, a quantity of connections based at least in part on a quantity of quality of sendee flows associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE, wherein the quantity of connections comprises a quantity’ of MP-QUIC; and establishing the quantity of connections based at least in part on the quality of service flows associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE, wherein processing the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE is based at least in part on one or more of the first set of URSP rules, the traffic information associated with the data traffic, or the quantity of connections.

[0220] Aspect 16: The method of any of aspects 1 through 15, further comprising: triggering, via the higher layer of the UE, registration of one or both of the first protocol stack or the second protocol stack, wherein obtaining, via the higher layer of the UE, the first set of URSP rules is based at least in part on the registration of one or both of the first protocol stack or the second protocol stack.

[0221] Aspect 17: The method of aspect 16, further comprising: transmitting subscription information that includes a multi-steering mode capability associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE, wherein the registration of one or both of the first protocol stack or the second protocol stack is based at least in part on the subscription information that includes a multi-steering mode capability associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE.

[0222] Aspect 18: The method of any of aspects 16 through 17, wherein the registration of the second protocol stack occurs in response to an establishment of a dual stack PDU session via the first protocol stack of the UE.

[0223] Aspect 19: A method for wireless communications at a network entity, comprising: obtaining, from a second network entity, subscription information associated with a UE; obtaining, from a third network entity, one or both of a first set of URSP rules or a second set of URSP rules; and outputting, to a higher layer of the UE, one or both of the first set of URSP rules to a first protocol stack of a set of protocol stacks of the UE or the second set of URSP rules to a second protocol stack of the set of protocol stacks of the UE, wherein the subscription information indicates a multisteering mode capability associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE, wherein the first protocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, wherein the higher layer comprises a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack.

[0224] Aspect 20: A UE for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 18.

[0225] Aspect 21 : A UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 18.

[0226] Aspect 22: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 18.

[0227] Aspect 23: A netw ork entity for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupledwith the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 19 through 19.

[0228] Aspect 24: A network entity for wireless communications, comprising at least one means for performing a method of any of aspects 19 through 19.

[0229] Aspect 25: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 19 through 19.

[0230] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE. LTE-A, LTE-A Pro. or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.

[0231] Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0232] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g.. a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). Any functions or operations described herein as beingcapable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.

[0233] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0234] 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 location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory' medium that may be used to carry' or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or yvireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers.Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.

[0235] 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’) 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, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described 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.”

[0236] As used herein, including in the claims, the article “a” before a noun is open- ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a,” “at least one,” “one or more,” “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.”

[0237] The term '‘determine” or '‘determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory) and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0238] In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label.

[0239] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not '‘preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0240] 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, the disclosure 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.

Claims

CLAIMSWhat is claimed is:1 . A user equipment (UE), comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to: obtain, via a higher layer of the UE, a first set of UE route selection policy (URSP) rules from a first protocol stack of a set of protocol stacks of the UE, wherein the set of protocol stacks comprises at least two protocol stacks comprising the first protocol stack of the UE and a second protocol stack of the UE. wherein the first protocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, wherein the higher layer comprises a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack; and process, via the higher layer of the UE, the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE based at least in part on the first set of URSP rules and traffic information associated with the data traffic.

2. The UE of claim 1, wherein: the higher layer of the UE is separate from the first protocol stack of the UE and the second protocol stack of the UE, the higher layer is different than one or more of a non-access stratum (NAS) layer, a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical (PHY) layer, the first protocol stack and the second protocol stack correspond to cellular communications, the first protocol stack and the second protocol stack each comprising a control plane protocol stack and a user plane protocol stack,the control plane protocol stack comprising one or more of the NAS layer, the RRC layer, the PDCP layer, the RLC layer, the MAC layer, or the PHY layer, and the user plane protocol stack comprising one or more of the PDCP layer, an service data adaption protocol (SDAP) layer, the RLC layer, the MAC layer, or the PHY layer.

3. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: receive one or both of the first set of URSP rules via the first protocol stack of the UE or a second set of URSP rules via the second protocol stack of the UE, wherein to process the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE is based at least in part on one or more of the first set of URSP rules, the second set of URSP rules, or the traffic information associated with the data traffic.

4. The UE of claim 3, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: process the first set of URSP rules and the second set of URSP rules based at least in part on receiving the first set of URSP rules and the second set of URSP rules, wherein processing the first set of URSP rules and the second set of URSP rules includes aggregating the first set of URSP rules and the second set of URSP rules, wherein to process the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE is based at least in part on one or more of the first set of URSP rules, the second set of URSP rules, the traffic information associated with the data traffic, or the aggregated set of URSP rules.

5. The UE of claim 4, wherein: each URSP rule in the aggregated set of URSP rules corresponds to a priority, and the aggregated set of URSP rules comprises the first set of URSP rules and the second set of URSP rules.

6. The UE of claim 3, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: refrain from processing the second set of URSP rules via the second protocol stack associated with the UE. wherein to process the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE is in response to refraining from processing the second set of URSP rules and based at least in part on the first set of URSP rules and the traffic information associated with the data traffic.

7. The UE of claim 3, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: output, via the second protocol stack of the UE, an indication that the second protocol stack of the UE is a secondary protocol stack, wherein to receive the second set of URSP rules via the second protocol stack of the UE comprises receiving an empty set of URSP rules.

8. The UE of claim 7, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: determine an absence of the second set of URSP rules based at least in part on the indication that the second protocol stack of the UE is the secondary protocol stack.

9. The UE of claim 3, wherein: the first set of URSP rules associates a first application with a first protocol data unit (PDU) session without dual stack protocol data unit (DS-PDU) capability, and the second set of URSP rules associates a second application with a second PDU session without multi-access protocol data unit (MA-PDU) capability.

10. The UE of claim 1, wherein: the first protocol stack corresponds to one or more of a first subscription permanent identifier (SUPI), a first international mobile station equipment identifier (IMEI), or a first set of security credentials, andthe second protocol stack corresponds to one or more of a second subscription permanent identifier (SUPI), a second international mobile station equipment identifier (IMEI), or a second set of security credentials.

11. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: activate, via the first protocol stack of the UE, the second protocol stack of the UE based at least in part on one or more of the first set of URSP rules being applicable for the data traffic, an aggregated set of URSP rules being applicable for the data traffic, a multi-protocol stack capability supported by one or both of the first access network or the second access network for the data traffic, or a protocol data unit (PDU) session for the data traffic being associated with a network slice that supports the multiprotocol stack capability, wherein to process the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE is based at least in part on one or more of the first set of URSP rules, the traffic information associated with the data traffic, or activating the second protocol stack associated with the UE.

12. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: trigger, via the higher layer of the UE, one or both of the first protocol stack of the UE or the second protocol stack of the UE to perform a protocol data unit (PDU) session establishment procedure, wherein to process the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE is based at least in part on one or more of the first set of URSP rules, the traffic information associated with the data traffic, or the PDU session establishment procedure.

13. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: transmit a protocol data unit (PDU) session establishment request message;receive a PDU session establishment response message based at least in part on the PDU session establishment request message; and establish a PDU session for the data traffic based at least in part on the PDU session establishment request message and the PDU session establishment request message, wherein to process the data traffic associated with the UE via one or both of the first protocol stack or the second protocol stack is based at least in part on the established PDU session for the data traffic and a set of data traffic routing rules.

14. The UE of claim 13, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: associate the PDU session establishment request message with one or both of the first set of URSP rules or the second set of URSP rules, wherein to establish the PDU session for the data traffic is based at least in part on associating the PDU session establishment request message with one or both of the first set of URSP rules, the second set of URSP rules.

15. The UE of claim 1 , wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: determine, via the higher layer of the UE, a quantity of connections based at least in part on a quantity of quality of service flows associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE, wherein the quantity of connections comprises a quantity of multiple path quick user data protocol connections (MP-QUIC); and establish the quantity of connections based at least in part on the quality of service flows associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE, wherein to process the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE is based at least in part on one or more of the first set of URSP rules, the traffic information associated with the data traffic, or the quantity of connections.

16. The UE of claim 1 , wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:trigger, via the higher layer of the UE, registration of one or both of the first protocol stack or the second protocol stack, wherein to obtain, via the higher layer of the UE, the first set of URSP rules is based at least in part on the registration of one or both of the first protocol stack or the second protocol stack.

17. The UE of claim 16, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: transmit subscription information that includes a multi-steering mode capability associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE, wherein the registration of one or both of the first protocol stack or the second protocol stack be based at least in part on the subscription information that includes the multi-steering mode capability associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE.

18. The UE of claim 16, wherein the registration of the second protocol stack occurs in response to an establishment of a dual stack protocol data unit (PDU) session via the first protocol stack of the UE.

19. A network entity, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity' to: obtain, from a second network entity, subscription information associated with a user equipment (UE); obtain, from a third network entity, one or both of a first set of UE route selection policy (URSP) rules or a second set of URSP rules; and output, to a higher layer of the UE, one or both of the first set of URSP rules to a first protocol stack of a set of protocol stacks of the UE or the second set of URSP rules to a second protocol stack of the set of protocol stacks of the UE, wherein the subscription information indicates a multi-steering mode capability associated with one or both of the first protocol stack of the UE or the second protocol stack of the UE. wherein the first protocol stack corresponds toa first access network and the second protocol stack corresponds to a second access network, wherein the higher layer comprises a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack.

20. A method for wireless communications at a user equipment (UE), comprising: obtaining, via a higher layer of the UE. a first set of UE route selection policy (URSP) rules from a first protocol stack of a set of protocol stacks of the UE, wherein the set of protocol stacks comprises at least two protocol stacks comprising the first protocol stack of the UE and a second protocol stack of the UE, wherein the first protocol stack corresponds to a first access network and the second protocol stack corresponds to a second access network, wherein the higher layer comprises a management function for one or more of steering, switching, or aggregating data traffic associated with one or both of the first protocol stack or the second protocol stack; and processing, via the higher layer of the UE, the data traffic associated with the UE via one or both of the first protocol stack of the UE or the second protocol stack of the UE based at least in part on the first set of URSP rules and traffic information associated with the data traffic.

Images