Supporting network traffic steering function for wireless communications

Abstract

Various aspects of the present disclosure relate to supporting network traffic steering function for wireless communications. A first information associated with a multi-protocol-stack capability of a UE for enabling a network traffic steering function is transmitted via a first protocol stack of the UE. The UE is capable of receiving or transmitting data via one or both of the first protocol stack and a second protocol stack of the UE based at least in part on the multi-protocol-stack capability of the UE. A second information for enabling the network traffic steering function is received via the first protocol stack.

Description

SUPPORTING NETWORK TRAFFIC STEERING FUNCTION FOR WIREEESS COMMUNICATIONSTECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more specifically to supporting network traffic steering function for wireless communications.BACKGROUND

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

[0003] The Access Traffic Steering, Switching, and Splitting (ATSSS) framework, developed in 3 GPP Releases 16 through 19, may enable simultaneous transmission of data across a 5G radio access network (RAN) and a non-3GPP access network such as wireless local area network (WLAN).

[0004] In some cases, a DualSteer feature, which may also be referred to as dual steer feature, dual steer function, or other suitable terminology, may enable a UE to simultaneously utilize two 3GPP radio access networks (RANs), such as terrestrial and satellite new radio (NR). The user plane data transmitted on the respective RANs may be aggregated at a common anchor user plane function (UPF) within a core network, wherein no coordination may be required between the RANs. Additional details pertaining to theDualSteer feature can be found, for example, in 3GPP Technical Report (TR) 22.841 V19.0.0 (2023-12).

[0005] As wireless communications transitions from 5Gto beyond 5G, it may be beneficial to support a network traffic steering function, for example, by extending the ATSSS framework and / or the DualSteer feature, to support selective or simultaneous utilization of multiple 3GPP RANs, such as 5G and beyond 5GRANs.SUMMARY

[0006] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, 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”. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0007] In a first aspect, some implementations of the methods, systems, and apparatuses described herein may include: transmitting, via a first protocol stack of a user equipment (UE), a first information associated with a multi-protocol-stack capability of the UE for enabling a network traffic steering function, and receiving, via the first protocol stack, a second information for enabling the network traffic steering function. The UE is capable of receiving or transmitting data via one or both of the first protocol stack and a second protocol stack of the UE based at least in part on the multi-protocol-stack capability of the UE.

[0008] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the second protocol stack is in a null state or an inactive state during and between transmission of the first information and reception of the second information.

[0009] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the second protocol stack is in a null state or an inactive state until transmission of the first information or reception of the second information.

[0010] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the first information indicates that the UE has multi-protocol- stack capability. For example, the first information may include an indicator (e.g., one or more bits) indicating that the UE has multi-protocol-stack capability. For example, the first information may include information indicating that the UE comprises the second protocol stack (e.g., in addition to the first protocol stack).

[0011] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the first information indicates a request for an identity for the second protocol stack.

[0012] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the second information comprises one or more of a core network identity (an identify of a core network) for the first protocol stack or a core network identity (an identify of a core network) for the second protocol stack. For example, the second information may comprise a core network identity for the second protocol stack, and optionally, a core network identity for the first protocol stack (e.g., if the core network identity for the first protocol stack has not yet been received or obtained by the UE).

[0013] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the second information comprises one or more network traffic steering rules for the first protocol stack and the second protocol stack. The one or more network traffic steering rules may govern when, which, or / or how data is communicated via the first protocol stack and the second protocol stack.

[0014] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the second information comprises one or more radio frequencies (RFs), one or more radio access technologies (RATs), or one or more public land mobile networks (PLMNs) for wireless communication via the second protocol stack.

[0015] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the second information comprises one or more candidate cells suitable for wireless communication via the second protocol stack.

[0016] Some implementations of the methods, systems, and apparatuses described herein may include, in the first aspect: in response to transmission of the first information and prior to reception of the second information: receiving, via the first protocol stack, a request message to authenticate the UE; and transmitting, via the first protocol stack, a response message comprising credential information for authenticating the UE.

[0017] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the UE includes a plurality of identity modules each associated with a respective protocol stack of the UE.

[0018] Some implementations of the methods, systems, and apparatuses described herein may include, in the first aspect: in response to transmission of the first information and prior to reception of the second information: receiving a request message to authenticate a first identity module associated with the first protocol stack or a second identity module associated with the second protocol stack; and transmitting a response message comprising one or more of a first credential information of the first identity module (for authenticating the first identity module) or a second credential information of the second identity module (for authenticating the second identity module).

[0019] Some implementations of the methods, systems, and apparatuses described herein may include, in the first aspect: obtaining (e.g., deriving) one or more keys for encryption, integrity protection, authentication, or privacy for the second protocol stack, and providing the one or more keys to the second protocol stack for encryption, integrity protection, authentication, or privacy at the second protocol stack.

[0020] Some implementations of the methods, systems, and apparatuses described herein may include, in the first aspect: outputting the second information to the second protocol stack for use by the second protocol stack to enable the network traffic steering function.

[0021] Some implementations of the methods, systems, and apparatuses described herein may include, in the first aspect: initiating, at the first protocol stack, a first radio resource control (RRC) connection establishment procedure; transmitting via the first protocol stack, information associated with the network traffic steering function; and receiving, via the first protocol stack, network traffic steering assistance information comprising radio information for the second protocol stack and core network information for the second protocol stack.

[0022] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the information associated with the network traffic steering function comprises an indication that the UE has multi-protocol-stack capability.

[0023] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the information associated with the network traffic steering function comprises an indication of whether one or more identity modules of the UE are available.

[0024] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the information associated with the network traffic steering function comprises core network information associated with the first protocol stack. The core network information associated with the first protocol stack may include one or more of registered access and mobility management function (AMF) related information or mobile network identity related information associated with the first protocol stack. The AMF related information associated with the first protocol stack may include AMF associated with the first protocol stack. The mobile network identity related information associated with the first protocol stack may include, e.g., PLMN identity, short-term mobile subscriber identity (S-TMSI), or like identity information associated with the first protocol stack.

[0025] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the information associated with the network traffic steering function comprises a physical cell identity (PCI), a radio frequency (RF), or a radio access technology (RAT) associated with the second protocol stack.

[0026] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the information associated with the network traffic steering function comprises an indication of availability of one or more core network identities of the UE.

[0027] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the radio information for the second protocol stack comprises information associated with PCI, RF, or RAT for the second protocol stack, such as a PCI, a RF, or a RAT for the second protocol stack.

[0028] Some implementations of the methods, systems, and apparatuses described herein may include, in the first aspect: filtering the radio information for the second protocol stack based on one or more signal qualities associated with one or more received radio signals. The one or more received radio signals are based on the information associated with PCI, the RF, or the RAT in the radio information for the second protocol stack.

[0029] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the core network information for the second protocol stack comprises one or more of AMF related information or mobile network identity related information for the second protocol stack. The AMF related information for the second protocol stack may include AMF for the second protocol stack. The mobile network identity related information for the second protocol stack may include, e.g., PLMN identity, S-TMSI, or like identity information for the second protocol stack.

[0030] Some implementations of the methods, systems, and apparatuses described herein may include, in the first aspect: receiving an indication to activate the second protocol stack; and providing, to the second protocol stack, at least, a core network identity for the second protocol stack, the radio information for the second protocol stack, and thecore network information for the second protocol stack. Some implementations of the methods, systems, and apparatuses described herein may further include initializing activation of the second protocol stack.

[0031] Some implementations of the methods, systems, and apparatuses described herein may include, in the first aspect: initiating, at the second protocol stack, a second RRC connection establishment procedure based on the core network identity for the second protocol stack, the radio information for the second protocol stack, and the core network information for the second protocol stack.

[0032] Some implementations of the methods, systems, and apparatuses described herein may include, in the first aspect: initiating establishment of a multi-access protocol data unit (PDU) session for the first protocol stack and the second protocol stack.

[0033] In some implementations of the methods, systems, and apparatuses described herein, in the first aspect: the indication to activate the second protocol stack is based at least in part on an application associated with the UE requiring the network traffic steering function.

[0034] Some implementations of the methods, systems, and apparatuses described herein may include, in the first aspect: switching the first protocol stack to a null state or an inactive state after activation of the second protocol stack.

[0035] In some implementations of the methods, systems, and apparatuses described herein, the first aspect is performed at the UE.

[0036] In a second aspect, some implementations of the methods, systems, and apparatuses described herein may include: receiving a first information associated with a multi-protocol-stack capability of a UE for enabling a network traffic steering function, and transmitting a second information for enabling the network traffic steering function. The UE is capable of receiving or transmitting data via one or both of a first protocol stack and a second protocol stack of the UE based at least in part on the multi-protocol-stack capability of the UE.

[0037] In some implementations of the methods, systems, and apparatuses described herein, the second aspect is performed at the network entity (NE) (network equipment such as base station).

[0038] Other aspects and features will become apparent by consideration of the detailed description and the accompanying drawings. Any feature(s) described herein with reference to any aspect(s) may be combined with any other feature(s) described herein with reference to any aspect(s), where appropriate or applicable.BRIEF DESCRIPTION OF THE DRAWINGS

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

[0040] Figure 2 illustrates an example architecture for supporting network traffic steering function across 5G and beyond-5G in the same public land mobile network (PLMN) in accordance with aspects of the present disclosure.

[0041] Figure 3 illustrates an example of distributing data traffic across 5G and beyond- 5G using different steering modes and steering functionalities in accordance with aspects of the present disclosure.

[0042] Figure 4 illustrates an example for supporting network traffic steering function for wireless communication in accordance with aspects of the present disclosure.

[0043] Figure 5 illustrates an example for supporting network traffic steering function for wireless communication in accordance with aspects of the present disclosure.

[0044] Figure 6 illustrates an example for supporting network traffic steering function for wireless communication in accordance with aspects of the present disclosure.

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

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

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

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

[0049] Figure 11 illustrates a flowchart of a method performed by a NE in accordance with aspects of the present disclosure.

[0050] Figure 12 illustrates an example for supporting network traffic steering function for wireless communication in accordance with aspects of the present disclosure.

[0051] Figure 13 illustrates an example for supporting network traffic steering function for wireless communication in accordance with aspects of the present disclosure.

[0052] Figure 14 illustrates an example for supporting network traffic steering function for wireless communication in accordance with aspects of the present disclosure.

