Techniques for wireless communication using multiple radio access technologies

Abstract

Methods, systems, and devices are described that support techniques for wireless communication using multiple radio access technologies (RATs). The described techniques provide dual connectivity (DC), carrier aggregation, or both, in which different carriers are provided via different RATs. The multi-RAT DC configuration may include separate network entities that provide communications for different cell groups of different RATs, where dynamic power control may be implemented across RATs. Additionally or alternatively, the multi-RAT carrier aggregation techniques may provide separate component carriers configured for carrier aggregation, where different component carriers use different RATs. A combination of DC and carrier aggregation may be provided, where a DC configured cell group may include a plurality of component carriers in a carrier aggregation scheme.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 876,339, filed by Hosseini et al. on July 28, 2022, entitled “TECHNIQUESFOR WIRELESS COMMUNICATIONS USING MULTIPLE RADIO ACCESS TECHNOLOGIES,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including techniques for wireless communications using various radio access technologies. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. These systems may be able to 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, advanced LTE (LTE-A) systems, or LTE-A Pro systems), fifth generation (5G) systems, which may be referred to as new radio (NR) systems, and sixth generation (6G) systems. These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more network devices (e.g., base stations) that support wireless communication of communication devices, which may be referred to as user equipment (UE).

[0005] Different generations of wireless multiple access communication systems use associated different radio access technologies (RATs) to provide wireless connectivity, and in some cases may be deployed concurrently, where coverage areas overlap. In some cases, a UE may be able to communicate using multiple RATs, and different RATs may be suitable for different types of communications. Therefore, in order to provide efficient and reliable communication between UEs using different RATs and associated radio access networks (RANs), it may be desirable to provide techniques for efficient communication using multiple RATs. Summary of the invention

[0006] The described techniques relate to improved methods, systems, devices, and apparatuses that support techniques for wireless communications using multiple radio access technologies (RATs). According to various aspects, the described techniques provide dual connectivity (DC), carrier aggregation, or both, wherein different carriers are provided via different RATs. According to some aspects, a multi-RAT DC configuration may include a separate network entity that provides communications for different groups of cells of different RATs, wherein dynamic power control may be implemented across the RATs. In some cases, power control signaling may be provided that indicates which RAT is prioritized for power control (e.g., a network entity indicates that a first RAT is prioritized for power control, and the transmit power for a second RAT is scaled based on the power used by the first RAT). Additionally or alternatively, uplink power control may be based on prioritization of two or more services associated with different carriers of different network entities (e.g., a carrier with a high priority transmission is prioritized and receives full transmit power, and a carrier providing a lower priority transmission has a scaled power). In other cases, carriers may additionally or alternatively be prioritized based on the waveform used for transmission (e.g., a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform used for data may have a lower priority than a frequency modulated continuous wave (FMCW) waveform used for sensing) or based on channel type or content (e.g., a physical uplink control channel (PUCCH) transmission may take precedence over a physical uplink shared channel (PUSCH) transmission).

[0007] According to some aspects, additionally or alternatively, a multi-RAT carrier aggregation configuration may include a single network entity that provides scheduling for different component carriers (CCs) using different RATs. In some cases, a first CC (e.g., for a primary cell (PCell)) may be associated with a first RAT, and a second CC (e.g., for a secondary cell (SCell)) may be associated with a second RAT. In some cases, multiple bandwidth parts (BWPs) may be configured at a UE, and different BWPs may be associated with different RATs, such that a first CC may be configured for a first RAT or a second RAT based on the BWP of the carrier. Alternatively, a CC may be configured with multiple BWPs, and each BWP may be associated with one RAT or multiple RATs. In such cases, switching the first CC to a different BWP may thus switch the first CC between different RATs. In some cases, power control may be provided for each CC based on one or more of a service provided via the associated CC, a waveform type of the associated CC, a channel type of the associated CC, or any combination thereof. \Similarly, various carrier aggregation functions for CCs (e.g., uplink control information transmission, confirmation / negative confirmation feedback, resource scheduling, logical channel prioritization, UE capability reporting, discontinuous reception (DRX) configuration, or any combination thereof) may be provided for each RAT or may be multiplexed across RATs.

[0008] In some additional aspects, additionally or alternatively, a semi-static carrier group configuration may provide carrier groups where CCs in each of two or more groups may use a first RAT, a second RAT, or a mix of RATs, where the CCs remain in one group until subsequent signaling reconfigures the carrier group to have different CCs, different RATs for the CCs, or any combination thereof (e.g., the carrier groups are semi-static). In some cases, power control may be provided for each CC of each group of CCs based on one or more of a service provided via the associated CC, a waveform type of the associated CC, a channel type of the associated CC, or any combination thereof. Similarly, various carrier aggregation functions for CCs (e.g., uplink control information transmission, ACK / NACK feedback, resource scheduling, logical channel prioritization, UE capability reporting, discontinuous reception (DRX) configuration, or any combination thereof) may be provided for each RAT or may be multiplexed across RATs.

[0009] In further aspects, additionally or alternatively, multi-RAT mixed mode carrier aggregation and DC configuration may be implemented. In such aspects, a cell group with a DC configuration may include multiple different CCs in a carrier aggregation configuration, where different CCs may use different RATs. In some cases, similar to what is discussed above, different CCs may be associated with different RATs based on the BWP of the CCs. In some cases, the timing boundary between the first RAT and the second RAT may be synchronized, and the first RAT communications may be multiplexed with the second RAT communications on the same carrier.

[0010] A method for wireless communication at a user equipment (UE) is described. The method may include: receiving carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first radio access technology and the secondary component carrier uses a second radio access technology; and communicating with a first radio access network using the primary component carrier and communicating with a second radio access network using the secondary component carrier based on the carrier aggregation configuration information.

[0011] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first radio access technology and the secondary component carrier uses a second radio access technology; and based on the carrier aggregation configuration information, use the primary component carrier to communicate with a first radio access network and use the secondary component carrier to communicate with a second radio access network.

[0012] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first radio access technology and the secondary component carrier uses a second radio access technology; and means for communicating with a first radio access network using the primary component carrier and communicating with a second radio access network using the secondary component carrier based on the carrier aggregation configuration information.

[0013] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to receive carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first radio access technology and the secondary component carrier uses a second radio access technology; and based on the carrier aggregation configuration information, use the primary component carrier to communicate with a first radio access network and use the secondary component carrier to communicate with a second radio access network.

[0014] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first radio access technology may be a fifth generation (5G) radio access technology, and the second radio access technology may be a sixth generation (6G) radio access technology. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the same network entity provides physical layer scheduling information for both the primary component carrier and the secondary component carrier.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving carrier aggregation configuration information may include operations, features, components, or instructions for performing the following actions: receiving a bandwidth portion configuration for a set of multiple bandwidth portions for a channel bandwidth, a primary component carrier, a secondary component carrier, or both being configurable to operate on the set of multiple bandwidth portions, wherein a first bandwidth portion in the set of multiple bandwidth portions is associated with a first radio access technology and a second bandwidth portion in the set of multiple bandwidth portions is associated with a second radio access technology, and wherein the primary component carrier is associated with the first radio access technology based on being configured with the first bandwidth portion, and the secondary component carrier is associated with the second radio access technology based on being configured with the second bandwidth portion.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a primary component carrier is configured to operate on a plurality of bandwidth portions, and wherein communication via one or both of the first radio access technology or the second radio access technology is based on which of the plurality of bandwidth portions is used for communication.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving carrier aggregation configuration information may include operations, features, components, or instructions for performing the following actions: receiving an indication of which of the first radio access technology or the second radio access technology is associated with a primary component carrier and a secondary component carrier via one or more of the following: control channel communication; an indication of a control resource set (CORESET) associated with each component carrier, where different CORESETs are associated with different radio access technologies; downlink control information communication; or any combination thereof.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining a first uplink transmit power for a first uplink transmission via a primary component carrier and a second uplink transmit power for a second uplink transmission via a secondary component carrier based on an indication in the carrier aggregation configuration information as to which of the first radio access technology or the second radio access technology has a higher priority for uplink power control.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: identifying that both uplink communications and downlink communications are to be sent via a primary component carrier, a secondary component carrier, or both, or via a first bandwidth portion, a second bandwidth portion, or both, wherein each bandwidth portion is associated with one or more radio access technologies; and prioritizing uplink communications or downlink communications based on which of the first radio access technology or the second radio access technology has a higher priority for communication, a service type associated with each of the uplink communications and the downlink communications, a priority of data to be sent in each of the uplink communications and the downlink communications, a physical layer channel type sent in each of the uplink communications and the downlink communications, a waveform type used for each of the uplink communications and the downlink communications, or any combination thereof.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: identifying a first uplink transmission to be provided to a first radio access network and a second uplink transmission to be provided to a second radio access network; and determining one or more of the component carriers or bandwidth portions to be used for each of the first uplink transmission and the second uplink transmission based on carrier aggregation configuration information; or multiplexing the first uplink transmission and the second uplink transmission for transmission via one component carrier or bandwidth portion.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the determination may be based on one or more of: a codebook type associated with the first uplink transmission and the second uplink transmission, a waveform of the first uplink transmission and the second uplink transmission, a transmission format of a physical layer channel carrying the first uplink transmission and the second uplink transmission, a priority order of the first radio access technology and the second radio access technology, a service type associated with the first uplink transmission and the second uplink transmission, or any combination thereof.

[0022] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first uplink transmission and the second uplink transmission include one or more of the following: feedback information indicating whether one or more downlink communications are successfully decoded, uplink control information, uplink shared channel data, or any combination thereof. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving one or more triggers to perform one or more operations associated with a primary component carrier or a secondary component carrier, wherein the one or more triggers are received separately for each radio access technology, or receiving a single trigger indicating that one or more operations are performed using both the first radio access technology and the second radio access technology.

[0023] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the one or more operations include one or more of the following: sounding reference signal transmission, activation or deactivation of a secondary cell that uses a secondary component carrier to provide service, semi-persistent scheduling or configuration grant activation or deactivation, power control procedures, or any combination thereof. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the one or more triggers are provided in a downlink control information trigger container or a medium access control (MAC) control element trigger container, and each trigger is applied to one or both of the first radio access technology or the second radio access technology based on the type of the trigger container that provides the one or more triggers.

[0024] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending a scheduling request via a primary component carrier or a secondary component carrier or via a first bandwidth portion or a second bandwidth portion, wherein the scheduling request is for resources of the first radio access technology, the second radio access technology, or both the first radio access technology and the second radio access technology. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving one or more resource allocations or bandwidth portion scheduling indications, wherein the one or more resource allocations or bandwidth portion scheduling indications are provided for each radio access technology or across each radio access technology.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, logical channel prioritization for two or more logical channels to be provided via a primary component carrier or a secondary component carrier is based on which of the first radio access technology or the second radio access technology is associated with one or more of the primary component carrier, the secondary component carrier, or the bandwidth portion carrying data for the associated logical channels. Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a UE capability report indicating one or more UE capabilities for each radio access technology or across radio access technologies.

[0026] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a discontinuous reception configuration for the UE is provided for each radio access technology or across radio access technologies. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a primary component carrier and a secondary component carrier are included in a first set of component carriers of a first cell group of a dual connectivity configuration of the UE, and a second set of component carriers are configured in a second cell group of the dual connectivity configuration of the UE.

[0027] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a first MAC entity provides scheduling information for a first set of component carriers, and a second medium access control (MAC) entity provides scheduling information for a second set of component carriers. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a primary component carrier and a secondary component carrier are each assigned to a first cell group or a second cell group based on one or more of a service type associated with each respective component carrier, a physical layer indication or a MAC layer indication associated with each respective component carrier, one or more physical layer channels carried using each respective component carrier, a type of information carried using each respective component carrier, or any combination thereof.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a set of multiple bandwidth parts (BWPs) is configured for communication at a UE, each BWP in the set of multiple BWPs is associated with one of a first radio access technology or a second radio access technology, different BWPs in the set of multiple BWPs are configured for different services, and a BWP switching for a carrier indicates that the radio access technology associated with the carrier is to be switched.

[0029] A method for wireless communication at a UE is described. The method may include: receiving dual connectivity configuration information for a first cell group and a second cell group, wherein the first cell group is served using one or more carriers using a first radio access technology, and the second cell group is served using one or more carriers using a second radio access technology, and wherein different network entities provide physical layer scheduling information for the first cell group and the second cell group; receiving uplink power control information, the uplink power control information including an indication of a first uplink transmission power for a first uplink transmission and a second uplink transmission power for a second uplink transmission, the first uplink transmission power and the second uplink transmission power being indicated as being preferentially used for uplink power control based on which of the first carrier of the first cell group or the second carrier of the second cell group is indicated; and sending a first uplink transmission using the first carrier concurrently with sending a second uplink transmission using the second carrier, the first uplink transmission using the first uplink transmission power and the second uplink transmission using the second uplink transmission power.

[0030] A device for wireless communication at a UE is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to receive dual connectivity configuration information for a first cell group and a second cell group, wherein one or more carriers using a first radio access technology are used to provide services for the first cell group, and one or more carriers using a second radio access technology are used to provide services for the second cell group, and wherein different network entities provide physical layer scheduling information for the first cell group and the second cell group; receive uplink power control information, the uplink power control information including an indication of a first uplink transmission power for a first uplink transmission and a second uplink transmission power for a second uplink transmission, the first uplink transmission power and the second uplink transmission power are based on which of the first carrier of the first cell group or the second carrier of the second cell group is indicated as being preferentially used for uplink power control; and send a first uplink transmission using the first carrier concurrently with sending a second uplink transmission using the second carrier, the first uplink transmission using the first uplink transmission power and the second uplink transmission using the second uplink transmission power.

[0031] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for receiving dual connectivity configuration information for a first cell group and a second cell group, wherein the first cell group is served using one or more carriers using a first radio access technology, and the second cell group is served using one or more carriers using a second radio access technology, and wherein different network entities provide physical layer scheduling information for the first cell group and the second cell group; a component for receiving uplink power control information, the uplink power control information including an indication of a first uplink transmission power for a first uplink transmission and a second uplink transmission power for a second uplink transmission, the first uplink transmission power and the second uplink transmission power being indicated as being preferentially used for uplink power control based on which of the first carrier of the first cell group or the second carrier of the second cell group is indicated; and a component for sending a first uplink transmission using the first carrier concurrently with sending a second uplink transmission using the second carrier, the first uplink transmission using the first uplink transmission power and the second uplink transmission using the second uplink transmission power.

[0032] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by a processor to receive dual connectivity configuration information for a first cell group and a second cell group, wherein the first cell group is served using one or more carriers using a first radio access technology, and the second cell group is served using one or more carriers using a second radio access technology, and wherein different network entities provide physical layer scheduling information for the first cell group and the second cell group; receive uplink power control information, the uplink power control information including an indication of a first uplink transmission power for a first uplink transmission and a second uplink transmission power for a second uplink transmission, the first uplink transmission power and the second uplink transmission power are based on which of the first carrier of the first cell group or the second carrier of the second cell group is indicated as being preferentially used for uplink power control; and send a first uplink transmission using the first carrier concurrently with sending a second uplink transmission using the second carrier, the first uplink transmission using the first uplink transmission power and the second uplink transmission using the second uplink transmission power.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the dual connectivity configuration information indicates a carrier priority ordering based on one or more services, one or more priorities, or any combination thereof associated with the first carrier and the second carrier.

[0034] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining power scaling associated with the first carrier and the second carrier based on one or more services associated with each of the first carrier and the second carrier, one or more priorities, or any combination thereof. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first carrier and the second carrier are prioritized for uplink power control based on a priority ranking of one or more physical layer services or medium access control layer logical channels provided using the first carrier and the second carrier and associated services or logical channels provided in the dual connectivity configuration information.

[0035] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first carrier and the second carrier are prioritized for uplink power control based on the waveform type priority ranking provided in the dual connectivity configuration information and the associated waveform types of the first carrier and the second carrier. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first carrier and the second carrier are prioritized for uplink power control based on one or more types of channels or data types provided using the first carrier and the second carrier. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the dual connectivity configuration information configures at least two or more component carriers in a carrier aggregation configuration for a first cell group, and the first cell group includes component carriers associated with different radio access technologies.

[0036] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a first MAC entity provides physical layer scheduling information for each component carrier of a first cell group, and a second MAC entity provides physical layer scheduling information for each component carrier of a second cell group. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining that the first carrier is included in the first cell group or the second cell group based on one or more of a type of service provided using the first carrier, a physical layer or medium access control layer indication associated with the first carrier, one or more channels sent via the first carrier, a type of information sent via the first carrier, a priority associated with the information sent via the first carrier, or any combination thereof.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a set of multiple bandwidth parts (BWPs) is configured for communication at a UE, each BWP in the set of multiple BWPs is associated with one of a first radio access technology or a second radio access technology, different BWPs in the set of multiple BWPs are configured for different services, and a BWP switching for a carrier indicates that the radio access technology associated with the carrier is to be switched.

[0038] A method for wireless communication at a UE is described. The method may include: receiving dual connectivity configuration information for a first cell and a second cell, wherein the first cell is associated with a first carrier using a first radio access technology, and the second cell is associated with a second carrier using a second radio access technology, and wherein the first carrier and the second carrier share the same set of wireless resources multiplexed between the first cell and the second cell in a time interval synchronized between the first radio access technology and the second radio access technology; and using the first carrier to communicate with a first radio access network and using the second carrier to communicate with a second radio access network based on a multiplexing configuration indicated in the dual connectivity configuration information, wherein the first carrier and the second carrier are different component carriers configured using frequency domain multiplexing or are the same component carrier configured using time domain multiplexing.

[0039] A device for wireless communication at a UE is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to receive dual connectivity configuration information for a first cell and a second cell, wherein the first cell is associated with a first carrier using a first radio access technology, and the second cell is associated with a second carrier using a second radio access technology, and wherein the first carrier and the second carrier share the same set of wireless resources multiplexed between the first cell and the second cell in a time interval synchronized between the first radio access technology and the second radio access technology; and based on the multiplexing configuration indicated in the dual connectivity configuration information, use the first carrier to communicate with a first radio access network and use the second carrier to communicate with a second radio access network, wherein the first carrier and the second carrier are different component carriers configured using frequency domain multiplexing or the same component carrier configured using time domain multiplexing.

[0040] Another apparatus for wireless communication at a UE is described. The apparatus may include a component for receiving dual connectivity configuration information for a first cell and a second cell, wherein the first cell is associated with a first carrier using a first radio access technology, and the second cell is associated with a second carrier using a second radio access technology, and wherein the first carrier and the second carrier share the same set of wireless resources multiplexed between the first cell and the second cell in a time interval synchronized between the first radio access technology and the second radio access technology; and a component for using the first carrier to communicate with a first radio access network and using the second carrier to communicate with a second radio access network based on a multiplexing configuration indicated in the dual connectivity configuration information, wherein the first carrier and the second carrier are different component carriers configured using frequency domain multiplexing or are the same component carrier configured using time domain multiplexing.

