Techniques for updating transmit configuration indicator (TCI) state in wireless communications

Abstract

Aspects described herein relate to receiving first downlink control information (DCI) indicating a first transmit configuration indicator (TCI) state to be applied to a first component carrier (CC) at a first beam application time (BAT); receiving a second DCI indicating a second TCI state to be applied to the first CC or a second CC at a second BAT; and applying the first TCI state or the second TCI state to one or more of the first CC or the second CC within the time period based at least in part on a first attribute of the first DCI and a second attribute of the second DCI if the first BAT and the second BAT are within the same time period. Other aspects relate to transmitting the DCI. Other aspects relate to cases where the BAT is not within the same time period.

Description

[0001] Priority Claims under 35 U.S.C. § 119 and 120

[0002] This patent application claims priority to non - provisional patent application Ser. No. 18 / 477,078, entitled "TECHNIQUES FOR UPDATING TRANSMISSION CONFIGURATION INDICATOR (TCI) STATES IN WIRELESS COMMUNICATIONS", filed on Sep. 29, 2023, and provisional patent application Ser. No. 63 / 381,281, entitled "TECHNIQUES FOR UPDATING TRANSMISSION CONFIGURATION INDICATOR (TCI) STATES IN WIRELESS COMMUNICATIONS", filed on Oct. 27, 2022. These applications are assigned to the assignee of this application and are hereby expressly incorporated by reference herein for all purposes. Field of the Disclosure

[0003] Aspects of the present disclosure generally relate to wireless communication systems and, more particularly, to techniques for updating transmission configuration indicator (TCI) states.

[0004] Related Art

[0005] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcasting, etc. These systems can be multi - access systems that are capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi - access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single - carrier frequency division multiple access (SC - FDMA) systems.

[0006] These multiple access techniques have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. For example, the fifth-generation (5G) wireless communication technology (which may be referred to as 5G New Radio (5GNR)) is designed to extend and support diverse usage scenarios and applications for the current mobile network generation. In one aspect, the 5G communication technology may include: enhanced mobile broadband addressing for accessing multimedia content, services, and data for human-centric use cases; ultra-reliable low-latency communication (URLLC) with certain specifications for latency and reliability; and massive machine-type communication that allows for the transmission of a very large number of connected devices and relatively small amounts of non-latency-sensitive information. SUMMARY OF THE INVENTION

[0007] A simplified review of one or more aspects is presented below to provide a basic understanding of these aspects. This summary of the invention is not an extensive overview of all contemplated aspects, and is neither intended to identify key or critical elements of all aspects nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0008] According to one aspect, a method for wireless communication at a user equipment (UE) is provided. The method includes: receiving first downlink control information (DCI) indicating a first transmission configuration indicator (TCI) state to be applied to a first component carrier (CC) at a first beam application time (BAT); receiving second DCI indicating a second TCI state to be applied to the first CC or a second CC at a second BAT; and, in the case where the first BAT and the second BAT are within the same time period, applying the first TCI state or the second TCI state to one or more of the first CC or the second CC during the time period based at least in part on a first attribute of the first DCI and a second attribute of the second DCI.

[0009] In another aspect, a method for wireless communication at a network node is provided. The method includes: transmitting first DCI indicating a first TCI state to be applied to a first CC at a first BAT; transmitting second DCI indicating a second TCI state to be applied to the first CC or a second CC at a second BAT; and, in the case where the first BAT and the second BAT are within the same time period, applying the first TCI state or the second TCI state to one or more of the first CC or the second CC during the time period based at least in part on a first attribute of the first DCI and a second attribute of the second DCI.

[0010] On the other hand, a method for wireless communication at a UE is provided. The method includes: receiving a first DCI indicating a first TCI state to be applied to a first CC at a first BAT; receiving a second DCI indicating a second TCI state to be applied to the first CC or a second CC at a second BAT, where the first BAT is earlier in time than the second BAT; in a case where the first DCI is received earlier than the second DCI, applying the first TCI state at the first BAT and applying the second TCI state at the second BAT; and in a case where the second DCI is received earlier than the first DCI, applying the first TCI state at the first BAT and avoiding applying the second TCI state at the second BAT.

[0011] On the other hand, a method for wireless communication at a network node is provided. The method includes: sending a first DCI indicating a first TCI state to be applied to a first CC at a first BAT; and in a case where the second BAT is earlier than the first BAT, avoiding sending a second DCI indicating a second TCI state to be applied to the first CC or a second CC at the second BAT after the first DCI.

[0012] On the other hand, a device for wireless communication is provided. The device includes: a transceiver; one or more memories configured to store instructions individually or in combination; and one or more processors communicatively coupled to the one or more memories. The one or more processors are configured to execute the instructions individually or in combination to cause the device to: receive a first DCI indicating a first TCI state to be applied to a first CC at a first BAT; receive a second DCI indicating a second TCI state to be applied to the first CC or a second CC at a second BAT; and in a case where the first BAT and the second BAT are within the same time period, apply the first TCI state or the second TCI state to one or more of the first CC or the second CC during the time period based at least in part on a first attribute of the first DCI and a second attribute of the second DCI.

[0013] In another aspect, a device for wireless communication is provided, the device comprising: a transceiver; one or more memories configured to store instructions, individually or in combination; and one or more processors communicatively coupled to the one or more memories. The one or more processors are configured to execute the instructions, individually or in combination, to cause the device to: transmit a first DCI indicating a first TCI state to be applied to a first CC at a first BAT; transmit a second DCI indicating a second TCI state to be applied to the first CC or a second CC at a second BAT; and, in the case where the first BAT and the second BAT are within the same time period, apply the first TCI state or the second TCI state to one or more of the first CC or the second CC at least partially based on a first attribute of the first DCI and a second attribute of the second DCI within the time period.

[0014] In additional aspects, a device for wireless communication is provided, the device comprising: a transceiver; one or more memories configured to store instructions; and one or more processors communicatively coupled to the transceiver and the one or more memories. The one or more processors are configured to execute the instructions to perform the operations of the methods described herein. In another aspect, a device for wireless communication is provided, the device comprising components for performing the operations of the methods described herein. In yet another aspect, one or more computer-readable media are provided, the one or more computer-readable media comprising code executable by one or more processors to perform the operations of the methods described herein.

[0015] To achieve the foregoing and related purposes, one or more aspects include the features described in full below and particularly pointed out in the claims. The following description and the drawings set forth in detail some illustrative features of one or more aspects. However, these features are only some of the ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Aspects of the disclosure will be described hereinafter in conjunction with the accompanying drawings, which are provided to illustrate and not to limit the aspects of the disclosure, where like reference numerals represent like elements and in which:

[0017] Figure 1 An example of a wireless communication system in accordance with various aspects of the present disclosure is illustrated;

[0018] Figure 2 is a diagram illustrating an example of a decomposed base station architecture in accordance with various aspects of the present disclosure;

[0019] Figure 3 is a block diagram illustrating an example of a user equipment (UE) according to various aspects of the present disclosure;

[0020] Figure 4 is a block diagram illustrating an example of a base station according to various aspects of the present disclosure;

[0021] Figure 5 is a flowchart illustrating an example of a method for applying a transmission configuration indicator (TCI) state based on multiple received downlink control information (DCI) according to aspects described herein;

[0022] Figure 6 is a flowchart illustrating an example of a method for configuring a UE to apply a TCI state based on multiple received DCI according to aspects described herein;

[0023] Figure 7 illustrates an example of a timeline in which multiple DCIs with TCI indication or update are conveyed according to aspects described herein;

[0024] Figure 8 illustrates an example of a timeline for receiving multiple DCIs with TCI state update or indication via multiple component carriers (CCs) according to aspects described herein;

[0025] Figure 9 illustrates an example of a timeline for receiving multiple DCIs with TCI state update or indication via multiple CCs and sending acknowledgement (ACK) feedback for the multiple DCIs according to aspects described herein;

[0026] Figure 10 illustrates an example of a timeline in which multiple DCIs with TCI indication or update are conveyed, where the multiple DCIs have beam application times (BATs) in different time periods according to aspects described herein;

[0027] Figure 11 is a flowchart illustrating an example of a method for ignoring a TCI indication indicated by a DCI earlier than the DCI corresponding to the current indicated TCI according to aspects described herein;

[0028] Figure 12 is a flowchart illustrating an example of a method for avoiding sending a TCI indication indicated by a DCI earlier than the DCI corresponding to the current indicated TCI according to aspects described herein; and

[0029] Figure 13 is a block diagram illustrating an example of a multiple-input multiple-output (MIMO) communication system including a base station and a UE according to various aspects of the present disclosure. Detailed implementation manners

[0030] Aspects will now be described with reference to the accompanying drawings. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It will be evident, however, that such aspects may be practiced without these specific details.

[0031] The described features generally relate to updating transmission configuration indicator (TCI) states in wireless communications. In some wireless communication technologies (such as fifth-generation (5G) new radio (NR)), a network node may configure TCI states for a user equipment (UE), and these TCI states may be used for communication between the network node and the UE. For example, a TCI state may correspond to quasi-co-location (QCL) parameters or a beam to be used for communication via a component carrier (CC) to achieve a spatial direction for communication. In one example, a network node may use radio resource control (RRC) signaling to configure TCI states, and may also use a media access control (MAC) control element (CE) to activate a subset of the configured TCI states, and the media access control (MAC) control element (CE) may indicate an index of the RRC-configured TCI states to be activated. The network node may also indicate one of these TCI states (e.g., an index of the activated TCI state) in downlink control information (DCI) for communication related to the DCI (e.g., communication via a resource grant indicated by the DCI). Additionally, in 5G NR, communication resources may be divided in the time domain into symbols (e.g., orthogonal frequency division multiplexing (OFDM), single-carrier frequency division multiplexing (SC-FDM) symbols, etc.), time slots of multiple symbols, and the like.

[0032] In an example, in 5G NR, when the cyclic redundancy check (CRC) of the downlink control information (DCI) is scrambled by a configured scheduling radio network temporary identifier (CS-RNTI), DCI formats 1_1 or 1_2 can be used to indicate the transmission configuration indicator (TCI) state to be used by the user equipment (UE) when communicating with the network node, without scheduling any downlink assignment. In this example, the redundancy version (RV) and modulation and coding scheme (MCS) fields of DCI formats 1_1 or 1_2, as defined in 5G NR, can be set to all "1", the new data indicator (NDI) can be 0, the frequency domain resource allocation (FDRA) can be all "0" for FDRA type 0, or all "1" for FDRA type 1, or all "0" for dynamicSwitch, the TCI field can be set to indicate the TCI state ID, the PDSCH to HARQ feedback timing indicator field (if present) can be used to indicate the time offset from the DCI to its acknowledgement (ACK) in the physical uplink control channel (PUCCH), and for type 1 hybrid automatic repeat request (HARQ)-ACK codebooks, the time domain resource allocation (TDRA) field can be used to derive the virtual physical downlink shared channel (PDSCH) location, which can be further used to determine the location of the ACK information in the HARQ-ACK codebook.

[0033] For example, for DCI-based beam or TCI state indication, the UE and / or network node may apply the new TCI state in the first time slot that is at least X milliseconds (ms) or Y symbols after the last symbol of the ACK of the DCI that includes combined or separate DL / UL beam indication. For example, the ACK of the beam indication DCI may include a dedicated ACK (e.g., when the DCI has no downlink (DL) resource grant or assignment), or may otherwise include the ACK of the scheduled PDSCH resource grant. For example, X ms or Y symbols may satisfy the UE capabilities for switching beams after transmitting the ACK. In an example, when applying a common TCI state among multiple component carriers (CCs), X or Y may be determined based on the CC with the minimum subcarrier spacing (SCS). In one example, for MAC-CE-based beam or TCI state activation, the indicated TCI may be activated 3 ms after the ACK of the MAC-CE.

