Joint network selection for devices with two protocol stacks

Abstract

Methods, systems, and devices are described for methods of wireless communication. A user equipment (UE) can obtain a first list of access network combinations that support dual-oriented operations at the UE, where the dual-oriented operations enable the UE to transmit data packets associated with a data flow across a set of access networks. The UE can obtain a second list of access network combinations that support the dual-oriented operations at the UE. The UE can then initiate a registration procedure to a first access network and a second access network according to a joint selection of the first access network for a first protocol stack and the second access network for a second protocol stack. The first access network and the second access network can be jointly selected based on the first list of access network combinations and the second list of access network combinations.

Description

Cross-referencing

[0001] This patent application claims priority to Greek patent application No. 20240100236, filed on April 3, 2024, entitled “JOINT NETWORKSELECTION FOR A DEVICE WITH TWO PROTOCOL STACKS”, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] The following relates to a method for wireless communication, which includes joint network selection for devices with two protocol stacks. Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing 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-A 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 Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses for supporting joint network selection for devices having two protocol stacks. For example, the described technology provides selection of access networks for dual-direction operation at a User Equipment (UE). The UE can use a corresponding protocol stack to perform a radio frequency scan to identify a first list and a second list of available access networks. The UE can then obtain a first list and a second list of access network combinations supporting dual-direction operation at the UE. Using the first and second lists of available access networks, and the first and second lists of access network combinations, the UE can jointly select a first access network and a second access network. The UE can then initiate a registration process to the first and second access networks based on the joint selection of the first access network for the first protocol stack and the second access network for the second protocol stack.

[0005] A method for wireless communication by a UE is described. The method may include: obtaining a first list of access network combinations supporting dual-direction operation at the UE, wherein the dual-direction operation enables the UE to transmit data packets associated with a data stream across a set of multiple access networks; obtaining a second list of access network combinations supporting the dual-direction operation at the UE; and initiating a registration process with the first access network and the second access network based on a joint selection of a first access network for a first protocol stack and a second access network for a second protocol stack, the first access network and the second access network being jointly selected based on the first list of access network combinations and the second list of access network combinations.

[0006] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute the code to enable the UE to: obtain a first list of access network combinations supporting dual-direction operation at the UE, wherein the dual-direction operation enables the UE to transmit data packets associated with a data stream across a set of multiple access networks; obtain a second list of access network combinations supporting the dual-direction operation at the UE; and initiate a registration process to the first access network and the second access network based on a joint selection of a first access network for a first protocol stack and a second access network for a second protocol stack, the first access network and the second access network being jointly selected based on the first list of access network combinations and the second list of access network combinations.

[0007] Another UE for wireless communication is described. The UE may include: means for obtaining a first list of access network combinations supporting dual-direction operation at the UE, wherein the dual-direction operation enables the UE to transmit data packets associated with a data stream across a set of multiple access networks; means for obtaining a second list of access network combinations supporting the dual-direction operation at the UE; and means for initiating a registration process to the first access network and the second access network based on a joint selection of a first access network for a first protocol stack and a second access network for a second protocol stack, the first access network and the second access network being jointly selected based on the first list of access network combinations and the second list of access network combinations.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors for: obtaining a first list of access network combinations supporting dual-direction operation at the UE, wherein the dual-direction operation enables the UE to transmit data packets associated with a data stream across a set of multiple access networks; obtaining a second list of access network combinations supporting the dual-direction operation at the UE; and initiating a registration process to the first access network and the second access network based on a joint selection of a first access network for a first protocol stack and a second access network for a second protocol stack, the first access network and the second access network being jointly selected based on the first list of access network combinations and the second list of access network combinations.

[0009] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for: performing a radio frequency scan to obtain a first list of available access networks against the first protocol stack; performing the radio frequency scan to obtain a second list of available access networks against the second protocol stack; and obtaining the first list of available access networks from the first protocol stack and the second list of available access networks from the second protocol stack, wherein initiating the registration process may be based on the first list of available access networks, the second list of available access networks, the first list of access network combinations, and the second list of access network combinations.

[0010] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for: sorting the first list of access network combinations and the second list of access network combinations according to priority; selecting a first access network based on matching the sorted first list of access network combinations with the first list of available access networks; and selecting a second access network based on matching the sorted second list of access network combinations with the second list of available access networks.

[0011] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for selecting the first access network and the second access network based on the highest priority access network combination that may be included in both the first list of access network combinations and the second list of access network combinations.

[0012] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, obtaining the first list of access network combinations may include operations, features, components, or instructions for retrieving the first list of access network combinations from the first protocol stack.

[0013] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the first list of access network combinations may be stored in a generic subscriber identity module associated with the first protocol stack.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, obtaining the first list of access network combinations may include operations, features, components, or instructions for: receiving a message indicating the first list of access network combinations during the registration process, based on the first protocol stack and the first access network supporting the dual-direction operation at the UE.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, obtaining the second list of access network combinations may include operations, features, components, or instructions for retrieving the second list of access network combinations from the second protocol stack.

[0016] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the second list of access network combinations may be stored in a generic subscriber identity module associated with the second protocol stack.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, obtaining the second list of access network combinations may include operations, features, components, or instructions for: receiving a message indicating the second list of access network combinations during the registration process, based on the second protocol stack and the second access network supporting the dual-direction operation at the UE.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the generic subscriber identity module associated with the first protocol stack and the generic subscriber identity module associated with the second protocol stack may be issued by the same network operator.

[0019] The methods described herein, some examples of UEs and nontransitory computer-readable media may also include operations, features, components or instructions for: determining that a dual-direction operation mode can be enabled at the UE, wherein obtaining the first list of access network combinations and obtaining the second list of access network combinations may be based on determining that the dual-direction operation mode can be enabled at the UE.

[0020] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first access network and the second access network may be associated with the same Public Land Mobile Network (PLMN) or different PLMNs, and the first access network and the second access network may be associated with the same Radio Access Technology (RAT) or different RATs. Attached Figure Description

[0021] Figure 1 An example of a wireless communication system supporting joint network selection for devices having two protocol stacks, according to one or more aspects of this disclosure, is shown.

[0022] Figure 2 An example of a wireless communication system supporting joint network selection for devices having two protocol stacks, according to one or more aspects of this disclosure, is shown.

[0023] Figure 3 An example of a process flow supporting joint network selection for devices with two protocol stacks, according to one or more aspects of this disclosure, is shown.

[0024] Figure 4 and Figure 5 A block diagram is shown that supports joint network selection for devices having two protocol stacks, according to one or more aspects of this disclosure.

[0025] Figure 6 A block diagram is shown of a communication manager that supports joint network selection for devices with two protocol stacks, according to one or more aspects of this disclosure.

[0026] Figure 7 A diagram is shown illustrating a system including a device that supports joint network selection for devices having two protocol stacks, according to one or more aspects of this disclosure.