[0041] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by a processor to receive dual connectivity configuration information for a first cell and a second cell, wherein the first cell is associated with a first carrier using a first radio access technology, and the second cell is associated with a second carrier using a second radio access technology, and wherein the first carrier and the second carrier share the same set of wireless resources multiplexed between the first cell and the second cell in a time interval synchronized between the first radio access technology and the second radio access technology; and based on the multiplexing configuration indicated in the dual connectivity configuration information, use the first carrier to communicate with a first radio access network and use the second carrier to communicate with a second radio access network, wherein the first carrier and the second carrier are different component carriers configured using frequency domain multiplexing or the same component carrier configured using time domain multiplexing.

[0042] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the time interval may be a time slot or symbol synchronized at a corresponding time slot or symbol boundary used in a first radio access network and a second radio access network, and the multiplexing configuration indicates time division multiplexing in the time slot or symbol. Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving scheduling information for a first cell from a first scheduling entity associated with a first radio access network and receiving scheduling information for a second cell from a second scheduling entity associated with a second radio access network. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the dual connectivity configuration information provides a set of time slots, wherein a first subset of time slots is used for a first radio access network and a second subset of time slots is used for a second radio access network. In some examples of the methods, devices, and non-transitory computer-readable media described herein, a ratio of a first number of time slots in a first subset of time slots to a second number of time slots in a second subset of time slots is determined based on a buffer state associated with each cell, a time division duplex (TDD) time slot mode of each cell, or any combination thereof.

[0043] In some examples of the methods, devices, and non-transitory computer-readable media described herein, a scheduling pattern for a first subset of time slots and a second subset of time slots is provided in downlink control information, in a MAC control element, in a downlink signal indicating a time slot sequence and a corresponding cell, or in any combination thereof. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the scheduling pattern is applied to uplink communications and downlink communications for in-band transmission and inter-band transmission for each carrier. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the multiplexing configuration indicated in the dual connectivity configuration information provides frequency domain multiplexing or spatial domain multiplexing. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the multiplexing configuration indicated in the dual connectivity configuration information provides radio spectrum sharing for two or more operators, and the two or more operators use a first radio access technology, a second radio access technology, or both to operate different radio access networks.

[0044] A method for wireless communication at a network entity is described. The method may include: sending carrier aggregation configuration information for a primary component carrier and for a secondary component carrier to a UE, wherein the primary component carrier uses a first radio access technology and is associated with a first radio access network, and the secondary component carrier uses a second radio access technology and is associated with a second radio access network; and communicating with the UE based on the carrier aggregation configuration information.

[0045] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to send carrier aggregation configuration information for a primary component carrier and for a secondary component carrier to a UE, wherein the primary component carrier uses a first radio access technology and is associated with a first radio access network, and the secondary component carrier uses a second radio access technology and is associated with a second radio access network; and communicate with the UE based on the carrier aggregation configuration information.

[0046] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for sending carrier aggregation configuration information for a primary component carrier and for a secondary component carrier to a UE, wherein the primary component carrier uses a first radio access technology and is associated with a first radio access network, and the secondary component carrier uses a second radio access technology and is associated with a second radio access network; and means for communicating with the UE based on the carrier aggregation configuration information.

[0047] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to send carrier aggregation configuration information for a primary component carrier and for a secondary component carrier to a UE, wherein the primary component carrier uses a first radio access technology and is associated with a first radio access network, and the secondary component carrier uses a second radio access technology and is associated with a second radio access network; and communicate with the UE based on the carrier aggregation configuration information.

[0048] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first radio access technology may be a fifth generation (5G) radio access technology and the second radio access technology may be a sixth generation (6G) radio access technology, and the same scheduling entity provides physical layer scheduling information for both the primary component carrier and the secondary component carrier.

[0049] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending carrier aggregation configuration information may include operations, features, components, or instructions for performing the following actions: sending a bandwidth portion configuration for a set of multiple bandwidth portions of a channel bandwidth, a primary component carrier, a secondary component carrier, or both being configurable to operate on the set of multiple bandwidth portions, wherein a first bandwidth portion in the set of multiple bandwidth portions is associated with a first radio access technology and a second bandwidth portion in the set of multiple bandwidth portions is associated with a second radio access technology, and wherein the primary component carrier is associated with the first radio access technology based on being configured with the first bandwidth portion, and the secondary component carrier is associated with the second radio access technology based on being configured with the second bandwidth portion.

[0050] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending carrier aggregation configuration information may include operations, features, components, or instructions for performing the following actions: sending an indication of which of the first radio access technology or the second radio access technology is associated with the primary component carrier and the secondary component carrier via one or more of the following: control channel communication; a control resource set (CORESET) indication associated with each component carrier, where different CORESETs are associated with different radio access technologies; downlink control information communication; or any combination thereof.

[0051] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a first uplink transmit power for a first uplink transmission via a primary component carrier or a first bandwidth portion and a second uplink transmit power for a second uplink transmission via a secondary component carrier or a second bandwidth portion are determined based on an indication in carrier aggregation configuration information as to which of the first radio access technology or the second radio access technology has a higher priority for uplink power control.

[0052] Some examples of the methods, apparatus and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: identifying that both uplink communications and downlink communications are to be sent via a primary component carrier, a secondary component carrier, or both; and prioritizing uplink communications or downlink communications based on which of the first radio access technology or the second radio access technology has a higher priority for communication, a service type associated with each of the uplink communication and the downlink communication, a priority of data to be sent in each of the uplink communication and the downlink communication, a physical layer channel type sent in each of the uplink communication and the downlink communication, a waveform type used for each of the uplink communication and the downlink communication, or any combination thereof.

[0053] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a first uplink transmission is provided to a first radio access network and a second uplink transmission is provided to a second radio access network, and wherein the carrier aggregation configuration information indicates that the first uplink transmission is to be sent via a primary component carrier and the second uplink transmission is to be sent via a secondary component carrier, or that the first uplink transmission and the second uplink transmission are to be multiplexed via the primary component carrier or the secondary component carrier.

[0054] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the per-component carrier transmission of the first uplink transmission and the second uplink transmission or the multiplexed transmission of the first uplink transmission and the second uplink transmission may be based on one or more of: a codebook type associated with the first uplink transmission and the second uplink transmission, a waveform of the first uplink transmission and the second uplink transmission, a transmission format of a physical layer channel carrying the first uplink transmission and the second uplink transmission, an order of priority of the first radio access technology and the second radio access technology, a service type associated with the first uplink transmission and the second uplink transmission, or any combination thereof.

[0055] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the first uplink transmission and the second uplink transmission include one or more of the following: feedback information indicating whether one or more downlink communications are successfully decoded, uplink control information, uplink shared channel data, or any combination thereof. Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending one or more triggers to perform one or more operations associated with a primary component carrier or a secondary component carrier, wherein the one or more triggers are sent separately for each radio access technology, or sending a single trigger indicating that one or more operations are performed using both the first radio access technology and the second radio access technology. In some examples of the methods, devices, and non-transitory computer-readable media described herein, one or more operations include one or more of the following: sounding reference signal transmission, activation or deactivation of a secondary cell associated with a secondary component carrier, semi-persistent scheduling or configuration grant activation or deactivation, power control procedures, or any combination thereof. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, one or more triggers are provided in a downlink control information trigger container or a MAC control element trigger container, and each trigger is applied to one or both of the first radio access technology or the second radio access technology based on the type of trigger container in which the one or more triggers are provided.

[0056] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a scheduling request is provided from a UE via a primary component carrier or a secondary component carrier, wherein the scheduling request is for resources of a first radio access technology, a second radio access technology, or both the first radio access technology and the second radio access technology. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending one or more resource allocations or bandwidth portion scheduling indications to the UE, wherein the one or more resource allocations or bandwidth portion scheduling indications are provided for each radio access technology or across radio access technologies. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, logical channel priority sorting for two or more logical channels to be provided via a primary component carrier or a secondary component carrier is based on which of the first radio access technology or the second radio access technology is associated with the primary component carrier or the secondary component carrier carrying the associated logical channel.

[0057] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the UE provides a UE capability report indicating one or more UE capabilities for each radio access technology or across radio access technologies. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a discontinuous reception configuration for the UE is provided for each radio access technology or across radio access technologies. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the primary component carrier and the secondary component carrier are included in a first set of component carriers of a first cell group of a dual connectivity configuration of the UE, and the second set of component carriers is configured in a second cell group of the dual connectivity configuration of the UE.

[0058] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a first MAC entity provides scheduling information for a first set of component carriers, and a second MAC entity provides scheduling information for a second set of component carriers. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a primary component carrier and a secondary component carrier are each assigned to a first cell group or a second cell group based on one or more of a service type associated with each respective component carrier, a physical layer indication or a MAC layer indication associated with each respective component carrier, one or more physical layer channels carried using each respective component carrier, a type of information carried using each respective component carrier, or any combination thereof.

[0059] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a set of multiple bandwidth parts (BWPs) is configured for communication at a UE, each BWP in the set of multiple BWPs is associated with one of a first radio access technology or a second radio access technology, different BWPs in the set of multiple BWPs are configured for different services, and a BWP switching for a carrier indicates that the radio access technology associated with the carrier is to be switched.

[0060] A method for wireless communication at a network entity is described. The method may include: sending dual connectivity configuration information for a first cell group and a second cell group to a UE, wherein the first cell group is associated with one or more carriers using a first radio access technology, and the second cell group is associated with one or more carriers using a second radio access technology, and wherein different scheduling entities provide physical layer scheduling information for the first cell group and the second cell group; sending uplink power control information to the UE, the uplink power control information including an indication of a first uplink transmission power for a first uplink transmission and a second uplink transmission power for a second uplink transmission, the first uplink transmission power and the second uplink transmission power being indicated as being preferentially used for uplink power control based on which of the first carrier of the first cell group or the second carrier of the second cell group is indicated; and receiving a first uplink transmission from the UE using the first carrier, wherein the first uplink transmission is sent concurrently with sending the second uplink transmission using the second carrier of the second cell group, the first uplink transmission using the first uplink transmission power and the second uplink transmission using the second uplink transmission power.

[0061] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instruction may be executable by the processor to cause the device to send dual connectivity configuration information for a first cell group and a second cell group to a UE, wherein the first cell group is associated with one or more carriers using a first radio access technology, and the second cell group is associated with one or more carriers using a second radio access technology, and wherein different scheduling entities provide physical layer scheduling information for the first cell group and the second cell group; send uplink power control information to the UE, the uplink power control information including an indication of a first uplink transmission power for a first uplink transmission and a second uplink transmission power for a second uplink transmission, the first uplink transmission power and the second uplink transmission power being indicated as being preferentially used for uplink power control based on which of the first carrier of the first cell group or the second carrier of the second cell group is indicated; and receive a first uplink transmission from the UE using the first carrier, wherein the first uplink transmission is sent concurrently with the second uplink transmission sent using the second carrier of the second cell group, the first uplink transmission uses the first uplink transmission power and the second uplink transmission uses the second uplink transmission power.

[0062] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a component for sending dual connectivity configuration information for a first cell group and a second cell group to a UE, wherein the first cell group is associated with one or more carriers using a first radio access technology, and the second cell group is associated with one or more carriers using a second radio access technology, and wherein different scheduling entities provide physical layer scheduling information for the first cell group and the second cell group; a component for sending uplink power control information to the UE, the uplink power control information including an indication of a first uplink transmission power for a first uplink transmission and a second uplink transmission power for a second uplink transmission, the first uplink transmission power and the second uplink transmission power being indicated as being preferentially used for uplink power control based on which of the first carrier of the first cell group or the second carrier of the second cell group is indicated as being preferentially used for uplink power control; and a component for receiving a first uplink transmission from the UE using a first carrier, wherein the first uplink transmission is sent concurrently with sending a second uplink transmission using a second carrier of the second cell group, the first uplink transmission using the first uplink transmission power and the second uplink transmission using the second uplink transmission power.

[0063] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions that are executable by a processor to send dual connectivity configuration information for a first cell group and a second cell group to a UE, wherein the first cell group is associated with one or more carriers using a first radio access technology, and the second cell group is associated with one or more carriers using a second radio access technology, and wherein different scheduling entities provide physical layer scheduling information for the first cell group and the second cell group; send uplink power control information to the UE, the uplink power control information including an indication of a first uplink transmit power for a first uplink transmission and a second uplink transmit power for a second uplink transmission, the first uplink transmit power and the second uplink transmit power being indicated as being preferentially used for uplink power control based on which of a first carrier of the first cell group or a second carrier of the second cell group is indicated; and receive a first uplink transmission from the UE using the first carrier, wherein the first uplink transmission is sent concurrently with sending a second uplink transmission using the second carrier of the second cell group, the first uplink transmission using the first uplink transmit power and the second uplink transmission using the second uplink transmit power.

[0064] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the dual connectivity configuration information indicates a carrier prioritization based on one or more services associated with the first carrier and the second carrier. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a power scaling associated with the first carrier and the second carrier is based on one or more services associated with each of the first carrier and the second carrier.

[0065] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first carrier and the second carrier are prioritized for uplink power control based on a priority ranking of one or more physical layer services or medium access control layer logical channels provided using the first carrier and the second carrier and associated services or logical channels provided in the dual connectivity configuration information. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first carrier and the second carrier are prioritized for uplink power control based on a waveform type priority ranking provided in the dual connectivity configuration information and associated waveform types of the first carrier and the second carrier.

[0066] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first carrier and the second carrier are prioritized for uplink power control based on one or more types of channels or data types provided via the first carrier and the second carrier. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the dual connectivity configuration information configures two or more component carriers in a carrier aggregation configuration for at least a first cell group, and the first cell group includes component carriers associated with different radio access technologies.

[0067] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a first MAC entity provides physical layer scheduling information for each component carrier of a first cell group, and a second MAC entity provides physical layer scheduling information for each component carrier of a second cell group. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining that the first carrier is included in the first cell group or the second cell group based on one or more of a type of service provided using the first carrier, a physical layer or medium access control layer indication associated with the first carrier, one or more channels sent via the first carrier, a type of information sent via the first carrier, or any combination thereof.

[0068] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a set of multiple bandwidth parts (BWPs) is configured for communication at a UE, each BWP in the set of multiple BWPs is associated with one of a first radio access technology or a second radio access technology, different BWPs in the set of multiple BWPs are configured for different services, and a BWP switching for a carrier indicates that the radio access technology associated with the carrier is to be switched.

[0069] A method for wireless communication at a network entity is described. The method may include: sending dual connectivity configuration information for a first cell and a second cell to a UE, wherein the first cell is associated with a first carrier using a first radio access technology, and the second cell is associated with a second carrier using a second radio access technology, and wherein the first carrier and the second carrier share the same set of radio resources multiplexed between the first cell and the second cell in a time interval synchronized between the first radio access technology and the second radio access technology; and communicating with the UE based on the multiplexing configuration indicated in the dual connectivity configuration information.

[0070] A device for wireless communication at a network entity is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to send dual connectivity configuration information for a first cell and a second cell to a UE, wherein the first cell is associated with a first carrier using a first radio access technology, and the second cell is associated with a second carrier using a second radio access technology, and wherein the first carrier and the second carrier share the same set of wireless resources multiplexed between the first cell and the second cell in a time interval synchronized between the first radio access technology and the second radio access technology; and communicate with the UE based on the multiplexing configuration indicated in the dual connectivity configuration information.

[0071] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a component for sending dual connectivity configuration information for a first cell and a second cell to a UE, wherein the first cell is associated with a first carrier using a first radio access technology, and the second cell is associated with a second carrier using a second radio access technology, and wherein the first carrier and the second carrier share the same set of radio resources multiplexed between the first cell and the second cell in a time interval synchronized between the first radio access technology and the second radio access technology; and a component for communicating with the UE based on the multiplexing configuration indicated in the dual connectivity configuration information.

[0072] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions that can be executed by a processor to send dual connectivity configuration information for a first cell and a second cell to a UE, wherein the first cell is associated with a first carrier using a first radio access technology, and the second cell is associated with a second carrier using a second radio access technology, and wherein the first carrier and the second carrier share the same set of radio resources multiplexed between the first cell and the second cell in a time interval synchronized between the first radio access technology and the second radio access technology; and communicate with the UE based on the multiplexing configuration indicated in the dual connectivity configuration information.

[0073] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the time interval may be a time slot synchronized at a time slot boundary used in a first radio access technology and a second radio access technology, and the multiplexing configuration indicates time division multiplexing in the time slot. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the dual connectivity configuration information provides a set of time slots, wherein a first subset of time slots is used for a first radio access technology and a second subset of time slots is used for a second radio access technology. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a ratio of a first number of time slots in a first subset of time slots to a second number of time slots in a second subset of time slots is determined based on a buffer state associated with each cell, a TDD time slot mode of each cell, or any combination thereof.

[0074] In some examples of the methods, devices, and non-transitory computer-readable media described herein, a scheduling pattern for a first subset of time slots and a second subset of time slots is provided in downlink control information, in a MAC control element, in a downlink signal indicating a time slot sequence and a corresponding cell, or in any combination thereof. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the scheduling pattern is applied to uplink communications and downlink communications for in-band transmission and inter-band transmission for each carrier. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the multiplexing configuration indicated in the dual connectivity configuration information provides frequency domain multiplexing or spatial domain multiplexing. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the multiplexing configuration indicated in the dual connectivity configuration information provides radio spectrum sharing for two or more operators, and the two or more operators use a first radio access technology, a second radio access technology, or both to operate different radio access networks. BRIEF DESCRIPTION OF THE DRAWINGS

[0075] Figure 1 An example of a wireless communication system supporting techniques for wireless communications using multiple radio access technologies (RATs) in accordance with one or more aspects of the present disclosure is illustrated.

[0076] Figure 2 An example of a network architecture supporting techniques for wireless communications using multiple RATs in accordance with one or more aspects of the present disclosure is illustrated.

[0077] Figures 3 to 5 An example of a wireless communication system supporting techniques for wireless communications using multiple RATs in accordance with one or more aspects of the present disclosure is illustrated.

[0078] Figures 6 to 8An example of a process flow supporting techniques for wireless communications using multiple RATs in accordance with one or more aspects of the present disclosure is illustrated.

[0079] Fig. 9 and Fig.10 A block diagram of a device supporting techniques for wireless communications using multiple RATs is shown in accordance with one or more aspects of the present disclosure.

[0080] Fig.11 A block diagram of a communications manager supporting techniques for wireless communications using multiple RATs is shown in accordance with one or more aspects of the present disclosure.

[0081] Fig.12

[0013] A diagram of a system including devices supporting techniques for wireless communications using multiple RATs is shown in accordance with one or more aspects of the present disclosure.

[0082] Fig.13 and Fig.14 A block diagram of a device supporting techniques for wireless communications using multiple RATs is shown in accordance with one or more aspects of the present disclosure.

[0083] Fig.15 A block diagram of a communications manager supporting techniques for wireless communications using multiple RATs is shown in accordance with one or more aspects of the present disclosure.

[0084] Fig.16 A diagram of a system including devices supporting techniques for wireless communications using multiple RATs is shown in accordance with one or more aspects of the present disclosure.