[0034] In 5G NR, for example, Technical Specification (TS) 38.214 indicates that when the UE is about to transmit the last symbol of the PUCCH with HARQ-ACK information that corresponds to DCI carrying TCI state indication and not requiring DL assignment or to PDSCH scheduling by DCI carrying TCI state indication, and if the indicated TCI state is different from the previously indicated TCI state, the indicated [TCI state] with [tci-StateId_r17] that can be configured in RRC signaling shall be applied starting from the first time slot that is at least BeamAppTime_r17 symbols after the last symbol of the PUCCH. Both the first time slot and the BeamAppTime_r17 symbols are determined on the active bandwidth part (BWP) with the minimum SCS among the carriers where beam indication is applied. The UE can assume one indicated [TCI state] with [tci-StateId_r17] for the downlink (DL) and uplink (UL) at once, for DL only, or for UL only.

[0035] In some examples, the UE can be configured with multiple CC lists, where each list can include multiple CCs that are configured for or can be configured for communication between the UE and the network node. In an example, the CCs on the same list share the same TCI update or indication from DCI, MAC-CE, etc. In an example where CC1 and CC2 are configured on the same list, if the UE receives a TCI update MAC-CE for CC1, the UE can apply the update to both CC1 and CC2. In an example where CC1 and CC2 are configured on the same list, if the UE receives a DCI indicating a TCI update for CC1, the UE can apply the same TCI to both CC1 and CC2. In an example, the timeline of DCI updates across multiple CCs can include a first time slot after X symbols counted from the last symbol of the ACK to the DCI, where the duration X can be configured in the RRC per BWP. When the CCs applying beam indication have different SCSs (e.g., different symbol durations), the UE and / or the network node can use the active BWP with the minimum SCS (e.g., the maximum symbol length) to determine the timeline.

[0036] In an example, in 5G NR, a UE and / or a network node may determine a beam application time (BAT) for applying a beam after the configuration of the beam, where the BAT may be based on when communication for applying the beam is received or acknowledged. In an example, the first time slot and symbol of the BAT (which may also refer to the BeamAppTime_r17 parameter in 5G NR) may be determined on the active BWP having the minimum SCS among the active BWPs of the carrier for which the beam application is indicated. However, the active BWP (e.g., for a given CC) may change over time. For example, a network node may change the active BWP of a given CC for various reasons, such as modifying the size of the BWP for power savings or scheduling a larger amount of data, reducing interference to other UEs, etc. Thus, the CC having the minimum SCS may change between the time of receiving a TCI update or indication and the time of applying the TCI update or indication. In this regard, aspects described herein may relate to whether to determine the active BWP based on the DCI reception time (for TCI state update or indication) or the ACK time for the DCI. In other aspects described herein, a network node may avoid a change in the active BWP between a DCI and its corresponding ACK, which change may result in different BAT duration determinations.

[0037] Additionally, in an example, a network node may employ PDCCH repetition when sending a PDCCH to a UE. For example, if PDCCH reception by the UE includes two PDCCH candidates from a corresponding search space set, the PDCCH monitoring occasion for the UE to monitor the PDCCH may be a combination of the PDCCH monitoring occasions for the two PDCCH candidates. Additionally, in this example, the end of the PDCCH reception may be the end of the PDCCH candidate with the later end. When the UE does not need to monitor one of the two PDCCH candidates, the PDCCH reception may also include the two PDCCH candidates. In this example, aspects described herein may relate to indicating or determining which PDCCH candidate (or which DCI among the multiple DCIs received among the multiple PDCCH candidates) to use when applying a TCI update or indication.

[0038] In some aspects described herein, the UE may not expect the TCI indicated by a second DCI in any CC to become effective earlier than (or not later than) the TCI indicated by a first DCI that is received earlier than the second DCI. In one example, the network node may ensure this rule. In another example, the UE may ignore the TCI indication indicated by the first DCI that is received earlier than (or not later than) the second DCI corresponding to the currently indicated TCI. In other aspects described herein, the UE and / or the network node may handle a situation where multiple DCIs indicating TCI status updates or indications are to be applied in a similar time period (e.g., in the same time slot). For example, priority rules may be defined based on which TCI indication corresponds to a later monitoring occasion, based on the CCID of the CC through which the DCI is received or transmitted, and / or other considerations.

[0039] In any case, for example, defining or otherwise allowing the UE and / or the network node to apply the TCI status based on multiple received TCI status indications or updates may allow for predictable behavior of the UE and the network node, which may improve the accuracy of the TCI status indication or update procedure. This may improve the communication efficiency between the UE and the network node, thereby improving resource utilization, UE performance, and thus the user experience of using the UE, etc.

[0040] The features described below will be presented in more detail with reference to Figures 1 to 13 the features described above.

[0041] As used in this application, the terms "component", "module", "system", etc. are intended to include computer-related entities, such as but not limited to hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be but not limited to: a process running on a processor, a processor, an object, an executable file, an executing thread, a program, and / or a computer. By way of illustration, both an application running on a computing device and the computing device can be components. One or more components can exist in a process and / or an executing thread, and the components can be located in one computer and / or distributed between two or more computers. Additionally, these components are capable of executing from various computer-readable media having various data structures stored thereon. The components can communicate, for example, in a local and / or remote process manner through signals having one or more data packets (such as data from one component that interacts with another component in a local system, a distributed system, and / or across a network such as the Internet with other systems).

[0042] As used herein, a processor, at least one processor, and / or one or more processors (individually or in combination) configured to perform or operable to perform multiple actions are intended to include at least two different processors capable of performing different subsets, overlapping subsets, or non-overlapping subsets of the multiple actions, or a single processor capable of performing all of the multiple actions. In a non-limiting example of multiple processors capable of performing different actions in combination among the multiple actions, a description of a processor, at least one processor, and / or one or more processors configured to or operable to perform actions X, Y, and Z may include at least a first processor configured to or operable to perform a first subset of X, Y, and Z (e.g., perform X) and at least a second processor configured to or operable to perform a second subset of X, Y, and Z (e.g., perform Y and Z). Alternatively, a first processor, a second processor, and a third processor may be respectively configured to or operable to perform the respective actions among actions X, Y, and Z. It should be understood that any combination of one or more processors may each be configured to or operable to perform any one of the multiple actions or any combination of the multiple actions.

[0043] As used herein, a memory, at least one memory, and / or one or more memories (individually or in combination) configured to store or storing thereon instructions executable by one or more processors to perform a plurality of actions are intended to include at least two different memories of different subsets, overlapping subsets, or non-overlapping subsets capable of storing instructions for different subsets, overlapping subsets, or non-overlapping subsets of the plurality of actions, or a single memory capable of storing instructions for performing all of the plurality of actions. In a non-limiting example of one or more memories (individually or in combination) capable of storing different subsets of instructions for performing different actions of the plurality of actions, a description of a memory, at least one memory, and / or one or more memories configured to or operable to store or storing thereon instructions for performing actions X, Y, and Z may include at least a first memory configured to or operable to store or storing thereon a first subset of instructions (e.g., instructions for performing X) for a first subset of X, Y, and Z, and at least a second memory configured to or operable to or storing thereon a second subset of instructions (e.g., instructions for performing Y and Z) for a second subset of X, Y, and Z. Alternatively, a first memory, a second memory, and a third memory may be respectively configured to store or storing thereon a respective one of a first subset of instructions for performing X, a second subset of instructions for performing Y, and a third subset of instructions for performing Z. It should be understood that any combination of one or more memories may each be configured to or operable to store or storing thereon any one of the instructions or any combination of these instructions executable by one or more processors to perform any one of the plurality of actions or any combination of the plurality of actions. Further, one or more processors may each be coupled to at least one of the one or more memories and configured to or operable to execute instructions to perform the plurality of actions. For example, in the above non-limiting example of different subsets of instructions for performing actions X, Y, and Z, a first processor may be coupled to the first memory storing instructions for performing action X, at least a second processor may be coupled to at least a second memory storing instructions for performing actions Y and Z, and the first processor and the second processor may jointly execute the respective subsets of instructions to complete the performance of actions X, Y, and Z. Alternatively, three processors may access one memory among three different memories, each of the three memories storing instructions for performing action X, Y, or Z, and the three processors may jointly execute the respective subsets of instructions to complete the performance of actions X, Y, and Z. Alternatively, a single processor may execute instructions stored on a single memory or distributed over multiple memories to complete the performance of actions X, Y, and Z.

[0044] The techniques described herein can be used in various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, single-carrier FDMA, and other systems. The terms "system" and "network" are often used interchangeably. CDMA systems may implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers the IS-2000, IS-95, and IS-856 standards. Release 0 and A of IS-2000 are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems may implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA systems may implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM TM etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents of an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents of an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used in the above systems and radio technologies and other systems and radio technologies, including cellular (e.g., LTE) communication on a shared radio frequency spectrum band. However, the following description describes the LTE / LTE-A system for example purposes and uses the LTE term in most of the following description, but these techniques can also be applied outside of LTE / LTE-A applications (e.g., applied to the Fifth Generation (5G) New Radio (NR) network or other next-generation communication systems).

[0045] The following description provides examples and is not intended to limit the scope, applicability, or examples set forth in the claims. The functions and arrangements of the elements discussed may be changed without departing from the scope of the disclosure. Various procedures or components may be omitted, replaced, or added as appropriate for each example. For example, the methods described may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with respect to some examples may be combined in other examples.

[0046] Aspects or features will be presented with respect to a system that may include multiple devices, components, modules, etc. It should be understood and appreciated that various systems may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in connection with the figures. Combinations of these methods may also be used.

[0047] Figure 1 FIG. is an example diagram illustrating a wireless communication system and an access network 100. A wireless communication system (also referred to as a wireless wide area network (WWAN)) may include base stations 102, UEs 104, an evolved packet core (EPC) 160, and / or a 5G core (5GC) 190. The base stations 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells may include base stations. Small cells may include femto cells, pico cells, and micro cells. In an example, the base stations 102 may further include gNBs 180, as further described herein. In one example, in accordance with aspects described herein, some nodes of the wireless communication system may have a modem 340 and a UE communication component 342 for applying a TCI state based on multiple received DCIs. Additionally, in accordance with aspects described herein, some nodes may have a modem 440 and a BS communication component 442 for configuring a UE to apply a TCI state based on multiple received DCIs. Although the UE 104 is shown as having a modem 340 and a UE communication component 342, and the base station 102 / gNB 180 is shown as having a modem 440 and a BS communication component 442, this is an illustrative example, and substantially any node or any type of node may include a modem 340 and a UE communication component 342 and / or a modem 440 and a BS communication component 442 for providing the corresponding functionality described herein.