[0027] Figures 8 to 11 A flowchart illustrating a method for joint network selection for a device having two protocol stacks, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0028] Some wireless communication networks support dual-steer functionality and operation. Dual-steer (also known as dualsteer, DualSteer, DS, etc.) is a feature that allows a device to transmit packets associated with a data stream (e.g., an application) across two different access networks. For example, a user equipment (UE) with dual-steer capability can be a device with multiple (e.g., two) protocol stacks and supporting the steering and handover of user data (for different services) across two access networks (e.g., 3GPP access networks). The two access networks can be associated with different accesses to the same network or can belong to different networks. For example, an access network can be defined by a combination of a Public Land Mobile Network (PLMN) and a Radio Access Technology (RAT) (e.g., a first access network can be associated with a first PLMN and a first RAT, and a second radio access network can be associated with a first PLMN and a different second RAT, to name just one example of a PLMN / RAT combination that can define a corresponding access network). UEs capable of dual-direction can switch data transmission (e.g., switching data streams from one access network to another) or direct data transmission (e.g., deciding which access network to use is done on a per-packet basis). Devices with dual-direction capability can use radio scanning to identify available radio access networks to perform access network selection for dual-direction in each stack. However, this method for access network selection may not take dual-direction characteristics into account. For example, there may not be a pre-existing service arrangement between the selected access networks to support dual-direction packet data unit sessions between them, and the benefits of dual-direction operation may not be realized when such access networks are selected (e.g., the selected access network may be incompatible with dual-direction operation and / or functionality).

[0029] The techniques described herein provide a first list and a second list of access network combinations supporting dual-direction at the UE. The UE can then establish connections with the first and second access networks based on the retrieved lists. According to the aspects described herein, the UE can use a first protocol stack and a second protocol stack to perform joint network selection for dual-direction. In one example, the general subscriber identity module of each protocol stack can be configured with a priority list for dual-direction access network combinations. The UE can receive a priority list of access network tuples for dual-direction and a list of available access networks from each protocol stack. The UE can then cross-reference this information and determine the available access network combination with the highest priority. For example, the UE can use the first and second protocol stacks to select the access network combination with the highest priority in both lists. The UE can then initiate registration with the first access network via the first stack and with the second access network via the second stack, based on the selected access network combination.

[0030] The aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described by way of process flow. The aspects of this disclosure are further illustrated and described by way of apparatus diagrams, system diagrams, and flowcharts relating to joint network selection for a device having two protocol stacks.

[0031] Figure 1 An example of a wireless communication system 100 supporting joint network selection for devices having two protocol stacks, according to one or more aspects of this disclosure, is shown. The wireless communication system 100 may include: one or more devices, such as one or more network devices (e.g., network entity 105); one or more UEs 115; and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0032] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0033] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Examples of UE 115 are illustrated herein. The UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including UE 115 or network entity 105), such as... Figure 1 As shown.

[0034] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or 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, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be 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 UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0035] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links), or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

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

[0037] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed among multiple network entities (e.g., network entity 105), such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration advocated by O-RAN), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a central unit (CU) such as CU 160, a distributed unit (DU) such as DU 165, a radio unit (RU) such as RU 170, a RAN intelligent controller (RIC) such as RIC 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system such as SMO system 180, or any combination thereof. RU 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0038] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host upper protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) may connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or some combination thereof, and DU 165, RU 170, or both may host lower protocol layers, such as Layer 1 (L1) (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 CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between DU 165 and RU 170, such that DU 165 may support one or more layers of the protocol stack, and RU 170 may support one or more different layers of the protocol stack. DU 165 may (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by a different one of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.

[0039] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities in network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor entities (e.g., IAB donors) may communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include IAB mobile terminals (IAB-MTs) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) that support communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., IAB node 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0040] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity 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 having a wired or wireless connection to the core network 130. The IAB donor may include one or more of CU 160, DU 165, and RU 170, in which case CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, CU 160 may communicate with core network 130 via an interface (which may be part of a backhaul link) and may communicate with other CUs (e.g., including CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be another part of a backhaul link).

[0041] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may be relayed by other IAB nodes 104 for UE transmission). Additionally or alternatively, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104, depending on the AN's relay chain or configuration. The IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB nodes (e.g., IAB node 104) to receive signaling from parent IAB nodes (e.g., IAB node 104), and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB nodes to send signals to child IAB nodes or UE 115.

[0042] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, an IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. An IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via one or more DUs (e.g., DU 165). In other words, data can be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104 (e.g., other IAB nodes). Communication with IAB node 104 can be scheduled by the IAB donor or by the DU 165 of IAB node 104.

[0043] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

[0044] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances, vehicles, or meters.

[0045] The UE 115 described herein can communicate with various types of devices, such as the UE 115 which sometimes operates as a relay, as well as network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0046] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0047] In some examples, such as in carrier aggregation configurations, carriers may have acquisition or control signaling that coordinates operation against other carriers. Carriers may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. Carriers may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or carriers may operate in non-standalone mode, in which case different carriers (e.g., of the same or different RATs) are used to anchor the connection.

[0048] The communication link 125 of the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. The carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0049] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0050] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, UE 115 can be configured to utilize multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and communication for UE 115 can be constrained to one or more active BWPs.

[0051] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, while This can represent the supported Discrete Fourier Transform (DFT) size. The time interval for organizing communication resources can be based on radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0052] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may also be divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems, such as wireless communication system 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0053] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0054] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to transmit control information to UE115 (e.g., one or more UEs), or it may include a UE-specific search space set for transmitting control information to UE115.

[0055] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, etc., or may include buildings, subsets of buildings, or external space between or overlapping coverage areas, etc.

[0056] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0057] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas (such as coverage area 110). In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) may overlap, but coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., network entity 105). In some other examples, overlapping coverage areas (such as coverage area 110) associated with different technologies may be supported by different network entities (e.g., network entity 105). The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different RATs to support communication for coverage area 110 (e.g., different coverage areas).

[0058] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timing, and transmissions from different network entities (e.g., different network entities within network entity 105) can be roughly aligned in time. For asynchronous operation, network entities 105 can have different frame timing, and in some examples, transmissions from different network entities (e.g., different network entities within network entity 105) may not be aligned in time. The techniques described herein can be used for both synchronous and asynchronous operation.

[0059] Some UE 115 devices (such as MTC or IoT devices) can be relatively low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or instruments to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based service charging.

[0060] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115 may include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0061] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0062] In some examples, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as D2D communication link 135) (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in this group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to one or more UEs within the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0063] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities can connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0064] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is 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 these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

