Dual boot operations for wireless communications

Abstract

Methods, systems, and devices are described for wireless communication. A user equipment (UE) can be configured to support multiple subscriber identity modules (SIMs) and multiple corresponding subscribers that can provide wireless service to the UE. Each of the SIMs can be associated with a corresponding protocol stack. The UE can be configured with a different layer than the protocol stacks, such as a dual boot layer. The dual boot layer can manage routing and booting of data traffic associated with one or more of the protocol stacks of the UE. The UE can process, via the dual boot layer, data traffic via one or more of the protocol stacks of the UE based on a first set of UE route selection policy (URSP) rules, traffic information associated with the data traffic, and capabilities of the one or more of the protocol stacks.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 919,060, filed October 17, 2024, entitled “DUAL-STEERINGOPERATIONS FOR WIRELESS COMMUNICATIONS,” and U.S. Provisional Patent Application No. 63 / 620,717, filed January 12, 2024, entitled “DUAL-STEERING OPERATIONS FOR WIRELESS COMMUNICATIONS,” each of which has been assigned to the assignee of this application and each of which is expressly incorporated herein by reference. Technical Field

[0003] The following text relates to wireless communication, including dual-boot operation for wireless communication. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. 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 of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses supporting dual-booting operation for wireless communication. For example, the described technology implements a layer, such as a dual-booting layer, that supports multiple subscriptions for User Equipment (UE). The UE may be configured with one or more protocol stacks to support multiple subscriptions, and each of the one or more protocol stacks may be configured to communicate with an associated access network. The dual-booting layer may differ from the protocol stacks and may be configured to manage (e.g., bootstrap or route) data services of the protocol stacks and to manage (e.g., bootstrap or route) those data services through the associated access network. The dual-booting layer may manage data services based on UE Routing Policy (URSP) rules.

[0006] A method for wireless communication by a UE is described. The method may include: transmitting, via a first protocol stack of a set of multiple protocol stacks of the UE, an indication of the UE's ability to route data services associated with the UE via the first protocol stack or a second protocol stack of the set of multiple protocol stacks, wherein the first protocol stack corresponds to a first subscription of a set of multiple subscriptions of the UE, and the second protocol stack corresponds to a second subscription of the set of multiple subscriptions; receiving, based on the UE's capability, a first set of URSP rules for routing the data services associated with the UE; and, based on the first set of URSP rules and the UE's capability, routing the data services associated with the UE via a higher layer of the UE, via one or both of the first protocol stack or the second protocol stack.

[0007] 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 so that the UE: transmits an indication of the UE's ability to route data services associated with the UE via a first protocol stack in a set of multiple protocol stacks, wherein the first protocol stack corresponds to a first subscription in a set of multiple subscriptions of the UE, and the second protocol stack corresponds to a second subscription in the set of multiple subscriptions; receives a first set of URSP rules for routing the data services associated with the UE based on the UE's capability; and routes the data services associated with the UE via one or both of the first protocol stack or the second protocol stack, via a higher layer of the UE, based on the first set of URSP rules and the UE's capability.

[0008] Another UE for wireless communication is described. The UE may include: components for transmitting an indication of the UE's ability to route data services associated with the UE via a first protocol stack in a set of multiple protocol stacks, wherein the first protocol stack corresponds to a first subscription in a set of multiple subscriptions of the UE, and the second protocol stack corresponds to a second subscription in the set of multiple subscriptions; components for receiving a first set of URSP rules for routing the data services associated with the UE based on the UE's capability; and components for routing the data services associated with the UE via a higher layer of the UE, via one or both of the first and second protocol stacks, based on the first set of URSP rules and the UE's capability.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: transmit an indication of the UE's capability to route data services associated with the UE via a first protocol stack in a set of multiple protocol stacks, wherein the first protocol stack corresponds to a first subscription in a set of multiple subscriptions of the UE, and the second protocol stack corresponds to a second subscription in the set of multiple subscriptions; receive a first set of URSP rules for routing the data services associated with the UE based on the UE's capability; and route the data services associated with the UE via one or both of the first protocol stack and the second protocol stack, via a higher layer of the UE, based on the first set of URSP rules and the UE's capability.

[0010] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first set of URSP rules may be received via the first protocol stack, and the method, apparatus, and nontransitory computer-readable media may include further operations, features, components, or instructions for receiving a second set of URSP rules for guiding the data service via the second protocol stack and based on the capability of the UE, wherein the first set of URSP rules may be associated with the first protocol stack, and the second set of URSP rules may be associated with the second protocol stack.

[0011] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first set of URSP rules can be received via the higher layer of the UE and can be associated with both the first protocol stack and the second protocol stack.

[0012] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, each rule in the first set of URSP rules may include a set of routing descriptors (RSDs) and a service descriptor, and each RSD in the set of RSDs may include: a preferred access type indicating whether single boot or dual boot is performed; and a validity field indicating one or more radio access technology (RAT) capabilities corresponding to one or more of the first protocol stack, the second protocol stack, the first subscription, or the second subscription or any combination thereof.

[0013] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, routing the data service via one or both of the first protocol stack or the second protocol stack may include operations, features, components, or instructions for performing the following actions: routing the data service based on a first URSP rule, which is based on service information associated with the data service and one or more service descriptors associated with one or more URSP rules in the first set of URSP rules.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, routing the data service based on the first URSP rule may include operations, features, components, or instructions for performing the following actions: routing the data service via both the first protocol stack and the second protocol stack based on the preferred access type associated with the first RSD of the first URSP rule for routing the data service, the first RSD being based on the capabilities of one or both of the first and second protocol stacks and one or more validity indicators associated with one or more RSDs associated with the first URSP rule.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, routing the data service based on the first URSP rule may include operations, features, components, or instructions for performing the following actions: routing the data service via one of the first protocol stacks or the second protocol stack based on the preferred access type associated with a first RSD of the first URSP rule for routing the data service, the first RSD being based on capabilities associated with one or both of the first and second protocol stacks and one or more validity indicators associated with one or more RSDs of the first URSP rule.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, routing the data service based on the first URSP rule may include operations, features, components, or instructions for performing the following actions: routing the data service via one of the first protocol stack or the second protocol stack based on a first RSD associated with the first URSP rule for routing the data service, wherein the first RSD is associated with the first URSP rule based on an RSD and the validity indicator associated with the first RSD is empty.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, each RSD in this set includes a subscription validity indicator that identifies the protocol stack used to route the data service.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, routing the data service based on the first URSP rule may include operations, features, components, or instructions for performing the following actions: routing the data service via a protocol stack identified by a subscription validity indicator associated with the first RSD, guided by a preferred access type indication sheet associated with the first RSD, the first RSD being associated with the first URSP rule for routing the data service and based on the capabilities of one or both of the first and second protocol stacks and one or more validity indicators associated with one or more RSDs associated with the first URSP rule.

[0019] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, routing the data service based on the first URSP rule may include operations, features, components, or instructions for performing the following actions: routing the data service via one or both of the first protocol stack or the second protocol stack based on the fact that the subscription validity indicator associated with the first RSD of the first URSP rule for routing the data service is empty, the first RSD being based on the capabilities of one or both of the first and second protocol stacks and one or more validity indicators associated with one or more RSDs associated with the first URSP rule.

[0020] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, routing the data service via one or both of the first protocol stack or the second protocol stack may include operations, features, components, or instructions for routing the data service via both the first protocol stack or the second protocol stack.

[0021] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for performing the following actions: initiating a first packet data unit (PDU) session at the first protocol stack; initiating a second PDU session at the second protocol stack; sending a first request to the core network and via the first protocol stack to establish the first PDU session, wherein the first request indicates an identifier associated with the second protocol stack and an identifier associated with the second PDU session; and sending a second request to the core network and via the second protocol stack to establish the second PDU session, wherein the second request indicates an identifier associated with the first protocol stack and an identifier associated with the first PDU session.

[0022] A method for wireless communication by a network entity is described. The method may include: receiving from a UE an indication of the UE's ability to bootstrap data services associated with the UE via a set of multiple protocol stacks of the UE, wherein each protocol stack of the UE corresponds to a corresponding subscription in a set of multiple subscriptions of the UE; updating a first set of URSP rules based on the UE's capability to support dual bootstrap functionality at the UE; and sending the first set of URSP rules to the UE.

[0023] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the memories. The processors may operate individually or jointly to execute the code so that the network entity: receives from a UE an indication of the UE's ability to bootstrap data services associated with the UE via a set of multiple protocol stacks of the UE, wherein each protocol stack of the UE corresponds to a corresponding subscription in a set of multiple subscriptions of the UE; updates a first set of URSP rules, at least in part, based on the UE's capability, to support dual-bootstrap functionality at the UE; and sends the first set of URSP rules to the UE.

[0024] Another network entity for wireless communication is described. This network entity may include: components for receiving from a UE an indication of the UE's ability to bootstrap data services associated with the UE via a set of multiple protocol stacks of the UE, wherein each protocol stack of the UE corresponds to a corresponding subscription in a set of multiple subscriptions of the UE; components for updating a first set of URSP rules based on the UE's capability to support dual-bootstrap functionality at the UE; and components for sending the first set of URSP rules to the UE.

[0025] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive from a UE an indication of the UE's ability to bootstrap data services associated with the UE via a set of multiple protocol stacks of the UE, wherein each protocol stack of the UE corresponds to a corresponding subscription in a set of multiple subscriptions of the UE; update a first set of URSP rules, at least in part, based on the UE's capability, to support dual-bootstrap functionality at the UE; and send the first set of URSP rules to the UE.

[0026] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first set of URSP rules may be associated with a first protocol stack in the set of multiple protocol stacks of the UE, and the method, apparatus, and nontransitory computer-readable media may include further operations, features, components, or instructions for transmitting a second set of URSP rules based on the UE's capability to support the dual-booting functionality at the UE, wherein the second set of URSP rules may be associated with a second protocol stack in the set of multiple protocol stacks of the UE.

[0027] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, this first set of URSP rules may be associated with this set of multiple protocol stacks of the UE.

[0028] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, each rule in the first set of URSP rules may include a set of RSDs and a service descriptor, and each RSD in the set of RSDs may include: a preferred access type indicating whether single bootstrapping or dual bootstrapping is performed; and a validity field indicating one or more RAT capabilities corresponding to one or more of the following: a first protocol stack in the set of multiple protocol stacks, a second protocol stack in the set of multiple protocol stacks, a first subscription in the set of multiple subscriptions, or a second subscription in the set of multiple subscriptions, or any combination thereof.

[0029] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, each RSD in the set of RSDs includes a subscription validity indicator that identifies which protocol stack in the set of multiple protocol stacks of the UE routes the service.

[0030] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving from the UE a first request to establish a first PDU session associated with a first protocol stack in the set of multiple protocol stacks of the UE, wherein the first request includes an identifier associated with a second protocol stack in the set of multiple protocol stacks of the UE and an identifier associated with a second PDU session associated with the second protocol stack.

[0031] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving a second request from the UE to establish the second PDU session, wherein the second request includes indications of an identifier associated with the first protocol stack and an identifier associated with the first PDU session.

[0032] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for associating the first PDU session and the second PDU session with the UE based on receiving the first request and the second request. Attached Figure Description

[0033] Figure 1 and Figure 2 An example of a wireless communication system supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure is shown.

[0034] Figures 3 to 5 Examples of user equipment and access networks supporting dual-boot operation for wireless communication are shown according to one or more aspects of this disclosure.

[0035] Figure 6 An example of a process flow supporting dual-boot operation for wireless communication is shown according to one or more aspects of this disclosure.

[0036] Figure 7 and Figure 8 A block diagram of a device supporting dual-boot operation for wireless communication is shown, according to one or more aspects of this disclosure.

[0037] Figure 9 A block diagram of a communication manager supporting dual-boot operation for wireless communication, according to one or more aspects of this disclosure, is shown.

[0038] Figure 10 A diagram is shown of a system including a device supporting dual-boot operation for wireless communication, according to one or more aspects of this disclosure.

[0039] Figure 11 and Figure 12 A block diagram of a device supporting dual-boot operation for wireless communication is shown, according to one or more aspects of this disclosure.

[0040] Figure 13 A block diagram of a communication manager supporting dual-boot operation for wireless communication, according to one or more aspects of this disclosure, is shown.

[0041] Figure 14 A diagram is shown of a system including a device supporting dual-boot operation for wireless communication, according to one or more aspects of this disclosure.

[0042] Figures 15 to 19 A flowchart illustrating a method for supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure is shown. Detailed Implementation

[0043] Various aspects of this disclosure relate to a wireless communication device (such as a User Equipment (UE)) that can be configured with multiple subscriptions to support one or more wireless services over one or more access networks. Specifically, this disclosure relates to a new layer of a UE that can be configured to manage data services associated with multiple subscriptions. For example, the UE can be configured to support multiple subscriptions via a corresponding Subscriber Identification Module (SIM) associated with the UE (e.g., included in the UE or electronically registered for the UE, such as in an electronic SIM (eSIM)). By way of example, a multi-SIM UE with two SIMs may include a first SIM and a second SIM, the first SIM using a first network to provide a subscription for international voice calling services, and the second SIM using a second network to provide a subscription for domestic voice calling services. As another example, a multi-SIM UE may include one SIM for a personal subscription using the first network and another SIM for a business subscription using the same network.