[0053] Figure 15 illustrates an example for supporting network traffic steering function for wireless communication in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0054] Network traffic steering function may be useful for facilitating the migration of wireless communications from 5G to beyond 5G. However, the implementation of the network traffic steering function in access and non-access radio protocols such as 5G and beyond 5G systems is not fully defined. The present disclosure provides example implementations of the methods, systems, and apparatuses that can support network traffic steering function for wireless communication, e.g., from 3GPP L2 / L3 protocol perspective. To this end, in example implementations of the present disclosure, the UE may have multi- protocol-stack (e.g., dual-protocol-stack) capability, i.e., it may include multiple (e.g., two) protocol stacks. If these protocol stacks in the UE are active most of the time or all the time, the UE may function as multiple UEs in the same form factor, and it may have to repeat the same operations (e.g., measurement, reporting, etc.) for each of the protocol stacks. This may lead to wasted resources (e.g., power, processing resources, communication resources, etc.), especially considering that the protocol stacks (in the same UE) are in sameenvironment. The present disclosure provides example implementations of the methods, systems, and apparatuses that can reduce or minimize such repeat or duplication.

[0055] In example implementations of the present disclosure, the UE may transmit, via a first protocol stack of the UE, a first information associated with a multi-protocol-stack capability of the UE for enabling a network traffic steering function, and the UE may receive, via the first protocol stack, a second information for enabling the network traffic steering function. The UE is capable of receiving or transmitting data via one or both of the first protocol stack and a second protocol stack of the UE based at least in part on the multi- protocol-stack capability of the UE. The network traffic steering function may enable communication of data via one or both of the first protocol stack and the second protocol stack of the UE. The second information for enabling the network traffic steering function may be provided, e.g., subsequently, to the second protocol stack to enable the network traffic steering function. Correspondingly, in example implementations of the present disclosure, the NE may receive a first information associated with a multi-protocol-stack capability of a UE for enabling a network traffic steering function, and the NE may transmit a second information for enabling the network traffic steering function. The UE is capable of receiving or transmitting data via one or both of the first protocol stack and a second protocol stack of the UE based at least in part on the multi-protocol-stack capability of the UE. The network traffic steering function may enable communication of data via one or both of the first protocol stack and the second protocol stack of the UE.

[0056] In one example implementation of the present disclosure, only one of the protocol stacks of the UE may be initially activated to provide service to the user, and another protocol stack of the UE may be activated and used when necessary. This may reduce waste of resources (e.g., power, processing resources, communication resources, etc.). In one example implementation of the present disclosure, the initially activated protocol stack may perform operations such as measurements, registration, security authentication, key derivation, or any combinations thereof. The information or results obtained from these operations may be used by another protocol stack of the UE, and this may shorten the time for activating and operating the other protocol stack (i.e., the other protocol stack may “come up” faster). In one example implementation of the presentdisclosure, one of the protocol stacks of the UE may be designated as a primary stack. When the UE powers on, the primary stack may be activated, and it may initiate frequency scan (raw / fine). The non-access stratum (NAS) layer may provide public land mobile network (PLMN) / radio access technology (RAT) information to the access stratum of the primary stack, which may perform cell and PLMN selection according to legacy procedures. The other protocol stack of the UE may remain in a null state or an inactive state. The primary stack may perform idle mode tasks such as receiving system information, monitoring paging, cell selection / re-selection, etc. In one example implementation of the present disclosure, the UE may, via the primary stack, inform the core network (CN) access and mobility management function (AMF) that it has multi- protocol-stack capability (e.g., DualSteer capability) and is interested to use the network traffic steering function (e.g., the DualSteer feature). The UE may seek two different CN identities. This may be performed with an initiated registration procedure, which could be an initial registration or a periodic registration, by including explicit information in an associated registration message.

[0057] Providing a network traffic steering function that can support selective or simultaneous use of two 3GPP radio access networks (RANs), such as 5G and beyond 5G RANs, may be advantageous. For example, a network traffic steering function supported across 5G and beyond 5G (e.g., 6G) may provide various advantages by enabling dynamic use of multiple such radio access networks. For example, the network traffic steering function may ensure efficient coexistence, allowing wireless communications network operators to gradually deploy beyond 5G (e.g., 6G) infrastructure while maintaining robust 5G operations. User plane data from 5G and beyond 5G (e.g., 6G) RANs may be dynamically aggregated at a common user plane anchor, which enables efficient resource utilization and uninterrupted service. For example, by supporting phased deployment, the network traffic steering function may mitigate the challenges of network fragmentation. 5G RANs may provide foundational coverage while beyond 5G (e.g., 6G) RANs may enhance capacity and performance. The dynamic allocation of traffic between these networks can ensure optimized user experience during the transition, with high-performance applications leveraging beyond 5G (e.g., 6G) and basic services continuing on 5G. For example, the network traffic steering function may accelerate the adoption of beyond 5G (e.g., 6G), byenabling inter-PLMN connectivity, allowing users to access beyond 5G (e.g., 6G) services via roaming partners even if their home wireless communications network operator has not yet deployed beyond 5G (e.g., 6G) services. This flexibility may reduce the risks and costs of transitioning, as wireless communications network operators may incrementally deploy beyond 5G (e.g., 6G) components while maximizing the utility of 5G systems.

[0058] Aspects of the present disclosure are described in the context of a wireless communications system.

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

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

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

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

[0063] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface. The UE may be able to support receiving or transmitting data via one or both of the first protocol stack and a second protocol stack of the UE based at least in part on a multi-protocol-stack capability of the UE.

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

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

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

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

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

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

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

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

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

[0073] Figure 2 illustrates an example architecture 200 for supporting network traffic steering function across 5G and beyond-5G (e.g., 6G) in the same PLMN in accordance with aspects of the present disclosure. The example architecture 200 in Figure 2 is simplified to illustrated components relevant to the present disclosure. In this example, the network traffic steering function may be a dual steer function.

[0074] As shown in Figure 2, the architecture 200 includes a UE 202 operable to support 5G and beyond 5G communications, a core network 204 including a 5GC enhanced to support beyond-5G, a 5G RAN 206A and a beyond-5G RAN 206B each operably connected between the UE 202 and the core network 204, and a data network 208 operably connected with the core network 204.

[0075] The UE 202 includes multi-access steering functionalities such as Multipath Transmission Control Protocol (MPTCP), Multipath Quick UDP Internet Connections (QUIC) (MPQUIC), and ATSSS-Low Layer (ATSSS-LL) for enabling advanced traffic steering, switching, and splitting capabilities for various types of traffic, e.g., UDP, TCP, IP, Ethernet. The UE 202 also includes a performance measurement function (PMF). Additional details pertaining to the steering functionalities and the PMF functionalities can be found, e.g., in 3GPP Technical Specifications (TS) 23.501 V19.2.1 (2025-01). The UE 202 is arranged to connect with the control plane of the core network 204 via control plane connection(s).

[0076] The core network 204 includes a 5G control plane that is enhanced to support beyond-5G. The core network 204 also includes a user plane anchor, which includes multi-access steering functionalities such as MPTCP, MPQUIC, and ATSSS-LL, and a PMF, corresponding to the UE 202.

[0077] The 5G RAN 206A is arranged to establish a 5G access connection with the UE 202 and the core network 204. The 5G RAN 206A is connected to the UE 202, to the control plane of the core network 204 via N2 interface, and to the user plane anchor of the core network 204 via N3 interface. The beyond-5G RAN 206B is arranged to establish a beyond-5G access connection for the UE 202 and the core network 204. The beyond-5G RAN 206B is connected to the UE 202, to the control plane of the core network 204 via N2’ interface, and to the user plane anchor of the core network 204 via N3’ interface.

[0078] The multi-access steering functionalities in the UE 202 collaborate with the corresponding multi-access proxy functionalities in the user plane anchor to ensure efficient multi-access connectivity in the uplink (UL) and downlink (DL) directions across the 5G and beyond-5G access connections based on the corresponding traffic steering rules provided by the control plane. The role of the PMF in both the UE 202 and user plane anchor is to dynamically measure performance metrics on each access (e.g., round-trip time (RTT) and packet loss rate) and adjust the traffic routing accordingly. By measuring these metrics, it is feasible to route traffic to the access with the smallest delay or to the access with the smallest packet loss rate.

[0079] In use, registration is performed. Specifically, in this setup, the UE 202 may register to the common core network 204 via both the 5G RAN 206A and the beyond-5G RAN 206B. Connection is further established. Specifically, the UE 202 may establish separate access connections to the common user plane anchor of the core network 204, which is selected by the control plane of the core network 204 during the connection establishment phase. Rules may be further generated. For example, based on network policy, the control plane of the core network 204 may generate traffic steering rules and distributes them to UE 202 and the user plane anchor of the core network 204. These rules may dictate how uplink and downlink traffic should be distributed across the 5G access connection and the beyond-5G access connection and may enable dynamic resource utilization and seamless service continuity. This may be useful for managing the transition from 5Gto beyond-5G.

[0080] Figure 3 illustrates an example of distributing data traffic across 5G and beyond- 5G using different steering modes and steering functionalities in accordance with aspects of the present disclosure.

[0081] As shown in Figure 3, a UE 302 is operably connected with a user plane anchor 304 of a core network via a 5G RAN 306A and a beyond-5G RAN 306B. The UE 302 may include various steering functionalities, such as MPTCP, ATSSS-LL, MPQUIC, and it may use various steering modes for uplink data flow. The user plane anchor 304 may correspondingly include various steering functionalities, such as MPTCP, ATSSS-LL, MPQUIC, and it may use various steering modes for downlink data flow. The UE 302 and the user plane anchor 304 may include traffic steering rules, which may be generated by the control plane of the core network and may dictate how uplink and downlink traffic should be distributed across the 5G RAN 306A and the beyond-5G RAN 306B. In this example, the steering modes may include steering modes defined in the context of ATSSS in 3 GPP, which may include active-standby, priority-based, smallest-delay, load-balancing, and redundant steering. Different steering functionalities and steering modes may be applied by the UE 302 for uplink traffic and by the user plane anchor 304 for downlink traffic.Additional details pertaining to the defined steering modes can be found e.g., in 3 GPP Technical Specifications (TS) 23.501 V19.2.1 (2025-01) (e.g., clause 5.32.8).

[0082] In this example, each steering functionality may apply different steering modes for different traffic flows, such as the traffic flows illustrated in solid lines, dashed lines, and dotted lines.

[0083] In one example, the MPTCP steering functionality may apply the active-standby steering mode for the data traffic flow (app data packets) illustrated in solid lines (e.g., a TCP flow destined to address a.b.c.d), which sends the data traffic of this flow over 5G access (via 5GRAN 306A) only and may fall back to beyond-5G access (via beyond-5G RAN 306B) when the 5G access becomes unavailable.