[0065] The wireless communication system 100 can also operate in the Ultra High Frequency (SHF) band (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the Extremely High Frequency (EHF) band (e.g., from 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU170), and the EHF antennas of the corresponding devices can be smaller and closer together than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmission, EHF transmission may experience even greater attenuation and shorter distances. The techniques disclosed herein can be adopted for transmission across one or more different frequency bands, and the frequency band usage specified across these frequency bands may vary by country or regulatory authority.

[0066] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0067] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation 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, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0068] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0069] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device by the transmitting or receiving device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0070] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 along different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

[0071] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0072] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under relatively poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0073] Wireless communication system 100 may support dual-direction (e.g., dualsteer, DS), where dual-direction can be a wireless communication feature / functionality that allows a device to transmit packets associated with a data stream (e.g., an application) across two different access networks (e.g., access networks belonging to the same or different operators). In some examples, the two access networks can be different accesses to the same network (e.g., 5G and LTE of the same operator). Alternatively, the two access networks can belong to different networks. Dual-direction transmission can refer to transmission that can be switched or directed. When switched, a data stream from an application can be switched from one access network to another. When directed, the device (e.g., UE 115) can decide which access network to use on a per-packet basis. In some examples, the decision to switch or direct can be based on the quality of service available on each access network (e.g., latency, packet loss rate, signal strength, etc.). Typically, there may be a lack of protocols for dual-direction operation of a device between two or more networks.

[0074] According to one or more aspects described herein, UE 115 may obtain a first list of access network combinations that support dual-direction operation at the UE, wherein the dual-direction operation enables the UE to send data packets associated with a data stream across the set of access networks. In some examples, UE 115 may obtain a second list of access network combinations that support dual-direction operation at the UE 115. UE 115 may then initiate a registration process with the first and second access networks based on a joint selection of a first access network for a first protocol stack and a second access network for a second protocol stack. In some cases, the first and second access networks may be jointly selected based on the first list and the second list of access network combinations.

[0075] Figure 2An example of a wireless communication system 200 supporting joint network selection for devices having two protocol stacks, according to one or more aspects of this disclosure, is shown. In some examples, aspects of the wireless communication system 200 may be implemented by, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a first network entity 105-a, a second network entity 105-b, and a UE 115-a, which may be referenced respectively. Figure 1 Examples of network entity 105 and UE 115 described herein. Although a single network entity 105 is illustrated herein, it should be understood that the functionality described herein can be implemented by a single network entity.

[0076] In some examples, UE 115-a can communicate with network entities 105-a and 105-b via a first communication link 205 and a second communication link 210, respectively. In some cases, UE 115-a can communicate with network entities 105-a and 105-b via the same communication link. Depending on one or more aspects, UE 115-a and network entity 105 can communicate according to dual-direction operation. In some examples, dual-direction operation can support dual-direction packet data unit sessions via terrestrial access and non-terrestrial access (e.g., satellite). In some cases, satellite access can be deployed by the same PLMN as terrestrial access or by a different PLMN. In such examples, the quality of service on the two accesses can be different, with the quality of service for each access fluctuating over time. In some examples, even if deployed by the same operator, satellite access and terrestrial access can have different PLMN identifiers (e.g., satellite access using Mobile Country Code (MCC) 9xx, configured as a PLMN equivalent to the terrestrial access PLMN). As described herein, a PLMN identifier may include an MCC and a Mobile Network Code (MNC). The MCC may specify the country, and the MNC may specify the operator within that country. MCC 9xx may refer to a shared MCC that is not associated with any country. This deployment allows operators to provide service without deploying a terrestrial network and provides applications with a smooth handover between non-terrestrial and terrestrial networks. Additionally or alternatively, when both networks are available, this deployment may allow operators to provide capacity and / or throughput enhancements.

[0077] When operating in dual-direction mode, UE 115-a can use two protocol stacks (control plane stack 1 and control plane stack 2) to access separate access networks. Figure 2In the example, UE 115-a can use a first subscription (using Universal Subscriber Identity Module 1) to access a first access network (accessed via network entity 105-a). Additionally, UE 115-a can use a second subscription (using Universal Subscriber Identity Module 2) to access a second access network (accessed via network entity 105-a). For example, each protocol stack in a device with dual-steer capability can use a separate subscription (e.g., a separate Universal Subscriber Identity Module). In some examples, each Universal Subscriber Identity Module may be associated with a corresponding Subscription Permanent Identifier (SUPI). Each protocol stack may include a NAS Session Management (NAS-SM) layer, a NAS Mobility Management (NAS-MM) layer, an RRC layer, an RLC layer, a MAC layer, and a PHY layer. The dualsteer control plane can communicate with each protocol stack, which in turn can communicate with a Universal Integrated Circuit Card (UICC) domain. Universal Subscriber Identity Module 1 and Universal Subscriber Identity Module 2 may be included in the UICC domain. In some examples, each stack in a device with dual-direction capability (e.g., UE 115-a) can separately register to the corresponding access network for each stack using a corresponding generic subscriber identity module. During registration, each protocol stack can provide an indication of support for dual-direction and can receive such an indication from the corresponding network entity.

[0078] In some examples, the wireless communication system 200 can communicate according to a dual-direction control / coordination layer that coordinates dual-direction features across two protocol stacks. Specifically, the dual-direction control / coordination layer can control packet data unit session establishment and network selection for dual-direction. In some examples, UE 115-a can be enabled with dual-direction mode. Enabling dual-direction mode can trigger network selection for dual-direction. In some examples, UE 115 can power on with dual-direction mode enabled, in which case the initial network selection can be network selection for dual-direction. In one example, dual-direction mode can be activated when the second protocol stack is activated.

[0079] In some examples, for the PLMN identifier selection process (single-stack single universal subscriber identity module), the UE can select the access network based on a priority list of PLMN and RAT combinations configured in the universal subscriber identity module by the home PLMN identifier. For example, the priority list of PLMN and radio access network combinations configured in the universal subscriber identity module could be as follows: 1. PLMN A / 5G 2. PLMN B / 5G 3.PLMN A / 4G 4. PLMN B / 4G 5. PLMN C (4G or 5G)

[0080] The UE can scan available access networks and select the highest priority access network from a list in the General Subscriber Identity Module (GSM). As described herein, the access network can refer to a combination of PLMN and RAT. However, when performing network selection for two stacks, a priority mismatch may occur if the UE selects the highest priority access network in each list (a first list for the first GSM and a second list for the second GSM). Furthermore, this selection process may only focus on network selection without considering dual-direction characteristics.

[0081] In one example, the first protocol stack can use General Subscriber Identity Module 1 and can select PLMN identifier X. The second protocol stack can use General Subscriber Identity Module 2 and can select PLMN Y. Both PLMN X and PLMN Y can support dual-direction. However, there may not be a pre-existing service arrangement between PLMN X and PLMN Y to support dual-direction Packet Data Unit sessions between them, and specifically not for subscribers of General Subscriber Identity Module 1. In this scenario, the device may be unable to use the dual-direction feature as long as the main stack resides on PLMN identifier X.