[0044] Each SIM in a SIM can be configured to connect the UE to the core network via a network entity, such as a base station or access network. Multiple SIMs can be configured to connect to one or more core networks via the same or different network entities. The core network can provide radio services supported by subscriptions. The UE can be configured with multiple protocol stacks to support multiple SIMs and corresponding subscriptions. For example, each SIM can be associated with a corresponding protocol stack. The protocol stack can be configured in the UE's modem and can be used to route data traffic (e.g., data from one or more applications of the UE) from the UE's operating system and via connections (such as Protocol Data Unit (PDU) sessions) to one or more core networks.

[0045] According to various aspects of this disclosure, the UE may be configured at the modem with layers or other functionalities different from those associated with one or more protocol stacks of one or more subscriptions. A layer may be a higher layer, such as a dual bootstrapping layer, which manages the routing and bootstrapping of data services across multiple protocol stacks of the UE through one or more access networks and to one or more core networks. In some cases, a dual bootstrapping layer may be configured to route or boots data services through a single protocol stack of the UE. In other cases, the UE may be configured such that the dual bootstrapping layer can route or boots data services through multiple protocol stacks in the protocol stack at a given time. Bootstrapping data via multiple protocol stacks can be referred to as dual bootstrapping.

[0046] The dual bootstrapping layer can be configured to route or direct data services across multiple protocol stacks through one or more access networks based on one or more UE Routing Policy (URSP) rules. The UE can receive URSP rules from one or more core networks (e.g., directly or indirectly via Radio Access Network (RAN) nodes). URSP rules can provide rules or conditions under which the dual bootstrapping layer routes or directs data services to one or more protocol stacks. In some cases, routing rules can be based on UE-associated capabilities, UE manufacturer configuration, subscription choices (such as whether the user has subscribed to a specific service, e.g., Non-Terrestrial Network (NTN) or 6G), user preferences, service information associated with the data service, etc.

[0047] The UE can be configured to associate a unique session (such as a PDU session) with each protocol stack in the UE's protocol stack. For example, the UE can determine to establish a unique PDU session associated with each protocol stack via a PDU session establishment process coordinated with one or more core networks in the core network. Once established, the UE and the core network can communicate with each other via the PDU connection, such as by sending and receiving data. The core network can use the PDU connection to send one or more URSP rules to the UE.

[0048] In some cases, the UE can notify the core network of its dual-booting capability, and in response, the core network can update one or more URSP rules in the URSP rules to enable the UE to utilize its dual-booting capability. The core network can send the updated URSP rules to the UE, and the UE can use the updated URSP rules to manage routing and booting services through the appropriate protocol stack.

[0049] By enabling the UE to have additional functionalities that differ from the protocol stack, such as a higher layer (e.g., dual bootstrap layer) or manage data services within the protocol stack, the UE can experience improved communication reliability, reduced latency, an improved user experience associated with reduced processing, and more efficient utilization of communication resources.

[0050] The various aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to dual-boot operation for wireless communication, and are further described with reference to these diagrams.

[0051] Figure 1 An example of a wireless communication system 100 supporting dual-boot operation for wireless communication 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.

[0052] 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, RAN node, or network equipment, among other designations. 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).

[0053] 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 Some example UE 115s are shown below. Figure 1As shown, 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 the UE 115 or network entity 105).

[0054] 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.

[0055] 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. The 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, or may include 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 may communicate with the core network 130 via communication link 155.

[0056] One or more of the network entities 105 or network equipment 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, Node B, evolved Node B (eNB), next-generation Node B or gigabit Node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home Node B, home evolved Node B 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 physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0057] 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 across 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 sponsored by the O-RAN Alliance), 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)).

[0058] 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 higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities 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) can 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 can 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 can each be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split may be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can (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.

[0059] 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 an IAB mobile terminal (IAB-MT) 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.

[0060] 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).

[0061] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability). 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 relay UE transmissions through other IAB nodes 104). 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 signaling notifications to child IAB nodes or UE 115.

[0062] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 with 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 of IAB node 104 (e.g., other IAB nodes). Communication with IAB node 104 can be scheduled by the IAB donor or DU 165 of IAB node 104.

[0063] In the context of applying the techniques described herein to 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).

[0064] 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.

[0065] The UE 115 described herein may be able to communicate with various types of devices, such as the UE 115 which may sometimes operate 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.

[0066] 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 may be configured with 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).

[0067] 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 may 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.

[0068] 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, and The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for communication resources can be organized according to 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).

[0069] 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 certain 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 certain 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.

[0070] 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)).

[0071] Depending on the technology, carriers can be used to multiplex physical channels for communication. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used 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 may be defined by a set of symbol periods and may 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 may monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set may 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 may 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 public 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 configured to transmit control information to UE115 (e.g., a particular UE).

[0072] In some examples, network entity 105 (e.g., base station 140, RU 170) can 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) can overlap, but coverage areas 110 (e.g., different coverage areas) can 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 can 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 support communication in coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

[0073] 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.

[0074] 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 such a 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, where each UE 115 sends 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.

[0075] 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 delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may 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.

[0076] 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 High 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).

[0077] 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.

[0078] 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.

[0079] 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 specific 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. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0080] 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.

[0081] Based on the aspects described herein, UE 115 can be configured with multiple protocol stacks. These multiple protocol stacks may correspond to multiple subscriptions supporting one or more radio services through one or more network entities (such as one or more base stations 140). A protocol stack may refer to one or more protocol layers, which may be ordered in a layered architecture (e.g., structure). In some examples, UE 115 may be configured with new layers different from the protocol stacks, such as a dual bootstrapping layer. The dual bootstrapping layer can manage the routing and bootstrapping of data services such as those described herein through one or more access networks and to one or more core networks, based on one or more rules, information associated with data services, and the capabilities of UE 115 or one or more protocol stacks in UE 115's protocol stack.

[0082] Figure 2 An example of a wireless communication system 200 supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure is shown. In some examples, the wireless communication system 200 may implement as described in the reference. Figure 1 The described aspects of the wireless communication system 100 may be implemented by aspects of the wireless communication system. For example, the wireless communication system 200 may include UE 115-a, access network 145-a, access network 145-b, and core network 130-a, which may be respectively as referenced. Figure 1 Examples of the described UE 115 and core network 130. The wireless communication system 200 may support multiple RATs, including 4G LTE, 5G NR, or combinations thereof. For example, one or more of access networks 145-a or 145-b may support one or more of 4G LTE or 5G NR. It should be noted that the wireless communication system 200 may support radio access technologies other than 5G NR.

[0083] UE 115-a and access network 145-a may perform wireless communication (e.g., receiving, acquiring, transmitting, or outputting one or more control messages or data) via communication link 125-a. Additionally or alternatively, UE 115-a and access network 145-b may perform wireless communication (e.g., receiving, acquiring, transmitting, or outputting one or more control messages or data) via communication link 125-b. Communication link 125-a and communication link 125-b may be as referenced. Figure 1 An example of the described communication link 125.

[0084] UE 115-a can support the routing or guidance of data services for different radio services through different access networks (such as one or more of access networks 145-a or 145-b), each of which can communicate (e.g., receive, acquire, transmit or output one or more of control information or data) to one or more core networks (such as core network 130-a) to support radio services (e.g., applications enabled for UE 115-a).

[0085] One or more access networks 145-a and 145-b may provide UE 115-a with connectivity to core network 130-a to provide access to radio services (e.g., one or more applications enabled for UE 115-a). For example, access network 145-a may communicate (e.g., receive, acquire, transmit, or output one or more of its own) control information or data to core network 130-a via communication link 125-c, or access network 145-b may communicate (e.g., receive, acquire, transmit, or output one or more of its own) control information or data to core network 130-a via communication link 125-d. Communication links 125-c and 125-d may be as described in reference... Figure 1 An example of the described communication link 125.

[0086] UE 115-a may connect to core network 130-a via one or more of access networks 145-a or 145-b, and at least in part, based on a connection procedure. For example, UE 115-a (or one or more protocol stacks therein) may perform a registration procedure, whereby UE 115-a (or one or more protocol stacks therein) obtains an IP address, and core network 130-a may establish a context for UE 115-a (e.g., also referred to as the UE context), thereby allowing UE 115-a to communicate with other network entities (e.g., network functions). In response to UE 115-a successfully completing the registration procedure, UE 115-a (or one or more protocol stacks therein) may connect to core network 130-a. Core network 130-a may manage various functions, such as providing radio services for subscriptions associated with the UE.

[0087] UE 115-a may include an operating system 225, a modem 220, and other components. The operating system 225 can manage and support certain basic and common functions of the UE, such as scheduling tasks, managing hardware and software resources, controlling peripheral devices, and executing applications (such as application 230). The modem 220 can manage the transmission of data to and from UE 115-a. For example, the modem 220 can manage the transmission of data associated with application 230 from UE 115-a and to core network 130-a. UE 115-a may include one or more data interfaces 235 between the operating system 225 and the modem 220 to facilitate the transmission of data to and from the operating system 225 and the modem 220. For example, the modem 220 can receive data traffic associated with one or more applications in application 230 from the operating system 225 and via data interface 235. Once data traffic is received, the modem 220 can manage the transmission of data traffic to core network 130-a. Modem 220 can also manage the reception of data services from core network 130-a to UE 115-a. Once a data service is received, modem 220 can control the transmission of the data service to the appropriate application 230 via data interface 235.

[0088] In some cases, UE 115-a may be a multi-subscriber identity module (SIM) device and may be equipped with multiple SIMs. Multiple SIMs allow UE 115-a to register with and connect to one or more access networks and one or more core networks to access the subscription services associated with each SIM. For example, UE 115-a may be equipped with a first SIM 202 and a second SIM 204, such as at modem 220. The first SIM 202 may be configured to connect to access network 145-a to access services provided by one or more core networks (such as core network 130-a). The second SIM 204 may be configured to connect to access network 145-b to access services provided by one or more core networks (such as core network 130-a). In some cases, access network 145-a and access network 145-b may be the same access network. In other cases, access network 145-a and access network 145-b may be different networks. Furthermore, although in Figure 2A single core network 130-a is shown, but in some cases, service may be provided by more than one core network. UE 115-a can register and connect to one or more of access networks 145-a or 145-b using either the first SIM 202 or the second SIM 204. UE 115-a can also register and connect to core network 130-a via one or more of access networks 145-a or 145-b and using either the first SIM 202 or the second SIM 204. Each of the first SIM 202 and the second SIM 204 of UE 115-a can be associated with a subscriber identifier, which may include an International Mobile Subscriber Identity (IMSI) and a Mobile Subscriber Integrated Services Digital Network Number (MSISDN).

[0089] To support multiple SIMs, the modem 220 of UE 115-a can be configured with multiple protocol stacks. Each of the multiple protocol stacks can be associated with one of the multiple SIMs and their corresponding subscriptions. For example, modem 220 can be configured with a first protocol stack 205 and a second protocol stack 210. It should be noted that UE 115-a can be equipped with more than two protocol stacks. Protocol stack 205 can be associated with a first SIM 202 (which can be associated with a first subscription), and protocol stack 210 can be associated with a second SIM 204 (which can be associated with a second subscription). Each of the first protocol stack 205 and the second protocol stack 210 can include one or more protocol layers, which can be ordered in a layered architecture.

[0090] For example, at higher levels, each of protocol stacks 205 and 210 may include one or more of the following: a Non-Access Stratum (NAS) layer 255, which can support service and signaling messages between UE 115-a and core network 130-a, and the establishment of communication sessions between UE 115-a and core network 130-a; an Access Stratum (AS) layer 260, which can support data transmission over a wireless connection; and an RF layer 265, which can support radio transmission and reception. Protocol stacks 205 and 210 may not be limited to the layers shown, but may include different or additional layers.

[0091] Modem 220 can also be configured with new layers that are different from protocol stacks 205 and 210. For example, modem 220 can be configured with higher layers, such as dual bootstrap layer 215. Dual bootstrap layer 215 can be different from both protocol stacks 205 and 210. For example, dual bootstrap layer 215 can be separate from both protocol stacks 205 and 210 (including different protocol layers within each of protocol stacks 205 and 210) (e.g., deencapsulated). Dual bootstrap layer 215 can reside (e.g., be located) above protocol stacks 205 and 210. While dual bootstrap layer 215 can reside above protocol stacks 205 and 210, dual bootstrap layer 215 can interface with other layers or components (e.g., hardware, software) above and below dual bootstrap layer 215. Therefore, dual bootstrap layer 215 can support interoperability with one or more different protocol layers within each of protocol stacks 205 and 210.

[0092] The dual bootstrapping layer 215 may also include a control plane and a user plane. The control plane of the dual bootstrapping layer 215 may be at least partially based on bootstrapping rules (such as URSP rules) that can be obtained (e.g., received) from the network (e.g., core network 130-a) to manage the bootstrapping or routing of data services to one or more protocol stacks 205 and 210 of UE 115-a. The dual bootstrapping layer 215 may also be configured with a mechanism (e.g., triggering conditions) for UE 115-a to receive URSP rules, for example, in response to registration by UE 115-a or one or more of its protocol stacks 205 and 210 to the core network 130-a, where registration includes an indication of support for dual bootstrapping capability in response to the establishment of a PDU session by one of the protocol stacks (such as protocol stack 205). In some cases, the URSP rules may be updated rules, such as when an indication of support for dual bootstrapping capability is provided to the core network 130-a. The updated URSP rules can be configured to support dual booting capability of one or more of the protocol stacks 205 and 210 of UE 115-a or UE 115.