[0084] In one example, the MPTCP steering functionality may apply the load-balancing steering mode for the data traffic flow (app data packets) illustrated in dashed lines, which splits the app data packets illustrated in dashed lines across both 5G and beyond-5G accesses (via both 5G RAN 306A and beyond-5G RAN 306B). The load-balancing steeringmode (e.g., for the data traffic flow (app data packets) illustrated in dashed lines) can split the packets of a single data flow (e.g., all packets with the same IP 5-tuple) across 5G and beyond-5G accesses. It may do so by applying fixed split percentages (e.g., 20% on 5G access and 80% on beyond-5G access), or by applying dynamic split percentages that may be autonomously and independently determined by the UE 302 and user plane anchor 304 with an intention to maximize the throughput of the uplink and downlink data flows, respectively. The dynamic split percentages may be applied if the network provides, as part of the traffic steering rules, an autonomous load-balance indicator for the data flow. If such an indicator is not provided, the fixed split percentages included in the traffic steering rules may be applied.

[0085] The distribution of data traffic across 5G access and beyond-5G access can be based on traffic steering rules derived by the control plane of the core network when the UE 302 establishes a multi -access (MA) data connection (i.e., MA PDU session), which may include separate access connections over 5G and beyond-5GRANs 306A, 306B between the UE 302 and the user plane anchor 304. The traffic steering rules may be generated based on multi-access control policy configured in the core network (e.g., by the Operations, Administration, and Maintenance (0AM) module).

[0086] An example traffic steering rule that may be provided to the UE 302 may include: (1) rule identity, (2) rule precedence, (3) traffic descriptor, including“com. example. app 1” (such as YouTube®, Netflix®) as application identity, and “TCP” as protocol, (4) access selection descriptor, including “MPTCP” as steering functionality, “load-balancing” as steering mode, “50% over 5G and 50% over beyond-5G” as steering mode information, and “Max Round-Trip-Time (RTT) = 10ms” as threshold value. This example traffic steering rule specifies that the TCP traffic of application “com.example.appl” should be steered using the MPTCP steering functionality using a load-balancing steering mode that must send 50% of the traffic over 5G access and 50% of the traffic over beyond-5G access (fixed split percentages), provided that the RTT of each of these accesses does not exceed 10 ms, and if the RTT of an access exceeds 10ms, then no traffic should be sent on this access.

[0087] Figure 4 illustrates an example signaling flow diagram of operations for supporting network traffic steering function for wireless communication in accordance with aspects of the present disclosure. In this example, the UE has multi-protocol-stack capability (e.g., dual-protocol-stack capability), and it includes a first protocol stack (Stack- 1) and a second protocol stack (Stack-2). The multi -protocol-stack capability (e.g., dual- protocol-stack capability) can be considered as a network traffic steering capability, which allows communication of data via at least the first protocol stack and the second protocol stack, selectively or simultaneously. The first protocol stack and the second protocol stack may each be arranged for communicating data via a respective cellular network connection. The respective cellular network connections may include at least two 3 GPP network connections, e.g., a 5G network connection and a beyond-5G network connection. In this example, the first protocol stack is arranged to communicate with core network 1 (CN1) via random access network 1 (RANI) whereas the second protocol stack is arranged to communicate with core network 2 (CN2) via random access network 2 (RAN2). In this example, the first protocol stack is at least initially designated as a primary stack.

[0088] At 401, the UE powers on and the first protocol stack (primary stack) is activated. The second protocol stack remains in a null state or an inactive state.

[0089] The first protocol stack may initiate a frequency scan (raw / fine). The non-access stratum (NAS) layer of the first protocol stack may provide PLMN / RAT information to the access stratum of the first protocol stack.

[0090] At 402, the first protocol stack performs cell and PLMN selection according to legacy procedures. Additional details pertaining to the procedures can be found, e.g., in 3GPP Technical Specifications (TS) 38.304 VI 8.4.0 (2024-12). The first protocol stack may also perform idle mode tasks such as receiving system information, monitoring paging, cell selection / re-selection, etc.

[0091] At 403, a single or joint registration operation is performed, via the first protocol stack (the second protocol stack remains null or inactive). In one example of the registration operation, the UE, via the first protocol stack, may inform the core network access and mobility management function (CN-AMF) that it has dual protocol stack (or dual steer) capability and is interested to use the network traffic steering function (e.g., dualsteer) feature. The UE may request two different core network identities. In one example, the request of the two different core network identities may be performed with an initiated registration procedure, which could be the initial registration or a periodic registration, by including explicit information in the registration message. In another example, the first protocol stack may initiate a registration procedure at any point after the first protocol stack is registered with the CN-AMF. The request / indication can be made by including capability indication for dual stack capability, e.g., by including one explicit bit for such purpose (e.g., to request two different core network identities).

[0092] In the example in which the request of the two different core network identities is performed with the initiated registration procedure, the core network may initiate an authentication procedure with the first protocol stack. Additional details pertaining to the procedures can be found, e.g., in 3GPP Technical Specifications (TS) 33.501 V19.1.0 (2025-01). Upon successful authentication, the core network may consider the request for two core network identities and may accordingly allocate two core network identities for the UE: one identity for the first protocol stack, which can be used immediately, and another identity for the second protocol stack, which can be used later when needed. A periodic tracking area update / registration procedure from the UE may request the network to keep the second identity alive in the context of the UE.

[0093] In one example, the UE has two universal subscriber identity modules (USIMs) or like identity modules. In this example, the core network, upon receiving the request for two identities (or for the second identity, if the first identity has already been provided) indicating that UE has access to a second USIM, may run a fresh identity request and / or authentication procedure to verify the second USIM. If the second USIM is successfully verified, the core network may allocate the second identity to the UE, as received via the first protocol stack. The first protocol stack may share the second identity with the second protocol stack, as and when need arises. The second USIM credential for authentication could be based on a physical USIM, a UICC, or a distributed ID (DID). In one example, the multiple registrations in the same PLMN procedure, such as that disclosed in 3 GPP Technical Specifications (TS) 33.501 V19.1.0 (2025-01), may be used as a baseline.

[0094] The first protocol stack may request two different core network identities (or the first protocol stack may request a second identity if the first protocol stack has already been registered and has already been provided with a first identity) from the core network.

[0095] Upon receiving the registration request message requesting for a second identity / joint registration for dual steer, the CN-AMF may determine whether the UE is or has been authenticated by the network. To this end, the UE may include its derived core network identity (a temporary version such as short-term mobile subscriber identity (S- TMSI) value) to the core network. The CN-AMF may decide to omit the authentication in case there is available security context for the UE by means of a first core network identity (e.g., GUTI), e.g. when the UE is successfully registered to 3GPP access.

[0096] If the UE registers to the same CN-AMF and indicates it has dual steer capability (or dual protocol stack capability) and requests two different core network identities, the CN-AMF may decide not to run a new authentication if it has an available security context for the UE. In this case, the UE may directly use the available common 5G NAS security context to protect the new registration request for second core network identity. The CN-AMF and the UE may establish a common NAS security context including a single set of NAS keys and algorithm at the time of first registration over any access. The CN-AMF and the UE may also store parameters specific to each NAS connection in the common NAS security context including two pairs of NAS COUNTs for each access (i.e. 3GPP access for two different links).

[0097] In one example, with the successful conclusion of the joint registration procedure, the UE may receive dual steer rules (i.e., traffic steering rules). Additionally, the UE may receive up to two core network identities. The core network, when providing two core network identities, may create a binding of the two core network identities and may ensure that the UE is paged only on the first (primary) core network identity. Additionally, the UE may receive RF, RAT, and / or PLMN suggestion from the network side. The first network (including either or both RAT and CN) may, based on the current location of the UE (cell identity, frequency, and RAT), estimate possible radio cell(s) where the second protocol stack of the UE might be able to camp and establish a second communication link,different from the first communication link, to benefit from diversity, suitable for network traffic steering (dual steer) function.

[0098] In one example, as a result of the successful conclusion of the joint registration procedure or as part of the registration procedure, e.g., for primary authentication (Authentication and Key Agreement (AKA) procedure), the UE and the core network may have derived some of the higher keys in the key hierarchy. The keys may include one or more of: authentication server key (KAUSF), session establishment key (KSEAF), access and mobility management function key (KAMF), narrowband access stratum integrity key (KNASint), narrowband access stratum encryption key (KNASenc), etc. Additional details pertaining to these keys may be found, e.g., in 3GPP Technical Specifications (TS) 33.501 V19.1.0 (2025-01) (e.g., Figure 6.2.1-1). In one example, the first protocol stack may represent the second protocol stack and derive the key(s). The first protocol stack may provide the keys to the second protocol stack, e.g., later, as and when needed.

[0099] The UE capability pertaining to the second protocol stack (or to dual protocol stack) may be requested by the network. In other words, the network may initiate the obtaining of the UE capability pertaining to the second protocol stack (or the dual protocol stack capability of the UE). In one example, the UE may inform the RAN node (e.g., gNB) that the UE has initiated a joint registration for dual steer. To this end, an indication (e.g., an explicit field / establishment cause) can be included in a RRC connection request (Msg3) transmitted via the first protocol stack, or the indication can be included in the RRC connection setup complete message transmitted via the first protocol stack. The RAN node, after receiving the indication from the UE, can transmit a UE capability enquiry to the UE to request or enquire the capability of the second protocol stack or both protocol stacks. In response, the UE may provide the UE capability to the RAN node. The RAN node, upon receiving UE capability, may forward it to the CN-AMF. In another example, the CN-AMF may request the RAN node to obtain the capability of the second protocol stack of the UE. The RAN node, after receiving the request from the CN, may transmit a UE capability enquiry to the UE to request for the capability of the second protocol stack or both protocol stacks. In response, the UE may provide the UE capability to the RAN node. The RAN node, upon receiving UE capability, may forward it to the CN-AMF. In another example,UE capability fetching by the core network may operate in a legacy way, but UE includes capabilities of the second protocol stack or both protocol stacks when responding to the UE capability enquiry from the core network.

[0100] Throughout 401 to 403, the second protocol stack may remain in a null state or an inactive state.

[0101] After the operations in 401 to 403, the dual steer function may be triggered.

[0102] In one example, as part of the triggering, the first protocol stack may be in an RRC idle state and the second protocol stack may be in a null state or an inactive state, and an application may trigger the dual steer function wherein the dual steer rule requires or prefers the use of the second protocol stack.

[0103] In another example, as part of the triggering, the first protocol stack may be in an RRC connected state and the second protocol stack may be in a null state or an inactive state, and an application may trigger the dual steer function wherein the dual steer rule requires or prefers the use of the second protocol stack.

[0104] In some cases, it may be energy inefficient for the UE to keep both protocol stacks active all the time. However, in some cases, it may be useful to be able to activate and use the second protocol stack as soon as possible.