[0082] To address this scenario, the aspects described herein provide dual-direction-aware dual-direction network selection. For example, the first and second protocol stacks of UE 115-a can perform joint network selection for dual-direction. In some examples, the generic subscriber identity module of each stack can be configured with a priority list for dual-direction access network combinations. Examples of such a list include: PLMN X / 5G + PLMN X / 4G PLMN X / 5G + PLMN Y / 4G PLMN X / 4G + PLMN X / 5G PLMN X / 4G + PLMN Z / 5G

[0083] In such examples, a dual-direction control / coordination layer ensures that the two protocol stacks select the combination of access networks with the highest priority across two lists, thereby enabling efficient dual-direction operation and functionality.

[0084] According to one or more aspects described herein, UE 115-a can perform an RF scan to obtain a first list of available access networks for a first protocol stack. Additionally, UE 115-a can obtain a first list of access network combinations that support dual-direction operation at UE 115-a. As described herein, dual-direction operation enables UE 115-a to transmit data packets associated with a data flow across a set of access networks. Additionally, UE 115-a can perform an RF scan to obtain a second list of available access networks for a second protocol stack. UE 115-a can also obtain a second list of access network combinations that support dual-direction operation at UE 115-a. Therefore, UE 115-a can (e.g., from each stack) obtain a prioritized list of access network tuples (e.g., access network pairs) for dual-direction and a list of available access networks. UE 115-a can then cross-reference this information and identify the highest priority available access network combination. For example, a first list and a second list of access network combinations can be sorted according to priority, and UE 115-a can select a first access network based on matching the sorted first list of access network combinations with a first list of available access networks. Similarly, UE 115-a can select a second access network based on matching the sorted second list of access network combinations with a second list of available access networks. That is, UE 115-a can jointly select multiple access networks based on the lists of available access networks and access network pairs. As described herein, UE 115-a can perform selection (e.g., joint selection) based on priority, wherein the selection of the first and second access networks is based on the highest relative priority access network combination included in both the first and second lists of access network combinations.

[0085] When identifying the highest priority combination of access networks (e.g., a first access network and a second access network) in the list of available access networks, UE 115-a may initiate a registration process with the first access network and the second access network based on a joint selection of the first access network for the first protocol stack and the second access network for the second protocol stack. Alternatively, UE 115-a may provide separate access network information to each stack for the registration process.

[0086] In some examples, one or more priority lists of access network combinations may be stored in one or more generic subscriber identity modules. The network may use a suitable signaling protocol, such as the Roaming Direction (SoR) protocol specified in the standard documentation, to perform updates to one or more priority lists of access network combinations stored in one or more generic subscriber identity modules. Additionally or alternatively, UE 115-a may receive one or more priority lists of access network combinations during the registration process (e.g., via one or more messages). That is, UE 115-a may receive signaling indicating a first list and a second list of access network combinations.

[0087] The techniques described herein enable PLMN identifier selection for each protocol stack to be bidirectionally aware. As described herein, PLMN selection can be implemented by a bidirectional control / coordination layer. Additionally, the techniques described herein avoid the possibility of failing to find a suitable combination of access networks for bidirectional selection due to the lack of bidirectionally aware network selection in the main protocol stack. In other words, joint access network selection using the described techniques ensures bidirectional functionality / operation is maintained when the UE 115 communicates with multiple access networks.

[0088] Figure 3 An example of a process flow 300 supporting joint network selection for a device having two protocol stacks, according to one or more aspects of this disclosure, is shown. Process flow 300 can be executed by UE 115 and network entity 105, and they can be as described regarding... Figure 1 and Figure 2 Examples of the corresponding devices described. In the following description of process flow 300, the operations between UE 115 and network entity 105 may be performed in a different order than the example order shown. Some operations may also be omitted from process flow 300, and other operations may be added to process flow 300. Furthermore, although some operations or signaling are shown to occur at different times for discussion purposes, these operations may actually occur simultaneously.

[0089] At 302, UE 115 can determine whether dual-direction mode is enabled at UE 115. If UE 115 determines that dual-direction mode is not enabled, then at 304, UE 115 can use the first protocol stack to perform an RF scan. At 306, UE 115 can identify a list of available PLMN access networks. At 308, UE 115 can receive a priority list of access networks from the General Subscriber Identity Module 310. At 312, the first protocol stack of UE 115 can select the available access network with the highest priority.

[0090] Additionally, if UE 115 determines that dual-direction mode is not enabled, then at 314, UE 115 can use a second protocol stack to perform an RF scan. At 316, UE 115 can identify a list of available PLMN access networks. At 318, UE 115 can receive a priority list of access networks from the General Subscriber Identity Module 320. At 322, UE 115's second protocol stack can select the available access network with the highest priority.

[0091] If UE 115 determines that dual-direction mode is enabled, then at 324, UE 115 can use the first protocol stack to perform an RF scan. For example, UE 115 can perform an RF scan to obtain a first list of available access networks against the first protocol stack. At 326, UE 115 can receive the list of available access networks from the first protocol stack (protocol stack 1).

[0092] At 328, UE 115 may receive a priority list of access networks from the general subscriber identity module 330. For example, UE 115 may obtain a first list of access network combinations that support dual-direction operation at UE 115.

[0093] Additionally, at 332, UE 115 can use the second protocol stack to perform an RF scan. For example, UE 115 can perform an RF scan to obtain a second list of available access networks against the second protocol stack. At 334, UE 115 can receive the list of available access networks from the second protocol stack (protocol stack 2).

[0094] At 336, UE 115 may receive a priority list of access networks from the general subscriber identity module 338. For example, UE 115 may obtain a second list of access network combinations that support dual-direction operation at UE 115.

[0095] At 340, UE 115 may select a first access network and a second access network based on the highest priority access network combination included in both a first list and a second list of access network combinations. At 342, UE 115 may provide the selected access network to a first protocol stack (protocol stack 1) and a second protocol stack (protocol stack 2). In some examples, aspects such as 326, 328, 334, 336, 340, and 342 may be performed by a joint PLMN selection logic implemented at UE 115 (e.g., included in or associated with dual-direction control logic (DSCL)).

[0096] Figure 4A block diagram 400 illustrates a device 405 supporting joint network selection for devices having two protocol stacks, according to one or more aspects of this disclosure. Device 405 may be an example of aspects of UE 115 as described herein. Device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. Device 405, or one or more components of device 405 (e.g., receiver 410, transmitter 415, communication manager 420), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0097] Receiver 410 may provide components 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 joint network selection for devices with two protocol stacks). The information may be passed to other components of device 405. Receiver 410 may utilize a single antenna or a collection of antennas.

