Default beam for multi-downlink control information based multi-transmit receive point with unified transmission configuration indicator

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive, in a first control resource set (CORESET) associated with a first CORESET pool index, first downlink control information (DCI) that indicates a first transmission configuration indicator (TCI) state to be applied starting from a first starting time. The UE may receive, in a second CORESET associated with a second CORESET pool index, second DCI that indicates a second TCI state to be applied starting from a second starting time. The UE may receive third DCI that schedules a downlink communication. The UE may receive the downlink communication using a default beam associated with the first CORESET pool index or the second CORESET pool index in connection with a default beam condition associated with the third DCI. Numerous other aspects are described.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for a default beam for multi-downlink control information (DCI) based multi-transmit receive point (TRP) with a unified transmission configuration indicator (TCI).

BACKGROUND

SUMMARY

Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive, in a first control resource set (CORESET) associated with a first CORESET pool index, first downlink control information (DCI) that indicates a first transmission configuration indicator (TCI) state to be applied starting from a first starting time associated with the first DCI. The one or more processors may be configured to receive, in a second CORESET associated with a second CORESET pool index, second DCI that indicates a second TCI state to be applied starting from a second starting time associated with the second DCI. The one or more processors may be configured to receive third DCI that schedules a downlink communication. The one or more processors may be configured to receive the downlink communication using a default beam associated with the first CORESET pool index or the second CORESET pool index in connection with a default beam condition associated with the third DCI.

Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive, in a first component carrier, first DCI that indicates a first TCI state to be applied for communications associated with a first CORESET pool index in a second component carrier starting from a first starting time associated with the first DCI. The one or more processors may be configured to receive second DCI that indicates a second TCI state to be applied for communications associated with a second CORESET pool index in the second component carrier starting from a second starting time associated with the second DCI. The one or more processors may be configured to receive, in the first component carrier, third DCI that schedules a downlink communication in the second component carrier. The one or more processors may be configured to receive the downlink communication in the second component carrier using a default beam in connection with a default beam condition associated with the third DCI, wherein the default beam is determined to be a beam associated with the first TCI state or a beam associated with the second TCI state based at least in part on whether the downlink communication is associated with the first CORESET pool index or the second CORESET pool index.

Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit, in a first CORESET associated with a first CORESET pool index of multiple CORESET pool indexes configured for a UE, first DCI that indicates a TCI state to be applied starting from a starting time associated with the first DCI. The one or more processors may be configured to transmit a downlink communication scheduled by second DCI using a default beam in connection with a default beam condition associated with the second DCI and in connection with the default beam being associated with the first CORESET pool index.

Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving, in a first CORESET associated with a first CORESET pool index, first DCI that indicates a first TCI state to be applied starting from a first starting time associated with the first DCI. The method may include receiving, in a second CORESET associated with a second CORESET pool index, second DCI that indicates a second TCI state to be applied starting from a second starting time associated with the second DCI. The method may include receiving third DCI that schedules a downlink communication. The method may include receiving the downlink communication using a default beam associated with the first CORESET pool index or the second CORESET pool index in connection with a default beam condition associated with the third DCI.

Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving, in a first component carrier, first DCI that indicates a first TCI state to be applied for communications associated with a first CORESET pool index in a second component carrier starting from a first starting time associated with the first DCI. The method may include receiving second DCI that indicates a second TCI state to be applied for communications associated with a second CORESET pool index in the second component carrier starting from a second starting time associated with the second DCI. The method may include receiving, in the first component carrier, third DCI that schedules a downlink communication in the second component carrier. The method may include receiving the downlink communication in the second component carrier using a default beam in connection with a default beam condition associated with the third DCI, wherein the default beam is determined to be a beam associated with the first TCI state or a beam associated with the second TCI state based at least in part on whether the downlink communication is associated with the first CORESET pool index or the second CORESET pool index.

Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting, in a first CORESET associated with a first CORESET pool index of multiple CORESET pool indexes configured for a UE, first DCI that indicates a TCI state to be applied starting from a starting time associated with the first DCI. The method may include transmitting a downlink communication scheduled by second DCI using a default beam in connection with a default beam condition associated with the second DCI and in connection with the default beam being associated with the first CORESET pool index.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive, in a first CORESET associated with a first CORESET pool index, first DCI that indicates a first TCI state to be applied starting from a first starting time associated with the first DCI. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive, in a second CORESET associated with a second CORESET pool index, second DCI that indicates a second TCI state to be applied starting from a second starting time associated with the second DCI. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive third DCI that schedules a downlink communication. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive the downlink communication using a default beam associated with the first CORESET pool index or the second CORESET pool index in connection with a default beam condition associated with the third DCI.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive, in a first component carrier, first DCI that indicates a first TCI state to be applied for communications associated with a first CORESET pool index in a second component carrier starting from a first starting time associated with the first DCI. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive second DCI that indicates a second TCI state to be applied for communications associated with a second CORESET pool index in the second component carrier starting from a second starting time associated with the second DCI. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive, in the first component carrier, third DCI that schedules a downlink communication in the second component carrier. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive the downlink communication in the second component carrier using a default beam in connection with a default beam condition associated with the third DCI, wherein the default beam is determined to be a beam associated with the first TCI state or a beam associated with the second TCI state based at least in part on whether the downlink communication is associated with the first CORESET pool index or the second CORESET pool index.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit, in a first CORESET associated with a first CORESET pool index of multiple CORESET pool indexes configured for a UE, first DCI that indicates a TCI state to be applied starting from a starting time associated with the first DCI. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit a downlink communication scheduled by second DCI using a default beam in connection with a default beam condition associated with the second DCI and in connection with the default beam being associated with the first CORESET pool index.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, in a first CORESET associated with a first CORESET pool index, first DCI that indicates a first TCI state to be applied starting from a first starting time associated with the first DCI. The apparatus may include means for receiving, in a second CORESET associated with a second CORESET pool index, second DCI that indicates a second TCI state to be applied starting from a second starting time associated with the second DCI. The apparatus may include means for receiving third DCI that schedules a downlink communication. The apparatus may include means for receiving the downlink communication using a default beam associated with the first CORESET pool index or the second CORESET pool index in connection with a default beam condition associated with the third DCI.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, in a first component carrier, first DCI that indicates a first TCI state to be applied for communications associated with a first CORESET pool index in a second component carrier starting from a first starting time associated with the first DCI. The apparatus may include means for receiving second DCI that indicates a second TCI state to be applied for communications associated with a second CORESET pool index in the second component carrier starting from a second starting time associated with the second DCI. The apparatus may include means for receiving, in the first component carrier, third DCI that schedules a downlink communication in the second component carrier. The apparatus may include means for receiving the downlink communication in the second component carrier using a default beam in connection with a default beam condition associated with the third DCI, wherein the default beam is determined to be a beam associated with the first TCI state or a beam associated with the second TCI state based at least in part on whether the downlink communication is associated with the first CORESET pool index or the second CORESET pool index.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, in a first CORESET associated with a first CORESET pool index of multiple CORESET pool indexes configured for a UE, first DCI that indicates a TCI state to be applied starting from a starting time associated with the first DCI. The apparatus may include means for transmitting a downlink communication scheduled by second DCI using a default beam in connection with a default beam condition associated with the second DCI and in connection with the default beam being associated with the first CORESET pool index.

DETAILED DESCRIPTION

In some aspects, the UE120may include a communication manager140. As described in more detail elsewhere herein, the communication manager140may receive, in a first control resource set (CORESET) associated with a first CORESET pool index, first downlink control information (DCI) that indicates a first transmission configuration indicator (TCI) state to be applied starting from a first starting time associated with the first DCI; receive, in a second CORESET associated with a second CORESET pool index, second DCI that indicates a second TCI state to be applied starting from a second starting time associated with the second DCI; receive third DCI that schedules a downlink communication; and receive the downlink communication using a default beam associated with the first CORESET pool index or the second CORESET pool index in connection with a default beam condition associated with the third DCI. Additionally, or alternatively, the communication manager140may perform one or more other operations described herein.

In some aspects, as described in more detail elsewhere herein, the communication manager140may receive, in a first component carrier, first DCI that indicates a first TCI state to be applied for communications associated with a first CORESET pool index in a second component carrier starting from a first starting time associated with the first DCI; receive second DCI that indicates a second TCI state to be applied for communications associated with a second CORESET pool index in the second component carrier starting from a second starting time associated with the second DCI; receive, in the first component carrier, third DCI that schedules a downlink communication in the second component carrier; and receive the downlink communication in the second component carrier using a default beam in connection with a default beam condition associated with the third DCI, wherein the default beam is determined to be a beam associated with the first TCI state or a beam associated with the second TCI state based at least in part on whether the downlink communication is associated with the first CORESET pool index or the second CORESET pool index. Additionally, or alternatively, the communication manager140may perform one or more other operations described herein.

In some aspects, a network node (e.g., a base station110, a TRP, or one or more components described in connection withFIG.3) may include a communication manager150. As described in more detail elsewhere herein, the communication manager150may transmit, in a first CORESET associated with a first CORESET pool index of multiple CORESET pool indexes configured for a UE, first DCI that indicates a TCI state to be applied starting from a starting time associated with the first DCI; and transmit a downlink communication scheduled by second DCI using a default beam in connection with a default beam condition associated with the second DCI and in connection with the default beam being associated with the first CORESET pool index. Additionally, or alternatively, the communication manager150may perform one or more other operations described herein.

The controller/processor240of the base station110, the controller/processor280of the UE120, and/or any other component(s) ofFIG.2may perform one or more techniques associated with a default beam for multi-DCI based multi-TRP with a unified TCI, as described in more detail elsewhere herein. For example, the controller/processor240of the base station110, the controller/processor280of the UE120, and/or any other component(s) ofFIG.2may perform or direct operations of, for example, process1500ofFIG.15, process1600ofFIG.16, process1700ofFIG.17, and/or other processes as described herein. The memory242and the memory282may store data and program codes for the base station110and the UE120, respectively. In some examples, the memory242and/or the memory282may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the base station110and/or the UE120, may cause the one or more processors, the UE120, and/or the base station110to perform or direct operations of, for example, process1500ofFIG.15, process1600ofFIG.16, process1700ofFIG.17, and/or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples. In some aspects, a network node described herein is the base station110, is included in the base station110, or includes one or more components of the base station110shown inFIG.2. In some aspects, a TRP described herein is the base station110, is included in the base station110, or includes one or more components of the base station110shown inFIG.2.

In some aspects, the UE120includes means for receiving, in a first CORESET associated with a first CORESET pool index, first DCI that indicates a first TCI state to be applied starting from a first starting time associated with the first DCI; means for receiving, in a second CORESET associated with a second CORESET pool index, second DCI that indicates a second TCI state to be applied starting from a second starting time associated with the second DCI; means for receiving third DCI that schedules a downlink communication; and/or means for receiving the downlink communication using a default beam associated with the first CORESET pool index or the second CORESET pool index in connection with a default beam condition associated with the third DCI.

In some aspects, the UE120includes means for receiving, in a first component carrier, first DCI that indicates a first TCI state to be applied for communications associated with a first CORESET pool index in a second component carrier starting from a first starting time associated with the first DCI; means for receiving second DCI that indicates a second TCI state to be applied for communications associated with a second CORESET pool index in the second component carrier starting from a second starting time associated with the second DCI; means for receiving, in the first component carrier, third DCI that schedules a downlink communication in the second component carrier; and/or means for receiving the downlink communication in the second component carrier using a default beam in connection with a default beam condition associated with the third DCI, wherein the default beam is determined to be a beam associated with the first TCI state or a beam associated with the second TCI state based at least in part on whether the downlink communication is associated with the first CORESET pool index or the second CORESET pool index. The means for the UE120to perform operations described herein may include, for example, one or more of communication manager140, antenna252, modem254, MIMO detector256, receive processor258, transmit processor264, TX MIMO processor266, controller/processor280, or memory282.

In some aspects, a network node includes means for transmitting, in a first CORESET associated with a first CORESET pool index of multiple CORESET pool indexes configured for a UE, first DCI that indicates a TCI state to be applied starting from a starting time associated with the first DCI; and/or means for transmitting a downlink communication scheduled by second DCI using a default beam in connection with a default beam condition associated with the second DCI and in connection with the default beam being associated with the first CORESET pool index. In some aspects, the means for the network node to perform operations described herein may include, for example, one or more of communication manager150, transmit processor220, TX MIMO processor230, modem232, antenna234, MIMO detector236, receive processor238, controller/processor240, memory242, or scheduler246.

FIG.3is a diagram illustrating an example disaggregated base station300architecture. The disaggregated base station300architecture may include one or more CUs310that can communicate directly with a core network320via a backhaul link, or indirectly with the core network320through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC)325via an E2 link, or a Non-Real Time (Non-RT) RIC315associated with a Service Management and Orchestration (SMO) Framework305, or both). A CU310may communicate with one or more DUs330via respective midhaul links, such as an F1 interface. The DUs330may communicate with one or more RUs340via respective fronthaul links. The RUs340may communicate with respective UEs120via one or more radio frequency (RF) access links. In some implementations, the UE120may be simultaneously served by multiple RUs340.

Lower-layer functionality can be implemented by one or more RUs340. In some deployments, an RU340, controlled by a DU330, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s)340can be implemented to handle over the air (OTA) communication with one or more UEs120. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s)340can be controlled by the corresponding DU330. In some scenarios, this configuration can enable the DU(s)330and the CU310to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

FIG.4is a diagram illustrating an example logical architecture of a distributed RAN400, in accordance with the present disclosure.

A 5G access node405may include an access node controller410. The access node controller410may be a CU of the distributed RAN400. In some aspects, a backhaul interface to a 5G core network415may terminate at the access node controller410. The 5G core network415may include a 5G control plane component420and a 5G user plane component425(e.g., a 5G gateway), and the backhaul interface for one or both of the 5G control plane and the 5G user plane may terminate at the access node controller410. Additionally, or alternatively, a backhaul interface to one or more neighbor access nodes430(e.g., another 5G access node405and/or an LTE access node) may terminate at the access node controller410.

The access node controller410may include and/or may communicate with one or more TRPs435(e.g., via an F1 Control (F1-C) interface and/or an F1 User (F1-U) interface). A TRP435may be a DU of the distributed RAN400. In some aspects, a TRP435may correspond to a base station110described above in connection withFIG.1. For example, different TRPs435may be included in different base stations110. Additionally, or alternatively, multiple TRPs435may be included in a single base station110. In some aspects, a base station110may include a CU (e.g., access node controller410) and/or one or more DUs (e.g., one or more TRPs435). In some cases, a TRP435may be referred to as a cell, a panel, an antenna array, or an array.

A TRP435may be connected to a single access node controller410or to multiple access node controllers410. In some aspects, a dynamic configuration of split logical functions may be present within the architecture of distributed RAN400. For example, a PDCP layer, an RLC layer, and/or a MAC layer may be configured to terminate at the access node controller410or at a TRP435.

In some aspects, multiple TRPs435may transmit communications (e.g., the same communication or different communications) in the same transmission time interval (TTI) (e.g., a slot, a mini-slot, a subframe, or a symbol) or different TTIs using different quasi co-location (QCL) relationships (e.g., different spatial parameters, different TCI states, different precoding parameters, and/or different beamforming parameters). In some aspects, a TCI state may be used to indicate one or more QCL relationships. A TRP435may be configured to individually (e.g., using dynamic selection) or jointly (e.g., using joint transmission with one or more other TRPs435) serve traffic to a UE120.

As indicated above,FIG.4is provided as an example. Other examples may differ from what was described with regard toFIG.4.

FIG.5is a diagram illustrating an example500of multi-TRP communication (sometimes referred to as multi-panel communication), in accordance with the present disclosure. As shown inFIG.5, multiple TRPs505may communicate with the same UE120. A TRP505may correspond to a TRP435described above in connection withFIG.4.