[0105] To this end, in a first example case, the first protocol stack may wake up the second protocol stack and provide radio information to the second protocol stack. The radio information may help to narrows down the frequency search of the second protocol stack to a particular frequency or frequency band. In one example, the radio information may be obtained by the first protocol stack from the broadcast information of the serving cell of the first protocol stack. For example, in a 5G system, the neighbour cell information is broadcasted in SIB3 for intra-frequency neighbours, in SIB4 for inter-frequency neighbours, and in SIB5 for inter-RAT neighbours. Optionally, the first protocol stack may include, in the radio information provided to the second protocol stack, only those candidates (PCIs, frequency, and RAT) that are good from radio perspective, i.e., have good radio strength (received signal strength indicator (RS SI), reference signal received power (RSRP), and / or reference signal received quality (RSRQ)) measured onsynchronizing signal block (SSB) or any other reference signal (RS) transmission. In another example, the radio information may be obtained by the first protocol stack from the network (e.g., the CN-AMF and / or the RAN node). Optionally, the first protocol stack may include, in the radio information provided to the second protocol stack, only those candidates (PCIs, frequency, and RAT) that are good from radio perspective i.e., have good radio strength (RS SI, RSRP and / or RSRQ) measured on SSB or any other RS transmission.

[0106] The first protocol stack may wake up the second protocol stack and provide the radio information to the second protocol stack only when the upper layers provides an indication to do so (e.g., at application trigger or when the upper layers request activation of the second protocol stack for obtaining statistical values such as RTT, error rate, etc.).

[0107] In a second example case, the first protocol stack may wake up the second protocol stack and provide the radio information to the second protocol stack same as in the first example case. However, in this second example case, the first protocol stack does not wait for the second protocol stack to become activated and operational (i.e., fully active). Instead, the UE starts a new application on the first protocol stack and, when the second protocol stack is fully active (camped, and optionally RRC connection established with its serving network), the dual steer rules (e.g., at IP layer) may shift the data traffic (access traffic shifting) to the second protocol stack. The first protocol stack for the triggering application / purpose is no longer used. For example, when the second protocol stack is camped, it provides an indication to the first protocol stack internally and a MA PDU session request may be initiated from the first protocol stack or the second protocol stack.

[0108] Since the second protocol stack has already been registered (based on the registration procedure discussed with respect to operations 403), the second protocol stack has been authenticated, and it may also have derived the security keys. Thus, with the help of radio information received from the first protocol stack, data transmission on the second 3 GPP access link (via the second protocol stack) may start relatively quickly.

[0109] Turning back to Figure 4 for an example of the dual steer triggering.

[0110] At 404, the first protocol stack initiates a RRC connection establishment procedure. The UE transmits, via the first protocol stack, an RRC connection establishmentrequest to its serving RAN node RANI. The RRC connection request may include information associated with the dual steer capability (or dual protocol stack capability) of the UE. The information may be referred to as dual steer information (DS info.). For example, the information may include an indication that the UE has dual steer capability (or dual protocol stack capability). For example, the information may include one or more of: information indicating that the UE has dual protocol stack capability (dual steer capability); information indicating availability of one or two USIMs in the UE; core network (AMF) information of the first protocol stack (e.g., registered AMF, mobile network identity information (such as selected PLMN-identity, S-TMSI value, or like identity information)); radio information for the second protocol stack, if available, (e.g., if the second protocol stack is already camped and therefore has a cell (PCI), frequency and RAT information to provide); and information indicating availability of one or more core network identities of the UE (e.g., [0, 1 or 2], depending on whether registration has been performed). Both core network identities may be indicated for periodic or (re)registration cases.

[0111] In one example, the information associated with the dual steer capability (or dual protocol stack capability) of the UE (DS info.) may be transmitted to RAN node RANI at any time after the RRC connection establishment procedure, as and when the second protocol stack needs to be used.

[0112] At 405, RAN node RANI in turn transmits a next generation application protocol (NGAP) setup request to CN1. The NGAP setup request may include the information associated with the dual steer capability (or dual protocol stack capability) of the UE received from the UE.

[0113] At 406, the network (CN1 and / or RAN node RANI) in response provides dual steer assistance information to the UE, via the first protocol stack. The dual steer assistance information may include radio information and core network information. The radio information and the core network information includes information for the second protocol stack. The radio information for the second protocol stack may include, e.g., cell (PCI), frequency, and RAT information. The core network information for the second protocol stack may include, e.g., registered AMF and / or mobile network identity information (such as selected PLMN-identity, S-TMSI value, or like identity information).

[0114] At 407, the first protocol stack provides the received dual steer assistance information, in particular the received radio information for the second protocol stack, to the second protocol stack.

[0115] At 408, the second protocol stack provides a camped response or indication to the first protocol stack.

[0116] At 409, the first protocol stack provides the received dual steer assistance information, in particular the received core network information for the second protocol stack, to the second protocol stack. The first protocol stack may further provide one or both core network identities to the second protocol stack.

[0117] At 410, the second protocol stack initiates a RRC connection establishment procedure. The UE transmits, via the second protocol stack, an RRC connection establishment request to its serving RAN node RAN2. The RRC connection request may include an establishment cause “dual steer”. In subsequent messages, e.g., in Msg5, the UE may provide the core network information and one or both core network identities of the UE. A Multi Access (MA) PDU session request may be further included in the Msg5.

[0118] RAN2 may, based on the received information, locate or identify the corresponding CN-AMF. At 411, RAN2 initiates NGAP establishment and forwards the non-access stratum (NAS) message, including the MA PDU session request, to the CN- AMF.

[0119] In one example, at 412, the first protocol stack may initiate MA PDU session establishment procedure, e.g., around the time of activating the second protocol stack. The CN-AMF nodes (e.g., of CN1, CN2) may exchange information to validate the request and, at 413, may transmit a MA PDU session acceptance message to the UE via the first protocol stack.

[0120] At 414, a dual steer session is enabled and established.

[0121] It should be noted that the example of Figure 4 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. For example, the UE in theexample of Figure 4 may be any multi -protocol-stack device, not necessarily a dual- protocol-stack device. For example, the example of Figure 4 may optionally be implemented at least in part using the system illustrated in Figure 2 or Figure 3. For example, the operations in 404 to 406 may be combined with the operations in 403. For example, the operations in 407 and 409 may be combined, or may be performed in a different order than illustrated. For example, the MA PDU session establishment procedure may be initiated via the second protocol stack and the operations 412 and 413 may be omitted.

[0122] In some example implementations, the ATSSS framework may be used for creating two 3 GPP accesses / links, which results in a dual steer protocol. In some example implementations, only one protocol stack may be active as far as possible, and so the implementation of the dual steer may have reduced power consumption. In some example implementations, the second protocol stack may become activated and operational relatively quickly. This may be due to one or more of: the sharing of radio information from an active protocol stack to a not yet fully active protocol stack; the performing of preliminary measurements by the first protocol stack on behalf of the second protocol stack; the performing of a joint registration procedure, which saves time for registering and authenticating the second protocol stack; the derivation of security keys for the second protocol stack before it is fully active; the definition of new establishment cause and core network information, which may provide quicker access at air-interface and core network context creation / maintenance; etc.

[0123] Figure 5 illustrates an example signaling flow diagram of operations for supporting network traffic steering function for wireless communication in accordance with aspects of the present disclosure. In this example, the UE has multi-protocol-stack capability (e.g., dual-protocol-stack capability), and it includes a first protocol stack (Stack- 1) and a second protocol stack (Stack-2). The multi -protocol-stack capability (e.g., dual- protocol-stack capability) can be considered as a network traffic steering capability, which allows communication of data via at least the first protocol stack and the second protocol stack, selectively or simultaneously. The first protocol stack and the second protocol stack may each be arranged for communicating data via a respective cellular network connection.The respective cellular network connections may include at least two 3 GPP network connections, e.g., a 5G network connection and a beyond-5G network connection. In this example, the first protocol stack is arranged to communicate with core network 1 (CN1) via random access network 1 (RANI) whereas the second protocol stack is arranged to communicate with core network 2 (CN2) via random access network 2 (RAN2). In this example, the first protocol stack is at least initially designated as a primary stack.

[0124] The example signaling flow diagram in Figure 5 may be considered as a continuation of the signaling flow diagram of Figure 4.

[0125] At 501, a dual steer session is enabled and established. In one example, 501 may correspond to 414 in Figure 4.

[0126] In some cases, for the network traffic steering function, switching of dual steer link or tearing down of one of the dual steer links may be required.

[0127] At 502, based on the dual steer rules, an application (APP) operating on the IP layer may decide to use another link (associated with another protocol stack) due to a change in the radio condition(s), which can be determined based on measurements associated with the operation of the application, e.g., the packet error, retransmission rate, or transmission delay etc. Additionally or alternatively, the application operating on the IP layer may stop operation. If the application is the only application running on the first link, then the first link may be torn down using legacy NAS and RRC release procedure. This may result in a mobility situation, in which the UE transits from using the first link (associated with the first protocol stack) to using the second link (associated with the second protocol stack) without requiring the lower layer mobility procedure. In one example, for maintenance of each link, the lower layer based RRC connected mobility handover procedure may still be used transparently to lower layer.

[0128] At 503, the UE transmits, via the second protocol stack, to CN2, an indication to release the first protocol stack (to cease using the first link).

[0129] At 504, the CN-AMF nodes (e.g., of CN1, CN2) may exchange information for releasing the first protocol stack.

[0130] At 505, CN1 transmits to RAN node RANI information (approval or instruction) for releasing the first protocol stack.

[0131] At 506, the RAN node RANI in turn provides the stack / RRC connection release approval or instruction to the UE via the first protocol stack, to release the first protocol stack.

[0132] Once released, the first protocol stack may enter into a NULL state and not to RRC idle or inactive state. This means that the serving network of the second protocol stack may provide the signaling connection and coverage to the UE. The first protocol stack may be subsequently activated or reactivated, and it may serve a new application or the application running on the second link (associated with the second protocol stack) may be switched to the first link (associated with the first protocol stack).

[0133] It should be noted that the example of Figure 5 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. For example, the example of Figure 5 may optionally be implemented at least in part using the system illustrated in Figure 2 or Figure 3. For example, the example of Figure 5 may be modified to implement the release of the second protocol stack.

[0134] Figure 6 illustrates an example signaling flow diagram of operations for supporting network traffic steering function for wireless communication in accordance with aspects of the present disclosure. In this example, the UE has multi-protocol-stack capability and it includes two or more protocol stacks. The multi-protocol-stack capability can be considered as a network traffic steering capability. The protocol stacks may each be arranged for communicating data via a respective cellular network connection. The respective cellular network connections may include 3GPP network connections. In this example, the UE is arranged to communicate with the core network, in particular the security anchor function (SEAF) and / or the access & mobility management function (AMF).

