Session management function instance and user plane function instance selection for dual-steer

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) transmits, to a network entity via a first radio access network (RAN) using a primary protocol stack of the UE, a first request for establishment of a dual-steer packet data unit (PDU) session. The dual-steer PDU session includes a primary session associated with the primary protocol stack and a secondary session associated with a secondary protocol stack. The UE receives, from the network entity via the first RAN, a correlation value at the primary protocol stack. The UE transmits a second request for establishment of the secondary session of the dual-steer PDU session, the second request includes the correlation value. The UE communicates first messages via the first RAN using the primary session and second messages via the second RAN using the secondary session based on the first request and the second request.

Description

SESSION MANAGEMENT FUNCTION INSTANCE AND USER PEANE FUNCTION INSTANCE SELECTION FOR DUAL-STEERCROSS REFERENCE

[0001] The present Application for Patent claims priority to Greek Patent Application No. 20240100022 by SPEICHER et al., entitled “SESSION MANAGEMENT FUNCTION INSTANCE AND USER PLANE FUNCTION INSTANCE SELECTION FOR DUAL-STEER,” filed Januaiy 11, 2024. which is assigned to the assignee hereof and expressly incorporated by reference herein.FIELD OF TECHNOLOGY

[0002] The following relates to wireless communications, including session management function (SMF) instance and user plane function (UPF) instance selection for dual-steer.BACKGROUND

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

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support session management function (SMF) instance and user plane function (UPF) instance selection for dual-steer packet data unit (PDU) session. For example, the described techniques provide for a user equipment (UE) including a dualsteer protocol stack that selects the same SMF and UPF using a correlation value. The correlation value may be an SMF identifier (ID) or a data network name (DNN) ID. The correlation value may be exchanged between a primary protocol stack of the UE and a secondary protocol stack of the UE.

[0005] In some examples, selecting the same SMF and UPF may involve a shared SMF ID that is stored in the primary protocol stack and the secondary protocol stack. In such examples, a unified data management context (e.g., subscription information) of the primary protocol stack and the secondary' protocol stack may share data fields. The SMF ID for the SMF may be stored in a first unified data management (UDM) context for the primary protocol stack and in a second UDM context for the second primary protocol stack after the SMF is allocated for the dual-steer PDU session by the network. The correlation value (e.g., the SMF ID or the DNN ID) and / or the common SMF ID in the UDM contexts may facilitate in efficiently and accurately identifying the same SMF and / or UPF that may be used for dual traffic steering, switching, and / or splitting over the two 3GPP access networks (e g., the first access network and the second access network) of the dual-steering PDU session.BRIEF DESCRIPTION OF THE DRAWINGS

[0006] FIG. 1 shows an example of a wireless communications system that supports session management function (SMF) instance and user plane function (UPF) instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0007] FIG. 2 shows an example of a block diagram of stacks of UEs 115 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0008] FIG. 3 shows an example of a process flow using a correlation value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0009] FIG. 4 shows an example of a process flow using a correlation value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0010] FIG. 5 shows an example of a process flow using a correlation value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0011] FIG. 6 shows an example of a process flow using a correlation value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0012] FIG. 7 shows an example of a process flow using a data network name (DNN) value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0013] FIG. 8 shows an example of a process flow using a DNN value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0014] FIG. 9 shows an example of a process flow using a DNN value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0015] FIG. 10 shows an example of a process flow using a DNN value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0016] FIG. 11 shows an example of process flow associated with a unified data management context that supports SMF instance and UPF instance selection for dualsteer in accordance with one or more aspects of the present disclosure.

[0017] FIGs. 12 and 13 show block diagrams of devices that support SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0018] FIG. 14 shows a block diagram of a communications manager that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0019] FIG. 15 shows a diagram of a system including a device that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0020] FIGs. 16 and 17 show block diagrams of devices that support SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0021] FIG. 18 shows a block diagram of a communications manager that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0022] FIG. 19 shows a diagram of a system including a device that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.

[0023] FIGs. 20 through 25 show flowcharts illustrating methods that support SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION

[0024] Some wireless communication systems may involve access traffic steering switching and splitting (ATSSS). In such systems, the network may manage multiple access (MA) networks, where the network steers traffic by switching from one access network to another or splitting the traffic over MA networks. The MA networks may include 3rd generation partnership project (3GPP) access networks (e.g., Long Term Evolution (LTE) network) and non-3GPP access networks (e.g., Wi-Fi network). In some examples, the ATSSS wireless communication systems may include a packet dataunit (PDU) session that forms a data path (e.g., a logical connection) between a user equipment (UE) and the core network. In some examples, the established PDU session of the ATSSS wireless communication systems may be a dual-steer PDU session that includes a primary protocol stack of the UE that is associated with a first access network and a secondary protocol stack of the UE that is associated with a second access network, where the two access networks are 3GPP access networks. The dual-steer PDU may manage traffic over the first access network and the second access network. Traffic steering, switching, and / or splitting over the two 3GPP networks may involve using a common session management function (SMF) and a common user plane function (UPF) between the primary protocol stack and the secondary protocol stack. However, identifying the same SMF and the UPF to use for the primary protocol stack and the secondary' protocol stack may be difficult.

[0025] To identify the same SMF and the UPF, a UE including a dual-steer protocol stack may select the same SMF and UPF using a correlation value. The correlation value may be an SMF identifier (ID) or a data network name (DNN) ID. The correlation value may be exchanged between a primary protocol stack of the UE and a secondary protocol stack of the UE. In some examples, selecting the same SMF and UPF may involve using a shared SMF ID that is stored in the primary protocol stack and the secondary protocol stack. In such examples, a unified data management (UDM) context (e.g., subscription information) of the primary protocol stack and the secondary protocol stack may share data fields. The SMF ID for the SMF may be stored in a first UDM context for the primary protocol stack and in a second UDM context for the second primary' protocol stack after the SMF is allocated for the dual-steer PDU session by the network. The correlation value (e.g., the SMF ID or the DNN ID) and / or the common SMF ID in the UDM contexts may facilitate in efficiently and accurately identifying the same SMF and / or UPF that may be used for dual traffic steering, switching, and / or splitting over the tyvo 3GPP access networks (e.g., the first access network and the second access netw ork) of the dual-steering PDU session.

[0026] Aspects of the disclosure are initially described in the context of yvireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to SMF instance and UPF instance selection for dual-steer.

[0027] FIG. 1 shows an example of a wireless communications system 100 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 105, one or more UEs 115. and a core network 130. In some examples, the wireless communications system 100 may be a LTE network, an LTE- Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

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

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

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

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

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

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

[0036] For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor), IAB nodes 104, and one or more UEs 115. The IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node with a wired or wireless connection to core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). IAB donor and IAB nodes 104 may communicate via an Fl interface according to a protocol that defines signaling messages (e.g., an Fl AP protocol). Additionally, or alternatively, the CU 160 may communicate with the core network via an interface, which may be an example of a portion of backhaul link, and may communicate with other CUs 160 (e g., a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of a portion of a backhaul link.

[0037] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities). A DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with the IAB node 104. That is. an IAB donor may be referred to as a parent node incommunication with one or more child nodes (e.g., an TAB donor may relay transmissions for UEs through one or more other I AB nodes 104). Additionally, or alternatively, an IAB node 104 may also be referred to as a parent node or a child node to other IAB nodes 104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of IAB nodes 104 may provide a Uu interface for a child IAB node 104 to receive signaling from a parent IAB node 104, and the DU interface (e.g., DUs 165) may provide a Uu interface for a parent IAB node 104 to signal to a child IAB node 104 or UE 115.

[0038] For example, IAB node 104 may be referred to as a parent node that supports communications for a child IAB node, or referred to as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 with a wired or wireless connection (e.g., a backhaul communication link 120) to the core network 130 and may act as parent node to IAB nodes 104. For example, the DU 165 of IAB donor may relay transmissions to UEs 115 through IAB nodes 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of IAB donor may signal communication link establishment via an Fl interface to IAB nodes 104, and the IAB nodes 104 may schedule transmissions (e.g.. transmissions to the UEs 115 relayed from the IAB donor) through the DUs 165. That is, data may be relayed to and from IAB nodes 104 via signaling via an NR Uu interface to MT of the IAB node 104. Communications with IAB node 104 may be scheduled by a DU 165 of IAB donor and communications with IAB node 104 may be scheduled by DU 165 of IAB node 104.

[0039] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support SMF instance and UPF instance selection for dual-steer as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 180).

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

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

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

[0043] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different radio access technology).

[0044] The communication links 125 shown in the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 1 15, uplink transmissions (e.g., return link transmissions) from a UE 115 to a netw ork entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode).

[0045] A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3. 5, 10, 15, 20. 40. or 80 megahertz (MHz)). Devices of the wireless communications system 100 (e.g., the network entities 105, the UEs 115, or both) may have hardw are configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

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

[0047] One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (A / ) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 1 1 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.

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

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

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

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

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

[0053] The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base stations 140) may have similar frame timings, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, network entities 105 may have different frame timings, and transmissions from different network entities 105 may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.

[0054] Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g.. a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs 115 include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs)) within a carrier, within a guard-band of a earner, or outside of a carrier.

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

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

[0057] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity7that manages access and mobility (e g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a UPF (UPF)). The control plane entity7may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g.. basestations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

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

[0059] The wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170), and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, such techniques may facilitate using antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country' or regulating body.

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

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

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

[0063] The wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. An RLC layer may perform packet segmentation and reassembly to communicate via logical channels. A MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.

[0064] The wireless communication systems 100 may involve a dual-steer PDU session that includes a primary protocol stack of the UE 1 15 that is associated with a first access network (e.g., a 3GPP access network) and a secondary protocol stack of the UE 115 that is associated with a second access network (e.g., another 3GPP access network that differs from the first access network). The dual-steer PDU of the UE 115 may manage traffic over the first access network and / or the second access network. Traffic steering, switching, and / or splitting over the 3GPP networks may involve using a common SMF and a common UPF between the primary protocol stack and the secondary' protocol stack. However, identifying the same SMF and the UPF to use for the primary protocol stack and the secondary protocol stack may be difficult.

[0065] As discussed herein, to identify’ the same SMF and the UPF. the UE 115 may use a correlation value, in some examples. The correlation value may be an SMF ID or a DNN ID. The correlation value may be exchanged between the primary protocol stack of the UE 115 and the secondary protocol stack of the UE 115. In some examples, selecting the same SMF and UPF may involve a shared SMF ID that is stored in theprimary protocol stack and the secondary protocol stack. In such examples, a UDM context (e.g., subscription information) of the primary' protocol stack and the secondary' protocol stack may share data fields. The SMF ID for the SMF may be stored in a first UDM context for the primary protocol stack and in a second UDM context for the second primary protocol stack after the SMF is allocated for the dual-steer PDU session by the network entity' 105. The correlation value (e.g., the SMF ID or the DNN ID) and / or the common SMF ID in the UDM contexts may facilitate in efficiently and accurately identifying the same SMF and / or UPF that may be used for dual-traffic steering, switching, and / or splitting over the two 3 GPP access networks (e.g., the first access network and the second access network) of the dual-steering PDU session.

[0066] FIG. 2 shows an example of a block diagram 200 of protocol stacks of UEs 11 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The block diagram 200 mayimplement aspects of or may be implemented by aspects of the wireless communications system 100. For example, the block diagram 200 may include a UE 115-a, a UE 115-b, and a network entity' 105-a, which may be examples of a UE 115 and a network entity 105 described with respect to FIG. 1. In some examples, the UE 115-a and the UE 115-b may be part of the same UE 115 but correspond to different protocol stacks of the UE 115.

[0067] The block diagram 200 corresponds to an ATSSS multiple-access (MA) PDU session, which may include the dual-steer PDU session. The dual-steer PDU session may include two access networks (e.g., radio access networks (RAN)). In some examples, an MA PDU session may include one 3GPP access network and one non-3GPP access network. In some examples, the MA PDU session may provide service inter-public land mobile network (inter-PLMN) or between PLMNs, or may provide service intra-PLMN or within the same PLMN.