The multiple TRPs505(shown as TRP A and TRP B) may communicate with the same UE120in a coordinated manner (e.g., using coordinated multipoint transmissions) to improve reliability and/or increase throughput. The TRPs505may coordinate such communications via an interface between the TRPs505(e.g., a backhaul interface and/or an access node controller410). The interface may have a smaller delay and/or higher capacity when the TRPs505are co-located at the same base station110(e.g., when the TRPs505are different antenna arrays or panels of the same base station110), and may have a larger delay and/or lower capacity (as compared to co-location) when the TRPs505are located at different base stations110. The different TRPs505may communicate with the UE120using different QCL relationships (e.g., different TCI states), different DMRS ports, and/or different layers (e.g., of a multi-layer communication).

In a first multi-TRP transmission mode (e.g., Mode 1), a single physical downlink control channel (PDCCH) may be used to schedule downlink data communications for a single physical downlink shared channel (PDSCH). In this case, multiple TRPs505(e.g., TRP A and TRP B) may transmit communications to the UE120on the same PDSCH. For example, a communication may be transmitted using a single codeword with different spatial layers for different TRPs505(e.g., where one codeword maps to a first set of layers transmitted by a first TRP505and maps to a second set of layers transmitted by a second TRP505). As another example, a communication may be transmitted using multiple codewords, where different codewords are transmitted by different TRPs505(e.g., using different sets of layers). In either case, different TRPs505may use different QCL relationships (e.g., different TCI states) for different DMRS ports corresponding to different layers. For example, a first TRP505may use a first QCL relationship or a first TCI state for a first set of DMRS ports corresponding to a first set of layers, and a second TRP505may use a second (different) QCL relationship or a second (different) TCI state for a second (different) set of DMRS ports corresponding to a second (different) set of layers. In some aspects, a TCI state in DCI (e.g., transmitted on the PDCCH, such as DCI format 1_0 or DCI format 1_1) may indicate the first QCL relationship (e.g., by indicating a first TCI state) and the second QCL relationship (e.g., by indicating a second TCI state). The first and the second TCI states may be indicated using a TCI field in the DCI. In general, the TCI field can indicate a single TCI state (for single-TRP transmission) or multiple TCI states (for multi-TRP transmission as discussed here) in this multi-TRP transmission mode (e.g., Mode 1).

In a second multi-TRP transmission mode (e.g., Mode 2), multiple PDCCHs may be used to schedule downlink data communications for multiple corresponding PDSCHs (e.g., one PDCCH for each PDSCH). In this case, a first PDCCH may schedule a first codeword to be transmitted by a first TRP505, and a second PDCCH may schedule a second codeword to be transmitted by a second TRP505. Furthermore, first DCI (e.g., transmitted by the first TRP505) may schedule a first PDSCH communication associated with a first set of DMRS ports with a first QCL relationship (e.g., indicated by a first TCI state) for the first TRP505, and second DCI (e.g., transmitted by the second TRP505) may schedule a second PDSCH communication associated with a second set of DMRS ports with a second QCL relationship (e.g., indicated by a second TCI state) for the second TRP505. In this case, DCI (e.g., having DCI format 1_0 or DCI format 1_1) may indicate a corresponding TCI state for a TRP505corresponding to the DCI. The TCI field of the DCI indicates the corresponding TCI state (e.g., the TCI field of the first DCI indicates the first TCI state and the TCI field of the second DCI indicates the second TCI state). The second multi-TRP transmission mode (e.g., Mode 2) may also be referred to as “multi-DCI based multi-TRP.”

FIG.6is a diagram illustrating an example600of TRP differentiation at a UE based at least in part on a CORESET pool index, in accordance with the present disclosure. In some aspects, a CORESET pool index (or CORESETPoolIndex) value may be used by a UE (e.g., UE120) to identify a TRP associated with an uplink grant received on a PDCCH.

A CORESET may refer to a control region that is structured to support an efficient use of resources, such as by flexible configuration or reconfiguration of resources for one or more PDCCHs associated with a UE. In some aspects, a CORESET may occupy the first symbol of an orthogonal frequency division multiplexing (OFDM) slot, the first two symbols of an OFDM slot, or the first three symbols of an OFDM slot. Thus, a CORESET may include multiple resource blocks (RBs) in the frequency domain, and either one, two, or three symbols in the time domain. In 5G, a quantity of resources included in a CORESET may be flexibly configured, such as by using RRC signaling to indicate a frequency domain region (for example, a quantity of RBs) or a time domain region (for example, a quantity of symbols) for the CORESET.

As illustrated inFIG.6, a UE120may be configured with multiple CORESETs in a given serving cell. Each CORESET configured for the UE120may be associated with a CORESET identifier (CORESET ID). For example, a first CORESET configured for the UE120may be associated with CORESET ID 1, a second CORESET configured for the UE120may be associated with CORESET ID 2, a third CORESET configured for the UE120may be associated with CORESET ID 3, and a fourth CORESET configured for the UE120may be associated with CORESET ID 4.

As further illustrated inFIG.6, two or more (for example, up to five) CORESETs may be grouped into a CORESET pool. Each CORESET pool may be associated with a CORESET pool index. As an example, CORESET ID 1 and CORESET ID 2 may be grouped into CORESET pool index 0, and CORESET ID 3 and CORESET ID 4 may be grouped into CORESET pool index 1. In a multi-TRP configuration, each CORESET pool index value may be associated with a particular TRP605. As an example, and as illustrated inFIG.6, a first TRP605(TRP A) may be associated with CORESET pool index 0 and a second TRP605(TRP B) may be associated with CORESET pool index 1. The UE120may be configured by a higher layer parameter, such as PDCCH-Config, with information identifying an association between a TRP and a CORESET pool index value assigned to the TRP. Accordingly, the UE120may identify the TRP that transmitted DCI to the UE120by determining the CORESET ID of the CORESET in which the PDCCH carrying the DCI was transmitted, determining the CORESET pool index value associated with the CORESET pool in which the CORESET ID is included, and identifying the TRP associated with the CORESET pool index value. Multi-TRP operation may be defined for the UE120in a given component carrier (CC) by configuring two CORESET pool index values in different CORESETs in an active bandwidth part (BWP) of the CC. In some examples, if a CORESET is not configured with a CORESET pool index value, a CORESET pool index value of 0 may be assumed for that CORESET.

FIG.7is a diagram illustrating an example700of using beams for communications between a base station and a UE, in accordance with the present disclosure. As shown inFIG.7, a base station110and a UE120may communicate with one another.

The base station110may transmit to UEs120located within a coverage area of the base station110. The base station110and the UE120may be configured for beamformed communications, where the base station110may transmit in the direction of the UE120using a directional BS transmit (Tx) beam, and the UE120may receive the transmission using a directional UE receive (Rx) beam. Each BS Tx beam may have an associated beam identifier (ID), beam direction, or beam symbols, among other examples. The base station110may transmit downlink communications via one or more BS Tx beams705.

The UE120may attempt to receive downlink transmissions via one or more UE Rx beams710, which may be configured using different beamforming parameters at Rx circuitry of the UE120. The UE120may identify a particular BS Tx beam705, shown as BS Tx beam705-A, and a particular UE Rx beam710, shown as UE Rx beam710-A, that provide relatively favorable performance (for example, that have a best channel quality of the different measured combinations of BS Tx beams705and UE Rx beams710). In some examples, the UE120may transmit an indication of which BS Tx beam705is identified by the UE120as a preferred BS Tx beam, which the base station110may select for transmissions to the UE120. The UE120may thus attain and maintain a beam pair link (BPL) with the base station110for downlink communications (for example, a combination of the BS Tx beam705-A and the UE Rx beam710-A), which may be further refined and maintained in accordance with one or more established beam refinement procedures.

A downlink beam, such as a BS Tx beam705or a UE Rx beam710, may be associated with a TCI state. A TCI state may indicate a directionality or a characteristic of the downlink beam, such as one or more QCL properties of the downlink beam. A QCL property may include, for example, a Doppler shift, a Doppler spread, an average delay, a delay spread, or spatial receive parameters, among other examples. In some examples, each BS Tx beam705may be associated with a synchronization signal block (SSB), and the UE120may indicate a preferred BS Tx beam705by transmitting uplink transmissions in resources of the SSB that are associated with the preferred BS Tx beam705. A particular SSB may have an associated TCI state (for example, for an antenna port or for beamforming). The base station110may, in some examples, indicate a downlink BS Tx beam705based at least in part on antenna port QCL properties that may be indicated by the TCI state. A TCI state may be associated with one downlink reference signal set (for example, an SSB and an aperiodic, periodic, or semi-persistent channel state information reference signal (CSI-RS)) for different QCL types (for example, QCL types for different combinations of Doppler shift, Doppler spread, average delay, delay spread, or spatial receive parameters, among other examples). In cases where the QCL type indicates spatial receive parameters, the QCL type may correspond to analog receive beamforming parameters of a UE Rx beam710at the UE120. Thus, the UE120may select a corresponding UE Rx beam710from a set of BPLs based at least in part on the base station110indicating a BS Tx beam705via a TCI indication.

The base station110may maintain a set of activated TCI states for downlink shared channel transmissions and a set of activated TCI states for downlink control channel transmissions. The set of activated TCI states for downlink shared channel transmissions may correspond to beams that the base station110uses for downlink transmission on a PDSCH. The set of activated TCI states for downlink control channel communications may correspond to beams that the base station110may use for downlink transmission on a PDCCH or in a CORESET. The UE120may also maintain a set of activated TCI states for receiving the downlink shared channel transmissions and the CORESET transmissions. If a TCI state is activated for the UE120, then the UE120may have one or more antenna configurations based at least in part on the TCI state, and the UE120may not need to reconfigure antennas or antenna weighting configurations. In some examples, a number (e.g., up to 128) TCI states may be configured for the UE120by a configuration message, such as an RRC message, that is transmitted from the base station110to the UE120. In some examples, the base station110may transmit, to the UE120, a MAC control element (MAC-CE) that activates a number (e.g., up to 8) of the configured TCI states for PDSCH. For example, the MAC-CE may indicate a set of activated TCI states for PDSCH for the UE120. The activated TCI states may be mapped to respective TCI codepoints in DCI. In some examples, DCI that schedules a PDSCH communication (e.g., DCI format 1_1 and/or DCI format 1_2) may indicate an activated TCI state, from the set of activated TCI states, via a TCI field included in the DCI. For example, the TCI field of the DCI may include an indication of a TCI codepoint that maps to an activated TCI state to be used by the UE120to receive the scheduled PDSCH communication. In some examples, the indication of the activated TCI in the DCI that schedules a PDSCH communication may not be applicable to PDSCH communications other than the PDSCH communication scheduled by that DCI. In some cases, the TCI field may not be present in scheduling DCI for a PDSCH communication (e.g., based at least in part on RRC configurations tci-PresentinDCI and/or tci-PresentinDCI-1-2, which are included as part of a CORESET configuration). In some examples, if the TCI field is not present in scheduling DCI for a PDSCH communication, the TCI state for the scheduled PDSCH communication follows the TCI state of the scheduling CORESET (e.g., the CORESET in which the scheduling DCI is detected by the UE120).

In some examples, when two CORESET pool index values are configured for a CC (e.g., for multi-TRP operation), separate MAC-CEs may be transmitted to the UE120to activate a number (e.g., up to 8) TCI states per CORESET pool index. For example, a first MAC-CE may indicate a first set of activated TCI states associated with a first CORESET pool index value (e.g., CORESET pool index 0) and a second MAC-CE may indicate a second set of activate TCI states associated with a second CORESET pool index value (e.g., CORESET pool index 1). The first set of activated TCI states associated with the first CORESET pool index value are activated states for communications between the UE120and a first TRP, and the second set of activated TCI states associated with the second CORESET pool index value are activated states for communications between the UE120and a second TRP. In this case, a TCI codepoint in the TCI field of a DCI (e.g., DCI format 1_1 or 1_2) may be interpreted differently (e.g., based on the corresponding MAC-CE) depending on whether the DCI is received in a CORESET associated with the first CORESET pool index value (e.g., CORESET pool index 0) or in a CORESET associated with the second CORESET pool index value (e.g., CORESET pool index 1).

For uplink communications, the UE120may transmit in the direction of the base station110using a directional UE Tx beam, and the base station110may receive the transmission using a directional BS Rx beam. Each UE Tx beam may have an associated beam ID, beam direction, or beam symbols, among other examples. The UE120may transmit uplink communications via one or more UE transmit beams715.

The base station110may receive uplink transmissions via one or more BS Rx beams720. The base station110may identify a particular UE Tx beam715, shown as UE Tx beam715-A, and a particular BS Rx beam720, shown as BS Rx beam720-A, that provide relatively favorable performance (for example, that have a best channel quality of the different measured combinations of UE Tx beams715and BS Rx beams720). In some examples, the base station110may transmit an indication of which UE Tx beam715is identified by the base station110as a preferred UE Tx beam, which the base station110may select for transmissions from the UE120. The UE120and the base station110may thus attain and maintain a BPL for uplink communications (for example, a combination of the UE Tx beam715-A and the BS Rx beam720-A), which may be further refined and maintained in accordance with one or more established beam refinement procedures. In some examples, an uplink beam, such as a UE Tx beam715or a BS Rx beam720, may be associated with a spatial relation. A spatial relation may indicate a directionality or a characteristic of the uplink beam, similar to one or more QCL properties, as described above.

FIG.8is a diagram illustrating an example800of using a default beam for a downlink communication, in accordance with the present disclosure.

As shown inFIG.8, a UE (e.g., UE120) may receive DCI that schedules a PDSCH communication. The PDSCH communication may be scheduled to be transmitted to the UE at a scheduling offset with respect to the DCI that schedules the PDSCH communication. “Scheduling offset” refers to a time offset between the DCI and the PDSCH communication scheduled by the DCI. The DCI may include an indication of a TCI state that identifies the downlink beam (e.g., the UE Rx beam) for the PDSCH communication. The TCI state may indicate a QCL property of a downlink beam in accordance with a QCL type. In some cases (e.g., for communications in FR2), the QCL type may be QCL-TypeD, which indicates spatial receive parameters for the downlink beam. In some examples, in a case in which QCL-TypeD is used (e.g., in FR2), the indicated TCI state in the scheduling DCI for a PDSCH communication may only be applied for the PDSCH communication if the scheduling offset between the scheduling DCI and the scheduled PDSCH communication is equal to or larger than a time duration for QCL (e.g., timeDurationForQCL). The time duration for QCL (e.g., timeDurationForQCL) may be a time duration indicated in or configured based at least in part on UE capability information for the UE. For example, the time duration for QCL (e.g., timeDurationForQCL) may be a time duration in which the UE is capable of decoding DCI and changing an Rx beam of the UE in accordance with an indicated TCI state in the DCI.

As shown inFIG.8, in some cases, the scheduling offset for a scheduled PDSCH communication may be less than the time duration for QCL (e.g., timeDurationForQCL). If the scheduling offset is less than the time duration for QCL (e.g., timeDurationForQCL), a default beam may be used for the PDSCH communication, as there may not be enough time for the UE to decode the DCI and apply an Rx beam corresponding to the TCI state indicated in the DCI. The default beam may be a beam associated with a default QCL assumption (e.g., for QCL-TypeD) for PDSCH.

The UE may be configured with periodic monitoring occasions for search space (SS) sets associated with different CORESETs. In some examples, in a case in which the scheduling offset between a scheduling DCI and a scheduled PDSCH communication is less than the time duration for QCL (e.g., timeDurationForQCL), the default QCL assumption that identifies the default beam for the PDSCH communication may be a QCL/TCI state associated with a CORESET having a lowest CORESET ID among CORESETs with monitored SS sets in a latest slot in which one or more CORESETs within an active BWP of a serving cell are monitored by the UE. That is, the default beam for a PDSCH communication with a scheduling offset that is less than the time duration for QCL may be the beam associated with a monitored CORESET having the lowest CORESET ID in the latest slot (with respect to the slot in which the PDSCH communication is scheduled) in which one or more CORESETs are monitored by the UE. In some examples, the UE may use the TCI state of the monitored CORESET ID in the latest slot in which one or more CORESETs are monitored to determine the default QCL assumption for a PDSCH communication with a scheduling offset that is less than the time duration for QCL in cases in which the UE is not configured with two CORESET pool index values and/or in cases in which the UE is configured with two CORESET pool index values, but the UE is not configured with two default beams enabled for the two CORESET pool index values (e.g., respective default beams enabled for the two CORESET pool index values).