[0093] In some cases, the user plane of dual bootstrapping layer 215 may support one or more of the following: Hypertext Transfer Protocol (HTTP) (e.g., HTTP3), Multipath QUIC (MP-QUIC) protocol, User Datagram Protocol (UDP), or IP. Dual bootstrapping layer 215 may determine the establishment of at least a certain number of MP-QUIC connections based, at least in part, on the number of Quality of Service (QoS) flows associated with both protocol stack 205 and protocol stack 210. For example, UE 115-a may establish one MP-QUIC connection per QoS flow. Additionally or alternatively, the user plane of dual bootstrapping layer 215 may support one or more of the following: Multipath Transmission Control Protocol (MPTCP), TCP, IP, or Aware Service Bootstrapping, Handover, and Split-Lower Layer (ATSSS-LL) protocol.

[0094] The dual bootstrapping layer 215 can also manage constraints on UE 115-a based on UE 115-a's hardware / software capabilities or device architecture configuration (e.g., RF band combination capabilities, chipset capabilities, manufacturer configuration, user preferences, subscription choices, or a combination thereof). In this way, routing and bootstrapping decisions can be UE-centric rather than network-based.

[0095] The dual bootstrapping layer 215 can coordinate the session management functionality of each of the first protocol stack 205 or the second protocol stack 210, thereby triggering the establishment of one or more corresponding PDU sessions and connections by one or more of the protocol stacks 205 or 210. For example, the dual bootstrapping layer 215 can coordinate the establishment of PDU session 295 between the first protocol stack 205 and the core network 130-a, and the establishment of PDU session 297 between the second protocol stack 210 and the core network 130-a. The dual bootstrapping layer 215 can enable the first protocol stack 205 to initiate PDU session 295 at UE 115-a, and can also enable the sending of a message (e.g., a PDU session establishment request message) via access network 145-a to the core network 130-a requesting the establishment of PDU session 295 between the first protocol stack 205 of the core network 130-a and UE 115-a. UE 115-a can receive a PDU session establishment response message indicating whether the request is accepted or rejected from core network 130-a and via access network 145-a. Upon accepting a request to establish PDU session 295, a PDU session 295 connection can be established between core network 130-a and the first protocol stack 205. For example, core network 130-a can associate (e.g., bind) the requested PDU session to the corresponding protocol stack. For example, core network 130-a can bind PDU session 295 to protocol stack 205. Similarly, dual bootstrapping layer 215 can enable the second protocol stack 210 to initiate PDU session 297 at UE 115-a, and can send a PDU session establishment request message via access network 145-b to core network 130-a requesting the establishment of PDU session 297 between core network 130-a and the second protocol stack 210 of UE 115-a. UE 115-a can receive a PDU session establishment response message indicating whether the request has been accepted or rejected from core network 130-a and via access network 145-b. Upon accepting a request to establish PDU session 297, a PDU session 297 connection can be established between core network 130-a and the second protocol stack 210. For example, core network 130-a can bind PDU session 297 to protocol stack 210.

[0096] Once a PDU session is established, core network 130-a can send one or more URSP rules to UE 115-a via the PDU session connection. Core network 130-a may include a Unified Data Repository (UDR) that stores UE information (e.g., subscription information), which can be managed (e.g., updated, removed, modified, adjusted, deleted, stored) by other network entities (such as the Policy Control Function (PCF) of core network 130-a) for URSP rules used by UE 115-a. Core network 130-a may also include a Unified Data Management Function (UDM) that stores UE information. Core network 130-a may also include an Access and Mobility Management Function (AMF) that can obtain UE information from the UDM and output (e.g., forward, send, route) the UE information to the PCF of core network 130-a. Based on UE information, the PCF of core network 130-a can provide URSP rules to one or more of UE 115-a, access network 145-a, or access network 145-b.

[0097] In some cases, URSP rules can be provided (e.g., sent) to UE 115-a by core network 130-a via one or more PDU sessions in a PDU session. For example, URSP rule 292 can be sent from core network 130-a to protocol stack 205 of UE 115-a via PDU session 295, or URSP rule 294 can be sent from core network 130-a to protocol stack 210 of UE 115-a via PDU session 297. Alternatively, URSP rule 292 and URSP rule 294 can both be sent to UE 115-a via PDU session 295 and PDU session 297, respectively. In some cases, access network 145-a or access network 145-b may obtain one or more of URSP rules 292 and 294 from core network 130-a, and access network 145-a or access network 145-b may send signaling carrying one or more of URSP rules 292 and 294 to UE 115-a via one or both of protocol stacks 205 and 210. UE 115-a may process (e.g., demodulate, decode) the signaling to identify one or more URSP rules 292 and 294 associated with one or both of protocol stacks 205 and 210. Dual bootstrapping layer 215 may obtain (e.g., receive) one or more of URSP rules 292 and 294 from one or both of protocol stacks 205 and 210.

[0098] In some cases, URSP rule 292 and URSP rule 294 may be the same set of rules. In other cases, URSP rule 292 and URSP rule 294 may be different rules applied independently to a specific protocol stack. For example, URSP rule 292 may include rules to be applied by the first protocol stack 205, while URSP rule 294 may include rules to be applied by the second protocol stack 210.

[0099] URSP rules 292 and 294 may each include a set of rules that will be used by one or more of protocol stacks 205 and 210 to determine how to route services from UE 115-a to the core network. For example, a URSP rule may provide one or more rules or conditions under which the dual bootstrapping layer 215 will coordinate the routing or bootstrapping of data services to one or more of protocol stacks 205 and 210. In some cases, URSP rules may be based on or depend on capabilities associated with UE 115-a or subscriptions associated with different protocol stacks 205 and 210 (e.g., RAT capabilities associated with a subscription), UE manufacturer configuration, subscription selection (such as whether the user has subscribed to a specific service, such as NTN or 6G), user preferences, service information associated with data services, etc.

[0100] Each URSP rule may include information mapping different types of data services to one or more rules that indicate where to route that type of data service when certain conditions are met. For example, each URSP rule may include a service descriptor. Different types of data services can be indicated in the URSP rule by service information (also referred to as a "service descriptor") that determines when a particular URSP rule applies. When a service descriptor matches the corresponding information of an application (such as one of applications in application 230) associated with the data service to be routed, the dual bootstrapping layer 215 can determine that the URSP rule applies. The service descriptor can then be mapped in the URSP rule to one or more routing descriptors (RSDs). RSDs may include one or more parameters or fields indicating different conditions under which the corresponding type of data service (as indicated by the service descriptor) should be routed to a specific PDU session (such as via the associated protocol stack) also indicated by the RSD. For example, the RSD field may indicate information such as application descriptor, data network name (DNN), PDU session information, preferred access type, etc.

[0101] The dual bootstrapping layer 215 can determine, at least in part, whether a particular URSP rule applies to a particular application data service and how such data service is routed (e.g., via which protocol stack and corresponding PDU session) based on one or more of the service descriptor and RSD.

[0102] Figure 3 An example block diagram 300 of a UE115-b and a core network 130-b supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure is shown. In some examples, the UE 115-b and the core network 130-b can implement as described in reference respectively. Figure 1 and Figure 2 The described aspects of wireless communication system 100 or wireless communication system 200 may be implemented by or by aspects of these wireless communication systems. For example, UE 115-b may be as described with reference to... Figure 1 and Figure 2 The example described is UE 115 or UE 115-a. Core network 130-b can be as described in reference respectively. Figure 1 and Figure 2 Examples of core network 130 or core network 130-a as described.

[0103] UE 115-b may include an operating system 325 and a modem 320. The operating system 325 may support one or more applications 330. The operating system 325 may be as described in the reference. Figure 2 An example of the operating system 225 described herein. Modem 320 may interface with operating system 325 via data interface 335 to receive and transmit data services associated with one or more applications 330. Modem 320 may be as described in the reference. Figure 2 An example of the described modem 220.

[0104] The modem 320 can be configured with multiple subscriptions (such as via multiple SIMs) and corresponding protocol stacks to support one or more wireless services, such as reference SIMs, over one or more access networks. Figure 1 and Figure 2 As described. For example, UE115-b can be configured with protocol stack 305 and protocol stack 310, which can be as described in the reference. Figure 2 Examples of protocol stack 205 and protocol stack 210 are described.

[0105] The modem 320 can be additionally configured to support dual boot and can be configured with a dual boot layer 315, which can be as shown in the reference. Figure 2An example of the described dual bootstrapping layer 215. Dual bootstrapping layer 315 can be configured to route or bootstrap data services received from operating system 325 via data interface 335 to one or more of protocol stacks 305 and 310. Data can be routed from one or more of protocol stacks 305 and 310 to core network 130-b via one or more corresponding PDU sessions 395 and 397.

[0106] In some cases, UE 115-b may send an indication of its dual-booting capability to core network 130-b. For example, one or more of UE 115-b's protocol stacks 305 and 310 may send signaling including an indication of the protocol stacks' dual-booting capability via one or more of PDU sessions 395 and 397 (or in some cases via the corresponding access network). In some cases, the signaling may include additional information, such as information identifying the number of subscriptions or protocol stacks that UE 115-b is configured for, or information related to other capabilities of UE 115-b. In some cases, the information indicating dual-booting and additional information may be provided to core network 130-b as part of the process by which one or more of UE 115-b's protocol stacks 305 and 310 register with core network 130-b. In other words, protocol stacks 305 and 310 of UE 115-e can register with core network 130-b to obtain access to radio services associated with core network 130-b. To register with the network, protocol stacks 305 and 310 can perform a registration process, which may include exchanging signaling (e.g., information) with one or more access networks or core network 130-b in the corresponding access network.

[0107] In response to receiving information indicating dual bootstrapping capability of UE 115-b or one or more of protocol stacks 305 and 310, core network 130-b may send one or more URSP rules to UE 115-b via one or more of PDU sessions 395 and 397. For example, in Figure 3In the example, core network 130-b can transmit URSP rules via both PDU session 395 and PDU session 397. For example, URSP rule 392 can be transmitted to protocol stack 305 of UE 115-b via PDU session 395, and URSP rule 394 can be transmitted to protocol stack 310 of UE 115-b via PDU session 395. URSP rule 392 and URSP rule 394 can be the same set of rules or different sets of rules. In this case, URSP rule 392 can be associated with protocol stack 305, and dual bootstrapping layer 315 can use URSP rule 392 to make routing decisions associated with protocol stack 305. Similarly, in this example, URSP rule 394 can be associated with protocol stack 310, and dual bootstrapping layer 315 can use URSP rule 394 to make routing decisions associated with protocol stack 310.

[0108] URSP rules 392 and 394 can each be a set of URSP rules and can include one or more URSP rules. Each URSP rule can include a service descriptor identifying the type of data service (such as information identifying services from a specific application in application 330) and a mapping to one or more RSDs indicating where or how to route the corresponding type of data service (as indicated by a service identifier) ​​when certain conditions are met. For example, each RSD can include one or more parameters or fields that provide indication of where or how to route the corresponding type of data service and the conditions to be met to trigger such routing. In some cases, RSDs can be configured with new fields, such as a capability validity field, which can indicate the device capabilities to be met for the RSD to be valid for use by the dual bootstrapping layer 315 when routing data services. For example, the capability validity field (also referred to as the "RAT validity field") can be associated with one or more RATs supported by the device for accessing one or more of these access networks or core networks 130-a. For example, the capability validity field can provide an indication of one or more RAT capabilities or combinations of RAT capabilities associated with one or more protocol stacks in the protocol stack of UE 115-b that must be satisfied in order for the associated RSD to be valid when routing data services by the dual bootstrap layer 315.

[0109] For example, URSP rule 392 can be received at protocol stack 305. URSP rule 392 may include a first URSP rule with a first RSD, which may include a capability validity field indicating the combination of NR and LTE. In this case, when one protocol stack (such as protocol stack 305) supports NR and another protocol stack (such as protocol stack 310) supports LTE, the dual bootstrapping layer 315 can determine that the first RSD is valid for routing data services at protocol stack 305. As another example, the second RSD of the first URSP (received at protocol stack 305) may include a capability validity field indicating the combination of LTE and LTE. In this example, when one protocol stack (such as protocol stack 305) supports LTE and another protocol stack (such as protocol stack 310) also supports LTE, the dual bootstrapping layer 315 can determine that the second RSD is valid for routing data services at protocol stack 305. If the RATs of protocol stacks 305 and 310 do not match any combination of the RATs indicated by the capability validity field of the first or second RSD of URSP rule 392, the dual bootstrap layer 315 can determine that neither the first nor the second RSD is valid for routing at the management protocol stack 305. Therefore, the corresponding data service may not be routed using protocol stack 305 and thus may not be sent to core network 130-b (e.g., when other RSDs of the first URSP or other URSP rules of URSP rule 392 are invalid).

[0110] The capability validity field may not be limited to a combination of two RATs and may alternatively include any number of RATs, such as (for example) the number of RATs corresponding to the number of protocol stacks configured for UE 115-b. In some cases, the capability validity field may include fewer RAT indications than the number of protocol stacks configured for UE 115-b. For example, in some cases, the capability validity field of the URSP rule's RSD may indicate a single RAT indication or no RAT indication (e.g., the capability validity field may be empty).

[0111] When the capability validity field of an RSD indicates a single RAT, the dual bootstrapping layer 315 can use the associated RSD to route data services if the RAT associated with the protocol stack to which the URSP applies corresponds to the indicated RAT. For example, if a URSP rule 392 received at protocol stack 305 and associated with that protocol stack includes a first URSP rule (which includes a first RSD with a capability validity field indicating a single RAT, such as LTE), the dual bootstrapping layer 315 can only determine that the first RSD is valid for protocol stack 305 (the protocol stack associated with URSP rule 392) if protocol stack 305 supports LTE. In this case, the dual bootstrapping layer 315 can use the first RSD to manage the routing of data services at protocol stack 305. In this example, if protocol stack 305 does not support LTE, the first RSD may not be used to manage the routing of data services at protocol stack 305.