[0068] In some examples, a dual-steer device (e.g., mobile device) may switch or steer traffic across two different 3GPP access networks. In some examples, a dual-steer device supporting traffic steering and switching of user data (for different services) across tw o 3GPP access networks may be a single UE 115-a, for example, to support non-simultaneous data transmission over the two netw orks. In some examples, the dualsteer device supporting traffic steering and switching of user data across the two 3GPPaccess networks may include two separate UEs 115, for example, in case of simultaneous data transmission over the two access networks.

[0069] In some examples, the dual-steer PDU session of the UE 115-a and / or UE 115-b (e.g., a single UE 115 or two separate UEs 115) may be established within a single PLMN or the dual-steer PDU session may have one 3GPP access over a primary PLMN and the another 3GPP access over another (secondary) PLMN or non-public network (NPN). In some examples, the access networks may not be shared (e.g., use different radio access networks). In some examples, the 3GPP access networks may be the same radio access network (RAT) or different RATs. For example, the RATs may include an NR network and another NR network, a non-terrestrial network (NTN) and another NTN network, an NR network and an LTE network, an NR network and an NTN network, and so forth.

[0070] The dual-steer PDU session of a dual-steer device may include a single UE 115, or two UEs 115. For example, the dual-steer device may include a primary’ UE, such as UE 1 15-a, which may be awake and communicating (e.g., “on”) and may awaken or activate a secondary' UE, such as UE 115-b. The secondary UE 115 may be activated by the primary’ UE 115, for example, based on a UE route selection policy (URSP) rule. In such examples, the primary UE 115 may receive and process one or more URSP rules. A dual-steer layer 226 may include a control plane (CP) and a user plane (UP). The UP may' use a hypertext protocol (HTTP3), a multipath extension quick user datagram protocol (UDP) internet connection (MP-QUIC), UDP, internet protocol (IP), or multipath transport protocol (MPTCP), transport protocol (TCIP), or a combination thereof. The CP may manage dual-steer rules received from the network (e.g., network entity 105-a). The dual-steer layer 226 may link PDU sessions of the primary' UE 115 and the secondary' UE 115. In some examples, the primary’ UE 115 and the secondary' UE 115 may be provisioned (e.g., pre-provisioned) with separate subscription permanent identifiers (SUPIs) and / or international mobile equipment identities (IMEIs), as well as provisioned with separate security credentials. The dualsteer layer may7establish at least as many MP-QUIC connections as the quantity of quality of service(QoS) paths (e.g., QoS flows) of both UEs 115 (e.g., a single MP- QUIC connection per QoS flow).

[0071] As discussed herein, the UE 115-a (e.g., the primary UE) may correspond to a primary' protocol UE stack and the UE 115-b (e.g., the secondary UE) may correspond to a second protocol UE stack. The dual-steer device may include a dual-steer UE 115, where the UE 115 has two separate UE stacks on top of or communicating with a dualsteer management function (DS management function). In some cases, the dual-steer UE 115 may be a single UE that includes the UE 115-a and the UE 115-b, or the dualsteer UE 115 may be a two different UEs (e.g., the UE 115-a and the UE 115-b) managed by the dual-steer layer 226.

[0072] The dual-steer data flow, as shown in block diagram 200, may include the UE 1 15-a, the UE 115-b, the network entity 105-a, a first radio access network 210-a associated with a primary PDU session and the UE 115-a, a second radio access network 210-b associated with a secondary' PDU session and the UE 115-b, an AMF 220-a, an AMF 220-b, a dual-steer layer 226, a data network 230 (e.g., data network manager module), a UPF 235, a UDM 240, an SMF 245, a unified data management (UDF) 250, and a policy control function (PCF) 255. Data may be communicated between these components of the block diagram 200 to facilitate dua-steering.

[0073] The UDM 240 and the user data repository' (UDR) 250 may be logically the same for the UE 115-a (e.g., primary UE or primary protocol stack of the same UE 115) and the UE 1 15-b (e.g., secondary UE or secondary protocol stack of the same UE 115). If the subscriptions are from the same operator (e.g., component), then a common SMF 245 or PDU session anchor (PSA), and / or UPF 235 or PCF 255, may be selected for the first PDU session associated with the first radio access network 210-a (e.g.. a primary' PDU session associated with the UE 115-a) and the secondary PDU session associated with the second radio access network 210-b (e.g., a secondary' PDU session associated with the UE 115-b). The dual-steer PDU sessions may terminate (e.g., end point) on the same data network. For example, the same source address (e.g., IP) may be used for data packets (e.g., of N6 user plane) from the UE 115-a and the UE 115-b.

[0074] In some examples, a core network (CN) may allocate the same address (e.g., IP address) to the UE 115-a and the UE 115-b for a dual-steer PDU session in order to select the same serving SMF 245 for the two UEs 115. The same UPF 235 may be selected for both UE 115-a and UE 115-b since the traffic of some service data flow (SDF) may split between the first radio access network 210-a and second radio accessnetwork 210-b and aggregation of the data may occur at the UE 1 15-a (e.g., in downlink communications) and at the UPF 235 (e.g., in uplink communications). However, selecting the same instance of SMF 245 and the same instance of UPF 235 (e.g., PSA) for both the UE 115-a and the UE 115-b of the dual-steer device for a PDU session, may be difficult. The techniques described herein with respect to at least FIGs. 3-11 facilitate selecting the same instance of the SMF 245 and / or the same instance of the UPF 235.

[0075] In the wireless communications system of the block diagram 200, the network entity 105-a may communicate with the UE 115-a and the UE 115-b, that may be part of the same UE 115 but different protocol stacks, using a communication link 125. In some examples, the communication link 125 may include a first channel for transmitting data from the UE 115-a and / or the UE 115-b to the network entity 105-a and a second channel for transmitting data from the network entity 105-a to the UE 115-a and / or the UE 115-b. The communication link 125 may be an example of an NR or LTE link between the UE 115-a and / or the UE 115-b and the network entity 105-a. The communication link 125 may include a bi-directional link that enables both uplink and dow nlink communications, for example, via the channels of the communication link 125. For example, the UE 115-a and / or the UE 115-b may transmit uplink messages (e.g., uplink transmissions), such as uplink control signals or uplink data signals, to the network entity 105-a using the first channel (e.g., of the communication link 125) and the network entity7105-a may transmit downlink messages (e.g., downlink transmissions), such as downlink control signals or downlink data signals, to the UE 115-a and / or the UE 115-b using the second channel (e.g., of the communication link 125). In some examples, the downlink messages may be part of control signaling transmitted form the network entity 105-a.

[0076] The UE 115 including the dual-steer protocol stacks (e.g., UE 115-a and UE 115-b) may transmit (e.g., via the communication link 125), to the network entity 105-a via the first radio access network 210-a using a primary protocol stack (e.g., UE 115-a) of the UE 115, a first request for establishment of a PDU session (e.g., a dual steer PDU session). The PDU session may include a primary session associated with the primary protocol stack and a secondary session associated with a secondary protocol stack. The protocol stack may include the primary protocol stack and the secondary protocol stack.The UE 1 15 may receive, from the network entity 105-a via the first radio access network 210-a, a correlation value at the primary protocol stack based on the first request. The UE 115, to the network entity 105-a via the second radio access network 210-b using the secondary protocol stack of the UE 115, a second request for establishment of the PDU session. The second request may include the correlation value.

[0077] The UE 115 may communicate one or more first messages via the first radio access network 210-a using the primary session and one or more second messages via the second radio access network 210-b using the secondary session based on the first request and the second request. Receiving, from the network entity 105-a, the correlation value, may include receiving a PDU session request accept message including the correlation value based on the first request. The PDU session request accept message may indicate activation of the primary PDU session in the primary protocol stack.

[0078] The UE 115 may communicate, via the dual -steer layer 226, the correlation value from the primary protocol stack to the secondary protocol stack. The UE 115 may receive a PDU session request accept message based on the second request, the PDU session request accept message indicating activation of the secondary session of the PDU session. Receiving, from the network entity 105-a, the correlation value may include receiving the correlation value from a serving SMF 245 of a network, where the correlation value is indicative of the serving SMF 245.

[0079] Transmitting, to the network entity 105-a, the correlation value to the secondary’ protocol stack may include transmitting the correlation value to the serving SMF 245 of a network via an AMF 220. The PDU session may be associated with a same UPF 235 for the primary protocol stack and the secondary’ protocol stack of the UE 115. The correlation value may include an SMF ID or a DNN ID. An IP address for the PDU session may be the same as an IP address for the primary' protocol stack and for the secondary protocol stack.

[0080] In some examples, the network entity 105-a may obtain, via the first radio access network 210-a from a primary protocol stack of the UE 115, a first request for establishment of a PDU session. The PDU session may include a primary’ PDU sessionassociated with the primary protocol stack and a secondary PDU session associated with a secondary protocol stack, where a protocol stack of the UE 115 includes the primary protocol stack and the secondary protocol stack. The network entity 105-a may output, to the UE 115 via the first radio access network 210-a (e.g.. of UE 115-a), a correlation value at the primary protocol stack based on the first request. The network entity 105-a may obtain, via the second radio access network 210-b from the secondary protocol stack of the UE 115 (e.g., UE 115-b), a second request for establishment of the secondary PDU session of the PDU session, the second request including the correlation value. The network entity 105-a may communicate one or more first messages via the first radio access network 210-a using the primary PDU session and one or more second messages via the second radio access network 210-b using the secondary PDU session based on the first request and the second request.

[0081] In some examples, the network entity 105-a may associate the correlation value with the primary PDU session for establishment of the PDU session. The network entity 105-a may select a same SMF 245 for the primary protocol stack and the secondary protocol stack based on the correlation value. The network entity 105-a may output data to the PDU session (e.g.. steer traffic of user data) via one of the first radio access network 210-a using the primary PDU session or the second radio access network 210-b using the secondary PDU session.

[0082] In some examples, the network entity 105-a may obtain a request for establishment of a PDU session from a primary protocol stack of a dual-steer protocol stack of the UE 115, where a subscription of the primary' protocol stack is correlated with a subscription of a secondary protocol stack of the dual-steer protocol stack. The network entity 105-a may establish, based on the subscription of the primary protocol stack being correlated with the subscription of a secondary protocol stack, a primary session via the first radio access network 210-a using a first UDM context for the primary’ protocol stack and a secondary session via the second radio access network 210-b using a second UDM context for the secondary protocol stack. The dual-steer PDU session may include the primary session that is associated with the primary protocol stack and the secondary' session that is associated with the secondary' protocol stack. The first UDM context may include a serving SMF ID and the second UDM context may include the serving SMF ID.

[0083] The network entity 105-a may communicate one or more first messages via the first radio access network 210-a using the primary session and one or more second messages via the second radio access network 210-b using the secondary session. The network entity 105-a may include an AMF 220 or a UDM 240. The network entity 105-a may store the serving SMF ID for a SMF 245 in the first UDM context for the primary protocol stack and in the second UDM context for the secondary protocol stack after the SMF 245 is allocated for the dual-steer PDU session. Establishing the secondary session may include the network entity 105-a establishing, via an AMF 220 associated with the network entity 105-a, the secondary session using the serving SMF ID received from a UDM 240 associated with the network entity 105-a. The network entity 105-a may include a first AMF, a second AMF and a UDM function, or any combination thereof. The network entity 105-a may generate the first UDM context for the primary protocol stack, where the first UDM context includes the serving SMF ID. The network entity 105-a may store the serving SMF ID in the second UDM context for the secondary protocol stack. The correlation value may include a SMF ID or a DNN ID. An IP address for the PDU session may be the same as an IP address for the primary protocol stack and for the secondary protocol stack.

[0084] FIG. 3 shows an example of a process flow 300 using a correlation value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The process flows 300-1100 of FIGs. 3- 11 may implement aspects of or may be implemented by aspects of the wireless communications system 100 or the block diagram 200. For example, the process flows 300-110 may include a UE 1 15-c, which may be an example of a UE 115 (e.g., protocol stack of the UE 115) described herein. The process flow 300 may also include an access network 310 (e.g., access network 210-a and / or 210-b of FIG. 2), an AMF 320 (e.g., the AMF 220-a and / or the AMF 220-b of FIG. 2). a UPF 335 (e.g., the UPF 235 of FIG. 2), an SMF 345 (e.g., 245 of FIG. 2), a PCF 355 (e.g., the PCF 255 of FIG. 2). a UDM 340 (e.g., the UDM 240 of FIG. 2), and the data network (DN) 330 (e g., the data network 230 of FIG. 2).

[0085] In the following description of the process flows 300-1100, the operations performed by various components (e.g., a UE 115, a network entity 105, and / or components of block diagram 200) may be performed in different orders or at differenttimes than the exemplar}7order shown. Some operations may also be omitted from the process flows 300-1100, or other operations may be added to the process flows 300- 1100. Further, while operations in the process flows 300-1100 are illustrated as being performed by respective components, the examples herein are not to be construed as limiting, as the described features may be associated with any quantity of different devices.