[0048] The base station 102 configured for 4G LTE (which may be collectively referred to as the evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a backhaul link 132 (e.g., using the S1 interface). The base station 102 configured for 5G NR (which may be collectively referred to as the Next Generation RAN (NG-RAN)) can interface with the 5GC 190 via a backhaul link 184. Among other functions, the base station 102 can perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, radio access network information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 can communicate directly or indirectly with each other (e.g., via the EPC 160 or 5GC 190) on a backhaul link 134 (e.g., using the X2 interface). The backhaul link 134 can be wired or wireless.

[0049] Base station 102 may communicate wirelessly with one or more UEs 104. Each base station in base station 102 may provide communication coverage for a corresponding geographical coverage area 110. There may be overlapping geographical coverage areas 110. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved Node B (eNB) (HeNB) that may serve a restricted group (which may be referred to as a closed subscriber group (CSG)). The communication link 120 between base station 102 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. Base station 102 / UE104 may use up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) of bandwidth per carrier allocated in carrier aggregation of up to Yx MHz (e.g., corresponding to x component carriers) of transmission in the DL and / or UL directions. These carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric for DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). A component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0050] In another example, certain UEs 104 may use device-to-device (D2D) communication link 158 to communicate with each other. D2D communication link 158 may use DL / UL WWAN spectrum. D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be via various wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0051] The wireless communication system may further include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a Clear Channel Assessment (CCA) before communication to determine whether the channel is available.

[0052] The small cell 102' may operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell 102' may adopt NR and use the same 5 GHz unlicensed spectrum as that used by the Wi-Fi AP 150. The small cell 102' adopting NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network.

[0053] The base station 102 (whether it is a small cell 102' or a large cell (e.g., a macro base station)) may include an eNB, a gNodeB (gNB), or other types of base stations. Some base stations, such as the gNB 180, may operate in the traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with the UE 104. When the gNB 180 operates at mmW or near mmW frequencies, the gNB 180 may be referred to as a mmW base station. The Extremely High Frequency (EHF) is a part of the RF in the electromagnetic spectrum. The EHF has a range of 30 GHz to 300 GHz, with wavelengths between 1 millimeter and 10 millimeters. The radio waves in this frequency band may be referred to as millimeter waves. The near mmW may extend down to a frequency of 3 GHz, with a wavelength of 100 millimeters. The Super High Frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communication using the mmW / near mmW radio frequency band has extremely high path loss and short distances. The mmW base station 180 may use beamforming 182 together with the UE 104 to compensate for the extremely high path loss and short distances. The base station 102 mentioned in this article may include the gNB 180.

[0054] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that processes signaling between the UE 104 and the EPC 160. Generally speaking, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are passed through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to an IP service 176. The IP service 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functions for MBMS user service configuration and delivery. The BM-SC 170 may serve as an entry point for MBMS transmissions sent by content providers, may be used to authorize and initiate MBMS bearer services in a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area for a particular broadcast service, and may be responsible for session management (start / stop) and for collecting eMBMS-related charging information.

[0055] The 5GC 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may communicate with a Unified Data Management (UDM) 196. The AMF 192 may be a control node that processes signaling between the UE 104 and the 5GC 190. Generally speaking, the AMF 192 may provide QoS flow and session management. User Internet Protocol (IP) packets (e.g., from one or more UEs 104) may be transmitted through the UPF 195. The UPF 195 may provide UE IP address allocation and other functions for one or more UEs. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS streaming service, and / or other IP services.

[0056] A base station may also be referred to as a gNB, Node B, evolved Node B (eNB), access point, base station transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmission reception point (TRP), or some other suitable term. Base station 102 provides an access point for UE 104 to EPC 160 or 5GC 190. Examples of UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other device with similar functionality. Some of the UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). IoT UEs may include machine type communication (MTC) / enhanced MTC (eMTC, also referred to as Category (CAT)-M or Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, and other types of UEs. In this disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

[0057] The deployment of a communication system, such as a 5G New Radio (NR) system, can be arranged with various components or constituent parts in multiple ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, radio access network (RAN) nodes, core network nodes, network elements, or network equipment, such as a base station (BS, e.g., BS102), or one or more units (or one or more components) performing base station functionality, can be implemented in a centralized architecture or a distributed architecture. For example, a BS, such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit receive point (TRP), or cell, etc., can be implemented as a centralized base station (also referred to as a stand-alone BS or monolithic BS) or a distributed base station.

[0058] A centralized base station can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A distributed base station can be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. A DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0059] Base station type operations or network designs can consider the aggregation characteristics of base station functionality. For example, a distributed base station can be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration initiated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also referred to as a cloud radio access network (C-RAN)). The distribution can include distributing functions across two or more units at various physical locations, as well as virtually distributing the functions of at least one unit, which can achieve flexibility in network design. The various units of a distributed base station or a distributed RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0060] In an example, the BS communication component 442 may send and / or the UE communication component 342 may receive TCI state updates or indication information in multiple DCIs via one or more CCs. For example, the UE communication component 342 and / or the BS communication component 442 may apply the TCI state update or indication from a given DCI among multiple DCIs, where these DCIs are received in the same time period (e.g., the same time slot). In another example, the BS communication component 442 may avoid sending TCI state updates or indications between the time when an initial TCI state update or indication is transmitted and the time when the UE applies the initial TCI state update or indication. In yet another example, the UE communication component 342 may ignore or avoid applying TCI state updates or indications that are received before the initial TCI state update or indication and are to be applied after the initial TCI state update or indication. In these examples and / or other examples described herein, the UE 104 and the base station 102 may apply the same TCI state, where multiple DCIs indicating the TCI state for one or more associated CCs are received.

[0061] Figure 2 A diagram illustrating an example of an exemplary disaggregated base station 200 architecture is shown. The disaggregated base station 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both). The CU 210 may communicate with one or more distributed units (DUs) 230 via a respective midhaul link (such as an F1 interface). The DU 230 may communicate with one or more radio units (RUs) 240 via a respective fronthaul link. The RU 240 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some specific implementations, the UE 104 may be served simultaneously by multiple RUs 240.

[0062] Each of the units (e.g., CU 210, DU 230, RU 240, and the near RT RIC 225, non-RT RIC 215, and SMO framework 205) may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or the associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, the units may include a wired interface that is configured to receive or transmit signals to one or more of the other units via the wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or transmit signals, or both, to one or more of the other units via the wireless transmission medium.

[0063] In some aspects, the CU 210 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may utilize an interface that is configured to communicate signals with other control functions hosted by the CU 210. The CU 210 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some embodiments, the CU 210 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, the CU 210 may be implemented to communicate with the DU 230 for network control and signaling.

[0064] The DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, the DU 230 may host one or more of the radio link control (RLC) layer, the media access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation, etc.) at least partially depending on a functional split (such as those defined by the 3rd Generation Partnership Project (3GPP)). In some aspects, the DU 230 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 230 or with control functions hosted by the CU 210.

[0065] Lower layer functionality may be implemented by one or more RUs 240. In some deployments, the RUs 240 controlled by the DU 230 may correspond to logical nodes that host 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, etc.) or both at least partially based on a functional split (such as a lower layer functional split). In such an architecture, the RUs 240 may be implemented to handle over-the-air (OTA) communication with one or more UEs 104. In some embodiments, the real-time and non-real-time aspects of the control plane and user plane communication with the RUs 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the implementation of the DU 230 and the CU 210 in a cloud-based RAN architecture (such as a vRAN architecture).

[0066] The SMO framework 205 can be configured to support the RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, and these dedicated physical resources can be managed via operation and maintenance interfaces (such as the O1 interface). For virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 290) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, the CU 210, DU 230, RU 240, and near RT RIC 225. In some specific implementations, the SMO framework 205 can communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some specific implementations, the SMO framework 205 can communicate directly with one or more RUs 240 via the O1 interface. The SMO framework 205 can also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205.

[0067] The non-RT RIC 215 can be configured to include logical functions that can enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near RT RIC 225 (such as via the A1 interface). The near RT RIC 225 can be configured to include logical functions that can enable near-real-time control and optimization of RAN elements and resources through interfaces (such as via the E2 interface) via data collection and actions, and this interface connects one or more CUs 210, one or more DUs 230, or both, and the O-eNB to the near RT RIC 225.

[0068] In some specific implementations, to generate the AI / ML models to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 225 and can be received from non-network data sources or from network functions at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune the RAN behavior or performance. For example, the non-RT RIC 215 may monitor the long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 205 (such as reconfiguration via O1) or via creating RAN management policies (such as A1 policies).

[0069] In an example, as described herein, the BS communication component 442 may be implemented at least partially within the CU 210 and may send TCI state updates or indications to the UE, apply TCI state updates or indications to the UE, etc., via one or more DUs 230, and send configuration information to the UE, etc., via one or more DUs 230. In another example, as described herein, the BS communication component 442 may be implemented at least partially within the DU 230 and may send TCI state updates or indications to the UE, apply TCI state updates or indications to the UE, etc., via one or more RUs 240, etc.

[0070] Turning now Figures 3 to 13 , aspects are depicted with reference to one or more components and one or more methods that can perform the actions or operations described herein, where the aspects in the dashed lines may be optional. Although the operations described below in Figure 5 , Figure 6 , Figure 11 and Figure 12 are presented in a specific order and / or presented as being performed by example components, it should be understood that the ordering of these actions and the components performing the actions may vary depending on the specific implementation. Additionally, it should be understood that the actions, functions, and / or components described below may be performed by a specially programmed processor, a processor executing specially programmed software or a computer-readable medium, or any other combination of hardware components and / or software components capable of performing the described actions or functions.

[0071] Referring to Figure 3, An example of a specific implementation of UE 104 may include various components, some of which have been described above and are further described herein, including components such as one or more processors 312, one or more memories 316, and one or more transceivers 302 that communicate via one or more buses 344. For example, one or more processors 312 may include a single processor or multiple processors configured to perform one or more functions described herein. For example, multiple processors may be configured to perform a specific subset of the set of functions described herein, such that the multiple processors may perform the set of functions together. Similarly, for example, one or more memories 316 may include a single memory device or multiple memory devices configured to store instructions or parameters for performing one or more functions described herein. For example, multiple memory devices may be configured to store instructions or parameters for a specific subset of the set of functions described herein, such that the multiple memory devices together may store instructions or parameters for the set of functions. According to aspects described herein, one or more processors 312, one or more memories 316, and one or more transceivers 302 may operate in conjunction with modem 340 and / or UE communication component 342, which is used to apply TCI states based on multiple received DCIs.

[0072] In one aspect, one or more processors 312 may include modem 340 and / or may be part of modem 340 that uses one or more modem processors. Thus, various functions related to UE communication component 342 may be included in modem 340 and / or processor 312, and in one aspect, may be performed by a single processor, while in other aspects, different functions among these functions may be performed by a combination of two or more different processors. For example, in one aspect, one or more processors 312 may include a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receive processor, or any one or any combination of transceiver processors associated with transceiver 302. In other aspects, some of the features of one or more processors 312 and / or modem 340 that are associated with UE communication component 342 may be performed by transceiver 302.

[0073] Additionally, one or more memories 316 may be configured to store data used herein and / or a local version of an application 375, or one or more subcomponents of a UE communication component 342 and / or its subcomponents executed by at least one processor 312. The one or more memories 316 may include any type of computer-readable medium usable by a computer or at least one processor 312, such as random access memory (RAM), read-only memory (ROM), magnetic tape, magnetic disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In one aspect, for example, when the UE 104 is operating at least one processor 312 to execute one or more subcomponents of the UE communication component 342 and / or its subcomponents, the one or more memories 316 may be a non-transitory computer-readable storage medium storing one or more computer-executable codes defining one or more subcomponents of the UE communication component 342 and / or its subcomponents and / or data associated therewith.

[0074] The transceiver 302 may include at least one receiver 306 and at least one transmitter 308. The receiver 306 may include hardware, firmware, and / or software code executable by a processor that includes instructions and is stored in a memory (e.g., a computer-readable medium). The receiver 306 may be, for example, a radio frequency (RF) receiver. In one aspect, the receiver 306 may receive signals transmitted by at least one base station 102. Additionally, the receiver 306 may process such received signals and may also obtain measurements of these signals, such as but not limited to Ec / Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. The transmitter 308 may include hardware, firmware, and / or software code executable by a processor that includes instructions and is stored in a memory (e.g., a computer-readable medium). Suitable examples of the transmitter 308 may include but are not limited to an RF transmitter.