[0112] When the capability validity field of an RSD is empty (e.g., no RAT is indicated), the dual bootstrapping layer 315 can use the associated RSD to route traffic, regardless of the RAT associated with the protocol stack to which the associated URSP applies. For example, if a URSP rule 394 received at protocol stack 310 and associated with that protocol stack includes a first URSP rule (which includes a first RSD with an empty capability validity field), then the dual bootstrapping layer 315 can determine that the first RSD is valid for protocol stack 310 (the protocol stack associated with URSP rule 394), regardless of the RAT supported by protocol stack 310. In this case, the dual bootstrapping layer 315 can use the first RSD to manage the routing of data traffic at protocol stack 310.

[0113] When the RSD of one or more URSP rules in a URSP rule is identified as valid by the dual bootstrapping layer 315, the dual bootstrapping layer 315 can use the preferred access type field of the RSD to determine how or where to route traffic. When the conditions specified by the RSD are met (e.g., when the RSD is determined to be valid), the preferred access type field of the RSD can provide an indication to the dual bootstrapping layer 315 whether it should perform single bootstrapping (e.g., boots data traffic to a single protocol stack) or dual bootstrapping (e.g., boots data traffic to multiple protocol stacks). For example, when the preferred access type field indicates that single bootstrapping should be performed (e.g., when the preferred access field has the value "3GPP"), the dual bootstrapping layer 315 can boot or route data traffic to the protocol stack associated with the corresponding URSP rule.

[0114] For example, the simplified structures of URSP rule 392 and URSP rule 394 are shown in Tables 1 and 2 below.

[0115] Table 1

[0116]

[0117] Referring to Table 1, URSP rule 392 can be received at protocol stack 305. URSP rule 392 can be used by dual bootstrapping layer 315 for routing decisions at protocol stack 305. URSP rule 392 may include: a first URSP rule (e.g., rule 1), which applies when data traffic associated with App A (e.g., an application in application 330) needs to be routed; and rule 2, which applies when data traffic associated with App B (e.g., an application in application 330) needs to be routed. Therefore, if protocol stack 305 and protocol stack 310 support a combination of NR RAT and LTE RAT, dual bootstrapping layer 315 can determine that RSD1 is valid for routing App A traffic. If both protocol stack 305 and protocol stack 310 support NR RAT, dual bootstrapping layer 315 can determine that RSD2 is valid for routing App A traffic. If both protocol stack 305 and protocol stack 310 support LTE RAT, dual bootstrapping layer 315 can determine that RSD3 is valid for routing App A traffic. In this example, the dual bootstrapping layer 315 can also determine that RSD4 is valid for routing the App A service, regardless of the RATs supported by protocol stacks 305 and 310. Therefore, if the dual bootstrapping layer 315 determines that RSD1 is valid for the App A service, it can determine to perform dual bootstrapping to route the App A service. That is, the dual bootstrapping layer 315 can use both protocol stacks 305 and 310 to route the App A service. If the dual bootstrapping layer 315 determines that RSD2, RSD3, or RSD4 is valid for the App A service, it can use single bootstrapping to route the App A service. That is, in this case, only a single protocol stack (such as protocol stack 305 associated with URSP rule 392) can be used to route the App A service. The dual bootstrapping layer 315 can make a similar determination regarding the validity of RSDs for data services associated with App B.

[0118] In some cases, when more than one RSD is determined to be valid for a particular type of data service and the RSDs indicate different preferred access types, a priority indicator (not shown) associated with the RSD can be used to determine which RSD to use. For example, the dual bootstrap layer 315 can select the RSD with the highest priority to route data services for that type of data service.

[0119] Table 2

[0120]

[0121] Referring to Table 2, URSP rule 394 can be received at protocol stack 310. URSP rule 394 can be used by dual bootstrapping layer 315 for routing decisions at protocol stack 310. URSP rule 394 may include: a first URSP rule (e.g., rule 1), which can be applied when data traffic associated with App B (e.g., an application in application 330) needs to be routed; and rule 2, which can be applied when data traffic associated with App C (e.g., an application in application 330) needs to be routed.

[0122] Therefore, if protocol stacks 305 and 310 support a combination of NR RAT and LTE RAT, then dual bootstrapping layer 315 can determine that RSD1 is valid for routing App B services. If protocol stack 310 supports LTE, then dual bootstrapping layer 315 can determine that RSD5 is valid for routing App B services. Therefore, if dual bootstrapping layer 315 determines that RSD1 is valid for App B services, then dual bootstrapping layer 315 can determine to perform dual bootstrapping to route App B services. That is, dual bootstrapping layer 315 can use both protocol stacks 310 and 305 to route App B services. If dual bootstrapping layer 315 determines that RSD5 is valid for App B services, then dual bootstrapping layer 315 can use single bootstrapping to route App B services. That is, in this case, protocol stack 310 associated with URSP rule 394 can be used to route App B services. Dual bootstrapping layer 315 can make a similar determination regarding the validity of RSDs for data services associated with App C.

[0123] Therefore, when URSP rules 392 and 394 are independently sent to each of protocol stacks 305 and 310, when the dual bootstrapping layer 315 processes the URSP rules at each protocol stack, if the dual bootstrapping layer 315 identifies a valid RSD that includes an instruction to perform single bootstrapping, then the dual bootstrapping layer 315 uses the protocol stack associated with the corresponding URSP rule. That is, a valid single-booted URSP rule on protocol stack 305 can result in routing via protocol stack 305, and a valid single-booted URSP rule on protocol stack 310 can result in routing via protocol stack 310.

[0124] In some cases, when the dual bootstrapping layer 315 determines that dual bootstrapping should be performed, each of the protocol stacks 305 and 310 can be triggered to establish a PDU session with the core network 130-a (e.g., establish a new or updated PDU session, or in some cases, use an existing PDU session). In this case, each of the protocol stacks 305 and 310 can initiate a PDU session (such as PDU session 395 and PDU session 397) separately (e.g., establish a new or updated PDU session, or in some cases, use an existing PDU session). Additionally, each of the protocol stacks 305 and 310 can send a PDU session establishment request to the core network 130-b. The PDU session establishment request may include information identifying the protocol stack and the corresponding PDU session associated with the peer protocol stack. For example, a PDU session establishment request sent by protocol stack 305 to the core network 130-b may include information identifying protocol stack 310 and the corresponding PDU session 397. For example, a PDU session establishment request from protocol stack 305 may include indications of a Subscription Permanent Identifier (SUPI) associated with protocol stack 310 and a PDU session identifier associated with PDU session 397. Similarly, a PDU session establishment request sent by protocol stack 310 to core network 130-b may include information identifying protocol stack 305 and the corresponding PDU session 395. For example, a PDU session establishment request from protocol stack 310 may include indications of a SUPI associated with protocol stack 305 and a PDU session identifier associated with PDU session 395.

[0125] Core network 130-b can receive PDU session establishment requests from protocol stacks 305 and 310, and can determine which PDU session to associate (e.g., bind) to the corresponding protocol stack. For example, core network 130-b can bind PDU session 395 to protocol stack 305, and can bind PDU session 397 to protocol stack 310. Core network 130-b can additionally associate or bind PDU sessions 395 and 397 to coordinate dual booting at UE 115-b.

[0126] Figure 4 An example block diagram 400 of a UE 115-c and a core network 130-c supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure is shown. In some examples, the UE 115-c and the core network 130-c can implement as described in reference respectively. Figure 1 and Figure 2 The described aspects of wireless communication system 100 and wireless communication system 200 may be implemented by these aspects of wireless communication systems. UE 115-c may be as follows (refer to...) Figure 1 , Figure 2and Figure 3 Examples of UE 115, UE 115-a, or UE 115-b are described. Core network 130-c can be as described in the respective examples. Figure 1 , Figure 2 and Figure 3 Examples of core network 130, core network 130-a, or core network 130-b described.

[0127] UE 115-c may include an operating system 425 and a modem 420. The operating system 425 may support one or more applications 430. The operating system 425 may be as described in the reference. Figure 2 and Figure 3 Examples of operating systems 225 or 325 described herein. Modem 420 may interface with operating system 425 via data interface 435 to receive and transmit data services associated with one or more applications 430. Modem 420 may be as described in the reference. Figure 2 and Figure 3 Examples of modems 220 or 320 as described.

[0128] The modem 420 can be configured with multiple subscriptions (such as via multiple SIMs) and corresponding protocol stacks to support one or more wireless services, such as reference SIMs, over one or more access networks. Figure 1 , Figure 2 and Figure 3 As described. For example, UE115-c can be configured with protocol stack 405 and protocol stack 410, which can be as described in the reference. Figure 2 and Figure 3 Examples of protocol stacks 205 and 210 or protocol stacks 305 and 310 are described.

[0129] The modem 420 can be additionally configured to support dual boot and can be configured with a dual boot layer 415, which can be as shown in the reference. Figure 2 and Figure 3 Examples of dual bootstrapping layers 215 or 315 are described. Dual bootstrapping layer 415 can be configured to route or bootstrap data services received from operating system 425 via data interface 435 to one or more of protocol stacks 405 and 410. Data can be routed from one or more of protocol stacks 405 and 410 to core network 130-c via one or more corresponding PDU sessions 495 (e.g., PDU session 495-a and PDU session 495-b) and PDU sessions 497 (e.g., PDU session 497-a and PDU session 497-b).

[0130] In some cases, UE 115-c may send an indication of its dual-booting capability to core network 130-c. For example, one or more of UE 115-c's protocol stacks 405 and 410 may send signaling including an indication of the protocol stacks' dual-booting capability via one or more of PDU sessions 495 and 497 (or in some cases via the corresponding access network). In some cases, the signaling may include additional information, such as information identifying the number of subscriptions or protocol stacks that UE 115-c is configured for, or information related to other capabilities of UE 115-c. In some cases, the information indicating dual-booting and additional information may be provided to core network 130-c as part of the process by which one or more of UE 115-c's protocol stacks 405 and 410 register with core network 130-c. In other words, protocol stacks 405 and 410 of UE 115-e can register with core network 130-c to obtain access to radio services associated with core network 130-c. To register with the network, protocol stacks 405 and 410 can perform a registration process, which may include exchanging signaling (e.g., information) with one or more access networks or core network 130-c in the corresponding access network.

[0131] In response to receiving information indicating dual bootstrapping capability for UE 115-c or one or more of protocol stacks 405 and 410, core network 130-c may send a single set of URSP rules to UE 115-c via either PDU session 495 or PDU session 497. The single set of URSP rules may be a comprehensive set of URSP rules applicable to each protocol stack in the protocol stack of UE 115-c. Core network 130-c may send comprehensive URSP rule 492. Comprehensive URSP rule 492 may be sent to a single protocol stack (rather than sending a separate set of URSP rules to each protocol stack in the protocol stack, as referenced). Figure 3 (As described). For example, in Figure 4 In the example, core network 130-c can send comprehensive URSP rule 492 to protocol stack 405 via PDU session 495. Core network 130-c can transmit comprehensive URSP rule 492 to UE 115-c when the URSP rule applies to each protocol stack in the UE's protocol stack. In this case, dual bootstrapping layer 415 can obtain (e.g., receive) comprehensive URSP rule 492 from protocol stack 405 and can use comprehensive URSP rule 492 to make routing decisions associated with both protocol stack 405 and protocol stack 410.

[0132] The comprehensive URSP rule 492 can be similar to the one regarding Figure 3The URSP rules 392 and 394 are described. For example, each composite URSP rule in composite URSP rule 492 may include a service descriptor identifying the type of data service (such as information identifying services from a specific application in application 430) and a mapping to one or more RSDs that indicate where or how to route the corresponding type of data service (as indicated by the service identifier) ​​when certain conditions are met. Each RSD may include one or more parameters or fields that provide indication of where or how to route the corresponding type of data service and the conditions that must be met to trigger such routing. In some cases, when URSP rules (such as composite URSP rule 492) apply to multiple protocol stacks, RSDs may be configured with additional fields, such as a subscription validity field, which may indicate which protocol stack (e.g., which subscriber) the data service should be routed to in the case of a valid RSD.

[0133] For example, the simplified structure of the comprehensive URSP rule 492, which includes the subscriber validity field, is shown in Table 3 below.

[0134] Table 3

[0135]

[0136] Referring to Table 3, the synthesized URSP rule 492 can be received at protocol stack 405 and can be passed to the dual bootstrapping layer 415 for processing. The synthesized URSP rule 492 can be used by the dual bootstrapping layer 415 for routing decisions at both protocol stack 405 and protocol stack 410. The synthesized URSP rule 492 may include: a first URSP rule, such as rule 1, which can be applied when data traffic associated with App A (e.g., an application in application 430) needs to be routed; rule 2, which can be applied when data traffic associated with App B (e.g., an application in application 430) needs to be routed; and rule 3, which can be applied when data traffic associated with App C (e.g., an application in application 430) needs to be routed.

[0137] Therefore, if protocol stacks 405 and 410 support a combination of NR RAT and LTE RAT, then dual bootstrapping layer 415 can determine that RSD1 is valid for routing App A service. If both protocol stacks 405 and 410 support NR RAT, then dual bootstrapping layer 415 can determine that RSD2 is valid for routing App A service. If both protocol stacks 405 and 410 support LTE RAT, then dual bootstrapping layer 415 can determine that RSD3 is valid for routing App A service. Dual bootstrapping layer 415 can also determine that RSD4 is valid for routing App A service, regardless of the RAT supported by protocol stacks 405 and 410. In the case of RSD5 (which includes a single RAT in its capability validity field), if the protocol stack indicated by the subscription validity field supports LTE, then dual bootstrapping layer 415 can determine that RSD5 is valid for routing App A service.