[0098] Transmitter 415 may provide components for transmitting signals generated by other components of device 405. For example, transmitter 415 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to joint network selection for devices with two protocol stacks, including packets, user data, control information, or any combination thereof. In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0099] The communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be examples of components used to perform various aspects of joint network selection for a device having two protocol stacks as described herein. For example, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0100] In some examples, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0101] Additionally or alternatively, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in code (e.g., referred to as processor executable code) executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be executed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, individually or collectively, as components for performing the functions described in this disclosure).

[0102] In some examples, the communication manager 420 may be configured to use a receiver 410, a transmitter 415, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 420 may receive information from the receiver 410, transmit information to the transmitter 415, or integrate with the receiver 410, the transmitter 415, or both to acquire information, output information, or perform various other operations as described herein.

[0103] The communication manager 420 may support wireless communication according to examples disclosed herein. For example, the communication manager 420 may be capable of, configured to, or operable to support components for obtaining a first list of access network combinations supporting dual-direction operation at the UE, wherein dual-direction operation enables the UE to send data packets associated with a data stream across a set of multiple access networks. The communication manager 420 may be capable of, configured to, or operable to support components for obtaining a second list of access network combinations supporting dual-direction operation at the UE. The communication manager 420 may be capable of, configured to, or operable to support components for initiating a registration process to a first access network and a second access network based on a joint selection of a first access network for a first protocol stack and a second access network for a second protocol stack, wherein the first and second access networks are jointly selected based on the first list and the second list of access network combinations.

[0104] By including or configuring a communication manager 420 according to an example as described herein, device 405 (e.g., controlling receiver 410, transmitter 415, communication manager 420 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption and utilizing communication resources more efficiently.

[0105] Figure 5 A block diagram 500 of device 505 supporting joint network selection for devices having two protocol stacks, according to one or more aspects of this disclosure, is shown. Device 505 may be an example of aspects of device 405 or UE 115 as described herein. Device 505 may include receiver 510, transmitter 515, and communication manager 520. Device 505 or one or more components of device 505 (e.g., receiver 510, transmitter 515, communication manager 520) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0106] Receiver 510 may provide components 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 joint network selection for devices with two protocol stacks). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0107] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to joint network selection for devices with two protocol stacks, including packets, user data, control information, or any combination thereof. In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0108] Device 505 or its various components may be examples of parts used to perform various aspects of joint network selection for devices having two protocol stacks as described herein. For example, communication manager 520 may include access network combination component 525, registration component 530, or any combination thereof. Communication manager 520 may be examples of aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to use receiver 510, transmitter 515, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or integrate in combination with receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0109] The communication manager 520 may support wireless communication according to examples disclosed herein. The access network combination component 525 is capable of, configured to, or operable to support components for obtaining a first list of access network combinations supporting dual-direction operation at the UE, wherein dual-direction operation enables the UE to send data packets associated with a data stream across a set of multiple access networks. The access network combination component 525 is capable of, configured to, or operable to support components for obtaining a second list of access network combinations supporting dual-direction operation at the UE. The registration component 530 is capable of, configured to, or operable to support components for initiating a registration process to a first access network and a second access network based on a joint selection of a first access network for a first protocol stack and a second access network for a second protocol stack, wherein the first and second access networks are jointly selected based on the first list and the second list of access network combinations.

[0110] Figure 6A block diagram 600 is shown of a communication manager 620 supporting joint network selection for a device having two protocol stacks, according to one or more aspects of this disclosure. The communication manager 620 may be an example of a communication manager 420, a communication manager 520, or aspects thereof as described herein. The communication manager 620 or its various components may be examples of parts for performing various aspects of joint network selection for a device having two protocol stacks as described herein. For example, the communication manager 620 may include an access network combination component 625, a registration component 630, an RF scanning component 635, an access network availability component 640, an operation mode component 645, a sorting component 650, an access network selection component 655, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0111] The communication manager 620 may support wireless communication according to examples disclosed herein. The access network combining component 625 is capable of, configured to, or operable to support components for obtaining a first list of access network combinations supporting dual-direction operation at the UE, wherein dual-direction operation enables the UE to send data packets associated with a data stream across a set of multiple access networks. In some examples, the access network combining component 625 is capable of, configured to, or operable to support components for obtaining a second list of access network combinations supporting dual-direction operation at the UE. The registration component 630 is capable of, configured to, or operable to support components for initiating a registration process to a first access network and a second access network based on a joint selection of a first access network for a first protocol stack and a second access network for a second protocol stack, the first and second access networks being jointly selected based on the first list and the second list of access network combinations.

[0112] In some examples, the RF scanning component 635 is capable of, configured to, or operable to support components for performing RF scans to obtain a first list of available access networks against a first protocol stack. In some examples, the RF scanning component 635 is capable of, configured to, or operable to support components for performing RF scans to obtain a second list of available access networks against a second protocol stack. In some examples, the access network availability component 640 is capable of, configured to, or operable to support components for obtaining a first list of available access networks from a first protocol stack and a second list of available access networks from a second protocol stack, wherein the registration process is initiated based on the first list of available access networks, the second list of available access networks, a first list of combinations of access networks, and the second list of combinations of access networks.

[0113] In some examples, the sorting component 650 is capable of, configured to, or operable to support components for sorting a first list and a second list of access network combinations according to priority. In some examples, the access network selection component 655 is capable of, configured to, or operable to support components for selecting a first access network based on matching the sorted first list of access network combinations with a first list of available access networks. In some examples, the access network selection component 655 is capable of, configured to, or operable to support components for selecting a second access network based on matching the sorted second list of access network combinations with a second list of available access networks.

[0114] In some examples, the access network selection component 655 is capable of, configured to, or operable to support components for selecting a first access network and a second access network based on the highest priority access network combination included in both a first list of access network combinations and a second list of access network combinations.

[0115] In some examples, in order to support obtaining a first list of access network combinations, the access network combination component 625 can be configured or operable to support components for retrieving a first list of access network combinations from a first protocol stack.

[0116] In some examples, the first list of access network combinations is stored in a generic subscriber identity module associated with the first protocol stack.

[0117] In some examples, in order to support obtaining a first list of access network combinations, the access network combination component 625 is capable of, configured to, or operable to support a component for receiving a message indicating the first list of access network combinations during the registration process for dual-directed operation at the UE based on a first protocol stack and a first access network.

[0118] In some examples, to support obtaining a second list of access network combinations, the access network combination component 625 is capable of, configured, or operable to support components for retrieving the second list of access network combinations from a second protocol stack. In some examples, the second list of access network combinations is stored in a generic subscriber identity module associated with the second protocol stack.

[0119] In some examples, in order to support obtaining a second list of access network combinations, the access network combination component 625 is capable of, configured to, or operable to support a component for receiving a message indicating a second list of access network combinations during the registration process for dual-direction operation at the UE based on a second protocol stack and a second access network.