[0085] Figures 17 to 33 A flow chart illustrating a method of supporting techniques for wireless communications using multiple RATs in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0086] This article discusses technologies for wireless communications in which a user equipment (UE) can concurrently communicate with two or more radio access networks (RANs) using different radio access technologies (RATs). In the case where two or more RANs may be able to provide services for the UE, such technologies may allow for concurrent deployment of different RATs and efficient communication. For example, as the sixth generation (6G) system architecture and procedures are being developed and deployed, it may be beneficial to allow concurrent use of 6G RAT and 5G RAT to provide enhanced flexibility to provide services for both 5G and 6G devices and devices capable of both 5G and 6G communications. In addition, it may be beneficial to use different RATs to schedule different services, such as using a 6G RAT with lower latency to efficiently provide services for delay-sensitive services, while using a 5G RAT with higher latency but enhanced coverage or lower power consumption (or both) to efficiently provide services for relatively delay-tolerant services.

[0087] However, in the case where the UE is to communicate using multiple RATs concurrently, the power allocation of the available UE transmit power between the RATs is used so that the UE transmits at an appropriate power level. In the case where the first RAT has a longer timeline (e.g., timing between resource allocation and associated transmission) than the second RAT (such as 4G RAT has a longer timeline than 5G RAT), the transmit power of the first RAT can be set, and the transmit power of the second RAT can be scaled based on the transmit power of the first RAT. In the case where the communication processing timelines between the RATs are equal or the first RAT may not always have a longer timeline (e.g., 5G RAT may have an equal, longer, or shorter timeline than the corresponding timeline of the 6G RAT, depending on the service provided), the transmit power of the first RAT may not be known before determining the transmit power of the other RAT. According to various aspects discussed herein, techniques for hybrid RAT power control are provided. In some cases, techniques for determining which RAT has a higher priority for transmit power allocation are provided, and when the two RATs have concurrent transmissions, the other RAT with a lower priority can have its power scaled.

[0088] According to some aspects, a multi-RAT dual connectivity (DC) configuration may include separate network entities that schedule communications for different groups of cells of different RATs, where dynamic power control may be implemented across the RATs. In some cases, power control signaling may be provided that indicates which RAT is prioritized for power control (e.g., the network entity indicates that a first RAT is prioritized for power control, and the transmit power for a second RAT is scaled based on the power used at the first RAT). Additionally or alternatively, uplink power control may be based on prioritization of two or more services associated with different carriers of different network entities (e.g., a carrier with a high priority transmission is prioritized and receives full transmit power, and a carrier providing a lower priority transmission has a scaled power). In other cases, carriers may additionally or alternatively be prioritized based on the waveform used for transmission (e.g., a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform used for data may have a lower priority than a frequency modulated continuous wave (FMCW) waveform used for sensing) or based on channel type or content (e.g., a physical uplink control channel (PUCCH) transmission may take precedence over a physical uplink shared channel (PUSCH) transmission).

[0089] In addition, for mixed RAT deployments, it may be beneficial to implement carrier aggregation, where the same scheduling entity (e.g., the same medium access control (MAC) entity) schedules component carriers of different RATs. According to some aspects discussed herein, multi-RAT carrier aggregation techniques are discussed, where different component carriers (CCs) use different RATs. In some cases, a first CC (e.g., for a primary cell (PCell)) may be associated with a first RAT, and a second CC (e.g., for a secondary cell (SCell)) may be associated with a second RAT. In some cases, multiple bandwidth parts (BWPs) may be configured, and different BWPs may be associated with different RATs, such that a first CC may be configured for a first RAT or a second RAT based on the BWP of the carrier. In such cases, switching the first CC to a different BWP may thus switch the first CC between different RATs. In some cases, power control for each CC may be provided based on one or more of a service provided via the associated CC (e.g., based on an indicator associated with a service or priority), a waveform type of the associated CC, a channel type of the associated CC, or any combination thereof. Similarly, various carrier aggregation functions for CCs (e.g., uplink control information transmission, ACK / NACK feedback, resource scheduling, logical channel prioritization, UE capability reporting, discontinuous reception (DRX) configuration, or any combination thereof) may be provided for each RAT or may be multiplexed across RATs. Thus, various techniques as discussed herein may allow flexible scheduling of different devices, different services, or a combination thereof across different RATs using different carriers.

[0090] In further aspects, additionally or alternatively, multi-RAT mixed mode carrier aggregation and DC configuration may be implemented. In such aspects, a cell group with a DC configuration may include multiple different CCs in a carrier aggregation configuration, where different CCs may use different RATs. In some cases, similar to what is discussed above, different CCs may be associated with different RATs based on the BWP of the CCs. In some cases, the timing boundary between the first RAT and the second RAT may be synchronized, and the first RAT communications may be multiplexed with the second RAT communications on the same carrier.

[0091] Thus, the techniques discussed herein may allow concurrent communications at a UE with multiple RANs using different RATs. Such concurrent communications may use carrier aggregation, in which different RATs are used to provide different CCs, where one scheduling entity (e.g., a cloud-based scheduling entity that provides scheduling functionality for both 5G RAN and 6G RAN) controls scheduling decisions about a group of carriers (e.g., all aggregated CCs belong to the same medium access control (MAC) entity). Additionally or alternatively, such concurrent communications may use DC, which may be enabled with independent coordination of scheduling decisions about two groups of carriers (e.g., each cell group belongs to a different MAC entity). By providing the flexibility to communicate concurrently via multiple RATs, the techniques discussed herein may provide enhanced network efficiency and reliability, enhanced scheduling flexibility for network operators, and an enhanced user experience by providing service provision with enhanced throughput and reduced latency at different RANs.

[0092] Various aspects of the present disclosure are first described in the context of wireless communication systems. Various aspects of the present disclosure are further illustrated by and described with reference to process flows, device diagrams, system diagrams, and flow charts involving techniques for wireless communication using multiple RATs.

[0093] Figure 1 An example of a wireless communication system 100 that supports techniques for wireless communication using multiple RATs in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless 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 according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

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

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

[0098] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

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

[0100] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 can be 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 are performed by different ones of CU 160, DU 165, or RU 170). CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that communicate via such communication links.

[0101] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may 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 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports 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., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0102] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an 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, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol defining a signaling message (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0103] The IAB node 104 may refer to a RAN node that provides IAB functions (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node toward a child node associated with the IAB node 104, and the IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. That is, the IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay transmissions to the UE through one or more other IAB nodes 104). Additionally or alternatively, the IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and the DU interface (e.g., DU 165) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115.

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

[0105] Where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the techniques for wireless communications using multiple RATs as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

[0107] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115 which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

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

[0109] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified based on a channel raster used for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

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

[0111] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers for a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be capable of being configured to support communications using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0112] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a resource of a subcarrier, in which case the symbol period and the 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 coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high rate of communication. Wireless communication resources may refer to a combination of RF spectrum resources, time 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.

[0113] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0114] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, for which Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0115] 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, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further 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 in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of 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., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

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

[0117] According to various techniques, physical channels may be multiplexed using carriers for communication. Physical control channels and physical data channels may be multiplexed for signaling via downlink carriers, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to 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 cascaded manner. The aggregation level of a control channel candidate 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 sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

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

[0119] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to a UE 115 that has a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) than a macro cell, and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 that has a service subscription with a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0120] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0121] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different RATs.

[0122] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

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

[0124] In some examples, the UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (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 that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0125] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units) using vehicle-to-network (V2N) communications, or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170), or both.

[0126] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an 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), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0127] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about 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 may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0128] The wireless communication system 100 may also operate in an ultra-high frequency (SHF) region (also known as a centimeter band) that may be in the range of 3 GHz to 30 GHz or an extremely high frequency (EHF) region (also known as a millimeter band) that uses a spectrum (e.g., from 30 GHz to 300 GHz). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between a UE 115 and a network entity 105 (e.g., a base station 140, a RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be subject to even greater attenuation and a shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0129] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ licensed assisted access (LAA), LTE-unlicensed (LTE-U) RAT, or NR technology in an unlicensed band (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating using an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0130] The 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 technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0131] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include: single-user MIMO (SU-MIMO), for which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are sent to multiple devices.

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

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

[0134] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0135] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0136] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

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

[0138] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of data being successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0139] In some cases, the wireless communication system 100 may provide communications using two or more RATs. For example, one or more network entities 105 may provide communications for a first RAN using a first RAT, and one or more network entities 105 may provide communications for a second RAN using a second RAT. In some cases, one network entity 105 may provide communications for both the first RAN and the second RAN using a first RAT and a second RAT, respectively. In some cases, one or more UEs 115 may be able to communicate using both the first RAT and the second RAT, and in some cases may have concurrent connections via the two RATs. According to various aspects, techniques for DC, carrier aggregation, or both are provided, wherein different carriers are provided via different RATs. In some cases, a multi-RAT DC configuration may include a separate network entity 105 that provides communications for different cell groups of different RATs, wherein dynamic power control may be implemented across RATs. In some cases, power control signaling may be provided, indicating which RAT is preferentially used for power control. Additionally or alternatively, uplink power control may be based on prioritization of two or more services associated with different carriers of different network entities 105 (e.g., carriers with high priority transmissions are prioritized and receive full transmission power, and carriers providing lower priority transmissions have scaled power). In other cases, additionally or alternatively, carriers may be prioritized based on waveforms used for transmissions or based on channel type or content.

[0140] Additionally or alternatively, multi-RAT carrier aggregation may be used to communicate with one or more UEs 115, and the multi-RAT carrier aggregation configuration may include a single network entity 105 that provides scheduling for different CCs using different RATs. In some cases, a first CC (e.g., for a PCell) may be associated with a first RAT, and a second CC (e.g., for an SCell) may be associated with a second RAT. In some cases, multiple BWPs may be configured at the UE 115, and different BWPs may be associated with different RATs, such that a first CC may be configured for a first RAT or a second RAT based on a carrier's BWP. In such cases, switching the first CC to a different BWP may thus switch the first CC between different RATs. In some cases, power control may be provided for each CC based on one or more of a service provided via the associated CC (e.g., based on an indicator associated with a service or priority), a waveform type of the associated CC, a channel type of the associated CC, or any combination thereof. Similarly, various carrier aggregation functions for CCs (e.g., uplink control information transmission, ACK / NACK feedback, resource scheduling, logical channel prioritization, UE capability reporting, DRX configuration, or any combination thereof) may be provided for each RAT or may be multiplexed across RATs.

[0141] In further aspects, additionally or alternatively, multi-RAT mixed mode carrier aggregation and DC configuration may be implemented. In such aspects, a cell group with a DC configuration may include multiple different CCs in a carrier aggregation configuration, where different CCs may use different RATs. In some cases, similar to what is discussed above, different CCs may be associated with different RATs based on the BWP of the CCs. In some cases, the timing boundary between the first RAT and the second RAT may be synchronized, and the first RAT communications may be multiplexed with the second RAT communications on the same carrier.

[0142] Figure 2 An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with a core network 130-a through one or more disaggregated network entities 105 (e.g., a near-RT RIC 175-b via an E2 link, or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. The RU 170-a can be associated with a corresponding coverage area 110-a and can communicate with the UE 115-a via one or more communication links 125-a. In some implementations, the UE 115-a can be served by multiple RUs 170-a simultaneously.

[0143] Each network entity 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, the network entity 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to send signals to one or more of the other network entities 105 on a wireless transmission medium, or both.

[0144] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0145] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional divisions, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented with an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU160-a.

[0146] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable at least a portion of the DU 165-a and the CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture implemented in a service-based network 220).

[0147] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the virtualized network entity 105 may provide one or more services, core network, and RAN functions are merged so that the same entity can provide such functions. In some cases, upper layer scheduling functionality such as functions of DU 165-a and CU 160-a may be effectively implemented via software at a service-based network 220, which may provide a cloud virtualization entity 215 for one or more functions of CU 160-a and optionally DU 165-a, which may communicate with the service-based network 220 via a backhaul communication link 120-b. In addition, in some specific implementations, SMO 180-a, service-based network 220, or both may communicate with components of multiple different RANs (e.g., 5G RAN and 6G RAN) using different RATs. According to the techniques discussed herein, scheduling decisions across different network functionalities may be coordinated to provide multi-RAT carrier aggregation, multi-RAT dual connectivity, or both. For example, UE 115-a may be connected to RU 170-a with 5G capabilities and RU 170-a with 6G capabilities, which are effectively controlled by a single DU 165-a or coordinated DU 165-a. Furthermore, in some implementations, the SMO 180-a may communicate with components configured in accordance with the 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0148] The non-RT RIC 175-a may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

[0149] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 175-b and may be received from a non-network data source or from a network function at the SMO 180-a or the non-RT RIC 175. In some examples, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns of performance and employ an AI model or ML model to perform corrective actions through the SMO 180-a (e.g., via reconfiguration of O1) or via the generation of a RAN management policy (such as an A1 policy).

[0150] Figure 3 An example of a wireless communication system 300 that supports techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 300 can implement aspects of the wireless communication system 100. In this example, the wireless communication system 300 includes a network entity 105-a and a UE 115-b, which can be as described with respect to Figure 1 and Figure 2 Examples of corresponding devices discussed.

[0151] In this example, the network entity 105-a may provide scheduling functionality for a carrier aggregation configuration in which the UE 115-b may be configured with a first downlink CC 305 and a second downlink CC 310 and a first uplink CC 315 and a second uplink CC 320. Figure 3, two uplink CCs and two downlink CCs are illustrated, but it should be understood that the techniques discussed herein are applicable to any number of uplink CCs or downlink CCs, and the number of uplink CCs may be different from the number of downlink CCs. In some specific implementations, the first downlink CC 305 may be a PCell, and the first downlink CC 305 and the first uplink CC 315 may operate using a first RAT (e.g., 5G RAT), and the second downlink CC 310 and the second uplink CC 320 may be SCells operating using a second RAT (e.g., 6G RAT). Although each RAT has one uplink CC and one downlink CC in this example, in other cases, each RAT may have multiple uplink CCs and / or downlink CCs, and different RATs may have different numbers of uplink CCs and / or downlink CCs.

[0152] exist Figure 3 In an example of , the network entity 105-a may provide scheduling functionality for each CC. In some specific implementations, the network entity 105-a may include a cloud virtualization entity 215 and two or more RUs 170, wherein at least one RU provides communications for a first RAT and at least one RU provides communications for a second RAT. The network entity 105-a may provide a carrier aggregation configuration 325 to the UE 115-b via a first downlink CC 305, which may configure CCs 305-320 in the carrier aggregation configuration at the UE 115-b. According to various aspects discussed herein, the network entity 105-a may include a cloud virtualization entity or communicate with a cloud virtualization entity (e.g., via a fronthaul communication link 168), which may provide the same MAC entity that schedules each of the CCs 305-320. For example, the MAC entity may communicate with both the 5G RAN and the 6G RAN and may receive information for each RAN regarding the amount of data to be communicated between the UE 115-b and the network entity 105-a, one or more services associated with the data, or any combination thereof. The MAC entity may schedule communications via different CCs 305-320 based on the information. Figure 3 In the example illustrated in , a first downlink CC 305 may be used to schedule a first downlink transmission 330, a second downlink CC 310 may be used to schedule a second downlink transmission 335, a first uplink CC 315 may be used to schedule a first uplink transmission 340, and a second uplink CC 320 may be used to schedule a second uplink transmission 345.

[0153] In some cases, CCs 305-320 may be configured as a first cell group. In some cases, different carriers may be configured for carrier aggregation or DC based on whether upper layer functionality can be coordinated and the timeline for such coordination compared to the dynamic lower layer scheduling timeline. Figure 4 and Figure 5 The examples of DC configurations for different carriers or cell groups are discussed in more detail in the examples of . Carriers configured in different cell groups in a DC configuration have relatively little coordination, which in some cases can be configured or semi-statically configured (for example, for power control), and these carriers can have independent scheduling, where carriers of different DC cell groups have no scheduling dependencies. Therefore, in such DC configurations, except for power control in some cases, physical layer operations can be independent across cell groups. For power control across cell groups, there may be dependencies across groups depending on the operating mode, as shown in reference Figure 4 and Figure 5 In contrast, for an example such as Figure 3 In the carrier aggregation configuration illustrated in FIG. 1 , carriers using different RATs may be coordinated for scheduling and power control through a scheduling entity (eg, a MAC entity) that provides physical layer operations (eg, scheduling and power control operations) for both RATs.

[0154] In another example discussed herein, a mixed mode carrier aggregation / DC operation may be implemented, wherein operation is performed according to a carrier aggregation configuration if the coordination timeline between the RATs is faster than or similar to the scheduling timeline of the data to be communicated, and wherein operation is also performed according to a DC configuration. In such mixed mode operation, DC or carrier aggregation operation across carriers may depend on the specific services or operations of the different carriers, the corresponding timelines of the different carriers, and how closely the scheduling entity can coordinate the scheduling of the different RATs. In some cases, the relationship between the coordination timeline and the scheduling timeline may be service-dependent or operation-dependent (e.g., a delay-insensitive eMBB service may tolerate longer delays until a scheduling coordination message is available, and thus carrier aggregation operation may be implemented, while a URLLC service may be delay-intolerant, resulting in tighter scheduling coordination to implement the timeline, and thus DC operation may be implemented when one or more carriers have associated service priorities corresponding to URLLC).

[0155] refer to Figure 3In the carrier aggregation configuration 325, the network entity 105-a may have an associated scheduling entity that is capable of coordinating scheduling across the two RATs within a scheduling timeline associated with the services provided by each RAT. In some cases, the carrier aggregation configuration 325 may provide information for each CC 305-320 indicating which RAT to use. In other cases, the carrier aggregation configuration 325 may provide a BWP-level configuration, where different BWPs are associated with different RATs, and whether the CC 305-320 uses the first RAT or the second RAT depends on which BWP the CC 305-320 is configured with. Thus, in this example, the first downlink CC 305 and the first uplink CC 315 may each be associated with a BWP configured for the first RAT, and the second downlink CC 310 and the second uplink CC 320 may each be associated with a BWP configured for the second RAT. Such a BWP-based configuration may provide a flexible way to switch carriers back and forth across RATs as needed, and may provide additional flexibility to the scheduler based on a specific mix of data to be sent at different points in time. In other cases, the configuration of CCs 305-320 utilizing the corresponding RAT may be provided via control information (e.g., via a physical downlink control channel (PDCCH)), via a control resource set (CORESET), via downlink control information (DCI), or any combination thereof. In some cases, the configuration via PDCCH / CORESET / DCI may be provided on a shared carrier, where some physical layer channels (e.g., PDDCH) may follow a structure for one RAT (e.g., a 5G physical channel structure), and other physical layer channels may follow a structure for a different RAT.