[0086] In some examples, to select the same SMF 345 instance for the primary7UE 11 -c (e.g., UE 115-a of FIG. 2) and the secondary7UE 115 (e.g., UE 115-b of FIG. 2), a SMF correlation ID (e.g., correlation value) may be used. The SMF correlation ID may be an information element (IE) as part of non-access stratum (NAS) signaling. After establishing a data connection for a dual-steer UE 115 (e.g., via communications with a network entity7105), the serving SMF 345 may provide a correlation ID to the primary7UE 115 in NAS signaling. The SMF 345 may also configure the correlation ID in the network repository function (NRF) so that the NRF may associate (e.g., resolve) the correlation ID to the specific SMF 345 instance.

[0087] The primary UE 115-c may pass the correlation ID to the secondary7UE 115 via the dual-steer layer. The secondary UE 115 may indicate the correlation ID to the AMF 320 during a PDU session establishment request in NAS signaling. After receiving the correlation ID. the AMF 320 may forward the correlation ID to the NRF. The NRF may select the SMF 345 instance based on the correlation ID provided by the secondary7UE 115. The correlation ID may be an identity7of the serving SMF or may be a network generated tag that supports the NRF in selecting the serving SMF. In some examples, the correlation ID may have a limited validity7(e.g., expires or changes after a threshold time) to ensure that the correlation ID is not used (e.g., re-used) for other PDU sessions, for example, to reduce miscommunications in PDU session establishment. In some examples, the correlation ID may have a value correlated to the PDU session ID of the primary PDU session of the primary7UE 115-c. A subscription of the secondary UE 115 may include information, such as the SUPI of the primary UE 115-c. The selected SMF 345 instance may identify the context of the primary UE 115-c based on the secondary7UE’s subscription (that includes the SUPI associated with the primary7UE 115-c). The SMF 345 instance may select the same UPF 335 instance used for primaryUE 1 15-c since the identity of the selected UPF 335 is part of the context associated with the primary UE 115-c.

[0088] As part of dual-steer PDU session establishment using the correlation ID, at 305, the primary UE 115-c may transmit signaling to the AMF 320 that indicates a PDU session establishing request for establishment of a dual-steer PDU session, as well indicating dual-steer capabilities (e.g., MTCP, MQUIC, lower layer functionality, etc ).

[0089] At 350, the AMF 315 may communicate with the NRF and select an SMF 345 capable of supporting the dual-steer. At 350, the AMF 320 may forward the PDU request to the selected SMF 345. At 360, the SMF 345 may retrieve subscription or subscription updates (e.g., from the UDM 340). The subscription may indicate whether the dual-steer PDU session is appropriate (e.g., allowed). That is, at 360, the SMF 345 may retrieve whether the requested dual-steer PDU session is allowed or not allowed.

[0090] At 365, the SMF 345 may transmit signaling indicating a response to the AMF 320. The response may include whether the dual-steer PDU session is allowed. At 370, if the session is allowed, PDU session authentication procedures may be performed using one or more components of the process flow 300. At 375, the selected (e.g., serving) SMF 345 may select a PFC. At 380, the PCF 355 may determine, based on policy and subscription, if the dual-steer PDU session is allow ed. The SMF 345 may derive traffic and N4 rules from policy and charging control (PCC) rules. At 385, the SMF 345 may select the dual-steer capable UPF 335. At 390, the DN 330 may transmit N4 rules to the selected UPF 335, as well as N4 session establishment or modification request. At 395, the UPF 335 may transmit signaling indication a response to the N4 session establishment or modification request (e.g., dual-steer PDU session establishment).

[0091] FIG. 4 shows an example of a process flow 400 using a correlation value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The process flow 400 may be an extension of process flow 300. The process flow 400 may include a dual-steer layer 425, a primary UE 115-d. an access network 410 (e.g.. access network 210-a and / or 210-b of FIG. 2), an AMF 420 (e.g., the AMF 220-a and / or the AMF 220-b of FIG. 2), a UPF 435 (e.g., the UPF 235 of FIG. 2), an SMF 445 (e.g., 245 of FIG. 2), a PCF 455 (e.g.,the PCF 255 of FIG. 2), a UDM 440 (e.g., the UDM 240 of FIG. 2), and the DN 430 (e.g., the data network 230 of FIG. 2).

[0092] At 403, 405, and 415, the SMF 445 may mark the PDU session as a dualsteer PDU session, resulting in an activation of the dual-steer feature in the primary' UE 115-d. The SMF 445 may include an SMF correlation ID to be used in establishing the dual-steer PDU establishment for a secondary UE 1 15 (e g., of FIG. 5 and FIG. 6). The PMF may be addressed if lower layer functionality is supported. For example, linkspecific MP preferences and proxy information may be used for the PMF, if MP TCP or MP QUIC are supported. In some examples, the primary UE 115-d may indicate the dual-steer PDU acceptance and forward the SMF correlation ID to the dual-steer layer 425.

[0093] At 450, the access network 410 may transmit signaling indicating a N2 PDU session response to the AMF 420. At 460, the primary UE 115-d may transmit a first uplink data to the UPF 435. At 465, the AMF 420 may transmit signaling to the SMF 445 indicating a PDU session update for a context request. At 470, the SMF 445 may transmit signaling indicating an NSMF PDU request to the UPF 435. At 475, the UPF 435 transmit signaling indicating a NSMF PDU request to the SMF 445 based on the request. At 480, the PCF 455 may register the response. At 483, the UPF 435 may transmit signaling indicating a first downlink data to the primary UE 115-d.

[0094] At 485, the SMF 445 may transmit signaling to the AMF 420 indicating a PDU session response and at 487, the SMF 445 may transmit signaling to the AMF 420 indicating a notification associated with the response. At 490, the SMF 445 may transmit signaling indicating an IP address configuration to the primary UE 115-d. (e.g., via SMF 445 to the UPF 435, to the primary UE 115-d). An SMF initiated policy association modification may be communicated between the SMF 445 and the PCF 455. At 495, the PDU session may accepted message may be transmitted from the primary' UE 115-d to the dual-steer layer 425. At 497, the SMF 445 may communicate signaling to unsubscribe to the UDM 440.

[0095] FIG. 5 shows an example of a process flow 500 using a correlation value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The process flow 500 may be anextension of process flow 400. The process flow 500 may include a dual-steer layer 525, a secondary UE 115-e, an access network 510 (e.g., access network 210-a and / or 210-b of FIG. 2), an AMF 520 (e.g., the AMF 220-a and / or the AMF 220-b of FIG. 2), a UPF 535 (e.g.. the UPF 235 of FIG. 2), an SMF 545 (e.g., 245 of FIG. 2), a PCF 555 (e.g., the PCF 255 of FIG. 2), a UDM 540 (e.g., the UDM 240 of FIG. 2), and the DN 530 (e.g., the data network 230 of FIG. 2).