[0135] At 601, the UE transmits a registration request to the SEAF / AMF of the core network. The registration request may be a request to register one or more (N, can be anyinteger) protocol stacks with the core network. The registration request may include information associated with the multi-protocol-stack capability of the UE and / or information associated with the network traffic steering function. The information associated with the multi -protocol-stack capability of the UE may include, e.g., information indicating that the UE has multi-protocol-stack capability, information indicating that the UE comprises a particular protocol stack, information requesting an identity for at least the second protocol stack.

[0136] SEAF / AMF of the core network, after receiving the registration request, may determine that authentication of the UE or the protocol stack(s) or associated identity module(s) of the UE may be required. At 602, the SEAF / AMF of the core network transmits an authentication request to the UE.

[0137] At 603, the UE transmits an authentication response containing credential information for authenticating the UE or the protocol stack(s) or associated identity module(s) of the UE to the SEAF / AMF of the core network.

[0138] After successful authentication, at 604, the SEAF / AMF of the core network transmits a registration acceptance indication to the UE. The registration acceptance indication includes one or more core network identities (core network IDs) for the protocol stack(s) or their associated identity module(s).

[0139] It should be noted that the example of Figure 6 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. For example, the example of Figure 6 may optionally be implemented at least in part using the system illustrated in Figure 2 or Figure 3. For example, operations 602 and 603 may be omitted.

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

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

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

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

[0144] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the UE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the UE 700 in accordance with examples as disclosed herein.

[0145] The UE 700 may be configured to support one or more means for transmitting, via a first protocol stack of the UE 700, a first information associated with a multi-protocol- stack capability of the UE 700 for enabling a network traffic steering function, and receiving, via the first protocol stack, a second information for enabling the network traffic steering function. The UE 700 is capable of receiving or transmitting data via one or both of the first protocol stack and a second protocol stack of the UE 700 based at least in part on the multi-protocol-stack capability of the UE 700. The network traffic steering function may enable communication of data via one or both of the first protocol stack and the second protocol stack of the UE 700. The multi-protocol-stack capability may be a dual-protocol- stack capability. The multi-protocol-stack capability can be considered as a network traffic steering capability. The network traffic steering function may be a dual steer function. The network traffic steering function may allow communication of data via at least the first protocol stack and the second protocol stack, selectively or simultaneously. The first protocol stack and the second protocol stack may each be arranged for communicating data via a respective cellular network connection. For example, the first protocol stack may be arranged for communicating data via a first 3GPP connection (e.g., 5G connection) and the second protocol stack may be arranged for communicating data via a second 3 GPP connection (e.g., beyond-5G (e.g., 6G) connection). For example, the first protocol stack may be arranged for communicating data via a first beyond-5G connection and the second protocol stack may be arranged for communicating data via a second beyond-5G connection. In one example, the second protocol stack maybe in a null state or an inactive state during and between transmission of the first information and reception of the second information. In one example, the second protocol stack maybe in a null state or an inactive state until transmission of the first information or reception of the second information. The first information may indicate that the UE 700 has multi-protocol-stack capability. For example, the first information may include: an indicator (e.g., one or more bits) indicating that the UE 700 has multi-protocol-stack capability, information indicating that the UE 700 includes the second protocol stack, etc. Additionally or alternatively, the first information may indicate a request for an identity for at least the second protocol stack. The second information may include one or more of: a core network identity for the first protocol stack; a core network identity for the second protocol stack; one or more network traffic steeringrules for the first protocol stack and the second protocol stack; one or more radio frequencies (RFs), one or more radio access technologies (RATs), or one or more public land mobile networks (PLMNs) for wireless communication via the second protocol stack; or one or more candidate cells suitable for wireless communication via the second protocol stack.

[0146] The UE 700 may be configured to support one or more means for, in response to transmission of the first information and prior to reception of the second information: receiving, via the first protocol stack, a request message to authenticate the UE 700, and transmitting, via the first protocol stack, a response message comprising credential information for authenticating the UE 700. The UE 700 may include a plurality of identity modules each associated with a respective protocol stack of the UE 700. The UE 700 may be configured to support one or more means for, in response to transmission of the first information and prior to reception of the second information: receiving a request message to authenticate a first identity module associated with the first protocol stack or a second identity module associated with the second protocol stack, and transmitting a response message comprising one or more of a first credential information of the first identity module or a second credential information of the second identity module.

[0147] The UE 700 may be configured to support one or more means for obtaining (e.g., deriving) one or more keys for encryption, integrity protection, authentication, or privacy for the second protocol stack, and providing the one or more keys to the second protocol stack for encryption, integrity protection, authentication, or privacy at the second protocol stack. The UE 700 may be configured to support one or more means for outputting the second information to the second protocol stack for use by the second protocol stack to enable the network traffic steering function.

[0148] The UE 700 may be configured to support one or more means for initiating, at the first protocol stack, a first radio resource control (RRC) connection establishment procedure; transmitting via the first protocol stack, information associated with the network traffic steering function; and receiving, via the first protocol stack, network traffic steering assistance information comprising radio information for the second protocol stack and core network information for the second protocol stack. The first information may comprise theinformation associated with the network traffic steering function. For example, the transmission of the information associated with the network traffic steering function may be part of the transmission of the first information. The second information may comprise the network traffic steering assistance information. For example, the reception of the network traffic steering assistance information may be part of the reception of the second information. The information associated with the network traffic steering function may include one or more of: an indication that the UE 700 has multi-protocol-stack capability; an indication of whether one or more identity modules of the UE 700 are available; core network information associated with the first protocol stack, which may include one or more of: registered AMF related information (e.g., registered AMF associated with the first protocol stack)or mobile network identity related information associated with the first protocol stack (e.g., PLMN identity, short-term mobile subscriber identity (S-TMSI), or like identity information associated with the first protocol stack); a physical cell identity (PCI), a radio frequency (RF), or a radio access technology (RAT) associated with the second protocol stack; or an indication of availability of one or more core network identities of the UE 700.

[0149] The radio information for the second protocol stack may include information associated with PCI, RF, and / or RAT for the second protocol stack (such as a PCI, a RF, or a RAT for the second protocol stack). The UE 700 may be configured to support one or more means for filtering the radio information for the second protocol stack based on one or more signal qualities associated with one or more received radio signals. The one or more received radio signals are based on the information associated with the PCI, the RF, and / or the RAT in the radio information for the second protocol stack. The core network information for the second protocol stack may include AMF related information (e.g., AMF for the second protocol stack) and / or mobile network identity related information (e.g., PLMN identity, S-TMSI, or like identity information for the second protocol stack).

[0150] The UE 700 may be configured to support one or more means for receiving an indication to activate the second protocol stack; and providing, to the second protocol stack, at least, a core network identity for the second protocol stack, the radio information for the second protocol stack, and the core network information for the second protocol stack. Theindication to activate the second protocol stack may be based at least in part on an application associated with the UE 700 requiring the network traffic steering function. The UE 700 may be configured to support one or more means for initializing activation of the second protocol stack.

[0151] The UE 700 may be configured to support one or more means for initiating, at the second protocol stack, a second RRC connection establishment procedure based on the core network identity for the second protocol stack, the radio information for the second protocol stack, and the core network information for the second protocol stack.

[0152] The UE 700 may be configured to support one or more means for initiating establishment of a multi-access protocol data unit (PDU) session for communicating data using at least the first protocol stack and the second protocol stack.

[0153] The UE 700 may be configured to support one or more means for switching the first protocol stack to a null state or an inactive state after activation of the second protocol stack.

[0154] The controller 706 may manage input and output signals for the UE 700. The controller 706 may also manage peripherals not integrated into the UE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.

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

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

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

[0158] Figure 8 illustrates an example of a processor 800 in accordance with aspects of the present disclosure. The processor 800 may support a network traffic steering function for wireless communication in accordance with aspects of the present disclosure. The processor 800 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 800 may include a controller 802 configured to perform various operations in accordance with examples as described herein. The processor 800 may optionally include at least one memory 804, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 800 may optionally include one or more arithmetic-logic units (ALUs) 806. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

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

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

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

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

[0163] The memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 800, cause the processor 800 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 802 and / or the processor 800 may be configured to execute computer-readable instructions stored in the memory 804 to cause the processor 800 to perform various functions. For example, the processor 800 and / or the controller 802 may be coupled with or to the memory 804, the processor 800, the controller 802, and the memory 804 may be configured to perform various functions described herein. In some examples, the processor 800 may include multiple processors and the memory 804 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.

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

[0165] The processor 800 may support wireless communication in accordance with examples as disclosed herein.

[0166] The processor 800 may be configured to or operable to transmit, via a first protocol stack of a UE, a first information associated with a multi-protocol-stack capability of the UE for enabling a network traffic steering function, and receive, via the first protocol stack, a second information for enabling the network traffic steering function. The UE is capable of receiving or transmitting data via one or both of the first protocol stack and a second protocol stack of the UE based at least in part on the multi-protocol-stack capability of the UE. The network traffic steering function may enable communication of data via one or both of the first protocol stack and the second protocol stack of the UE. The multi- protocol-stack capability may be a dual-protocol-stack capability. The multi-protocol-stack capability can be considered as a network traffic steering capability. The network traffic steering function may be a dual steer function. The network traffic steering function may allow communication of data via at least the first protocol stack and the second protocol stack, selectively or simultaneously. The first protocol stack and the second protocol stack may each be arranged for communicating data via a respective cellular network connection. For example, the first protocol stack may be arranged for communicating data via a 5G connection and the second protocol stack may be arranged for communicating data via a beyond-5G (e.g., 6G) connection. For example, the first protocol stack may be arranged for communicating data via a first beyond-5G connection and the second protocol stack may be arranged for communicating data via a second beyond-5G connection. In one example, the second protocol stack maybe in a null state or an inactive state during and between transmission of the first information and reception of the second information. In one example, the second protocol stack maybe in a null state or an inactive state until transmission of the first information or reception of the second information. The first information may indicate that the UE has multi -protocol-stack capability. For example, the first information may include: an indicator (e.g., one or more bits) indicating that the UE has multi-protocol-stack capability, information indicating that the UE includes the second protocol stack, etc. Additionally or alternatively, the first information may indicate a request for an identity for at least the second protocol stack. The second information may include one or more of: a core network identity for the first protocol stack; a core network identity for the second protocol stack; one or more network traffic steering rules for the first protocol stack and the second protocol stack; one or more radio frequencies (RFs), one ormore radio access technologies (RATs), or one or more public land mobile networks (PLMNs) for wireless communication via the second protocol stack; or one or more candidate cells suitable for wireless communication via the second protocol stack.