[0138] Therefore, if dual bootstrapping layer 415 determines that RSD1 is valid for App A service, then dual bootstrapping layer 415 can determine to perform dual bootstrapping to route App A service. That is, dual bootstrapping layer 415 can use both protocol stack 405 and protocol stack 410 to route App A service. If dual bootstrapping layer 415 determines that RSD2, RSD3, RSD4, or RSD5 is valid for App A service, then dual bootstrapping layer 415 can use single bootstrapping (such as those indicated by the 3GPP value of the Preferred Access Type field) to route App A service. That is, only a single protocol stack can be used to route App A service. In this case, the subscription validity field can be used to identify which protocol stack is used to route the data. For example, if RSD2, RSD3, or RSD4 is determined to be valid for App A service, the service can be routed via protocol stack 1, which may correspond to, for example, protocol stack 405. If RSD5 is determined to be valid for App A service, the service can be routed via protocol stack 2, which may correspond to protocol stack 410. The dual bootstrapping layer 415 can make similar determinations regarding the validity of the RSD for data services associated with App B and App C.

[0139] Figure 5 An example block diagram 500 of a UE 115-d and a core network 130-d supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure is shown. In some examples, the UE 115-d and the core network 130-d can implement as described in reference 115-d to the core network 130-d respectively. Figure 1 and Figure 2 The described aspects of wireless communication system 100 and wireless communication system 200 may be implemented by these aspects of wireless communication systems. UE 115-d may be as referred to respectively Figure 1 , Figure 2 , Figure 3 and Figure 4 Examples of UE 115, UE 115-a, UE 115-b, or UE 115-c are described. Core network 130-d can be as described in the following references: Figure 1 , Figure 2 , Figure 3 and Figure 4 Examples of core network 130, core network 130-a, core network 130-b, or core network 130-c described.

[0140] UE 115-d may include an operating system 525 and a modem 520. The operating system 525 may support one or more applications 530. The operating system 525 may be as described in the reference... Figure 2 , Figure 3 and Figure 4 Examples of operating systems 225, 325, or 425 are described. Modem 520 may interface with operating system 525 via data interface 535-1, data interface 535-2, or a combination thereof to receive and transmit data services associated with one or more applications 530. Modem 520 may be as described in the reference. Figure 2 , Figure 3 and Figure 4 Examples of the described modems 220, 320, or 420.

[0141] The modem 520 can be configured with multiple subscriptions (such as via multiple SIMs) and corresponding protocol stacks to support one or more wireless services, such as reference SIMs, over one or more access networks. Figure 1 , Figure 2 , Figure 3 and Figure 4 As described. For example, UE 115-d can be configured with protocol stack 505 and protocol stack 510, which can be as described in the reference. Figure 2 , Figure 3 and Figure 4 Examples of protocol stacks 205 and 210, 305 and 310, or 405 and 410 are described.

[0142] The modem 520 can be additionally configured to support dual boot and can be configured with a dual boot layer 515, which can be as shown in the reference. Figure 2 , Figure 3 and Figure 4Examples of dual bootstrap layers 215, 315, or 415 are described. Dual bootstrap layer 515 can be configured to route or bootstrap data services received from operating system 525 to one or more of protocol stacks 505 and 510 via one or more of data interfaces 535-1 or 535-2. Data can be routed from one or more of protocol stacks 505 and 510 to core network 130-d via one or more corresponding PDU sessions 595 (e.g., PDU session 595-a and PDU session 595-b) and PDU sessions 597 (e.g., PDU session 597-a and PDU session 597-b).

[0143] In some cases, UE 115-d may send an indication of its dual-booting capability to core network 130-d. For example, one or more of protocol stacks 505 and 510 of UE 115-d may send signaling including an indication of the dual-booting capability of one or more of protocol stacks 505 and 510 via one or more of PDU sessions 595 and 495 (or in some cases via the corresponding access network).

[0144] In response to receiving information indicating dual bootstrapping capability of UE 115-d or one or more of protocol stacks 505 and 510, core network 130-d may send this information to UE 115-d via either PDU session 595 or PDU session 495. In some cases, dual bootstrapping layer 515 may optionally notify (e.g., send or transmit) URSP rules 592 and 594 to operating system 525, and operating system 525 may control the routing or bootstrapping of data services according to URSP rules 592 and 594 and using data interfaces 535-1 and 535-2 respectively interfaced with protocol stacks 505 and 510, instead of managing the routing and bootstrapping of data services from operating system 525 according to URSP rules 592 and 594.

[0145] For example, in some cases, the dual boot layer 515 can provide URSP rules 592 and URSP rules 594 to the operating system 525, and the operating system 525 can then use these rules to communicate with the operating system 525. Figures 2 to 4Routing decisions are made in the manner described. Alternatively, the dual bootstrap layer 515 may not provide URSP rules 592 and 594 to the operating system 525, but may instead provide the operating system 525 with routing decisions determined by the dual bootstrap layer 515. Based on the routing decisions (determined by the operating system 525 or the dual bootstrap layer 515), the operating system 525 may use one or more of data interfaces 535-1 and 535-2 to route data services to the appropriate protocol stack. For example, data interface 535-1 may interface with protocol stack 505 and may be used to route data services to protocol stack 505. Data interface 535-2 may interface with protocol stack 510 and may be used to route data services to protocol stack 510. In some cases, data interfaces 535-1 and 535-2 may be used concurrently to route data services, such as when URSP rule 592 or URSP rule 594 indicates that dual bootstrap should be performed.

[0146] Figure 6 An example of a process flow 600 supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure is shown. Process flow 600 can be implemented as described in reference respectively. Figure 1 and Figure 2 The wireless communication system 100 and wireless communication system 200 are described in various aspects. Process flow 600 may include UE 115-e and access networks 145-c and 145-d, which may be examples of the corresponding devices described herein. UE 115-e may include protocol stack 1 605, protocol stack 2 610, and dual bootstrapping layer 615, as referenced herein. Figures 1 to 5 As described herein, process flow 600 may additionally include a core network 130-e, which may be the example core network 130 as described herein.

[0147] In the following description of process flow 600, operations between UE 115-e, access network 145-c, access network 145-d, and core network 130-e may be sent in a different order than the example order shown, or these operations may be performed in a different order or at different times. Some operations may also be omitted from process flow 600, and other operations may be added to process flow 600.

[0148] At locations 602 and 604, the protocol stack 1605 of UE 115-e can perform one or more procedures to connect to and register with one or more of the access network 145-c and the core network 130-e. The connection and registration procedures may include exchanging signaling (e.g., information) with one or more of the access network 145-c and the core network 130-e. In some cases, the signaling may include an indication of dual-booting capability for UE 115-e or its protocol stack 1605.

[0149] At locations 606 and 608, the protocol stack 2 610 of UE 115-e can perform one or more procedures to connect to and register with one or more of access networks 145-d and core networks 130-e. The connection and registration procedures may include exchanging signaling (e.g., information) with one or more of access networks 145-d and core networks 130-e. In some cases, the signaling may include an indication of dual-booting capability for UE 115-e or its protocol stack 2610.

[0150] At 610, based on received instructions regarding the capabilities of UE 115-e or one or more of protocol stacks 605 and 610, core network 130-e can update one or more URSP rules associated with UE 115-e or one or more of protocol stacks 605 and 610. The updated URSP rules can be configured to support dual-booting capabilities of UE 115-e or one or more of UE 115-e's protocol stacks 605 and 610.

[0151] At points 612 and 614, core network 130-e can send or transmit updated URSP rules to UE 115-e, such as via one or more of protocol stacks 605 and 610, respectively. In some cases, core network 130-e can transmit URSP rules to each of one or more protocol stacks 605 and 610. In other cases, core network 130-e can transmit a single aggregated set of URSP rules to one of protocol stacks 605 and 610.

[0152] At 616 and 618, in some cases, the dual bootstrap layer 615 of UE 115-e (which can be responsible for managing the routing of data services according to rules) can obtain (e.g., receive) URSP rules from one or more of protocol stacks 605 and 610.

[0153] At 620, the dual bootstrap layer 615 can make routing decisions based on URSP rules and service information associated with data services.

[0154] At points 622 and 624, one or more of protocol stacks 605 and 610 may transmit a PDU session establishment request to core network 130-e. In some cases, the PDU session establishment request may be transmitted in response to dual bootstrapping 615 determining (at 620) to perform dual bootstrapping to route data traffic to one or more of protocol stacks 605 and 610. The PDU session establishment request may include information identifying the protocol stack and the corresponding PDU session associated with the peer protocol stack. For example, each PDU session establishment request may include indications of the SUPI associated with the peer protocol stack and the PDU session identifier associated with the PDU session of the peer protocol stack. In some cases, when a first PDU session establishment request is received from protocol stack 1 605, core network 130-e may be unaware of an upcoming second PDU session from protocol stack 2 610. In this scenario, core network 130-e can ignore the dual-booting information provided by the first PDU session establishment request, and at a later time, when the second PDU session establishment request is received by core network 130-e, core network 130-e can proceed to step 626.

[0155] At point 626, when core network 130-e receives a PDU session establishment request, it can associate or bind the PDU session associated with each PDU session establishment request in the PDU session establishment request, so that core network 130-e can know that the corresponding session is associated with the same UE 115-e.

[0156] At 628 and 630, core network 130-e can transmit an acknowledgment of acceptance of one or more PDU session establishment requests to one or more of protocol stack 1 605 and protocol stack 2 610.

[0157] Figure 7 A block diagram 700 illustrates a device 705 supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure. Device 705 may be an example of various aspects of UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, communication manager 720), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0158] Receiver 710 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 associated with dual-boot operation for wireless communication). The information may be delivered to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.

[0159] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with dual-boot operation for wireless communication). In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0160] The communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be examples of parts for performing various aspects of dual-boot operation for wireless communication as described herein. For example, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0161] In some examples, the communication manager 720, receiver 710, transmitter 715, 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).

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

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

[0164] 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 transmitting an indication of the UE's ability to route data services associated with the UE via a first protocol stack in a set of multiple protocol stacks of the UE, wherein the first protocol stack corresponds to a first subscription in a set of multiple subscriptions of the UE, and the second protocol stack corresponds to a second subscription in a set of multiple subscriptions. The communication manager 720 may be capable of, configured to, or operable to support components for receiving a first set of URSP rules for routing data services associated with the UE based on the UE's capabilities. The communication manager 720 may be capable of, configured to, or operable to support components for routing data services associated with the UE via one or both of the first or second protocol stack, at least partially based on the first set of URSP rules and the UE's capabilities, via a higher layer of the UE.

[0165] By including or configuring a communication manager 720 according to an example as described herein, device 705 (e.g., at least one processor that controls or otherwise couples to receiver 710, transmitter 715, communication manager 720, or a combination thereof) can support techniques for reducing processing and utilizing communication resources more efficiently.

[0166] Figure 8A block diagram 800 of a device 805 supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of device 705 or UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805 or one or more components of device 805 (e.g., receiver 810, transmitter 815, communication manager 820) 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).

[0167] Receiver 810 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 associated with dual-boot operation for wireless communication). The information may be delivered to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

[0168] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with dual-boot operation for wireless communication). In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0169] Device 805 or its various components may be examples of parts for performing various aspects of dual-booting operations for wireless communication as described herein. For example, communication manager 820 may include capability transmitter 825, URSP manager 830, routing manager 835, or any combination thereof. Communication manager 820 may be examples of aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to use receiver 810, transmitter 815, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or be integrated in combination with receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0170] Communication manager 820 may support wireless communication according to examples disclosed herein. Capability transmitter 825 is capable of, configured to, or operable to support components for transmitting an indication of the UE's capability to route data services associated with the UE via a first protocol stack in a set of multiple protocol stacks of the UE, wherein the first protocol stack corresponds to a first subscription in a set of multiple subscriptions of the UE, and the second protocol stack corresponds to a second subscription in a set of multiple subscriptions. URSP manager 830 is capable of, configured to, or operable to support components for receiving a first set of URSP rules for routing data services associated with the UE based on the UE's capabilities. Routing manager 835 is capable of, configured to, or operable to support components for routing data services associated with the UE via one or both of the first protocol stack or the second protocol stack, via a higher layer of the UE, based on the first set of URSP rules and the UE's capabilities.

[0171] Figure 9 A block diagram 900 is shown of a communication manager 920 supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure. The communication manager 920 may be an example of aspects of the communication manager 720, communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of parts for performing various aspects of the dual-boot operation for wireless communication as described herein. For example, the communication manager 920 may include a capability transmitter 925, a URSP manager 930, a routing manager 935, a PDU manager 940, a session request manager 945, 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).

[0172] Communication Manager 920 may support wireless communication according to examples disclosed herein. Capability Transmitter 925 is capable of, configured to, or operable to support components for transmitting an indication of the UE's capability to route data services associated with the UE via a first protocol stack in a set of multiple protocol stacks of the UE, wherein the first protocol stack corresponds to a first subscription in a set of multiple subscriptions of the UE, and the second protocol stack corresponds to a second subscription in a set of multiple subscriptions. URSP Manager 930 is capable of, configured to, or operable to support components for receiving a first set of URSP rules for routing data services associated with the UE based on the UE's capabilities. Routing Manager 935 is capable of, configured to, or operable to support components for routing data services associated with the UE via one or both of the first protocol stack or the second protocol stack, via a higher layer of the UE, based on the first set of URSP rules and the UE's capabilities.