[0096] The process flow 500 may generally correspond to the process flow 300. For example, 505, 515, 550, 560, 565, 570, 575, 580, 585. 590, and 595 may correspond to 305, 315. 350, 360, 365, 370, 375. 380, 385. 390, and 395 of FIG. 3, respectively.However, at 503, the dual-steer layer 525 may, based on information received in FIG. 4, trigger the establishment of the dual-steer PDU Session for the secondary' UE 115-e and provide the SMF correlation ID to the secondary' UE 115-e. Additionally, at 580 and 590, the rules may not be provided (e.g.. to the UPF 535 since they were provided for the primary UE 115 (e.g., primary UE 115-d of FIG. 4). Also, at 585. the SMF 545 may select the same dual-steer capable UPF 535 instance of the primary UE 1 15 based on secondary UE 115-e subscription information (which includes the primary UE SUPI). The serving SMF 545 instance may use the subscription information to identify the context of the primary UE 115, and then to select the same UPF 535 instance that was used for primary UE 115 (e.g., the identify of the selected UPF 535 is part of the primary' UE’s context).

[0097] FIG. 6 shows an example of a process flow 600 using a correlation value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The process flow 600 may be an extension of process flow 500. The process flow 600 may include a dual-steer layer 625, a secondary' UE 115-f, an access network 610 (e.g., access network 210-a and / or 210-b of FIG. 2), an AMF 620 (e.g., the AMF 220-a and / or the AMF 220-b of FIG. 2), a UPF 635 (e.g.. the UPF 235 of FIG. 2), an SMF 645 (e.g., 245 of FIG. 2), a PCF 655 (e.g., the PCF 255 of FIG. 2), a UDM 640 (e.g., the UDM 240 of FIG. 2), and the DN 630 (e.g., the data network 230 of FIG. 2).

[0098] The process flow 600 may generally correspond to the process flow 400. For example, 603, 605, 615, 650, 660, 665, 670, 675, 680. 683, 685, 687, 690, 693, 695, and 697 may correspond to 403, 405, 415, 450, 460, 465, 470. 475, 480, 483, 485, 487. 490,493, 495, and 497 of FIG. 3, respectively. However, at 603, the dual-steer layer 625 may, based on information received in FIG. 4, trigger the establishment of the dual-steer PDU Session for the secondary UE 115-f and provide the SMF correlation ID to the secondary UE 115-f. Additionally, at 580 and 590, the rules may not be provided (e.g.. to the UPF 635 since they were provided for the primary UE 115 (e.g., primary UE 115-d of FIG. 4). Also, at 685, the SMF 645 may select the same dual-steer capable UPF 635 instance of the primary UE 115 based on secondary UE 115-f subscription information (which includes the primary UE SUPI). The serving SMF 645 instance may use the subscription information to identify the context of the primary UE 115. and then to select the same UPF 635 instance that was used for primary UE 115 (e.g., the identity of the selected UPF 635 is part of the primary UE’s context). However, at 603, 605, and 615, the SMF 645 may allocate the same IP address for the secondary UE 115-f as allocated for the primary UE 115. Also, traffic rules may not be provided to the secondary UE 115-f since the rules were already received by the primary UE 1 15.

[0099] In some examples, to select the same SMF 645 and UPF 635 for the primary UE 115 and the secondary UE 115-f, a correlation DNN may be used (e.g., re-use existing IE with modified value). The DNN may be similar to the SMF correlation ID with respect to providing an identifier, but the DNN may use existing signaling for the secondary UE 115-f (e.g., no new IES) and existing SMF 645 selection. The primary UE’s SMF may provide a correlation DNN to the primary UE 115 upon successful PDU session establishment for dual-steer. The correlation DNN may enable the network to select the correct serving SMF 645. For example, the DNN may be ■‘intemet.mobileoperatorl.com” and the correlation DNN may be “123dualsteer.mobileoperatorl.com.” The SMF 645 may also configure the correlation DNN in the NRF so that NRF may later associate the correlation DNN to the same SMF 645 instance. The primary UE 115 may pass the correlation DNN to the secondary UE 115-f via the dual-steer layer 625. The secondary UE 115-f may use the correlation DNN from the dual-steer layer 625 layer in a PDU session establishment request.

[0100] FIG. 7 shows an example of a process flow 700 using a DNN value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The process flow 700 may include a primary UE 115-g, an access network 710 (e.g., access network 210-a and / or 210-b of FIG. 2),an AMF 720 (e.g., the AMF 220-a and / or the AMF 220-b of FIG. 2), a UPF 735 (e.g., the UPF 235 of FIG. 2), an SMF 745 (e.g., 245 of FIG. 2), a PCF 755 (e.g., the PCF 255 of FIG. 2), a UDM 740 (e.g., the UDM 240 of FIG. 2), and the DN 730 (e.g., the data network 230 of FIG. 2).

[0101] The process flow 700 may generally correspond to process 300. For example, 705, 715, 750, 760, 765, 770, 775, 780, 785, 790, and 795 may correspond to 305, 315, 350, 360, 365, 370, 375, 380, 385, 390, and 395 of FIG. 3, respectively.

[0102] FIG. 8 shows an example of a process flow 800 using a DNN value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The process flow 800 may be an extension of process flow 700. The process flow 800 may include a dual-steer layer 825, a primary UE f 15-h, an access network 810 (e.g., access network 210-a and / or 210-b of FIG. 2), an AMF 820 (e.g., the AMF 220-a and / or the AMF 220-b of FIG. 2), a UPF 835 (e.g., the UPF 235 of FIG. 2), an SMF 845 (e.g., 245 of FIG. 2), a PCF 855 (e.g.. the PCF 255 of FIG. 2), a UDM 840 (e.g., the UDM 240 of FIG. 2), and the DN 830 (e.g., the data network 230 of FIG. 2).

[0103] The process flow 800 may generally correspond to the process flow 400. For example, 803, 805, 815, 850, 860, 865, 870, 875, 880. 883, 885, 887, 890, 893, 895, and 897 may correspond to 403, 405, 415, 450, 460. 465, 470. 475, 480, 483, 485, 487. 490, 493, 495, and 497 of FIG. 3, respectively. However, at 803, 805, and 815, the SMF 845 may a correlation DNN to be used during the PDU establishment for the secondary' UE 115. Also, at 895 (e.g., or after 815) the primary' UE 115-h may indicate the DS PDU acceptance and forward the correlation DNN to the dual-steer layer 825.

[0104] FIG. 9 shows an example of a process flow 900 using a DNN value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The process flow 900 may be an extension of process flow 800. The process flow 900 may include a dual-steer layer 925, a secondary UE 115-i, an access network 910 (e.g., access network 210-a and / or 210-b of FIG. 2), an AMF 920 (e.g., the AMF 220-a and / or the AMF 220-b of FIG. 2). a UPF 935 (e.g., the UPF 235 of FIG. 2), an SMF 945 (e.g., 245 of FIG. 2), a PCF 955 (e g., the PCF 255of FTG. 2), a UDM 940 (e.g., the UDM 240 of FIG. 2), and the DN 930 (e.g., the data network 230 of FIG. 2).

[0105] The process flow 900 may generally correspond to the process flow 500. For example, 909, 915, 950, 960, 965, 970, 975, 980, 985. 990, and 995 may correspond to 903, 905. 915, 950, 960, 965, 970. 975, 980. 985, 990, and 995 of FIG. 3. respectively. However, at 903, the dual-steer layer 925 may provide the correlation DNN instead of the SMF ID. At 905, the secondary UE 115-i may transmit signaling indicating the correlation DNN instead of the SMF ID.

[0106] FIG. 10 shows an example of a process flow 1000 using the DNN value that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The process flow 1000 may be an extension of process flow 900. The process flow 1000 may include a dual-steer layer 1025, a secondary' UE 115-j, an access network 1010 (e.g., access network 210-a and / or 210-b of FIG. 2), an AMF 1020 (e.g., the AMF 220-a and / or the AMF 220-b of FIG. 2), a UPF 1035 (e.g., the UPF 235 of FIG. 2), an SMF 1045 (e.g., 245 of FIG. 2), a PCF 1055 (e.g., the PCF 255 of FIG. 2), a UDM 1040 (e.g., the UDM 240 of FIG. 2), and the DN 1030 (e.g., the data network 230 of FIG. 2).

[0107] The process flow 1000 may generally correspond to the process flow 600. For example. 1003, 1005, 1015, 1050, 1060. 1065, 1070, 1075, 1080. 1083, 1085, 1087, 1090, 1093, 1095, and 1097 may correspond to 603, 605, 615, 650, 660, 665, 670, 675, 680, 683, 685, 687, 690, 693, 695, and 697 of FIG. 3, respectively.

[0108] FIG. 11 shows an example of a process flow 1100 associated with a UDM context that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The process flow 1100 may include a dual-steer layer 1125, a primary' UE 115-k, a secondary UE 115-1, an AMF 1120 (e.g., the AMF 220-a and / or the AMF 220-b of FIG. 2), an SMF 1145 and (e.g., 245 of FIG. 2).

[0109] In process flow 1100, a shared SMF ID may be stored in the UE UDM context of the primary UE 115-k and in the UE UDM context of a secondary UE 115-1. The UDM context (subscription information) of the primary' UE 115-k and the UE and the secondary UE 115-1 may have shared data fields to facilitate selecting the same SMF1 145. When a UE 115 is allowed, configured, and / or subscribed to use dual-steer, the two subscriptions associated with the dual-steer may be allowing the UDM 1140 to know that the subscription of the primary' UE 115-k is correlated to the subscription of the secondary’ UE 115-1.

[0110] At 1160, the ID of the secondary UE 115-1 (e.g.. SUPI) may be stored in the primary' UE 115-k record. At 1165, the ID of the primary UE 115-k (e g., SUPI) may be stored the record of the secondary' UE 115-1 together with an indication that the correlation is for the dual-steer UE 115.

[0111] During the dual-steer PDU Session establishment for the primary UE 115-k, a serving SMF 1145 is selected for the primary UE 115-k and stored in the UDM 1140, and the serving SMF ID is also stored in the secondary UE 115-1 UDM context so that the AMF 1120 that serves the secondary' UE 115-1 may retrieve the serving SMF ID of the SMF 1145 assigned for the primary' UE 115 (for the same DNN / Single-Network Slice Selection Assistance Information (S-NSSAI) combination).

[0112] At 1170, the AMF 1120 may then select the SMF 1145 identified by serving SMF ID. The AMF 1 120 may select the SMF 1 145 after the primary UE 115-k establishes the PDU session for dual steer and after the SMF 1145 provides information to the UDM 1140. At 1175, UDM 1140 may receive (e.g., from the SMF 1145) the information related to the PDU session for dual steer for the primary UE 115-k, and the UDM 1140 may store the relevant information also in the UDM 1140 record for the secondary UE 115-1. At 1185, dual-steer layer 1125 may establish the correlation with the subscription for dual-steer establishing PDU session.

[0113] In some examples, the primary UE 115-k dual-steer PDU establishment may involve the UDM 1140 updating context of primary UE 115-k and of the secondary UE 115-1 after the SMF 1145 is allocated for primary UE 115-k by adding selected SMF ID to both contexts. The UDM 1140 may' update the AMF 1120 of the secondary UE 115-1 (change in UDM logic, not in signaling). The UDM 1140 may perform this update during registration of the secondary UE 115-1 (e.g., AMF gets the secondary UE 115-1 subscription information for the first time). In some examples, the UDM 1140 may perform this update if the secondary UE 1 15-1 is already registered when the UDM 1 140 context is modified, for example, with separate UDM- AMF interaction due tosubscription updates of UE 1 15 subscription data. In some examples, such as for the secondary^ UE 115-1 PDU establishment, the AMF 1120 may not interact with NRF to select the SMF 1145. Instead, the AMF 1120 may use the SMF ID received from the UDM 1140 to establish the DS PDU Session.

[0114] FIG. 12 shows a block diagram 1200 of a device 1205 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of aspects of a UE 115 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215. and a communications manager 1220. The device 1205, or one or more components of the device 1205 (e.g., the receiver 1210, the transmitter 1215, and the communications manager 1220), may include at least one processor, which may be coupled with at least one memory7, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g.. via one or more buses).

[0115] The receiver 1210 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to SMF instance and UPF instance selection for dual-steer). Information may be passed on to other components of the device 1205. The receiver 1210 may utilize a single antenna or a set of multiple antennas.

[0116] The transmitter 1215 may provide a means for transmitting signals generated by other components of the device 1205. For example, the transmitter 1215 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to SMF instance and UPF instance selection for dual-steer). In some examples, the transmitter 1215 may be co-located with a receiver 1210 in a transceiver module. The transmitter 1215 may utilize a single antenna or a set of multiple antennas.

[0117] The communications manager 1220. the receiver 1210, the transmitter 1215, or various combinations thereof or various components thereof may be examples of means for performing various aspects of SMF instance and user plane function instanceselection for dual-steer as described herein. For example, the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

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

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

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

[0121] The communications manager 1220 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1220 is capable of, configured to, or operable to support a means for transmitting, to a network entity via a first radio access network using a primary protocol stack of the UE, a first request for establishment of a dual-steer PDU session, the dual-steer PDU session including a primary session associated with the primary protocol stack and a secondary session associated with a secondary protocol stack, where the dual-steer protocol stack includes the primary protocol stack and the secondary protocol stack. The communications manager 1220 is capable of, configured to, or operable to support a means for receiving, from the network entity via the first radio access network, a correlation value at the primary protocol stack based on the first request. The communications manager 1220 is capable of, configured to. or operable to support a means for transmitting, to the network entity via a second radio access network using the secondary protocol stack of the UE, a second request for establishment of the secondary session of the dual-steer PDU session, the second request including the correlation value. The communications manager 1220 is capable of, configured to, or operable to support a means for communicating one or more first messages via the first radio access network using the primary session and one or more second messages via the second radio access network using the secondary' session based on the first request and the second request.

[0122] By including or configuring the communications manager 1220 in accordance with examples as described herein, the device 1205 (e.g., at least one processor controlling or otherwise coupled with the receiver 1210, the transmitter 1215, the communications manager 1220, or a combination thereof may support techniques for efficiently and accurately identifying the same SMF and / or UPF that may be used for dual traffic steering, switching, and / or splitting over the two 3GPP access networks (e.g., the first access network and the second access network) of the dual-steering PDU session.

[0123] FIG. 13 shows a block diagram 1300 of a device 1305 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or moreaspects of the present disclosure. The device 1305 may be an example of aspects of a device 1205 or a UE 115 as described herein. The device 1305 may include a receiver 1310. a transmitter 1315. and a communications manager 1320. The device 1305, or one or more components of the device 1305 (e.g., the receiver 1310, the transmitter 1315, and the communications manager 1320), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0124] The receiver 1310 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to SMF instance and UPF instance selection for dual-steer).Information may be passed on to other components of the device 1305. The receiver 1310 may utilize a single antenna or a set of multiple antennas.

[0125] The transmitter 1315 may provide a means for transmitting signals generated by other components of the device 1305. For example, the transmitter 1315 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to SMF instance and UPF instance selection for dual-steer). In some examples, the transmitter 1315 may be co-located with a receiver 1310 in a transceiver module. The transmitter 1315 may utilize a single antenna or a set of multiple antennas.

[0126] The device 1305, or various components thereof, may be an example of means for performing various aspects of SMF instance and UPF instance selection for dual-steer as described herein. For example, the communications manager 1320 may include a DS-PDU session request manager 1325, a correlation value manager 1330, a message communication manager 1335, or any combination thereof. The communications manager 1320 may be an example of aspects of a communications manager 1220 as described herein. In some examples, the communications manager 1320, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1310, the transmitter 1315, or both. For example, the communications manager 1320 may receive information from the receiver 1310, sendinformation to the transmitter 1315, or be integrated in combination with the receiver 1310, the transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.

[0127] The communications manager 1320 may support wireless communications in accordance with examples as disclosed herein. The DS-PDU session request manager 1325 is capable of, configured to, or operable to support a means for transmitting, to a network entity via a first radio access network using a primary protocol stack of the UE, a first request for establishment of a dual-steer PDU session, the dual-steer PDU session including a primary session associated with the primary protocol stack and a secondarysession associated with a secondary protocol stack, where the dual-steer protocol stack includes the primary protocol stack and the secondary protocol stack. The correlation value manager 1330 is capable of, configured to, or operable to support a means for receiving, from the network entity via the first radio access network, a correlation value at the primary protocol stack based on the first request. The DS-PDU session request manager 1325 is capable of, configured to, or operable to support a means for transmitting, to the network entity via a second radio access network using the secondary- protocol stack of the UE, a second request for establishment of the secondary session of the dual-steer PDU session, the second request including the correlation value. The message communication manager 1335 is capable of, configured to, or operable to support a means for communicating one or more first messages via the first radio access network using the primary session and one or more second messages via the second radio access network using the secondary session based on the first request and the second request.