[0075] Furthermore, in one aspect, the UE 104 may include an RF front end 388 that may communicate operatively with one or more antennas 365 and the transceiver 302 to receive and transmit radio transmissions, e.g., wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by the UE 104. The RF front end 388 may be connected to one or more antennas 365 and may include one or more low noise amplifiers (LNAs) 390, one or more switches 392, one or more power amplifiers (PAs) 398, and one or more filters 396 for transmitting and receiving RF signals.

[0076] In one aspect, the LNA 390 can amplify the received signal to a desired output level. In one aspect, each LNA 390 can have a specified minimum gain value and a maximum gain value. In one aspect, the RF front end 388 can use one or more switches 392 to select a particular LNA 390 and its specified gain value based on the desired gain value for a particular application.

[0077] In addition, for example, the RF front end 388 can use one or more PAs 398 to amplify the signal for RF output to a desired output power level. In one aspect, each PA 398 can have a specified minimum gain value and a maximum gain value. In one aspect, the RF front end 388 can use one or more switches 392 to select a particular PA 398 and its specified gain value based on the desired gain value for a particular application.

[0078] Additionally, for example, the RF front end 388 can use one or more filters 396 to filter the received signal to obtain an input RF signal. Similarly, in one aspect, for example, corresponding filters 396 can be used to filter the output from the corresponding PAs 398 to generate an output signal for transmission. In one aspect, each filter 396 can be connected to a particular LNA 390 and / or PA 398. In one aspect, the RF front end 388 can use one or more switches 392 to select a transmit path or a receive path that uses the specified filter 396, LNA 390, and / or PA 398 based on a configuration specified by the transceiver 302 and / or the processor 312.

[0079] Accordingly, the transceiver 302 can be configured to transmit and receive wireless signals via the RF front end 388 through one or more antennas 365. In one aspect, the transceiver can be tuned to operate at a specified frequency such that the UE 104 can communicate with, for example, one or more base stations 102 or with one or more cells associated with one or more base stations 102. In one aspect, for example, the modem 340 can configure the transceiver 302 to operate at a specified frequency and power level based on the UE configuration of the UE 104 and the communication protocol used by the modem 340.

[0080] In one aspect, the modem 340 can be a multi-band multi-mode modem that can process digital data and communicate with the transceiver 302 such that the transceiver 302 is used to transmit and receive digital data. In one aspect, the modem 340 can be multi-band and configured to support multiple frequency bands for a particular communication protocol. In one aspect, the modem 340 can be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, the modem 340 can control one or more components of the UE 104 (e.g., the RF front end 388, the transceiver 302) to implement the transmission and / or reception of signals from the network based on a specified modem configuration. In one aspect, the modem configuration can be based on the mode of the modem and the frequency band used. In another aspect, the modem configuration can be based on UE configuration information associated with the UE 104 provided by the network during cell selection and / or cell reselection.

[0081] In one aspect, according to the aspects described herein, the UE communication component 342 can optionally include a DCI processing component 352 for processing DCI received from a network node, the DCI can include TCI state indication or update for one or more CCs; and / or a TCI application component 354 for applying the TCI state to one or more CCs based on one of the multiple received DCIs.

[0082] In one aspect, the processor 312 can correspond to one or more of the processors described in connection with the UE in Figure 13 Similarly, one or more memories 316 can correspond to one or more of the memories described in connection with the UE in Figure 13

[0083] Referring to Figure 4 ​, An example of a specific implementation of base station 102 (e.g., base station 102 and / or gNB 180, as described above) may include various components, some of which have been described above, but also includes components such as one or more processors 412, one or more memories 416, and one or more transceivers 402 that are in communication via one or more buses 444. For example, one or more processors 412 may include a single processor or multiple processors configured to execute one or more functions described herein. For example, multiple processors may be configured to execute a specific subset of the set of functions described herein, such that the multiple processors may execute the set of functions together. Similarly, for example, one or more memories 416 may include a single memory device or multiple memory devices configured to store instructions or parameters for executing one or more functions described herein. For example, multiple memory devices may be configured to store instructions or parameters for a specific subset of the set of functions described herein, such that the multiple memory devices together may store instructions or parameters for the set of functions. According to aspects described herein, one or more processors 412, one or more memories 416, and one or more transceivers 402 may operate in conjunction with modem 440 and BS communication component 442, which are used to configure the UE to apply TCI states based on multiple received DCIs.

[0084] Transceiver 402, receiver 406, transmitter 408, one or more processors 412, one or more memories 416, application 475, bus 444, RF front end 488, LNA 490, switch 492, filter 496, PA 498, and one or more antennas 465 may be the same as or similar to the corresponding components of UE 104 as described above, but are configured or otherwise programmed for base station operation rather than UE operation.

[0085] In one aspect, according to aspects described herein, BS communication component 442 may optionally include DCI component 452, which is used to send DCI to the UE to indicate TCI states for one or more CCs, scheduling resources (e.g., PDSCH, PUCCH, PUSCH resources, etc.); and / or TCI application component 454, which is used to apply TCI states to one or more CCs based on a DCI sent in one of the multiple sent DCIs.

[0086] In one aspect, processor 412 may correspond to one or more of the processors described in connection with the Figure 13 base station. Similarly, one or more memories 416 may correspond to one or more of the memories described in connection with the Figure 13 base station.

[0087] Figure 5 A flowchart illustrating an example of method 500 for applying a TCI state based on multiple received DCIs, in accordance with aspects described herein. Figure 6 A flowchart illustrating an example of method 600 for configuring a UE to apply a TCI state based on multiple received DCIs, in accordance with aspects described herein. In the example, UE 104 may use one or more of the components described in Figure 1 and Figure 3 to perform the functions described in method 500. In the example, base station 102 (e.g., a gNB, a monolithic base station, or a part of a split base station, etc.) may use one or more of the components described in Figure 1 and Figure 4 to perform the functions described in method 600. For ease of explanation, methods 500 and 600 are described in conjunction with each other; however, methods 500 and 600 do not need to be performed together and may in fact be performed independently using separate devices.

[0088] In method 600, at block 602, a first DCI may be transmitted indicating a first TCI state to be applied to a first CC at a first BAT. In one aspect, DCI component 452 (e.g., in conjunction with processor 412, one or more memories 416, transceiver 402, BS communication component 442, etc.) may transmit (e.g., for UE 104) a first DCI indicating a first TCI state to be applied to a first CC in a first BAT. For example, a network node may configure multiple TCI states in RRC signaling and / or activate multiple TCI states (e.g., a subset of the TCI states configured in RRC signaling) via MAC-CE. In the example, BS communication component 442 may transmit a DCI to indicate one of the configured or activated TCI states to be applied to a CC for communicating over the resources indicated in the DCI, etc. For example, DCI component 452 may transmit a DCI via PDCCH in a PDCCH monitoring occasion and / or may transmit a DCI in multiple PDCCH repetitions in multiple PDCCH monitoring occasions, as described above.

[0089] In method 600, at block 604, a second DCI indicating a second TCI state to be applied to a first CC or a second CC at a second BAT may be sent. In one aspect, a DCI component 452 (e.g., in conjunction with a processor 412, one or more memories 416, a transceiver 402, a BS communication component 442, etc.) may send (e.g., for UE 104) a second DCI indicating a second TCI state to be applied to a first CC or a second CC in a second BAT. For example, the DCI component 452 may send the second DCI via the first CC or the second CC, or send a second DCI that otherwise indicates the first CC or the second CC. Additionally, for example, the DCI component 452 may send the second DCI after sending the first DCI and before applying the first TCI state from the first DCI.

[0090] In method 500, at block 502, a first DCI indicating a first TCI state to be applied to a first CC at a first BAT may be received. In one aspect, a DCI processing component 352 (e.g., in conjunction with a processor 312, one or more memories 316, a transceiver 302, a UE communication component 342, etc.) may receive a first DCI indicating a first TCI state to be applied to a first CC in a first BAT. For example, the first DCI may identify the first TCI state as one of a plurality of configured or active TCI states (e.g., using an index in a list of active TCI state identifiers). For example, the DCI processing component 352 may receive the DCI via a PDCCH in a PDCCH monitoring occasion (which may also include a resource grant), and / or may receive the DCI in a plurality of PDCCH repetitions in a plurality of PDCCH monitoring occasions, as described above. In any case, for example, the DCI processing component 352 may apply a TCI state update or indication at or after the first BAT. Additionally, as described, the BAT may also be configured for UE104.

[0091] In method 500, at block 504, a second DCI indicating a second TCI state to be applied to a first CC or a second CC at a second BAT may be received. In one aspect, a DCI processing component 352 (e.g., in conjunction with a processor 312, one or more memories 316, a transceiver 302, a UE communication component 342, etc.) may receive a second DCI indicating a second TCI state to be applied to a first CC or a second CC in a second BAT. For example, the DCI processing component 352 may receive the second DCI via the first CC or the second CC, or receive a second DCI that otherwise indicates the first CC or the second CC. Additionally, for example, the DCI processing component 352 may receive the second DCI after sending the first DCI and before applying the first TCI state from the first DCI.

[0092] In some examples, the second TCI state may have a BAT in the same time period as the first TCI state, or in other words, the beam indication received later may become effective at an earlier time compared to the beam indication received earlier. For example, assume that the active BWP is taken into account when receiving the beam indication DCI (e.g., the first DCI with the first TCI state indication), or when the active BWP is taken into account when transmitting the ACK for the first DCI. After the BWP change, the second TCI state in the second DCI indication may become effective before or at the same time as the first TCI state (e.g., in the same time slot). In one example, the later DCI may reflect the latest decision of the network and may thus overwrite any earlier and conflicting DCIs. In the case where the TCI states are to be applied in the same time period (e.g., the same time slot), the network node and / or UE 104 may apply the first TCI state or the second TCI state based on one or more rules.

[0093] Thus, for example, in method 500, at block 506, in the case where the first BAT and the second BAT are in the same time period (e.g., in the same time slot), the first TCI state or the second TCI state may be applied to one or more of the first CC or the second CC in this time period at least partially based on the first attribute of the first DCI and the second attribute of the second DCI. In one aspect, the TCI application component 354 (e.g., in combination with the processor 312, one or more memories 316, transceiver 302, UE communication component 342, etc.) may apply the first TCI state or the second TCI state to one or more of the first CC or the second CC in this time period at least partially based on the first attribute of the first DCI and the second attribute of the second DCI in the case where the first BAT and the second BAT are in the same time period (e.g., in the same time slot). For example, the first attribute and the second attribute may be one or more of the monitoring occasion for the first DCI and the second DCI, the CC corresponding to the DCI, the BWP identifier (ID) corresponding to the DCI, the ACK time corresponding to the DCI, the control resource set (CORESET) ID corresponding to the DCI, the search space (SS) set ID corresponding to the DCI, etc.

[0094] Similarly, for example, in method 600, at block 606, in the case where the first BAT and the second BAT are within the same time period (e.g., within the same time slot), the first TCI state or the second TCI state may be applied to one or more of the first CC or the second CC during this time period at least in part based on the first attribute of the first DCI and the second attribute of the second DCI. In one aspect, the TCI application component 454 (e.g., in conjunction with the processor 412, one or more memories 416, transceiver 402, BS communication component 442, etc.) may, in the case where the first BAT and the second BAT are within the same time period (e.g., within the same time slot), apply the first TCI state or the second TCI state to one or more of the first CC or the second CC during this time period at least in part based on the first attribute of the first DCI and the second attribute of the second DCI. In this regard, the network node and the UE 104 may apply the same (or reciprocal) beam at a given point in time and may communicate using the same (or reciprocal) beam. In Figure 7 Examples are shown.