[0167] The processor 800 may be configured to or operable to support one or more means for, in response to transmission of the first information and prior to reception of the second information: receiving, via the first protocol stack, a request message to authenticate the UE, and transmitting, via the first protocol stack, a response message comprising credential information for authenticating the UE. The UE may include a plurality of identity modules each associated with a respective protocol stack of the UE. The processor 800 may be configured to or operable to support one or more means for, in response to transmission of the first information and prior to reception of the second information: receiving a request message to authenticate a first identity module associated with the first protocol stack or a second identity module associated with the second protocol stack, and transmitting a response message comprising one or more of a first credential information of the first identity module or a second credential information of the second identity module.

[0168] The processor 800 may be configured to or operable to obtain (e.g., deriving) one or more keys for encryption, integrity protection, authentication, or privacy for the second protocol stack, and provide the one or more keys to the second protocol stack for encryption, integrity protection, authentication, or privacy at the second protocol stack. The processor 800 may be configured to or operable to output the second information to the second protocol stack for use by the second protocol stack to enable the network traffic steering function.

[0169] The processor 800 may be configured to or operable to initiate, at the first protocol stack, a first RRC connection establishment procedure; transmit, via the first protocol stack, information associated with the network traffic steering function; and receive, via the first protocol stack, network traffic steering assistance information comprising radio information for the second protocol stack and core network information for the second protocol stack. The first information may comprise the information associated with the network traffic steering function. For example, the transmission of the information associated with the network traffic steering function may be part of thetransmission of the first information. The second information may comprise the network traffic steering assistance information. For example, the reception of the network traffic steering assistance information may be part of the reception of the second information. The information associated with the network traffic steering function may include one or more of: an indication that the UE has multi-protocol-stack capability; an indication of whether one or more identity modules of the UE are available; core network information associated with the first protocol stack, which may include one or more of: registered AMF related information (e.g., registered AMF associated with the first protocol stack) or mobile network identity related information associated with the first protocol stack (e.g., PLMN identity, S-TMSI, or like identity information associated with the first protocol stack); a PCI, a RF, or a RAT associated with the second protocol stack; or an indication of availability of one or more core network identities of the UE.

[0170] The radio information for the second protocol stack may include information associated with PCI, RF, and / or RAT for the second protocol stack (such as a PCI, a RF, or a RAT for the second protocol stack). The processor 800 may be configured to or operable to filter the radio information for the second protocol stack based on one or more signal qualities associated with one or more received radio signals. The one or more received radio signals are based on the information associated with the PCI, the RF, and / or the RAT in the radio information for the second protocol stack. The core network information for the second protocol stack may include AMF related information (e.g., AMF for the second protocol stack) and / or mobile network identity related information (e.g., PLMN identity, S- TMSI, or like identity information for the second protocol stack).

[0171] The processor 800 may be configured to or operable to receive an indication to activate the second protocol stack; and provide, to the second protocol stack, at least, a core network identity for the second protocol stack, the radio information for the second protocol stack, and the core network information for the second protocol stack. The indication to activate the second protocol stack may be based at least in part on an application associated with the UE requiring the network traffic steering function. The processor 800 may be configured to or operable to initialize activation of the second protocol stack.

[0172] The processor 800 may be configured to or operable to initiate, at the second protocol stack, a second RRC connection establishment procedure based on the core network identity for the second protocol stack, the radio information for the second protocol stack, and the core network information for the second protocol stack.

[0173] The processor 800 may be configured to or operable to initiate establishment of a multi-access PDU session for communicating data using at least the first protocol stack and the second protocol stack.

[0174] The processor 800 may be configured to or operable to switch the first protocol stack to a null state or an inactive state after activation of the second protocol stack.

[0175] Figure 9 illustrates an example of a NE 900 in accordance with aspects of the present disclosure. The NE 900 may support a network traffic steering function for wireless communication in accordance with aspects of the present disclosure. The NE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0176] The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting one or more means for performing the functions described in the present disclosure.

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

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

[0179] In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured to cause the NE 900 to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904). For example, the processor 902 may support wireless communication at the NE 900 in accordance with examples as disclosed herein.

[0180] The NE 900 may be configured to support one or more means for receiving a first information associated with a multi-protocol-stack capability of a UE for enabling a network traffic steering function, and transmitting a second information for enabling the network traffic steering function. The UE is capable of receiving or transmitting data via one or both of a first protocol stack and a second protocol stack of the UE based at least in part on the multi-protocol-stack capability of the UE. The network traffic steering function may enable communication of data via one or both of the first protocol stack and the second protocol stack. The multi-protocol-stack capability may be a dual-protocol-stack capability. The multi-protocol-stack capability can be considered as a network traffic steering capability. The network traffic steering function may be a dual steer function. The network traffic steering function may allow communication of data via at least the first protocol stack and the second protocol stack of the UE, selectively or simultaneously. The first protocol stack and the second protocol stack may each be arranged for communicating data via a respective cellular network connection. The first information may indicate that the UEhas multi-protocol-stack capability. For example, the first information may include: an indicator (e.g., one or more bits) indicating that the UE has multi-protocol-stack capability, information indicating that the UE includes the second protocol stack, etc. Additionally or alternatively, the first information may indicate a request for an identity for at least the second protocol stack. The second information may include one or more of: a core network identity for the first protocol stack; a core network identity for the second protocol stack; one or more network traffic steering rules for the first protocol stack and the second protocol stack; one or more radio frequencies (RFs), one or more radio access technologies (RATs), or one or more public land mobile networks (PLMNs) for wireless communication via the second protocol stack; or one or more candidate cells suitable for wireless communication via the second protocol stack.

[0181] The controller 906 may manage input and output signals for the NE 900. The controller 906 may also manage peripherals not integrated into the NE 900. In some implementations, the controller 906 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 906 may be implemented as part of the processor 902.

[0182] In some implementations, the NE 900 may include at least one transceiver 908. In some other implementations, the NE 900 may have more than one transceiver 908. The transceiver 908 may represent a wireless transceiver. The transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or a combination thereof.

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

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

[0185] Figure 10 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The method may support network traffic steering function for wireless communication in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.

[0186] At 1002, the method may include transmitting, via a first protocol stack of a UE, a first information associated with a multi-protocol-stack capability of the UE for enabling a network traffic steering function. The UE is capable of receiving or transmitting data via one or both of the first protocol stack and a second protocol stack of the UE based at least in part on the multi-protocol-stack capability of the UE. The network traffic steering function may enable communication of data via one or both of the first protocol stack and the second protocol stack of the UE. The multi-protocol-stack capability may be a dual- protocol-stack capability. The multi-protocol-stack capability can be considered as a network traffic steering capability. The network traffic steering function may be a dual steer function. The network traffic steering function may allow communication of data via at least the first protocol stack and the second protocol stack, selectively or simultaneously. The first protocol stack and the second protocol stack may each be arranged for communicating data via a respective cellular network connection. For example, the first protocol stack may be arranged for communicating data via a 5G connection and the secondprotocol stack may be arranged for communicating data via a beyond-5G (e.g., 6G) connection. For example, the first protocol stack may be arranged for communicating data via a first beyond-5G connection and the second protocol stack may be arranged for communicating data via a second beyond-5G connection. The first information may indicate that the UE has multi-protocol-stack capability. For example, the first information may include: an indicator (e.g., one or more bits) indicating that the UE has multi-protocol- stack capability, information indicating that the UE includes the second protocol stack, etc. Additionally or alternatively, the first information may indicate a request for an identity for at least the second protocol stack. For example, the second protocol stack maybe in a null state or an inactive state at least during the transmission of the first information. For example, the second protocol stack maybe in a null state or an inactive state until the transmission of the first information. The operation(s) of 1002 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1002 may be performed by a UE 700 as described with reference to Figure 7 or a processor 800 as described with reference to Figure 8.

[0187] At 1004, the method may include receiving, via the first protocol stack, a second information for enabling the network traffic steering function. The second information may include one or more of: a core network identity for the first protocol stack; a core network identity for the second protocol stack; one or more network traffic steering rules for the first protocol stack and the second protocol stack; one or more radio frequencies (RFs), one or more radio access technologies (RATs), or one or more public land mobile networks (PLMNs) for wireless communication via the second protocol stack; or one or more candidate cells suitable for wireless communication via the second protocol stack. For example, the second protocol stack maybe in a null state or an inactive state at least during the reception of the second information. For example, the second protocol stack maybe in a null state or an inactive state until the reception of the second information. The second information may be provided, e.g., subsequently, to the second protocol stack to enable the network traffic steering function. The operation(s) of 1004 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1004 may be performed by a UE 700 as described with reference to Figure 7 or a processor 800 as described with reference to Figure 8.

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

[0189] Figure 11 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The method may support network traffic steering function for wireless communication in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0190] At 1102, the method may include receiving a first information associated with a multi-protocol-stack capability of a UE for enabling a network traffic steering function. The UE is capable of receiving or transmitting data via one or both of a first protocol stack and a second protocol stack of the UE based at least in part on the multi-protocol-stack capability of the UE. The network traffic steering function may enable communication of data via one or both of the first protocol stack and the second protocol stack of the UE. The multi-protocol-stack capability may be a dual-protocol-stack capability. The multi- protocol-stack capability can be considered as a network traffic steering capability. The network traffic steering function may be a dual steer function. The network traffic steering function may allow communication of data via at least the first protocol stack and the second protocol stack, selectively or simultaneously. The first protocol stack and the second protocol stack may each be arranged for communicating data via a respective cellular network connection. For example, the first protocol stack may be arranged for communicating data via a 5G connection and the second protocol stack may be arranged for communicating data via a beyond-5G (e.g., 6G) connection. For example, the first protocol stack may be arranged for communicating data via a first beyond-5G connection and the second protocol stack may be arranged for communicating data via a second beyond-5G connection. The first information may indicate that the UE has multi-protocol-stack capability. For example, the first information may include: an indicator (e.g., one or more bits) indicating that the UE has multi-protocol-stack capability, information indicating that the UE includes the second protocol stack, etc. Additionally or alternatively, the firstinformation may indicate a request for an identity for at least the second protocol stack. The operation(s) of 1102 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1104 may be performed by a NE 900 as described with reference to Figure 9.

[0191] At 1104, the method may include transmitting a second information for enabling the network traffic steering function. The second information may include one or more of: a core network identity for the first protocol stack; a core network identity for the second protocol stack; one or more network traffic steering rules for the first protocol stack and the second protocol stack; one or more radio frequencies (RFs), one or more radio access technologies (RATs), or one or more public land mobile networks (PLMNs) for wireless communication via the second protocol stack; or one or more candidate cells suitable for wireless communication via the second protocol stack. The operation(s) of 1104 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1104 may be performed by a NE 900 as described with reference to Figure 9.

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

[0193] Figure 12 illustrates an example for supporting network traffic steering function for wireless communication in accordance with aspects of the present disclosure.