[0128] FIG. 14 shows a block diagram 1400 of a communications manager 1420 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The communications manager 1420 maybe an example of aspects of a communications manager 1220, a communications manager 1320, or both, as described herein. The communications manager 1420, or various components thereof, may be an example of means for performing various aspects of SMF instance and UPF instance selection for dual-steer as described herein. For example, the communications manager 1420 may include a DS-PDU session request manager 1425. a correlation value manager 1430, a message communicationmanager 1435, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0129] The communications manager 1420 may support wireless communications in accordance with examples as disclosed herein. The DS-PDU session request manager 1425 is capable of, configured to, or operable to support a means for transmitting, to a network entity via a first radio access network using a primary protocol stack of the UE, a first request for establishment of a dual-steer PDU session, the dual-steer PDU session including a primary session associated with the primary protocol stack and a secondarysession associated with a secondary protocol stack, where the dual-steer protocol stack includes the primary protocol stack and the secondary protocol stack. The correlation value manager 1430 is capable of, configured to, or operable to support a means for receiving, from the network entity via the first radio access network, a correlation value at the primary protocol stack based on the first request. In some examples, the DS-PDU session request manager 1425 is capable of, configured to, or operable to support a means for transmitting, to the network entity via a second radio access network using the secondary protocol stack of the UE, a second request for establishment of the secondary session of the dual-steer PDU session, the second request including the correlation value. The message communication manager 1435 is capable of, configured to, or operable to support a means for communicating one or more first messages via the first radio access network using the primary session and one or more second messages via the second radio access network using the secondary- session based on the first request and the second request.

[0130] In some examples, to support receiving, from the network entity, the correlation value, the DS-PDU session request manager 1425 is capable of, configured to, or operable to support a means for receiving a dual-steer PDU session request accept message including the correlation value based on the first request, the dual-steer PDU session request accept message indicating activation of the primary session in the primary protocol stack session.

[0131] In some examples, the correlation value manager 1430 is capable of, configured to, or operable to support a means for communicating, via a dual-steer layer, the correlation value from the primary protocol stack to the secondary- protocol stack.

[0132] In some examples, the DS-PDU session request manager 1425 is capable of, configured to, or operable to support a means for receiving a dual-steer PDU session request accept message based on the second request, the dual-steer PDU session request accept message indicating activation of the secondary session of the dual-steer PDU session.

[0133] In some examples, to support receiving, from the network entity, the correlation value, the correlation value manager 1430 is capable of, configured to, or operable to support a means for receiving the correlation value from a serving SMF of a network, where the correlation value is indicative of the serving SMF.

[0134] In some examples, to support transmitting, to the network entity, the correlation value to the secondary protocol stack, the correlation value manager 1430 is capable of, configured to, or operable to support a means for transmitting the correlation value to the serving SMF of a network via an access and mobility function.

[0135] In some examples, the dual-steer PDU session is associated with a same UPF for the primary protocol stack and the secondary protocol stack.

[0136] In some examples, the correlation value includes a SMF ID or a DNN ID.

[0137] In some examples, an internet protocol address for the dual-steer PDU session is the same as an IP address for the primary protocol stack and for the secondary protocol stack.

[0138] FIG. 15 shows a diagram of a system 1500 including a device 1505 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The device 1505 may be an example of or include the components of a device 1205, a device 1305, or a UE 115 as described herein. The device 1505 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1505 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1520, an input / output (I / O) controller 1510, a transceiver 1515, an antenna 1525. at least one memory 1530. code 1535. and at least one processor 1540. These components may be in electronic communication or otherwise coupled (e.g.,operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1545).

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

[0140] In some cases, the device 1505 may include a single antenna 1525. However, in some other cases, the device 1505 may have more than one antenna 1525, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1515 may communicate bi-directionally, via the one or more antennas 1525. wired, or wireless links as described herein. For example, the transceiver 1515 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1515 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1525 for transmission, and to demodulate packets received from the one or more antennas 1525. The transceiver 1515, or the transceiver 1515 and one or more antennas 1525, may be an example of a transmitter 1215, a transmitter 1315, a receiver 1210, a receiver 1310, or any combination thereof or component thereof, as described herein.

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

[0142] The at least one processor 1540 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the at least one processor 1540 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 1540. The at least one processor 1540 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory' 1530) to cause the device 1505 to perform various functions (e.g., functions or tasks supporting SMF instance and UPF instance selection for dual-steer). For example, the device 1505 or a component of the device 1505 may include at least one processor 1540 and at least one memory' 1530 coupled with or to the at least one processor 1540, the at least one processor 1540 and at least one memory 1530 configured to perform various functions described herein. In some examples, the at least one processor 1540 may include multiple processors and the at least one memory' 1530 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1540 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry' (including, for example, one or both of processor circuitry (which may include the at least one processor 1540) and memory' circuitry' (which may include the at least one memory 1530)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1540 or a processing system including the at least one processor 1540 may be configured to, configurable to, or operable to cause the device 1505 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operableto” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory- 1530 or otherwise, to perform one or more of the functions described herein.

[0143] The communications manager 1520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1520 is capable of, configured to, or operable to support a means for transmitting, to a network entity via a first radio access network using a primary protocol stack of the UE. a first request for establishment of a dual-steer PDU session, the dual-steer PDU session including a primary session associated with the primary protocol stack and a secondary session associated with a secondary protocol stack, where the dual-steer protocol stack includes the primary protocol stack and the secondary' protocol stack. The communications manager 1520 is capable of, configured to, or operable to support a means for receiving, from the network entity via the first radio access network, a correlation value at the primary protocol stack based on the first request. The communications manager 1520 is capable of, configured to, or operable to support a means for transmitting, to the network entity via a second radio access network using the secondary protocol stack of the UE, a second request for establishment of the secondary session of the dual-steer PDU session, the second request including the correlation value. The communications manager 1520 is capable of, configured to, or operable to support a means for communicating one or more first messages via the first radio access network using the primary session and one or more second messages via the second radio access network using the secondary session based on the first request and the second request.

[0144] By including or configuring the communications manager 1520 in accordance with examples as described herein, the device 1505 may support techniques for efficiently and accurately identify ing the same SMF and / or UPF that may be used for dual traffic steering, switching, and / or splitting over the two 3GPP access networks (e.g., the first access network and the second access network) of the dual-steering PDU session.

[0145] In some examples, the communications manager 1520 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1515, the one or more antennas 1525, or anycombination thereof. Although the communications manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1520 may be supported by or performed by the at least one processor 1540, the at least one memory 1530, the code 1535, or any combination thereof. For example, the code 1535 may include instructions executable by the at least one processor 1540 to cause the device 1505 to perform various aspects of SMF instance and UPF instance selection for dual-steer as described herein, or the at least one processor 1540 and the at least one memory 1530 may be otherwise configured to, individually or collectively, perform or support such operations.

[0146] FIG. 16 shows a block diagram 1600 of a device 1605 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The device 1605 may be an example of aspects of a network entity 105 as described herein. The device 1605 may include a receiver 1610, a transmitter 1615. and a communications manager 1620. The device 1605, or one or more components of the device 1605 (e.g., the receiver 1610, the transmitter 1615, and the communications manager 1620), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

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

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

[0149] The communications manager 1620, the receiver 1610, the transmitter 1615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of SMF instance and UPF instance selection for dual-steer as described herein. For example, the communications manager 1620, the receiver 1610, the transmitter 1615, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

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

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

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

[0153] The communications manager 1620 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1620 is capable of, configured to, or operable to support a means for obtaining, via a first radio access network from a primary protocol stack of a UE, a first request for establishment of a dual-steer PDU session, the dual-steer PDU session including a primary session associated with the primary protocol stack and a secondary session associated with a secondary protocol stack, where a dual-steer protocol stack of the UE includes the primary protocol stack and the secondary' protocol stack. The communications manager 1620 is capable of, configured to. or operable to support a means for outputting, to the UE via the first radio access network, a correlation value at the primary protocol stack based on the first request. The communications manager 1620 is capable of, configured to, or operable to support a means for obtaining, via a second radio access network from the secondary protocol stack of the UE, a second request for establishment of the secondary session of the dual-steer PDU session, the second request including the correlation value. The communications manager 1620 is capable of, configured to, or operable to support a means for communicating one or more first messages via the first radio access network using the primary session and one or more second messages via the second radio access network using the secondary session based on the first request and the second request.

[0154] Additionally, or alternatively, the communications manager 1620 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1620 is capable of, configured to, or operable to support a means for obtaining a request for establishment of a dual-steer PDU session from a primary protocol stack of a dual-steer protocol stack of a UE, where a subscription of the primary protocol stack is correlated with a subscription of a secondary' protocol stack of the dual-steer protocol stack. The communications manager 1620 is capable of, configured to, or operable to support a means for establishing, based on the subscription of the primary protocol stack being correlated with the subscription of a secondary protocol stack, a primary session via a first radio access network using a first unified data management context for the primary' protocol stack and a secondary' session via a second radio access network using a second unified data management context for the secondary’ protocol stack, the dual-steer PDU session including the primary' session that is associated with the primary' protocol stack and the secondary session that is associated with the secondary' protocol stack, the first unified data management context including a serving SMF ID and the second unified data management context including the serving SMF ID. The communications manager 1620 is capable of, configured to, or operable to support a means for communicating one or more first messages via the first radio access network using the primary session and one or more second messages via the second radio access network using the secondary’ session.

[0155] By including or configuring the communications manager 1620 in accordance with examples as described herein, the device 1605 (e.g., at least one processor controlling or otherwise coupled with the receiver 1610, the transmitter 161 , the communications manager 1620, or a combination thereof may support techniques for efficiently and accurately identifying the same SMF and / or UPF that may be used for dual traffic steering, switching, and / or splitting over the two 3GPP access networks (e.g., the first access network and the second access network) of the dual-steering PDU session.

[0156] FIG. 17 shows a block diagram 1700 of a device 1705 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The device 1705 may be an example of aspects of adevice 1605 or a network entity 105 as described herein. The device 1705 may include a receiver 1710, a transmitter 1715, and a communications manager 1720. The device 1705. or one or more components of the device 1705 (e.g., the receiver 1710, the transmitter 1715. and the communications manager 1720), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

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

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

[0159] The device 1705, or various components thereof, may be an example of means for performing various aspects of SMF instance and UPF instance selection fordual-steer as described herein. For example, the communications manager 1720 may include a DS-PDU session request manager 1725, a correlation value manager 1730, a message communication manager 1735, a DS-PDU session establishment manager 1740. or any combination thereof. The communications manager 1720 may be an example of aspects of a communications manager 1620 as described herein. In some examples, the communications manager 1720, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1710, the transmitter 1715. or both. For example, the communications manager 1720 may receive information from the receiver 1710, send information to the transmitter 1715, or be integrated in combination with the receiver 1710, the transmitter 1715, or both to obtain information, output information, or perform various other operations as described herein.

[0160] The communications manager 1720 may support wireless communications in accordance with examples as disclosed herein. The DS-PDU session request manager 1725 is capable of, configured to, or operable to support a means for obtaining, via a first radio access network from a primary protocol stack of a UE, a first request for establishment of a dual-steer PDU session, the dual-steer PDU session including a primary session associated with the primary protocol stack and a secondary session associated with a secondary protocol stack, where a dual-steer protocol stack of the UE includes the primary protocol stack and the secondary protocol stack. The correlation value manager 1730 is capable of, configured to, or operable to support a means for outputting, to the UE via the first radio access network, a correlation value at the primary protocol stack based on the first request. The DS-PDU session request manager 1725 is capable of, configured to, or operable to support a means for obtaining, via a second radio access network from the secondary protocol stack of the UE, a second request for establishment of the secondary session of the dual-steer PDU session, the second request including the correlation value. The message communication manager 1735 is capable of, configured to, or operable to support a means for communicating one or more first messages via the first radio access network using the primary session and one or more second messages via the second radio access network using the secondary session based on the first request and the second request.

[0161] Additionally, or alternatively, the communications manager 1720 may support wireless communications in accordance with examples as disclosed herein. The DS-PDU session request manager 1725 is capable of, configured to, or operable to support a means for obtaining a request for establishment of a dual-steer PDU session from a primary protocol stack of a dual-steer protocol stack of a UE, where a subscription of the primary protocol stack is correlated with a subscription of a secondary' protocol stack of the dual-steer protocol stack. The DS-PDU session establishment manager 1740 is capable of, configured to, or operable to support a means for establishing, based on the subscription of the primary protocol stack being correlated with the subscription of a secondary protocol stack, a primary session via a first radio access network using a first unified data management context for the primary protocol stack and a secondary' session via a second radio access network using a second unified data management context for the secondary protocol stack, the dual-steer PDU session including the primary session that is associated with the primary protocol stack and the secondary session that is associated with the secondary protocol stack, the first unified data management context including a serving SMF ID and the second unified data management context including the serving SMF ID. The message communication manager 1735 is capable of, configured to, or operable to support a means for communicating one or more first messages via the first radio access network using the primary' session and one or more second messages via the second radio access network using the secondary' session.

[0162] FIG. 18 shows a block diagram 1800 of a communications manager 1820 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The communications manager 1820 may be an example of aspects of a communications manager 1620, a communications manager 1720, or both, as described herein. The communications manager 1820, or various components thereof, may be an example of means for performing various aspects of SMF instance and UPF instance selection for dual-steer as described herein. For example, the communications manager 1820 may include a DS-PDU session request manager 1825, a correlation value manager 1830, a message communication manager 1835, a DS-PDU session establishment manager 1840, a SMF manager 1845. an ID manager 1850, a UDM context manager 1855, or any combination thereof. Eachof these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses) which may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0163] The communications manager 1820 may support wireless communications in accordance with examples as disclosed herein. The DS-PDU session request manager 1825 is capable of, configured to, or operable to support a means for obtaining, via a first radio access network from a primary protocol stack of a UE, a first request for establishment of a dual-steer PDU session, the dual-steer PDU session including a primary session associated with the primary protocol stack and a secondary session associated with a secondary protocol stack, where a dual-steer protocol stack of the UE includes the primary protocol stack and the secondary' protocol stack. The correlation value manager 1830 is capable of, configured to, or operable to support a means for outputting, to the UE via the first radio access network, a correlation value at the primary' protocol stack based on the first request. In some examples, the DS-PDU session request manager 1825 is capable of, configured to, or operable to support a means for obtaining, via a second radio access network from the secondary protocol stack of the UE, a second request for establishment of the secondary session of the dualsteer PDU session, the second request including the correlation value. The message communication manager 1835 is capable of, configured to, or operable to support a means for communicating one or more first messages via the first radio access netw ork using the primary' session and one or more second messages via the second radio access network using the secondary session based on the first request and the second request.