[0095] Figure 7 An example of a timeline 700 is illustrated in which multiple DCIs with TCI indication or update are conveyed. In timeline 700, DCI1 702 including a TCI1 state update or indication may be conveyed. The UE receiving DCI1 702 may be scheduled to send feedback (e.g., based on a k value as defined in 5G NR, or other offset from receiving DCI1 702) and may send an ACK for DCI1 at 704. The UE may apply the TCI1 state at time 706 after the BAT, which may correspond to a time slot. Additionally, in timeline 700, an active BWP change may be received at 708 or 710. For example, the network node may change the BWP for one or more CCs at 708 or 710 using RRC signaling, MAC-CE, DCI, etc. Further, in timeline 700, DCI2 712 including a TCI2 state update or indication may be conveyed. The UE receiving DCI2 712 may be scheduled to send feedback (e.g., based on the k value or other offset from receiving DCI2 712) and may send an ACK for DCI2 at 714. The UE may also apply the TCI2 state at time 706 after the BAT, which may be due to the BWP change at 708 or 710. In this example, and as described above and further herein, the TCI application component 354 of the UE 104 and / or the TCI application component 454 of the network node may apply the TCI 1 state or the TCI2 state to one or more CCs based on one or more rules, associated parameters, etc.

[0096] In method 600, optionally at block 608, a configuration for applying TCI state to the first CC and the second CC in the CC list may be sent. In one aspect, the BS communication component 442 (e.g., in conjunction with the processor 412, one or more memories 416, transceiver 402, etc.) may send (e.g., for UE 104) a configuration for applying TCI state to the first CC and the second CC in the CC list. For example, the BS communication component 442 may use RRC signaling, MAC-CE, DCI, etc. to send this configuration and configure multiple CCs in the CC list, where the CC list may be related to applying the same TCI state to the CCs. In this regard, when a network node configures a TCI state for one CC (e.g., in the DCI received via or otherwise indicating that one CC), this may indicate applying the TCI state to that one CC and any other CCs in the same CC list as that one CC.

[0097] In method 500, optionally at block 508, a configuration for applying TCI state to the first CC and the second CC in the CC list may be received. In one aspect, the UE communication component 342 (e.g., in conjunction with the processor 312, one or more memories 316, transceiver 302, etc.) may receive a configuration for applying TCI state to the first CC and the second CC in the CC list. For example, the UE communication component 342 may use RRC signaling, MAC-CE, DCI, etc. to receive this configuration and configure multiple CCs in the CC list, where the CC list may be related to applying the same TCI state to the CCs in the list. In this regard, when a network node configures a TCI state for one CC (e.g., in the DCI received via or otherwise indicating that one CC), the TCI application component 354 may apply the TCI state to that one CC and any other CCs in the same CC list as that one CC.

[0098] In this example, the first DCI and the second DCI may be associated with different CCs, and the TCI application component 354 and / or 454 may apply the TCI state to each of the different CCs based on the CC being configured in a CC list and one or more rules having a BAT in the same or a similar time period (e.g., within a time slot) for selecting which TCI state to apply together with these TCI states. For example, rules may be defined to prioritize the DCI. Among all CCs sharing the same TCI indication, if at least two different TCI indications are simultaneously in effect in a CC, the TCI indications may be prioritized by rules, and the prioritized TCI may be applied. Priority rules may be defined based on a first attribute and a second attribute (e.g., based on comparing the first attribute with the second attribute, or based on the first attribute and the second attribute to otherwise select one of the first TCI or the second TCI).

[0099] For example, the TCI application component 354 and / or 454 may apply the first TCI state or the second TCI state based on priority rules considering one or more of the following aspects of the TCI state (and / or the corresponding DCI), and / or may also define a tie-breaking order for when to apply the TCI state at the same time period: the TCI indication corresponding to a later monitoring occasion of the corresponding DCI may be prioritized; the TCI indication indicated in the DCI for the CC having the lowest (or highest or specific) CC ID may be prioritized; the TCI indication indicated in the DCI for the BWP having the lowest (or highest or specific) BWP ID may be prioritized; the TCI indication indicated as having the earliest (or latest or specific) ACK time may be prioritized; the TCI indication having the lowest (or highest or specific) CORE SET ID may be prioritized; the TCI indication having the lowest (or highest or specific) SS set ID may be prioritized; etc. In a specific example, the TCI application component 354 and / or 454 may apply the first TCI state or the second TCI state based on which TCI indication corresponds to a later monitoring occasion of the corresponding DCI, and if the first TCI state and the second TCI state correspond to the same monitoring occasion of the DCI (or at least monitoring occasions in the same time period such as the same symbol or time slot), the TCI application component 354 and / or 454 may apply the first TCI state or the second TCI state based on the CC ID of the CC through which the corresponding TCI state is received in the corresponding DCI (e.g., the TCI application component 354 and / or 454 may apply the TCI state corresponding to the lowest CC ID). In Figure 8 an example is shown.

[0100] Figure 8An example of a timeline 800 for receiving multiple DCIs with TCI state updates or indications is illustrated. In the timeline 800, the DCIs are received via CC0 and CC1 that can be associated with each other in a CC list. For example, in the timeline 800, DCI1 802 can be received via CC0 and can include TCI1 as a unified TCI (e.g., unified DL and UL) based on CORESET0. Additionally, in the timeline 800, DCI2 804 can be received via CC1 and can include TCI2 as a unified TCI. Additionally, in the timeline 800, DCI3 806 can be received via CC0 and can include TCI3 as a unified TCI based on CORESET1 and SS3. Additionally, in the timeline 800, DCI4 808 can be received via CC1 and can include TCI4 as a unified TCI. Additionally, in the timeline 800, DCI5 810 can be received via CC0 and can include TCI5 as a unified TCI based on CORESET0 and SS1, and the repetition 812 of DCI5 can also be received via CC0 and can include TCI5 as a unified TCI based on CORESET1 and SS2.

[0101] In addition to the above rules, for example, in the case where the TCI state is associated with a PDCCH repetition (such as TCI 5), the TCI application component 354 and / or 454 can apply the TCI state based on the monitoring occasion of one of these repetitions (such as the earliest repetition or the latest repetition). In the example, the monitoring occasion can be the merger of all repetitions. In one example, the monitoring occasion for the rule for applying the TCI state can be determined based on the earliest symbol of the occasion, the last symbol in the earliest repetition, the last symbol of the occasion, etc. In the example of the timeline 800, and in the case where the monitoring occasion can be determined based on the earliest symbol of the occasion, the TCI application component 354 and / or 454 can apply TCI3 because TCI3 and TCI4 correspond to the latest monitoring occasion (e.g., DCI3 and DCI4 because TCI5 is considered based on the earliest symbol of DCI5 810), and TCI3 corresponds to the CC with a lower (e.g., more prioritized) CC ID of CC0.

[0102] For example, based on the indication in 5G NR TS 38.214, when the UE is about to transmit the last symbol of the PUCCH with HARQ-ACK information (the HARQ-ACK information corresponds to the lowest CCID in the latest occasion of one or more DCIs carrying TCI state indication and not requiring DL assignment or corresponds to the PDSCH scheduling by the DCI carrying TCI state indication), and if the indicated TCI state is different from the previously indicated TCI state, the indicated [TCI state] with [tci-StateId_r17] shall be applied starting from the first time slot, which is at least BeamAppTime_r17 symbols after the last symbol of the PUCCH. Both the first time slot and the BeamAppTime_r17 symbols are determined on the active BWP with the minimum SCS among the carriers applying beam indication. The UE may assume one indicated [TCI state] with [tci-StateId_r17] for DL and UL at a time, for DL only, or for UL only.

[0103] In the example, in method 500, optionally at block 510, a first ACK for the first DCI and a second ACK for the second DCI may be transmitted. In one aspect, the UE communication component 342 (e.g., in combination with the processor 312, one or more memories 316, transceiver 302, etc.) may transmit a first ACK for the first DCI and a second ACK for the second DCI. As described, for example, the TCI application component 354 may apply the TCI state based on the BAT starting from the time of transmitting the first ACK and / or the second ACK. In one example, in the case where the UE communication component 342 transmits the first ACK and the second ACK within the same time period (e.g., within the same time slot), the BATs for the first TCI state and the second TCI state may occur in the subsequent same time period. In the example, in method 600, optionally at block 610, a first ACK for the first DCI and a second ACK for the second DCI may be received. In one aspect, the BS communication component 442 (e.g., in combination with the processor 412, one or more memories 416, transceiver 402, etc.) may receive a first ACK for the first DCI and a second ACK for the second DCI (e.g., within the same time period). In Figure 9 The example is shown.

[0104] Figure 9An example of a timeline 900 for receiving multiple DCIs with TCI state updates or indications via multiple CCs and sending ACK feedback for the multiple DCIs is illustrated. In timeline 900, the DCIs are received via CC0 and CC1 that can be associated with each other in a CC list. For example, in timeline 900, DCI1 902 can be received via CC0 and can include TCI1 as a unified TCI (e.g., unified DL and UL) based on CORESET0. Additionally, in timeline 900, DCI2 904 can be received via CC1 and can include TCI2 as a unified TCI. Additionally, in timeline 900, DCI3 906 can be received via CC0 and can include TCI3 as a unified TCI based on CORESET1 and SS3. Additionally, in timeline 900, DCI4 908 can be received via CC1 and can include TCI4 as a unified TCI. Additionally, in timeline 900, DCI5 910 can be received via CC0 and can include TCI5 as a unified TCI based on CORESET0 and SS1, and the repetition 912 of DCI5 can also be received via CC0 and can include TCI5 as a unified TCI based on CORESET1 and SS2. In this example, PUCCH 914 can be scheduled for all of these DCIs and can include ACKs for DCI1, DCI2, DCI3, DCI4, DCI5. In this example, the BAT for applying all of DCI1, DCI2, DCI3, DCI4, DCI5 can be at 916. Thus, the TCI application component 354 and / or 454 can apply one of TCI state 1, TCI state 2, TCI state 3, TCI state 4, TCI state 5 based on the above priority rules.

[0105] Similarly, for example, the TCI application component 354 and / or 454 can apply TCI state 3 based on the latest monitoring occasion and the lowest CC ID. In other words, in this example, DCI1, DCI2, DCI3, DCI4, DCI5 are ACKed by the same PUCCH: based on the current rules, all TCI indications in the DCIs can be applied simultaneously. DCI3 and DCI4 are received last in time; the reception time of DCI5 is based on the earliest time of the occasion. DCI3 has a smaller CC ID than DCI4. DCI3 is selected to determine the TCI, and TCI3 can be applied. In one example, some PUCCHs in the PUCCH can include PUCCH repetitions, and the PUCCH repetitions can affect the BAT for the corresponding TCI state. If the PUCCH repetitions still overlap and result in a BAT in the same or a similar time period, the rules described herein can still be applied to determine the TCI state. For example, Figure 9Among DCI1, DCI2, DCI3, DCI4, and DCI5, they can be ACKed by different PUCCHs and / or corresponding repetitions, but the PUCCHs can still overlap in time. Therefore, DCI 1 - DCI5 can still be considered to be ACKed simultaneously. The overlap in time can mean: (1) overlap at the symbol granularity; (2) overlap at the slot granularity. For PUCCH repetitions, the overlap in time can be detected or determined based on any symbol in the repetition, or the last repetition, or the earliest repetition. In addition, the TCI state can be detected or determined separately for only DL, only UL, or combined DL and UL TCI state indications.