When two CORESET pool index values are configured for a CC, the UE may indicate the capability of the UE to use to default beams (e.g., a respective default beam per CORESET pool index value). In some cases, the UE may be configured (e.g., via RRC signaling) to enable respective default beams for the two CORESET pool index values. For example, an RRC parameter enableDefaultTCI-StateperCoresetPoolIndex may indicate whether the UE is configured with two default beams enabled for the two CORESET pool index values. In the case in which two CORESET pool index values are configured for a UE (e.g., multi-TRP operation), and the UE is configured with two default beams enabled for the two CORESET pool index values, the default QCL assumption for a PDSCH communication associated with a CORESET index pool value (e.g., based at least in part on the CORESET pool index value of the PDCCH communication including the DCI that scheduled the PDSCH communication) may be a QCL/TCI state associated with a CORESET having a lowest CORESET ID among CORESETs associated with the same CORESET index pool value as the PDSCH communication with monitored SS sets in a latest slot in which one or more CORESETs associated with that CORESET index poll value within the active BWP of the serving cell are monitored by the UE. That is, the default beam for a PDSCH communication associated with a CORESET index pool value may be the beam associated with the CORESET having the lowest CORESET ID among monitored CORESETs associated with the index pool value in a latest slot in which one or more CORESETs associated with the index pool value are monitored.

FIG.9is a diagram illustrating an example900of using a unified TCI beam indication, in accordance with the present disclosure.

As described above in connection withFIG.7, in some examples, a TCI state may be used for a downlink beam indication, and a spatial relation may be used for an uplink beam indication. Such beam indications may be referred to herein as “non-unified beam indications.” Non-unified beam indications may be applied to one channel for one communication scheduled in that channel.

In some examples, a base station (e.g., base station110) and a UE (e.g., UE120) may use a unified TCI framework for both downlink and uplink beam indications. In the unified TCI framework, TCI state indications may be used to indicate a joint downlink and uplink TCI state or to indicate separate downlink and uplink TCI states. Such a TCI state indication that may be used to indicate a joint downlink and uplink beam, a separate downlink beam, or a separate uplink beam is referred to herein as a “unified TCI state indication.” A unified TCI state indication (e.g., a joint downlink and uplink TCI state indication and/or separate downlink and uplink TCI state indications) may be applied to multiple channels. For example, the unified TCI state indication of a joint uplink and downlink TCI state may be used to indicate a beam direction for one or more downlink channels (e.g., PDSCH and/or PDCCH) or reference signals (e.g., CSI-RS) and for one or more uplink channels (e.g., physical uplink shared channel (PUSCH) and/or physical uplink control channel (PUCCH)) or reference signals (e.g., a sounding reference signal (SRS)). The unified TCI state indication of a separate downlink TCI state may be used to indicate a beam direction for multiple downlink channels (e.g., PDSCH and PDCCH) or reference signals (e.g., CSI-RS). The unified TCI state indication of a separate uplink TCI state may be used to indicate a beam direction to be used for multiple uplink channels (e.g., PUSCH and PUCCH) or reference signals (e.g., SRS). In some examples, the unified TCI state indication may be “sticky,” such that the indicated beam direction will be used for the channels and/or reference signals to which the TCI state indication applies until a further indication is received.

In some examples, there may be two TCI state indication modes in the unified TCI state framework. A first mode may be a separate downlink and uplink TCI state indication mode, in which separate downlink and uplink TCI states are used to indicate downlink and uplink beam directions for the UE. For example, the separate downlink and uplink TCI state indication mode may be used when the UE is having maximum permissible exposure (MPE) issues to indicate different beam directions, for the UE, for an uplink beam (e.g., a UE Tx beam) and a downlink beam (e.g., a UE Rx beam). A second mode may be a joint downlink and uplink TCI state indication mode, in which a TCI state indication is used to indicate, to the UE, a joint uplink and downlink beam direction. For example, the joint downlink and uplink TCI state indication mode may be used when the UE has channel correspondence between downlink and uplink channels (which may be assumed in some examples), and the same beam direction can be used for an uplink beam (e.g., a UE Tx beam) and a downlink beam (e.g., a UE Rx beam).

In some examples, in the unified TCI state framework, downlink TCI states, uplink TCI states, and/or joint downlink and uplink TCI states may be configured for a UE via RRC signaling from a base station. A MAC-CE, transmitted from the base station to the UE, may activate a number of the RRC-configured TCI states and indicate a mapping of TCI field codepoints. In some examples, one TCI field codepoint may represent a joint downlink and uplink TCI state, and the TCI field codepoint may be used for a joint downlink and uplink beam indication. In some examples, one TCI field may represent a pair of TCI states including a downlink TCI state and an uplink TCI state, and the TCI field codepoint may be used for a separate downlink and uplink beam indication. In some examples, one TCI field codepoint may represent only a downlink TCI state, and the TCI field codepoint may be used for a downlink only beam indication. In some examples, one TCI field codepoint may represent only an uplink TCI state, and the TCI field codepoint may be used for an uplink only beam indication. If the MAC-CE indicates a mapping to only a single TCI field codepoint, the MAC-CE may serve as the beam indication. In this case, the UE may begin applying the beam indication indicated in the MAC-CE a certain time duration (e.g., 3 ms) after a hybrid automatic repeat request acknowledgement (HARQ-ACK) transmitted to the base station in response to the PDSCH communication carrying the MAC-CE.

If the MAC-CE indicates a mapping to more than one TCI field codepoint, DCI including an indication of a TCI field codepoint may be used to provide a beam indication to the UE. As shown inFIG.9, and by reference number905, the UE may receive (e.g., via a PDCCH communication) DCI that includes an indication of a TCI field codepoint. The TCI field codepoint may map to a unified TCI state indication, which may correspond to a joint downlink and uplink TCI state, a separate downlink and uplink TCI state pair, a downlink only TCI state, or an uplink only TCI state. In some aspects, DL DCI (e.g., DCI format 1_1/1_2), with or without a downlink assignment, may be used to provide the beam indication (e.g., the indication of the TCI field codepoint). The DCI that includes the indication of the TCI field codepoint may be referred to a “beam indication DCI.”

As further shown inFIG.9, the UE may transmit, to the base station, a PUCCH communication that includes a HARQ-ACK in response to the DCI including the TCI field codepoint (e.g., the beam indication DCI). As shown by reference number910, the UE may apply the beam indication starting in a first slot that is at least Y symbols after a last symbol of the PUCCH communication carrying the HARQ-ACK feedback transmitted in response to the beam indication DCI. For example, Y may be configured for the UE (e.g., via RRC signaling) based at least in part on UE capability. The beam indication may be applied to downlink channels and reference signals (e.g., PDSCH, PDCCH, and CSI-RS), uplink channels and reference signals (e.g., PUSCH, PUCCH, and SRS), or both downlink and uplink channels and reference signals, depending on the type of TCI field codepoint. The beam indication (e.g., the unified TCI state indication) may be “sticky.” That is, the beam indication is not specific to a scheduled PDSCH communication, but instead once the UE starts applying the beam indication, the UE may continue to use indicated beam for the applicable channels and reference signals until the UE receives another beam indication DCI (e.g., another DCI format 1_1/1_2 including a TCI field codepoint) that changes the beam.

As indicated above,FIG.9is provided as an example. Other examples may differ from what is described with respect toFIG.9.

FIG.10is a diagram illustrating an example1000of using unified TCI beam indications for multi-DCI based multi-TRP communications, in accordance with the present disclosure.

In some aspects, the unified TCI framework may be extended to multi-TRP communications including multi-DCI based multi-TRP. In the case of multi-DCI based multi-TRP, separate unified TCI beam indications for multiple downlink and/or uplink channels and signals may be transmitted to a UE (e.g., UE120) for channels and signals associated with different CORESET pool index values. As shown inFIG.10, UE may communicate with a first TRP (TRP1) and a second TRP (TRP2) in a multi-DCI multi-TRP mode. TRP1 may be associated with a first CORESET pool index (CORESET pool index 0), and TRP2 may be associated with a second CORESET pool index (CORESET pool index 1).

As shown by reference number1005, the UE may receive, from TRP1, first beam indication DCI that includes a TCI field codepoint that indicates a first unified TCI state (e.g., TCI state 1) to be applied to multiple downlink and/or uplink channels and signals associated with CORESET pool index 0 (e.g., for communications between TRP1 and the UE). The UE may receive a PDCCH communication carrying the first beam indication DCI in a CORESET associated with CORESET pool index 0. The first beam indication DCI may be DCI format 1_1 or 1_2, with or without a downlink assignment (e.g., with or without PDSCH scheduling). The TCI field codepoint may map to a unified TCI state (e.g., TCI state 1), from a set of activated TCI states associated with CORESET pool index 0 for the UE. For example, the TCI field codepoint included in the first beam indication may map to a joint downlink and uplink TCI state, a separate downlink and uplink TCI state pair, a downlink only TCI state, or an uplink only TCI state. The UE may transmit, to TRP1, a PUCCH communication that includes HARQ-ACK feedback for the first beam indication DCI. As shown by reference number1010, the UE may apply TCI state 1 (e.g., the TCI state indicated in the first beam indication DCI) starting in a first slot that is at least Y symbols after a last symbol of the PUCCH communication carrying the HARQ-ACK feedback transmitted in response to the first beam indication DCI. For example, Y may be configured for the UE (e.g., via RRC signaling) based at least in part on UE capability. TCI state 1 may be applied to downlink and/or uplink channels and reference signals associated with CORESET pool index 0 (e.g., including CORESETs associated with CORESET pool index 0). The indication of the unified TCI state (e.g., TCI state 1) in the first beam indication may be “sticky,” such that the indicated TCI state will be used for the channels and/or reference signals to which the TCI state indication applies until another beam indication DCI associated with CORESET pool index 0 is received by the UE.

As shown by reference number1015, the UE may receive, from TRP2, second beam indication DCI that includes a TCI field codepoint that indicates a second unified TCI state (e.g., TCI state 2) to be applied to multiple downlink and/or uplink channels and signals associated with CORESET pool index 1 (e.g., for communications between TRP2 and the UE). The UE may receive a PDCCH communication carrying the second beam indication DCI in a CORESET associated with CORESET pool index 1. The second beam indication DCI may be DCI format 1_1 or 1_2, with or without a downlink assignment (e.g., with or without PDSCH scheduling). The TCI field codepoint may map to a unified TCI state (e.g., TCI state 2), from a set of activated TCI states associated with CORESET pool index 1 for the UE. For example, the TCI field codepoint included in the second beam indication may map to a joint downlink and uplink TCI state, a separate downlink and uplink TCI state pair, a downlink only TCI state, or an uplink only TCI state. The UE may transmit, to TRP2, a PUCCH communication that includes HARQ-ACK feedback for the second beam indication DCI. As shown by reference number1020, the UE may apply TCI state 2 (e.g., the TCI state indicated in the second beam indication DCI) starting in a first slot that is at least Y symbols after a last symbol of the PUCCH communication carrying the HARQ-ACK feedback transmitted in response to the second beam indication DCI. TCI state 2 may be applied to downlink and/or uplink channels and reference signals associated with CORESET pool index 1 (e.g., including CORESETs associated with CORESET pool index 1). The indication of the unified TCI state (e.g., TCI state 2) in the second beam indication may be “sticky,” such that the indicated TCI state will be used for the channels and/or reference signals to which the TCI state indication applies until another beam indication DCI associated with CORESET pool index 1 is received by the UE.

The UE may receive, from TRP1 or TRP2, scheduling DCI (e.g., DCI format 1_1 or 1_2) that schedules a PDSCH communication to the UE. For example, the UE may receive scheduling DCI from TRP1 in a CORESET associated with CORESET pool index 0, or the UE may receive scheduling DCI from TRP2 in a CORESET associated with CORESET pool index 1. In cases in which QCL-TypeD (e.g., FR2) is used, when the scheduling offset between the scheduling DCI and the scheduled PDSCH communication is less than a time duration for QCL (e.g., timeDurationForQCL), the UE may use a default beam for receiving the scheduled PDSCH communication. When the UE is configured with two default beams (e.g., respective default beams for the two CORESET pool index values) enabled (e.g., by enableDefaultTCI-StatePerCoresetPoolIndex), the default beam for receiving the scheduled PDSCH communication may be a beam associated with a monitored CORESET associated with the same CORESET pool index as the scheduled PDSCH (e.g., a beam associated with the same CORESET pool index as the PDCCH communication carrying the scheduling DCI that scheduled the PDSCH communication), as described above in connection withFIG.8. However, the UE may not be configured with two default beams (e.g., a respective default beam per CORESET pool index) enabled for multi-DCI based multi-TRP. For example, the UE may not be configured with two default beams enabled in a case in which the UE is not capable of receiving two different beams simultaneously and/or in a case in which the UE does not indicate the capability to use two default beams to a base station (e.g., via TRP1 or TRP2). In some cases, the UE may be capable of using two default beams, but a base station may not configure the UE with two default beams enabled, for example to reduce power consumption associated with the UE buffering on two default beams.

In some examples, in a case in which the UE is not configured with two default beams (e.g., respective default beams for the two CORESET pool indexes) enabled for multi-DCI based multi-TRP, the default beam for a scheduled PDSCH communication with a scheduling offset that is less than the time duration for QCL (e.g., timeDurationForQCL) may be a beam associated with a monitored CORESET having the lowest CORESET ID in the latest slot (with respect to the slot in which the PDSCH communication is scheduled) in which one or more CORESETs are monitored by the UE. As shown inFIG.10, and by reference number1025, the UE may be configured with monitoring occasions for search space sets associated with a first CORESET with a CORESET ID of 1 and monitoring occasions of SS sets associated with a second CORESET with a CORESET ID of 3. The first CORESET (e.g., CORESET ID=1) may be associated with CORESET pool index 0, and the second CORESET (e.g., CORESET ID=3) may be associated with CORESET pool index 1. The default beam for a PDSCH communication scheduled in a given slot may be determined using the QCL assumption of the CORESET with the lowest CORESET ID in the latest monitored slot (e.g., the latest slot in which one or more CORESETs are monitored by the UE). As shown by reference number1030, if the PDSCH communication is scheduled in a slot in which the first CORESET (e.g., CORESET ID=1) and the second CORESET are both monitored by the UE, the default beam used for the PDSCH communication is a beam associated with the first CORESET, which has a lower CORESET ID than the second CORESET. If the PDSCH communication is scheduled in a slot in which only the second CORESET is monitored by the UE, the default beam for the PDSCH communication is the beam associated with the second CORESET. If the PDSCH communication is scheduled in a slot in which no CORESET is monitored by the UE, the default beam for the PDSCH communication is the beam associated with the monitored CORESET with the lowest CORESET ID in a latest slot, prior to the slot in which the PDSCH communication is scheduled, in which one or more CORESETs are monitored by the UE. If the default beam is the beam associated with the first CORESET, which is associated with CORESET pool index 0, the scheduled PDSCH communication is transmitted to the UE from TRP1. If the default beam is the beam associated with the second CORESET, which is associated with CORESET pool index 1, the scheduled PDSCH communication is transmitted to the UE from TRP2.

As described above, in the case in which the UE is not configured with two default beams enabled for multi-DCI based multi-TRP, the default beam for a PDSCH communication may be a beam that follows the QCL assumption of the CORESET with the lowest CORESET ID in the latest monitored slot, irrespective of the CORESET pool index association. In this case, the default beam for the PDSCH communication is a function of the SS set monitoring periodicity associated with different CORESETs, and whether the default beam is from TRP1 or TRP2 depends on whether the CORESET with the lowest CORESET ID in the latest monitored slot (e.g., the latest slot in which an SS set for at least one CORESET is monitored for PDCCH) is associated with CORESET pool index 0 or CORESET pool index 1. Thus, the network may not have the flexibility or control to schedule a PDSCH communication with a scheduling offset less than the time duration for QCL from one of the TRPs in a given slot, irrespective of the SS set and CORESET configurations. This may result in reduced reliability for PDSCH communications and decreased network throughput due to reduced scheduling flexibility.