[0156] In some implementations, uplink power control for the first uplink CC 315 and the second uplink CC 320 can be provided, wherein the total available power amount (e.g., P) can be allocated between the carriers based at least in part on one or more of a configured allocation, a priority associated with a corresponding RAT, a service type of the communication (e.g., based on an indicator associated with a service provided with scheduling information for the communication), a priority of the service of each carrier (e.g., based on an indicator of the priority provided with scheduling information for the communication), a channel type and content of data to be sent on each carrier, a waveform used by each carrier, or any combination thereof. CMAX). This may be accomplished similarly to 5G CA power control; additional aspects provided for the last power control option for DC in the previous slide may also be considered. For example, a first uplink power for the first uplink CC 315 may be determined based on the first uplink CC 315 having a higher priority communication than the second uplink CC 320 (e.g., a communication with a high priority indication such as associated with URLLC communication), and a second uplink power for the second uplink CC 320 may be scaled based on the first uplink power and the total amount of available uplink power available for the aggregated carriers. In addition, in some cases, the scheduling entity may identify a period of time when both uplink data and downlink data are present, and uplink / downlink prioritization for conflict resolution of scheduling uplink or downlink may be based at least in part on parameters associated with each carrier, such as the RAT, service type, priority of communication, channel type (e.g., PUCCH or PUSCH) and content (e.g., ACK / NACK indication, measurement report, etc.), waveform, or any combination thereof. In some cases, the scheduling entity may perform such conflict resolution based on one or more parameters and allocate resources to CCs 305-320 accordingly.

[0157] In some cases, UE 115-b may send feedback information, such as HARQ ACK / NACK feedback, where such feedback information may be determined for both RATs based on associated communications for each respective RAT. In some cases, the feedback information may be provided for each RAT (e.g., separate feedback information is provided for each RAT), or may be multiplexed across RATs (e.g., a single feedback information transmission may include HARQ ACK / NACK information for both RATs). In some cases, whether the feedback information is provided separately for each RAT or multiplexed across RATs may be based at least in part on a codebook type of the feedback information (e.g., a HARQ codebook used to provide the feedback information), a waveform and format of a channel carrying the feedback information, a priority of associated communications, services provided by each RAT, or any combination thereof. For example, both RATs may provide lower priority communications (e.g., eMBB communications) and feedback information may be provided in a multiplexed manner, or one RAT may provide higher priority communications (e.g., URLLC communications) and feedback information may be provided separately for each RAT. Additionally or alternatively, based on the same considerations as discussed with respect to feedback information, data, uplink control information, or both may be multiplexed or provided separately for each RAT.

[0158] In some implementations, the triggering events for various different operations may be per-RAT triggering events or cross-RAT triggering events. For example, a sounding reference signal (SRS) may be triggered by a per-RAT trigger (e.g., triggering the SRS for each RAT separately) or a cross-RAT trigger (e.g., a trigger received on one RAT indicates that the SRS is to be sent on both RATs, or a trigger received from one RAT may indicate that the SRS is to be sent on another RAT). Similarly, other triggering events may be per-RAT or cross-RAT, such as SCell activation or deactivation, semi-persistent scheduling (SPS) activation or deactivation, configuration grant (CG) uplink transmission activation or deactivation, power saving indication (e.g., PDCCH skipping, sleep operation, wake-up signal (WUS)), or any combination thereof. For example, in the case where a cross-RAT triggering event is configured, DCI activation or deactivation operations for both 5G and 6G carriers or BWPs may be provided from a 6G carrier or BWP. In some cases, the cross-RAT trigger may be joint (e.g., a trigger on a 5G carrier may indicate behavior / operation that applies to both 5G and 6G carriers / BWPs) or separate (e.g., a trigger on a 5G carrier indicates behavior / operation for a 6G carrier). In other examples, a trigger may be provided for each RAT rather than for each carrier (e.g., all carriers or BWPs associated with a RAT may have an event triggered by a single trigger event for that RAT). In still other examples, a WUS may wake up the UE 115-b, or a go-to-sleep (GTS) indication may trigger a low power mode on all carriers regardless of the associated RAT, or a subset of carriers of the same, different, or both RATs. In some cases, a per-RAT or cross-RAT trigger event may apply regardless of the trigger container (e.g., DCI or MAC-CE) that provides the associated trigger, or a per-RAT or cross-RAT trigger event may depend on the type of container (e.g., a trigger event provided via a DCI is per-RAT, and a trigger event provided via a MAC-CE is cross-RAT).

[0159] In some cases, UE 115-b may send a request for uplink resources in a scheduling request (SR) communication. In some specific implementations, the SR may provide a request for uplink resources for each RAT or across RATs. For example, an SR for 5G (e.g., provided via the first uplink CC 315) may indicate a request for 5G uplink resources, and an SR for 6G (e.g., provided via the second uplink CC 320) may indicate a request for 6G uplink resources. In other cases, a shared SR may indicate a request for 5G or 6G uplink resources, and the scheduling entity may provide resource allocation based on which RAT will provide the most efficient communication (e.g., based on load balancing between uplink carriers, transmit power associated with the uplink carriers, priority of associated communications or services, etc.). In some cases, cross-carrier or cross-BWP scheduling may be provided for each RAT or across RATs.

[0160] In some implementations, at the MAC layer, logical channel (LCH) prioritization may explicitly or implicitly (e.g., via waveform type) take into account the associated RAT, and a logical channel may be associated with only one RAT or multiple RATs (e.g., only 5G, only 6G, or both). In some cases, logical channels may be associated with different services (e.g., 5G sensing vs. 6GML measurement / data delivery), and prioritization may be based on the associated services. In some cases, the mapping of data from LCH to physical layer channels may be separate for each RAT, or may apply across RATs.

[0161] In some implementations, the UE 115-b may report one or more capabilities to the network entity 105-a, and the capability report may be per RAT or cross-RAT. Furthermore, in some cases, a first subset of features may be reported for each RAT, while a second subset of features may be reported across RATs. For example, the UE 115-b may provide a capability report indicating support for feature X of 5G, support for feature X of 6G, and support for feature X of 5G+6G. The scheduling entity may then schedule communications based on the reported capabilities of the UE 115-b.

[0162] In some implementations, a discontinuous reception (DRX) procedure may be configured per RAT or across RATs. In the case where DRX is configured across RATs and in the case where multiple DRX configurations are allowed, each DRX group may have carriers from one RAT or both RATs.

[0163] Figure 4Another example of a wireless communication system 400 that supports techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 400 can implement aspects of the wireless communication system 100 or 300. In this example, the wireless communication system 400 includes a first network entity 105-b, a second network entity 105-c, and a UE 115-c, which can be as shown with respect to Figures 1 to 3 Examples of corresponding devices discussed.

[0164] In this example, the first network entity 105-b may provide services for a first group of cells including a first downlink carrier 405 and a first uplink carrier 410. According to the DC configuration 425, the second network entity 105-c may provide services for a second group of cells including a second downlink carrier 415 and a second uplink carrier 420. In some cases, separate scheduling entities (e.g., separate MAC entities associated with the first network entity 105-b and the second network entity 105-c) may provide scheduling functions for the first group of cells and the second group of cells. Figure 4 4 illustrates one uplink carrier and one downlink carrier for each cell group, but it should be understood that the techniques discussed herein are applicable to any number of uplink carriers or downlink carriers for each cell group. In some implementations, the first downlink carrier 405 and the first uplink carrier 410 may operate using a first RAT (e.g., 5G RAT), and the second downlink carrier 415 and the second uplink carrier 420 may operate using a second RAT (e.g., 6G RAT).

[0165] As indicated, in this example, a separate scheduling entity may provide scheduling functionality for each cell group. Figure 3As discussed, the scheduling entity may include a cloud virtualization entity 215 and two or more RUs 170, wherein at least one RU provides communications for a first RAT and at least one RU provides communications for a second RAT. However, in this example, the scheduling entity may not be able to provide coordination of scheduling that meets the timelines of different RATs to support carrier aggregation for carriers of each cell group, and the DC configuration 425 may indicate a separate cell group. Therefore, in such cases, the same MAC entity may provide scheduling for each cell group, and may provide scheduling information separately for each of the first network entity 105-b and the second network entity 105-c. One or more MAC entities may schedule communications via different carriers 405-320, which may include a first downlink transmission 430 using a first downlink carrier 405, a first uplink transmission 435 using a first uplink carrier 410, a second downlink transmission 440 using a second downlink carrier 415, and a second uplink transmission 445 using a second uplink carrier 420.

[0166] According to various aspects discussed herein, power control techniques for DC configuration can be provided for different cell groups associated with different RATs. Such power control techniques may include dynamic power control or semi-static power control. In some implementations, semi-static power control can be implemented across cell groups, where a maximum transmit power for each cell group is provided such that the total transmit power does not exceed a maximum transmit power supported by the UE 115-c (e.g., P CG1 +P CG2 ≤Ptot), and power control is performed independently across the cell groups based on the associated maximum transmit power of the cell group. In a specific implementation using dynamic power control, one carrier or cell group may be identified as having priority and may receive a transmit power corresponding to the calculated transmit power, and the transmit power of another carrier or cell group may be scaled down to provide a total transmit power that does not exceed the maximum transmit power of the UE 115-c. In some cases, carriers or cell groups may be identified as having priority based on a timeline associated with the communication. For example, where one cell group (e.g., a cell group associated with a 4G RAT having an n+4 timeline between a grant to receive in subframe n and a transmission in subframe n+4) always has a longer timeline than another cell group (e.g., a cell group associated with a 5G RAT having a configurable N1 / N2 processing time that is always shorter than the n+4 timeline), the cell group with the longer timeline may use the calculated transmit power, and when the total power would exceed the maximum transmit power of the UE 115-c, the other cell group may have a scaled down transmit power.

[0167] In other cases, such as where the first cell group is associated with a 5G RAT and the second cell group is associated with a 6G RAT, the associated timeline of one cell group may not always be longer than the timeline of the other cell group. For example, communications using the first cell group may be associated with higher priority transmissions (e.g., URLLC communications) than communications using the second cell group (e.g., eMBB communications), and the timeline of the first cell group may be shorter than the timeline of the second cell group (e.g., the N1 / N2 processing time of high priority communications of the first RAT may be shorter than the N1 / N2 processing time of lower priority communications of the second RAT). However, in other cases, the second cell group may be associated with higher priority communications than the first cell group and may have a corresponding timeline that is shorter than the timeline of the first cell group. Therefore, it may not be desirable to always limit the transmit power of one RAT to favor another RAT.

[0168] In some implementations, dynamic power control of a first cell group and a second cell group may be used, wherein one cell group always takes precedence over the other cell group. For example, a 5G cell group may take precedence over a 6G cell group, or vice versa. In some cases, a cell group may be prioritized based on the expected service and associated requirements. In other implementations, dynamic power control may provide priorities for different carriers based on use cases, priorities, services, or any combination thereof. In such implementations, power scaling is not necessarily for a cell group, but actual services may be considered. For example, a 5G high priority transmission (e.g., URLLC) may have a higher priority than a 6G low priority transmission (e.g., eMBB); or a data transmission may have a higher priority than a transmission for positioning or sensing. Many other examples for prioritization may be used for dynamic power control, and these described examples are provided for the purpose of discussion and illustration. In some cases, the priority may be visible to the physical layer, or may depend on a logical channel in the MAC layer. In some cases, additionally or alternatively, prioritization may be based on waveform type, where some services may be implicitly tied to a particular waveform (e.g., CP-OFDM for data may have a higher priority than frequency modulated continuous wave (FMCW) for sensing). In other cases, additionally or alternatively, channel type (e.g., PUSCH or PUCCH), communication content, or any combination thereof may be used to determine the prioritization of cell groups or carriers.

[0169] Figure 5Another example of a wireless communication system 500 that supports techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 500 can implement aspects of the wireless communication systems 100, 300, or 400. In this example, the wireless communication system 500 includes a first network entity 105-d, a second network entity 105-e, and a UE 115-d, which can be as shown with respect to Figures 1 to 4 Examples of corresponding devices discussed.

[0170] In this example, the first network entity 105-d may provide services for the first cell group 505, and the second network entity 105-e may provide services for the second cell group 510. In this example, the first cell group 505 may have a carrier aggregation configuration including a first downlink CC 515-a, a second downlink CC 515-b, a first uplink CC 520-a, and a second uplink CC 520-b. According to the DC configuration, the second network entity 105-e may provide services for the second cell group 510 including a third downlink CC 525-a, a fourth downlink CC 525-b, a third uplink CC 530-a, and a fourth uplink CC 530-b. In some cases, different carriers within each cell group 505 and 510 may be associated with different RATs. For example, a first downlink CC 515-a and a first uplink CC 520-a may be provided using a first RAT (e.g., 5G RAT), and a second downlink CC 515-b and a second uplink CC 520-b may be provided using a second RAT (e.g., 6G RAT). Thus, the wireless communication system 500 of this example may provide a mixed mode carrier aggregation and dual connectivity configuration.

[0171] In some implementations, in this hybrid mode configuration, the UE 115-d and the network entity 105 may perform some operations using carrier aggregation techniques and perform other operations using DC techniques. For example, in traditional carrier aggregation, a group of carriers may be semi-statically aggregated according to a carrier aggregation configuration. Similarly, in a traditional DC configuration, two groups of independent carriers may be semi-statically configured, and within each group, carriers may be aggregated according to carrier aggregation techniques. According to some aspects, Figure 5The hybrid mode configuration illustrated in the example may provide a flexible and dynamically changeable cell group. In some implementations, transmission or reception for the first RAT or the second RAT may be indicated to the UE 115-d based on the carrier or BWP configuration. In some cases, a carrier or BWP of the first RAT and a carrier or BWP of the second RAT may be included in the first cell group 505 or the second cell group 510 based at least in part on one or more parameters associated therewith, such as the physical layer characteristics discussed herein (e.g., associated priority or service, etc.).

[0172] For example, four carriers may be provided, of which two are provided using a first RAT (e.g., CC0 and CC1 are 5G carriers), and the other two are provided using a second RAT (e.g., CC2 and CC3 are 6G carriers). In this configuration, a first time slot with a lower priority transmission (e.g., eMBB) may be scheduled on all four carriers, and in this case, the UE 115-d may treat these carriers as aggregated and perform HARQ feedback, multiplexing, prioritization, power control, etc. based on carrier aggregation. In a second time slot, one CC (e.g., CC2) may be scheduled with a high priority communication (e.g., 6G URLLC communication), and the remaining CCs (e.g., CC0, CC1, CC3) may be scheduled with a lower priority communication (e.g., eMBB communication). In this case, CC0, CC1, and CC3 may be considered to be in a first cell group 505, and CC2 may be considered to be in a separate second cell group 510. In this case, DC is used across both groups, and carrier aggregation is used across CC0, CC1, and CC3 (e.g., power control across CC0 / CC1 / CC3 and CC2 is based on the mode adopted for DC). Although this example illustrates cell grouping according to different services, such cell grouping may also be performed based on different physical layer or MAC layer indications, channels, or content. In some cases, this hybrid mode may be provided based on whether the schedulers for each RAT are able to coordinate their transmissions closely enough to provide carrier aggregation (in which case DC may be used), which may depend on how fast the coordination is relative to the overall latency requirements of the packets sent. For example, for eMBB and URLLC, the scheduler may be able to coordinate in a manner similar to carrier aggregation for sending eMBB packets (e.g., which is more tolerant of delays), but may not be able to coordinate as quickly as required for URLLC.

[0173] In another specific implementation, the multi-RAT based BWP switching can be combined with Figures 3 to 5In such cases, different BWPs may be used to provide different services (e.g., 6G eMBB data, 5G URLLC, 5G sidelink, narrowband IoT, etc.), and different services may be enabled for the same UE 115 on the same CC in a TDM manner, or different services may be enabled concurrently on different CCs. In some cases, BWP switching for a CC (e.g., CC-based services) may indicate an inter-RAT switching. Additionally, in some implementations, multi-RAT synchronous DC (SDC) may be configured, where inter-RAT switching for one or more carriers may be based on a time domain cycle. In such cases, timing synchronization may be provided (e.g., until symbol boundaries), and multiple different cells that may be used to provide services to the UE may have such timing synchronization. When synchronization across carriers of different RATs is available (e.g., 5G / 6G synchronization until symbol boundaries), the slot boundaries may be aligned (e.g., using some UE assistance to feedback different timing advance (TA) values). In such cases, although universal scheduling may not be provided, conflicts between RATs may be avoided via slot pre-scheduling across RATs. For example, for a certain number of time slots (e.g., every 10 time slots), the two RATs may determine a scheduling pattern in these time slots (e.g., for 10 time slots, the scheduling pattern may be 5G, 5G, 5G, 6G, 6G, 5G, 5G, 5G, 6G, 6G). In some cases, the time slot scheduling may be based on the buffer status on each RAT, the corresponding TDD time slot pattern, fairness, one or more predetermined rules, or any combination thereof. In some cases, the mode may be signaled to the UE (e.g., via DCI, one or more MAC-CEs, RRC signaling, or other sequence-based DL control) to help the UE decode the corresponding grant. Such a pattern may be provided to indicate which RAT may potentially be used for downlink and uplink communications on a set of time domain resources (e.g., at the time slot or symbol level), which may be applicable to both intra-band and inter-band SDC cases. In some cases, the pattern may also be applied to the downlink when both RATs are in the same carrier or the downlink throughput envelope is to be shared across the two RATs. In addition or in lieu of time domain pre-scheduling, pre-scheduling in the frequency domain, spatial domain, or both may be performed.In some cases, such a pre-scheduling mechanism may be used for spectrum sharing across different network operators, where partitions are provided to different operators based on load, for example.

[0174] Figure 6 An example of a process flow 600 for supporting techniques for wireless communication using multiple RATs in accordance with one or more aspects of the present disclosure is illustrated. In some examples, the process flow 600 may implement aspects of the wireless communication system 100, 300, 400, or 500. The process flow 600 may include a network entity 105-f and a UE 115-e, which may be reference Figures 1 to 5 An example of a corresponding device as described. In this example, the network entity 105-f may provide a carrier aggregation configuration in which different CCs are provided using different RATs, as discussed herein. The following alternative examples may be implemented, in which some of the steps are performed in a different order than described or not performed at all. In some cases, the operations may include additional features not mentioned below, or additional operations may be added.

[0175] At 605, the UE 115-e and the network entity 105-f may establish a connection. The connection may be established according to established techniques, such as RRC connection establishment techniques. In some cases, as part of the connection establishment or independently of the connection establishment, the UE 115-e may provide capability information to the network entity 105-f, which may indicate capabilities for multi-RAT carrier aggregation or multi-RAT DC or both.

[0176] At 610, the network entity 105-f may determine a multi-RAT carrier aggregation configuration for the UE 115-b. In some cases, as discussed herein, the carrier aggregation configuration provides for one or more CCs that use a first RAT and one or more other CCs that use a second RAT. In some cases, the multi-RAT carrier aggregation configuration may be determined based on a scheduling entity associated with the network entity 105-f being able to coordinate scheduling of each CC that uses a different RAT in the multi-RAT carrier aggregation configuration.