[0173] In some examples, a first set of URSP rules is received via a first protocol stack, and the URSP manager 930 is capable of, configured to, or operable to support components for receiving a second set of URSP rules for bootstrapping data services via a second protocol stack and based on the UE's capabilities, wherein the first set of URSP rules is associated with the first protocol stack, and the second set of URSP rules is associated with the second protocol stack.

[0174] In some examples, the first set of URSP rules is received via a higher layer of the UE and associated with both the first and second protocol stacks.

[0175] In some examples, to support each RSD in the set of RSDs, the URSP manager 930 is capable of, configured to, or operable to support a component for a preferred access type, which indicates whether single boot or dual boot is performed. In some examples, to support each RSD in the set of RSDs, the URSP manager 930 is capable of, configured to, or operable to support a component for a validity field, which indicates one or more RAT capabilities corresponding to one or more of a first protocol stack, a second protocol stack, a first subscription, or a second subscription, or any combination thereof.

[0176] In some examples, in order to support routing data services via one or both of a first protocol stack or a second protocol stack, the route manager 935 is capable of, configured or operable to support components for routing data services based on a first URSP rule, which is based on service information associated with the data service and one or more service descriptors associated with one or more URSP rules in a first set of URSP rules.

[0177] In some examples, to support routing data services based on a first URSP rule, the route manager 935 is capable of, configured to, or operable to support components for routing data services via both a first protocol stack and a second protocol stack based on a preferred access type associated with a first RSD associated with the first URSP rule for routing data services, the first RSD being based on the capabilities of one or both of the first and second protocol stacks and one or more validity indicators associated with one or more RSDs associated with the first URSP rule.

[0178] In some examples, to support routing data services based on a first URSP rule, the route manager 935 is capable of, configured to, or operable to support components for routing data services via one of a first protocol stack or a second protocol stack based on a preferred access type associated with a first RSD associated with the first URSP rule for routing data services, the first RSD being based on capabilities associated with one or both of the first and second protocol stacks and one or more validity indicators associated with one or more RSDs associated with the first URSP rule.

[0179] In some examples, in order to support routing data services based on a first URSP rule, the route manager 935 is capable of, configured to, or operable to support a component for routing data services via one of a first protocol stack or a second protocol stack based on a first RSD associated with the first URSP rule for routing data services, wherein the first RSD is associated with the first URSP rule and the validity indicator associated with the first RSD is empty.

[0180] In some examples, each RSD in the set of RSDs includes a subscription validity indicator that identifies the protocol stack used to route data traffic.

[0181] In some examples, to support routing data services based on a first URSP rule, the route manager 935 is capable of, configured to, or operable to support components for routing data services via a protocol stack identified by a subscription validity indicator associated with a first RSD, guided by a preferred access type indication form associated with the first RSD, which is associated with a first URSP rule for routing data services and is based on the capabilities of one or both of a first protocol stack and a second protocol stack, and one or more validity indicators associated with one or more RSDs associated with the first URSP rule.

[0182] In some examples, to support routing data services based on a first URSP rule, the route manager 935 is capable of, configured to, or operable to support components for routing data services via one or both of a first protocol stack or a second protocol stack based on an empty subscription validity indicator associated with a first RSD associated with the first URSP rule for routing data services, the first RSD being based on the capabilities of one or both of the first and second protocol stacks and one or more validity indicators associated with one or more RSDs associated with the first URSP rule.

[0183] In some examples, in order to support routing data services via one or both of the first protocol stack or the second protocol stack, the route manager 935 can be, configured, or operated to support components for routing data services via either the first protocol stack or the second protocol stack.

[0184] In some examples, the PDU manager 940 is capable of, configured to, or operable to support components for initiating a first PDU session at a first protocol stack. In some examples, the PDU manager 940 is capable of, configured to, or operable to support components for initiating a second PDU session at a second protocol stack. In some examples, the session request manager 945 is capable of, configured to, or operable to support components for sending a first request to the core network and via the first protocol stack to establish a first PDU session, wherein the first request indicates an identifier associated with the second protocol stack and an identifier associated with the second PDU session. In some examples, the session request manager 945 is capable of, configured to, or operable to support components for sending a second request to the core network and via the second protocol stack to establish a second PDU session, wherein the second request indicates an identifier associated with the first protocol stack and an identifier associated with the first PDU session.

[0185] Figure 10A diagram of a system 1000 including a device 1005 supporting dual-boot operation for wireless communication, according to one or more aspects of this disclosure, is shown. Device 1005 may be an example of device 705, device 805, or UE 115 as described herein, or may include components thereof. Device 1005 may communicate with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof) (e.g., wirelessly). Device 1005 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1020, an input / output (I / O) controller (e.g., I / O controller 1010), a transceiver 1015, one or more antennas 1025, at least one memory 1030, code 1035, and at least one processor 1040. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1045).

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

[0187] In some cases, device 1005 may include a single antenna 1025. However, in other cases, device 1005 may have more than one antenna 1025, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1015 may communicate bidirectionally via one or more antennas 1025 as described herein, or via a wired or wireless link. For example, transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1015 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1025 for transmission; and demodulating packets received from one or more antennas 1025. Transceiver 1015, or transceiver 1015 and one or more antennas 1025, may be an example of transmitter 715, transmitter 815, receiver 710, receiver 810, or any combination thereof or components thereof as described herein.

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

[0189] At least one processor 1040 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 1040. At least one processor 1040 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1030) to cause device 1005 to perform various functions (e.g., functions or tasks supporting dual-boot operation for wireless communication). For example, device 1005 or components of device 1005 may include at least one processor 1040 and at least one memory 1030 coupled to or coupled to at least one processor 1040, the at least one processor 1040 and at least one memory 1030 being configured to perform the various functions described herein. In some examples, at least one processor 1040 may include multiple processors, and at least one memory 1030 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1040 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1040) and memory circuitry (which may include at least one memory 1030)) 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 1040 or a processing system including at least one processor 1040 may be configured, capable of being configured, or operable to cause device 1005 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “configurable to,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1030 or otherwise.

[0190] The communication manager 1020 may support wireless communication according to examples disclosed herein. For example, the communication manager 1020 may be capable of, configured to, or operable to support components for transmitting an indication of the UE's ability to route data services associated with the UE via a first protocol stack in a set of multiple protocol stacks of the UE, or a second protocol stack in a set of multiple protocol stacks, wherein the first protocol stack corresponds to a first subscription in a set of multiple subscriptions of the UE, and the second protocol stack corresponds to a second subscription in a set of multiple subscriptions. The communication manager 1020 may be capable of, configured to, or operable to support components for receiving a first set of URSP rules for routing data services associated with the UE based on the UE's capabilities. The communication manager 1020 may be capable of, configured to, or operable to support components for routing data services associated with the UE, via one or both of the first or second protocol stack, through a higher layer of the UE, at least in part based on the first set of URSP rules and the UE's capabilities.

[0191] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 can support techniques for reducing latency, improving user experience related to reduced processing, utilizing communication resources more efficiently, improving coordination between devices, and improving the utilization of processing power.

[0192] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 1015, one or more antennas 1025, or any combination thereof, or otherwise cooperating with them. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported by or executed by at least one processor 1040, at least one memory 1030, code 1035, or any combination thereof. For example, code 1035 may include instructions that may be executed by at least one processor 1040 to cause the device 1005 to perform various aspects of the dual-boot operation for wireless communication as described herein, or at least one processor 1040 and at least one memory 1030 may be otherwise configured to perform or support such operations individually or jointly.

[0193] Figure 11A block diagram 1100 of a device 1105 supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure is shown. Device 1105 may be an example of aspects of network entity 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105, or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, communication manager 1120), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0194] Receiver 1110 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, PDUs, serving data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

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

[0196] The communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be examples of components used to perform various aspects of dual-boot operation for wireless communication as described herein. For example, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0197] In some examples, the communication manager 1120, receiver 1110, transmitter 1115, 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 a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, 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).

[0198] Additionally or alternatively, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., referred to as processor executable code) (e.g., implemented as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 1120, receiver 1110, transmitter 1115, 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 as or otherwise individually or collectively to support the performance of the functions described in this disclosure).

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

[0200] Communication manager 1120 may support wireless communication according to examples disclosed herein. For example, communication manager 1120 may be capable of, configured to, or operable to support components for receiving from a UE an indication of the UE's ability to bootstrap data services associated with the UE via a set of multiple protocol stacks of the UE, wherein each protocol stack of the UE corresponds to a corresponding subscription in a set of multiple subscriptions of the UE. Communication manager 1120 may be capable of, configured to, or operable to support components for updating a first set of URSP rules, at least in part, based on the UE's capabilities, to support dual-bootstrap functionality at the UE. Communication manager 1120 may be capable of, configured to, or operable to support components for sending the first set of URSP rules to the UE.

[0201] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 (e.g., at least one processor that controls or is otherwise coupled to receiver 1110, transmitter 1115, communication manager 1120, or a combination thereof) can support techniques for reducing processing and utilizing communication resources more efficiently.

[0202] Figure 12 A block diagram 1200 of a device 1205 supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure is shown. Device 1205 may be an example of aspects of device 1105 or network entity 105 as described herein. Device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. Device 1205 or one or more components of device 1205 (e.g., receiver 1210, transmitter 1215, communication manager 1220) 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).

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

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

[0205] Device 1205 or its various components may be examples of parts for performing various aspects of dual-booting operations for wireless communication as described herein. For example, communication manager 1220 may include capability receiver 1225, URSP rule manager 1230, URSP rule transmitter 1235, or any combination thereof. Communication manager 1220 may be examples of aspects of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to use receiver 1210, transmitter 1215, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated in combination with receiver 1210, transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0206] Communication manager 1220 may support wireless communication according to examples disclosed herein. Capability receiver 1225 is capable of, configured to, or operable to support components for receiving from the UE an indication of the UE's capability to bootstrap data services associated with the UE via a set of multiple protocol stacks of the UE, wherein each protocol stack of the UE corresponds to a corresponding subscription in a set of multiple subscriptions of the UE. URSP rule manager 1230 is capable of, configured to, or operable to support components for updating a first set of URSP rules based on the UE's capabilities to support dual-bootstrap functionality at the UE. URSP rule transmitter 1235 is capable of, configured to, or operable to support components for sending the first set of URSP rules to the UE.

[0207] Figure 13A block diagram 1300 is shown of a communication manager 1320 supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure. The communication manager 1320 may be an example of aspects of the communication manager 1120, communication manager 1220, or both as described herein. The communication manager 1320 or its various components may be examples of parts for performing various aspects of the dual-boot operation for wireless communication as described herein. For example, the communication manager 1320 may include a capability receiver 1325, a URSP rule manager 1330, a URSP rule transmitter 1335, a PDU request receiver 1340, a PDU session component 1345, 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). Communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components or virtualization components associated with network entity 105, between devices, components or virtualization components associated with network entity 105), or any combination thereof.

[0208] Communication manager 1320 may support wireless communication according to examples disclosed herein. Capability receiver 1325 is capable of, configured to, or operable to support components for receiving from the UE an indication of the UE's capability to bootstrap data services associated with the UE via a set of multiple protocol stacks of the UE, wherein each protocol stack of the UE corresponds to a corresponding subscription in a set of multiple subscriptions of the UE. URSP rule manager 1330 is capable of, configured to, or operable to support components for updating a first set of URSP rules based on the UE's capabilities to support dual-bootstrap functionality at the UE. URSP rule transmitter 1335 is capable of, configured to, or operable to support components for sending the first set of URSP rules to the UE.

[0209] In some examples, the first set of URSP rules is associated with a first protocol stack in a set of multiple protocol stacks of the UE, and the URSP rule transmitter 1335 is capable of, configured to, or operable to support components for transmitting a second set of URSP rules based on the UE's capabilities to support dual-boot functionality at the UE, wherein the second set of URSP rules is associated with a second protocol stack in a set of multiple protocol stacks of the UE.

[0210] In some examples, the first set of URSP rules is associated with a set of multiple protocol stacks of the UE.

[0211] In some examples, to support each RSD in the set of RSDs, the URSP rule manager 1330 is capable of, configured to, or operable to support a component for a preferred access type, which indicates whether to perform a single boot or a dual boot. In some examples, to support each RSD in the set of RSDs, the URSP rule manager 1330 is capable of, configured to, or operable to support a component for a validity field, which indicates one or more RAT capabilities corresponding to one or more of the following: a first protocol stack in a set of multiple protocol stacks, a second protocol stack in a set of multiple protocol stacks, a first subscription in a set of multiple subscriptions, or a second subscription in a set of multiple subscriptions, or any combination thereof.

[0212] In some examples, each RSD in the set of RSDs includes a subscription validity indicator that identifies which protocol stack in a set of multiple protocol stacks of the UE routes the service.

[0213] In some examples, the PDU request receiver 1340 is capable of, configured to, or operable to support components for receiving a first request from the UE to establish a first PDU session associated with a first protocol stack in a set of multiple protocol stacks associated with the UE, wherein the first request includes an identifier associated with a second protocol stack in the set of multiple protocol stacks associated with the UE and an identifier associated with a second PDU session associated with the second protocol stack.

[0214] In some examples, the PDU request receiver 1340 is capable of, configured to, or operable to support components for receiving a second request from the UE to establish a second PDU session, wherein the second request includes indications of an identifier associated with the first protocol stack and an identifier associated with the first PDU session.

[0215] In some examples, the PDU session component 1345 is capable of, configured to, or operable to support components for associating a first PDU session and a second PDU session with the UE based on the receipt of a first request and a second request.