Some techniques and apparatuses described herein enable a UE to receive, in a first CORESET associated with a first CORESET pool index, first DCI that indicates a first TCI state to be applied starting from a first starting time associated with the first DCI, and receive, in a second CORESET associated with a second CORESET pool index, second DCI that indicates a second TCI state to be applied starting from a second starting time associated with the second DCI. The UE may receive third DCI that schedules a downlink communication, and the UE may receive the downlink communication using a default beam associated with the first CORESET pool index or the second CORESET pool index in connection with a default beam condition associated with the third DCI. In some aspects, a determination of whether the default beam is associated with the first CORESET pool index or the second CORESET pool index may be independent of SS set and CORESET configurations for the UE. As a result, flexibility for scheduling PDSCH communications with scheduling offset less than a time duration threshold from a first TRP or a second TRP may be increased, which may result in improved reliability of PDSCH communications and increased network throughput.

As indicated above,FIG.10is provided as an example. Other examples may differ from what is described with respect toFIG.10.

FIG.11is a diagram illustrating an example1100associated with a default beam for multi-DCI based multi-TRP with a unified TCI, in accordance with the present disclosure. As shown inFIG.11, example1100includes a first TRP1105-1, a second TRP1105-2, and a UE120. In some aspects, the TRPs1105and UE120may be included in a wireless network, such as wireless network100. The TRPs1105and the UE120may communicate via a wireless access link, which may include an uplink and a downlink.

In some aspects, the TRPs1105may communicate with the UE120using multi-DCI based multi-TRP communications. In some aspects, the first TRP1105-1may be associated with a first CORESET pool index (e.g., CORESET pool index 0), and the second TRP1105-2may be associated with a second CORESET pool index (e.g., CORESET pool index 1). The UE120may be configured with one or more CORESETs associated with the first CORESET pool index (e.g., CORESET pool index 0) and one or more CORESETs associated with the second CORESET pool index (e.g., CORESET pool index 1). In some aspects, the UE120may not be configured with respective default beams enabled for the first CORESET pool index and the second CORESET pool index (e.g., the UE120may not be configured with two default beams). For example, the RRC parameter enableDefaultTCI-StatePerCoresetPoolIndex may not be configured for the UE120.

As shown inFIG.11, and by reference number1110, the UE120may receive first beam indication DCI (e.g., “first DCI”) associated with the first CORESET pool index. The UE120may receive the first beam indication DCI in a CORESET associated with the first CORESET pool index. The first TRP1105-1may transmit the first beam indication DCI to the UE120in a PDCCH communication in a CORESET associated with the first CORESET pool index.

In some aspects, the first beam indication DCI may be DCI format 1_1 or 1_2, with or without scheduling information for a downlink communication (e.g., a PDSCH communication). The first beam indication DCI may indicate a first TCI state (e.g., a first unified TCI state) to be applied, for communications associated with the first CORESET pool index (e.g., communications between the first TRP1105-1and the UE120), starting from a first starting time associated with the first beam indication DCI. In some aspects, the first starting time associated with the first beam indication DCI may be a first slot at least Y symbols after a last symbol of a PUCCH communication including HARQ-ACK feedback associated with the first beam indication DCI. For example, the number of symbols Y used to determine the starting time may be configured for the UE120via RRC signaling. In some aspects, the first TCI state indicated by the first beam indication DCI may be “sticky,” and may be applied for downlink channels (e.g., PDSCH and PDCCH) and downlink reference signals (e.g., CSI-RS) (or for downlink and uplink channels and reference signals) associated with the first CORESET pool index until another beam indication DCI associated with the first CORESET pool index is transmitted to the UE120by the first TRP1105-1.

The first beam indication DCI may include, in a TCI field of the first beam indication DCI, a TCI field codepoint that indicates a unified TCI state (e.g., a downlink TCI state or a joint downlink and uplink TCI state) to be applied starting from the first starting time for communications associated with the first CORESET pool index. The TCI field codepoint may map to an activated TCI state from a set of activated TCI states associated with the first CORESET pool index for the UE120. For example, the TCI field codepoint included in the first beam indication may map to a joint downlink and uplink TCI state, a pair of TCI states including separate downlink and uplink TCI states, or a downlink only TCI state. The set of activated states associated with the first CORESET pool index may be indicated in a MAC-CE transmitted to the UE120from the first TRP1105-1. In some aspects, the UE120may determine that the TCI field codepoint included in the first beam indication DCI maps to a TCI state from the set of activated TCI states associated with the first CORESET pool index based at least in part on receiving the first beam indication DCI in a CORESET associated with the first CORESET pool index.

As shown inFIG.11, and by reference number1115, the UE120may receive second beam indication DCI (e.g., “second DCI”) associated with the second CORESET pool index. The UE120may receive the second beam indication DCI in a CORESET associated with the second CORESET pool index. The second TRP1105-2may transmit the second beam indication DCI to the UE120in a PDCCH communication in a CORESET associated with the second CORESET pool index.

In some aspects, the second beam indication DCI may be DCI format 1_1 or 1_2, with or without scheduling information for a downlink communication (e.g., a PDSCH communication). The second beam indication DCI may indicate a second TCI state (e.g., a second unified TCI state) to be applied, for communications associated with the second CORESET pool index (e.g., communications between the second TRP1105-2and the UE120), starting from a second starting time associated with the second beam indication DCI. In some aspects, the second starting time associated with the second beam indication DCI may be a first slot at least Y symbols after a last symbol of a PUCCH communication including HARQ-ACK feedback associated with the second beam indication DCI. In some aspects, the second TCI state indicated by the second beam indication DCI may be “sticky,” and may be applied for downlink channels (e.g., PDSCH and PDCCH) and downlink reference signals (e.g., CSI-RS) (or for downlink and uplink channels and reference signals) associated with the second CORESET pool index until another beam indication DCI associated with the second CORESET pool index is transmitted to the UE120by the second TRP1105-2.

The second beam indication DCI may include, in a TCI field of the second beam indication DCI, a TCI field codepoint that indicates a unified TCI state (e.g., a downlink TCI state or a joint downlink and uplink TCI state) to be applied starting from the second starting time for communications associated with the second CORESET pool index. The TCI field codepoint may map to an activated TCI state from a set of activated TCI states associated with the second CORESET pool index for the UE120. For example, the TCI field codepoint included in the second beam indication may map to a joint downlink and uplink TCI state, a pair of TCI states including separate downlink and uplink TCI states, or a downlink only TCI state. The set of activated states associated with the second CORESET pool index may be indicated in a MAC-CE transmitted to the UE120from the second TRP1105-2. In some aspects, the UE120may determine that the TCI field codepoint included in the second beam indication DCI maps to a TCI state from the set of activated TCI states associated with the second CORESET pool index based at least in part on receiving the second beam indication DCI in a CORESET associated with the second CORESET pool index.

As further shown inFIG.11, and by reference number1120, the UE120may receive scheduling DCI (e.g., “third DCI”) that schedules a downlink communication (e.g., a PDSCH communication) to be transmitted to the UE120. For example, the first TRP1105-1may transmit the scheduling DCI to the UE120in a CORESET associated with the first CORESET pool index, or the second TRP1105-2may transmit the scheduling DCI to the UE120in a CORESET associated with the second CORESET pool index.

As further shown inFIG.11, and by reference number1125, the UE120may detect a default beam condition associated with the scheduling DCI. The default beam condition associated with the scheduling DCI may be a condition that triggers the use of a default beam for receiving the scheduled downlink communication (e.g., PDSCH communication) by the UE120.

In some aspects, the UE120may detect the default beam condition in connection with a determination that a scheduling offset between the scheduling DCI and the scheduled downlink communication (e.g., PDSCH communication) is less than a time duration threshold. In some aspects, the time duration threshold may be the time duration for QCL (e.g., timeDurationforQCL). For example, when QCL-TypeD is used (e.g., in FR2), the UE120may detect the default beam condition in connection with a determination that the scheduling offset between the scheduling DCI and the scheduled downlink communication (e.g., PDSCH communication) is less than the time duration for QCL (e.g., timeDurationForQCL). The time duration for QCL (e.g., timeDurationForQCL) may be a time duration indicated in or configured based at least in part on UE capability information for the UE120.

As further shown inFIG.11, and by reference number1130, the UE120may receive the scheduled downlink communication (e.g., PDSCH communication) using a default beam associated with the first CORESET pool index or the second CORESET pool index. When the default beam for the scheduled downlink communication is a beam associated with the first CORESET pool index, the first TRP1105-1may transmit the scheduled downlink communication to the UE120, and the UE120may receive the scheduled downlink communication from the first TRP1105-1, using the default beam. When the default beam for the scheduled downlink communication is a beam associated with the second CORESET pool index, the second TRP1105-2may transmit the scheduled downlink communication to the UE120, and the UE120may receive the scheduled downlink communication from the second TRP1105-2, using the default beam.

The UE120, in connection with detecting the default beam condition associated with the scheduling DCI, may determine the default beam to use to receive the downlink communication (e.g., PDSCH communication) scheduled by the scheduling DCI. In some aspects, the UE120may not be configured with respective beams enabled for the first CORESET pool index and the second CORESET pool index. In some aspects, the default beam may be a latest indicated beam associated with a fixed CORESET pool index value. That is, the default beam may be a beam corresponding to a latest indicated TCI state associated with a fixed CORESET pool index. In this case, the fixed CORESET pool index may the first CORESET pool index or the second CORESET pool index. For example, the fixed CORESET pool index may be the first CORESET pool index, and the latest indicated TCI state associated with the first CORESET pool index may be the first TCI state indicated in the first beam indication DCI. In this case, the default beam may be a beam associated with the first TCI state indicated in the first beam indication DCI. In another example, the fixed CORESET pool index may be the second CORESET pool index, and the latest indicated TCI state associated with the second CORESET pool index may be the second TCI state indicated in the second beam indication DCI. In this case, the default beam may be a beam associated with the second TCI state indicated in the second beam indication DCI. In aspects in which the default beam is the latest indicated beam associated with the fixed CORESET pool index, the default beam will be associated with the same TRP in all slots (e.g., the TRP associated with the fixed CORESET pool index). In some aspects, the fixed CORESET pool index may be specified in a wireless communication standard (e.g., a 3GPP standard) or configured for the UE120(e.g., via RRC signaling). In some aspects, the fixed CORESET pool index may be CORESET pool index 0.

In some aspects, the default beam may be a beam associated with a CORESET with a lowest CORESET identifier among one or more CORESETs associated with a fixed CORESET pool index monitored in a latest slot in which at least one CORESET associated with the fixed CORESET pool index is monitored. In this case, the UE120may consider only CORESETs associated with the fixed CORESET pool index when determining the lowest CORESET ID among the monitored CORESET. In this way, the default beam is always associated with the same TRP (e.g., the TRP associated with the fixed CORESET pool index). The fixed CORESET pool index may be the first CORESET pool index or the second CORESET pool index. In some aspects, the fixed CORESET pool index may be specified in a wireless communication standard (e.g., a 3GPP standard) or configured for the UE120(e.g., via RRC signaling).

In some aspects, the UE120may determine whether the default beam is associated with the first CORESET pool index or the second CORESET pool index based at least in part on a pattern in a time domain. For example, the UE120may compare a slot in which the downlink communication is scheduled with the pattern in the time domain to determine whether the default beam for the downlink communication is associated with the first CORESET pool index or the second CORESET pool index. In some aspects, the pattern in the time domain for determining whether the default beam is associated with the first CORESET pool index or the second CORESET pool index may be independent with respect to the configuration of search space sets for CORESETs associated with the first CORESET pool index and the second CORESET pool index. In some aspects, the pattern may be a slot-level pattern that identifies a first set of slots in which the default beam is associated with the first CORESET pool index and a second set of slots in which the default beam is associated with the second CORESET pool index. The slot-level pattern may be based at least in part on a slot number. For example, the default beam for a downlink communication (e.g., PDSCH communication) may be associated with the first CORESET pool index (e.g., CORESET pool index 0) in even slots and associated with the second CORESET pool index (e.g., CORESET pool index 1) in odd slots. In some aspects, the slot-level pattern may be based at least in part on an absolute slot number, and in some aspects, the slot-level pattern may be based at least is part on relative slot number relative to a slot in which a beam indication with a given CORESET pool index is applied (e.g., relative to a slot in which the first TCI state or the second TCI state is applied).

In some aspects, the time domain (e.g., slot-level) pattern for determining whether the default beam is associated with the first CORESET pool index or the second CORESET pool index may be configured for the UE120via RRC signaling. For example, the UE120may receive a configuration of the pattern in one or more RRC messages (e.g., from the first TRP1105-1and/or the second TRP1105-2) that indicate a first set of slots in which the default beam is associated with the first CORESET pool index and/or a second set of slots in which the default beam is associated with the second CORESET pool index. In some aspects, a pattern of the slots in which the default beam is associated with the first CORESET pool index and a pattern of the slots in which the default beam is associated with the second CORESET pool index may be separately configured for the UE120(e.g., in separate RRC messages from the first TRP1105-1and the second TRP1105-2). In some aspects, the pattern of slots for the default beam may be configured for one CORESET pool index (e.g., CORESET pool index 1) (e.g., in an RRC message from the corresponding TRP), and the UE120may determine that the default beam is associated with the other CORESET pool index (e.g., CORESET pool index 0) in slots not included in the configured pattern of slots.

In some aspects, that pattern for determining whether the default beam is associated with the first CORESET pool index or the second CORESET pool index may be indicated in a MAC-CE that indicates the set of activated TCI states for the at least one of the first CORESET pool index or the second CORESET pool index. In this case, the pattern may be common to all TCI field codepoints indicated in the MAC-CE, and independent of the beam indication DCI and the specific TCI codepoint included in the beam indication DCI. For example, the UE120may receive an indication of a pattern of slots in which the default beam is associated with the first CORESET pool index in a MAC-CE (e.g., transmitted by the first TRP1105-1) that indicates the set of activated TCI states associated with the first CORESET pool index. Additionally, or alternatively, the UE120may receive an indication of a pattern of slots in which the default beam is associated with the second CORESET pool index in a MAC-CE (e.g., transmitted by the second TRP1105-2) that indicates the set of activated TCI states associated with the second CORESET pool index.

In some aspects, the pattern of slots in which the default beam is associated with a CORESET pool index may be indicated as part of the TCI codepoint in the beam indication DCI associated with that CORESET pool index. In this case, the MAC-CE that indicates the set of activated TCI states associated with that CORESET pool index may indicate a set of TCI field codepoints and a mapping between each TCI field codepoints, of the set of TCI field codepoints, and a respective TCI state and pattern of slots for which the default beam is associated with that CORESET pool index. For example, the first beam indication DCI may include an indication of a TCI codepoint that indicates the first TCI state and a pattern for a first set of slots in which the default beam is associated with the first CORESET pool index. In this case, the UE120may receive a MAC-CE (e.g., from the first TRP1105-1) that indicates a set of TCI codepoints for the first CORESET pool index and a mapping between each TCI codepoint of the set of TCI codepoints for the first CORESET pool index and a respective TCI state and pattern combination. Additionally, or alternatively, the second beam indication DCI may include an indication of a TCI codepoint that indicates the second TCI state and a pattern for a second set of slots in which the default beam is associated with the second CORESET pool index. In this case, mappings between TCI codepoints for the second CORESET pool index and respective TCI state and pattern combinations may be included in the MAC-CE that indicates the set of activated TCI states associated with the second CORESET pool index.

In some aspects, the UE120may receive separate indications (e.g., via RRC signaling, MAC-CE, or DCI) of a pattern of slots in which the default beam is associated with the first CORESET pool index and a pattern of slots in which the default beam is associated with the second CORESET pool index. In some aspects, the UE120may receive an indication (e.g., via RRC signal, MAC-CE, or DCI) of a pattern of slots for which the default beam is associated with one CORESET pool index, and the UE120may determine that the default beam is associated with the other CORESET pool index in slots not included in indicated the pattern of slots.

In a case in which the UE120determines, based at least in part on the pattern in the time domain, that the default beam for the scheduled downlink communication (e.g., PDSCH communication) is associated with the first CORESET pool index, the default beam may a beam associated with the first TCI state indicated in the first beam information (e.g., the latest indicated TCI state in beam forming DCI associated the first CORESET pool index). In a case in which the UE120determines, based at least in part on the pattern in the time domain, that the default beam for the scheduled downlink communication (e.g., PDSCH communication) is associated with the second CORESET pool index, the default beam may a beam associated with the second TCI state indicated in the second beam information (e.g., the latest indicated TCI state in beam forming DCI associated the second CORESET pool index).