[0120] In some examples, the generic subscriber identity module associated with the first protocol stack and the generic subscriber identity module associated with the second protocol stack are issued by the same network operator. In some examples, the operation mode component 645 is capable of, configured to, or operable to support components for determining whether a dual-directed operation mode is enabled at the UE, wherein obtaining a first list of access network combinations and obtaining a second list of access network combinations are based on determining that a dual-directed operation mode is enabled at the UE.

[0121] In some examples, the first access network and the second access network are associated with the same PLMN or different PLMNs. In some examples, the first access network and the second access network are associated with the same RAT or different RATs.

[0122] Figure 7 A diagram of a system 700 including device 705 supporting joint network selection for devices having two protocol stacks, according to one or more aspects of this disclosure, is shown. Device 705 may be an example of device 405, device 505, or UE 115 as described herein, or may include components thereof. Device 705 may (e.g., wirelessly) communicate with one or more other devices (e.g., network entity 105, UE 115, or any combination thereof). Device 705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 720, an input / output (I / O) controller (e.g., I / O controller 710), a transceiver 715, one or more antennas 725, at least one memory 730, code 735, and at least one processor 740. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 745).

[0123] I / O controller 710 manages the input and output signals of device 705. I / O controller 710 can also manage peripheral devices not integrated into device 705. In some cases, I / O controller 710 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ®Alternatively, the I / O controller 710 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 710 may be implemented as part of one or more processors, such as at least one processor 740. In some cases, a user may interact with the device 705 via the I / O controller 710 or via hardware components controlled by the I / O controller 710.

[0124] In some cases, device 705 may include a single antenna. However, in other cases, device 705 may have more than one antenna, which can concurrently transmit or receive multiple wireless transmissions. Transceiver 715 may use a wired or wireless link to communicate bidirectionally via one or more antennas 725, as described herein. For example, transceiver 715 may represent a wireless transceiver and be able to communicate bidirectionally with another wireless transceiver. Transceiver 715 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 725 for transmission; and demodulating packets received from one or more antennas 725. Transceiver 715, or transceiver 715 and one or more antennas 725, may be an example of transmitter 415, transmitter 515, receiver 410, receiver 510, or any combination thereof or component thereof as described herein.

[0125] At least one memory 730 may include random access memory (RAM) and read-only memory (ROM). At least one memory 730 may store computer-readable code, computer-executable code, or processor-executable code, such as code 735. Code 735 may include instructions that, when executed by at least one processor 740, cause device 705 to perform the various functions described herein. Code 735 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 735 may not be directly executable by at least one processor 740, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 730 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0126] At least one processor 740 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 740 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 740. At least one processor 740 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 730) to cause device 705 to perform various functions (e.g., functions or tasks supporting joint network selection for devices with two protocol stacks). For example, device 705 or components of device 705 may include at least one processor 740 and at least one memory 730 coupled to or coupled to at least one processor 740, the at least one processor 740 and the at least one memory 730 being configured to perform the various functions described herein.

[0127] In some examples, at least one processor 740 may include multiple processors, and at least one memory 730 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 740 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 740) and memory circuitry (which may include at least one memory 730)) or components that receive or receive input and process the input 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, at least one processor 740 or a processing system including at least one processor 740 may be configured, capable of being configured, or operable to cause device 705 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “operable to” can be used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code 735 (e.g., processor-executable code) stored in at least one memory 730 or otherwise.

[0128] The communication manager 720 may support wireless communication according to examples disclosed herein. For example, the communication manager 720 may be capable of, configured to, or operable to support components for obtaining a first list of access network combinations supporting dual-direction operation at the UE, wherein dual-direction operation enables the UE to send data packets associated with a data stream across a set of multiple access networks. The communication manager 720 may be capable of, configured to, or operable to support components for obtaining a second list of access network combinations supporting dual-direction operation at the UE. The communication manager 720 may be capable of, configured to, or operable to support components for initiating a registration process to a first access network and a second access network based on a joint selection of a first access network for a first protocol stack and a second access network for a second protocol stack, wherein the first and second access networks are jointly selected based on the first list and the second list of access network combinations.

[0129] By including or configuring a communication manager 720 according to an example as described herein, device 705 can support techniques for improving communication reliability, reducing latency, improving and reducing user experience related to processing, reducing power consumption, utilizing communication resources more efficiently, and improving coordination between devices.

[0130] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 715, one or more antennas 725, or any combination thereof, or otherwise cooperating with them. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or executed by at least one processor 740, at least one memory 730, code 735, or any combination thereof. For example, code 735 may include instructions that can be executed by at least one processor 740 to cause device 705 to perform various aspects of joint network selection for devices having two protocol stacks as described herein, or at least one processor 740 and at least one memory 730 may be otherwise configured to perform or support such operations individually or jointly.

[0131] Figure 8 A flowchart illustrating a method 800 for joint network selection for a device having two protocol stacks, according to one or more aspects of this disclosure, is shown. Operation of method 800 may be implemented by a UE or its components as described herein. For example, operation of method 800 may be performed by, as referenced... Figures 1 to 7 The UE 115 described herein performs the following: In some examples, the 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 use dedicated hardware to perform aspects of the described functions.

[0132] At 805, the method may include obtaining a first list of access network combinations that support dual-direction operation at the UE, wherein the dual-direction operation enables the UE to send data packets associated with a data stream across a set of multiple access networks. The operation at 805 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 805 may be provided as referenced. Figure 6 The described access network assembly component 625 is executed.

[0133] At 810, the method may include obtaining a second list of access network combinations that support dual-direction operation at the UE. The operation of 810 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 810 may be derived from, as referenced... Figure 6 The described access network assembly component 625 is executed.

[0134] At 815, the method may include initiating a registration process with a first access network and a second access network based on a joint selection of a first access network for a first protocol stack and a second access network for a second protocol stack, wherein the first and second access networks are jointly selected based on a first list of access network combinations and a second list of access network combinations. The operation of 815 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 815 may be provided as referenced. Figure 6 The described registration component 630 is executed.

[0135] Figure 9 A flowchart illustrating a method 900 for joint network selection for a device having two protocol stacks, according to one or more aspects of this disclosure, is shown. Operation of method 900 can be implemented by a UE or its components as described herein. For example, operation of method 900 can be achieved by, as referenced... Figures 1 to 7 The UE 115 described herein performs the following: In some examples, the 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 use dedicated hardware to perform aspects of the described functions.

[0136] At 905, the method may include performing a radio frequency scan to obtain a first list of available access networks against a first protocol stack. The operation of 905 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 905 may be derived from, as referenced... Figure 6 The described radio frequency scanning component 635 performs this function.

[0137] At 910, the method may include obtaining a first list of access network combinations that support dual-direction operation at the UE, wherein the dual-direction operation enables the UE to send data packets associated with a data stream across a set of multiple access networks. The operation at 910 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 910 may be derived from, as referenced... Figure 6 The described access network assembly component 625 is executed.