[0177] In some cases, at 615, the network entity 105-f may optionally determine a BWP configuration and a RAT associated with each BWP. For example, a first BWP configuration may be associated with a first RAT and a second BWP configuration may be associated with a second RAT, so a CC configured for the first BWP may use the first RAT and a CC configured for the second BWP may use the second RAT. In addition, a CC using the first RAT and the first BWP may be switched to use the second BWP, which may also indicate that the CC will switch from the first RAT to the second RAT. Optionally, at 620, the network entity 105-f may determine a CORESET configuration and a RAT associated with each CORESET, and may configure the CC for different RATs based on the associated CORESET.

[0178] At 625, the network entity 105-f may send a carrier aggregation configuration, which may be received at the UE 115-e. Based on the carrier aggregation configuration, the UE 115-e may configure multiple CCs according to the carrier aggregation configuration, wherein one or more CCs use a first RAT and one or more UEs use a second RAT. At 630, a scheduling entity associated with the network entity 105-f (e.g., a MAC entity that provides scheduling for both the first RAT and the second RAT) may allocate resources for communication across the configured CCs. At 635, the network entity 105-f may send scheduling information to the UE 115-e indicating the resources allocated for the CCs.

[0179] At 640, the UE 115-d may determine the CCs and the RAT for each CC based at least in part on the carrier aggregation configuration and the scheduling information. In some cases, the RAT associated with each CC may be determined based on a BWP for each CC, which may be indicated in the scheduling information, in the carrier aggregation configuration, or in both. In some cases, the RAT associated with each CC may be based on a priority of communications associated with each CC, a waveform type associated with each CC, a service type associated with each CC, content of data sent on each CC, a channel type associated with each CC, or any combination thereof.

[0180] At 645, the UE 115-e may optionally determine an uplink transmit power for each CC based on a priority associated with each CC, provided uplink resource allocations. In some cases, the uplink transmit power may be dynamically determined based on a priority of communications associated with each CC, a waveform type associated with each CC, a service type associated with each CC, content of data transmitted on each CC, a channel type associated with each CC, or any combination thereof. At 650, the UE 115-e and the network entity 105-f may send and receive uplink communications and downlink communications on multiple CCs in accordance with the carrier aggregation configuration and scheduling information.

[0181] Figure 7 An example of a process flow 700 for supporting techniques for wireless communication using multiple RATs in accordance with one or more aspects of the present disclosure is illustrated. In some examples, the process flow 700 can implement aspects of the wireless communication system 100, 300, 400, or 500. The process flow 700 can include a first network entity 105-g, a second network entity 105-h, and a UE 115-f, which can be reference Figures 1 to 6An example of a corresponding device as described. In this example, the network entity 105 may provide a DC configuration in which one or more carriers of different cell groups are provided using different RATs, as discussed herein. The following alternative examples may be implemented, in which some of the steps are performed in a different order than described or not performed at all. In some cases, the operations may include additional features not mentioned below, or additional operations may be added.

[0182] At 705, the first network entity 105-g and the second network entity 105-h may determine a cell group configuration for DC communication. In some cases, a scheduling entity (e.g., the same MAC entity) may be associated with the first network entity 105-g and the second network entity 105-h and may determine that a plurality of cell groups are to be established using a DC configuration. In some cases, the same scheduling entity may make such a determination. In other cases, a separate scheduling entity may be associated with each RAT. At 710, the first network entity 105-g may send the DC configuration information to the UE 115-f.

[0183] At 715, the first network entity 105-g may determine uplink power control for uplink transmissions of the UE 115-f based on the DC configuration. At 720, the first network entity 105-g may send power control information to the UE 115-f (e.g., along with an uplink resource allocation for uplink transmissions to the first network entity 105-g). In some cases, the second network entity 105-h may also determine to send power control information and provide scheduling information for communicating with the second network entity 105-h.

[0184] At 725, the first network entity 105-g may allocate resources for a first cell group associated with the first network entity 105-g. At 730, the first network entity 105-g may send scheduling information for the first cell group to the UE 115-f. At 735, the second network entity 105-h may allocate resources for a second cell group associated with the second network entity 105-h. At 740, the second network entity 105-h may send scheduling information for the second cell group to the UE 115-f.

[0185] At 745, the UE 115-f may determine the carriers and the RATs associated with the carriers based on the cell group information in the DC configuration. At 750, the UE 115-f may determine the uplink transmit power for each carrier and each cell group according to the techniques as discussed herein (e.g., based at least in part on the priority, power control information, and scheduling information associated with the cell group). At 755, the UE 115-f and the first network entity 105-g may send and receive uplink communications and downlink communications based on the DC configuration, the scheduling information, and the determined transmit power. Similarly, at 760, the UE 115-f and the second network entity 105-h may send and receive uplink communications and downlink communications based on the DC configuration, the scheduling information, and the determined transmit power.

[0186] Figure 8 An example of a process flow 800 for supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 800 can implement aspects of the wireless communication system 100, 300, 400, or 500. The process flow 800 may include a first network entity 105-i, a second network entity 105-j, and a UE 115-g, which may be reference Figures 1 to 7 An example of a corresponding device as described. In this example, the network entity 105 may provide a multi-RAT communication configuration in which different RATs may be multiplexed on one or more carriers of one or more cell groups, as discussed herein. The following alternative examples may be implemented, in which some of the steps are performed in a different order than described or not performed at all. In some cases, the operations may include additional features not mentioned below, or additional operations may be added.

[0187] At 805, the first network entity 105-i and the second network entity 105-j may determine a cell group configuration and a RAT multiplexing configuration for DC communication. In some cases, a scheduling entity (e.g., the same MAC entity) may be associated with the first network entity 105-i and the second network entity 105-j, and may determine that multiple RATs may be used for communication with the UE 115-g. As discussed herein, in some cases, a first RAT may be used for communication at the first network entity 105-i, and a second RAT may be used for communication at the second network entity 105-j. In addition, time boundaries (e.g., time slot boundaries) for communication using the first RAT and the second RAT may be synchronized, and a multiplexing pattern of one or more carriers may be determined, wherein a subset of resources of the carrier is used for the first RAT and a different subset of resources of the carrier is used for the second RAT. In some cases, the same scheduling entity may make such a determination. In other cases, a separate scheduling entity may be associated with each RAT. At 810, the first network entity 105-i may send carrier configuration information to the UE 115-g.

[0188] At 815, the first network entity 105-i may allocate resources for a carrier in which communications of the first RAT are multiplexed with communications of the second RAT. At 820, the first network entity 105-i may send scheduling information for the first RAT to the UE 115-g. In some cases, the scheduling information may indicate a subset of resources of the carrier that includes communications of the first RAT. At 825, the second network entity 105-j may allocate resources for a carrier in which communications of the second RAT are multiplexed with communications of the first RAT. At 830, the second network entity 105-j may send scheduling information for the second RAT to the UE 115-g. In some cases, the scheduling information may indicate a subset of resources of the carrier that includes communications of the second RAT.

[0189] At 835, the UE 115-g may determine a carrier (and optionally one or more other carriers) for communication and a RAT multiplexing associated with the carrier based on the carrier configuration information and the scheduling information. At 840, the UE 115-g may determine multiplexing resources associated with each RAT. At 845, the UE 115-g and the first network entity 105-i may send and receive uplink communications and downlink communications based on the RAT multiplexing on the carrier. Similarly, at 850, the UE 115-g and the second network entity 105-j may send and receive uplink communications and downlink communications based on the RAT multiplexing on the carrier.

[0190] Fig. 9A block diagram 900 of a device 905 supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0191] The receiver 910 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to technologies for wireless communication using multiple RATs), user data, control information, or any combination thereof. The information may be communicated to other components of the device 905. The receiver 910 may utilize a single antenna or a collection of multiple antennas.

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

[0193] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the techniques for wireless communication using multiple RATs as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

[0194] In some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0195] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0196] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated in conjunction with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0197] According to examples as disclosed herein, the communication manager 920 may support wireless communications at the UE. For example, the communication manager 920 may be configured to or otherwise support components for receiving carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first RAT and the secondary component carrier uses a second RAT. The communication manager 920 may be configured to or otherwise support components for communicating with a first RAN using the primary component carrier and communicating with a second RAN using the secondary component carrier based on the carrier aggregation configuration information.

[0198] Additionally or alternatively, according to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. For example, the communication manager 920 may be configured to or otherwise support components for receiving DC configuration information for a first cell group and a second cell group, wherein the first cell group is served using one or more carriers using a first RAT and the second cell group is served using one or more carriers using a second RAT, and wherein different network entities provide physical layer scheduling information for the first cell group and the second cell group. The communication manager 920 may be configured to or otherwise support components for receiving uplink power control information, the uplink power control information including an indication of a first uplink transmit power for a first uplink transmission and a second uplink transmit power for a second uplink transmission, the first uplink transmit power and the second uplink transmit power being indicated as being preferentially used for uplink power control based on which of the first carrier of the first cell group or the second carrier of the second cell group is indicated. The communications manager 920 may be configured or otherwise support components for sending a first uplink transmission using a first carrier concurrently with sending a second uplink transmission using a second carrier, the first uplink transmission using a first uplink transmit power and the second uplink transmission using a second uplink transmit power.

[0199] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at the UE. For example, the communication manager 920 may be configured to or otherwise support components for receiving DC configuration information for a first cell and a second cell, wherein the first cell is associated with a first carrier using a first RAT, and the second cell is associated with a second carrier using a second RAT, and wherein the first carrier and the second carrier share the same set of wireless resources multiplexed between the first cell and the second cell in a time interval synchronized between the first RAT and the second RAT. The communication manager 920 may be configured to or otherwise support components for communicating with a first RAN using a first carrier and communicating with a second RAN using a second carrier based on a multiplexing configuration indicated in the DC configuration information.

[0200] By including or configuring the communication manager 920 according to the examples described herein, the device 905 (e.g., a processor controlling the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof or otherwise coupled thereto) can support techniques for multi-RAT DC communication, carrier aggregation communication, or a combination thereof, wherein scheduling flexibility for communication using different RATs can be provided through different carriers that can be associated with different RATs. Such techniques can provide more efficient resource utilization, enhanced throughput, and enhanced communication reliability, as well as network scheduling flexibility for communication using different RATs.

[0201] Fig.10 A block diagram 1000 of a device 1005 supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or UE 115 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0202] The receiver 1010 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to technologies for wireless communication using multiple RATs), user data, control information, or any combination thereof. The information may be communicated to other components of the device 1005. The receiver 1010 may utilize a single antenna or a collection of multiple antennas.

[0203] The transmitter 1015 may provide means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to techniques for wireless communication using multiple RATs), user data, control information, or any combination thereof. In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0204] The device 1005 or its various components may be examples of components for performing various aspects of the techniques for wireless communication using multiple RATs as described herein. For example, the communication manager 1020 may include a CA configuration manager 1025, a multi-RAT CA communication manager 1030, a DC configuration manager 1035, a transmit power manager 1040, a DC scheduling manager 1045, or any combination thereof. The communication manager 1020 may be an example of various aspects of the communication manager 920 as described herein. In some examples, the communication manager 1020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 1010, the transmitter 1015, or both. For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or be integrated with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0205] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a UE. The CA configuration manager 1025 may be configured to or otherwise support components for receiving carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first RAT and the secondary component carrier uses a second RAT. The multi-RAT CA communication manager 1030 may be configured to or otherwise support components for communicating with a first RAN using the primary component carrier and communicating with a second RAN using the secondary component carrier based on the carrier aggregation configuration information.

[0206] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at the UE. The DC configuration manager 1035 may be configured to or otherwise support components for receiving DC configuration information for a first cell group and a second cell group, wherein the first cell group is served using one or more carriers employing a first RAT and the second cell group is served using one or more carriers employing a second RAT, and wherein different network entities provide physical layer scheduling information for the first cell group and the second cell group. The transmit power manager 1040 may be configured to or otherwise support components for receiving uplink power control information, the uplink power control information including an indication of a first uplink transmit power for a first uplink transmission and a second uplink transmit power for a second uplink transmission, the first uplink transmit power and the second uplink transmit power being indicated as being prioritized for uplink power control based on which of the first carrier of the first cell group or the second carrier of the second cell group is indicated as being prioritized for uplink power control. The DC scheduling manager 1045 may be configured or otherwise support components for sending a first uplink transmission using a first carrier concurrently with sending a second uplink transmission using a second carrier, the first uplink transmission using a first uplink transmission power and the second uplink transmission using a second uplink transmission power.

[0207] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at the UE. The DC configuration manager 1035 may be configured to or otherwise support components for receiving DC configuration information for a first cell and a second cell, wherein the first cell is associated with a first carrier using a first RAT, and the second cell is associated with a second carrier using a second RAT, and wherein the first carrier and the second carrier share the same set of radio resources multiplexed between the first cell and the second cell in a time interval synchronized between the first RAT and the second RAT. The DC scheduling manager 1045 may be configured to or otherwise support components for communicating with a first RAN using a first carrier and communicating with a second RAN using a second carrier based on a multiplexing configuration indicated in the DC configuration information.

[0208] Fig.11 A block diagram 1100 of a communication manager 1120 supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of the techniques for wireless communication using multiple RATs as described herein. For example, the communication manager 1120 may include a CA configuration manager 1125, a multi-RAT CA communication manager 1130, a DC configuration manager 1135, a transmit power manager 1140, a DC scheduling manager 1145, a BWP manager 1150, a CORESET manager 1155, a UL / DL prioritization manager 1160, an SR manager 1165, a DRX manager 1170, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0209] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a UE. The CA configuration manager 1125 may be configured to or otherwise support components for receiving carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first RAT and the secondary component carrier uses a second RAT. The multi-RAT CA communication manager 1130 may be configured to or otherwise support components for communicating with a first RAN using the primary component carrier and communicating with a second RAN using the secondary component carrier based on the carrier aggregation configuration information. In some examples, the first RAT is a fifth generation (5G) RAT and the second RAT is a sixth generation (6G) RAT, and wherein the same network entity provides physical layer scheduling information for both the primary component carrier and the secondary component carrier.

[0210] In some examples, to support receiving carrier aggregation configuration information, the BWP manager 1150 may be configured to or otherwise support components for receiving bandwidth portion configurations for a set of multiple bandwidth portions of a channel bandwidth, on which a primary component carrier, a secondary component carrier, or both can be configured to operate. In some examples, to support receiving carrier aggregation configuration information, the BWP manager 1150 may be configured to or otherwise support components for a set of multiple bandwidth portions where a first bandwidth portion in the set of multiple bandwidth portions is associated with a first RAT and a second bandwidth portion in the set of multiple bandwidth portions is associated with a second RAT. In some examples, to support receiving carrier aggregation configuration information, the BWP manager 1150 may be configured to or otherwise support components for a set of multiple bandwidth portions where a primary component carrier is associated with a first RAT based on being configured with the first bandwidth portion and a secondary component carrier is associated with a second RAT based on being configured with the second bandwidth portion.

[0211] In some examples, to support receiving carrier aggregation configuration information, CORESET manager 1155 may be configured or otherwise support means for receiving an indication of which of the first RAT or the second RAT is associated with the primary component carrier and the secondary component carrier via one or more of: control channel communication; a control resource set (CORESET) indication associated with each component carrier, where different CORESETs are associated with different RATs; downlink control information communication; or any combination thereof. In some examples, transmit power manager 1140 may be configured or otherwise support means for determining a first uplink transmit power for a first uplink transmission via the primary component carrier and a second uplink transmit power for a second uplink transmission via the secondary component carrier based on an indication in the carrier aggregation configuration information of which of the first RAT or the second RAT has a higher priority for uplink power control.

[0212] In some examples, the UL / DL prioritization manager 1160 may be configured to or otherwise support components for identifying that both uplink communications and downlink communications are to be sent via a primary component carrier, a secondary component carrier, or both. In some examples, the UL / DL prioritization manager 1160 may be configured to or otherwise support components for prioritizing uplink communications or downlink communications based on which of the first RAT or the second RAT has a higher priority for communication, a service type associated with each of the uplink communications and the downlink communications, a priority of data to be sent in each of the uplink communications and the downlink communications, a physical layer channel type sent in each of the uplink communications and the downlink communications, a waveform type used for each of the uplink communications and the downlink communications, or any combination thereof.

[0213] In some examples, the multi-RAT CA communication manager 1130 may be configured to or otherwise support components for identifying a first uplink transmission to be provided to the first RAN and a second uplink transmission to be provided to the second RAN. In some examples, the multi-RAT CA communication manager 1130 may be configured to or otherwise support components for performing the following operations: determining, based on the carrier aggregation configuration information, to send the first uplink transmission via a primary component carrier and to send the second uplink transmission via a secondary component carrier, or to multiplex the first uplink transmission and the second uplink transmission for transmission via the primary component carrier or the secondary component carrier. In some examples, the determination is based on one or more of the following: a codebook type associated with the first uplink transmission and the second uplink transmission, a waveform of the first uplink transmission and the second uplink transmission, a transmission format of a physical layer channel carrying the first uplink transmission and the second uplink transmission, a priority order of the first RAT and the second RAT, a service type associated with the first uplink transmission and the second uplink transmission, or any combination thereof. In some examples, the first uplink transmission and the second uplink transmission include one or more of: feedback information indicating whether one or more downlink communications are successfully decoded, uplink control information, uplink shared channel data, or any combination thereof.

[0214] In some examples, the multi-RAT CA communication manager 1130 may be configured to or otherwise support a component for receiving one or more triggers for performing one or more operations associated with a primary component carrier or a secondary component carrier or a single trigger indicating that one or more operations are performed using both a first RAT and a second RAT, wherein the one or more triggers are received separately for each RAT. In some examples, the one or more operations include one or more of the following: sounding reference signal transmission, activation or deactivation of a secondary cell that provides service using a secondary component carrier, semi-persistent scheduling or configuration grant activation or deactivation, power control procedures, or any combination thereof. In some examples, the one or more triggers are provided in a downlink control information trigger container or a medium access control (MAC) control element (CE) trigger container, and each trigger is applied to one or both of the first RAT or the second RAT based on the type of the trigger container that provides the one or more triggers. In some examples, the SR manager 1165 may be configured to or otherwise support a component for sending a scheduling request via a primary component carrier or a secondary component carrier, wherein the scheduling request is for resources of the first RAT, the second RAT, or both of the first RAT and the second RAT.

[0215] In some examples, the BWP manager 1150 may be configured to or otherwise support components for receiving one or more resource allocations or bandwidth portion scheduling indications, wherein the one or more resource allocations or bandwidth portion scheduling indications are provided for each RAT or across RATs. In some examples, logical channel prioritization for two or more logical channels to be provided via a primary component carrier or a secondary component carrier is based on which of the first RAT or the second RAT is associated with the primary component carrier or the secondary component carrier carrying the associated logical channel.

[0216] In some examples, CA configuration manager 1125 may be configured or otherwise support components for sending a UE capability report indicating one or more UE capabilities for each RAT or across RATs. In some examples, a discontinuous reception configuration for the UE is provided for each RAT or across RATs.