As described above, the UE120may receive, in a first CORESET associated with a first CORESET pool index, first DCI that indicates a first TCI state to be applied starting from a first starting time associated with the first DCI, and the UE120may receive, in a second CORESET associated with a second CORESET pool index, second DCI that indicates a second TCI state to be applied starting from a second starting time associated with the second DCI. The UE120may receive third DCI that schedules a downlink communication, and the UE120may receive the downlink communication using a default beam associated with the first CORESET pool index or the second CORESET pool index in connection with a default beam condition associated with the third DCI. In some aspects, a determination of whether the default beam is associated with the first CORESET pool index or the second CORESET pool index may be independent of SS set and CORESET configurations for the UE120. As a result, flexibility for scheduling PDSCH communications with scheduling offset less than a time duration threshold from a first TRP or a second TRP may be increased, which may result in improved reliability of PDSCH communications and increased network throughput.

As indicated above,FIG.11is provided as an example. Other examples may differ from what is described with respect toFIG.11.

FIG.12is a diagram illustrating an example1200associated with a default beam for multi-DCI based multi-TRP with a unified TCI, in accordance with the present disclosure. As shown inFIG.12, example1200includes multi-DCI based multi-TRP communications between a UE, a first TRP (TRP1), and a second TRP (TRP2). TRP1 may be associated with a first CORESET pool index (CORESET pool index 0), and TRP2 may be associated with a second CORESET pool index (CORESET pool index 1). The UE may be configured without respective default beams (e.g., two default beams) enabled for CORESET pool index 0 and CORESET pool index 1.

As shown inFIG.12, and by reference number1205, the UE may receive, from TRP1, first beam indication DCI that includes a TCI field codepoint that indicates a first TCI state (e.g., TCI state 1) to be applied to channels and signals associated with CORESET pool index 0 (e.g., for communications between TRP1 and the UE) starting from a starting time associated with the first beam indication DCI. The UE may receive the first beam indication DCI in a CORESET associated with CORESET pool index 0. The first beam indication DCI may be DCI format 1_1 or 1_2, with or without PDSCH scheduling. The TCI field codepoint may map to a TCI state (e.g., TCI state 1), from a set of activated TCI states associated with CORESET pool index 0 for the UE. As shown by reference number1210, the UE may apply TCI state 1 (e.g., the TCI state indicated in the first beam indication DCI) starting in a first slot that is at least a configured number (Y) of symbols after a last symbol of a PUCCH communication carrying HARQ-ACK feedback for the first beam indication DCI. The UE may apply TCI state 1 to multiple downlink and/or uplink channels and reference signals associated with CORESET pool index 0 (e.g., including CORESETs associated with CORESET pool index 0). For example, the UE may apply TCI state 1 to downlink signals and channels (and uplink signals and channels, in some examples) associated with CORESET pool index 0 from the starting time associated with the first beam indication DCI until the UE receives an indication of a different TCI state in another beam indication DCI associated with CORESET pool index 0.

As shown by reference number1215, the UE may receive, from TRP2, second beam indication DCI that includes a TCI field codepoint that indicates a second TCI state (e.g., TCI state 2) to be applied to channels and signals associated with CORESET pool index 1 (e.g., for communications between TRP2 and the UE) starting from a starting time associated with the second beam indication DCI. The UE may receive the second beam indication DCI in a CORESET associated with CORESET pool index 1. The second beam indication DCI may be DCI format 1_1 or 1_2, with or without PDSCH scheduling. The TCI field codepoint may map to a TCI state (e.g., TCI state 2), from a set of activated TCI states associated with CORESET pool index 1 for the UE. As shown by reference number1220, the UE may apply TCI state 2 (e.g., the TCI state indicated in the second beam indication DCI) starting in a first slot that is at least a configured number (Y) of symbols after a last symbol of a PUCCH communication carrying HARQ-ACK feedback for the second beam indication DCI. The UE may apply TCI state 2 to multiple downlink and/or uplink channels and reference signals associated with CORESET pool index 1 (e.g., including CORESETs associated with CORESET pool index 1). For example, the UE may apply TCI state 2 to downlink signals and channels (and uplink signals and channels, in some examples) associated with CORESET pool index 1 from the starting time associated with the second beam indication DCI until the UE receives an indication of a different TCI state in another beam indication DCI associated with CORESET pool index 1.

The UE may receive, from TRP1 or TRP2, scheduling DCI (e.g., DCI format 1_1 or 1_2) that schedules a PDSCH communication to the UE. The UE may detect a default beam condition associated with the scheduling DCI. For example, in a case in which QCL-TypeD is used (e.g., in FR2), the UE may detect the default beam condition when the scheduling offset between the scheduling DCI and the scheduled PDSCH communication is less than a time duration for QCL (e.g., timeDurationForQCL). The UE, in connection with detecting the default beam condition, may receive the scheduled PDSCH communication using a default beam. In some aspects, the UE may not be configured with two default beams (e.g., respective default beams for CORESET pool index 0 and CORESET pool index 1), and the UE may determine the default beam to use for receiving the scheduled PDSCH communication. For example, the UE may determine whether the beam is associated with CORESET pool index 0 (e.g., associated with TRP1) of CORESET pool index 1 (e.g., associated with TRP2).

In some aspects, the default beam for the scheduled PDSCH communication may be a latest indicated beam associated with a fixed CORESET pool index value. As shown by reference number1225, in one example, the default beam for a PDSCH communication scheduled in a given slot may be a beam associated with the latest indicated TCI state associated with CORESET pool index 0 (e.g., TCI state 1 indicated in the first beam indication DCI).

In some aspects, the UE may determine whether the default beam, for a PDSCH communication scheduled in a given slot, is associated with CORESET pool index 0 or CORESET pool index 1 based at least in part on a pattern in the time domain. As shown by reference number1230, a slot-level pattern indicates a first set of slots in which the default beam is associated with CORESET pool index 0 and a second set of slots in which the default beam is associated with CORESET pool index 1. In the first set of slots, in which the default beam is associated with CORESET pool index 0, the default beam may be a beam associated with the latest indicated TCI state associated with CORESET pool index 0 (e.g., TCI state 1 indicated in the first beam indication DCI). In the second set of slots, in which the default beam is associated with CORESET pool index 1, the default beam may be a beam associated with the latest indicated TCI state associated with CORESET pool index 1 (e.g., TCI state 2 indicated in the second beam indication DCI).

As indicated above,FIG.12is provided as an example. Other examples may differ from what is described with respect toFIG.12.

“Cross-carrier” scheduling refers to DCI carried in one CC scheduling one or more communications on another CC. For example, cross-carrier scheduling may be used to schedule PDSCH communications, PUSCH communications, and/or reference signal transmissions (e.g., for downlink and/or uplink reference signals). The CC in which the DCI is carried may be referred to as the “scheduling CC,” and the CC in which a communication is scheduled may be referred to as the “scheduled CC.” In some cases, a scheduling CC may be used to carry DCI that schedules communications on multiple different scheduled CCs. With cross-carrier scheduling for PDSCH communications, the scheduling DCI/CORESET and the scheduled PDSCH are in different CCs, and the scheduled CC may not be configured with any CORESET, as the UE may not monitor for PDCCH on the scheduled CC. In this case, the default beam for a PDSCH scheduled in the scheduled CC cannot be determined from latest monitored CORESETs in the scheduled CC.

In some examples, for a PDSCH scheduled with cross-carrier scheduling, the default beam for a PDSCH communication (both in cases in which the TCI field is not present in the scheduling DCI and in cases in which the scheduling offset is less than the time duration for QCL), may be a beam corresponding to the activated TCI state with the lowest TCI state ID (e.g., among the set of TCI states activated by a MAC-CE). That is the UE may obtain the QCL assumption for the default beam for a scheduled PDSCH communication from the activated TCI state with the lowest TCI state ID applicable to the PDSCH communication in the active BWP of the scheduled CC.

In some examples, in the case of multi-DCI based multi-TRP with cross carrier scheduling, when a UE is configured with two default beams enabled (e.g., when enableDefaultTCI-StatePerCoresetPoolIndex is configured for the UE), the default beam for a PDSCH communication associated with a CORESET pool index value may be determined based at least in part on the activated TCI state with the lowest TCI state ID among the activated TCI states for the that CORESET pool index value. For example, a default beam for a PDSCH communication associated with CORESET pool index 0 may be a beam associated with the activated TCI state with the lowest TCI state ID among the active TCI states for CORESET pool index 0. Similarly, a default beam for a PDSCH communication associated with CORESET pool index 1 may be a beam associated with the activated TCI state with the lowest TCI state ID among the active TCI states for CORESET pool index 1. However, when a DCI-based beam indication is used in the unified TCI framework, the UE may start applying a beam associated with an indicated TCI state, from the set of activated TCI states, to downlink channels and reference signals (and/or uplink channels and reference signals), and continue applying the same beam until another beam indication DCI is received. In this case, the beam indicated by the beam indication DCI (e.g., DCI format 1_1/1_2 with or without a downlink assignment) may not be the activated TCI state with the lowest TCI state ID. Accordingly, in cases in which the unified TCI framework is used for DCI-based beam indications in multi-DCI based multi-TRP with cross-carrier scheduling, a beam indication DCI may indicate a TCI state for a CORESET pool index other than the TCI state with the lowest TCI state ID among the activated TCI states for the CORESET pool index. Thus, the default beam for a PDSCH communication associated with the CORESET pool index may be different from the beam that is being applied to downlink channels and reference signals. As a result, the UE may unnecessarily switch from the indicated beam for downlink communications to a different default beam in order to receive a scheduled PDSCH communication in cases in which the use of the default beam is triggered. This may increase power consumption by the UE and may decrease reliability of the PDSCH communication due to the UE using a default beam that is less reliable than the beam indicated in the beam indication DCI to receive the PDSCH communication.

Some techniques and apparatuses described herein enable, a UE to receive, in a first CC, first DCI that indicates a TCI state to be applied for communications associated with a CORESET pool index in a second CC starting from a first starting time associated with the first DCI. The UE may receive second DCI that indicates a second TCI state to be applied for communications associated with a second CORESET pool index in the second component carrier starting from a second starting time associated with the second DCI. The UE may receive, in the first component carrier, third DCI that schedules a downlink communication in the second component carrier. The UE may receive the downlink communication in the second component carrier using a default beam in connection with a default beam condition associated with the third DCI, and the default beam may be determined to be a beam associated with the first TCI state or a beam associated with the second TCI state based at least in part on whether the downlink communication is associated with the first CORESET pool index or the second CORESET pool index. In some aspects, the default beam may be a beam associated with the first TCI state when the default beam is associated with the first CORESET pool index, and the default beam may be a beam associated with the second TCI state when the default beam is associated with the second CORESET pool index. As a result, the UE may use a default beam associated with the DCI-based TCI state indication for a CORESET pool index, even when the TCI state indicated in the DCI is not the TCI state with the lowest TCI state ID among a set of activated TCI states for the CORESET pool index. Thus, the UE may avoid unnecessarily switching between an indicated beam for a CORESET pool index in a CC and a different default beam when receiving scheduled downlink communications, which may reduce power consumption by the UE and increase reliability of multi-TRP cross-carrier scheduled downlink communications to the UE.

FIG.13is a diagram illustrating an example1300associated with a default beam for multi-DCI based multi-TRP with cross-carrier scheduling and a unified TCI, in accordance with the present disclosure. As shown inFIG.13, example1300includes a first TRP1305-1, a second TRP1305-2, and a UE120. In some aspects, the TRPs1305and UE120may be included in a wireless network, such as wireless network100. The TRPs1305and the UE120may communicate via a wireless access link, which may include an uplink and a downlink.

In some aspects, the TRPs1305may communicate with the UE120using multi-DCI based multi-TRP communications. In some aspects, the first TRP1305-1may be associated with a first CORESET pool index (e.g., CORESET pool index 0), and the second TRP1305-2may be associated with a second CORESET pool index (e.g., CORESET pool index 1). The UE120may be configured with one or more CORESETs associated with the first CORESET pool index (e.g., CORESET pool index 0) and one or more CORESETs associated with the second CORESET pool index (e.g., CORESET pool index 1). In some aspects, the UE120may be configured with respective default beams enabled for the first CORESET pool index and the second CORESET pool index (e.g., the UE120may be configured with two default beams). For example, the RRC parameter enableDefaultTCI-StatePerCoresetPoolIndex may be configured for the UE120.

A shown inFIG.13, and by reference number1310, the UE120may receive first beam indication DCI (e.g., “first DCI”) associated with the first CORESET pool index. The first TRP1305-1may transmit the first beam indication DCI to the UE120. In some aspects, the first beam indication DCI may be received by the UE120in a first CC, and the first beam indication DCI may indicate a first TCI state to be applied for communications associated with the first CORESET pool index in a second CC starting from a first starting time associated with the first beam indication DCI. The second CC may be a scheduled CC that is configured to enable with multi-DCI based multi-TRP communications. In some aspects, the first CC may be a scheduling CC, in which scheduling DCI may also be transmitted to the UE120.

The first beam indication DCI may be DCI format 1_1 or 1_2 transmitted with or without scheduling information for a downlink communication (e.g., a PDSCH communication). In some aspects, the first starting time associated with the first beam indication DCI may be a first slot at least Y symbols after a last symbol of a PUCCH communication including HARQ-ACK feedback associated with the first beam indication DCI. For example, the number of symbols Y used to determine the starting time may be configured for the UE120via RRC signaling. In some aspects, the first TCI state indicated by the first beam indication DCI may be “sticky,” and may be applied for downlink channels (e.g., PDSCH and PDCCH) and downlink reference signals (e.g., CSI-RS) (or for downlink and uplink channels and reference signals) associated with the first CORESET pool index in the second CC until the UE120receives another beam indication DCI that indicates a different TCI state to be applied to communications associated with the first CORESET pool index in the second CC.

The first beam indication DCI may include, in a TCI field of the first beam indication DCI, a TCI field codepoint that indicates a unified TCI state (e.g., a downlink TCI state or a joint downlink and uplink TCI state) to be applied starting from the first starting time for communications associated with the first CORESET pool index in the second CC. The TCI field codepoint may map to an activated TCI state from a set of activated TCI states associated with the first CORESET pool index for the UE120. For example, the TCI field codepoint included in the first beam indication may map to a joint downlink and uplink TCI state, a pair of TCI states including separate downlink and uplink TCI states, or a downlink only TCI state. The set of activated states associated with the first CORESET pool index may be indicated in a MAC-CE transmitted to the UE120from the first TRP1305-1.

As shown inFIG.13, and by reference number1315, the UE120may receive second beam indication DCI (e.g., “second DCI”) associated with the second CORESET pool index. The second TRP1305-1may transmit the second beam indication DCI to the UE120. In some aspects, the second beam indication DCI may be transmitted for the second TRP1305-2to the UE120in the first CC (e.g., in the same CC in which the first beam indication DCI is transmitted from the first TRP1305-1to the UE120). In some aspects, the second beam indication DCI may be transmitted from the second TRP1305-2to the UE120in a third CC that is a different CC from the first CC in which the first beam indication DCI is transmitted from the first TRP1305-1to the UE120(and different from the second CC). The second beam indication DCI may indicate a second TCI state to be applied for communications associated with the second CORESET pool index in the second CC starting from a second starting time associated with the second beam indication DCI.

The second beam indication DCI may be DCI format 1_1 or 1_2 transmitted with or without scheduling information for a downlink communication (e.g., a PDSCH communication). In some aspects, the second starting time associated with the second beam indication DCI may be a first slot at least Y symbols after a last symbol of a PUCCH communication including HARQ-ACK feedback associated with the second beam indication DCI. In some aspects, the second TCI state indicated by the first beam indication DCI may be “sticky,” and may be applied for downlink channels (e.g., PDSCH and PDCCH) and downlink reference signals (e.g., CSI-RS) (or for downlink and uplink channels and reference signals) associated with the second CORESET pool index in the second CC until the UE120receives another beam indication DCI that indicates a different TCI state to be applied to communications associated with second first CORESET pool index in the second CC.