[0138] At 915, the method may include performing a radio frequency scan to obtain a second list of available access networks against a second protocol stack. The operation of 915 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 915 may be derived from, as referenced... Figure 6 The described radio frequency scanning component 635 performs this function.

[0139] At 920, the method may include obtaining a second list of access network combinations that support dual-direction operation at the UE. The operation at 920 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 920 may be derived from, as referenced... Figure 6 The described access network assembly component 625 is executed.

[0140] At 925, the method may include obtaining a first list of available access networks from a first protocol stack and a second list of available access networks from a second protocol stack, wherein the registration process is initiated based on the first list of available access networks, the second list of available access networks, the first list of access network combinations, and the second list of access network combinations. The operation of 925 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 925 may be derived from, as referenced... Figure 6 The described access network availability component 640 is executed.

[0141] At 930, the method may include initiating a registration process with a first access network and a second access network based on a joint selection of a first access network for a first protocol stack and a second access network for a second protocol stack, wherein the first and second access networks are jointly selected based on a first list of access network combinations and a second list of access network combinations. The operation of 930 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 930 may be derived from, as referenced... Figure 6 The described registration component 630 is executed.

[0142] Figure 10 A flowchart illustrating a method 1000 for joint network selection for a device having two protocol stacks, according to one or more aspects of this disclosure, is shown. Operation of method 1000 may be implemented by a UE or its components as described herein. For example, operation of method 1000 may be performed by, as referenced... Figures 1 to 7 The UE 115 described herein performs the following: In some examples, the 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 use dedicated hardware to perform aspects of the described functions.

[0143] At point 1005, the method may include a dual-directed operation at the UE based on a first protocol stack and a first access network, receiving a message indicating a first list of access network combinations during the registration process. The operation at point 1005 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at point 1005 may be provided by reference to [reference needed]. Figure 6 The described access network assembly component 625 is executed.

[0144] At 1010, the method may include obtaining a first list of access network combinations that support dual-direction operation at the UE, wherein the dual-direction operation enables the UE to send data packets associated with a data stream across a set of multiple access networks. The operation at 1010 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1010 may be derived from, as referenced... Figure 6 The described access network assembly component 625 is executed.

[0145] At point 1015, the method may include a dual-directed operation at the UE supported by a second protocol stack and a second access network, receiving a message indicating a second list of access network combinations during the registration process. The operation at point 1015 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at point 1015 may be derived from, as referenced... Figure 6 The described access network assembly component 625 is executed.

[0146] At 1020, the method may include obtaining a second list of access network combinations that support dual-direction operation at the UE. The operation at 1020 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1020 may be derived from, as referenced... Figure 6 The described access network assembly component 625 is executed.

[0147] At 1025, the method may include initiating a registration process with a first access network and a second access network based on a joint selection of a first access network for a first protocol stack and a second access network for a second protocol stack, wherein the first and second access networks are jointly selected based on a first list of access network combinations and a second list of access network combinations. The operation at 1025 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1025 may be provided as referenced. Figure 6 The described registration component 630 is executed.

[0148] Figure 11A flowchart illustrating a method 1100 for joint network selection for a device having two protocol stacks, according to one or more aspects of this disclosure, is shown. Operation of method 1100 can be implemented by a UE or its components as described herein. For example, operation of method 1100 can be performed by, as referenced... Figures 1 to 7 The UE 115 described herein performs the following: In some examples, the 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 use dedicated hardware to perform aspects of the described functions.

[0149] At 1105, the method may include determining that a dual-direction operation mode is enabled at the UE, wherein obtaining a first list of access network combinations and obtaining a second list of access network combinations are based on determining that a dual-direction operation mode is enabled at the UE. The operation of 1105 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1105 may be derived from, as referenced... Figure 6 The described operation mode is executed by component 645.

[0150] At 1110, the method may include obtaining a first list of access network combinations that support dual-direction operation at the UE, wherein the dual-direction operation enables the UE to send data packets associated with a data stream across a set of multiple access networks. The operation at 1110 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1110 may be derived from, as referenced... Figure 6 The described access network assembly component 625 is executed.

[0151] At 1115, the method may include obtaining a second list of access network combinations that support dual-direction operation at the UE. The operation at 1115 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1115 may be derived from, as referenced... Figure 6 The described access network assembly component 625 is executed.

[0152] At 1120, the method may include initiating a registration process with a first access network and a second access network based on a joint selection of a first access network for a first protocol stack and a second access network for a second protocol stack, wherein the first and second access networks are jointly selected based on a first list of access network combinations and a second list of access network combinations. The operation of 1120 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1120 may be provided as referenced. Figure 6 The described registration component 630 is executed.

[0153] The following provides an overview of the various aspects of this disclosure:

[0154] Aspect 1: A method for wireless communication at a UE, the method comprising: obtaining a first list of access network combinations supporting dual-direction operation at the UE, wherein the dual-direction operation enables the UE to transmit data packets associated with a data stream across multiple access networks; obtaining a second list of access network combinations supporting the dual-direction operation at the UE; and initiating a registration process to the first access network and the second access network based on a joint selection of a first access network for a first protocol stack and a second access network for a second protocol stack, the first access network and the second access network being jointly selected at least in part based on the first list of access network combinations and the second list of access network combinations.

[0155] Aspect 2: According to the method of aspect 1, the method further includes: performing a radio frequency scan to obtain a first list of available access networks for the first protocol stack; and performing the radio frequency scan to obtain a second list of available access networks for the second protocol stack; and obtaining the first list of available access networks from the first protocol stack and obtaining the second list of available access networks from the second protocol stack, wherein initiating the registration process is based at least in part on the first list of available access networks, the second list of available access networks, the first list of access network combinations, and the second list of access network combinations.

[0156] Aspect 3: According to the method of aspect 2, the method further includes: sorting the first list of access network combinations and the second list of access network combinations according to priority; selecting the first access network based at least in part on matching the sorted first list of access network combinations with the first list of available access networks; and selecting the second access network based at least in part on matching the sorted second list of access network combinations with the second list of available access networks.

[0157] Aspect 4: According to the method of aspect 3, the method further includes: selecting the first access network and the second access network based at least in part on the highest priority access network combination included in both the first list of access network combinations and the second list of access network combinations.

[0158] Aspect 5: The method according to any one of Aspects 1 to 4, wherein obtaining the first list of access network combinations comprises: retrieving the first list of access network combinations from the first protocol stack.

[0159] Aspect 6: According to the method of aspect 5, the first list of access network combinations is stored in a generic subscriber identity module associated with the first protocol stack.

[0160] Aspect 7: The method according to any one of Aspects 1 to 6, wherein obtaining the first list of access network combinations comprises: at least in part supporting the dual-direction operation at the UE based on the first protocol stack and the first access network, receiving a message indicating the first list of access network combinations during the registration process.