[0194] At 1202, registration of a UE, which has capability to enable a network traffic steering function for communicating data via one or both of a first protocol stack and a second protocol stack of the UE, is performed. The UE is capable of receiving or transmitting data via one or both of the first protocol stack and the second protocol stack of the UE based at least in part on a multi-protocol-stack capability of the UE. The registration may be performed by, at least, the UE (via the first protocol stack and while the second protocol stack is in a null state or an inactive state) and a network entity (network equipment such as a base station). The registration may be performed by the UE, the network entity, and a core network. The network traffic steering function may be a dual steer function. The network traffic steering function may allow communication of data viaat least the first protocol stack and the second protocol stack, selectively or simultaneously. The first protocol stack and the second protocol stack may each be arranged for communicating data via a respective cellular network connection. The respective cellular network connections may include at least two 3 GPP network connections, e.g., at least one 5G network connection and at least one beyond-5G network connection, or at least two beyond-5G network connections. The operation(s) of 1202 may be performed in accordance with examples as described herein.

[0195] At 1204, triggering of the network traffic steering function occurs. As a result of the triggering of the network traffic steering function, the second protocol stack may be activated and operated, e.g., based on information for enabling the network traffic steering function, which has been obtained via the first protocol stack (e.g., while the second protocol stack is in a null state or an inactive state). The operation(s) of 1204 may be performed in accordance with examples as described herein.

[0196] It should be noted that the example of Figure 12 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0197] Figure 13 illustrates an example for supporting network traffic steering function for wireless communication in accordance with aspects of the present disclosure. In this example, the UE has multi -protocol-stack capability (e.g., dual-protocol-stack capability), and it includes at least a first protocol stack and a second protocol stack. In the example of Figure 13, the first protocol stack is in an active state and the second protocol stack is in a null state or an inactive state.

[0198] At 1302, the UE transmits via the first protocol stack (active), and the NE correspondingly receives, information associated with the multi-protocol-stack capability of the UE for enabling a network traffic steering function. The UE is capable of receiving or transmitting data via one or both of the first protocol stack and the second protocol stack of the UE based at least in part on a multi-protocol-stack capability of the UE. The network traffic steering function may enable communication of data via one or both of the first protocol stack and a second protocol stack of the UE. For example, the network traffic steering function may allow communication of data via one or both of the first protocolstack and the second protocol stack, selectively or simultaneously. The first protocol stack and the second protocol stack may each be arranged for communicating data via a respective cellular network connection. The respective cellular network connections may include at least two 3 GPP network connections, e.g., a 5G network connection and a beyond-5G network connection. The information associated with the multi-protocol-stack capability of the UE may include information indicating that the UE has multi-protocol- stack capability, which may include an indicator (e.g., one or more bits) indicating that the UE has multi-protocol-stack capability, information indicating that the UE comprises one or more additional protocol stacks (e.g., the second protocol stack), etc. Additionally or alternatively, the information associated with the multi-protocol-stack capability of the UE may include information requesting an identity for at least the second protocol stack. The operation(s) of 1302 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1302 associated with the UE may be performed by a UE 700 as described with reference to Figure 7 and aspects of the operation(s) of 1302 associated with the NE may be performed by a NE 900 as described with reference to Figure 9.

[0199] At 1304, an authentication operation is performed at least by the UE and the NE. For example, the NE may transmit (e.g., based on information received from core network), and the UE may correspondingly receive via the first protocol stack (active), an authentication request to authenticate the UE. In response, the UE may transmit via the first protocol stack (active), and the NE may correspondingly receive, a response comprising credential information for authenticating the UE. The NE may provide the response or the credential information to the core network for authentication. In an example in which the UE includes multiple identity modules (e.g., universal subscriber identity module (USIM), universal integrated circuit card (UICC), distributed ID (DID), etc.) each associated with a respective protocol stack, the NE may transmit (e.g., based on information received from a core network), and the UE may correspondingly receive via the first protocol stack (active), an authentication request to authenticate a first identity module associated with the first protocol stack and / or a second identity module associated with the second protocol stack. In response, the UE may transmit via the first protocol stack (active), and the NE may correspondingly receive, credential information of the first identity module and / orcredential information of the second identity module. The NE may provide the credential information to the core network for authentication. The operation(s) of 1304 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1304 associated with the UE may be performed by a UE 700 as described with reference to Figure 7 and aspects of the operation(s) of 1304 associated with the NE may be performed by a NE 900 as described with reference to Figure 9.

[0200] At 1306, after successful authentication at 1304, the NE transmits, and the UE correspondingly receives via the first protocol stack (active), information for enabling the network traffic steering function. The information for enabling the network traffic steering function may be generated by the NE and / or by the core network (i.e., the core network may provide the information to the NE). The information for enabling the network traffic steering function may include a core network identity for the second protocol stack, and optionally a core network identity for the first protocol stack. Additionally or alternatively, the information for enabling the network traffic steering function may include one or more network traffic steering rules for communicating data via the first protocol stack and the second protocol stack, which govern the conditions for communicating via the first protocol stack and the second protocol stack. Additionally or alternatively, the information for enabling the network traffic steering function may include information associated with radio frequency, RAT, and / or public land mobile network (PLMN) suggested for use by the second protocol stack. Additionally or alternatively, the information for enabling the network traffic steering function may include information associated with one or more radio cells that may be suitable for use by the second protocol stack. The information for enabling the network traffic steering function may be provided to the second protocol stack for use by the second protocol stack to enable the network traffic steering function, e.g., if the enabling of network traffic steering function is triggered. The operation(s) of 1306 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1306 associated with the UE may be performed by a UE 700 as described with reference to Figure 7 and aspects of the operation(s) of 1306 associated with the NE may be performed by a NE 900 as described with reference to Figure 9.

[0201] As part of the operation(s) of 1304 and / or 1306, the NE may obtain (e.g., derive) keys for encryption, integrity protection, authentication, and / or privacy for the first protocol stack and the second protocol stack. These keys may be used by the second protocol stack, e.g., for enabling of network traffic steering function. These keys may be provided to the second protocol stack for use by the second protocol stack to enable the network traffic steering function, e.g., if the enabling of network traffic steering function is triggered.

[0202] It should be noted that the example of Figure 13 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. In one example, the operations 1302 and 1306 of Figure 13 may relate to a registration process for registering the UE which has capability to enable the network traffic steering function with the core network. In one example, the authentication operations in 1304 may be omitted. In one example, the UE in the example of Figure 13 performs the method of Figure 10; and the NE in the example of Figure 13 performs the method of Figure 11.

[0203] Figure 14 illustrates an example for supporting network traffic steering function for wireless communication in accordance with aspects of the present disclosure. In this example, the UE has multi-protocol-stack capability (e.g., dual-protocol-stack capability), and it includes at least a first protocol stack and a second protocol stack. In the example of Figure 14, prior to 1402, the first protocol stack is in an active state and the second protocol stack is in a null state or an inactive state.

[0204] At 1402, a first RRC connection establishment procedure is initiated at the first protocol stack (active). The operation(s) of 1402 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations) of 1402 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0205] At 1404, the UE transmits via the first protocol stack (active), and the NE correspondingly receives, information associated with the network traffic steering function. The information associated with the network traffic steering function may include information indicating that the UE has multi-protocol-stack capability, which may include an indicator (e.g., one or more bits) indicating that the UE has multi-protocol-stackcapability. Additionally or alternatively, the information associated with the network traffic steering function may include information indicating availability of one or more identity modules of the UE. Additionally or alternatively, the information associated with the network traffic steering function may include core network information associated with the first protocol stack. The core network information associated with the first protocol stack may include, e.g., registered AMF and / or mobile network identity information associated with the first protocol stack (such as PLMN identity, S-TMSI, or like identity information associated with the first protocol stack). Additionally or alternatively, the information associated with the network traffic steering function may include radio information associated with the second protocol stack, which may include information associated with PCI, radio frequency, and / or RAT associated with the second protocol stack. Additionally or alternatively, the information associated with the network traffic steering function may include information indicating availability of one or more core network identities of the UE. The operation(s) of 1404 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1404 associated with the UE may be performed by a UE 700 as described with reference to Figure 7 and aspects of the operation(s) of 1404 associated with the NE may be performed by a NE 900 as described with reference to Figure 9.

[0206] At 1406, the NE transmits, and the UE correspondingly receives via the first protocol stack (active), network traffic steering assistance information. The network traffic steering assistance information may be generated by the NE and / or the core network. The network traffic steering assistance information includes radio information for the second protocol stack and core network information for the second protocol stack. The radio information for the second protocol stack may include information associated with PCI, radio frequency, and / or RAT for the second protocol stack. The core network information for the second protocol stack may include AMF and / or mobile network identity information for the second protocol stack. The mobile network identity information for the second protocol stack may include, e.g., PLMN identity, S-TMSI, or like identity information for the second protocol stack). The UE, in particular the first protocol stack of the UE, may filter the radio information for the second protocol stack based on quality of radio signal obtained based on the PCI, the radio frequency, and / or the RAT in the radio information forthe second protocol stack. The network traffic steering assistance information may be provided to the second protocol stack for use by the second protocol stack to enable the network traffic steering function, e.g., if the enabling of network traffic steering function is triggered. The operation(s) of 1406 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1406 associated with the UE may be performed by a UE 700 as described with reference to Figure 7 and aspects of the operation(s) of 1406 associated with the NE may be performed by a NE 900 as described with reference to Figure 9.

[0207] At 1408, the enabling of the network traffic steering function is triggered at the UE. The triggering may include an indication to activate the second protocol stack. The enabling of the network traffic steering function may be triggered by an application or an upper layer of the protocol stack. The operation(s) of 1408 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations) of 1408 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0208] At 1410, the activation of the second protocol stack is initialized. For example, the first protocol stack of the UE may provide an initialization signal to the second protocol stack. The operation(s) of 1410 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1410 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0209] At 1412, the first protocol stack of the UE may provide, to the second protocol stack, information for enabling the network traffic steering function. The information for enabling the network traffic steering function may include, e.g., a core network identity for the second protocol stack, the radio information for the second protocol stack, and the core network information for the second protocol stack, which have been obtained via the first protocol stack. The information for enabling the network traffic steering function may further include the core network identity for the first protocol stack. The operation(s) of 1412 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1412 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0210] At 1414, a second RRC connection establishment procedure is initiated at the second protocol stack. The initiation of the second RRC connection establishment procedure may be based on the information for enabling the network traffic steering function received by the second protocol stack at 1412. The operation(s) of 1414 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1414 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0211] At 1416, establishment of a multi-access PDU session is initiated to enable and activate the network traffic steering function such that the UE can communicate data via the first protocol stack and the second protocol stack. The operation(s) of 1416 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1416 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0212] At 1418, the first protocol stack is caused to enter a null state or an inactive state. This may be due to a change in radio condition associate with the UE (resulting in change in packet error, retransmission rate, transmission delay, etc.), a change associated with an application that utilizes the first protocol stack for communicating data (e.g., stopping of the application). The operation(s) of 1418 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations) of 1418 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0213] It should be noted that the example of Figure 14 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. In one example, the operation(s) of 1404 of Figure 14 may be combined with the operations 1302 of Figure 13. In one example, the operation(s) of 1406 of Figure 14 may be combined with the operations 1306 of Figure 13. In one example, the operations 1304 of Figure 13 may be performed between the operation(s) of 1404 of Figure 14 and the operation(s) of 1406 of Figure 14. In one example, the UE in the example of Figure 14 performs the method of Figure 10; and the NE in the example of Figure 14 performs the method of Figure 11.