[0216] Figure 14A diagram of a system 1400 including a device 1405 supporting dual-boot operation for wireless communication, according to one or more aspects of this disclosure, is shown. Device 1405 may be an example of device 1105, device 1205, or network entity 105 as described herein, or may include components thereof. Device 1405 may communicate with other network devices or network equipment, such as network entity 105, UE 115, or any combination thereof. Communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1405 may include components supporting output and acquisition of communication, such as a communication manager 1420, a transceiver 1410, one or more antennas 1415, at least one memory 1425, code 1430, and at least one processor 1435. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1440).

[0217] Transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1410 may include a wired transceiver and be able to communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1410 may include a wireless transceiver and be able to communicate bidirectionally with another wireless transceiver. In some examples, device 1405 may include one or more antennas 1415 that may be able to transmit or receive wireless transmissions (e.g., concurrently). Transceiver 1410 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1415, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1415, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1415 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1415 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1410 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1410, or transceiver 1410 and one or more antennas 1415, or transceiver 1410 and one or more antennas 1415 and one or more processors or one or more memory components (e.g., at least one processor 1435, at least one memory 1425, or both) may be included in a chip or chip assembly mounted in device 1405. In some examples, transceiver 1410 may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0218] At least one memory 1425 may include RAM, ROM, or any combination thereof. At least one memory 1425 may store computer-readable, computer-executable code 1430 including instructions that, when executed by one or more processors of at least one processor 1435, cause device 1405 to perform the various functions described herein. Code 1430 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1430 may not be directly executable by one of the at least one processor 1435, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1425 may also include a BIOS, which controls basic hardware or software operations, such as interaction with peripheral components or devices. In some examples, at least one processor 1435 may include multiple processors, and at least one memory 1425 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 (e.g., as part of a processing system).

[0219] At least one processor 1435 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1435. At least one processor 1435 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1425) to cause device 1405 to perform various functions (e.g., functions or tasks supporting dual-boot operation for wireless communication). For example, device 1405 or components of device 1405 may include at least one processor 1435 and at least one memory 1425 coupled to one or more processors in at least one processor 1435, wherein the at least one processor 1435 and the at least one memory 1425 are configured to perform the various functions described herein. At least one processor 1435 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functions (e.g., by executing code 1430) to perform the functions of device 1405. At least one processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1405 (such as within one or more memories of at least one memory 1425). In some examples, at least one processor 1435 may include multiple processors, and at least one memory 1425 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 1435 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 1435) and memory circuitry (which may include at least one memory 1425)) or components that receive or acquire input and process the input to produce, generate, or acquire 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 1435 or a processing system including at least one processor 1435 may be configured, configured to, or operable to cause the device 1405 to perform one or more of the functions described herein.Furthermore, as described herein, “configurable to,” “configurable to,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1425 or otherwise.

[0220] In some examples, bus 1440 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1440 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1405, or communication performed between different components of device 1405 that are co-addressable or may be located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, at least one memory 1425, code 1430 and at least one processor 1435 may be located in one component of different components or partitioned between different components).

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

[0222] Communication manager 1420 may support wireless communication according to examples disclosed herein. For example, communication manager 1420 may be capable of, configured to, or operable to support components for receiving from a UE an indication of the UE's ability to bootstrap data services associated with the UE via a set of multiple protocol stacks of the UE, wherein each protocol stack of the UE corresponds to a corresponding subscription in a set of multiple subscriptions of the UE. Communication manager 1420 may be capable of, configured to, or operable to support components for updating a first set of URSP rules, at least in part, based on the UE's capabilities, to support dual-bootstrap functionality at the UE. Communication manager 1420 may be capable of, configured to, or operable to support components for sending the first set of URSP rules to the UE.

[0223] By including or configuring a communication manager 1420 according to an example as described herein, device 1405 can support techniques for improving and reducing the user experience associated with processing, utilizing communication resources more efficiently, improving coordination between devices, and improving the utilization of processing power.

[0224] In some examples, the communication manager 1420 may be configured to use or otherwise cooperate with transceiver 1410, one or more antennas 1415 (e.g., where applicable) or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by transceiver 1410, one or more processors in at least one processor 1435, one or more memories in at least one memory 1425, code 1430, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1435, at least one memory 1425, code 1430, or any combination thereof). For example, code 1430 may include instructions that can be executed by one or more of at least one processor 1435 to cause device 1405 to perform various aspects of dual-boot operation for wireless communication as described herein, or at least one processor 1435 and at least one memory 1425 may be otherwise configured to perform or support such operation individually or jointly.

[0225] Figure 15 A flowchart illustrating a method 1500 for supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure is shown. The operation of method 1500 can be implemented by a UE or its components as described herein. For example, the operation of method 1500 can be implemented by, as referenced... Figures 1 to 10 The UE 115 described herein performs the functions. In some examples, the UE can 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.

[0226] At 1505, the method may include: transmitting an indication of the UE's ability to initiate data services associated with the UE via a first protocol stack in a set of multiple protocol stacks of the UE, wherein the first protocol stack corresponds to a first subscription in a set of multiple subscriptions of the UE, and the second protocol stack corresponds to a second subscription in the set of multiple subscriptions. The operation of 1505 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to [reference needed]. Figure 9 The described capability transmitter 925 is used to perform this.

[0227] At 1510, the method may include: receiving a first set of URSP rules for guiding data services associated with the UE, based on the UE's capabilities. The operation of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be derived from references... Figure 9 The URSP Manager 930 described is used for execution.

[0228] At point 1515, the method may include: routing data services associated with the UE via a first set of URSP rules and the UE's capabilities, via a higher layer of the UE, via one or both of a first protocol stack or a second protocol stack. The operation of point 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of point 1515 may be derived from references... Figure 9 The described route manager 935 is used to execute this.

[0229] Figure 16 A flowchart illustrating a method 1600 for supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure is shown. Operation of method 1600 may be implemented by a UE or its components as described herein. For example, operation of method 1600 may be performed by, as described in reference... Figures 1 to 10 The UE 115 described herein performs the functions. In some examples, the UE can 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.

[0230] At 1605, the method may include: transmitting an indication of the UE's ability to initiate data services associated with the UE via a first protocol stack in a set of multiple protocol stacks of the UE, wherein the first protocol stack corresponds to a first subscription in a set of multiple subscriptions of the UE, and the second protocol stack corresponds to a second subscription in the set of multiple subscriptions. The operation of 1605 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to [reference needed]. Figure 9 The described capability transmitter 925 is used to perform this.

[0231] At 1610, the method may include: receiving a first set of URSP rules for guiding data services associated with the UE, based on the UE's capabilities. The operation of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be derived from references... Figure 9 The URSP Manager 930 described is used for execution.

[0232] At 1615, the method may include: receiving a second URSP rule set for guiding data services via a second protocol stack and based on the capabilities of the UE, wherein a first URSP rule set is associated with a first protocol stack, and a second URSP rule set is associated with a second protocol stack. The operation of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1615 may be provided by reference to [reference needed]. Figure 9 The URSP Manager 930 described is used for execution.

[0233] At 1620, the method may include: routing data services associated with the UE via a first set of URSP rules and the UE's capabilities, via a higher layer of the UE, via one or both of a first protocol stack or a second protocol stack. The operation of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1620 may be derived from references... Figure 9 The described route manager 935 is used to execute this.

[0234] Figure 17 A flowchart illustrating a method 1700 for supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure is shown. Operation of method 1700 can be implemented by a UE or its components as described herein. For example, operation of method 1700 can be performed by, as described in reference... Figures 1 to 10 The UE 115 described herein performs the functions. In some examples, the UE can 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.

[0235] At 1705, the method may include: transmitting an indication of the UE's ability to initiate data services associated with the UE via a first protocol stack in a set of multiple protocol stacks of the UE, wherein the first protocol stack corresponds to a first subscription in a set of multiple subscriptions of the UE, and the second protocol stack corresponds to a second subscription in the set of multiple subscriptions. The operation of 1705 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1705 may be provided by reference to [reference needed]. Figure 9 The described capability transmitter 925 is used to perform this.

[0236] At 1710, the method may include: receiving a first set of URSP rules for guiding data services associated with the UE, based on the UE's capabilities. The operation of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1710 may be derived from references... Figure 9 The URSP Manager 930 described is used for execution.

[0237] At 1715, the method may include: routing data services associated with the UE via a first set of URSP rules and the UE's capabilities, via a higher layer of the UE, via one or both of a first protocol stack or a second protocol stack. The operation of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1715 may be derived from references... Figure 9 The described route manager 935 is used to execute this.

[0238] At 1720, the method may include routing data traffic via either a first protocol stack or a second protocol stack. The operation of 1720 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1720 may be derived from references... Figure 9 The described route manager 935 is used to execute this.

[0239] Figure 18 A flowchart illustrating a method 1800 for supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure is shown. The operation of method 1800 may be implemented by a network entity or its components as described herein. For example, the operation of method 1800 may be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0240] At 1805, the method may include: receiving from the UE an indication of the UE's ability to orchestrate data services associated with the UE via a set of multiple protocol stacks of the UE, wherein each protocol stack of the UE corresponds to a corresponding subscription in a set of multiple subscriptions of the UE. The operation of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1805 may be provided by reference to [reference needed]. Figure 13 The described capability is performed by receiver 1325.

[0241] At 1810, the method may include: updating a first set of URSP rules based on the UE's capabilities to support dual-booting functionality at the UE. The operation of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1810 may be derived from references... Figure 13 The URSP rule manager 1330 described is executed.

[0242] At point 1815, the method may include sending a first set of URSP rules to the UE. The operation at 1815 may be performed according to examples disclosed herein. In some examples, aspects of the operation at 1815 may be derived from references... Figure 13The described URSP rule sender 1335 is executed.

[0243] Figure 19 A flowchart illustrating a method 1900 for supporting dual-boot operation for wireless communication according to one or more aspects of this disclosure is shown. The operation of method 1900 may be implemented by a network entity or its components as described herein. For example, the operation of method 1900 may be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0244] At 1905, the method may include: receiving from the UE an indication of the UE's ability to orchestrate data services associated with the UE via a set of multiple protocol stacks of the UE, wherein each protocol stack of the UE corresponds to a corresponding subscription in a set of multiple subscriptions of the UE. The operation of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1905 may be provided by reference to [reference]. Figure 13 The described capability is performed by receiver 1325.

[0245] At point 1910, the method may include: updating a first set of URSP rules based on the UE's capabilities to support dual-booting functionality at the UE. The operation of point 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of point 1910 may be derived from references... Figure 13 The URSP rule manager 1330 described is executed.

[0246] At point 1915, the method may include sending a first set of URSP rules to the UE. The operation at point 1915 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at point 1915 may be provided by reference to [reference needed]. Figure 13 The described URSP rule sender 1335 is executed.

[0247] At 1920, the method may include: sending a second set of URSP rules based on the UE's capabilities to support dual-booting functionality at the UE, wherein the second set of URSP rules is associated with a second protocol stack in a set of multiple protocol stacks of the UE. The operation at 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1920 may be provided by reference to [reference needed]. Figure 13 The described URSP rule sender 1335 is executed.

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

[0249] Aspect 1: A method for wireless communication by a UE, the method comprising: transmitting, via a first protocol stack of a plurality of protocol stacks of the UE, an indication of the UE's ability to route a data service associated with the UE via the first protocol stack or a second protocol stack of the plurality of protocol stacks, wherein the first protocol stack corresponds to a first subscription of a plurality of subscriptions of the UE, and the second protocol stack corresponds to a second subscription of the plurality of subscriptions; receiving, at least in part based on the UE's capability, a first set of UE routing policy (URSP) rules for routing the data service associated with the UE; and routing, at least in part based on the first set of URSP rules and the UE's capability, the data service associated with the UE via a higher layer of the UE, via one or both of the first protocol stack or the second protocol stack.

[0250] Aspect 2: According to the method of aspect 1, wherein the first set of URSP rules is received via the first protocol stack, the method further comprising: receiving a second set of URSP rules for guiding the data service via the second protocol stack and at least in part based on the capabilities of the UE, wherein the first set of URSP rules is associated with the first protocol stack, and the second set of URSP rules is associated with the second protocol stack.

[0251] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the first set of URSP rules is received via the higher layer of the UE and associated with both the first protocol stack and the second protocol stack.

[0252] Aspect 4: The method according to any one of Aspects 1 to 3, wherein each rule in the first set of URSP rules includes a set of Routing Descriptors (RSDs) and a service descriptor, and wherein each RSD in the set of RSDs includes: a preferred access type, the preferred access type indicating whether single bootstrapping or dual bootstrapping is performed; and a validity field, the validity field indicating one or more RAT capabilities corresponding to one or more of the first protocol stack, the second protocol stack, the first subscription, or the second subscription or any combination thereof.

[0253] Aspect 5: According to the method of aspect 4, routing the data service via one or both of the first protocol stack or the second protocol stack includes: routing the data service at least in part based on a first URSP rule, the first URSP rule being at least in part based on service information associated with the data service and one or more service descriptors associated with one or more URSP rules in the first set of URSP rules.

[0254] Aspect 6: According to the method of aspect 5, wherein routing the data service based at least in part on the first URSP rule comprises: routing the data service via both the first protocol stack and the second protocol stack based at least in part on the preferred access type associated with a first RSD of the first URSP rule for routing the data service, wherein the first RSD is based at least in part on the capability of one or both of the first protocol stack and the second protocol stack and one or more validity indicators associated with one or more RSDs of the first URSP rule.