[0161] Aspect 8: The method according to any one of Aspects 1 to 7, wherein obtaining the second list of access network combinations comprises: retrieving the second list of access network combinations from the second protocol stack.

[0162] Aspect 9: According to the method of aspect 8, the second list of access network combinations is stored in a generic subscriber identity module associated with the second protocol stack.

[0163] Aspect 10: The method according to any one of Aspects 1 to 9, wherein obtaining the second list of access network combinations further comprises: at least in part supporting the dual-direction operation at the UE based on the second protocol stack and the second access network, receiving a message indicating the second list of access network combinations during the registration process.

[0164] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the generic subscriber identity module associated with the first protocol stack and the generic subscriber identity module associated with the second protocol stack are issued by the same network operator.

[0165] Aspect 12: The method according to any one of Aspects 1 to 11, the method further comprising: determining that a dual-direction operation mode is enabled at the UE, wherein obtaining the first list of access network combinations and obtaining the second list of access network combinations are at least partially based on determining that the dual-direction operation mode is enabled at the UE.

[0166] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the first access network and the second access network are associated with the same Public Land Mobile Network (PLMN) or different PLMNs, and the first access network and the second access network are associated with the same RAT or different RATs.

[0167] Aspect 14: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the UE performs a method according to any one of Aspects 1 to 13.

[0168] Aspect 15: A UE for wireless communication, the UE comprising at least one component for performing a method according to any one of aspects 1 to 13.

[0169] Aspect 16: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 13.

[0170] It should be noted that the methods described herein describe possible specific implementations. Operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0171] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0172] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0173] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, graphics processing unit (GPU), neural processing unit (NPU), FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a 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 combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

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

[0175] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible 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, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0176] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, 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). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0177] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing 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 “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0178] The term "determine" encompasses a wide range of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0179] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0180] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some of the drawings, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0181] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Obtain a first list of access network combinations that support dual-direction operation at the UE, wherein the dual-direction operation enables the UE to send data packets associated with a data stream across multiple access networks; Obtain a second list of access network combinations that support the dual-direction operation at the UE; as well as Based on the joint selection of the first access network for the first protocol stack and the second access network for the second protocol stack, a registration process is initiated to the first access network and the second access network, which are jointly selected at least in part based on the first list of access network combinations and the second list of access network combinations.

2. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Perform a radio frequency scan to obtain a first list of available access networks for the first protocol stack; as well as Perform the radio frequency scan to obtain a second list of available access networks for the second protocol stack; as well as The first list of available access networks is obtained from the first protocol stack, and the second list of available access networks is obtained from the second protocol stack, wherein the registration process is initiated at least in part based on the first list of available access networks, the second list of available access networks, the first list of access network combinations, and the second list of access network combinations.

3. The UE of claim 2, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The first access network is selected at least in part based on matching the first list of combined access networks with the first list of available access networks; and The second access network is selected at least in part based on matching the second list of combined access networks with the second list of available access networks.

4. The UE of claim 3, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The first access network and the second access network are selected based at least in part on the highest priority access network combination included in both the first list of access network combinations and the second list of access network combinations.

5. The UE of claim 1, wherein, in order to obtain the first list of access network combinations, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: Retrieve the first list of access network combinations from the first protocol stack.

6. The UE of claim 5, wherein the first list of access network combinations is stored in a generic subscriber identity module associated with the first protocol stack.

7. The UE of claim 1, wherein, in order to obtain the first list of access network combinations, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The dual-direction operation at the UE is supported at least in part based on the first protocol stack and the first access network, and a message indicating the first list of access network combinations is received during the registration process.

8. The UE of claim 1, wherein, in order to obtain the second list of access network combinations, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The second list of access network combinations is retrieved from the second protocol stack.

9. The UE of claim 8, wherein the second list of access network combinations is stored in a generic subscriber identity module associated with the second protocol stack.

10. The UE of claim 1, wherein, in order to obtain the second list of access network combinations, the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The dual-direction operation at the UE is supported at least in part based on the second protocol stack and the second access network, and a message indicating the second list of access network combinations is received during the registration process.

11. The UE of claim 1, wherein the generic subscriber identity module associated with the first protocol stack and the generic subscriber identity module associated with the second protocol stack are issued by the same network operator.

12. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: It is determined that a dual-direction operation mode is enabled at the UE, wherein obtaining the first list of access network combinations and obtaining the second list of access network combinations are at least in part based on determining that the dual-direction operation mode is enabled at the UE.

13. The UE according to claim 1, wherein: The first access network and the second access network are associated with the same Public Land Mobile Network (PLMN) or different PLMNs, and The first access network and the second access network are associated with the same radio access technology (RAT) or different RATs.

14. A method for conducting wireless communication at a user equipment (UE), the method comprising: Obtain a first list of access network combinations that support dual-direction operation at the UE, wherein the dual-direction operation enables the UE to send data packets associated with a data stream across multiple access networks; Obtain a second list of access network combinations that support the dual-direction operation at the UE; as well as Based on the joint selection of the first access network for the first protocol stack and the second access network for the second protocol stack, a registration process is initiated to the first access network and the second access network, which are jointly selected at least in part based on the first list of access network combinations and the second list of access network combinations.

15. The method of claim 14, further comprising: Perform a radio frequency scan to obtain a first list of available access networks for the first protocol stack; as well as Perform the radio frequency scan to obtain a second list of available access networks for the second protocol stack; as well as The first list of available access networks is obtained from the first protocol stack, and the second list of available access networks is obtained from the second protocol stack, wherein the registration process is initiated at least in part based on the first list of available access networks, the second list of available access networks, the first list of access network combinations, and the second list of access network combinations.

16. The method of claim 15, further comprising: The first access network is selected at least in part based on matching the first list of combined access networks with the first list of available access networks; as well as The second access network is selected at least in part based on matching the second list of combined access networks with the second list of available access networks.

17. The method according to claim 16, further comprising: The first access network and the second access network are selected based at least in part on the highest priority access network combination included in both the first list of access network combinations and the second list of access network combinations.

18. The method of claim 14, wherein obtaining the first list of access network combinations comprises: Retrieve the first list of access network combinations from the first protocol stack.

19. The method of claim 18, wherein the first list of access network combinations is stored in a generic subscriber identity module associated with the first protocol stack.

20. A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to: Obtain a first list of access network combinations that support dual-direction operation at the user equipment (UE), wherein the dual-direction operation enables the UE to send data packets associated with a data stream across multiple access networks; Obtain a second list of access network combinations that support the dual-direction operation at the UE; and Based on the joint selection of the first access network for the first protocol stack and the second access network for the second protocol stack, a registration process is initiated to the first access network and the second access network, which are jointly selected at least in part based on the first list of access network combinations and the second list of access network combinations.

Images