[0214] Figure 15 illustrates an example for supporting network traffic steering function for wireless communication in accordance with aspects of the present disclosure. In this example, the UE has multi -protocol-stack capability (e.g., dual-protocol-stack capability), and it includes at least a first protocol stack and a second protocol stack. In the example of Figure 15, initially, the first protocol stack is in an active state and the second protocol stack is in a null state or an inactive state. The first protocol stack and the second protocol stack may each be arranged for communicating data via a respective cellular network connection. The respective cellular network connections may include at least two 3 GPP network connections, e.g., a 5G network connection and a beyond-5G network connection.

[0215] At 1502, the UE transmits, via the first protocol stack, a registration request for registering its multi-protocol-stack capability with a core network. The UE may transmit the registration request to the core network via a NE. The registration request may be a single request for registering only one protocol stack or a joint request for registering at least the first and second protocol stacks. The registration request may include information associated with the multi -protocol-stack capability of the UE and / or information associated with the network traffic steering function. The information associated with the multi- protocol-stack capability of the UE may include, e.g., information indicating that the UE has multi-protocol-stack capability, information indicating that the UE comprises the second protocol stack, information requesting an identity for the second protocol stack, etc. The operation(s) of 1502 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1502 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0216] At 1504, an authentication operation is performed by the UE and the core network via a NE. For example, the UE may include multiple identity modules (e.g., USIM) each for a respective protocol stack. The UE may receive, via the first protocol stack, at least one authentication request for at least one of the identity modules, and in response, transmits a response containing credential information for authenticating the at least one identity modules. The operation(s) of 1504 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations) of 1504associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0217] At 1506, upon successful authentication and registration, the UE receives, via the first protocol stack, registration acceptance indicating acceptance of the registration. The registration acceptance may include information for enabling the network traffic steering function. The information for enabling the network traffic steering function may include, e.g., a core network identity for the second protocol stack; a core network identity for the first protocol stack; network traffic steering rules for communicating data via the first protocol stack and the second protocol stack, which govern the conditions for communicating via the first protocol stack and the second protocol stack; radio information for the second protocol stack, which may include information associated with PCI, radio frequency, and / or RAT for the second protocol stack; and / or core network information for the second protocol stack, which may include AMF and / or mobile network identity information (e.g., PLMN identity, S-TMSI, or like identity information) for the second protocol stack. The information for enabling the network traffic steering function may include additional or alternative information. The operation(s) of 1506 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1506 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0218] At 1508, the UE receives, at the first protocol stack, an indication to activate the second protocol stack, e.g., as part of the triggering of the enabling of the network traffic steering function. The indication to activate the second protocol stack may be generated as a result of an application or an upper layer of the protocol stack triggering the enabling of the network traffic steering function. The operation(s) of 1508 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1508 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0219] At 1510, the first protocol stack initializes activation of the second protocol stack. For example, the first protocol stack may provide to the second protocol stack, and the second protocol stack may correspondingly receive from the first protocol stack, aninitiation signal (or activation command) to activate or “wake up” the second protocol stack. The operation(s) of 1510 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1510 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0220] At 1512, the first protocol stack provides to the second protocol stack, and the second protocol stack correspondingly receives from the first protocol stack, information for enabling the network traffic steering function. The information may include one or more of the information for enabling the network traffic steering function received in 1506. For example, the first protocol stack may provide to the second protocol stack the radio information for the second protocol stack (e.g., to assist with cell camping) and the core network information for the second protocol stack. The operation(s) of 1512 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1512 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0221] At 1514, the second protocol stack performs cell and PLMN selection based on the information received from the first protocol stack. The operation(s) of 1514 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1514 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0222] At 1516, the second protocol stack initiates RRC connection establishment. The second protocol stack may include the network traffic steering as an establishment cause. The operation(s) of 1516 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1516 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0223] At 1518, the UE transmits, via the second protocol stack, an RRC message. The RRC message may be transmitted to the UE. The RRC message may include the core network information for the second protocol stack (received from the first protocol stack). The operation(s) of 1518 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1518 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0224] At 1520, the UE receives, via the second protocol stack, RRC configuration or reconfiguration information. The RRC configuration or reconfiguration information may be generated by the UE and / or the core network. The RRC configuration or reconfiguration information may include configuration for one or more signaling and data radio bearer(s) for the second protocol stack. The operation(s) of 1520 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation(s) of 1520 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0225] At 1522, the UE initiates data communication via the second protocol stack, e.g., as part of the enabling of the network traffic steering function. For example, the UE initiates data communication (transmission and / or reception) on the established signaling and data radio bearer(s). The operation(s) of 1522 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations) of 1522 associated with the UE may be performed by a UE 700 as described with reference to Figure 7.

[0226] It should be noted that the example of Figure 15 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. In one example, the UE in the example of Figure 15 performs the method of Figure 10.

[0227] 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) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: transmit, via a first protocol stack of the UE, a first information associated with a multi-protocol-stack capability of the UE for enabling a network traffic steering function, wherein the UE is capable of receiving or transmitting data via one or both of the first protocol stack and a second protocol stack of the UE based at least in part on the multi-protocol- stack capability of the UE; and receive, via the first protocol stack, a second information for enabling the network traffic steering function.

2. The UE of claim 1, wherein the second protocol stack is in a null state or an inactive state until transmission of the first information or reception of the second information.

3. The UE of claim 1 or 2, wherein the first information indicates: the UE has multi-protocol-stack capability; or a request for an identity for the second protocol stack.

4. The UE of any one of claims 1 to 3, wherein the second information comprises one or more of: a core network identity for the first protocol stack or a core network identity for the second protocol stack.

5. The UE of any one of claims 1 to 4, wherein the second information comprises: one or more network traffic steering rules for the first protocol stack and the second protocol stack;one or more radio frequencies (RFs), one or more radio access technologies (RATs), or one or more public land mobile networks (PLMNs) for wireless communication via the second protocol stack; or one or more candidate cells suitable for wireless communication via the second protocol stack.

6. The UE of any one of claims 1 to 5, wherein the at least one processor is configured to cause the UE to: in response to transmission of the first information and prior to reception of the second information: receive, via the first protocol stack, a request message to authenticate the UE; and transmit, via the first protocol stack, a response message comprising credential information for authenticating the UE.

7. The UE of any one of claims 1 to 5, wherein the UE includes a plurality of identity modules, each identity module is associated with a respective protocol stack of the UE; and wherein the at least one processor is configured to cause the UE to: in response to transmission of the first information and prior to reception of the second information: receive a request message to authenticate one or more of a first identity module associated with the first protocol stack or a second identity module associated with the second protocol stack; and transmit a response message comprising one or more of a first credential information of the first identity module or a second credential information of the second identity module.

8. The UE of any one of claims 1 to 7, wherein the at least one processor is configured to cause the UE to: obtain one or more keys for encryption, integrity protection, authentication, or privacy for the second protocol stack; andprovide the one or more keys to the second protocol stack for encryption, integrity protection, authentication, or privacy at the second protocol stack.

9. The UE of any one of claims 1 to 8, wherein the at least one processor is configured to cause the UE to: output the second information to the second protocol stack for use by the second protocol stack to enable the network traffic steering function.

10. The UE of any one of claims 1 to 9, wherein the at least one processor is configured to cause the UE to: initiate, at the first protocol stack, a first radio resource control (RRC) connection establishment procedure; transmit, via the first protocol stack, information associated with the network traffic steering function; and receive, via the first protocol stack, network traffic steering assistance information comprising radio information for the second protocol stack and core network information for the second protocol stack.

11. The UE of claim 10, wherein the information associated with the network traffic steering function comprises one or more of: an indication that the UE has multi-protocol-stack capability; an indication of whether one or more identity modules of the UE are available; or core network information associated with the first protocol stack, including one or more of registered access and mobility management function (AMF) related information or mobile network identity related information associated with the first protocol stack.

12. The UE of claim 10 or 11 , wherein the information associated with the network traffic steering function comprises one or more of: a physical cell identity (PCI), a radio frequency (RF), or a radio access technology (RAT) associated with the second protocol stack; oran indication of availability of one or more core network identities of the UE.

13. The UE of any one of claims 10 to 12, wherein: the radio information for the second protocol stack comprises information associated with PCI, RF, / or RAT for the second protocol stack.

14. The UE of claim 13, wherein the at least one processor is configured to cause the UE to: filter the radio information for the second protocol stack based on one or more signal qualities associated with one or more received radio signals, the one or more received radio signals are based on the information associated with PCI, the RF, or the RAT in the radio information for the second protocol stack.

15. The UE of any one of claims 10 to 14, wherein: the core network information for the second protocol stack comprises one or more of AMF related information or mobile network identity related information for the second protocol stack.

16. The UE of any one of claims 10 to 15, wherein the at least one processor is configured to cause the UE to: receive an indication to activate the second protocol stack; and provide, to the second protocol stack, at least, a core network identity for the second protocol stack, the radio information for the second protocol stack, and the core network information for the second protocol stack.

17. The UE of claim 16, wherein the at least one processor is configured to cause the UE to: initiate, at the second protocol stack, a second RRC connection establishment procedure based on the core network identity for the second protocol stack, the radio information for the second protocol stack, and the core network information for the second protocol stack; andinitiate establishment of a multi-access protocol data unit (PDU) session for the first protocol stack and the second protocol stack.

18. The UE of claim 16 or 17, wherein the indication to activate the second protocol stack is based at least in part on an application associated with the UE requiring the network traffic steering function.

19. The UE of any one of claims 16 to 18, wherein the at least one processor is configured to cause the UE to: switch the first protocol stack to a null state or an inactive state after activation of the second protocol stack.

20. A network entity (NE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: receive a first information associated with a multi-protocol-stack capability of a UE for enabling a network traffic steering function, wherein the UE is capable of receiving or transmitting data via one or both of a first protocol stack and a second protocol stack of the UE based at least in part on the multi-protocol-stack capability of the UE; and transmit a second information for enabling the network traffic steering function.

Images