[0106] In one example, when the CCs are not in the same CC list, the rules can be applied by CC among all the DCIs that can be ACKed in the same PUCCH, and the TCI application components 354 and / or 454 can use the DCI received last in time to determine the TCI update (for example, the later received DCI can overwrite the earlier received DCI). When multiple DCIs are received at or during the same symbol in the CC, the DCI can be received using the CORESET ID, SS ID, etc. for tie-breaking (for example, to determine the DCI for which the TCI update is to be applied). For example, the DCI with a smaller CORESET ID or a smaller SS ID can overwrite the other DCIs used to apply the corresponding TCI state. However, when CC0 and CC1 are configured on the same list, the aspects described herein can apply to cases with PUCCH and PDCCH repetitions and / or be suitable for determining the DCI received last when the CCs have different SCSs.

[0107] For example, in the case where CC0 and CC1 are configured on the same list, the TCI update for all CCs in the CC list can be determined to be the TCI in the last received DCI among the DCIs that were last ACKed in the same symbol (or time slot). For example, the same time slot can be within the same PUCCH symbol. In another example, if multiple DCIs are received during a time that overlaps with the last received DCI, the TCI application component 354 and / or 454 can use the CC ID of the received DCI or the CC ID indicated in the DCI to select a DCI to determine the TCI update. For example, the overlap in time can refer to symbol-level overlap or time-slot-level overlap (e.g., two DCIs do not overlap in the same symbol but overlap in the same time slot), partial overlap such as when the CCs have different SCSs, the symbols can partially overlap (e.g., half-symbol overlap or half-time-slot overlap), etc. In another example, the TCI application component 354 and / or 454 can use a priority rule defined based on the CC ID (e.g., a smaller / larger CCID has a higher priority). In an example, if multiple DCIs are received during an overlapping time and have the same associated CC ID, the TCI application component 354 and / or 454 can use the CORESET ID to receive the DCI for tie-breaking (e.g., to determine the DCI for which to apply its TCI update). Further, if multiple DCIs are received with the same CORESET ID, the TCI application component 354 and / or 454 can use the search space ID to further break the tie (e.g., to determine the DCI for which to apply its TCI update).

[0108] Figure 10An example of a timeline 1000 is illustrated in which multiple DCIs with TCI indication or update are conveyed, and the multiple DCIs have BATs in different time periods. In timeline 1000, DCI1 1002 including a TCI1 status update or indication can be conveyed. A UE receiving DCI1 1002 can be scheduled to send feedback (e.g., based on a k value or other offset from receiving DCI1 1002) and can send an ACK for DCI1 at 1004 (e.g., after time k or other offset from receiving DCI1 1002). The UE can apply the TCI1 status after the BAT (shown as the BAT of the old BWP), which can correspond to a time slot. Additionally, in timeline 1000, an active BWP change can be received at 1008. For example, a network node can use RRC signaling, MAC-CE, DCI, etc. at 1008 to change the BWP for one or more CCs. Further, in timeline 1000, DCI2 1010 including a TCI2 status update or indication can be conveyed. A UE receiving DCI2 1010 can be scheduled to send feedback (e.g., based on a k value or other offset from receiving DCI2 1010) and can send an ACK for DCI2 at 1012. The UE can apply the TCI2 status after the BAT (shown as the BAT of the new BWP), which may be due to the BWP change at 1008. In this example, and as further described above and herein, the TCI application component 354 of UE 104 and / or the TCI application component 454 of the network node can apply the TCI 1 status or TCI2 status to one or more CCs based on one or more rules, associated parameters, etc.

[0109] In one example, out-of-order (OOO) rules similar to the rules for PDCCH, PDSCH, and corresponding ACK order in 5G NR can be used in this scenario. For example, in the OOO rules, a UE can expect that the ACK for an earlier PDSCH will not arrive later than the ACK for a later PDSCH, and the PDSCH scheduled by an earlier PDCCH should not arrive later than the PDSCH scheduled by a later PDCCH. The network node can ensure compliance with the OOO rules. In Figure 10 the example of, OOO rules can be added for DCI indication such that a UE does not expect the TCI indicated by a later received DCI in any CC to become effective earlier than (or not later than) the TCI indicated by an earlier received DCI, and the network node can ensure compliance with this rule. In Figure 10 another example of, a UE can ignore a TCI indication that is indicated by a DCI that is earlier than (or not later than) the DCI corresponding to the currently indicated TCI. Exemplifications are explained below with reference to Figure 11 and Figure 12 Explanation examples.

[0110] Figure 11 FIG. 1100 is a flow chart illustrating an example of a method for ignoring a TCI indication according to various aspects described herein, the TCI indication being indicated by a DCI earlier than the DCI corresponding to the current indication of the TCI. In the example, UE 104 may use one or more of the components described in FIGS. 1101 and 1102 to perform the functions described in method 1100. Figure 1 and Figure 3 to perform the functions described in method 1100.

[0111] In method 1100, at block 1102, a first DCI indicating a first TCI state to be applied to a first CC at a first BAT may be received. In one aspect, DCI processing component 352 (e.g., in combination with processor 312, one or more memories 316, transceiver 302, UE communication component 342, etc.) may receive a first DCI indicating a first TCI state to be applied to a first CC in a first BAT. For example, this may be similar to block 502 of method 500 described above in FIG. 1101. Figure 5 FIG. 1101.

[0112] In method 1100, at block 1104, a second DCI indicating a second TCI state to be applied to the first CC or a second CC at a second BAT may be received. In one aspect, DCI processing component 352 (e.g., in combination with processor 312, one or more memories 316, transceiver 302, UE communication component 342, etc.) may receive a second DCI indicating a second TCI state to be applied to the first CC or a second CC in a second BAT. For example, this may be similar to block 504 of method 500 described above in FIG. 1101, except that the second BAT may be in a different time period (e.g., a different time slot) than the first BAT, as shown, for example, in FIG. 1102. Figure 5 FIG. 1101, Figure 10 FIG. 1102.

[0113] In method 1100, optionally at block 1106, it may be determined whether the first DCI was received earlier than the second DCI. In one aspect, TCI application component 354 (e.g., in combination with processor 312, one or more memories 316, transceiver 302, UE communication component 342, etc.) may determine whether the first DCI was received earlier than the second DCI. If so, then in method 1100, optionally at block 1108, the first TCI state may be applied at the first BAT and the second TCI state may be applied at the second BAT. In one aspect, TCI application component 354 (e.g., in combination with processor 312, one or more memories 316, transceiver 302, UE communication component 342, etc.) may apply the first TCI state (e.g., for the first CC and / or the second CC) at the first BAT and may apply the second TCI state (e.g., for the first CC and / or the second CC) at the second BAT.

[0114] If the first DCI is not received earlier than the second DCI at block 1106, then optionally at block 1110, the first TCI state may be applied at the first BAT, and application of the second TCI state may be avoided at the second BAT. In one aspect, the TCI application component 354 (e.g., in conjunction with the processor 312, one or more memories 316, transceiver 302, UE communication component 342, etc.) may apply the first TCI state at the first BAT (e.g., for the first CC and / or the second CC) and may avoid applying the second TCI state at the second BAT (e.g., for the first CC and / or the second CC). This may be because the UE does not expect to receive the second DCI after receiving the first DCI (and before applying the first TCI state).

[0115] In method 1100, optionally at block 1112, a configuration may be received that configures the first CC and the second CC in a CC list for application of a TCI state. In one aspect, the UE communication component 342 (e.g., in conjunction with the processor 312, one or more memories 316, transceiver 302, etc.) may receive a configuration that configures the first CC and the second CC in a CC list for application of a TCI state. For example, the UE communication component 342 may receive this configuration using RRC signaling, MAC-CE, DCI, etc. and configure multiple CCs in the CC list, where the CC list may be related to applying the same TCI state to the CCs. In this regard, when a network node configures a TCI state for one CC (e.g., in the DCI that receives or otherwise indicates that one CC), the TCI application component 354 may apply that TCI state to that one CC and any other CCs in the same CC list as that one CC.

[0116] Figure 12 A flowchart illustrating an example of method 1200 for avoiding sending a TCI indication that is indicated by a DCI earlier than the DCI corresponding to the currently indicated TCI is shown. In the example, the base station 102 (e.g., a gNB, a monolithic base station, or a part of a decomposed base station, etc.) may use Figure 1 and Figure 4 one or more of the components described in

[0117] to perform the functions described in method 1200. Figure 6Block 602 of method 600 in

[0118] In method 1200, at block 1204, the second DCI indicating the second TCI state to be applied to the first CC or the second CC at the second BAT can be avoided in the case where the second BAT is earlier than the first BAT. In one aspect, the DCI component 452 (e.g., in conjunction with the processor 412, one or more memories 416, the transceiver 402, the BS communication component 442, etc.) can avoid sending the second DCI indicating the second TCI state to be applied to the first CC or the second CC in the second BAT in the case where the second BAT is earlier than the first BAT.

[0119] In method 1200, optionally at block 1206, a configuration for applying the TCI state to the first CC and the second CC in the CC list can be sent. In one aspect, the BS communication component 442 (e.g., in conjunction with the processor 412, one or more memories 416, the transceiver 402, etc.) can send (e.g., for the UE 104) a configuration for applying the TCI state to the first CC and the second CC in the CC list. For example, the BS communication component 442 can use RRC signaling, MAC-CE, DCI, etc. to send this configuration and configure multiple CCs in the CC list, where the CC list can be related to applying the same TCI state to the CCs. In this regard, when the network node configures the TCI state for one CC (e.g., in the DCI received or otherwise indicated through the one CC), this can indicate applying the TCI state to the one CC and any other CCs in the same CC list as the one CC.

[0120] Figure 13 is a block diagram of a MIMO communication system 1300 including the base station 102 and the UE 104. The MIMO communication system 1300 can illustrate aspects of the wireless communication access network 100 described with reference to Figure 1 The base station 102 can be an example of aspects of the base station 102 described with reference to Figure 1 The base station 102 can be equipped with the antenna 1334 and the antenna 1335, and the UE 104 can be equipped with the antenna 1352 and the antenna 1353. In the MIMO communication system 1300, the base station 102 may be capable of transmitting data simultaneously through multiple communication links. Each communication link can be referred to as a "layer", and the "rank" of the communication link can indicate the number of layers used for communication. For example, in a 2x2 MIMO communication system where the base station 102 transmits two "layers", the rank of the communication link between the base station 102 and the UE 104 is two.

[0121] At base station 102, a transmit (Tx) processor 1320 may receive data from a data source. The transmit processor 1320 may process the data. The transmit processor 1320 may also generate control symbols or reference symbols. A transmit MIMO processor 1330 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, or reference symbols if applicable, and may provide an output symbol stream to transmit modulators / demodulators 1332 and 1333. Each of the transmit modulators / demodulators 1332 to 1333 may process the respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each of the transmit modulators / demodulators 1332 to 1333 may further process the output sample stream (e.g., convert the output sample stream to analog, amplify, filter, and up-convert) to obtain a DL signal. In one example, the DL signals from the transmit modulators / demodulators 1332 and 1333 may be transmitted via antennas 1334 and 1335, respectively.