[0164] In some examples, the correlation value manager 1830 is capable of, configured to, or operable to support a means for associating the correlation value with the primary' session for establishment of the dual-steer PDU session.

[0165] In some examples, the SMF manager 1845 is capable of, configured to, or operable to support a means for selecting a same SMF for the primary protocol stack and the secondary' protocol stack based on the correlation value.

[0166] In some examples, the message communication manager 1835 is capable of, configured to, or operable to support a means for outputting data to the dual-steering PDU session via one of the first radio access network using the primary session or the second radio access network using the secondary session.

[0167] In some examples, to support outputting, to the UE via the first radio access network, the correlation value, the DS-PDU session request manager 1825 is capable of, configured to, or operable to support a means for outputting a dual-steer PDU session request accept message including the correlation value based on the first request, the dual-steer PDU session request accept message indicating activation of the primary session of the dual-steer PDU session.

[0168] In some examples, the network entity' includes one or more of a SMF manager, an AMF function, a NRF, or any combination thereof.

[0169] In some examples, the DS-PDU session request manager 1825 is capable of, configured to, or operable to support a means for outputting a dual-steer PDU session request accept message based on the second request, the dual-steer PDU session request accept message indicating activation of the secondary session of the dual-steer PDU session.

[0170] In some examples, to support outputting, to the UE via the first radio access network, the correlation value, the correlation value manager 1830 is capable of, configured to, or operable to support a means for outputting the correlation value from a serving SMF of a network, where the correlation value is indicative of the serving SMF.

[0171] In some examples, to support obtaining, via a second radio access network from the secondary protocol stack of the UE, a second request, the correlation value manager 1830 is capable of, configured to, or operable to support a means for obtaining the correlation value at the serving SMF of a network via an access and mobility' function.

[0172] In some examples, the dual-steer PDU session is associated with a same UPF for the primary protocol stack and the secondary protocol stack.

[0173] In some examples, the correlation value includes a SMF ID or a DNN ID.

[0174] In some examples, an internet protocol address for the dual-steer PDU session is the same as an IP address for the primary protocol stack and for the secondary protocol stack.

[0175] Additionally, or alternatively, the communications manager 1820 may support wireless communications in accordance with examples as disclosed herein. In some examples, the DS-PDU session request manager 1825 is capable of, configured to, or operable to support a means for obtaining a request for establishment of a dual-steer PDU session from a primary protocol stack of a dual-steer protocol stack of a UE, where a subscription of the primary protocol stack is correlated with a subscription of a secondary7protocol stack of the dual-steer protocol stack. The DS-PDU session establishment manager 1840 is capable of, configured to, or operable to support a means for establishing, based on the subscription of the primary protocol stack being correlated with the subscription of a secondary protocol stack, a primary session via a first radio access network using a first unified data management context for the primary' protocol stack and a secondary' session via a second radio access network using a second unified data management context for the secondary protocol stack, the dual-steer PDU session including the primary session that is associated with the primary protocol stack and the secondary session that is associated with the secondary protocol stack, the first unified data management context including a serving SMF ID and the second unified data management context including the serving SMF ID. In some examples, the message communication manager 1835 is capable of. configured to, or operable to support a means for communicating one or more first messages via the first radio access network using the primary' session and one or more second messages via the second radio access network using the secondary session.

[0176] In some examples, the network entity7includes an access and mobility management function or a unified data management function.

[0177] In some examples, the ID manager 1850 is capable of, configured to, or operable to support a means for storing the serving SMF ID for a SMF in the firstunified data management context for the primary protocol stack and in the second unified data management context for the secondary protocol stack after the SMF is allocated for the dual-steer PDU session.

[0178] In some examples, to support establishing the secondary session, the DS- PDU session establishment manager 1840 is capable of. configured to, or operable to support a means for establishing, via an access and mobility management function associated with the network entity, the secondary session using the serving SMF ID received from a unified data management associated with the network entity.

[0179] In some examples, the network entity may include an AMF function, a first UDM function, a second UDM function, or any combination thereof.

[0180] In some examples, the UDM context manager 1855 is capable of. configured to, or operable to support a means for generating the first unified data management context for the primary' protocol stack, the first unified data management context including the serving SMF ID.

[0181] In some examples, the ID manager 1850 is capable of. configured to, or operable to support a means for storing the serving SMF ID in the second unified data management context for the secondary' protocol stack.

[0182] In some examples, the correlation value includes a SMF ID or a DNN ID.

[0183] In some examples, an internet protocol address for the dual-steer PDU session is the same as an IP address for the primary protocol stack and for the secondary protocol stack.

[0184] In some examples, to support establishing the secondary session, the DS- PDU session establishment manager 1840 is capable of, configured to, or operable to support a means for copying the serving SMF ID from the first UDM context into the second UDM context based on additional information associated with the first UDM context.

[0185] In some examples, the additional information may include a reference to the second UDM context, the subscription identity of the secondary' protocol stack, or a combination thereof

[0186] FIG. 19 shows a diagram of a system 1900 including a device 1905 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The device 1905 may be an example of or include the components of a device 1605, a device 1705, or a network entity 105 as described herein. The device 1905 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device 1905 may include components that support outputting and obtaining communications, such as a communications manager 1920, a transceiver 1910, an antenna 1915, at least one memory 1925, code 1930, and at least one processor 1935. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g.. a bus 1940).

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

[0188] The at least one memory 1925 may include RAM, ROM, or any combination thereof. The at least one memory 1925 may store computer-readable, computerexecutable code 1930 including instructions that, when executed by one or more of the at least one processor 1935, cause the device 1905 to perform various functions described herein. The code 1930 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1930 may not be directly executable by a processor of the at least one processor 1935 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1925 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1935 may include multiple processors and the at least one memory 1925 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system).

[0189] The at least one processor 1935 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU. an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the at least one processor 1935 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 1935. The at least one processor 1935 may be configured toexecute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1925) to cause the device 1905 to perform various functions (e.g., functions or tasks supporting SMF instance and UPF instance selection for dual-steer). For example, the device 1905 or a component of the device 1905 may include at least one processor 1935 and at least one memory 1925 coupled with one or more of the at least one processor 1935, the at least one processor 1935 and the at least one memory 1925 configured to perform various functions described herein. The at least one processor 1935 may be an example of a cloud-computing platform (e g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1930) to perform the functions of the device 1905. The at least one processor 1935 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1905 (such as within one or more of the at least one memory 1925). In some examples, the at least one processor 1935 may include multiple processors and the at least one memory 1925 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1935 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry' (including, for example, one or both of processor circuitry' (which may include the at least one processor 1935) and memory circuitry (which may include the at least one memory 1925)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1935 or a processing system including the at least one processor 1935 may be configured to, configurable to, or operable to cause the device 1905 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1925 or otherwise, to perform one or more of the functions described herein.

[0190] In some examples, a bus 1940 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1940 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of the device 1905, or between different components of the device 1905 that may be co-located or located in different locations (e.g., where the device 1905 may refer to a system in which one or more of the communications manager 1920, the transceiver 1910, the at least one memory 1925, the code 1930, and the at least one processor 1935 may be located in one of the different components or divided between different components).

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

[0192] The communications manager 1920 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1920 is capable of, configured to, or operable to support a means for obtaining, via a first radio access network from a primary protocol stack of a UE, a first request for establishment of a dual-steer PDU session, the dual-steer PDU session including a primary session associated with the primary protocol stack and a secondary session associated with a secondary protocol stack, where a dual-steer protocol stack of the UE includes the primary protocol stack and the secondary protocol stack. The communications manager 1920 is capable of, configured to, or operable to support a means for outputting, to the UE via the first radio access network, a correlation value at the primary protocol stack based on the first request. The communications manager 1920 is capable of. configured to, or operable to support a means for obtaining, via asecond radio access network from the secondary protocol stack of the UE, a second request for establishment of the secondary session of the dual-steer PDU session, the second request including the correlation value. The communications manager 1920 is capable of, configured to, or operable to support a means for communicating one or more first messages via the first radio access network using the primary session and one or more second messages via the second radio access network using the secondary session based on the first request and the second request.

[0193] Additionally, or alternatively, the communications manager 1920 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1920 is capable of, configured to, or operable to support a means for obtaining a request for establishment of a dual-steer PDU session from a primary' protocol stack of a dual-steer protocol stack of a UE, where a subscription of the primary protocol stack is correlated with a subscription of a secondary protocol stack of the dual-steer protocol stack. The communications manager 1920 is capable of, configured to, or operable to support a means for establishing, based on the subscription of the primary protocol stack being correlated with the subscription of a secondary protocol stack, a primary session via a first radio access network using a first unified data management context for the primary protocol stack and a secondary session via a second radio access network using a second unified data management context for the secondary' protocol stack, the dual-steer PDU session including the primary' session that is associated with the primary protocol stack and the secondary' session that is associated with the secondary protocol stack, the first unified data management context including a serving SMF ID and the second unified data management context including the serving SMF ID. The communications manager 1920 is capable of, configured to, or operable to support a means for communicating one or more first messages via the first radio access network using the primary session and one or more second messages via the second radio access network using the secondary session.

[0194] By including or configuring the communications manager 1920 in accordance with examples as described herein, the device 1905 may support techniques for efficiently and accurately identifying the same SMF and / or UPF that may be used for dual traffic steering, switching, and / or splitting over the two 3GPP access networks(e.g., the first access network and the second access network) of the dual-steering PDU session.

[0195] In some examples, the communications manager 1920 may be configured to perform various operations (e.g.. receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1910, the one or more antennas 1915 (e g., where applicable), or any combination thereof. Although the communications manager 1920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1920 may be supported by or performed by the transceiver 1910, one or more of the at least one processor 1935, one or more of the at least one memory 1925, the code 1930, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1935, the at least one memory 1925, the code 1930, or any combination thereof). For example, the code 1930 may include instructions executable by one or more of the at least one processor 1935 to cause the device 1905 to perform various aspects of SMF instance and UPF instance selection for dual-steer as described herein, or the at least one processor 1935 and the at least one memory' 1925 may be otherwise configured to, individually or collectively, perform or support such operations.