The second beam indication DCI may include, in a TCI field of the second beam indication DCI, a TCI field codepoint that indicates a unified TCI state (e.g., a downlink TCI state or a joint downlink and uplink TCI state) to be applied starting from the second starting time for communications associated with the second CORESET pool index in the second CC. The TCI field codepoint may map to an activated TCI state from a set of activated TCI states associated with the second CORESET pool index for the UE120. For example, the TCI field codepoint included in the first beam indication may map to a joint downlink and uplink TCI state, a pair of TCI states including separate downlink and uplink TCI states, or a downlink only TCI state. The set of activated states associated with the second CORESET pool index may be indicated in a MAC-CE transmitted to the UE120from the second TRP1305-2.

As further shown inFIG.13, and by reference number1320, the UE120may receive, in the first CC, scheduling DCI (e.g., “third DCI”) that schedules a downlink communication in the second CC. For example, the scheduling DCI may schedule a PDSCH communication for the UE120in the second CC. The first CC may be a scheduling CC for cross-carrier scheduling, and the second CC may be a scheduled CC for the downlink communication (e.g., PDSCH communication) scheduled by the scheduling DCI.

The UE120may receive the scheduling DCI from the first TRP1305-1or from the second TRP1305-2. As shown by reference number1320a, the first TRP1305-1may transmit scheduling DCI to the UE120in the first CC, and the scheduling DCI may schedule a PDSCH communication associated with the first CORESET pool index (e.g., a PDSCH communication from the first TRP1305-1) in the second CC. As shown by reference number1320b, the second TRP1305-2may transmit scheduling DCI to the UE120in the first CC, and the scheduling DCI may schedule a PDSCH communication associated with the second CORESET pool index (e.g., a PDSCH communication from the second TRP1305-2) in the second CC.

As further shown inFIG.13, and by reference number1325, the UE120may detect a default beam condition associated with the scheduling DCI. The default beam condition associated with the scheduling DCI may be a condition that triggers the use of a default beam for receiving the scheduled downlink communication (e.g., PDSCH communication) by the UE120.

In some aspects, the UE120may detect the default beam condition in connection with a determination that a scheduling offset between the scheduling DCI and the scheduled downlink communication (e.g., PDSCH communication) is less than a time duration threshold. The time duration threshold may be based at least in part on a time duration for QCL (e.g., timeDurationforQCL). The time duration for QCL (e.g., timeDurationForQCL) may be a time duration indicated in or configured based at least in part on UE capability information for the UE120. In some aspects, the time duration threshold may be equal to the time duration for QCL (e.g., timeDurationForQCL). For example, when QCL-TypeD is used (e.g., in FR2), the UE120may detect the default beam condition in connection with a determination that the scheduling offset between the scheduling DCI and the scheduled downlink communication (e.g., PDSCH communication) is less than the time duration for QCL (e.g., timeDurationForQCL). In some aspects, in a case in which a first subcarrier spacing of the scheduling CC (e.g., the first CC) is different from a second subcarrier spacing of the scheduled CC (e.g., the second CC), the time duration threshold may be equal to a sum of the time duration for QCL (e.g., timeDurationForQCL) and a delay associated the first subcarrier spacing and the second subcarrier spacing being different. For example, in a case in which a numerology (μPDCCH) of the scheduling CC (e.g., the first CC) is less than a numerology (μPDSCH) of the scheduled CC (e.g., the second CC), the time duration threshold may be equal to a sum of timeDurationForQCL and a delay of

d⁢2μPDSCH2μPDCCH,
where d may be specified in a wireless communication standard (e.g., a 3GPP standard) or configured via RRC configuration.

In some aspects, the UE120may detect the default beam condition in connection with a determination that a TCI field is absent from the scheduling DCI.

As further shown inFIG.13, and by reference number1330, the UE120may receive the scheduled downlink communication in the second CC (e.g., from the first TRP1305-1or the second TRP1305-2) using a default beam associated with the first CORESET pool index or the second CORESET pool index. The UE120, in connection with detecting the default beam condition associated with the scheduling DCI, may determine the default beam to use to receive the downlink communication (e.g., PDSCH communication) scheduled in the second CC by the scheduling DCI.

In some aspects, in a case in which the UE120is configured with respective default beams enabled for the first CORESET pool index and the second CORESET pool index (e.g., the UE120is configured with two default beams enabled), the UE120may determine whether the default beam is a beam associated with the first TCI state (indicated in the first beam indication DCI) or a beam associated with the second TCI state (indicated in the first beam indication DCI) based at least in part on whether the downlink communication (e.g., PDSCH communication) is associated with the first CORESET pool index or the second CORESET pool index. The first TCI state, indicated in the first beam indication DCI, may be the latest indicated TCI state associated with the first CORESET pool index to be applied in the second CC. The second TCI state, indicated in the second beam indication DCI, may be the latest indicated TCI state associated with the second CORESET pool index to be applied in the second CC.

In some aspects, for a downlink communication (e.g., PDSCH communication) associated with the first CORESET pool index (e.g., CORESET pool index 0) that is scheduled (e.g., via cross-carrier scheduling) by DCI received in a different CC (e.g., the first CC), the default beam for the downlink communication (e.g., in a case in which the default beam condition is detected) may be a beam associated with a latest indicated TCI state associated with the first CORESET pool index in beam indication DCI. In this case, the default beam for a downlink communication (e.g., PDSCH communication) associated with the first CORESET pool index (e.g., scheduled by scheduling DCI associated the first CORESET pool index) may be a beam associated with the first TCI state indicated in the first beam indication DCI. Because the default beam is associated with the first CORESET pool index, the downlink communication is transmitted to the UE120from the first TRP1305-1. As shown by reference number1330a, for a scheduled PDSCH communication associated with the first CORESET pool index, the first TRP1305-1may transmit the PDSCH communication, and the UE120may receive the PDSCH communication, in the second CC using a default beam associated with the first TCI state indicated in the first beam indication DCI.

In some aspects, for a downlink communication (e.g., PDSCH communication) associated with the second CORESET pool index (e.g., CORESET pool index 1) that is scheduled (e.g., via cross-carrier scheduling) by DCI received in a different CC (e.g., the first CC), the default beam for the downlink communication (e.g., in a case in which the default beam condition is detected) may be a beam associated with a latest indicated TCI state associated with the second CORESET pool index in beam indication DCI. In this case, the default beam for a downlink communication (e.g., PDSCH communication) associated with the second CORESET pool index (e.g., scheduled by scheduling DCI associated the second CORESET pool index) may be a beam associated with the second TCI state indicated in the second beam indication DCI. Because the default beam is associated with the second CORESET pool index, the downlink communication is transmitted to the UE120from the second TRP1305-2. As shown by reference number1330b, for a scheduled PDSCH communication associated with the second CORESET pool index, the second TRP1305-2may transmit the PDSCH communication, and the UE120may receive the PDSCH communication, in the second CC using a default beam associated with the second TCI state indicated in the second beam indication DCI.

In some aspects, in a case in which the UE120is not configured with two default beams enabled for multi-DCI based multi-TRP with cross-carrier scheduling, the UE120may determine the default beam for a downlink communication (e.g., PDSCH communication) scheduled via-cross carrier scheduling in a CC (e.g., the second CC) configured for multi-DCI based multi-TRP based at least in part on a latest indicated TCI state associated with a fixed CORESET pool index (e.g., the first CORESET pool index or the second CORESET pool index) or based at least in part on a latest indicated TCI state of associated with a CORESET pool index that is determined in accordance with a pattern in a time domain, similar to as described above in connection withFIG.11.

As indicated above,FIG.13is provided as an example. Other examples may differ from what is described with respect toFIG.13.

FIG.14is a diagram illustrating an example1400associated with a default beam for multi-DCI based multi-TRP with cross-carrier scheduling and a unified TCI, in accordance with the present disclosure. As shown inFIG.14, example1400includes multi-DCI based multi-TRP communications between a UE, a first TRP (TRP1), and second TRP (TRP2). TRP1 may be associated with a first CORESET pool index (CORESET pool index 0), and TRP2 may be associated with a second CORESET pool index (CORESET pool index 1). The UE may be configured with respective default beams (e.g., two default beams) enabled for CORESET pool index 0 and CORESET pool index 1. A first CC (CC1) may be scheduling CC, and a second CC (CC2) may be a scheduled CC configured with cross carrier scheduling. CC2 may be configured for multi-DCI based multi-TRP communications associated with CORESET pool 0 and CORESET pool 1, and CC2 may be configured with unified TCI.

As shown inFIG.14, the UE may receive beam indication DCI1405in CC1 that indicates a TCI state to be applied to downlink signals and channels (or to downlink and uplink signals and channels) associated with CORESET pool index 1 in CC2 starting from a starting time1410associated with the beam indication DCI1405. The beam indication DCI1405may be DCI format 1_1/1_2 with or without PDSCH scheduling information. The beam indication DCI1405may indicate a TCI field codepoint that maps to a TCI state in a set of activated TCI states for the CORESET pool index 1. For example, as shown inFIG.14, the beam indication DCI1405may indicate a TCI field codepoint of 2, which maps to TCI state 4. The starting time1410associated with the beam indication DCI1405may start at a first slot at least a configured number (Y) of symbols after a last symbol of a PUCCH communication that includes the HARQ-ACK feedback for the beam indication DCI1405. The UE may start applying the TCI state (e.g., TCI state 4) indicated in the beam indication DCI1405at the start time1410, and the UE may apply the indicated TCI state (e.g., TCI state 4) to multiple downlink signals and channels associated with CORESET pool index 1 in CC2. For example, the UE may apply the indicated TCI state (e.g., TCI state 4) to downlink signals and channels associated with CORESET pool index 1 in CC2 from the starting time1410until the UE receives another beam indication DCI including an indication of a different TCI state for communications associated with CORESET 1 in CC2.

As further shown inFIG.14, the UE may receive beam indication DCI1415in CC1 that indicates a TCI state to be applied to downlink signals and channels (or to downlink and uplink signals and channels) associated with CORESET pool index 0 in CC2 starting from a starting time1420associated with the beam indication DCI1415. The beam indication DCI1415may be DCI format 1_1/1_2 with or without PDSCH scheduling information. The beam indication DCI1415may indicate a TCI field codepoint that maps to a TCI state in a set of activated TCI states for the CORESET pool index 0. For example, as shown inFIG.14, the beam indication DCI1415may indicate a TCI field codepoint of 1, which maps to TCI state 2. The starting time1420associated with the beam indication DCI1415may start at a first slot at least a configured number (Y) of symbols after a last symbol of a PUCCH communication that includes the HARQ-ACK feedback for the beam indication DCI1415. The UE may start applying the TCI state (e.g., TCI state 2) indicated in the beam indication DCI1415at the start time1420, and the UE may apply the indicated TCI state (e.g., TCI state 2) to multiple downlink signals and channels associated with CORESET pool index 0 in CC2. For example, the UE may apply the indicated TCI state (e.g., TCI state 2) to downlink signals and channels associated with CORESET pool index 0 in CC2 from the starting time1420until the UE receives another beam indication DCI including an indication of a different TCI state for communications associated with CORESET 0 in CC2.

As further shown inFIG.14, the UE may receive scheduling DCI1425in CC1 that schedules a PDSCH communication1430associated with CORESET pool index 1 in CC2. The UE may detect a default beam condition associated with the scheduling DCI1425. For example, a scheduling offset between the scheduling DCI1425and the scheduled PDSCH communication1430may be less than a time duration threshold (e.g., the scheduling offset may be less than timeDurationforQCL), which may trigger the UE to receive the scheduled PDSCH communication1430using a default beam. In some aspects, because the PDSCH communication1430is associated with CORESET pool index 1, the default beam for the receiving the PDSCH communication1430may be a default beam associated with the TCI state (e.g., TCI state 4) indicated in the latest beam indication DCI1405for CORESET pool index 1 in CC2. The PDSCH communication1430may be transmitted from TRP2, and received by the UE, in CC2 using the default beam associated with TCI state 4.

As shownFIG.14, the UE may use a beam associated with TCI state 4 as the default beam for receiving the PDSCH communication1430associated with CORESET pool index 1, because TCI state 4 was indicated (e.g., using the TCI field codepoint of 2) in the latest beam indication DCI1405for communications associated with CORESET pool index 1 in CC2. However, in the example ofFIG.14, TCI state 3 is the TCI state with the lowest TCI state ID among the set of activated TCI states for CORESET pool index 1. In some aspects, the UE may use the beam associated with the latest indicated TCI state (e.g., TCI 4) to be applied to communications associated with CORESET pool index 1 in CC2, even in a case in which the indicated TCI state (e.g., TCI state 4) is not the TCI state with the lowest TCI state ID (e.g., TCI state 3) among the activated TCI states for CORESET pool index 1.

As further shown inFIG.14, the UE may receive scheduling DCI1435in CC1 that schedules a PDSCH communication1440associated with CORESET pool index 0 in CC2. The UE may detect a default beam condition associated with the scheduling DCI1435. For example, a scheduling offset between the scheduling DCI1435and the scheduled PDSCH communication1440may be less than a time duration threshold (e.g., the scheduling offset may be less than timeDurationforQCL), which may trigger the UE to receive the scheduled PDSCH communication1440using a default beam. In some aspects, because the PDSCH communication1440is associated with CORESET pool index 0, the default beam for the receiving the PDSCH communication1440may be a default beam associated with the TCI state (e.g., TCI state 2) indicated in the latest beam indication DCI1415for CORESET pool index 0 in CC2. The PDSCH communication1440may be transmitted from TRP1, and received by the UE, in CC2 using the default beam associated with TCI state 2.

As shownFIG.14, the UE may use a beam associated with TCI state 2 as the default beam for receiving the PDSCH communication1440associated with CORESET pool index 0, because TCI state 2 was indicated (e.g., using the TCI field codepoint of 1) in the latest beam indication DCI1415for communications associated with CORESET pool index 0 in CC2. However, in the example ofFIG.14, TCI state 1 is the TCI state with the lowest TCI state ID among the set of activated TCI states for CORESET pool index 0. In some aspects, the UE may use the beam associated with the latest indicated TCI state (e.g., TCI 2) to be applied to communications associated with CORESET pool index 0 in CC2, even in a case in which the indicated TCI state (e.g., TCI state 2) is not the TCI state with the lowest TCI state ID (e.g., TCI state 1) among the activated TCI states for CORESET pool index 0.

As indicated above,FIG.14is provided as an example. Other examples may differ from what is described with respect toFIG.14.

FIG.15is a diagram illustrating an example process1500performed, for example, by a UE, in accordance with the present disclosure. Example process1500is an example where the UE (e.g., UE120) performs operations associated with a default beam for multi-DCI based multi-TRP with a unified TCI.

As shown inFIG.15, in some aspects, process1500may include receiving, in a first CORESET associated with a first CORESET pool index, first DCI that indicates a first TCI state to be applied starting from a first starting time associated with the first DCI (block1510). For example, the UE (e.g., using communication manager140and/or reception component1802, depicted inFIG.18) may receive, in a first CORESET associated with a first CORESET pool index, first DCI that indicates a first TCI state to be applied starting from a first starting time associated with the first DCI, as described above.

As further shown inFIG.15, in some aspects, process1500may include receiving, in a second CORESET associated with a second CORESET pool index, second DCI that indicates a second TCI state to be applied starting from a second starting time associated with the second DCI (block1520). For example, the UE (e.g., using communication manager140and/or reception component1802, depicted inFIG.18) may receive, in a second CORESET associated with a second CORESET pool index, second DCI that indicates a second TCI state to be applied starting from a second starting time associated with the second DCI, as described above.

As further shown inFIG.15, in some aspects, process1500may include receiving third DCI that schedules a downlink communication (block1530). For example, the UE (e.g., using communication manager140and/or reception component1802, depicted inFIG.18) may receive third DCI that schedules a downlink communication, as described above.