[0122] UE 104 may be an example of aspects of the UE 104 described in Figure 1 and Figure 3 . At UE 104, UE antennas 1352 and 1353 may receive the DL signals from base station 102 and may provide the received signals to transmit modulators / demodulators 1354 and 1355, respectively. Each of the transmit modulators / demodulators 1354 to 1355 may condition the respective received signal (e.g., filter, amplify, down-convert, and digitize the respective received signal) to obtain input samples. Each of the transmit modulators / demodulators 1354 to 1355 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 1356 may obtain the received symbols from the transmit modulators / demodulators 1354 and 1355, perform MIMO detection on the received symbols if applicable, and provide the detected symbols. A receive (Rx) processor 1358 may process (e.g., demodulate, de-interleave, and decode) the detected symbols, thereby providing decoded data for UE 104 to a data output, and providing decoded control information to processor 1380 or one or more memories 1382.

[0123] In some cases, processor 1380 may execute stored instructions to instantiate UE communication component 342 (see, e.g., Figure 1 and Figure 3 ).

[0124] On the uplink (UL), at the UE 104, the transmit processor 1364 may receive and process data from a data source. The transmit processor 1364 may also generate reference symbols for reference signals. Symbols from the transmit processor 1364 may be pre-coded by the transmit MIMO processor 1366 (if applicable), further processed by the modulator / demodulator 1354 and the modulator / demodulator 1355 (e.g., for single-carrier FDMA, etc.), and transmitted to the base station 102 according to communication parameters received from the base station 102. At the base station 102, the UL signals from the UE 104 may be received by the antennas 1334 and 1335, processed by the modulator / demodulator 1332 and the modulator / demodulator 1333, detected by the MIMO detector 1336 (if applicable), and further processed by the receive processor 1338. The receive processor 1338 may provide the decoded data to the data output and processor 1340 or one or more memories 1342.

[0125] In some cases, the processor 1340 may execute stored instructions to instantiate the BS communication component 442 (see, e.g., Figure 1 and Figure 4 ).

[0126] The components of the UE 104 may be implemented singly or jointly using one or more ASICs, where one or more ASICs are adapted to perform some or all of the applicable functions in hardware. Each of the indicated modules may be a component for performing one or more functions related to the operation of the MIMO communication system 1300. Similarly, the components of the base station 102 may be implemented singly or jointly using one or more application-specific integrated circuits (ASICs), where the one or more ASICs are adapted to perform some or all of the applicable functions in hardware. Each of the indicated components may be a component for performing one or more functions related to the operation of the MIMO communication system 1300.

[0127] The following aspects are merely illustrative, and aspects thereof may be combined with aspects of other embodiments or teachings described herein without limitation.

[0128] Aspect 1 is a method for wireless communication at a UE, the method comprising: receiving a first DCI indicating a first TCI state to be applied to a first CC at a first BAT; receiving a second DCI indicating a second TCI state to be applied to the first CC or a second CC at a second BAT; and, in a case where the first BAT and the second BAT are within the same time period, applying the first TCI state or the second TCI state to one or more of the first CC or the second CC at least partially based on a first attribute of the first DCI and a second attribute of the second DCI during the time period.

[0129] In aspect 2, the method according to aspect 1 includes wherein the first attribute includes a first monitoring occasion associated with the first DCI, and the second attribute includes a second monitoring occasion associated with the second DCI.

[0130] In aspect 3, the method according to aspect 2 includes wherein applying the first TCI state or the second TCI state includes: applying the first TCI state when the first monitoring occasion is later than the second monitoring occasion.

[0131] In aspect 4, the method according to any one of aspects 1 to 3 includes wherein the first attribute includes a first CCID associated with the first DCI, and the second attribute includes a second CC ID associated with the second DCI.

[0132] In aspect 5, the method according to aspect 4 includes wherein applying the first TCI state or the second TCI state includes: applying the first TCI state based on the first CC ID and the second CC ID when the first monitoring occasion of the first DCI is within the second monitoring occasion of the second DCI in time or at least partially overlaps with the second monitoring occasion.

[0133] In aspect 6, the method according to aspect 5 includes wherein the first DCI and the second DCI do not include a downlink channel assignment.

[0134] In aspect 7, the method according to any one of aspects 1 to 6 includes wherein the first attribute includes a first BWP ID associated with the first DCI, and the second attribute includes a second BWP ID associated with the second DCI.

[0135] In aspect 8, the method according to any one of aspects 1 to 7 includes wherein the first attribute includes a first ACK time associated with the first DCI, and the second attribute includes a second ACK time associated with the second DCI.

[0136] In aspect 9, the method according to any one of aspects 1 to 8 includes wherein the first attribute includes a first BWP ID associated with the first DCI, and the second attribute includes a second BWP ID associated with the second DCI.

[0137] In aspect 10, the method according to any one of aspects 1 to 9 includes wherein the first attribute includes a first CORESET ID associated with the first DCI, and the second attribute includes a second CORESET ID associated with the second DCI.

[0138] In aspect 11, the method according to any one of aspects 1 to 10 includes wherein the first attribute includes a first SS set ID associated with the first DCI, and the second attribute includes a second SS set ID associated with the second DCI.

[0139] In aspect 12, the method according to any one of aspects 1 to 11 includes wherein the first attribute includes a set of a plurality of first monitoring occasions associated with the first DCI, and the second attribute includes at least one second monitoring occasion associated with the second DCI, wherein applying the first TCI state or the second TCI state is based on one first monitoring occasion in the set of the plurality of first monitoring occasions and the at least one second monitoring occasion.

[0140] In aspect 13, the method according to aspect 12 includes wherein the one first monitoring occasion in the set of the plurality of first monitoring occasions includes one of the following: the earliest first monitoring occasion in the set of the plurality of first monitoring occasions, the latest first monitoring occasion in the set of the plurality of first monitoring occasions, or the latest first monitoring occasion in the earliest repetition of the first DCI in the set of the plurality of first monitoring occasions.

[0141] In aspect 14, the method according to any one of aspects 1 to 13 includes sending a first ACK for the first DCI and a second ACK for the second DCI.

[0142] In aspect 15, the method according to aspect 14 includes wherein applying the first TCI state or the second TCI state is further based on sending the first ACK and the second ACK in the same feedback time period.

[0143] In aspect 16, the method according to any one of aspects 1 to 15 includes wherein the first attribute includes a first time of receiving the first DCI and a second time of receiving the second DCI.

[0144] In aspect 17, the method according to any one of aspects 1 to 16 includes wherein in the case where the first DCI and the second DCI are received within the same or partially overlapping DCI time, the first attribute includes a first CORESET ID or a first SS set ID associated with the first DCI, and the second attribute includes a second CORESET ID or a second SS ID associated with the second DCI.

[0145] In aspect 18, the method according to any one of aspects 1 to 17 includes where applying the first TCI state or the second TCI state during the time period includes: applying the first TCI state or the second TCI state as one of an uplink TCI state, a downlink TCI state, or a unified uplink and downlink TCI state.

[0146] In aspect 19, the method according to any one of aspects 1 to 18 includes receiving a configuration that configures a first CC and a second CC in a CC list for applying a TCI state.

[0147] In aspect 20, the method according to aspect 19 includes where applying the first TCI state or the second TCI state includes: applying the first TCI state or the second TCI state to all CCs in the CC list.

[0148] Aspect 21 is a method for wireless communication at a network node, the method including: transmitting a first DCI indicating a first TCI state to be applied to a first CC at a first BAT; transmitting a second DCI indicating a second TCI state to be applied to the first CC or a second CC at a second BAT; and in the case where the first BAT and the second BAT are within the same time period, applying the first TCI state or the second TCI state to one or more of the first CC or the second CC during the time period at least partially based on a first attribute of the first DCI and a second attribute of the second DCI.

[0149] In aspect 22, the method according to aspect 21 includes where the first attribute includes a first monitoring occasion associated with the first DCI, and the second attribute includes a second monitoring occasion associated with the second DCI.

[0150] In aspect 23, the method according to aspect 22 includes where applying the first TCI state or the second TCI state includes: applying the first TCI state in the case where the first monitoring occasion is later than the second monitoring occasion.

[0151] In aspect 24, the method according to any one of aspects 21 to 23 includes where the first attribute includes a first CC ID associated with the first DCI, and the second attribute includes a second CC ID associated with the second DCI.

[0152] In aspect 25, the method according to aspect 24 includes where applying the first TCI state or the second TCI state includes: based on the first CC ID and the second CC ID, applying the first TCI state when a first monitoring occasion of the first DCI is within or at least partially overlaps in time with a second monitoring occasion of the second DCI.

[0153] In aspect 26, the method according to aspect 25 includes where the first DCI and the second DCI do not include a downlink channel assignment.

[0154] In aspect 27, the method according to any one of aspects 21 to 26 includes where the first attribute includes a first BWP ID associated with the first DCI, and the second attribute includes a second BWP ID associated with the second DCI.

[0155] In aspect 28, the method according to any one of aspects 21 to 27 includes where the first attribute includes a first ACK time associated with the first DCI, and the second attribute includes a second ACK time associated with the second DCI.

[0156] In aspect 29, the method according to any one of aspects 21 to 28 includes where the first attribute includes a first BWP ID associated with the first DCI, and the second attribute includes a second BWP ID associated with the second DCI.

[0157] In aspect 30, the method according to any one of aspects 21 to 29 includes where the first attribute includes a first CORE SET ID associated with the first DCI, and the second attribute includes a second CORE SET ID associated with the second DCI.

[0158] In aspect 31, the method according to any one of aspects 21 to 30 includes where the first attribute includes a first SS set ID associated with the first DCI, and the second attribute includes a second SS set ID associated with the second DCI.

[0159] In aspect 32, the method according to any one of aspects 21 to 31 includes where the first attribute includes a set of multiple first monitoring occasions associated with the first DCI, and the second attribute includes at least one second monitoring occasion associated with the second DCI, where applying the first TCI state or the second TCI state is based on one first monitoring occasion in the set of multiple first monitoring occasions and the at least one second monitoring occasion.

[0160] In aspect 33, the method according to aspect 32 includes that one of the first monitoring opportunities in the set of multiple first monitoring opportunities includes one of the following: the earliest first monitoring opportunity in the set of multiple first monitoring opportunities, the latest first monitoring opportunity in the set of multiple first monitoring opportunities, or the latest first monitoring opportunity in the earliest repetition of the first DCI in the set of multiple first monitoring opportunities.

[0161] In aspect 34, the method according to any one of aspects 21 to 33 includes receiving a first ACK for the first DCI and a second ACK for the second DCI.

[0162] In aspect 35, the method according to aspect 34 includes that applying the first TCI state or the second TCI state is further based on the scheduling resources for receiving the first ACK and the second ACK in the same feedback time period.

[0163] In aspect 36, the method according to any one of aspects 21 to 35 includes that the first attribute includes the first time for sending the first DCI and the second time for sending the second DCI.

[0164] In aspect 37, the method according to any one of aspects 21 to 36 includes that when the first DCI and the second DCI are sent within the same or partially overlapping DCI time, the first attribute includes the first CORESET ID or the first SS set ID associated with the first DCI, and the second attribute includes the second CORESET ID or the second SS ID associated with the second DCI.

[0165] In aspect 38, the method according to any one of aspects 21 to 37 includes that applying the first TCI state or the second TCI state within the time period includes: applying the first TCI state or the second TCI state as one of an uplink TCI state, a downlink TCI state, or a unified uplink and downlink TCI state.

[0166] In aspect 39, the method according to any one of aspects 21 to 38 includes sending a configuration for configuring the first CC and the second CC in the CC list for applying the TCI state.

[0167] In aspect 40, the method according to aspect 39 includes that applying the first TCI state or the second TCI state includes: applying the first TCI state or the second TCI state to all CCs in the CC list.