[0196] FIG. 20 shows a flowchart illustrating a method 2000 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The operations of the method 2000 may be implemented by a UE or its components as described herein. For example, the operations of the method 2000 may be performed by a UE 115 as described with reference to FIGs. 1 through 15. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0197] At 2005, the method may include transmitting, to a network entity via a first radio access network using a primary protocol stack of the UE, a first request for establishment of a PDU session, the PDU session including a primary PDU session associated with the primary' protocol stack and a secondary PDU session associated with a secondary’ protocol stack, where the protocol stack includes the primary protocol stackand the secondary protocol stack. The operations of block 2005 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed by a DS-PDU session request manager 1425 as described with reference to FIG. 14.

[0198] At 2010, the method may include receiving, from the network entity via the first radio access network, a correlation value at the primary' protocol stack based on the first request. The operations of block 2010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed by a correlation value manager 1430 as described with reference to FIG. 14.

[0199] At 2015, the method may include transmitting, to the network entity’ via a second radio access network using the secondary' protocol stack of the UE, a second request for establishment of the secondary PDU session, the second request including the correlation value. The operations of block 2015 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed by a DS-PDU session request manager 1425 as described with reference to FIG. 14.

[0200] At 2020, the method may include communicating one or more first messages via the first radio access network using the primary PDU session and one or more second messages via the second radio access network using the secondary PDU session based on the first request and the second request. The operations of block 2020 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2020 may be performed by a message communication manager 1435 as described with reference to FIG. 14.

[0201] FIG. 21 shows a flowchart illustrating a method 2100 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The operations of the method 2100 may be implemented by a UE or its components as described herein. For example, the operations of the method 2100 may be performed by a UE 115 as described with reference to FIGs. 1 through 15. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the describedfunctions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0202] At 2105, the method may include transmitting, to a network entity via a first radio access network using a primary' protocol stack of the UE, a first request for establishment of a PDU session, the PDU session including a primary session associated with the primary protocol stack and a secondary session associated with a secondary protocol stack, where the protocol stack includes the primary protocol stack and the secondary' protocol stack. The operations of block 2105 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2105 may be performed by a DS-PDU session request manager 1425 as described yvith reference to FIG. 14.

[0203] At 2110, the method may include receiving, from the netyvork entity via the first radio access netyvork, a correlation value at the primary protocol stack based on the first request. The operations of block 2110 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2110 may be performed by a correlation value manager 1430 as described yvith reference to FIG. 14.

[0204] At 2115, the method may include communicating, via a dual-steer layer, the correlation value from the primary protocol stack to the secondary protocol stack. The operations of block 2115 may be performed in accordance yvith examples as disclosed herein. In some examples, aspects of the operations of 2115 may be performed by a correlation value manager 1430 as described yvith reference to FIG. 14.

[0205] At 2120, the method may include transmitting, to the network entity via a second radio access network using the secondary protocol stack of the UE, a second request for establishment of the secondary session of the PDU session, the second request including the correlation value. The operations of block 2120 may be performed in accordance yvith examples as disclosed herein. In some examples, aspects of the operations of 2120 may be performed by a DS-PDU session request manager 1425 as described with reference to FIG. 14.

[0206] At 2125, the method may include communicating one or more first messages via the first radio access netyvork using the primary session and one or more secondmessages via the second radio access network using the secondary session based on the first request and the second request. The operations of block 2125 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2125 may be performed by a message communication manager 1435 as described with reference to FIG. 14.

[0207] FIG. 22 shows a flowchart illustrating a method 2200 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The operations of the method 2200 may be implemented by a network entity’ or its components as described herein. For example, the operations of the method 2200 may be performed by a network entity as described with reference to FIGs. 1 through 11 and 16 through 19. In some examples, a network entity7may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

[0208] At 2205, the method may include obtaining, via a first radio access network from a primary’ protocol stack of a UE, a first request for establishment of a PDU session, the PDU session including a primary’ PDU session associated with the primary' protocol stack and a secondary PDU session associated with a secondary protocol stack, where a protocol stack of the UE includes the primary protocol stack and the secondary protocol stack. The operations of block 2205 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2205 may be performed by a DS-PDU session request manager 1825 as described with reference to FIG. 18.

[0209] At 2210, the method may include outputting, to the UE via the first radio access network, a correlation value at the primary protocol stack based on the first request. The operations of block 2210 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2210 may be performed by a correlation value manager 1830 as described with reference to FIG. 18.

[0210] At 2215, the method may include obtaining, via a second radio access network from the secondary protocol stack of the UE, a second request for establishment of the secondary' PDU session of the PDU session, the second requestincluding the correlation value. The operations of block 2215 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2215 may be performed by a DS-PDU session request manager 1825 as described with reference to FIG. 18.

[0211] At 2220, the method may include communicating one or more first messages via the first radio access network using the primary PDU session and one or more second messages via the second radio access network using the secondary PDU session based on the first request and the second request. The operations of block 2220 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2220 may be performed by a message communication manager 1835 as described with reference to FIG. 18.

[0212] FIG. 23 shows a flowchart illustrating a method 2300 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The operations of the method 2300 may be implemented by a network entity or its components as described herein. For example, the operations of the method 2300 may be performed by a network entity as described with reference to FIGs. 1 through 11 and 16 through 19. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity’ may perform aspects of the described functions using special-purpose hardware.

[0213] At 2305, the method may include obtaining, via a first radio access network from a primary’ protocol stack of a UE, a first request for establishment of a PDU session, the PDU session including a primary PDU session associated with the primary protocol stack and a secondary PDU session associated with a secondary protocol stack, where a dual-steer protocol stack of the UE includes the primary protocol stack and the secondary protocol stack. The operations of block 2305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2305 may be performed by a DS-PDU session request manager 1825 as described with reference to FIG. 18.

[0214] At 2310, the method may include outputting, to the UE via the first radio access network, a correlation value at the primary’ protocol stack based on the firstrequest. The operations of block 2310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2310 may be performed by a correlation value manager 1830 as described with reference to FIG. 18.

[0215] At 2315, the method may include associating the correlation value with the primary PDU session for establishment of the PDU session. The operations of block 2315 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2315 may be performed by a correlation value manager 1830 as described with reference to FIG. 18.

[0216] At 2320, the method may include obtaining, via a second radio access network from the secondary protocol stack of the UE. a second request for establishment of the secondary PDU session of the PDU session, the second request including the correlation value. The operations of block 2320 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2320 may be performed by a DS-PDU session request manager 1825 as described with reference to FIG. 18.

[0217] At 2325, the method may include communicating one or more first messages via the first radio access network using the primary PDU session and one or more second messages via the second radio access network using the secondary' PDU session based on the first request and the second request. The operations of block 2325 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2325 may be performed by a message communication manager 1835 as described with reference to FIG. 18.

[0218] FIG. 24 show s a flow chart illustrating a method 2400 that supports SMF instance and UPF instance selection for dual-steer in accordance with one or more aspects of the present disclosure. The operations of the method 2400 may be implemented by a network entity or its components as described herein. For example, the operations of the method 2400 may be performed by a network entity as described with reference to FIGs. 1 through 11 and 16 through 19. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardw are.

[0219] At 2405, the method may include obtaining a request for establishment of a PDU session from a primary protocol stack of a protocol stack of a UE, where a subscription of the primary protocol stack is correlated with a subscription of a secondary protocol stack of the protocol stack. The operations of block 2405 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2405 may be performed by a DS-PDU session request manager 1825 as described with reference to FIG. 18.

[0220] At 2410, the method may include establishing, based on the subscription of the primary protocol stack being correlated with the subscription of a secondary protocol stack, a primary session via a first radio access network using a first unified data management context for the primary protocol stack and a secondary session via a second radio access network using a second unified data management context for the secondary protocol stack, the PDU session including the primary session that is associated with the primary protocol stack and the secondary session that is associated with the secondary protocol stack, the first unified data management context including a serving SMF ID and the second unified data management context including the serving SMF ID. The operations of block 2410 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2410 may be performed by a DS-PDU session establishment manager 1840 as described with reference to FIG. 18.

[0221] At 2415, the method may include communicating one or more first messages via the first radio access network using the primary session and one or more second messages via the second radio access network using the secondary session. The operations of block 2415 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2415 may be performed by a message communication manager 1835 as described with reference to FIG. 18.

[0222] FIG. 25 shows a flowchart illustrating a method 2500 that supports SMF instance and UPF instance selection for in accordance with one or more aspects of the present disclosure. The operations of the method 2500 may be implemented by a network entity or its components as described herein. For example, the operations of the method 2500 may be performed by a network entity as described with reference to FIGs. 1 through 11 and 16 through 19. In some examples, a network entity may executea set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

[0223] At 2505, the method may include obtaining a request for establishment of a PDU session from a primary protocol stack of a protocol stack of a UE. where a subscription of the primary protocol stack is correlated with a subscription of a secondary protocol stack of the protocol stack. The operations of block 2505 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2505 may be performed by a DS-PDU session request manager 1825 as described with reference to FIG. 18.

[0224] At 2510, the method may include storing the serving SMF ID for a SMF in the first unified data management context for the primary protocol stack and in the second unified data management context for the secondary' protocol stack after the SMF is allocated for the PDU session. The operations of block 2510 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2510 may be performed by an ID manager 1850 as described with reference to FIG. 18.

[0225] At 2515, the method may include establishing, based on the subscription of the primary protocol stack being correlated with the subscription of a secondary protocol stack, a primary session via a first radio access network using a first unified data management context for the primary protocol stack and a secondary session via a second radio access network using a second unified data management context for the secondary’ protocol stack, the PDU session including the primary session that is associated with the primary protocol stack and the secondary session that is associated with the secondary protocol stack, the first unified data management context including a serving SMF ID and the second unified data management context including the serving SMF ID. The operations of block 2515 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2515 may be performed by a DS-PDU session establishment manager 1840 as described with reference to FIG. 18.

[0226] At 2520, the method may include communicating one or more first messages via the first radio access network using the primary session and one or more second messages via the second radio access network using the secondary' session. The operations of block 2520 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2520 may be performed by a message communication manager 1835 as described with reference to FIG. 18.

[0227] The following aspects are given by way of illustration. Examples of the following aspects may be combined with examples or embodiments shown or discussed in relation to the figures or elsewhere herein.

[0228] Aspect 1 is a method for wireless communications at a UE including a protocol stack, that includes transmitting, to a network entity via a first radio access network using a primary protocol stack of the UE, a first request for establishment of a PDU session, the PDU session comprising a primary' PDU session associated with the primary’ protocol stack and a secondary PDU session associated with a secondary protocol stack, wherein the protocol stack comprises the primary protocol stack and the secondary protocol stack; receiving, from the network entity via the first radio access network, a correlation value at the primary' protocol stack based at least in part on the first request; transmitting, to the network entity via a second radio access network using the secondary' protocol stack of the UE, a second request for establishment of the secondary PDU session, the second request comprising the correlation value; and communicating one or more first messages via the first RAN using the primary' PDU session and one or more second messages via the second RAN using the secondary PDU session based at least in part on the first request and the second request.

[0229] In Aspect 2, the method of aspect 1 where receiving, from the network entity, the correlation value further includes: receiving a PDU session request accept message comprising the correlation value based at least in part on the first request, the PDU session request accept message indicating activation of the primary PDU session in the primary protocol stack.

[0230] In Aspect 3, the method of any of aspects 1 through 2 includes communicating, via a dual-steer layer, the correlation value from the primary' protocol stack to the secondary' protocol stack.

[0231] In Aspect 4, the method of any aspects 1 through 3 includes receiving a PDU session request accept message based at least in part on the second request, the PDU session request accept message indicating activation of the secondary PDU session.

[0232] In Aspect 5, the method of any of aspects 1 through 4 includes receiving, from the network entity, the correlation value further includes receiving the correlation value from a serving SMF of a network, wherein the correlation value is indicative of the serving SMF.