[0255] Aspect 7: The method according to any one of Aspects 5 to 6, wherein routing the data service based at least in part on the first URSP rule comprises: routing the data service via one of the first protocol stack or the second protocol stack based at least in part on the preferred access type associated with a first RSD of the first URSP rule for routing the data service, wherein the first RSD is based at least in part on a capability associated with one or both of the first protocol stack and the second protocol stack and one or more validity indicators associated with one or more RSDs of the first URSP rule.

[0256] Aspect 8: The method according to any one of Aspects 5 to 7, wherein routing the data service based at least in part on the first URSP rule comprises: routing the data service via one of the first protocol stack or the second protocol stack based at least in part on a first RSD associated with the first URSP rule for routing the data service, wherein the first RSD is at least in part based on an RSD associated with the first URSP rule and the validity indicator associated with the first RSD is empty.

[0257] Aspect 9: The method according to any one of Aspects 5 to 8, wherein each RSD in the set of RSDs includes a subscription validity indicator that identifies the protocol stack used for routing the data service.

[0258] Aspect 10: The method according to Aspect 9, wherein routing the data service based at least in part on the first URSP rule comprises: routing the data service via the protocol stack identified by the subscription validity indicator associated with the first RSD, guided at least in part on the preferred access type indication form associated with the first RSD, the first RSD being associated with the first URSP rule for routing the data service and based at least in part on the capabilities of one or both of the first and second protocol stacks and one or more validity indicators associated with one or more RSDs associated with the first URSP rule.

[0259] Aspect 11: The method according to any one of Aspects 9 to 10, wherein routing the data service based at least in part on the first URSP rule comprises: routing the data service via one or both of the first protocol stack or the second protocol stack based on the subscription validity indicator associated with a first RSD of the first URSP rule for routing the data service being empty, wherein the first RSD is based at least in part on the capabilities of one or both of the first protocol stack and the second protocol stack and one or more validity indicators associated with one or more RSDs of the first URSP rule.

[0260] Aspect 12: The method according to any one of Aspects 1 to 11, wherein routing the data service via one or both of the first protocol stack or the second protocol stack comprises: routing the data service via both the first protocol stack or the second protocol stack.

[0261] Aspect 13: The method according to aspect 12, the method further comprising: initiating a first packet data unit (PDU) session at the first protocol stack; initiating a second PDU session at the second protocol stack; sending a first request to the core network and via the first protocol stack to establish the first PDU session, wherein the first request indicates an identifier associated with the second protocol stack and an identifier associated with the second PDU session; and sending a second request to the core network and via the second protocol stack to establish the second PDU session, wherein the second request indicates an identifier associated with the first protocol stack and an identifier associated with the first PDU session.

[0262] Aspect 14: A method for wireless communication by a network entity, the method comprising: receiving from a UE an indication of the UE's ability to bootstrap data services associated with the UE via a plurality of protocol stacks of the UE, wherein each protocol stack of the UE corresponds to a corresponding subscription among a plurality of subscriptions of the UE; updating a first set of UE routing policy (URSP) rules at least in part based on the UE's capability to support dual bootstrap functionality at the UE; and sending the first set of URSP rules to the UE.

[0263] Aspect 15: The method according to aspect 14, wherein the first set of URSP rules is associated with a first protocol stack among the plurality of protocol stacks of the UE, the method further comprising: sending a second set of URSP rules at least in part based on the capabilities of the UE to support the dual-booting functionality at the UE, wherein the second set of URSP rules is associated with a second protocol stack among the plurality of protocol stacks of the UE.

[0264] Aspect 16: The method according to any one of Aspects 14 to 15, wherein the first set of URSP rules is associated with the plurality of protocol stacks of the UE.

[0265] Aspect 17: The method according to any one of Aspects 14 to 16, wherein each rule in the first set of URSP rules includes a set of Routing Descriptors (RSDs) and a service descriptor, and wherein each RSD in the set of RSDs includes: a preferred access type, the preferred access type indicating whether single bootstrapping or dual bootstrapping is performed; and a validity field, the validity field indicating one or more RAT capabilities corresponding to one or more of the following: a first protocol stack in the plurality of protocol stacks, a second protocol stack in the plurality of protocol stacks, a first subscription in the plurality of subscriptions, or a second subscription in the plurality of subscriptions, or any combination thereof.

[0266] Aspect 18: According to the method of aspect 17, each RSD in the set of RSDs includes a subscription validity indicator that identifies which protocol stack among the plurality of protocol stacks of the UE routes the service.

[0267] Aspect 19: The method according to any one of Aspects 14 to 18, the method further comprising: receiving from the UE a first request to establish a first PDU session associated with a first protocol stack among the plurality of protocol stacks of the UE, wherein the first request includes an indication of an identifier associated with a second protocol stack among the plurality of protocol stacks of the UE and an identifier associated with a second PDU session associated with the second protocol stack.

[0268] Aspect 20: The method according to aspect 19, the method further comprising: receiving from the UE a second request to establish the second PDU session, wherein the second request includes indications of an identifier associated with the first protocol stack and an identifier associated with the first PDU session.

[0269] Aspect 21: The method according to aspect 20, the method further comprising: associating the first PDU session and the second PDU session with the UE at least in part based on receiving the first request and the second request.

[0270] Aspect 22: 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 to cause the UE to perform a method according to any one of aspects 1 to 13.

[0271] Aspect 23: A UE for wireless communication, the UE including at least one component for performing the method according to any one of aspects 1 to 13.

[0272] Aspect 24: 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.

[0273] Aspect 25: A network entity for wireless communication, the network entity 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 to cause the network entity to perform a method according to any one of Aspects 14 to 21.

[0274] Aspect 26: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 14 to 21.

[0275] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform a method according to any one of aspects 14 to 21.

[0276] 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.

[0277] 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 other than 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.

[0278] 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.

[0279] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, 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 cooperating 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 functions or operations individually or jointly.

[0280] The functionality 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 functionality 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 functionality described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functionality can also be physically located in various locations, including portions distributed such that the functionality is implemented at different physical locations.

[0281] 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.

[0282] 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".

[0283] 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” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and subsequent reference to “the component” in a claim may be understood to be 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” may 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".

[0284] 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, obtaining, selecting, choosing, creating, and other similar actions.

[0285] 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.

[0286] 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 figures, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0287] 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: The instruction is sent via a first protocol stack among the plurality of protocol stacks of the UE to indicate the UE's ability to guide data services associated with the UE via the first protocol stack or the second protocol stack among the plurality of protocol stacks, wherein the first protocol stack corresponds to a first subscription among the plurality of subscriptions of the UE, and the second protocol stack corresponds to a second subscription among the plurality of subscriptions; The first set of UE routing policy (URSP) rules for guiding the data services associated with the UE is received, at least in part, based on the capabilities of the UE. as well as Based at least in part on the first set of URSP rules and the capabilities of the UE, the data services associated with the UE are routed via a higher layer of the UE, via one or both of the first protocol stack and the second protocol stack.

2. The UE of claim 1, wherein the first set of URSP rules is received via the first protocol stack, and the one or more processors are individually or jointly capable of further operating to execute the code to enable the UE to: The second set of URSP rules for guiding the data service is received via the second protocol stack and at least in part based on the capabilities of the UE, wherein the first set of URSP rules is associated with the first protocol stack, and the second set of URSP rules is associated with the second protocol stack.

3. The UE of claim 1, wherein the first set of URSP rules is received via the higher layer of the UE and associated with both the first protocol stack and the second protocol stack.

4. The UE of claim 1, wherein each rule in the first set of URSP rules comprises a set of routing descriptors (RSDs) and a service descriptor, and wherein each RSD in the set of RSDs comprises: The preferred access type indicates whether to perform a single boot or a dual boot; and The validity field indicates one or more radio access technology capabilities corresponding to one or more of the first protocol stack, the second protocol stack, the first subscription, or the second subscription, or any combination thereof.

5. The UE of claim 4, wherein, in order to route the data service via one or both of the first protocol stack and the second protocol stack, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The data service is routed at least in part based on a first URSP rule, which is based at least in part on service information associated with the data service and one or more service descriptors associated with one or more URSP rules in the first set of URSP rules.

6. The UE of claim 5, wherein, in order to route the data service at least in part based on the first URSP rule, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The data service is routed via both the first protocol stack and the second protocol stack, at least in part based on the preferred access type associated with a first RSD of the first URSP rule used for routing the data service, wherein the first RSD is at least in part based on the capabilities of one or both of the first protocol stack and the second protocol stack, and one or more validity indicators associated with one or more RSDs associated with the first URSP rule.

7. The UE of claim 5, wherein, in order to route the data service at least in part based on the first URSP rule, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The data service is routed via either the first protocol stack or the second protocol stack, at least in part, based on the preferred access type associated with a first RSD of the first URSP rule used for routing the data service. The first RSD is at least in part based on capabilities associated with one or both of the first and second protocol stacks and one or more validity indicators associated with one or more RSDs of the first URSP rule.

8. The UE of claim 5, wherein, in order to route the data service at least in part based on the first URSP rule, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The data service is routed via either the first protocol stack or the second protocol stack, at least in part based on a first RSD associated with the first URSP rule used for routing the data service, wherein the first RSD is at least in part based on an RSD associated with the first URSP rule and the validity indicator associated with the first RSD is empty.

9. The UE of claim 5, wherein each RSD in the set of RSDs includes a subscription validity indicator that identifies the protocol stack used for routing the data service.

10. The UE of claim 9, wherein, in order to route the data service at least in part based on the first URSP rule, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The data service is routed via the protocol stack identified by the subscription validity indicator associated with the first RSD, which is at least partially guided by the preferred access type indication form associated with the first RSD, the first RSD being associated with the first URSP rule for routing the data service, and at least partially based on the capabilities of one or both of the first and second protocol stacks and one or more validity indicators associated with one or more RSDs associated with the first URSP rule.

11. The UE of claim 9, wherein, in order to route the data service at least in part based on the first URSP rule, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The data service is routed via one or both of the first protocol stack and the second protocol stack based on the fact that the subscription validity indicator associated with the first RSD of the first URSP rule used for routing the data service is empty. The first RSD is based at least in part on the capabilities of one or both of the first protocol stack and the second protocol stack and one or more validity indicators associated with one or more RSDs associated with the first URSP rule.

12. The UE of claim 1, wherein, in order to route the data service via one or both of the first protocol stack and the second protocol stack, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The data service is routed via either the first protocol stack or the second protocol stack.

13. The UE of claim 12, wherein the one or more processors are individually or jointly further operable to execute the code to cause the UE to: Initiate a first protocol data unit (PDU) session at the first protocol stack; Initiate a second PDU session at the second protocol stack; Send a first request to the core network and via the first protocol stack to establish the first PDU session, wherein the first request indicates an identifier associated with the second protocol stack and an identifier associated with the second PDU session; as well as A second request to establish the second PDU session is sent to the core network and via the second protocol stack, wherein the second request indicates an identifier associated with the first protocol stack and an identifier associated with the first PDU session.

14. A network entity, the network entity 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 network entity: Receive an indication from the User Equipment (UE) of the UE’s ability to boot data services associated with the UE via multiple protocol stacks of the UE, wherein each protocol stack of the UE corresponds to a corresponding subscription among multiple subscriptions of the UE; The first set of UE routing policy (URSP) rules is updated, at least in part, based on the capabilities of the UE, to support dual-booting functionality at the UE; as well as Send the first set of URSP rules to the UE.

15. The network entity of claim 14, wherein the first set of URSP rules is associated with a first protocol stack among the plurality of protocol stacks of the UE, and the one or more processors are individually or jointly capable of further operating to execute the code to cause the network entity to: A second set of URSP rules is sent, at least in part, based on the capabilities of the UE, to support the dual-booting functionality at the UE, wherein the second set of URSP rules is associated with a second protocol stack among the plurality of protocol stacks of the UE.

16. The network entity of claim 14, wherein the first set of URSP rules is associated with the plurality of protocol stacks of the UE.

17. The network entity of claim 14, wherein each rule in the first set of URSP rules comprises a set of routing descriptors (RSDs) and a service descriptor, and wherein each RSD in the set of RSDs comprises: Preferred access type, wherein the preferred access type indicates whether to perform a single boot or a dual boot; and A validity field indicating one or more radio access technology capabilities corresponding to one or more of the following: a first protocol stack of the plurality of protocol stacks, a second protocol stack of the plurality of protocol stacks, a first subscription of the plurality of subscriptions, or a second subscription of the plurality of subscriptions, or any combination thereof.

18. The network entity of claim 14, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: The UE receives a first request to establish a first PDU session associated with a first protocol stack among the plurality of protocol stacks of the UE, wherein the first request includes an identifier associated with a second protocol stack among the plurality of protocol stacks of the UE and an identifier associated with a second PDU session associated with the second protocol stack.

19. The network entity of claim 18, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: The UE receives a second request to establish the second PDU session, wherein the second request includes indications of an identifier associated with the first protocol stack and an identifier associated with the first PDU session; and The first PDU session and the second PDU session are associated with the UE at least in part based on receiving the first request and the second request.

20. A method for wireless communication by a user equipment (UE), the method comprising: The instruction is sent via a first protocol stack among the plurality of protocol stacks of the UE to indicate the UE's ability to guide data services associated with the UE via the first protocol stack or the second protocol stack among the plurality of protocol stacks, wherein the first protocol stack corresponds to a first subscription among the plurality of subscriptions of the UE, and the second protocol stack corresponds to a second subscription among the plurality of subscriptions; The first set of UE routing policy (URSP) rules for guiding the data services associated with the UE is received, at least in part, based on the capabilities of the UE. as well as Based at least in part on the first set of URSP rules and the capabilities of the UE, the data services associated with the UE are routed via a higher layer of the UE, via one or both of the first protocol stack and the second protocol stack.

Images