[0217] In some examples, the primary component carrier and the secondary component carrier are included in a first set of component carriers of a first cell group of a DC configuration of the UE, and wherein the second set of component carriers is configured in a second cell group of the DC configuration of the UE. In some examples, a first medium access control (MAC) entity provides scheduling information for the first set of component carriers, and a second MAC entity provides scheduling information for the second set of component carriers. In some examples, the primary component carrier and the secondary component carrier are each assigned to the first cell group or the second cell group based on one or more of a service type associated with each respective component carrier, a physical layer indication or a MAC layer indication associated with each respective component carrier, one or more physical layer channels carried using each respective component carrier, a type of information carried using each respective component carrier, or any combination thereof. In some examples, a set of multiple BWPs is configured for communication at the UE, each BWP in the set of multiple BWPs is associated with one of a first RAT or a second RAT, wherein different BWPs in the set of multiple BWPs are configured for different services, and wherein a BWP switching indication for a carrier indicates that the RAT associated with the carrier is to be switched.

[0218] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 may support wireless communications at the UE. The DC configuration manager 1135 may be configured to or otherwise support components for receiving DC configuration information for a first cell group and a second cell group, wherein the first cell group is served using one or more carriers employing a first RAT and the second cell group is served using one or more carriers employing a second RAT, and wherein different network entities provide physical layer scheduling information for the first cell group and the second cell group. The transmit power manager 1140 may be configured to or otherwise support components for receiving uplink power control information, the uplink power control information including an indication of a first uplink transmit power for a first uplink transmission and a second uplink transmit power for a second uplink transmission, the first uplink transmit power and the second uplink transmit power being indicated as being preferentially used for uplink power control based on which of the first carrier of the first cell group or the second carrier of the second cell group is indicated. The DC scheduling manager 1145 may be configured to or otherwise support components for transmitting a first uplink transmission using a first carrier concurrently with transmitting a second uplink transmission using a second carrier, the first uplink transmission using a first uplink transmission power and the second uplink transmission using a second uplink transmission power. In some examples, the DC configuration information indicates a carrier priority ranking based on one or more services associated with the first carrier and the second carrier.

[0219] In some examples, the transmit power manager 1140 may be configured to or otherwise support components for determining power scaling associated with the first carrier and the second carrier based on one or more services associated with each of the first carrier and the second carrier. In some examples, the first carrier and the second carrier are prioritized for uplink power control based on a priority ranking of one or more physical layer services or medium access control layer logical channels and associated services or logical channels provided using the first carrier and the second carrier provided in the DC configuration information. In some examples, the first carrier and the second carrier are prioritized for uplink power control based on a waveform type priority ranking provided in the DC configuration information and the associated waveform types of the first carrier and the second carrier. In some examples, the first carrier and the second carrier are prioritized for uplink power control based on one or more types of channels or data types provided using the first carrier and the second carrier.

[0220] In some examples, the DC configuration information configures two or more component carriers in a carrier aggregation configuration for at least a first cell group, and wherein the first cell group includes component carriers associated with different RATs. In some examples, a first medium access control (MAC) entity provides physical layer scheduling information for each component carrier of the first cell group, and a second MAC entity provides physical layer scheduling information for each component carrier of the second cell group.

[0221] In some examples, the DC configuration manager 1135 may be configured to or otherwise support components for determining that the first carrier is included in the first cell group or the second cell group based on one or more of a type of service provided using the first carrier, a physical layer or medium access control layer indication associated with the first carrier, one or more channels sent via the first carrier, a type of information sent via the first carrier, or any combination thereof. In some examples, a set of multiple bandwidth parts (BWPs) are configured for communication at a UE, each BWP in the set of multiple BWPs is associated with one of a first RAT or a second RAT, wherein different BWPs in the set of multiple BWPs are configured for different services, and wherein a BWP switching indication for a carrier indicates that the RAT associated with the carrier is to be switched.

[0222] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 may support wireless communications at the UE. In some examples, the DC configuration manager 1135 may be configured to or otherwise support components for receiving DC configuration information for a first cell and a second cell, wherein the first cell is associated with a first carrier using a first RAT, and the second cell is associated with a second carrier using a second RAT, and wherein the first carrier and the second carrier share the same set of wireless resources multiplexed between the first cell and the second cell in a time interval synchronized between the first RAT and the second RAT. In some examples, the DC scheduling manager 1145 may be configured to or otherwise support components for using a first carrier to communicate with a first RAN and using a second carrier to communicate with a second RAN based on a multiplexing configuration indicated in the DC configuration information. In some examples, the time interval is a time slot synchronized at a time slot boundary used in the first RAN and the second RAN, and wherein the multiplexing configuration indicates time division multiplexing in the time slot.

[0223] In some examples, the DC scheduling manager 1145 may be configured to or otherwise support components for receiving scheduling information for the first cell from a first scheduling entity associated with the first RAN. In some examples, the DC scheduling manager 1145 may be configured to or otherwise support components for receiving scheduling information for the second cell from a second scheduling entity associated with the second RAN. In some examples, the DC configuration information provides a set of time slots, wherein a first subset of time slots is used for the first RAN and a second subset of time slots is used for the second RAN. In some examples, a ratio of a first number of time slots in the first subset of time slots to a second number of time slots in the second subset of time slots is determined based on a buffer state associated with each cell, a TDD time slot mode of each cell, or any combination thereof.

[0224] In some examples, a scheduling pattern for a first subset of time slots and a second subset of time slots is provided in downlink control information, in a MAC control element, in a downlink signal indicating a sequence of time slots and corresponding cells, or any combination thereof. In some examples, the scheduling pattern is applied to uplink communications and downlink communications for intra-band transmission and inter-band transmission for each carrier. In some examples, the multiplexing configuration indicated in the DC configuration information provides frequency domain multiplexing or spatial domain multiplexing. In some examples, the multiplexing configuration indicated in the DC configuration information provides radio spectrum sharing for two or more operators that operate different RANs using the first RAT, the second RAT, or both.

[0225] Fig.12A diagram of a system 1200 is shown that includes a device 1205 that supports techniques for wireless communication using multiple RATs in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of a device 905, a device 1005, or a UE 115 as described herein, or include components thereof. The device 1205 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1205 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1220, an input / output (I / O) controller 1210, a transceiver 1215, an antenna 1225, a memory 1230, a code 1235, and a processor 1240. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1245).

[0226] I / O controller 1210 can manage input signals and output signals of device 1205. I / O controller 1210 can also manage peripheral devices that are not integrated into device 1205. In some cases, I / O controller 1210 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1210 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 1210 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1210 may be implemented as part of a processor (such as processor 1240). In some cases, a user may interact with device 1205 via I / O controller 1210 or via hardware components controlled by I / O controller 1210.

[0227] In some cases, the device 1205 may include a single antenna 1225. However, in some other cases, the device 1205 may have more than one antenna 1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1215 may communicate bidirectionally via one or more antennas 1225, a wired or wireless link, as described herein. For example, the transceiver 1215 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1215 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1225 for transmission; and demodulating packets received from one or more antennas 1225. The transceiver 1215 or the transceiver 1215 and one or more antennas 1225 may be examples of transmitter 915, transmitter 1015, receiver 910, receiver 1010, or any combination thereof or components thereof as described herein.

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

[0229] Processor 1240 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1240 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1240. Processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1230) to enable device 1205 to perform various functions (e.g., various functions or tasks supporting technologies for wireless communication using multiple RATs). For example, device 1205 or a component of device 1205 may include processor 1240 and memory 1230 coupled to or coupled to processor 1240, and processor 1240 and memory 1230 are configured to perform the various functions described herein.

[0230] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a UE. For example, the communication manager 1220 may be configured to or otherwise support components for receiving carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first RAT and the secondary component carrier uses a second RAT. The communication manager 1220 may be configured to or otherwise support components for communicating with a first RAN using the primary component carrier and communicating with a second RAN using the secondary component carrier based on the carrier aggregation configuration information.

[0231] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1220 may support wireless communications at the UE. For example, the communication manager 1220 may be configured to or otherwise support components for receiving DC configuration information for a first cell group and a second cell group, wherein the first cell group is served using one or more carriers using a first RAT and the second cell group is served using one or more carriers using a second RAT, and wherein different network entities provide physical layer scheduling information for the first cell group and the second cell group. The communication manager 1220 may be configured to or otherwise support components for receiving uplink power control information, the uplink power control information including an indication of a first uplink transmit power for a first uplink transmission and a second uplink transmit power for a second uplink transmission, the first uplink transmit power and the second uplink transmit power being indicated as being prioritized for uplink power control based on which of the first carrier of the first cell group or the second carrier of the second cell group is indicated as being prioritized for uplink power control. The communications manager 1220 may be configured or otherwise support components for sending a first uplink transmission using a first carrier concurrently with sending a second uplink transmission using a second carrier, the first uplink transmission using a first uplink transmit power and the second uplink transmission using a second uplink transmit power.

[0232] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1220 may support wireless communications at the UE. For example, the communication manager 1220 may be configured to or otherwise support components for receiving DC configuration information for a first cell and a second cell, wherein the first cell is associated with a first carrier using a first RAT, and the second cell is associated with a second carrier using a second RAT, and wherein the first carrier and the second carrier share the same set of radio resources multiplexed between the first cell and the second cell in a time interval synchronized between the first RAT and the second RAT. The communication manager 1220 may be configured to or otherwise support components for communicating with a first RAN using a first carrier and communicating with a second RAN using a second carrier based on a multiplexing configuration indicated in the DC configuration information.

[0233] By including or configuring the communication manager 1220 according to examples as described herein, the device 1205 can support techniques for multi-RAT DC communication, carrier aggregation communication, or a combination thereof, wherein scheduling flexibility for communication using different RATs can be provided through different carriers that can be associated with different RATs. Such techniques can provide more efficient resource utilization, enhanced throughput, and enhanced communication reliability, as well as network scheduling flexibility for communication using different RATs.

[0234] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1215, one or more antennas 1225, or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the processor 1240, the memory 1230, the code 1235, or any combination thereof. For example, the code 1235 may include instructions executable by the processor 1240 to cause the device 1205 to perform various aspects of the techniques for wireless communication using multiple RATs as described herein, or the processor 1240 and the memory 1230 may be otherwise configured to perform or support such operations.

[0235] Fig.13 A block diagram 1300 of a device 1305 supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of aspects of the network entity 105 as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0236] Receiver 1310 may provide means for obtaining (e.g., receiving, determining, identifying) 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, protocol data units, service data units). The information may be passed to other components of device 1305. In some examples, receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1310 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0237] The transmitter 1315 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1305. For example, the transmitter 1315 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, protocol data units, service data units). In some examples, the transmitter 1315 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1315 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1315 and the receiver 1310 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0238] The communication manager 1320, the receiver 1310, the transmitter 1315, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the techniques for wireless communication using multiple RATs as described herein. For example, the communication manager 1320, the receiver 1310, the transmitter 1315, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

[0239] In some examples, the communication manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0240] Additionally or alternatively, in some examples, the communication manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0241] In some examples, communication manager 1320 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1310, transmitter 1315, or both. For example, communication manager 1320 may receive information from receiver 1310, transmit information to transmitter 1315, or be integrated in conjunction with receiver 1310, transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.

[0242] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. For example, the communication manager 1320 may be configured to or otherwise support components for sending carrier aggregation configuration information for a primary component carrier and for a secondary component carrier to a UE, wherein the primary component carrier uses a first RAT and is associated with a first RAN, and the secondary component carrier uses a second RAT and is associated with a second RAN. The communication manager 1320 may be configured to or otherwise support components for communicating with the UE based on the carrier aggregation configuration information.

[0243] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. For example, the communication manager 1320 may be configured to or otherwise support components for sending DC configuration information for a first cell group and a second cell group to a UE, wherein the first cell group is associated with one or more carriers using a first RAT, and the second cell group is associated with one or more carriers using a second RAT, and wherein different scheduling entities provide physical layer scheduling information for the first cell group and the second cell group. The communication manager 1320 may be configured to or otherwise support components for sending uplink power control information to the UE, the uplink power control information including an indication of a first uplink transmit power for a first uplink transmission and a second uplink transmit power for a second uplink transmission, the first uplink transmit power and the second uplink transmit power being based on which of the first carrier of the first cell group or the second carrier of the second cell group is indicated as being prioritized for uplink power control. The communication manager 1320 may be configured to or otherwise support components for receiving a first uplink transmission from a UE using a first carrier, wherein the first uplink transmission is sent concurrently with a second uplink transmission using a second carrier of a second cell group, the first uplink transmission using a first uplink transmission power and the second uplink transmission using a second uplink transmission power.

[0244] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. For example, the communication manager 1320 may be configured to or otherwise support components for sending DC configuration information for a first cell and a second cell to a UE, wherein the first cell is associated with a first carrier using a first RAT, and the second cell is associated with a second carrier using a second RAT, and wherein the first carrier and the second carrier share the same set of wireless resources multiplexed between the first cell and the second cell in a time interval synchronized between the first RAT and the second RAT. The communication manager 1320 may be configured to or otherwise support components for communicating with the UE based on the multiplexing configuration indicated in the DC configuration information.

[0245] By including or configuring the communication manager 1320 according to the examples described herein, the device 1305 (e.g., a processor controlling the receiver 1310, the transmitter 1315, the communication manager 1320, or a combination thereof or otherwise coupled thereto) can support techniques for multi-RAT DC communication, carrier aggregation communication, or a combination thereof, wherein scheduling flexibility for communication using different RATs can be provided through different carriers that can be associated with different RATs. Such techniques can provide more efficient resource utilization, enhanced throughput, and enhanced communication reliability, as well as network scheduling flexibility for communication using different RATs.

[0246] Fig.14 A block diagram 1400 of a device 1405 supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of aspects of the device 1305 or the network entity 105 as described herein. The device 1405 may include a receiver 1410, a transmitter 1415, and a communication manager 1420. The device 1405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0247] Receiver 1410 may provide means for obtaining (e.g., receiving, determining, identifying) 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, protocol data units, service data units). The information may be passed to other components of device 1405. In some examples, receiver 1410 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1410 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0248] The transmitter 1415 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1405. For example, the transmitter 1415 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, protocol data units, service data units). In some examples, the transmitter 1415 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1415 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1415 and the receiver 1410 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0249] The device 1405 or its various components may be examples of components for performing various aspects of the techniques for wireless communication using multiple RATs as described herein. For example, the communication manager 1420 may include a CA configuration manager 1425, a multi-RAT CA communication manager 1430, a DC configuration manager 1435, a transmit power manager 1440, a DC scheduling manager 1445, or any combination thereof. The communication manager 1420 may be an example of various aspects of the communication manager 1320 as described herein. In some examples, the communication manager 1420 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 1410, the transmitter 1415, or both. For example, the communication manager 1420 may receive information from the receiver 1410, transmit information to the transmitter 1415, or be integrated with the receiver 1410, the transmitter 1415, or both to obtain information, output information, or perform various other operations as described herein.

[0250] According to examples as disclosed herein, the communication manager 1420 may support wireless communications at a network entity. The CA configuration manager 1425 may be configured to or otherwise support components for sending carrier aggregation configuration information for a primary component carrier and for a secondary component carrier to a UE, wherein the primary component carrier uses a first RAT and is associated with a first RAN, and the secondary component carrier uses a second RAT and is associated with a second RAN. The multi-RAT CA communication manager 1430 may be configured to or otherwise support components for communicating with the UE based on the carrier aggregation configuration information.

[0251] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1420 may support wireless communications at a network entity. The DC configuration manager 1435 may be configured to or otherwise support components for sending DC configuration information for a first cell group and a second cell group to a UE, wherein the first cell group is associated with one or more carriers using a first RAT and the second cell group is associated with one or more carriers using a second RAT, and wherein different scheduling entities provide physical layer scheduling information for the first cell group and the second cell group. The transmit power manager 1440 may be configured to or otherwise support components for sending uplink power control information to the UE, the uplink power control information including an indication of a first uplink transmit power for a first uplink transmission and a second uplink transmit power for a second uplink transmission, the first uplink transmit power and the second uplink transmit power being based on which of the first carrier of the first cell group or the second carrier of the second cell group is indicated as being prioritized for uplink power control. The DC scheduling manager 1445 may be configured to or otherwise support components for receiving a first uplink transmission from a UE using a first carrier, wherein the first uplink transmission is sent concurrently with a second uplink transmission sent using a second carrier of a second cell group, the first uplink transmission using a first uplink transmission power and the second uplink transmission using a second uplink transmission power.

[0252] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1420 may support wireless communications at a network entity. The DC configuration manager 1435 may be configured to or otherwise support components for sending DC configuration information for a first cell and a second cell to a UE, wherein the first cell is associated with a first carrier using a first RAT, and the second cell is associated with a second carrier using a second RAT, and wherein the first carrier and the second carrier share the same set of wireless resources multiplexed between the first cell and the second cell in a time interval synchronized between the first RAT and the second RAT. The DC scheduling manager 1445 may be configured to or otherwise support components for communicating with the UE based on a multiplexing configuration indicated in the DC configuration information.

[0253] Fig.15A block diagram 1500 of a communication manager 1520 supporting techniques for wireless communication using multiple RATs in accordance with one or more aspects of the present disclosure is shown. The communication manager 1520 may be an example of aspects of the communication manager 1320, the communication manager 1420, or both as described herein. The communication manager 1520 or its various components may be examples of components for performing various aspects of the techniques for wireless communication using multiple RATs as described herein. For example, the communication manager 1520 may include a CA configuration manager 1525, a multi-RAT CA communication manager 1530, a DC configuration manager 1535, a transmit power manager 1540, a DC scheduling manager 1545, a BWP manager 1550, a CORESET manager 1555, a UL / DL prioritization manager 1560, an SR manager 1565, a DRX manager 1570, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0254] According to examples as disclosed herein, the communication manager 1520 may support wireless communications at a network entity. The CA configuration manager 1525 may be configured to or otherwise support components for sending carrier aggregation configuration information for a primary component carrier and for a secondary component carrier to a UE, wherein the primary component carrier uses a first RAT and is associated with a first RAN, and the secondary component carrier uses a second RAT and is associated with a second RAN. The multi-RAT CA communication manager 1530 may be configured to or otherwise support components for communicating with the UE based on the carrier aggregation configuration information. In some examples, the first RAT is a fifth generation (5G) RAT and the second RAT is a sixth generation (6G) RAT, and wherein the same scheduling entity provides physical layer scheduling information for both the primary component carrier and the secondary component carrier.

[0255] In some examples, to support sending carrier aggregation configuration information, the BWP manager 1550 may be configured to or otherwise support components for sending bandwidth portion configurations for a set of multiple bandwidth portions for a channel bandwidth, on which a primary component carrier, a secondary component carrier, or both can be configured to operate. In some examples, to support sending carrier aggregation configuration information, the BWP manager 1550 may be configured to or otherwise support components for a set of multiple bandwidth portions where a first bandwidth portion in the set of multiple bandwidth portions is associated with a first RAT and a second bandwidth portion in the set of multiple bandwidth portions is associated with a second RAT. In some examples, to support sending carrier aggregation configuration information, the BWP manager 1550 may be configured to or otherwise support components for a set of multiple bandwidth portions where a primary component carrier is associated with a first RAT based on being configured with the first bandwidth portion and a secondary component carrier is associated with a second RAT based on being configured with the second bandwidth portion.