As further shown inFIG.15, in some aspects, process1500may include receiving the downlink communication using a default beam associated with the first CORESET pool index or the second CORESET pool index in connection with a default beam condition associated with the third DCI (block1540). For example, the UE (e.g., using communication manager140and/or reception component1802, depicted inFIG.18) may receive the downlink communication using a default beam associated with the first CORESET pool index or the second CORESET pool index in connection with a default beam condition associated with the third DCI, as described above.

In a first aspect, the UE is not configured with respective default beams enabled for the first CORESET pool index and the second CORESET pool index.

In a second aspect, receiving the downlink communication using the default beam associated with the first CORESET pool index or the second CORESET pool index in connection with the default beam condition associated with the third DCI includes receiving the downlink communication using the default beam associated with the first CORESET pool index or the second CORESET pool index in connection with a scheduling offset between the second DCI and the downlink communication being less than a time duration for QCL.

In a third aspect, the default beam is a beam corresponding to a latest indicated TCI state associated with a fixed CORESET pool index, and the fixed CORESET pool index is the first CORESET pool index or the second CORESET pool index.

In a fourth aspect, the fixed CORESET pool index is the first CORESET pool index and the latest indicated TCI state associated with the fixed CORESET pool index is the first TCI state.

In a fifth aspect, the default beam is a beam associated with a CORESET with a lowest CORESET identifier among one or more CORESETs associated with a fixed CORESET pool index monitored in a latest slot in which at least one CORESET associated with the fixed CORESET pool index is monitored, and the fixed CORESET pool index is the first CORESET pool index or the second CORESET pool index.

In a sixth aspect, the default beam is determined to be associated with the first CORESET pool index or the second CORESET pool index based at least in part on a slot in which the downlink communication is scheduled and a pattern in a time domain.

In a seventh aspect, the default beam is a beam associated with the first TCI state based at least in part on a determination that the default beam is associated with the first CORESET pool index, or the default beam is a beam associated with the second TCI state based at least in part on a determination that the default beam is associated with the second CORESET pool index.

In an eighth aspect, the pattern is a slot-level pattern that identifies a first set of slots in which the default beam is associated with the first CORESET pool index and a second set of slots in which the default beam is associated with the second CORESET pool index.

In a ninth aspect, the slot-level pattern is based at least in part on a slot number.

In a tenth aspect, the first set of slots includes slots with even slot numbers and the second set of slots includes slots with odd slot numbers.

In an eleventh aspect, the slot-level pattern is based at least in part on an absolute slot number or the slot-level pattern is based at least in part on a relative slot number relative to a slot in which the first TCI state or the second TCI state is applied.

In a twelfth aspect, process1500includes receiving an RRC message including a configuration of the pattern, and the configuration of the pattern indicates at least one of a first set of slots in which the default beam is associated with the first CORESET pool index or a second set of slots in which the default beam is associated with the second CORESET pool index.

In a thirteenth aspect, process1500includes receiving an indication of the pattern in a MAC-CE that indicates one or more active TCI states for at least one of the first CORESET pool index or the second CORESET pool index, and the indication of the pattern indicates at least one of a first set of slots in which the default beam is associated with the first CORESET pool index or a second set of slots in which the default beam is associated with the second CORESET pool index.

In a fourteenth aspect, the first DCI includes an indication of a TCI codepoint that indicates the first TCI state and a pattern for a first set of slots in which the default beam is associated with the first CORESET pool index.

In a fifteenth aspect, process1500includes receiving a MAC-CE that indicates one or more TCI codepoints for the first CORESET pool index and a mapping between each TCI codepoint of the one or more TCI codepoints for the first CORESET pool index and a respective TCI state and pattern combination.

In a sixteenth aspect, the second DCI includes an indication of a TCI codepoint that indicates the second TCI state and a pattern for a second set of slots in which the default beam is associated with the second CORESET pool index.

In a seventeenth aspect, the first CORESET pool index is associated with a first transmit receive point and the second CORESET pool index is associated with a second transmit receive point.

In an eighteenth aspect, the downlink communication scheduled by the third DCI is a PDSCH communication.

In a nineteenth aspect, the first TCI state is a TCI state to be applied for communications associated with the first CORESET pool index starting from the first starting time associated with the first DCI, and the second TCI state is a TCI state to be applied for communications associated with the second CORESET pool index starting from the second starting time associated with the second DCI.

AlthoughFIG.15shows example blocks of process1500, in some aspects, process1500may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIG.15. Additionally, or alternatively, two or more of the blocks of process1500may be performed in parallel.

FIG.16is a diagram illustrating an example process1600performed, for example, by a network node, in accordance with the present disclosure. Example process1600is an example where the network node (e.g., TRP1105, TRP1305, base station110, CU310, DU330, RU340, or a combination thereof) performs operations associated with a default beam for multi-DCI based multi-TRP with unified TCI.

As shown inFIG.16, in some aspects, process1600may include transmitting, in a first CORESET associated with a first CORESET pool index of multiple CORESET pool indexes configured for a UE, first DCI that indicates a TCI state to be applied starting from a starting time associated with the first DCI (block1610). For example, the network node (e.g., using communication manager1908and/or transmission component1904, depicted inFIG.19) may transmit, in a first CORESET associated with a first CORESET pool index of multiple CORESET pool indexes configured for a UE, first DCI that indicates a TCI state to be applied starting from a starting time associated with the first DCI, as described above.

As further shown inFIG.16, in some aspects, process1600may include transmitting a downlink communication scheduled by second DCI using a default beam in connection with a default beam condition associated with the second DCI and in connection with the default beam being associated with the first CORESET pool index (block1620). For example, the network node (e.g., using communication manager1908and/or transmission component1904, depicted inFIG.19) may transmit a downlink communication scheduled by second DCI using a default beam in connection with a default beam condition associated with the second DCI and in connection with the default beam being associated with the first CORESET pool index, as described above.

In a first aspect, process1600includes transmitting the second DCI that schedules the downlink communication.

In a second aspect, alone or in combination with the first aspect, the UE is not configured with respective default beams enabled for the multiple CORESET indexes configured for the UE.

In a third aspect, alone or in combination with one or more of the first and second aspects, transmitting the downlink communication scheduled by second DCI using the default beam in connection with the default beam condition and in connection with the default beam being associated with the first CORESET pool index includes transmitting the downlink communication using the default beam in connection with a scheduling offset between the second DCI and the downlink communication being less than a time duration for QCL and in connection with the default beam being associated with the first CORESET pool index.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the default beam is a beam corresponding to a latest indicated TCI state associated with a fixed CORESET pool index of the multiple CORESET pool indexes configured for the UE, the fixed CORESET pool index is the first CORESET pool index, and the latest indicated TCI state associated with the fixed CORESET pool index is the TCI state indicated in the first DCI.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the default beam is a beam associated with a CORESET with a lowest CORESET identifier among one or more CORESETs associated with a fixed CORESET pool index monitored in a latest slot in which at least one CORESET associated with the fixed CORESET pool index is monitored, and the fixed CORESET pool index is the first CORESET pool index.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the default beam is determined to be associated with the first CORESET pool index or a second CORESET pool index, of the multiple CORESET pool indexes configured for the UE, based at least in part on a slot in which the downlink communication is scheduled and a pattern in a time domain.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the default beam is a beam associated with the TCI state indicated in the first DCI based at least in part on a determination that the default beam is associated with the first CORESET pool index.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the pattern is a slot-level pattern that identifies a first set of slots in which the default beam is associated with the first CORESET pool index and a second set of slots in which the default beam is associated with the second CORESET pool index.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the slot-level pattern is based at least in part on a slot number.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the first set of slots includes slots with even slot numbers and the second set of slots includes slots with odd slot numbers.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the slot-level pattern is based at least in part on an absolute slot number, or the slot-level pattern is based at least in part on a relative slot number relative to a slot in which the TCI state indicated in the first DCI is applied.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, process1600includes transmitting, to the UE, an RRC message including a configuration of the pattern, and the configuration of the pattern indicates at least one of a first set of slots in which the default beam is associated with the first CORESET pool index or a second set of slots in which the default beam is associated with the second CORESET pool index.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, process1600includes transmitting, to the UE, an indication of the pattern in a MAC-CE that indicates one or more activated TCI states for at least one of the first CORESET pool index or the second CORESET pool index, and the indication of the pattern indicates at least one of a first set of slots in which the default beam is associated with the first CORESET pool index or a second set of slots in which the default beam is associated with the second CORESET pool index.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the first DCI includes an indication of a TCI codepoint that indicates the TCI state and a pattern for a first set of slots in which the default beam is associated with the first CORESET pool index.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, process1600includes transmitting, to the UE, a MAC-CE that indicates one or more TCI codepoints for the first CORESET pool index and a mapping between each TCI codepoint of the one or more TCI codepoints for the first CORESET pool index and a respective TCI state and pattern combination.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the first CORESET pool index is associated with a first transmit receive point and a second CORESET pool index, of the multiple CORESET pool indexes configured for the UE, is associated with a second transmit receive point.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the downlink communication scheduled by the second DCI is a PDSCH communication.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the TCI state indicated in the first DCI is a TCI state to be applied for communications associated with the first CORESET pool index starting from the starting time associated with the first DCI.

AlthoughFIG.16shows example blocks of process1600, in some aspects, process1600may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIG.16. Additionally, or alternatively, two or more of the blocks of process1600may be performed in parallel.

FIG.17is a diagram illustrating an example process1700performed, for example, by a UE, in accordance with the present disclosure. Example process1700is an example where the UE (e.g., UE120) performs operations associated with a default beam for multi-DCI based multi-TRP with cross-carrier scheduling and a unified TCI.

As shown inFIG.17, in some aspects, process1700may include receiving, in a first component carrier, first DCI that indicates a first TCI state to be applied for communications associated with a first CORESET pool index in a second component carrier starting from a first starting time associated with the first DCI (block1710). For example, the UE (e.g., using communication manager140and/or reception component1802, depicted inFIG.18) may receive, in a first component carrier, first DCI that indicates a first TCI state to be applied for communications associated with a first CORESET pool index in a second component carrier starting from a first starting time associated with the first DCI, as described above.

As further shown inFIG.17, in some aspects, process1700may include receiving second DCI that indicates a second TCI state to be applied for communications associated with a second CORESET pool index in the second component carrier starting from a second starting time associated with the second DCI (block1720). For example, the UE (e.g., using communication manager140and/or reception component1802, depicted inFIG.18) may receive second DCI that indicates a second TCI state to be applied for communications associated with a second CORESET pool index in the second component carrier starting from a second starting time associated with the second DCI, as described above.

As further shown inFIG.17, in some aspects, process1700may include receiving, in the first component carrier, third DCI that schedules a downlink communication in the second component carrier (block1730). For example, the UE (e.g., using communication manager140and/or reception component1802, depicted inFIG.18) may receive, in the first component carrier, third DCI that schedules a downlink communication in the second component carrier, as described above.

As further shown inFIG.17, in some aspects, process1700may include receiving the downlink communication in the second component carrier using a default beam in connection with a default beam condition associated with the third DCI, wherein the default beam is determined to be a beam associated with the first TCI state or a beam associated with the second TCI state based at least in part on whether the downlink communication is associated with the first CORESET pool index or the second CORESET pool index (block1740). For example, the UE (e.g., using communication manager140and/or reception component1802, depicted inFIG.18) may receive the downlink communication in the second component carrier using a default beam in connection with a default beam condition associated with the third DCI, wherein the default beam is determined to be a beam associated with the first TCI state or a beam associated with the second TCI state based at least in part on whether the downlink communication is associated with the first CORESET pool index or the second CORESET pool index, as described above.

In a first aspect, the UE is configured with respective default beams enabled for the first CORESET pool index and the second CORESET pool index.

In a second aspect, receiving the downlink communication in the second component carrier using the default beam in connection with the default beam condition associated with the third DCI includes receiving the downlink communication in the second component carrier using a default beam in connection with a scheduling offset between the second DCI and the downlink communication being less than a time duration for QCL.

In a third aspect, the downlink communication is associated with the first CORESET pool index and the default beam is the beam associated with the first TCI state.

In a fourth aspect, the first TCI state is a latest indicated TCI state associated with the first CORESET pool index to be applied in the second component carrier.

In a fifth aspect, the downlink communication is associated with the second CORESET pool index and the default beam is the beam associated with the second TCI state.

In a sixth aspect, the second TCI state is a latest indicated TCI state associated with the second CORESET pool index to be applied in the second component carrier.

In a seventh aspect, the downlink communication scheduled by the third DCI is a PDSCH communication in the second component carrier.

In an eighth aspect, the first CORESET pool index is associated with a first transmit receive point and the second CORESET pool index is associated with a second transmit receive point.

In a ninth aspect, receiving the second DCI includes receiving the second DCI in the first component carrier.

In a tenth aspect, receiving the second DCI includes receiving the second DCI in a third component carrier that is different from the first component carrier and the second component carrier.

AlthoughFIG.17shows example blocks of process1700, in some aspects, process1700may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIG.17. Additionally, or alternatively, two or more of the blocks of process1700may be performed in parallel.

FIG.18is a diagram of an example apparatus1800for wireless communication. The apparatus1800may be a UE, or a UE may include the apparatus1800. In some aspects, the apparatus1800includes a reception component1802and a transmission component1804, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus1800may communicate with another apparatus1806(such as a UE, a base station, or another wireless communication device) using the reception component1802and the transmission component1804. As further shown, the apparatus1800may include the communication manager140. The communication manager140may include one or more of a detection component1808and/or a determination component1810, among other examples.

In some aspects, the apparatus1800may be configured to perform one or more operations described herein in connection withFIGS.11-14. Additionally, or alternatively, the apparatus1800may be configured to perform one or more processes described herein, such as process1500ofFIG.15, process1700ofFIG.17, or a combination thereof. In some aspects, the apparatus1800and/or one or more components shown inFIG.18may include one or more components of the UE described in connection withFIG.2. Additionally, or alternatively, one or more components shown inFIG.18may be implemented within one or more components described in connection withFIG.2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

The transmission component1804may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus1806. In some aspects, one or more other components of the apparatus1800may generate communications and may provide the generated communications to the transmission component1804for transmission to the apparatus1806. In some aspects, the transmission component1804may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus1806. In some aspects, the transmission component1804may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection withFIG.2. In some aspects, the transmission component1804may be co-located with the reception component1802in a transceiver.

The reception component1802may receive, in a first CORESET associated with a first CORESET pool index, first DCI that indicates a first TCI state to be applied starting from a first starting time associated with the first DCI. The reception component1802may receive, in a second CORESET associated with a second CORESET pool index, second DCI that indicates a second TCI state to be applied starting from a second starting time associated with the second DCI. The reception component1802may receive third DCI that schedules a downlink communication. The reception component1802may receive the downlink communication using a default beam associated with the first CORESET pool index or the second CORESET pool index in connection with a default beam condition associated with the third DCI.

The detection component1808may detect the default beam condition associated with the third DCI.

The determination component1810may determine the default beam for the downlink communication.

The reception component1802may receive an RRC message including a configuration of the pattern, wherein the configuration of the pattern indicates at least one of a first set of slots in which the default beam is associated with the first CORESET pool index or a second set of slots in which the default beam is associated with the second CORESET pool index.

The reception component1802may receive an indication of the pattern in a MAC-CE that indicates one or more active TCI states for at least one of the first CORESET pool index or the second CORESET pool index, wherein the indication of the pattern indicates at least one of a first set of slots in which the default beam is associated with the first CORESET pool index or a second set of slots in which the default beam is associated with the second CORESET pool index.

The reception component1802may receive a MAC-CE that indicates one or more TCI codepoints for the first CORESET pool index and a mapping between each TCI codepoint of the one or more TCI codepoints for the first CORESET pool index and a respective TCI state and pattern combination.

The reception component1802may receive, in a first component carrier, first DCI that indicates a first TCI state to be applied for communications associated with a first CORESET pool index in a second component carrier starting from a first starting time associated with the first DCI. The reception component1802may receive second DCI that indicates a second TCI state to be applied for communications associated with a second CORESET pool index in the second component carrier starting from a second starting time associated with the second DCI. The reception component1802may receive, in the first component carrier, third DCI that schedules a downlink communication in the second component carrier. The reception component1802may receive the downlink communication in the second component carrier using a default beam in connection with a default beam condition associated with the third DCI, wherein the default beam is determined to be a beam associated with the first TCI state or a beam associated with the second TCI state based at least in part on whether the downlink communication is associated with the first CORESET pool index or the second CORESET pool index.