[0233] In Aspect 6 is a method of any of aspects 1 through 5 includes transmitting, to the network entity, the correlation value to the secondary protocol stack further includes transmitting the correlation value to the serving SMF of a network via an AMF.

[0234] In Aspect 7 is a method of any of aspects 1 through 6 includes that the PDU session is associated with a same UPF for the primary protocol stack and the secondary protocol stack of the UE.

[0235] In Aspect 8 is a method of any of aspects 1 through 7 includes that the correlation value comprises a SMF ID or a DNN ID.

[0236] In Aspect 9 is a method of any of aspects 1 through 8 includes that an IP address for the PDU session is the same as an IP address for the primary protocol stack and for the secondary protocol stack.

[0237] Aspect 10 is a method for wireless communications at a network entity that includes obtaining, via a first RAN from a primary protocol stack of a UE, a first request for establishment of a PDU session, the PDU session comprising a primary PDU session associated with the primary protocol stack and a secondary PDU session associated with a secondary7protocol stack, wherein a protocol stack of the UE comprises the primary protocol stack and the secondary protocol stack; outputting, to the UE via the first RAN, a correlation value at the primary protocol stack based at least in part on the first request; obtaining, via a second RAN from the secondary protocol stack of the UE, a second request for establishment of the secondary PDU session of the PDU session, the second request comprising the correlation value; and communicating one or more first messages via the first RAN using the primary PDU session and one ormore second messages via the second RAN using the secondary PDU session based at least in part on the first request and the second request.

[0238] In Aspect 11 , the method of aspect 11 includes associating the correlation value with the primary PDU session for establishment of the PDU session.

[0239] In Aspect 12, the method of any of aspects 10 through 11 further includes selecting a same SMF for the primary protocol stack and the secondary protocol stack based at least in part on the correlation value.

[0240] In Aspect 13 the method of any of aspects 10 through 12 further includes that output data to the PDU session is via one of the first RAN using the primary PDU session or the second RAN using the secondary PDU session.

[0241] In Aspect 14. the method of any of aspects 10 through 13 further includes that outputting, to the UE via the first RAN, the correlation value further includes outputting a PDU session request accept message comprising the correlation value based at least in part on the first request, the PDU session request accept message indicating activation of the primary PDU session of the PDU session.

[0242] In Aspect 15. the method of any of aspects 10 through 14 includes that the network entity comprises one or more of a SMF, an AMF, a network repositor}' function, or any combination thereof.

[0243] In Aspect 16, the method of any of aspects 10 through 15, further includes outputting a PDU session request accept message based at least in part on the second request, the PDU session request accept message indicating activation of the secondary PDU session of the PDU session.

[0244] In Aspect 17, the method of any of aspects 10 through 1 further includes outputting, to the UE via the first RAN, the correlation value further comprises: outputting the correlation value from a serving SMF of a network, wherein the correlation value is indicative of the serving SMF.

[0245] In Aspect 18. the method of any of aspects 10 through 17 further includes that the PDU session is associated with a same UPF for the primary protocol stack and the secondary protocol stack.

[0246] In Aspect 19, the method of any of aspects 10 through 18 further includes that the correlation value comprises a SMF ID or a DNN ID.

[0247] In Aspect 20, the method of any of aspects 10 through 19 includes that an IP address for the PDU session is the same as an IP address for the primary protocol stack and the secondary protocol stack.

[0248] Aspect 21 is a method for wireless communications at a network entity, that includes obtaining a request for establishment of a PDU session from a primary' protocol stack of a protocol stack of a UE, wherein a subscription of the primary' protocol stack is correlated with a subscription of a secondary' protocol stack of the protocol stack; establishing, based at least in part on the subscription of the primary protocol stack being correlated with the subscription of the secondary protocol stack, a primary session via a first RAN using a first UDM context for the primary' protocol stack and a secondary' session via a second RAN using a second UDM context for the secondary protocol stack, the PDU session comprising the primary session that is associated with the primary' protocol stack and the secondary session that is associated with the secondary protocol stack, the first UDM context comprising a serving SMF ID and the second UDM context comprising the serving SMF ID; and communicating one or more first messages via the first RAN using the primary session and one or more second messages via the second RAN using the secondary session.

[0249] In Aspect 22, the method of aspect 21 that further includes the network entity7comprises an AMF or a UDM function.

[0250] In Aspect 23, the method of any of aspects 21 through 22 further include storing the serving SMF ID for a SMF in the first UDM context for the primary protocol stack and in the second UDM context for the secondary protocol stack after the SMF is allocated for the PDU session.

[0251] In Aspect 24, the method of any of aspects 21 through 23 include that establishing the secondary session further comprises: establishing, via an AMF associated with the network entity, the secondary' session using the serving SMF ID received from a UDM associated with the netyvork entity.

[0252] In Aspect 25, the method of any of aspects 21 through 24 include that network entity comprises a first AMF, a second AMF and a UDM function, or any combination thereof.

[0253] In Aspect 26, the method of any of aspects 21 through 25 further include generating the first UDM context for the primary protocol stack, the first UDM context comprising the serving SMF ID.

[0254] In Aspect 27, the method of any of aspects 21 through 26 further includes storing the serving SMF ID in the second UDM context for the secondary' protocol stack.

[0255] In Aspect 28, the method of any of aspects 21 through 27 include that the PDU session is associated with a same UPF for the primary protocol stack and the secondary protocol stack.

[0256] In Aspect 29, the method of any of aspects 21 through 28 include that copying the serving SMF ID from the first UDM context into the second UDM context based at least in part on additional information associated with the first UDM context.

[0257] In Aspect 30. the method of any of aspects 1-29 includes that the additional information comprises a reference to the second UDM context, a subscription identity of the secondary protocol stack, or a combination thereof.

[0258] Aspect 31 is a UE comprising a protocol stack for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE comprising a protocol stack to perform a method of any of aspects 1 through 9.

[0259] Aspect 32 is a UE comprising a protocol stack for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 9.

[0260] Aspect 32 is a non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 9.

[0261] Aspect 33 is a network entity for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 34 through 20.

[0262] Aspect 35 is a network entity for wireless communications, comprising at least one means for performing a method of any of aspects 36 through 20.

[0263] Aspect 37 is a non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 38 through 20.

[0264] Aspect 39 is a network entity for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 40 through 30.

[0265] Aspect 41 is a network entity for wireless communications, comprising at least one means for performing a method of any of aspects 42 through 30.

[0266] Aspect 43 is a non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 44 through 30.

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

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

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

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

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

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

[0273] As used herein, including in the claims, ‘"or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e.. A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

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

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

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

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

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

Claims

CLAIMSWhat is claimed is:1 . A user equipment (UE) comprising a protocol stack, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to: transmit, to a network entity via a first radio access network using a primary protocol stack of the UE, a first request for establishment of a packet data unit session, the packet data unit session comprising a primary packet data unit session associated with the primary protocol stack and a secondary packet data unit session associated with a secondary protocol stack, wherein the protocol stack comprises the primary’ protocol stack and the secondary protocol stack; receive, from the network entity via the first radio access network, a correlation value at the primary7protocol stack based at least in part on the first request; transmit, to the network entity' via a second radio access network using the secondary’ protocol stack of the UE, a second request for establishment of the secondary packet data unit session, the second request comprising the correlation value; and communicate one or more first messages via the first radio access network using the primary packet data unit session and one or more second messages via the second radio access network using the secondary packet data unit session based at least in part on the first request and the second request.

2. The UE of claim 1, wherein, to receive, from the network entity, the correlation value, the one or more processors are individually or collectively further operable to execute the code to cause the UE to: receive a packet data unit session request accept message comprising the correlation value based at least in part on the first request, the packet data unit session request accept message indicating activation of the primary packet data unit session in the primary7protocol stack.

3. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: communicate, via a dual-steer layer, the correlation value from the primary’ protocol stack to the secondary protocol stack.

4. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: receive a packet data unit session request accept message based at least in part on the second request, the packet data unit session request accept message indicating activation of the secondary packet data unit session.

5. The UE of claim 1, wherein, to receive, from the network entity, the correlation value, the one or more processors are individually or collectively further operable to execute the code to cause the UE to: receive the correlation value from a serving session management function of a network, wherein the correlation value is indicative of the serving session management function.

6. The UE of claim 5, wherein, to transmit, to the network entity’, the correlation value to the secondary protocol stack, the one or more processors are individually or collectively further operable to execute the code to cause the UE to: transmit the correlation value to the serving session management function of a network via an access and mobility' function.

7. A network entity, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity' to: obtain, via a first radio access network from a primary protocol stack of a user equipment (UE), a first request for establishment of a packet data unit session, the packet data unit session comprising a primary packet data unit session associated with the primary' protocol stack and a secondary' packet data unit session associated with a secondary protocol stack, wherein a protocol stackof the UE comprises the primary protocol stack and the secondary protocol stack; output, to the UE via the first radio access network, a correlation value at the primary protocol stack based at least in part on the first request; obtain, via a second radio access network from the secondary protocol stack of the UE, a second request for establishment of the secondary packet data unit session of the packet data unit session, the second request comprising the correlation value; and communicate one or more first messages via the first radio access network using the primary packet data unit session and one or more second messages via the second radio access network using the secondary' packet data unit session based at least in part on the first request and the second request.

8. The network entity of claim 7, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to: associate the correlation value with the primary packet data unit session for establishment of the packet data unit session.

9. The network entity of claim 7, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to: select a same session management function for the primary protocol stack and the secondary protocol stack based at least in part on the correlation value.

10. The network entity of claim 7, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to: output data to the packet data unit session via one of the first radio access network using the primary packet data unit session or the second radio access network using the secondary packet data unit session.

11. The network entity of claim 7, wherein, to output, to the UE via the first radio access network, the correlation value, the one or more processors areindividually or collectively further operable to execute the code to cause the network entity to: output a packet data unit session request accept message comprising the correlation value based at least in part on the first request, the packet data unit session request accept message indicating activation of the primary packet data unit session of the packet data unit session.

12. The network entity of claim 7, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to: output a packet data unit session request accept message based at least in part on the second request, the packet data unit session request accept message indicating activation of the secondary packet data unit session of the packet data unit session.

13. The network entity of claim 7, wherein, to output, to the UE via the first radio access network, the correlation value, the one or more processors are individually or collectively further operable to execute the code to cause the network entity' to: output the correlation value from a serv ing session management function of a network, wherein the correlation value is indicative of the serving session management function.

14. A network entity7, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to: obtain a request for establishment of a packet data unit session from a primary protocol stack of a protocol stack of a user equipment (UE). wherein a subscription of the primary protocol stack is correlated with a subscription of a secondary protocol stack of the protocol stack; establish, based at least in part on the subscription of the primary protocol stack being correlated with the subscription of the secondary protocol stack, a primary7session via a first radio access network using a first unified datamanagement context for the primary protocol stack and a secondary session via a second radio access network using a second unified data management context for the secondary protocol stack, the packet data unit session comprising the primary session that is associated with the primary protocol stack and the secondary session that is associated with the secondary protocol stack, the first unified data management context comprising a serving session management function identifier and the second unified data management context comprising the serving session management function identifier; and communicate one or more first messages via the first radio access network using the primary session and one or more second messages via the second radio access network using the secondary' session.

15. The network entity of claim 14, wherein the network entity comprises an access and mobility management function or a unified data management function.

16. The network entity of claim 14, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to: store the serving session management function identifier for a session management function in the first unified data management context for the primary protocol stack and in the second unified data management context for the secondary protocol stack after the session management function is allocated for the packet data unit session.

17. The network entity of claim 14, wherein, to establish the secondary session, the one or more processors are individually or collectively further operable to execute the code to cause the network entity to: establish, via an access and mobility management function associated with the network entity, the secondary session using the serving session management function identifier received from a unified data management associated with the network entity.

18. The network entity of claim 14, wherein the network entity comprises a first access and mobility management function, a second access and mobility' management function and a unified data management function, or any combination thereof.

19. The network entity of claim 14, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to: generate the first unified data management context for the primary protocol stack, the first unified data management context comprising the serving session management function identifier.

20. The network entity of claim 14, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to: copy the serving session management function identifier from the first unified data management context into the second unified data management context based at least in part on additional information associated with the first unified data management context.

Images