[0256] In some examples, to support sending carrier aggregation configuration information, the CORESET manager 1555 may be configured to or otherwise support means for sending an indication of which of the first RAT or the second RAT is associated with the primary component carrier and the secondary component carrier via one or more of: control channel communication; a control resource set (CORESET) indication associated with each component carrier, where different CORESETs are associated with different RATs; downlink control information communication; or any combination thereof. In some examples, a first uplink transmit power for a first uplink transmission via the primary component carrier and a second uplink transmit power for a second uplink transmission via the secondary component carrier are determined based on an indication in the carrier aggregation configuration information of which of the first RAT or the second RAT has a higher priority for uplink power control.

[0257] In some examples, the UL / DL prioritization manager 1560 may be configured to or otherwise support components for identifying that both uplink communications and downlink communications are to be sent via a primary component carrier, a secondary component carrier, or both. In some examples, the UL / DL prioritization manager 1560 may be configured to or otherwise support components for prioritizing uplink communications or downlink communications based on which of the first RAT or the second RAT has a higher priority for communication, a service type associated with each of the uplink communications and the downlink communications, a priority of data to be sent in each of the uplink communications and the downlink communications, a physical layer channel type sent in each of the uplink communications and the downlink communications, a waveform type used for each of the uplink communications and the downlink communications, or any combination thereof.

[0258] In some examples, a first uplink transmission is provided to a first RAN and a second uplink transmission is provided to a second RAN. In some examples, the carrier aggregation configuration information indicates that the first uplink transmission is to be transmitted via a primary component carrier and the second uplink transmission is to be transmitted via a secondary component carrier, or the first uplink transmission and the second uplink transmission are multiplexed via the primary component carrier or the secondary component carrier. In some examples, the per-component carrier transmission of the first uplink transmission and the second uplink transmission or the multiplexed transmission of the first uplink transmission and the second uplink transmission is based on one or more of the following: a codebook type associated with the first uplink transmission and the second uplink transmission, a waveform of the first uplink transmission and the second uplink transmission, a transmission format of a physical layer channel carrying the first uplink transmission and the second uplink transmission, a priority order of the first RAT and the second RAT, a service type associated with the first uplink transmission and the second uplink transmission, or any combination thereof. In some examples, the first uplink transmission and the second uplink transmission include one or more of: feedback information indicating whether one or more downlink communications are successfully decoded, uplink control information, uplink shared channel data, or any combination thereof.

[0259] In some examples, the multi-RAT CA communication manager 1530 may be configured to or otherwise support a component for sending one or more triggers to perform one or more operations associated with a primary component carrier or a secondary component carrier or a single trigger indicating the use of both a first RAT and a second RAT to perform one or more operations, wherein the one or more triggers are sent separately for each RAT. In some examples, the one or more operations include one or more of the following: sounding reference signal transmission, activation or deactivation of a secondary cell associated with a secondary component carrier, semi-persistent scheduling or configuration grant activation or deactivation, power control procedures, or any combination thereof. In some examples, the one or more triggers are provided in a downlink control information trigger container or a MAC control element trigger container, and each trigger is applied to one or both of the first RAT or the second RAT based on the type of the trigger container providing the one or more triggers. In some examples, a scheduling request is provided from the UE via the primary component carrier or the secondary component carrier, wherein the scheduling request is for resources of the first RAT, the second RAT, or both the first RAT and the second RAT.

[0260] In some examples, the BWP manager 1550 may be configured to or otherwise support components for sending one or more resource allocations or bandwidth portion scheduling indications to the UE, wherein the one or more resource allocations or bandwidth portion scheduling indications are provided for each RAT or across RATs. In some examples, logical channel prioritization for two or more logical channels to be provided via a primary component carrier or a secondary component carrier is based on which of the first RAT or the second RAT is associated with the primary component carrier or the secondary component carrier carrying the associated logical channel. In some examples, the UE provides a UE capability report indicating one or more UE capabilities for each RAT or across RATs. In some examples, a discontinuous reception configuration for the UE is provided for each RAT or across RATs.

[0261] In some examples, the primary component carrier and the secondary component carrier are included in a first set of component carriers of a first cell group of a DC configuration of the UE, and wherein the second set of component carriers is configured in a second cell group of the DC configuration of the UE. In some examples, the first MAC entity provides scheduling information for the first set of component carriers, and the second MAC entity provides scheduling information for the second set of component carriers. In some examples, the primary component carrier and the secondary component carrier are each assigned to the first cell group or the second cell group based on one or more of a service type associated with each respective component carrier, a physical layer indication or a MAC layer indication associated with each respective component carrier, one or more physical layer channels carried using each respective component carrier, a type of information carried using each respective component carrier, or any combination thereof. In some examples, a set of multiple BWPs is configured for communication at the UE, each BWP in the set of multiple BWPs is associated with one of a first RAT or a second RAT, wherein different BWPs in the set of multiple BWPs are configured for different services, and wherein a BWP switching indication for a carrier indicates that the RAT associated with the carrier is to be switched.

[0262] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1520 may support wireless communications at a network entity. The DC configuration manager 1535 may be configured to or otherwise support components for sending DC configuration information for a first cell group and a second cell group to a UE, wherein the first cell group is associated with one or more carriers using a first RAT and the second cell group is associated with one or more carriers using a second RAT, and wherein different scheduling entities provide physical layer scheduling information for the first cell group and the second cell group. The transmit power manager 1540 may be configured to or otherwise support components for sending uplink power control information to the UE, the uplink power control information including an indication of a first uplink transmit power for a first uplink transmission and a second uplink transmit power for a second uplink transmission, the first uplink transmit power and the second uplink transmit power being based on which of the first carrier of the first cell group or the second carrier of the second cell group is indicated as being prioritized for uplink power control. The DC scheduling manager 1545 may be configured to or otherwise support components for receiving a first uplink transmission from a UE using a first carrier, wherein the first uplink transmission is sent concurrently with a second uplink transmission sent using a second carrier of a second cell group, the first uplink transmission using a first uplink transmission power and the second uplink transmission using a second uplink transmission power.

[0263] In some examples, the DC configuration information indicates a carrier priority ranking based on one or more services associated with the first carrier and the second carrier. In some examples, the power scaling associated with the first carrier and the second carrier is based on one or more services associated with each of the first carrier and the second carrier. In some examples, the first carrier and the second carrier are prioritized for uplink power control based on the priority ranking of one or more physical layer services or medium access control layer logical channels and associated services or logical channels provided using the first carrier and the second carrier provided in the DC configuration information. In some examples, the first carrier and the second carrier are prioritized for uplink power control based on the waveform type priority ranking provided in the DC configuration information and the associated waveform types of the first carrier and the second carrier. In some examples, the first carrier and the second carrier are prioritized for uplink power control based on one or more types of channels or data types provided via the first carrier and the second carrier.

[0264] In some examples, the DC configuration information configures at least two or more component carriers in a carrier aggregation configuration for a first cell group, and wherein the first cell group includes component carriers associated with different RATs. In some examples, the first MAC entity provides physical layer scheduling information for each component carrier of the first cell group, and the second MAC entity provides physical layer scheduling information for each component carrier of the second cell group. In some examples, the DC configuration manager 1535 may be configured as or otherwise supports a component for performing the following operations: determining that the first carrier is included in the first cell group or the second cell group based on one or more of the type of service provided using the first carrier, a physical layer or medium access control layer indication associated with the first carrier, one or more channels sent via the first carrier, a type of information sent via the first carrier, or any combination thereof. In some examples, a set of multiple BWPs is configured for communication at a UE, each BWP in the set of multiple BWPs is associated with one of a first RAT or a second RAT, wherein different BWPs in the set of multiple BWPs are configured for different services, and wherein a BWP switching indication for a carrier indicates that the RAT associated with the carrier is to be switched.

[0265] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1520 may support wireless communications at a network entity. In some examples, the DC configuration manager 1535 may be configured as or otherwise support components for sending DC configuration information for a first cell and a second cell to a UE, wherein the first cell is associated with a first carrier using a first RAT, and the second cell is associated with a second carrier using a second RAT, and wherein the first carrier and the second carrier share the same set of wireless resources multiplexed between the first cell and the second cell in a time interval synchronized between the first RAT and the second RAT. In some examples, the DC scheduling manager 1545 may be configured as or otherwise support components for communicating with the UE based on a multiplexing configuration indicated in the DC configuration information.

[0266] In some examples, the time interval is a time slot synchronized at the time slot boundary used in the first RAN and the second RAN, and wherein the multiplexing configuration indicates time division multiplexing in the time slot. In some examples, the DC configuration information provides a set of time slots, wherein a first subset of time slots is used for the first RAN and a second subset of time slots is used for the second RAN. In some examples, the ratio of the first number of time slots in the first subset of time slots to the second number of time slots in the second subset of time slots is determined based on a buffer state associated with each cell, a TDD time slot mode of each cell, or any combination thereof. In some examples, a scheduling pattern for the first subset of time slots and the second subset of time slots is provided in downlink control information, in a MAC control element, in a downlink signal indicating a time slot sequence and a corresponding cell, or any combination thereof. In some examples, the scheduling pattern is applied to uplink communications and downlink communications for intra-band transmission and inter-band transmission for each carrier. In some examples, the multiplexing configuration indicated in the DC configuration information provides frequency domain multiplexing or spatial domain multiplexing. In some examples, the reuse configuration indicated in the DC configuration information provides radio spectrum sharing for two or more operators operating different RANs using the first RAT, the second RAT, or both.

[0267] Fig.16 A diagram of a system 1600 is shown that includes a device 1605 supporting techniques for wireless communication using multiple RATs in accordance with one or more aspects of the present disclosure. The device 1605 may be an example of a device 1305, a device 1405, or a network entity 105 as described herein, or include components thereof. The device 1605 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1605 may include components that support output and acquisition of communications, such as a communication manager 1620, a transceiver 1610, an antenna 1615, a memory 1625, a code 1630, and a processor 1635. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1640).

[0268] The transceiver 1610 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1610 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1610 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1605 may include one or more antennas 1615, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1610 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1615, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1615, from a wired receiver); and demodulating a signal. The transceiver 1610 or the transceiver 1610 and one or more antennas 1615 or wired interfaces (where applicable) may be examples of transmitter 1315, transmitter 1415, receiver 1310, receiver 1410, or any combination thereof or components thereof as described herein. In some examples, the transceiver 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, fronthaul communication link 168).

[0269] Memory 1625 may include RAM and ROM. Memory 1625 may store computer-readable, computer-executable code 1630 including instructions that, when executed by processor 1635, cause device 1605 to perform various functions described herein. Code 1630 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1630 may not be directly executable by processor 1635, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1625 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0270] Processor 1635 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1635 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1635. Processor 1635 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1625) to enable device 1605 to perform various functions (e.g., functions or tasks that support technology for wireless communication using multiple RATs). For example, device 1605 or a component of device 1605 may include processor 1635 and memory 1625 coupled to processor 1635, the processor 1635 and memory 1625 being configured to perform the various functions described herein. Processor 1635 can 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 functionality for performing the functions of device 1605 (e.g., by executing code 1630).

[0271] In some examples, bus 1640 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1640 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1605, or communications performed between different components of device 1605 that may be co-located or may be located in different locations (e.g., where device 1605 may refer to a system in which one or more of communication manager 1620, transceiver 1610, memory 1625, code 1630, and processor 1635 may be located in one of the different components or divided between the different components).

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

[0273] According to examples as disclosed herein, the communication manager 1620 may support wireless communications at a network entity. For example, the communication manager 1620 may be configured to or otherwise support components for sending carrier aggregation configuration information for a primary component carrier and for a secondary component carrier to a UE, wherein the primary component carrier uses a first RAT and is associated with a first RAN, and the secondary component carrier uses a second RAT and is associated with a second RAN. The communication manager 1620 may be configured to or otherwise support components for communicating with the UE based on the carrier aggregation configuration information.

[0274] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1620 may support wireless communications at a network entity. For example, the communication manager 1620 may be configured to or otherwise support components for sending DC configuration information for a first cell group and a second cell group to a UE, wherein the first cell group is associated with one or more carriers using a first RAT, and the second cell group is associated with one or more carriers using a second RAT, and wherein different scheduling entities provide physical layer scheduling information for the first cell group and the second cell group. The communication manager 1620 may be configured to or otherwise support components for sending uplink power control information to the UE, the uplink power control information including an indication of a first uplink transmit power for a first uplink transmission and a second uplink transmit power for a second uplink transmission, the first uplink transmit power and the second uplink transmit power being based on which of the first carrier of the first cell group or the second carrier of the second cell group is indicated as being prioritized for uplink power control. The communication manager 1620 may be configured to or otherwise support components for receiving a first uplink transmission from a UE using a first carrier, wherein the first uplink transmission is sent concurrently with a second uplink transmission using a second carrier of a second cell group, the first uplink transmission using a first uplink transmission power and the second uplink transmission using a second uplink transmission power.

[0275] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1620 may support wireless communications at a network entity. For example, the communication manager 1620 may be configured to or otherwise support components for sending DC configuration information for a first cell and a second cell to a UE, wherein the first cell is associated with a first carrier using a first RAT, and the second cell is associated with a second carrier using a second RAT, and wherein the first carrier and the second carrier share the same set of wireless resources multiplexed between the first cell and the second cell in a time interval synchronized between the first RAT and the second RAT. The communication manager 1620 may be configured to or otherwise support components for communicating with the UE based on the multiplexing configuration indicated in the DC configuration information.

[0276] By including or configuring the communication manager 1620 according to examples as described herein, the device 1605 can support techniques for multi-RAT DC communication, carrier aggregation communication, or a combination thereof, wherein scheduling flexibility for communication using different RATs can be provided through different carriers that can be associated with different RATs. Such techniques can provide more efficient resource utilization, enhanced throughput, and enhanced communication reliability, as well as network scheduling flexibility for communication using different RATs.

[0277] In some examples, the communication manager 1620 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1610, one or more antennas 1615 (e.g., where applicable), or any combination thereof. Although the communication manager 1620 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1620 may be supported or performed by the processor 1635, the memory 1625, the code 1630, the transceiver 1610, or any combination thereof. For example, the code 1630 may include instructions executable by the processor 1635 to cause the device 1605 to perform various aspects of the techniques for wireless communication using multiple RATs as described herein, or the processor 1635 and the memory 1625 may be otherwise configured to perform or support such operations.

[0278] Fig.17 A flowchart illustrating a method 1700 of supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or a component thereof as described herein. Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0279] At 1705, the method may include receiving carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first RAT and the secondary component carrier uses a second RAT. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.11 The CA configuration manager 1125 is used to execute.

[0280] At 1710, the method may include communicating with the first RAN using a primary component carrier and communicating with the second RAN using a secondary component carrier based on the carrier aggregation configuration information. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.11 The multi-RAT CA communication manager 1130 is used for execution.

[0281] Fig.18 A flowchart illustrating a method 1800 of supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a UE or a component thereof as described herein. Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0282] At 1805, the method may include receiving carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first RAT and the secondary component carrier uses a second RAT. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.11 The CA configuration manager 1125 is used to execute.

[0283] At 1810, the method may include receiving a bandwidth portion configuration for a set of multiple bandwidth portions of a channel bandwidth, on which a primary component carrier, a secondary component carrier, or both can be configured to operate. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.11 The BWP manager 1150 is performed. In some cases, a first bandwidth part in the set of multiple bandwidth parts is associated with a first RAT, and a second bandwidth part in the set of multiple bandwidth parts is associated with a second RAT. In some cases, the primary component carrier is associated with the first RAT based on being configured with the first bandwidth part, and the secondary component carrier is associated with the second RAT based on being configured with the second bandwidth part.

[0284] At 1815, the method may include communicating with the first RAN using the primary component carrier and communicating with the second RAN using the secondary component carrier based on the carrier aggregation configuration information. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Fig.11The multi-RAT CA communication manager 1130 is used for execution.

[0285] Fig.19 A flowchart illustrating a method 1900 of supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a UE or a component thereof as described herein. Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0286] At 1905, the method may include receiving carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first RAT and the secondary component carrier uses a second RAT. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Fig.11 The CA configuration manager 1125 is used to execute.

[0287] At 1910, the method may include determining a first uplink transmit power for a first uplink transmission via a primary component carrier and a second uplink transmit power for a second uplink transmission via a secondary component carrier based on an indication in the carrier aggregation configuration information regarding which of the first RAT or the second RAT has a higher priority for uplink power control. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Fig.11 The transmit power manager 1140 is used for execution.

[0288] At 1915, the method may include communicating with the first RAN using the primary component carrier and communicating with the second RAN using the secondary component carrier based on the carrier aggregation configuration information. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Fig.11 The multi-RAT CA communication manager 1130 is used for execution.

[0289] Fig. 20 A flowchart illustrating a method 2000 of supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 2000 may be implemented by a UE or a component thereof as described herein. Figures 1 to 12The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0290] At 2005, the method may include receiving carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first RAT and the secondary component carrier uses a second RAT. The operations of 2005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed as described in reference to Fig.11 The CA configuration manager 1125 is used to execute.

[0291] At 2010, the method may include identifying that both uplink communications and downlink communications are to be sent via a primary component carrier, a secondary component carrier, or both. The operations of 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed as described in reference to Fig.11 The UL / DL prioritization manager 1160 is used to perform the above-mentioned operations.

[0292] At 2015, the method may include prioritizing uplink communications or downlink communications based on which of the first RAT or the second RAT has a higher priority for communication, a service type associated with each of the uplink communications and the downlink communications, a priority of data to be sent in each of the uplink communications and the downlink communications, a physical layer channel type sent in each of the uplink communications and the downlink communications, a waveform type used for each of the uplink communications and the downlink communications, or any combination thereof. The operations of 2015 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed by as described in reference to Fig.11 The UL / DL prioritization manager 1160 is used to perform the above-mentioned operations.

[0293] At 2020, the method may include communicating with the first RAN using a primary component carrier and communicating with the second RAN using a secondary component carrier based on the carrier aggregation configuration information. The operations of 2020 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2020 may be performed as described in reference to Fig.11 The multi-RAT CA communication manager 1130 is used for execution.

[0294] Fig.21A flowchart illustrating a method 2100 of supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 2100 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 2100 may be implemented by a UE or a component thereof as described herein. Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0295] At 2105, the method may include receiving carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first RAT and the secondary component carrier uses a second RAT. The operations of 2105 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2105 may be performed as described in reference to Fig.11 The CA configuration manager 1125 is used to execute.

[0296] At 2110, the method may include identifying a first uplink transmission to be provided to the first RAN and a second uplink transmission to be provided to the second RAN. The operations of 2110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2110 may be performed as described in reference to Fig.11 The multi-RAT CA communication manager 1130 is used for execution.

[0297] At 2115, the method may include determining, based on the carrier aggregation configuration information, to send a first uplink transmission via a primary component carrier and to send a second uplink transmission via a secondary component carrier, or to multiplex the first uplink transmission and the second uplink transmission for transmission via the primary component carrier or the secondary component carrier. The operations of 2115 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2115 may be performed as described in reference to Fig.11 The multi-RATCA communication manager 1130 is used to execute.