The number and arrangement of components shown inFIG.18are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown inFIG.18. Furthermore, two or more components shown inFIG.18may be implemented within a single component, or a single component shown inFIG.18may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown inFIG.18may perform one or more functions described as being performed by another set of components shown inFIG.18.

FIG.19is a diagram of an example apparatus1900for wireless communication. The apparatus1900may be a network node, or a network node may include the apparatus1900. In some aspects, the apparatus1900includes a reception component1902and a transmission component1904, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus1900may communicate with another apparatus1906(such as a UE, a base station, or another wireless communication device) using the reception component1902and the transmission component1904. As further shown, the apparatus1900may include the communication manager1908. The communication manager1908may include a determination component1910, among other examples.

The communication manager1908may control and/or otherwise manage one or more operations of the reception component1902and/or the transmission component1904. In some aspects, the communication manager1908may include one or more antennas, a modem, a controller/processor, a memory, or a combination thereof, of the base station described in connection withFIG.2. The communication manager1908may be, or be similar to, the communication manager150depicted inFIGS.1and2. For example, in some aspects, the communication manager1908may be configured to perform one or more of the functions described as being performed by the communication manager150. In some aspects, the communication manager1908may include the reception component1902and/or the transmission component1904.

The transmission component1904may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus1906. In some aspects, one or more other components of the apparatus1900may generate communications and may provide the generated communications to the transmission component1904for transmission to the apparatus1906. In some aspects, the transmission component1904may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus1906. In some aspects, the transmission component1904may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the network node described in connection withFIG.2. In some aspects, the transmission component1904may be co-located with the reception component1902in a transceiver.

The transmission component1904may transmit, in a first CORESET associated with a first CORESET pool index of multiple CORESET pool indexes configured for a UE, first DCI that indicates a TCI state to be applied starting from a starting time associated with the first DCI. The transmission component1904may transmit a downlink communication scheduled by second DCI using a default beam in connection with a default beam condition associated with the second DCI and in connection with the default beam being associated with the first CORESET pool index.

The transmission component1904may transmit the second DCI that schedules the downlink communication.

The transmission component1904may transmit, to the UE, an RRC message including a configuration of the pattern, wherein the configuration of the pattern indicates at least one of a first set of slots in which the default beam is associated with the first CORESET pool index or a second set of slots in which the default beam is associated with the second CORESET pool index.

The transmission component1904may transmit, to the UE, an indication of the pattern in a MAC-CE that indicates one or more activated TCI states for at least one of the first CORESET pool index or the second CORESET pool index, wherein the indication of the pattern indicates at least one of a first set of slots in which the default beam is associated with the first CORESET pool index or a second set of slots in which the default beam is associated with the second CORESET pool index.

The transmission component1904may transmit, to the UE, a MAC-CE that indicates one or more TCI codepoints for the first CORESET pool index and a mapping between each TCI codepoint of the one or more TCI codepoints for the first CORESET pool index and a respective TCI state and pattern combination.

The determination component1910may determine the TCI state to be indicated by the first DCI, and/or a pattern that indicates at least one of a first set of slots in which the default beam is associated with the first CORESET pool index or a second set of slots in which the default beam is associated with the second CORESET pool index.

The following provides an overview of some Aspects of the present disclosure:Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving, in a first control resource set (CORESET) associated with a first CORESET pool index, first downlink control information (DCI) that indicates a first transmission configuration indicator (TCI) state to be applied starting from a first starting time associated with the first DCI; receiving, in a second CORESET associated with a second CORESET pool index, second DCI that indicates a second TCI state to be applied starting from a second starting time associated with the second DCI; receiving third DCI that schedules a downlink communication; and receiving the downlink communication using a default beam associated with the first CORESET pool index or the second CORESET pool index in connection with a default beam condition associated with the third DCI.Aspect 2: The method of Aspect 1, wherein the UE is not configured with respective default beams enabled for the first CORESET pool index and the second CORESET pool index.Aspect 3: The method of any of Aspects 1-2, wherein receiving the downlink communication using the default beam associated with the first CORESET pool index or the second CORESET pool index in connection with the default beam condition associated with the third DCI comprises: receiving the downlink communication using the default beam associated with the first CORESET pool index or the second CORESET pool index in connection with a scheduling offset between the second DCI and the downlink communication being less than a time duration for quasi co-location (QCL).Aspect 4: The method of any of Aspects 1-3, wherein the default beam is a beam corresponding to a latest indicated TCI state associated with a fixed CORESET pool index, and wherein the fixed CORESET pool index is the first CORESET pool index or the second CORESET pool index.Aspect 5: The method of Aspect 4, wherein the fixed CORESET pool index is the first CORESET pool index and the latest indicated TCI state associated with the fixed CORESET pool index is the first TCI state.Aspect 6: The method of any of Aspects 1-3, wherein the default beam is a beam associated with a CORESET with a lowest CORESET identifier among one or more CORESETs associated with a fixed CORESET pool index monitored in a latest slot in which at least one CORESET associated with the fixed CORESET pool index is monitored, and wherein the fixed CORESET pool index is the first CORESET pool index or the second CORESET pool index.Aspect 7: The method of any of Aspects 1-3, wherein the default beam is determined to be associated with the first CORESET pool index or the second CORESET pool index based at least in part on a slot in which the downlink communication is scheduled and a pattern in a time domain.Aspect 8: The method of Aspect 7, wherein the default beam is a beam associated with the first TCI state based at least in part on a determination that the default beam is associated with the first CORESET pool index, or wherein the default beam is a beam associated with the second TCI state based at least in part on a determination that the default beam is associated with the second CORESET pool index.Aspect 9: The method of any of Aspects 7-8, wherein the pattern is a slot-level pattern that identifies a first set of slots in which the default beam is associated with the first CORESET pool index and a second set of slots in which the default beam is associated with the second CORESET pool index.Aspect 10: The method of Aspect 9, wherein the slot-level pattern is based at least in part on a slot number.Aspect 11: The method of Aspect 10, wherein the first set of slots includes slots with even slot numbers and the second set of slots includes slots with odd slot numbers.Aspect 12: The method of any of Aspects 10-11, wherein the slot-level pattern is based at least in part on an absolute slot number, or the slot-level pattern is based at least in part on a relative slot number relative to a slot in which the first TCI state or the second TCI state is applied.Aspect 13: The method of any of Aspects 7-12, further comprising: receiving a radio resource control (RRC) message including a configuration of the pattern, wherein the configuration of the pattern indicates at least one of a first set of slots in which the default beam is associated with the first CORESET pool index or a second set of slots in which the default beam is associated with the second CORESET pool index.Aspect 14: The method of any of Aspects 7-12, further comprising: receiving an indication of the pattern in a medium access control (MAC) control element (MAC-CE) that indicates one or more active TCI states for at least one of the first CORESET pool index or the second CORESET pool index, wherein the indication of the pattern indicates at least one of a first set of slots in which the default beam is associated with the first CORESET pool index or a second set of slots in which the default beam is associated with the second CORESET pool index.Aspect 15: The method of any of Aspects 7-12, wherein the first DCI includes an indication of a TCI codepoint that indicates the first TCI state and a pattern for a first set of slots in which the default beam is associated with the first CORESET pool index.Aspect 16: The method of Aspect 15, further comprising: receiving a medium access control (MAC) control element (MAC-CE) that indicates one or more TCI codepoints for the first CORESET pool index and a mapping between each TCI codepoint of the one or more TCI codepoints for the first CORESET pool index and a respective TCI state and pattern combination.Aspect 17: The method of any of Aspects 15-16, wherein the second DCI includes an indication of a TCI codepoint that indicates the second TCI state and a pattern for a second set of slots in which the default beam is associated with the second CORESET pool index.Aspect 18: The method of any of Aspects 1-17, wherein the first CORESET pool index is associated with a first transmit receive point and the second CORESET pool index is associated with a second transmit receive point.Aspect 19: The method of any of Aspects 1-18, wherein the downlink communication scheduled by the third DCI is a physical downlink shared channel (PDSCH) communication.Aspect 20: The method of any of Aspects 1-19, wherein the first TCI state is a TCI state to be applied for communications associated with the first CORESET pool index starting from the first starting time associated with the first DCI, and the second TCI state is a TCI state to be applied for communications associated with the second CORESET pool index starting from the second starting time associated with the second DCI.Aspect 21: A method of wireless communication performed by a network node, comprising: transmitting, in a first control resource set (CORESET) associated with a first CORESET pool index of multiple CORESET pool indexes configured for a user equipment (UE), first downlink control information (DCI) that indicates a transmission configuration indicator (TCI) state to be applied starting from a starting time associated with the first DCI; and transmitting a downlink communication scheduled by second DCI using a default beam in connection with a default beam condition associated with the second DCI and in connection with the default beam being associated with the first CORESET pool index.Aspect 22: The method of Aspect 21, further comprising: transmitting the second DCI that schedules the downlink communication.Aspect 23: The method of any of Aspects 21-22, wherein the UE is not configured with respective default beams enabled for the multiple CORESET indexes configured for the UE.Aspect 24: The method of any of Aspects 21-23, wherein transmitting the downlink communication scheduled by second DCI using the default beam in connection with the default beam condition and in connection with the default beam being associated with the first CORESET pool index comprises: transmitting the downlink communication using the default beam in connection with a scheduling offset between the second DCI and the downlink communication being less than a time duration for quasi co-location (QCL) and in connection with the default beam being associated with the first CORESET pool index.Aspect 25: The method of any of Aspects 21-24, wherein the default beam is a beam corresponding to a latest indicated TCI state associated with a fixed CORESET pool index of the multiple CORESET pool indexes configured for the UE, wherein the fixed CORESET pool index is the first CORESET pool index, and wherein the latest indicated TCI state associated with the fixed CORESET pool index is the TCI state indicated in the first DCI.Aspect 26: The method of any of Aspects 21-24, wherein the default beam is a beam associated with a CORESET with a lowest CORESET identifier among one or more CORESETs associated with a fixed CORESET pool index monitored in a latest slot in which at least one CORESET associated with the fixed CORESET pool index is monitored, wherein the fixed CORESET pool index is the first CORESET pool index.Aspect 27: The method of any of Aspects 21-24, wherein the default beam is determined to be associated with the first CORESET pool index or a second CORESET pool index, of the multiple CORESET pool indexes configured for the UE, based at least in part on a slot in which the downlink communication is scheduled and a pattern in a time domain.Aspect 28: The method of Aspect 27, wherein the default beam is a beam associated with the TCI state indicated in the first DCI based at least in part on a determination that the default beam is associated with the first CORESET pool index.Aspect 29: The method of any of Aspects 27-28, wherein the pattern is a slot-level pattern that identifies a first set of slots in which the default beam is associated with the first CORESET pool index and a second set of slots in which the default beam is associated with the second CORESET pool index.Aspect 30: The method of Aspect 29, wherein the slot-level pattern is based at least in part on a slot number.Aspect 31: The method of Aspect 30, wherein the first set of slots includes slots with even slot numbers and the second set of slots includes slots with odd slot numbers.Aspect 32: The method of any of Aspects 30-31, wherein the slot-level pattern is based at least in part on an absolute slot number, or the slot-level pattern is based at least in part on a relative slot number relative to a slot in which the TCI state indicated in the first DCI is applied.Aspect 33: The method of any of Aspects 27-32, further comprising: transmitting, to the UE, a radio resource control (RRC) message including a configuration of the pattern, wherein the configuration of the pattern indicates at least one of a first set of slots in which the default beam is associated with the first CORESET pool index or a second set of slots in which the default beam is associated with the second CORESET pool index.Aspect 34: The method of any of Aspects 27-32, further comprising: transmitting, to the UE, an indication of the pattern in a medium access control (MAC) control element (MAC-CE) that indicates one or more activated TCI states for at least one of the first CORESET pool index or the second CORESET pool index, wherein the indication of the pattern indicates at least one of a first set of slots in which the default beam is associated with the first CORESET pool index or a second set of slots in which the default beam is associated with the second CORESET pool index.Aspect 35: The method of any of Aspects 27-32, wherein the first DCI includes an indication of a TCI codepoint that indicates the TCI state and a pattern for a first set of slots in which the default beam is associated with the first CORESET pool index.Aspect 36: The method of Aspect 35, further comprising: transmitting, to the UE, a medium access control (MAC) control element (MAC-CE) that indicates one or more TCI codepoints for the first CORESET pool index and a mapping between each TCI codepoint of the one or more TCI codepoints for the first CORESET pool index and a respective TCI state and pattern combination.Aspect 37: The method of any of Aspects 21-36, wherein the first CORESET pool index is associated with a first transmit receive point and a second CORESET pool index, of the multiple CORESET pool indexes configured for the UE, is associated with a second transmit receive point.Aspect 38: The method of any of Aspects 21-37, wherein the downlink communication scheduled by the second DCI is a physical downlink shared channel (PDSCH) communication.Aspect 39: The method of any of Aspects 21-38, wherein the TCI state indicated in the first DCI is a TCI state to be applied for communications associated with the first CORESET pool index starting from the starting time associated with the first DCI.Aspect 40: A method of wireless communication performed by a user equipment (UE), comprising: receiving, in a first component carrier, first downlink control information (DCI) that indicates a first transmission configuration indicator (TCI) state to be applied for communications associated with a first control resource set (CORESET) pool index in a second component carrier starting from a first starting time associated with the first DCI; receiving second DCI that indicates a second TCI state to be applied for communications associated with a second CORESET pool index in the second component carrier starting from a second starting time associated with the second DCI; receiving, in the first component carrier, third DCI that schedules a downlink communication in the second component carrier; and receiving the downlink communication in the second component carrier using a default beam in connection with a default beam condition associated with the third DCI, wherein the default beam is determined to be a beam associated with the first TCI state or a beam associated with the second TCI state based at least in part on whether the downlink communication is associated with the first CORESET pool index or the second CORESET pool index.Aspect 41: The method of Aspect 40, wherein the UE is configured with respective default beams enabled for the first CORESET pool index and the second CORESET pool index.Aspect 42: The method of any of Aspects 40-41, wherein receiving the downlink communication in the second component carrier using the default beam in connection with the default beam condition associated with the third DCI comprises: receiving the downlink communication in the second component carrier using a default beam in connection with a scheduling offset between the second DCI and the downlink communication being less than a time duration for quasi co-location (QCL).Aspect 43: The method of any of Aspects 40-42, wherein the downlink communication is associated with the first CORESET pool index and the default beam is the beam associated with the first TCI state.Aspect 44: The method of Aspect 43, wherein the first TCI state is a latest indicated TCI state associated with the first CORESET pool index to be applied in the second component carrier.Aspect 45: The method of any of Aspects 40-42, wherein the downlink communication is associated with the second CORESET pool index and the default beam is the beam associated with the second TCI state.Aspect 46: The method of Aspect 45, wherein the second TCI state is a latest indicated TCI state associated with the second CORESET pool index to be applied in the second component carrier.Aspect 47: The method of any of Aspects 40-46, wherein the downlink communication scheduled by the third DCI is a physical downlink shared channel (PDSCH) communication in the second component carrier.Aspect 48: The method of any of Aspects 40-47, wherein the first CORESET pool index is associated with a first transmit receive point and the second CORESET pool index is associated with a second transmit receive point.Aspect 49: The method of any of Aspects 40-48, wherein receiving the second DCI comprises: receiving the second DCI in the first component carrier.Aspect 50: The method of any of Aspects 40-48, wherein receiving the second DCI comprises: receiving the second DCI in a third component carrier that is different from the first component carrier and the second component carrier.Aspect 51: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-20.Aspect 52: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-20.Aspect 53: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-20.Aspect 54: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-20.Aspect 55: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-20.Aspect 56: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 21-39.Aspect 57: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 21-39.Aspect 58: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 21-39.Aspect 59: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 21-39.Aspect 60: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 21-39.Aspect 61: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 40-50.Aspect 62: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 40-50.Aspect 63: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 40-50.Aspect 64: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 40-50.Aspect 65: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 40-50.