[0168] Aspect 41 is a method for wireless communication at a UE, the method comprising: receiving a first (DCI) indicating a first TCI state to be applied to a first CC at a first BAT; receiving a second DCI indicating a second TCI state to be applied to the first CC or a second CC at a second BAT, wherein the first BAT is earlier in time than the second BAT; in the case where the first DCI is received earlier than the second DCI, applying the first TCI state at the first BAT and applying the second TCI state at the second BAT; and in the case where the second DCI is received earlier than the first DCI, applying the first TCI state at the first BAT and refraining from applying the second TCI state at the second BAT.

[0169] In aspect 42, the method of aspect 41 comprises receiving a configuration that configures a first CC and a second CC in a CC list for applying TCI states.

[0170] Aspect 43 is a method for wireless communication at a network node, the method comprising: transmitting a first DCI indicating a first TCI state to be applied to a first CC at a first BAT; and in the case where the second BAT is earlier than the first BAT, refraining from transmitting a second DCI indicating a second TCI state to be applied to the first CC or a second CC at the second BAT after the first DCI.

[0171] In aspect 44, the method of aspect 43 comprises transmitting a configuration that configures a first CC and a second CC in a CC list for applying TCI states.

[0172] Aspect 45 is a device for wireless communication, the device comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and operative when executed by the one or more processors to cause the device to perform any of the methods according to aspects 1 to 44.

[0173] Aspect 46 is a device for wireless communication, the device comprising components for performing any of the methods according to aspects 1 to 44.

[0174] Aspect 47 is one or more computer-readable media comprising code executable by one or more processors for wireless communication, the code comprising code for performing any of the methods according to aspects 1 to 44.

[0175] The above specific embodiments described in conjunction with the accompanying drawings describe examples and do not represent the only examples that can be implemented or fall within the scope of the claims. The term "example" as used in this specification means "serving as an example, instance, or illustration", rather than "preferred" or "superior to other examples". The specific embodiments include specific details for providing an understanding of the described technology. However, these technologies can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0176] Information and signals can be represented using any of a variety of different technologies and processes. For example, the data, instructions, commands, information, signals, bits, symbols, and chips mentioned in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, computer-executable code or instructions stored on a computer-readable medium, or any combination thereof.

[0177] The various illustrative blocks and components described in connection with the present disclosure can be implemented or executed using a specially programmed device, such as, but not limited to: a processor for performing the functions described herein, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. Although a specially programmed processor can be a microprocessor, in an alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. A specially programmed processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0178] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted through a non-transitory computer-readable medium as one or more instructions or codes. Other examples and specific embodiments fall within the scope and spirit of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using hardware, firmware, hardwiring, software executed by a specially programmed processor, or any combination of these items. The features implementing the functions can also be physically located at different positions, including being distributed such that various parts of the functions are implemented at different physical locations. Additionally, as used herein, including in the claims, the "or" used in a list of items starting with "at least one of" indicates a disjunctive list, such that for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0179] A computer-readable medium includes both computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, a computer-readable medium may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer or a general purpose or special purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable medium.

[0180] The foregoing description of the disclosure has been provided to enable a person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. In addition, while elements of the described aspects and / or embodiments have been described or claimed in the singular, the plural forms are also contemplated unless explicitly stated to be limited to the singular. Additionally, unless otherwise stated, all or part of any aspect and / or embodiment may be used in conjunction with all or part of any other aspect and / or embodiment. Accordingly, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A device for wireless communication, the device comprising: a transceiver; one or more memories configured to store instructions, either individually or in combination; and one or more processors communicatively coupled to the one or more memories, wherein the one or more processors are configured to execute the instructions, either individually or in combination, to cause the device to: receive first downlink control information (DCI) indicating a first transmission configuration indicator (TCI) state to be applied to a first component carrier (CC) at a first beam application time (BAT); receive second DCI indicating a second TCI state to be applied to the first CC or a second CC at a second BAT; and in a case where the first BAT and the second BAT are within the same time period, apply, at least in part based on a first attribute of the first DCI and a second attribute of the second DCI, the first TCI state or the second TCI state to one or more of the first CC or the second CC within the time period.

2. The device according to claim 1, wherein the first attribute includes a first monitoring occasion associated with the first DCI, and the second attribute includes a second monitoring occasion associated with the second DCI.

3. The device according to claim 2, wherein the one or more processors are configured to execute the instructions, either individually or in combination, to cause the device to: apply the first TCI state in a case where the first monitoring occasion is later than the second monitoring occasion.

4. The device according to claim 1, wherein the first attribute includes a first component carrier (CC) identifier (ID) associated with the first DCI, and the second attribute includes a second CC ID associated with the second DCI.

5. The device according to claim 4, wherein the one or more processors are configured to execute the instructions, either individually or in combination, to cause the device to: apply the first TCI state based on the first CC ID and the second CC ID in a case where a first monitoring occasion of the first DCI is within or at least partially overlaps in time with a second monitoring occasion of the second DCI.

6. The device according to claim 5, wherein the first DCI and the second DCI do not include a downlink channel assignment.

7. The device according to claim 1, wherein the first attribute includes a first bandwidth part (BWP) identifier (ID) associated with the first DCI, and the second attribute includes a second BWP ID associated with the second DCI.

8. The device according to claim 1, wherein the first attribute includes a first acknowledgment (ACK) time associated with the first DCI, and the second attribute includes a second ACK time associated with the second DCI.

9. The apparatus according to claim 1, wherein the first attribute includes a first bandwidth part (BWP) identifier (ID) associated with the first DCI, and the second attribute includes a second BWP ID associated with the second DCI.

10. The apparatus according to claim 1, wherein the first attribute includes a first control resource set (CORESET) identifier (ID) associated with the first DCI, and the second attribute includes a second CORESET ID associated with the second DCI.

11. The apparatus according to claim 1, wherein the first attribute includes a first search space (SS) set identifier (ID) associated with the first DCI, and the second attribute includes a second SS set ID associated with the second DCI.

12. The apparatus according to claim 1, wherein the first attribute includes a set of a plurality of first monitoring occasions associated with the first DCI, and the second attribute includes at least one second monitoring occasion associated with the second DCI, wherein the one or more processors are configured to execute the instructions individually or in combination to cause the apparatus to: apply the first TCI state or the second TCI state based on one first monitoring occasion in the set of the plurality of first monitoring occasions and the at least one second monitoring occasion.

13. The apparatus according to claim 12, wherein the one first monitoring occasion in the set of the plurality of first monitoring occasions includes one of the following: the earliest first monitoring occasion in the set of the plurality of first monitoring occasions; the latest first monitoring occasion in the set of the plurality of first monitoring occasions; or the latest first monitoring occasion in the earliest repetition of the first DCI in the set of the plurality of first monitoring occasions.

14. The apparatus according to claim 1, wherein the one or more processors are configured to execute the instructions individually or in combination to cause the apparatus to: send a first acknowledgment (ACK) for the first DCI and a second ACK for the second DCI.

15. The apparatus according to claim 14, wherein the one or more processors are configured to execute the instructions individually or in combination to cause the apparatus to: further apply the first TCI state or the second TCI state based on sending the first ACK and the second ACK in the same feedback time period.

16. The apparatus according to claim 1, wherein the first attribute includes a first time of receiving the first DCI and a second time of receiving the second DCI.

17. The apparatus according to claim 1, wherein in a case where the first DCI and the second DCI are received within the same or partially overlapping DCI time, the first attribute includes a first control resource set (CORESET) identifier (ID) associated with the first DCI or a first search space (SS) set ID, and the second attribute includes a second CORESET ID or a second SS ID associated with the second DCI.

18. The apparatus according to claim 1, wherein the one or more processors are configured to execute the instructions, individually or in combination, to cause the apparatus to: apply, within the time period, the first TCI state or the second TCI state as one of an uplink TCI state, a downlink TCI state, or a unified uplink and downlink TCI state.

19. The apparatus according to claim 1, wherein the one or more processors are configured to execute the instructions, individually or in combination, to cause the apparatus to: receive a configuration that configures the first CC and the second CC in a CC list for applying a TCI state.

20. The apparatus according to claim 19, wherein the one or more processors are configured to execute the instructions, individually or in combination, to cause the apparatus to: apply the first TCI state or the second TCI state to all CCs in the CC list.

21. An apparatus for wireless communication, the apparatus comprising: a transceiver; one or more memories configured to store instructions, individually or in combination; and one or more processors communicatively coupled to the one or more memories, wherein the one or more processors are configured to execute the instructions, individually or in combination, to cause the apparatus to: transmit a first downlink control information (DCI) indicating a first transmission configuration indicator (TCI) state to be applied to a first component carrier (CC) at a first beam application time (BAT); transmit a second DCI indicating a second TCI state to be applied to the first CC or a second CC at a second BAT; and in a case where the first BAT and the second BAT are within the same time period, apply, within the time period, the first TCI state or the second TCI state to one or more of the first CC or the second CC, at least partially based on a first attribute of the first DCI and a second attribute of the second DCI.

22. The apparatus according to claim 21, wherein the first attribute includes a first monitoring occasion associated with the first DCI, and the second attribute includes a second monitoring occasion associated with the second DCI.

23. The apparatus according to claim 22, wherein the one or more processors are configured to execute the instructions, individually or in combination, to cause the apparatus to: apply the first TCI state in a case where the first monitoring occasion is later than the second monitoring occasion.

24. The apparatus according to claim 21, wherein the first attribute includes a first component carrier (CC) identifier (ID) associated with the first DCI, and the second attribute includes a second CC ID associated with the second DCI.

25. The apparatus according to claim 24, wherein the one or more processors are configured to execute the instructions, individually or in combination, to cause the apparatus to: apply the first TCI state based on the first CC ID and the second CC ID when a first monitoring occasion of the first DCI is within a second monitoring occasion of the second DCI or at least partially overlaps with the second monitoring occasion in time.

26. The apparatus according to claim 21, wherein the first attribute includes a set of a plurality of first monitoring occasions associated with the first DCI, and the second attribute includes at least one second monitoring occasion associated with the second DCI, wherein the one or more processors are configured to execute the instructions, individually or in combination, to cause the apparatus to: apply the first TCI state or the second TCI state based on one first monitoring occasion in the set of the plurality of first monitoring occasions and the at least one second monitoring occasion.

27. A method for wireless communication at a user equipment (UE), the method comprises: receiving a first downlink control information (DCI) indicating a first transmission configuration indicator (TCI) state to be applied to a first component carrier (CC) at a first beam application time (BAT); receiving a second DCI indicating a second TCI state to be applied to the first CC or a second CC at a second BAT; and when the first BAT and the second BAT are within the same time period, applying the first TCI state or the second TCI state to one or more of the first CC or the second CC during the time period based at least in part on a first attribute of the first DCI and a second attribute of the second DCI.

28. The method according to claim 27, wherein the first attribute includes a first monitoring occasion associated with the first DCI, and the second attribute includes a second monitoring occasion associated with the second DCI.

29. A method for wireless communication at a network node, the method comprises: transmitting a first downlink control information (DCI) indicating a first transmission configuration indicator (TCI) state to be applied to a first component carrier (CC) at a first beam application time (BAT); transmitting a second DCI indicating a second TCI state to be applied to the first CC or a second CC at a second BAT; and when the first BAT and the second BAT are within the same time period, applying the first TCI state or the second TCI state to one or more of the first CC or the second CC during the time period based at least in part on a first attribute of the first DCI and a second attribute of the second DCI.

30. The method according to claim 29, wherein the first attribute includes a first monitoring occasion associated with the first DCI, and the second attribute includes a second monitoring occasion associated with the second DCI.

Images