[0298] At 2120, the method may include communicating with the first RAN using the primary component carrier and communicating with the second RAN using the secondary component carrier based on the carrier aggregation configuration information. The operations of 2120 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2120 may be performed as described in reference to Fig.11 The multi-RAT CA communication manager 1130 is used for execution.

[0299] Fig. 22A flowchart illustrating a method 2200 of supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 2200 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 2200 may be implemented by a UE or a component thereof as described herein. Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0300] At 2205, the method may include receiving carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first RAT and the secondary component carrier uses a second RAT. The operations of 2205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2205 may be performed as described in reference to Fig.11 The CA configuration manager 1125 is used to execute.

[0301] At 2210, the method may include communicating with the first RAN using a primary component carrier and communicating with the second RAN using a secondary component carrier based on the carrier aggregation configuration information. The operations of 2210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2210 may be performed as described in reference to Fig.11 The multi-RAT CA communication manager 1130 is used for execution.

[0302] At 2215, the method may include sending a scheduling request via a primary component carrier or a secondary component carrier, wherein the scheduling request is for resources of the first RAT, the second RAT, or both the first RAT and the second RAT. The operations of 2215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2215 may be performed as described in reference to Fig.11 The SR manager 1165 described above is executed.

[0303] At 2220, the method may include receiving one or more resource allocations or bandwidth portion scheduling indications, wherein the one or more resource allocations or bandwidth portion scheduling indications are provided for each RAT or across RATs. The operations of 2220 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2220 may be performed as described in reference to Fig.11 The BWP manager 1150 is used to execute.

[0304] Fig.23A flowchart illustrating a method 2300 of supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 2300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 2300 may be implemented by a UE or a component thereof as described herein. Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0305] At 2305, the method may include receiving DC configuration information for a first cell group and a second cell group, wherein the first cell group is served using one or more carriers using a first RAT and the second cell group is served using one or more carriers using a second RAT, and wherein different network entities provide physical layer scheduling information for the first cell group and the second cell group. The operations of 2305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2305 may be performed as described in reference to Fig.11 The DC configuration manager 1135 is used to execute.

[0306] At 2310, the method may include receiving uplink power control information, the uplink power control information including an indication of a first uplink transmit power of a first uplink transmission and a second uplink transmit power of a second uplink transmission, the first uplink transmit power and the second uplink transmit power being indicated as being preferentially used for uplink power control based on which of a first carrier of a first cell group or a second carrier of a second cell group is indicated. The operations of 2310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2310 may be performed by as described in reference to Fig.11 The transmit power manager 1140 is used for execution.

[0307] At 2315, the method may include sending a first uplink transmission using a first carrier concurrently with sending a second uplink transmission using a second carrier, the first uplink transmission using a first uplink transmission power and the second uplink transmission using a second uplink transmission power. The operations of 2315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2315 may be performed as described in reference to Fig.11 The DC scheduling manager 1145 is used for execution.

[0308] Fig.24A flowchart illustrating a method 2400 of supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 2400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 2400 may be implemented by a UE or a component thereof as described herein. Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0309] At 2405, the method may include receiving DC configuration information for a first cell group and a second cell group, wherein the first cell group is served using one or more carriers using a first RAT and the second cell group is served using one or more carriers using a second RAT, and wherein different network entities provide physical layer scheduling information for the first cell group and the second cell group. The operations of 2405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2405 may be performed as described in reference Fig.11 The DC configuration manager 1135 is used to execute.

[0310] At 2410, the method may include receiving uplink power control information, the uplink power control information including an indication of a first uplink transmission power of a first uplink transmission and a second uplink transmission power of a second uplink transmission, the first uplink transmission power and the second uplink transmission power being indicated as being preferentially used for uplink power control based on which of a first carrier of a first cell group or a second carrier of a second cell group is indicated. The operations of 2410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2410 may be performed by reference to Fig.11 The transmit power manager 1140 is used for execution.

[0311] At 2415, the method may include determining power scaling associated with the first carrier and the second carrier based on one or more services associated with each of the first carrier and the second carrier. The operations of 2415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2415 may be performed as described in reference Fig.11 The transmit power manager 1140 is used for execution.

[0312] At 2420, the method may include transmitting a first uplink transmission using a first carrier concurrently with transmitting a second uplink transmission using a second carrier, the first uplink transmission using a first uplink transmission power and the second uplink transmission using a second uplink transmission power. The operations of 2420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2420 may be performed as described in reference to Fig.11 The DC scheduling manager 1145 is used for execution.

[0313] Fig.25 A flowchart illustrating a method 2500 of supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 2500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 2500 may be implemented by a UE or a component thereof as described herein. Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0314] At 2505, the method may include receiving DC configuration information for a first cell group and a second cell group, wherein the first cell group is served using one or more carriers employing a first RAT and the second cell group is served using one or more carriers employing a second RAT, and wherein different network entities provide physical layer scheduling information for the first cell group and the second cell group. The operations of 2505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2505 may be performed as described in reference to Fig.11 The DC configuration manager 1135 is used to execute.

[0315] At 2510, the method may include receiving uplink power control information, the uplink power control information including an indication of a first uplink transmit power of a first uplink transmission and a second uplink transmit power of a second uplink transmission, the first uplink transmit power and the second uplink transmit power being indicated as being preferentially used for uplink power control based on which of a first carrier of a first cell group or a second carrier of a second cell group is indicated. The operations of 2510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2510 may be performed by reference to Fig.11 The transmit power manager 1140 is used for execution.

[0316] At 2515, the method may include determining that the first carrier is included in the first cell group or the second cell group based on one or more of a type of service provided using the first carrier, a physical layer or medium access control layer indication associated with the first carrier, one or more channels sent via the first carrier, a type of information sent via the first carrier, or any combination thereof. The operations of 2515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2515 may be performed as described in reference to Fig.11 The DC configuration manager 1135 is used to execute.

[0317] At 2520, the method may include transmitting a first uplink transmission using a first carrier concurrently with transmitting a second uplink transmission using a second carrier, the first uplink transmission using a first uplink transmission power and the second uplink transmission using a second uplink transmission power. The operations of 2520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2520 may be performed as described in reference to Fig.11 The DC scheduling manager 1145 is used for execution.

[0318] Fig.26 A flowchart illustrating a method 2600 of supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 2600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 2600 may be implemented by a UE or a component thereof as described herein. Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0319] At 2605, the method may include receiving DC configuration information for a first cell and a second cell, wherein the first cell is associated with a first carrier using a first RAT and the second cell is associated with a second carrier using a second RAT, and wherein the first carrier and the second carrier share a same set of radio resources multiplexed between the first cell and the second cell in a time interval synchronized between the first RAT and the second RAT. The operations of 2605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2605 may be performed as described in reference to Fig.11 The DC configuration manager 1135 is used to execute.

[0320] At 2610, the method may include using a first carrier to communicate with a first RAN based on a multiplexing configuration indicated in the DC configuration information and using a second carrier to communicate with a second RAN. The operations of 2610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2610 may be performed as described in reference to Fig.11 The DC scheduling manager 1145 is used for execution.

[0321] Fig. 27 A flowchart illustrating a method 2700 of supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 2700 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 2700 may be implemented by a UE or a component thereof as described herein. Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0322] At 2705, the method may include receiving DC configuration information for a first cell and a second cell, wherein the first cell is associated with a first carrier using a first RAT and the second cell is associated with a second carrier using a second RAT, and wherein the first carrier and the second carrier share a same set of radio resources multiplexed between the first cell and the second cell in a time interval synchronized between the first RAT and the second RAT. The operations of 2705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2705 may be performed as described in reference to Fig.11 The DC configuration manager 1135 is used to execute.

[0323] At 2710, the method may include receiving scheduling information for the first cell from a first scheduling entity associated with the first RAN. The operations of 2710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2710 may be performed as described in reference to Fig.11 The DC scheduling manager 1145 is used for execution.

[0324] At 2715, the method may include receiving scheduling information for the second cell from a second scheduling entity associated with the second RAN. The operations of 2715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2715 may be performed as described in reference to Fig.11 The DC scheduling manager 1145 is used for execution.

[0325] At 2720, the method may include using the first carrier to communicate with the first RAN based on the multiplexing configuration indicated in the DC configuration information and using the second carrier to communicate with the second RAN. The operations of 2720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2720 may be performed as described in reference to Fig.11 The DC scheduling manager 1145 is used for execution.

[0326] Fig.28 A flowchart illustrating a method 2800 of supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 2800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2800 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 8 as well as Figures 13 to 16 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0327] At 2805, the method may include sending carrier aggregation configuration information for a primary component carrier and for a secondary component carrier to the UE, wherein the primary component carrier uses a first RAT and is associated with a first RAN, and the secondary component carrier uses a second RAT and is associated with a second RAN. The operations of 2805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2805 may be performed as described in reference to Fig.15 The CA configuration manager 1525 is used to execute.

[0328] At 2810, the method may include communicating with the UE based on the carrier aggregation configuration information. The operations of 2810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2810 may be performed as described in reference Fig.15 The multi-RAT CA communication manager 1530 is used for execution.

[0329] Fig.29 A flowchart illustrating a method 2900 of supporting techniques for wireless communication using multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 2900 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2900 may be implemented by a network entity or a component thereof as described herein....

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: receiving carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first radio access technology and the secondary component carrier uses a second radio access technology; as well as The primary component carrier is used to communicate with a first radio access network based at least in part on the carrier aggregation configuration information and the secondary component carrier is used to communicate with a second radio access network. 2 . The method of claim 1 , wherein the first radio access technology is a fifth generation (5G) radio access technology and the second radio access technology is a sixth generation (6G) radio access technology. 3 . The method of claim 1 , wherein the same network entity provides physical layer scheduling information for both the primary component carrier and the secondary component carrier.

4. The method according to claim 1, wherein receiving the carrier aggregation configuration information comprises: receiving a bandwidth portion configuration for a plurality of bandwidth portions of a channel bandwidth, the primary component carrier, the secondary component carrier, or both being configurable to operate on the plurality of bandwidth portions, and wherein a first bandwidth portion of the plurality of bandwidth portions is associated with the first radio access technology and a second bandwidth portion of the plurality of bandwidth portions is associated with the second radio access technology, Wherein the primary component carrier is associated with the first radio access technology based at least in part on being configured with the first bandwidth portion, and the secondary component carrier is associated with the second radio access technology based at least in part on being configured with the second bandwidth portion.

5. The method according to claim 4, wherein: The primary component carrier is configured to operate over a plurality of bandwidth parts, and wherein communication via one or both of the first radio access technology or the second radio access technology is based at least in part on which of the plurality of bandwidth parts is used for communication.

6. The method according to claim 1, wherein receiving the carrier aggregation configuration information comprises: receiving an indication of which of the first radio access technology or the second radio access technology is associated with the primary component carrier and the secondary component carrier via one or more of: a control channel communication; A control resource set (CORESET) associated with each component carrier indicates, wherein different CORESETs are associated with different radio access technologies; downlink control information communication; or any combination thereof.

7. The method according to claim 1, further comprising: A first uplink transmit power for a first uplink transmission via the primary component carrier and a second uplink transmit power for a second uplink transmission via the secondary component carrier are determined based at least in part on an indication in the carrier aggregation configuration information as to which of the first radio access technology or the second radio access technology has a higher priority for uplink power control.

8. The method according to claim 1, further comprising: identifying that both uplink communications and downlink communications are to be transmitted via the primary component carrier, the secondary component carrier, or both, or via a first bandwidth portion, a second bandwidth portion, or both, wherein each bandwidth portion is associated with one or more radio access technologies; as well as The uplink communication or the downlink communication is prioritized based at least in part on which of the first radio access technology or the second radio access technology has a higher priority for communication, a service type associated with each of the uplink communication and the downlink communication, a priority of data to be sent in each of the uplink communication and the downlink communication, a physical layer channel type sent in each of the uplink communication and the downlink communication, a waveform type used for each of the uplink communication and the downlink communication, or any combination thereof.

9. The method according to claim 1, further comprising: identifying a first uplink transmission to be provided to the first radio access network and a second uplink transmission to be provided to the second radio access network; as well as Determine one or more of the component carriers or bandwidth parts to use for each of the first uplink transmission and the second uplink transmission based at least in part on the carrier aggregation configuration information, or multiplex the first uplink transmission and the second uplink transmission for transmission via one component carrier or bandwidth part.

10. The method of claim 9, wherein the determining is based at least in part on one or more of: a codebook type associated with the first uplink transmission and the second uplink transmission, a waveform of the first uplink transmission and the second uplink transmission, a transmission format of a physical layer channel carrying the first uplink transmission and the second uplink transmission, a priority order of the first radio access technology and the second radio access technology, a service type associated with the first uplink transmission and the second uplink transmission, or any combination thereof.

11. The method of claim 9, wherein the first uplink transmission and the second uplink transmission include one or more of the following: feedback information indicating whether one or more downlink communications are successfully decoded, uplink control information, uplink shared channel data, or any combination thereof.

12. The method according to claim 1, further comprising: One or more triggers are received to perform one or more operations associated with the primary component carrier or the secondary component carrier, wherein the one or more triggers are received separately for each radio access technology, or a single trigger is received indicating that the one or more operations are to be performed using both the first radio access technology and the second radio access technology.

13. The method of claim 12, wherein the one or more operations include one or more of: sounding reference signal transmission, activation or deactivation of a secondary cell that uses the secondary component carrier to provide service, semi-persistent scheduling or configuration grant activation or deactivation, power control procedures, or any combination thereof.

14. The method of claim 12, wherein the one or more triggers are provided in a downlink control information trigger container or a medium access control (MAC) control element trigger container, and wherein each trigger is applied to one or both of the first radio access technology or the second radio access technology based at least in part on a type of trigger container in which the one or more triggers are provided.

15. The method according to claim 1, further comprising: A scheduling request is sent via the primary component carrier or the secondary component carrier or via the first bandwidth part or the second bandwidth part, wherein the scheduling request is for resources of the first radio access technology, the second radio access technology, or both the first radio access technology and the second radio access technology.

16. The method according to claim 1, further comprising: One or more resource allocations or bandwidth portion scheduling indications are received, wherein the one or more resource allocations or bandwidth portion scheduling indications are provided per radio access technology or across radio access technologies.

17. The method of claim 1 , wherein logical channel prioritization for two or more logical channels to be provided via the primary component carrier or the secondary component carrier is based at least in part on which of the first radio access technology or the second radio access technology is associated with one or more of the primary component carrier, the secondary component carrier, or a bandwidth portion carrying data for an associated logical channel.

18. The method according to claim 1, further comprising: A UE capability report is sent indicating one or more UE capabilities for each radio access technology or across radio access technologies.

19. The method of claim 1, wherein a discontinuous reception configuration for the UE is provided per radio access technology or across radio access technologies.

20. The method of claim 1, wherein the primary component carrier and the secondary component carrier are included in a first set of component carriers of a first cell group of a dual connectivity configuration of the UE, and wherein a second set of component carriers is configured in a second cell group of the dual connectivity configuration of the UE.

21. The method of claim 20, wherein a first medium access control (MAC) entity provides scheduling information for the first set of component carriers and a second MAC entity provides scheduling information for the second set of component carriers.

22. The method of claim 20, wherein the primary component carrier and the secondary component carrier are each assigned to the first cell group or the second cell group based at least in part on one or more of a service type associated with each respective component carrier, a physical layer indication or a MAC layer indication associated with each respective component carrier, one or more physical layer channels carried using each respective component carrier, a type of information carried using each respective component carrier, or any combination thereof.

23. The method of claim 20, wherein a plurality of bandwidth parts (BWPs) are configured for communication at the UE, each of the plurality of BWPs being associated with one of the first radio access technology or the second radio access technology, wherein different ones of the plurality of BWPs are configured for different services, and wherein a BWP switch for a carrier indicates that the radio access technology associated with the carrier is to be switched.

24. A method for wireless communication at a network entity, the method comprising: sending carrier aggregation configuration information for a primary component carrier and for a secondary component carrier to a user equipment (UE), wherein the primary component carrier uses a first radio access technology and is associated with a first radio access network, and the secondary component carrier uses a second radio access technology and is associated with a second radio access network; and Communicating with the UE based at least in part on the carrier aggregation configuration information.

25. The method according to claim 24, wherein sending the carrier aggregation configuration information comprises: transmitting a bandwidth portion configuration for a plurality of bandwidth portions of a channel bandwidth, the primary component carrier, the secondary component carrier, or both being configurable to operate on the plurality of bandwidth portions, and wherein a first bandwidth portion of the plurality of bandwidth portions is associated with the first radio access technology and a second bandwidth portion of the plurality of bandwidth portions is associated with the second radio access technology, Wherein the primary component carrier is associated with the first radio access technology based at least in part on being configured with the first bandwidth portion, and the secondary component carrier is associated with the second radio access technology based at least in part on being configured with the second bandwidth portion.

26. The method according to claim 24, wherein sending the carrier aggregation configuration information comprises: sending an indication of which of the first radio access technology or the second radio access technology is associated with the primary component carrier and the secondary component carrier via one or more of: a control channel communication; A control resource set (CORESET) associated with each component carrier indicates, wherein different CORESETs are associated with different radio access technologies; downlink control information communication; or any combination thereof.

27. The method of claim 24, wherein a first uplink transmit power for a first uplink transmission via the primary component carrier or the first bandwidth portion and a second uplink transmit power for a second uplink transmission via the secondary component carrier or the second bandwidth portion are determined at least in part based on an indication in the carrier aggregation configuration information as to which of the first radio access technology or the second radio access technology has a higher priority for uplink power control.

28. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving carrier aggregation configuration information for a primary component carrier and for a secondary component carrier, wherein the primary component carrier uses a first radio access technology and the secondary component carrier uses a second radio access technology; as well as The primary component carrier is used to communicate with a first radio access network based at least in part on the carrier aggregation configuration information and the secondary component carrier is used to communicate with a second radio access network.

29. The apparatus of claim 28, wherein the instructions for receiving the carrier aggregation configuration information are executable by the processor to cause the apparatus to: receiving a bandwidth portion configuration for a plurality of bandwidth portions of a channel bandwidth, the primary component carrier, the secondary component carrier, or both being configurable to operate on the plurality of bandwidth portions, and wherein a first bandwidth portion of the plurality of bandwidth portions is associated with the first radio access technology and a second bandwidth portion of the plurality of bandwidth portions is associated with the second radio access technology, Wherein the primary component carrier is associated with the first radio access technology based at least in part on being configured with the first bandwidth portion, and the secondary component carrier is associated with the second radio access technology based at least in part on being configured with the second bandwidth portion.

30. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending carrier aggregation configuration information for a primary component carrier and for a secondary component carrier to a user equipment (UE), wherein the primary component carrier uses a first radio access technology and is associated with a first radio access network, and the secondary component carrier uses a second radio access technology and is associated with a second radio access network; and Communicating with the UE based at least in part on the carrier aggregation configuration information.

Images