Updating transmission configuration indicator for component carrier list

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a plurality of downlink control information (DCI) communications associated with a first component carrier and a second component carrier that indicate a plurality of respective transmission configuration indicator (TCI) states, where the first component carrier and the second component carrier are included in a same component carrier list. The UE may transmit a plurality of acknowledgement (ACK) messages via a plurality of respective physical uplink control channel (PUCCH) transmissions included in a single PUCCH or included in an overlapping PUCCH. The UE may apply a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state of the plurality of TCI states and according to one or more rules. Numerous other aspects are described.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 377,269, filed on September 27, 2022, entitled “UPDATING ATRANSMISSION CONFIGURATION INDICATOR FOR A COMPONENT CARRIER LIST,” and U.S. Non-Provisional Patent Application No. 18 / 352,067, filed on July 13, 2023, entitled “UPDATING A TRANSMISSION CONFIGURATION INDICATOR FOR A COMPONENT CARRIER LIST,” which are hereby expressly incorporated herein by reference. Technical Field

[0002] Aspects of the disclosure relate generally to wireless communications and to techniques and apparatus for updating a transmission configuration indicator of a component carrier list. Background Art

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies 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, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard released by the Third Generation Partnership Project (3GPP).

[0004] A wireless network may include one or more network nodes that support communication of wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communication and uplink communication. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0005] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and / or global level. New Radio (NR), which may also be referred to as 5G, is an enhancement set to the LTE mobile standard released by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (e.g., also referred to as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, thereby better supporting mobile broadband Internet access. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR and other radio access technologies remain beneficial. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are shown in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not considered to limit the scope of the present disclosure, as the specification may allow for other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0007] Figure 1 is a schematic diagram illustrating an example of a wireless network according to the present disclosure.

[0008] Figure 2 is a schematic diagram showing an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0009] Figure 3 is a schematic diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0010] Figure 4 is a schematic diagram showing an example of physical channels and reference signals in a wireless network according to the present disclosure.

[0011] Figure 5 is a schematic diagram showing an example of using beams for communication between a network node and a UE according to the present disclosure.

[0012] Figure 6 is a schematic diagram showing an example of carrier aggregation according to the present disclosure.

[0013] Figure 7 is a diagram showing an example of updating a transmission configuration indicator (TCI) using overlapping downlink control information according to the present disclosure.

[0014] Figure 8 is a schematic diagram showing an example of updating TCI for a component carrier list according to the present disclosure.

[0015] Fig. 9 is a schematic diagram showing a first example of TCI selection for TCI update according to the present disclosure.

[0016] Fig.10 is a schematic diagram showing a second example of TCI selection for TCI update according to the present disclosure.

[0017] Fig.11 is a schematic diagram showing a third example of TCI selection for TCI update according to the present disclosure.

[0018] Fig.12 is a schematic diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0019] Fig.13 is a schematic diagram illustrating an example process performed, for example, by a network node according to the present disclosure.

[0020] Fig.14 is a schematic diagram illustrating an example apparatus for wireless communication according to the present disclosure.

[0021] Fig.15 is a schematic diagram illustrating an example apparatus for wireless communication according to the present disclosure. Summary of the invention

[0022] Some aspects described herein relate to a method of performing wireless communications by a user equipment (UE). The method may include receiving a plurality of downlink control information (DCI) communications associated with a first component carrier and a second component carrier, the plurality of DCI communications indicating a plurality of corresponding transmission configuration indicator (TCI) states, wherein each of the first component carrier and the second component carrier is associated with at least one of the plurality of DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list. The method may include sending a plurality of acknowledgement (ACK) messages via a plurality of corresponding physical uplink control channel (PUCCH) transmissions, wherein the plurality of PUCCH transmissions are included in a single PUCCH or are included in overlapping PUCCHs. The method may include applying a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the plurality of TCI states and according to one or more rules.

[0023] Some aspects described herein relate to a method for performing wireless communications by a network node. The method may include sending multiple DCI communications associated with a first component carrier and a second component carrier, the multiple DCI communications indicating multiple corresponding TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication in the multiple DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list. The method may include receiving multiple ACK messages via multiple corresponding PUCCH transmissions, wherein the multiple PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs. The method may include applying a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the multiple TCI states and according to one or more rules.

[0024] Some aspects described herein relate to an apparatus for performing wireless communications by a UE. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive multiple DCI communications associated with a first component carrier and a second component carrier, the multiple DCI communications indicating multiple corresponding TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication in the multiple DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list. The one or more processors may be configured to send multiple ACK messages via multiple corresponding PUCCH transmissions, wherein the multiple PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs. The one or more processors may be configured to apply a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the multiple TCI states and according to one or more rules.

[0025] Some aspects described herein relate to an apparatus for performing wireless communications by a network node. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send multiple DCI communications associated with a first component carrier and a second component carrier, the multiple DCI communications indicating multiple corresponding TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication in the multiple DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list. The one or more processors may be configured to receive multiple ACK messages via multiple corresponding PUCCH transmissions, wherein the multiple PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs. The one or more processors may be configured to apply a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the multiple TCI states and according to one or more rules.

[0026] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication of a UE. When executed by one or more processors of the UE, the instruction set may enable the UE to receive multiple DCI communications associated with a first component carrier and a second component carrier, the multiple DCI communications indicating multiple corresponding TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication in the multiple DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list. When executed by one or more processors of the UE, the instruction set may enable the UE to send multiple ACK messages via multiple corresponding PUCCH transmissions, wherein the multiple PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs. When executed by one or more processors of the UE, the instruction set may enable the UE to apply a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the multiple TCI states and according to one or more rules.

[0027] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions may cause the network node to send multiple DCI communications associated with a first component carrier and a second component carrier, the multiple DCI communications indicating multiple corresponding TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication in the multiple DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list. When executed by one or more processors of the network node, the set of instructions may cause the network node to receive multiple ACK messages via multiple corresponding PUCCH transmissions, wherein the multiple PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs. When executed by one or more processors of the network node, the set of instructions may cause the network node to apply a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the multiple TCI states and according to one or more rules.

[0028] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a unit for receiving multiple DCI communications associated with a first component carrier and a second component carrier, the multiple DCI communications indicating multiple corresponding TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication in the multiple DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list. The apparatus may include a unit for sending multiple ACK messages via multiple corresponding PUCCH transmissions, wherein the multiple PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs. The apparatus may include: a unit for applying a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the multiple TCI states and according to one or more rules.

[0029] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a unit for sending multiple DCI communications associated with a first component carrier and a second component carrier, the multiple DCI communications indicating multiple corresponding TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication in the multiple DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list. The apparatus may include: a unit for receiving multiple ACK messages via multiple corresponding PUCCH transmissions, wherein the multiple PUCCH transmissions are included in a single PUCCH or included in overlapping PUCCHs. The apparatus may include: a unit for applying a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the multiple TCI states and according to one or more rules.

[0030] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated by the accompanying drawings.

[0031] The foregoing has been fairly broadly summarized according to the features and technical advantages of the examples of the present disclosure, so that the following detailed description can be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples can be easily used as the basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood according to the description below. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and is not intended to be a definition of the limitations of the claims.

[0032] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that these aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip embodiments or other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase equipment, medical equipment, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The device incorporating the described aspects and features can also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals can include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). It is intended that the aspects described herein can be practiced in a variety of devices, components, systems, distributed arrangements, and / or end-user devices of varying sizes, shapes, and structures. DETAILED DESCRIPTION

[0033] The following is a more complete description of various aspects of the present disclosure with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. More specifically, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether the aspect is implemented independently of any other aspect of the present disclosure or implemented in combination with any other aspect. For example, using any number of aspects set forth herein, a device can be implemented or a method can be implemented. In addition, the scope of the present disclosure is intended to cover such a device or method implemented using other structures, functions, or structures and functions other than the various aspects of the present disclosure set forth herein or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein can be embodied by one or more elements of the claims.

[0034] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the detailed description below by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements") and illustrated in the accompanying drawings. These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0035] Although various aspects may be described using terminology generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0036] Figure 11 is a schematic diagram showing an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be an aggregated network node, which means that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes, such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs).

[0037] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link (such as, RU). In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or via a midhaul link, such as a DU. In some examples, the network node 110 may be or include a network node that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregation network node 110 or a decomposition network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobile element of a network, a core network node, a network element, a network device, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 using any suitable transport network, through various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks.

[0038] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​the network node 110 and / or a network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several thousand meters) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 with an association with a femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. Figure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move according to the location of a mobile network node 110 (e.g., a mobile network node).

[0039] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with the network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform the one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to replicate the execution of at least a portion of a function, and the term "base station" or "network node" may refer to any one or more of those different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0040] The wireless network 100 may include one or more relay stations. A relay station is a network node that receives transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and sends transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions intended for other UEs 120. Figure 1 In the example shown, a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, or the like.

[0041] The wireless network 100 may be a heterogeneous network including different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, macro network nodes may have higher transmit power levels (e.g., 5 to 40 Watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 to 2 Watts).

[0042] The network controller 130 may be coupled to or communicate with a group of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a mid-range communication link. The network nodes 110 may communicate with each other directly or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

[0043] UE 120 can be dispersed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing device, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0044] Some UE 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UE. MTC UE and / or eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor and / or a location tag, which may communicate with a network node, another device (e.g., a remote device) or some other entity. Some UE 120 may be considered as an Internet of Things (IoT) device, and / or may be implemented as a NB-IoT (narrowband IoT) device. Some UE 120 may be considered as a user premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0045] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, an air interface, etc. A frequency may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0046] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary for communicating with each other). For example, UE 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocol (e.g., which may include vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, or vehicle-to-pedestrian (V2P) protocol), and / or mesh network. In such examples, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0047] The devices of the wireless network 100 can communicate using an electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc. by frequency or wavelength. For example, the devices of the wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is often referred to (interchangeably) as the "Sub-6 GHz" band in various documents and articles. Sometimes similar naming issues occur with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and articles, but it is different from the extremely high frequency (EHF) band (30GHz-300GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0048] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands of these mid-band frequencies as the frequency range name FR3 (7.125GHz-24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus the characteristics of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations above 52.6GHz. For example, three higher operating frequency bands have been identified as the frequency range names FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0049] With the above examples in mind, unless otherwise specifically stated, it should be understood that the term "sub-6 GHz" or similar terms (if used herein) can broadly refer to frequencies that can be below 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that the terms "millimeter wave" and the like (if used herein) can broadly refer to frequencies that can include mid-band frequencies, frequencies that can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or frequencies that can be within the EHF band. It is expected that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0050] In some aspects, the UE 120 may include a communications manager 140. As described in more detail elsewhere herein, the communications manager 140 may receive a plurality of downlink control information (DCI) communications associated with a first component carrier and a second component carrier, indicating a plurality of respective transmission configuration indicator (TCI) states, wherein each of the first component carrier and the second component carrier is associated with at least one of the plurality of DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list; send a plurality of acknowledgement (ACK) messages via a plurality of respective PUCCH transmissions, wherein the plurality of PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs; and, based at least in part on a TCI state in the plurality of TCI states and in accordance with one or more rules, apply a TCI update to at least one of the first component carrier or the second component carrier. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0051] In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a plurality of DCI communications associated with a first component carrier and a second component carrier, indicating a plurality of respective TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one of the plurality of DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list; receive a plurality of ACK messages via a plurality of respective PUCCH transmissions, wherein the plurality of PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs; and, based at least in part on a TCI state in the plurality of TCI states and in accordance with one or more rules, apply a TCI update to at least one of the first component carrier or the second component carrier. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0052] As indicated above, Figure 1 is provided as an example. Other examples may differ from those described above. Figure 1 Examples described.

[0053] Figure 22 is a schematic diagram showing an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs, or one or more DUs.

[0054] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a group of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a to 232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a respective output symbol stream (e.g., for OFDM) using a respective modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a respective modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0055] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may further process the input samples (e.g., for OFDM) using a demodulator component to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols (if applicable), and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0056] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0057] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0058] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 (if applicable), further processed by a modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modulator 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (eg, with reference to Figure 8-Figure 15 ).

[0059] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by an antenna 234, processed by a modem 232 (e.g., a demodulator component of the modem 232, shown as DEMOD), detected by a MIMO detector 236 (if applicable), and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of an antenna 234, a modem 232, a MIMO detector 236, a receive processor 238, a transmit processor 220, and / or a TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and a memory 242 to perform aspects of any of the methods described herein (e.g., with reference to Figure 8-Figure 15 ).

[0060] As described in greater detail elsewhere herein, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or any other component of FIG. 2 may perform one or more techniques associated with updating the TCI for the component carrier list. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in may perform or direct e.g. Fig.12 The process 1200 Fig.13 1300, and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause one or more processors, UE 120, and / or network node 110 to perform or instruct, for example Fig.12 The process 1200 Fig.13 The process 1300 and / or operations of other processes as described herein. In some examples, executing instructions may include: running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0061] In some aspects, a UE (e.g., UE 120) includes means for receiving a plurality of DCI communications associated with a first component carrier and a second component carrier, the plurality of DCI communications indicating a plurality of respective TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one of the plurality of DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list; means for sending a plurality of ACK messages via a plurality of respective PUCCH transmissions, wherein the plurality of PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs; and / or means for applying a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the plurality of TCI states and in accordance with one or more rules. Means for UE 120 to perform operations described herein may include, for example, one or more of the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0062] In some aspects, a network node (e.g., network node 110) includes a unit for sending multiple DCI communications associated with a first component carrier and a second component carrier, the multiple DCI communications indicating multiple corresponding TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication of the multiple DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list; a unit for receiving multiple ACK messages via multiple corresponding PUCCH transmissions, wherein the multiple PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs; and / or a unit for applying a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the multiple TCI states and according to one or more rules. The means for the network node 110 to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0063] Although Figure 2 The blocks in the 200 and 210 are shown as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functionality described with reference to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by, or under the control of, the controller / processor 280.

[0064] As noted above, Figure 2 is provided as an example. Other examples may differ from those described above. Figure 2 Examples described.

[0065] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways and have various components or parts. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or a network device can be implemented in an aggregated or decomposed architecture. For example, a base station (e.g., a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.), or one or more units (or one or more components) performing base station functions can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station. A "network entity" or a "network node" may refer to a decomposed base station, or to one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0066] An aggregated base station (e.g., an aggregated network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) can be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as, one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU can be implemented within a network 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 network nodes. The 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, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and so on.

[0067] The operation or network design of the base station type can take into account the aggregated nature of the base station functions. For example, a decomposed base station can be used in an IAB network, an open radio access network (O-RAN (such as a network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of the communication system by separating the base station functions into one or more units that can be deployed separately. The decomposed base station can include functions implemented on two or more units at different physical locations, as well as functions implemented virtually for at least one unit, which can achieve flexibility in network design. The various units of the decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0068] Figure 33 is a schematic diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as, a near RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective mid-haul links (such as, via an F1 interface). Each of the DUs 330 may communicate with one or more RUs 340 via respective front-end links. Each RU 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some embodiments, a UE 120 may be served simultaneously by multiple RUs 340.

[0069] Each unit, including CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305, may include one or more interfaces, or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each unit, or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more other units via a transmission medium. In some examples, each unit may include a wired interface and a wireless interface, the wired interface being configured to receive or send signals to one or more other units via a wired transmission medium, and the wireless interface may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) that is configured to receive signals or send signals or both to one or more other units via a wireless transmission medium.

[0070] In some aspects, CU 310 may accommodate one or more higher-layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, and the like. Each control function may be implemented with an interface configured to communicate signals with other control functions accommodated by CU 310. CU 310 may be configured to process user plane functions (e.g., central unit-user plane (CU-UP) functions), control plane functions (e.g., central unit-control plane (CU-CP) functions), or a combination thereof. In some embodiments, CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. CU 310 may be implemented to communicate with DU 330 as needed for network control and signaling.

[0071] Each DU 330 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, depending at least in part on the functional division (such as the functional division defined by 3GPP), the DU 330 may accommodate one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers. In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also accommodate one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, etc. Each layer (also referred to as a module) may be implemented with an interface configured to communicate signals with other layers (and modules) accommodated by the DU 330, or with the control functions accommodated by the CU 310.

[0072] Each RU 340 may implement lower layer functions. In some deployments, based on functional division (e.g., functional division defined by 3GPP) (such as, lower layer functional division), the RU 340 controlled by the DU 330 may correspond to a logical node that houses RF processing functions or low PHY layer functions, such as: performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In such an architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some embodiments, real-time and non-real-time aspects of control and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as, a vRAN architecture).

[0073] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some embodiments, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via an O1 interface. Furthermore, in some embodiments, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0074] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (e.g., via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources through data collection and actions on interfaces connecting one or more CUs 310, one or more DUs 330, or both, and O-eNBs with the near-RT RIC 325 (e.g., via an E2 interface).

[0075] In some embodiments, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be used by the near-RT RIC 325 and may be received at the SMO framework 305 or the non-RT RIC 315 from a non-network data source or from a network function. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and use the AI / ML model to perform corrective actions through the SMO framework 305 (such as, via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as, A1 interface policies).

[0076] As mentioned above, Figure 3 is provided as an example. Other examples may differ from those described above. Figure 3 Examples described.

[0077] Figure 4 4 is a schematic diagram illustrating an example 400 of physical channels and reference signals in a wireless network according to the present disclosure. Figure 4 As shown in , the downlink channel and the downlink reference signal may carry information from the network node 110 to the UE 120 , while the uplink channel and the uplink reference signal may carry information from the UE 120 to the network node 110 .

[0078] As shown, downlink channels may include: a physical downlink control channel (PDCCH) carrying DCI, a physical downlink shared channel (PDSCH) carrying downlink data, or a physical broadcast channel (PBCH) carrying system information, etc. In some aspects, PDSCH communications may be scheduled by PDCCH communications. As further shown, uplink channels may include: a PUCCH carrying uplink control information (UCI), a physical uplink shared channel (PUSCH) carrying uplink data, or a physical random access channel (PRACH) for initial network access, etc. In some aspects, UE 120 may send ACK or negative acknowledgement (NACK) feedback (e.g., ACK / NACK feedback, or ACK / NACK information) in the UCI on the PUCCH and / or PUSCH.

[0079] As further shown, the downlink reference signal may include a synchronization signal block (SSB), a channel state information (CSI) reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS) or a phase tracking reference signal (PTRS), etc. Also as shown, the uplink reference signal may include a sounding reference signal (SRS), a DMRS or a PTRS, etc.

[0080] The SSB may carry information used for initial network acquisition and synchronization, such as a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH, and a PBCH DMRS. The SSB is sometimes referred to as a synchronization signal / PBCH (SS / PBCH) block. In some aspects, the network node 110 may send multiple SSBs on multiple corresponding beams, and these SSBs may be used for beam selection.

[0081] The CSI-RS may carry information for downlink channel estimation (e.g., downlink CSI acquisition), which may be used for scheduling, link adaptation, or beam management, etc. The network node 110 may configure a CSI-RS set for the UE 120, and the UE 120 may measure the configured CSI-RS set. Based at least in part on the measurements, the UE 120 may perform channel estimation and may report channel estimation parameters (e.g., in a CSI report) such as a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a layer indicator (LI), a rank indicator (RI), or a reference signal received power (RSRP), etc. to the network node 110. The network node 110 can use the CSI report to select transmission parameters for downlink communication to the UE 120, such as the number of transmission layers (e.g., rank), precoding matrix (e.g., precoder), modulation and coding scheme (MCS), or refined downlink beams (e.g., using a beam refinement process or a beam management process), etc.

[0082] DMRS can carry information used to estimate the wireless channel to demodulate the associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of DMRS can be specific to the physical channel for which DMRS is used for estimation. DMRS is UE-specific, can be beamformed, can be restricted to scheduled resources (e.g., instead of being sent over a wideband), and is sent only when necessary. As shown, DMRS is used for both downlink and uplink communications.

[0083] PTRS can carry information for compensating for oscillator phase noise. Typically, phase noise increases as the oscillator carrier frequency increases. Therefore, PTRS can be used at high carrier frequencies (such as millimeter wave frequencies) to mitigate phase noise. PTRS can be used to track the phase of the local oscillator and achieve suppression of phase noise and common phase error (CPE). As shown, PTRS is used for both downlink communications (e.g., on PDSCH) and uplink communications (e.g., on PUSCH).

[0084] The PRS may carry information for implementing timing or ranging measurements of the UE 120 based on signals sent by the network node 110 to improve observed time difference of arrival (OTDOA) positioning performance. For example, the PRS may be a pseudo-random quadrature phase shift keying (QPSK) sequence mapped in a diagonal pattern with offsets in frequency and time to avoid conflicts with cell-specific reference signals and control channels (e.g., PDCCH). In general, the PRS may be designed to improve the detectability of the UE 120, which may need to detect downlink signals from multiple neighboring network nodes in order to perform OTDOA-based positioning. Therefore, the UE 120 may receive PRS from multiple cells (e.g., a reference cell and one or more neighboring cells), and may report a reference signal time difference (RSTD) based on OTDOA measurements associated with the PRS received from the multiple cells. In some aspects, the network node 110 may then calculate the position of the UE 120 based on the RSTD measurements reported by the UE 120.

[0085] The SRS may carry information for uplink channel estimation, which may be used for scheduling, link adaptation, precoder selection, or beam management, etc. The network node 110 may configure one or more SRS resource sets for the UE 120, and the UE 120 may send the SRS on the configured SRS resource sets. The SRS resource sets may have configured purposes, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, etc. The network node 110 may measure the SRS, may perform channel estimation based at least in part on the measurements, and may use the SRS measurements to configure communications with the UE 120.

[0086] As mentioned above, Figure 4 is provided as an example. Other examples may differ with respect to Figure 4 Examples described.

[0087] Figure 5 5 is a schematic diagram illustrating an example 500 of using beams for communication between a network node and a UE according to the present disclosure. Figure 5 As shown in FIG. 1 , the network node 110 and the UE 120 may communicate with each other.

[0088] The network node 110 may transmit to a UE 120 located within the coverage area of ​​the network node 110. The network node 110 and the UE 120 may be configured for beamforming communication, wherein the network node 110 may transmit in the direction of the UE 120 using a directional network node (NN) transmit beam (e.g., a BS transmit beam), and the UE 120 may receive the transmission using a directional UE receive beam. Each NN transmit beam may have an associated beam ID, beam direction, or beam symbol, etc. The network node 110 may transmit downlink communications via one or more NN transmit beams 505.

[0089] UE 120 may attempt to receive a downlink transmission via one or more UE receive beams 510, which may be configured using different beamforming parameters at a receive circuit of UE 120. UE 120 may identify a particular NN transmit beam 505 (shown as NN transmit beam 505-A) and a particular UE receive beam 510 (shown as UE receive beam 510-A) that provide relatively advantageous performance (e.g., best channel quality with different measured combinations of NN transmit beams 505 and UE receive beams 510). In some examples, UE 120 may send an indication of which NN transmit beam 505 is identified by UE 120 as a preferred NN transmit beam, and network node 110 may select the preferred NN transmit beam for transmission to UE 120. Thus, UE 120 can obtain and maintain a beam pair link (BPL) for downlink communication with network node 110 (e.g., a combination of NN transmit beam 505-A and UE receive beam 510-A), which can be further refined and maintained according to one or more established beam refinement processes.

[0090] A downlink beam, such as a NN transmit beam 505 or a UE receive beam 510, may be associated with a transmission configuration indication (TCI) state. The TCI state may indicate a directionality or characteristic of the downlink beam, such as one or more quasi-co-location (QCL) attributes of the downlink beam. The QCL attributes may include, for example, Doppler shift, Doppler spread, average delay, delay spread, or spatial reception parameters, etc. In some examples, each NN transmit beam 505 may be associated with a synchronization signal block (SSB), and the UE 120 may indicate a preferred NN transmit beam 405 by sending an uplink transmission in the resources of the SSB associated with the preferred NN transmit beam 505. A particular SSB may have an associated TCI state (e.g., for an antenna port or for beamforming). In some examples, the network node 110 may indicate a downlink NN transmit beam 505 based at least in part on an antenna port QCL attribute that may be indicated by a TCI state. The TCI state may be associated with a downlink reference signal set (e.g., SSB and aperiodic, periodic, or semi-persistent channel state information reference signal (CSI-RS)) for different QCL types (e.g., QCL types for different combinations of Doppler shift, Doppler spread, average delay, delay spread, or spatial reception parameters, etc.). In the case where the QCL type indicates spatial reception parameters, the QCL type may correspond to simulated receive beamforming parameters of the UE receive beam 510 at the UE 120. Thus, the UE 120 may select a corresponding UE receive beam 510 from the BPL set based at least in part on the network node 110 indicating the NN transmit beam 505 via the TCI indication.

[0091] The network node 110 may maintain an activated TCI state set for downlink shared channel transmission and an activated TCI state set for downlink control channel transmission. The activated TCI state set for downlink shared channel transmission may correspond to a beam that the network node 110 uses for downlink transmission on a physical downlink shared channel (PDSCH). The activated TCI state set for downlink control channel communication may correspond to a beam that the network node 110 may use for downlink transmission on a physical downlink control channel (PDCCH) or in a control resource set (CORESET). The UE 120 may also maintain an activated TCI state set for receiving downlink shared channel transmissions and CORESET transmissions. If a TCI state is activated for the UE 120, the UE 120 may have one or more antenna configurations based at least in part on the TCI state, and the UE 120 may not need to reconfigure antennas or antenna weighting configurations. In some examples, an activated TCI state set (e.g., an activated PDSCH TCI state and an activated CORESET TCI state) for UE 120 may be configured via a configuration message, such as a radio resource control (RRC) message.

[0092] Similarly, for uplink communications, UE 120 may transmit in the direction of network node 110 using a directional UE transmit beam, and network node 110 may receive transmissions using a directional NN receive beam. Each UE transmit beam may have an associated beam ID, beam direction, or beam symbol, etc. UE 120 may transmit uplink communications via one or more UE transmit beams 515.

[0093] The network node 110 may receive uplink transmissions via one or more NN receive beams 520 (e.g., BS receive beams). The network node 110 may identify a specific UE transmit beam 515 (shown as UE transmit beam 515-A) and a specific NN receive beam 520 (shown as NN receive beam 520-A) that provide relatively advantageous performance (e.g., best channel quality with different measured combinations of UE transmit beams 515 and NN receive beams 520). In some examples, the network node 110 may send an indication of which UE transmit beam 515 is identified by the network node 110 as a preferred UE transmit beam, which the network node 110 may select for transmissions from the UE 120. Thus, the UE 120 and the network node 110 may obtain and maintain a BPL for uplink communications (e.g., a combination of the UE transmit beam 515-A and the NN receive beam 520-A), which may be further refined and maintained according to one or more established beam refinement processes. An uplink beam, such as a UE transmit beam 515 or a NN receive beam 520, may be associated with a spatial relationship. The spatial relationship may indicate a directionality or characteristic of the uplink beam, similar to one or more QCL properties as described above.

[0094] As noted above, Figure 5 is provided as an example. Other examples may differ from those described above. Figure 5 Examples described.

[0095] Figure 6 is a diagram illustrating an example 600 of carrier aggregation according to the present disclosure.

[0096] Carrier aggregation is a technique that enables two or more component carriers (CCs, sometimes referred to as carriers) to be combined (e.g., into a single channel) for enhanced data capacity for a single UE 120. As shown, the carriers may be combined in the same or different frequency bands. Additionally or alternatively, contiguous or non-contiguous carriers may be combined. The network node 110 may configure carrier aggregation for the UE 120, such as in a radio resource control (RRC) message, a DCI, and / or another signaling message.

[0097] As indicated by reference numeral 605, in some aspects, carrier aggregation may be configured in an intra-band contiguous mode, wherein the aggregated carriers are contiguous with each other and are located in the same frequency band. As indicated by reference numeral 610, in some aspects, carrier aggregation may be configured in an intra-band non-contiguous mode, wherein the aggregated carriers are non-contiguous with each other and are located in the same frequency band. As indicated by reference numeral 615, in some aspects, carrier aggregation may be configured as an inter-band non-contiguous mode, wherein the aggregated carriers are non-contiguous with each other and are located in different frequency bands.

[0098] In carrier aggregation, a UE 120 may be configured with a primary carrier or primary cell (PCell) and one or more secondary carriers or secondary cells (SCells). In some aspects, the primary carrier may carry control information (e.g., downlink control information and / or scheduling information) for scheduling data communications on one or more secondary carriers, which may be referred to as cross-carrier scheduling. In some aspects, a carrier (e.g., a primary carrier or a secondary carrier) may carry control information for scheduling data communications on the carrier, which may be referred to as self-carrier scheduling or carrier self-scheduling.

[0099] As mentioned above, Figure 6 are provided as examples. Other examples may be related to Figure 6 The examples described are different.

[0100] Figure 7 is a diagram illustrating an example 700 of updating TCI using overlapping DCI according to the present disclosure.

[0101] In some cases, the DCI may indicate one or more beams to be used by the UE 120 and / or the network node 110. This may be referred to as a DCI-based beam indication. For a DCI-based beam indication, a TCI state (such as an updated TCI state) may be applied in the first time slot of at least X milliseconds or at least Y symbols after the last symbol of the ACK message corresponding to the beam indication, wherein the beam indication is a downlink beam indication, an uplink beam indication, or a joint (downlink and uplink) beam indication. For example, when the DCI has no downlink allocation, the ACK may be a dedicated ACK. Alternatively, the ACK may be an ACK for scheduling the PDSCH. The timing information (e.g., X milliseconds or Y symbols) may be configured according to capability information associated with the UE 120. In some cases, when a common TCI state is applied between multiple component carriers, X ms or Y symbols may be determined at least in part based on a component carrier with a minimum subcarrier spacing (SCS). In some other cases, the beam indication may be a beam indication based on a MAC control element (MAC-CE). For MAC-CE based beam indication, the indicated TCI may be activated 3ms after the ACK corresponding to the MAC-CE. In some cases, the TCI state may be applied to one or more channels or reference signals (eg, once activated), as shown in Table 1. Table 1

[0102] In some cases, DCI (such as DCI format 1_1 or 1_2) can be used to indicate the TCI state without scheduling any downlink allocation. For example, when the cyclic redundancy check (CRC) of the DCI is scrambled by the configured scheduling radio network temporary identifier (CS-RNTI), when the redundancy version (RV) field is set to all 1s, when the MCS field is set to all 1s, when the new data indicator (NDI) field is set to zero, and when the frequency domain resource allocation (FDRA) field is set to all zeros for FDRA type 0, all 1s for FDRA type 1, or all zeros for dynamic switching, the DCI can be used to indicate the TCI state without scheduling any downlink allocation. In some cases, the TCI field can be used to indicate a TCI state identifier (ID). In some cases, the PDSCH to hybrid automatic repeat request (HARQ) feedback timing indicator field can be used to indicate the time offset from the DCI to the corresponding ACK in the PUCCH. In some cases, such as for type 1 HARQ-ACK codebook, the time domain resource allocation (TDRA) field may be used to derive the virtual PDSCH position, which may be further used to determine the position of the ACK in the HARQ-ACK codebook.

[0103] In some cases, the UE 120 may be configured with one or more component carrier lists, each of which indicates multiple component carriers. Component carriers on the same component carrier list may share the same TCI indication (e.g., TCI update) from DCI or MAC-CE. In some cases, a component carrier may be included in only one component carrier list at a time. In one example, a first component carrier (CC0) and a second component carrier (CC1) may be configured on the same component carrier list. If the UE 120 receives a TCI update using a MAC-CE for CC0, the update may be applied to both CC0 and CC1. Alternatively, if the UE 120 receives a DCI indicating a TCI update for CC0, the same TCI may be applied to both CC0 and CC1 for the TCI update. For example, a DCI update may be applied across multiple component carriers in a first time slot, which is Y symbols counted from the last symbol of the ACK corresponding to the DCI. In some cases, when the component carriers have different SCSs, the component carrier with the smallest SCS (e.g., the maximum symbol length) may be used to determine the timeline of the DCI update.

[0104] As shown in example 700, UE 120 may receive multiple DCI communications associated with CC0 705 and CC1 710, such as DCI1 715, DCI2 720, DCI3 725, DCI4 730, and DCI5 735. Each DCI communication may indicate a TCI state. For example, DCI1 715 may indicate that TCI1 is applied, DCI2 720 may indicate that TCP2 is applied, DCI3 725 may indicate that TCI3 is applied, DCI4 730 may indicate that TCP4 is applied, and DCI5 735 may indicate that TCI5 is applied. At a first time, UE 120 may receive DCI1 715 and DCI5 735 associated with CC0 705, and may receive DCI2 720 associated with CC1 710. Therefore, DCI2 720, DCI1 715, and DCI5 735 may overlap during the first time. At the second time, UE 120 may receive DCI3 725 associated with CC0 705 and may receive DCI4 730 associated with CC1 710. Thus, DCI4 730 and DCI3 725 may overlap during the second time. UE 120 may send ACK messages corresponding to one or more of the received DCI communications. For example, UE 120 may send ACK1, ACK2, ACK3, ACK4, and ACK5 (shown as ACK1, 2, 3, 4, 5) corresponding to DCI1, DCI2, DCI3, DCI4, and DCI5, respectively.

[0105] In some cases, ACK messages based at least in part on (e.g., sent in response to) DCI communications associated with multiple component carriers may be included in the same PUCCH resource, such as PUCCH source 740. When these component carriers are not included in the component carrier list, the UE 120 and / or network node 110 may use the DCI received last in time to determine the TCI update. When multiple DCIs are received in the same symbol(s) of a component carrier, the UE 120 and / or network node 110 may use the CORESET ID or search space ID (which is used to receive the DCI) to determine the TCI update. In the above example, DCI3 725 and DCI4 730 may be the last received DCI communications associated with the component carriers and may overlap in time. Therefore, the UE 120 and / or network node 110 may determine the TCI update for CC0 and CC1 based at least in part on the CORESET ID or search space ID of DCI3 725 and DCI4 730. For example, if DCI3 725 has a smaller CORESET ID than DCI4 730, TCI3 may be used for TCI update. Alternatively, if DCI3 725 and DCI4 730 have the same CORESET ID, but DCI4 730 has a smaller search space ID than DCI3 725, TCI4 may be used for TCI update. However, when component carriers are included in the same component carrier list, the above-mentioned existing rules may not apply. For example, when a PUCCH or PDCCH associated with a component carrier has duplication, the existing rules may not apply, and / or when the last received DCI communication is associated with a component carrier with a different SCS, the existing rules may not apply. Therefore, the UE 120 and the network node 110 may not be able to determine which TCI is to be used for the component carriers included in the same component carrier list.

[0106] Techniques and apparatus for updating TCI for a component carrier list are described herein. In some aspects, a network node may send and a UE may receive multiple DCI communications associated with a first component carrier and a second component carrier, the multiple DCI communications indicating multiple corresponding TCI states, wherein each of the first component carrier and the second component carrier is associated with at least two DCI communications in the multiple DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list. The UE may send and the network node may receive multiple ACK messages via multiple corresponding PUCCH transmissions, wherein the multiple PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs. The UE and / or the network node may apply a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the multiple TCI states and according to one or more rules. In some aspects, the multiple DCI communications may include selected multiple DCIs associated with multiple corresponding ACK messages sent via the last PUCCH transmission in the multiple PUCCH transmissions. In this case, the TCI state may correspond to the TCI state associated with the last DCI communication in the selected multiple DCI communications. In some other aspects, the multiple DCI communications may include a first DCI communication and a second DCI communication that overlap in time and are associated with multiple corresponding ACK messages transmitted via a last PUCCH of the multiple PUCCH transmissions. In this case, the TCI state may be based at least in part on a component carrier identifier indicated by the first DCI communication or the second DCI communication.

[0107] As described above, an ACK message based at least in part on a DCI communication and associated with multiple component carriers may be included in the same PUCCH resource. When a component carrier is not included in a component carrier list, the UE or network node may use the DCI received last in time to determine a TCI update. When multiple DCIs are received in the same symbol of a component carrier, the UE or network node may use a CORESET ID or a search space ID to determine a TCI update. However, when component carriers are included in the same component carrier list, existing rules may not apply. Therefore, the UE and the network node may not be able to determine which TCI will be used for component carriers included in the same component carrier list. Using the techniques and devices described herein, the UE and the network node may determine a TCI update to be applied to multiple component carriers included in a component carrier list. The TCI update may be based at least in part on a selected DCI communication and one or more rules in a plurality of DCI communications, wherein each DCI communication indicates an application-specific TCI. Other details are described herein.

[0108] As noted above, Figure 7 is provided as an example. Other examples may differ from those described above. Figure 7 Examples described.

[0109] Figure 8 FIG. 8 is a diagram of an example of updating TCI for a component carrier list according to the present disclosure. UE 120 may communicate with network node 110 .

[0110] As indicated by reference numeral 805, the network node 110 may send and the UE 120 may receive a plurality of DCI communications associated with a first component carrier and a second component carrier, the plurality of DCI communications indicating a plurality of respective TCI states. At least one DCI communication of the plurality of DCI communications is associated with the first component carrier, and at least another DCI communication of the plurality of DCI communications is associated with the second component carrier. The first component carrier and the second component carrier may be included in the same component carrier list. Although example 800 shows the first component carrier and the second component carrier included in the component carrier list, any number of component carriers may be included in the component carrier list.

[0111] In one example, the network node 110 may send and the UE 120 may receive multiple DCI communications, the multiple DCI communications including a first DCI (DCI1), a second DCI (DCI2), a third DCI (DCI3), a fourth DCI (DCI4), and a fifth DCI (DCI5). A portion of the DCI communication may be associated with a first component carrier, and another portion of the DCI communication may be associated with a second component carrier. For example, the first DCI, the third DCI, and the fifth DCI may be associated with the first component carrier, and the second DCI and the fourth DCI may be associated with the second component carrier. In some aspects, some DCI communications may be received at different times. For example, DCI1 and DCI2 may be received during a first time period, and DCI3 and DCI4 may be received during a second time period. In some aspects, one or more of the DCI communications may be received in multiple time periods. For example, a first repetition of DCI5 may be received during a first time period, and a second repetition of DCI5 may be received during a second time period. In some aspects, each DCI communication may be associated with a corresponding TCI state. For example, a first DCI may indicate that a first TCI state (TCI1) is applied, a second DCI may indicate that a second TCI state (TCI2) is applied, a third DCI may indicate that a third TCI state (TCI3) is applied, a fourth DCI may indicate that a fourth TCI state (TCI4) is applied, and a fifth DCI may indicate that a fifth TCI state (TCI5) is applied. The TCI indicated in the DCI may be a unified TCI. In some aspects, at least a portion of the DCI communication may indicate a CORESET identifier and / or a search space (SS) identifier. For example, a first DCI may indicate CORESET0, and a third DCI may indicate CORESET1 and SS3. In some aspects, different repetitions of the DCI may indicate different CORESET identifiers or search space identifiers. For example, a first repetition of DCI5 may indicate CORESET0 and SS1, and a second repetition of DCI5 may indicate CORESET1 and SS2.

[0112] As indicated by reference numeral 810, the UE 120 may transmit via multiple corresponding PUCCH transmissions, and the network node 110 may receive multiple ACK messages. In some aspects, the multiple PUCCH transmissions may be included in a single PUCCH. For example, the UE 120 may transmit a first ACK (ACK1) corresponding to a first DCI, a second ACK (ACK2) corresponding to a second DCI, a third ACK (ACK3) corresponding to a third DCI, a fourth ACK (ACK4) corresponding to a fourth DCI, and a fifth ACK (ACK5) corresponding to a fifth DCI. In this example, these ACKs (e.g., ACK1, 2, 3, 4, 5) may be transmitted in a single PUCCH message. In some other aspects, the multiple PUCCH transmissions may be included in overlapping PUCCHs. For example, a portion of the ACK (e.g., ACK 2, 4) may be transmitted in a first PUCCH, and another portion of the ACK (e.g., ACK1, 3, 5) may be transmitted on a second PUCCH that overlaps the first PUCCH.

[0113] As indicated by reference numeral 815, the UE 120 and / or the network node 110 may apply a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the plurality of TCI states and in accordance with one or more rules. In some aspects, the one or more rules may be specific to component carriers included in the same component carrier list and may be different from the one or more rules in conjunction with the component carrier list. Figure 7 Describes the existing rules.

[0114] In some aspects, the one or more rules may indicate that the TCI update for a component carrier not included in the component carrier list will be based at least in part on the last received DCI of all DCIs that are acknowledged (ACKed) in the same PUCCH associated with the component carrier. In one example, the third component carrier may not be included in the same component carrier list as the first component carrier and the second component carrier, and / or may not be included in any component carrier list. The UE 120 may receive multiple DCI communications associated with the third component carrier, and may send multiple ACK messages via the PUCCH, wherein each ACK message in the multiple ACK messages corresponds to a corresponding DCI communication in the multiple DCI communications. In this example, the one or more rules may indicate that the TCI state indicated by the last received DCI communication in the multiple DCI communications will be used for the TCI update of the third component carrier. The last received DCI communication may be the most recently received DCI communication in the multiple DCI communications. In another example, two or more of the multiple DCI communications may overlap (e.g., may be received in the same symbol) and may be the last received DCI communication in the multiple DCI communications. In this case, the one or more rules may indicate that a TCI update is applied that is determined based at least in part on a CORESET ID and / or a search space ID associated with the two or more overlapping DCI communications. For example, the one or more rules may indicate that a TCI update is based at least in part on a TCI state associated with a DCI communication associated with a minimum CORESET ID or a minimum search space ID in the two or more overlapping DCI communications.

[0115] In some aspects, when a component carrier (such as a first component carrier and / or a second component carrier) is included in a component carrier list, the one or more rules may indicate that a TCI update for all component carriers included in the component carrier list is determined based at least in part on the last received DCI of all DCIs that were last acknowledged in the same symbol or time slot. The time slot may be located in the same PUCCH symbol. In an example, the UE 120 may perform a PUCCH transmission in a first PUCCH including ACK1, ACK2, ACK3, ACK4, and ACK5 corresponding to DCI1, DCI2, DCI3, DCI4, and DCI5, respectively. In this example, DCI5 may be the last received DCI communication and may not overlap with any other DCI communication. Therefore, the UE 120 and / or the network node 110 may apply a TCI update based at least in part on TCI5 indicated by DCI5. The TCI update may be applied to both the first component carrier and the second component carrier. For example, the one or more rules may indicate that the TCI update is applied to all component carriers included in the component carrier list.

[0116] In some aspects, the one or more rules may indicate: using a component carrier identifier, such as a component carrier identifier associated with the received DCI or a component carrier identifier indicated in the DCI, to select the DCI for determining the TCI update based at least in part on two or more DCI communications that overlap and are the last received DCI communications. In one example, the first component carrier and the second component carrier may be included in the same component carrier list. The last received DCI communication may include DCI3 and DCI5 associated with the first component carrier, and DCI4 associated with the second component carrier. DCI3, DCI4, and DCI5 may be overlapping DCIs. In some aspects, the overlap may be an overlap in time, such as a symbol-level overlap or a slot-level overlap. For example, two DCI communications may not overlap in the same symbol, but may overlap in the same slot. In some aspects, the overlap may be a partial overlap. For example, the first component carrier may have a different SCS from the second component carrier, and therefore, the first component carrier may only partially overlap with the second component carrier. The one or more rules may instruct the UE 120 and / or the network node 110 to determine the TCI update based at least in part on the component carrier identifier using one of TCI3, TCI4, and TCI5 (corresponding to the last received DCI communication). For example, the one or more rules may instruct the UE 120 and / or the network node 110 to select the TCI for the TCI update based at least in part on the corresponding DCI with the smallest component carrier identifier in the plurality of DCI communications. In another example, the one or more rules may instruct the UE 120 and / or the network node 110 to select the TCI for the TCI update based at least in part on the corresponding DCI with the largest component carrier identifier in the plurality of DCI communications.

[0117] In some aspects, two or more DCI communications in overlapping DCI communications may have the same component carrier identifier. For example, the minimum component carrier identifier may be the first component carrier identifier, and both DCI3 and DCI5 may be associated with the first component carrier. In this case, the one or more rules may indicate that the TCI for TCI update is selected based at least in part on the CORESET identifier associated with the corresponding DCI. For example, DCI3 may be associated with CORESET0, and DCI5 may be associated with CORESET1. Therefore, the UE 120 and / or the network node 110 may select TCI3 (corresponding to DCI3) to be applied as the TCI update for the first component carrier and the second component carrier. In some aspects, two or more DCI communications in overlapping DCI communications may have the same component carrier identifier and the same CORESET identifier. For example, both DCI3 and DCI5 may be associated with the first component carrier and associated with CORESET0. In this case, the one or more rules may indicate that the TCI for TCI update is selected based at least in part on the search space identifier associated with the corresponding DCI. For example, DCI3 may be associated with SS0, and DCI5 may be associated with SS1. Therefore, UE120 and / or network node 110 may select TCI3 (corresponding to DCI3) to be applied as a TCI update for the first component carrier and the second component carrier. The rules described herein are provided as examples only. For example, the one or more rules may be based at least in part on conditions different from a component carrier identifier, a CORESET identifier, and a search space identifier. Additionally or alternatively, the one or more rules may indicate that the conditions are applied in any order. For example, the one or more rules may indicate: selecting a TCI based at least in part on a corresponding DCI with a minimum search space identifier, regardless of the component carrier identifier and / or the CORESET identifier.

[0118] In some aspects, the TCI states for the component carriers in the component carrier list may be determined separately based at least in part on the transmission direction. For example, a first type of TCI may be associated with a downlink transmission and a joint transmission, while a second type of TCI may be associated with an uplink transmission. In some aspects, the UE 120 and / or the network node 110 may apply different TCI updates for downlink / joint transmission and uplink transmission. In one example, a DCI1 associated with a first component carrier (indicating UL TCI1) and a DCI2 associated with a second component carrier (indicating DL TCI2) may be received at a first time. A DCI3 associated with the first component carrier (indicating DL TCI3) and a DCI4 associated with the second component carrier (indicating UL TCI4) may be received at a second time. A DCI5 associated with the first component carrier (indicating DL TCI5) may be received at a third time. The one or more rules may indicate selecting an uplink TCI corresponding to the last received DCI indicating an uplink TCI, and selecting a downlink / joint TCI corresponding to the most recently received DCI indicating a downlink / joint TCI. In this case, the UE 120 and / or the network node 110 may select TCI4 for uplink TCI and may select TCI5 for downlink / joint TCI.

[0119] In some aspects, when a PDCCH carrying a DCI has repetitions, the last symbol in the last repetition may be used to determine the DCI reception time. The CORESET ID and / or search space ID may be different in different PDCCH repetitions. In some aspects, the CORESET ID and search space ID may be determined based at least in part on a predefined repetition, such as the last repetition of the PDCCH. In some aspects, when a PUCCH carrying an ACK has repetitions, the last portion of the PUCCH repetition may be used to determine the ACK reception time. In some aspects, when a PDCCH carrying a DCI has repetitions, the last symbol in the earliest repetition may be used to determine the DCI reception time.

[0120] As described above, an ACK message based at least in part on a DCI communication and associated with multiple component carriers may be included in the same PUCCH resource. When a component carrier is not included in the component carrier list, the UE 120 or the network node 110 may use the DCI received last in time to determine the TCI update. When multiple DCIs are received in the same symbol of a component carrier, the UE 120 or the network node 110 may use the CORESET ID or the search space ID to determine the TCI update. However, when the component carriers are included in the same component carrier list, the existing rules may not apply. Therefore, the UE 120 and the network node 110 may not be able to determine which TCI will be used for the component carriers included in the same component carrier list. Using the techniques and devices described herein, the UE 120 and the network node 110 may determine the TCI update to be applied to multiple component carriers included in the component carrier list. The TCI update may be based at least in part on a selected DCI communication and one or more rules in a plurality of DCI communications, wherein each DCI communication indicates that a specific TCI is applied.

[0121] As indicated above, Figure 8 is provided as an example. Other examples may differ from those described above. Figure 8 Examples described.

[0122] Fig. 9900 is a schematic diagram of a first example of TCI selection for TCI update according to the present disclosure. UE 120 may receive multiple DCI communications associated with CC0 705 and CC1 710, such as DCI1 905, DCI2 910, DCI3 915, DCI4 920, and DCI5 925. Each DCI communication may indicate a TCI state. For example, DCI1 905 may indicate that TCI1 is applied, DCI2 910 may indicate that TCI2 is applied, DCI3 915 may indicate that TCI3 is applied, DCI4 920 may indicate that TCI4 is applied, and DCI5 925 may indicate that TCI5 is applied. CC0 705 and CC1 710 may be configured on the same CC list, and TCI update may be applied to each CC on the CC list. At a first time, UE 120 may receive a first repetition of DCI1 905 associated with CC0 705, DCI2 910 associated with CC1 710, and DCI5 925 associated with CC0 705. At a second time, UE 120 may receive DCI3 915 associated with CC0 705, DCI4 920 associated with CC1 710, and a second repetition of DCI5 925 associated with CC0 705. UE 120 may send an ACK message corresponding to one or more of the received DCI communications via PUCCH 930. For example, UE 120 may send ACK1, ACK2, ACK3, ACK4, and ACK5 (shown as ACK1, 2, 3, 4, 5) corresponding to DCI1, DCI2, DCI3, DCI4, and DCI5, respectively. DCI1 905 may be associated with CORESET0. DCI3 915 may be associated with CORESET1 and SS3. A first repetition of DCI5 925 may be associated with CORESET0 and SS1, and a second repetition of DCI5 925 may be associated with CORESET1 and SS2.

[0123] As described herein, the UE 120 and / or the network node 110 may be configured with one or more rules for selecting a TCI state for performing TCI updates for component carriers included in the same component carrier list. The one or more rules may be based at least in part on the order in which the DCI communications are received, the PUCCH on which the corresponding ACK message is sent, the component carrier identifier, the CORESET identifier, and / or the search space identifier, etc. In this case, DCI1 905, DCI2 910, DCI3 915, DCI4 920, and DCI5 925 are acknowledged by the same PUCCH (PUCCH 930). The second repetition of DCI3 915, DCI4 920, and DCI5 925 is received last in time. DCI3 915 and DCI5 925 are received in the component carrier with the smaller component carrier identifier (CC0). The second repetition of DCI3 915 and DCI5 925 has the same CORESET ID (CORESET1). However, the second repetition of DCI5 925 has a smaller SSID than DCI3 915. For example, DCI5 925 is associated with SS2, while DCI3 915 is associated with SS3. Therefore, TCI5 indicated by DCI5 925 may be used as TCI for TCI update of all component carriers in the component carrier list.

[0124] As indicated above, Fig. 9 is provided as an example. Other examples may differ from those described above. Fig. 9 Examples described.

[0125] Fig.101 is a schematic diagram of a second example 1000 of TCI selection for TCI update according to the present disclosure. UE 120 may receive multiple DCI communications associated with CC0 705 and CC1 710, such as DCI1 1005, DCI2 1010, DCI3 1015, DCI4 1020, and DCI5 1025. Each DCI communication may indicate a TCI state. For example, DCI1 1005 may indicate that TCI1 is applied, DCI2 1010 may indicate that TCP2 is applied, DCI3 1015 may indicate that TCI3 is applied, DCI4 1020 may indicate that TCI4 is applied, and DCI5 1025 may indicate that TCI5 is applied. CC0 705 and CC1 710 may be configured on the same CC list, and TCI update may be applied to each CC on the CC list. At a first time, UE 120 may receive a first repetition of DCI1 1005 associated with CC0 705, DCI2 1010 associated with CC1 710, and DCI5 1025 associated with CC0 705. At a second time, UE 120 may receive DCI3 1015 associated with CC0 705, DCI4 1020 associated with CC1 710, and a second repetition of DCI5 1025 associated with CC0 705. UE 120 may send a first ACK message including ACK1, ACK3, and ACK5 associated with DCI1 1005, DCI3 1015, and DCI5 1025, respectively, at a third time. UE 120 may send the first ACK message via PUCCH 1030. UE 120 may send a second ACK message including ACK2 and ACK4 associated with DCI2 1010 and DCI4 1020, respectively, at a fourth time. UE 120 may send the second ACK message via PUCCH 1035. UE 120 may send a third ACK message including ACK1, ACK3, and ACK5 associated with DCI1 1005, DCI3 1015, and DCI5 1025, respectively, at a fourth time. UE 120 may send the third ACK message via PUCCH 1040. DCI1 905 may be associated with CORESET0. DCI3 915 may be associated with CORESET1 and SS3. A first repetition of DCI5 925 may be associated with CORESET0 and SS1, and a second repetition of DCI5 925 may be associated with CORESET1 and SS2.

[0126] As described herein, the UE 120 and / or the network node 110 may be configured with one or more rules for selecting a TCI state for performing TCI updates for component carriers included in the same component carrier list. The one or more rules may be based at least in part on the order in which the DCI communications are received, the PUCCH on which the corresponding ACK messages are sent, the component carrier identifier, the CORESET identifier, and / or the search space identifier, etc. In this case, the latest ACK corresponding to DCI1 1005, DCI2 1010, DCI3 1015, DCI4 1020, and DCI5 1025 is sent via different PUCCHs (e.g., PUCCH 1035 and PUCCH 1040). However, PUCCH 1035 and PUCCH 1040 overlap in time. Therefore, the UE 120 and / or the network node 110 may consider sending ACKs corresponding to DCI1 1005, DCI2 1010, DCI3 1015, DCI4 1020, and DCI5 1025 simultaneously. The second repetitions of DCI3 1015, DCI4 1020, and DCI5 1025 are received last in time. DCI3 1015 and DCI5 1025 are received in a component carrier with a smaller component carrier identifier (CC0). The second repetitions of DCI3 1015 and DCI5 1025 have the same CORESET ID (CORESET1). However, the second repetition of DCI5 1025 has a smaller SSID than DCI3 1015. For example, DCI5 1025 is associated with SS2, while DCI3 1015 is associated with SS3. Therefore, TCI5 indicated by DCI5 1025 may be used as TCI for TCI update for all component carriers in the component carrier list.

[0127] As indicated above, Fig.10 is provided as an example. Other examples may differ from those described above. Fig.10 Examples described.

[0128] Fig.111 is a schematic diagram of a third example 1100 of TCI selection for TCI update according to the present disclosure. As described herein, the TCI states for component carriers in a component carrier list may be determined separately based at least in part on a transmission direction. For example, a first type of TCI may be associated with a downlink transmission and a joint transmission, and a second type of TCI may be associated with an uplink transmission. CC0 705 and CC1 710 may be configured on the same CC list, and a TCI update may be applied to each CC on the CC list. In some aspects, the UE 120 and / or the network node 110 may apply different TCI updates for downlink / joint transmission and for uplink transmission. In one example, DCI1 1105 (indicating UL TCI1) associated with CC0 705 and DCI2 1110 (indicating DL TCI2) associated with CC1 710 may be received at a first time. DCI3 1115 (indicating DL TCI3) associated with CC0 705 and DCI4 1120 (indicating UL TCI4) associated with CC1 710 may be received at a second time. DCI5 1125 (indicating DL TCI5) associated with CC0 705 may be received at a third time. The one or more rules may indicate: selecting an uplink TCI corresponding to the last received DCI indicating an uplink TCI, and selecting a downlink / joint TCI corresponding to the last received DCI indicating a downlink / joint TCI. In this case, the last received DCI communication indicating an uplink TCI is DCI4 1120, and the last received communication indicating a downlink / joint TCI is TCI5 1125. Therefore, the UE 120 and / or the network node 110 may select TCI4 for the uplink TCI, and select TCI5 for the downlink / joint TCI.

[0129] As indicated above, Fig.11 is provided as an example. Other examples may differ from those described above. Fig.11 Examples described.

[0130] Fig.12 1 is a diagram illustrating an example process 1200 performed, for example, by a UE according to the present disclosure. Example process 1200 is an example in which a UE (eg, UE 120) performs operations associated with updating TCI for a component carrier list.

[0131] like Fig.12As shown, in some aspects, the process 1200 may include: receiving a plurality of DCI communications associated with a first component carrier and a second component carrier, the plurality of DCI communications indicating a plurality of corresponding TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication in the plurality of DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list (block 1210). For example, the UE (e.g., using the communication manager 140 and / or the receiving component 1402, Fig.14 ) may receive multiple DCI communications associated with a first component carrier and a second component carrier, the multiple DCI communications indicating multiple corresponding TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication of the multiple DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list, as described above.

[0132] like Fig.12 As further shown, in some aspects, process 1200 may include sending multiple ACK messages via multiple corresponding PUCCH transmissions, wherein the multiple PUCCH transmissions are included in a single PUCCH or included in overlapping PUCCHs (block 1220). For example, the UE (e.g., using communication manager 140 and / or transmitting component 1404, such as Fig.14 As shown) multiple ACK messages may be sent via multiple corresponding PUCCH transmissions, where the multiple PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs, as described above.

[0133] like Fig.12 As further shown, in some aspects, process 1200 may include: applying a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in a plurality of TCI states and according to one or more rules (block 1230). For example, the UE (e.g., using communication manager 140 and / or application component 1408, such as Fig.14 As shown) may apply a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in a plurality of TCI states and according to one or more rules, as described above.

[0134] Process 1200 may include additional aspects, such as any single aspect or any combination of the aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0135] In a first aspect, process 1200 includes receiving multiple other DCI communications indicating multiple corresponding other TCI states associated with a third component carrier that is not included in the component carrier list, sending multiple other ACK messages via multiple corresponding other PUCCH transmissions included in another PUCCH, wherein each ACK message in the multiple other ACK messages corresponds to a corresponding DCI communication in the multiple other DCI communications, and applying different TCI updates to the third component carrier based at least in part on a TCI state in the multiple other TCI states corresponding to a last DCI communication in the multiple other DCI communications.

[0136] In a second aspect, alone or in combination with the first aspect, process 1200 includes: updating the different TCI to the third component carrier according to a control resource set identifier or a component carrier identifier, at least in part based on two or more of the multiple DCI communications being received in the same symbol in the third component carrier.

[0137] In a third aspect, alone or in combination with one or more of the first and second aspects, applying the TCI update to the first component carrier and the second component carrier comprises: applying the TCI update to all component carriers in the same component carrier list.

[0138] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the plurality of DCI communications comprises: selected plurality of DCI communications associated with a plurality of ACK messages sent via a last PUCCH transmission of the plurality of PUCCH transmissions.

[0139] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the TCI state corresponds to a TCI state associated with a last DCI communication of the selected plurality of DCI communications.

[0140] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the last PUCCH transmission comprises multiple ACK messages sent in the same symbol or the same time slot.

[0141] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, the multiple DCI communications include a first DCI communication and a second DCI communication that overlap in time, and are associated with multiple ACK messages sent via a last PUCCH transmission among the multiple PUCCH transmissions.

[0142] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, the TCI state is based at least in part on a component carrier identifier associated with receiving the first DCI communication or the second DCI communication, or at least in part on a component carrier identifier included in the first DCI communication or the second DCI communication.

[0143] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the overlap associated with the overlap in time is a symbol-level overlap or a slot-level overlap.

[0144] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the overlap associated with the overlap in time is a partial overlap in time.

[0145] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the one or more rules indicate that the TCI state is applied to the first component carrier and the second component carrier according to a component carrier identifier priority.

[0146] In the twelfth aspect, alone or in combination with one or more aspects from the first to the eleventh aspects, the one or more rules further indicate: at least in part based on the first component carrier and the second component carrier having the same component carrier identifier priority, the TCI state is applied to the first component carrier and the second component carrier according to the control resource set priority.

[0147] In the thirteenth aspect, alone or in combination with one or more aspects of the first to twelfth aspects, the one or more rules further indicate: at least in part based on the first component carrier and the second component carrier having the same component carrier identifier priority and the same control resource set priority, the TCI state is applied to the first component carrier and the second component carrier according to the search space priority.

[0148] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, applying the TCI state to the first component carrier and the second component carrier includes: using the first TCI state for downlink TCI or joint TCI, and applying the second TCI state to the uplink TCI.

[0149] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, process 1200 includes: determining timing information, component carrier priority information, control resource set priority information, or search space priority information for DCI reception based on the last symbol in the last repetition of the repeated physical downlink control channel.

[0150] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, process 1200 includes: determining timing information, component carrier priority information, control resource set priority information, or search space priority information for ACK message transmission based on the last part of the repeated PUCCH.

[0151] In the seventeenth aspect, alone or in combination with one or more aspects from the first to sixteenth aspects, process 1200 includes: determining timing information, component carrier priority information, control resource set priority information, or search space priority information for DCI reception based on the last symbol in the first repetition of the repeated physical downlink control channel.

[0152] In an eighteenth aspect, alone or in combination with one or more of aspects one to seventeen, process 1200 includes starting a timer based at least in part on receiving a DCI associated with a first component carrier or a second component carrier, and applying a TCI update based at least in part on expiration of the timer.

[0153] In the nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, receiving multiple DCI communications associated with a first component carrier and a second component carrier includes: receiving a first DCI associated with the first component carrier indicating application of a first TCI state, receiving a second DCI associated with the first component carrier indicating application of a second TCI state, receiving a third DCI associated with the second component carrier indicating application of a third TCI state, and receiving a fourth DCI associated with the second component carrier indicating application of a fourth TCI state.

[0154] In the twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, sending the multiple ACK messages via the multiple corresponding PUCCH transmissions includes: sending a first ACK message corresponding to a first DCI via a first PUCCH transmission, sending a second ACK message corresponding to a second DCI via a second PUCCH transmission, sending a third ACK message corresponding to a third DCI via a third PUCCH transmission, and sending a fourth ACK message corresponding to a fourth DCI via a fourth PUCCH transmission, wherein the first PUCCH transmission, the second PUCCH transmission, the third PUCCH transmission, and the fourth PUCCH transmission are included in a single PUCCH or are included in overlapping PUCCHs.

[0155] Although Fig.12 An example block diagram of process 1200 is shown, but in some aspects, process 1200 may include Fig.12The blocks in the process 1200 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1200. Additionally or alternatively, two or more blocks in the blocks of the process 1200 may be executed in parallel.

[0156] Fig.13 is a diagram illustrating an example process 1300, for example, performed by a network node, according to the present disclosure. The example process 1300 is an example in which a network node (eg, the network node 110) performs operations associated with updating a TCI for a component carrier list.

[0157] like Fig.13 As shown, in some aspects, process 1300 may include: sending a plurality of DCI communications associated with a first component carrier and a second component carrier, which indicate a plurality of corresponding TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication in the plurality of DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list (block 1310). For example, a network node (e.g., using communication manager 150 and / or sending component 1504, such as Fig.15 As shown) can send multiple DCI communications associated with a first component carrier and a second component carrier, the multiple DCI communications indicating multiple corresponding TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication in the multiple DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list, as described above.

[0158] like Fig.13 As further shown, in some aspects, process 1300 may include receiving multiple ACK messages via multiple corresponding PUCCH transmissions, wherein the multiple PUCCH transmissions are included in a single PUCCH or included in overlapping PUCCHs (block 1320). For example, a network node (e.g., using communication manager 150 and / or receiving component 1502, such as Fig.15 ) may receive multiple ACK messages via multiple corresponding PUCCH transmissions, where the multiple PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs, as described above.

[0159] like Fig.13 As further shown, in some aspects, process 1300 may include applying a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in a plurality of TCI states and in accordance with one or more rules (block 1330). For example, a network node (e.g., using communication manager 150 and / or application component 1508, such as Fig.15 As shown) may apply a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in a plurality of TCI states and according to one or more rules, as described above.

[0160] Process 1300 may include additional aspects, such as any single aspect or any combination of the aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0161] In a first aspect, process 1300 includes sending multiple other DCI communications indicating multiple corresponding other TCI states associated with a third component carrier that is not included in the component carrier list, receiving multiple other ACK messages via multiple corresponding other PUCCH transmissions included in another PUCCH, wherein each ACK message in the multiple other ACK messages corresponds to a corresponding DCI communication in the multiple other DCI communications, and applying different TCI updates to the third component carrier based at least in part on a TCI state in the multiple other TCI states corresponding to a last DCI communication of the multiple other DCI communications.

[0162] In a second aspect, alone or in combination with the first aspect, process 1300 includes: applying the different TCI updates to the third component carrier according to a control resource set identifier or a component carrier identifier, at least in part based on two or more of the multiple DCI communications being sent in the same symbol in the third component carrier.

[0163] In a third aspect, alone or in combination with one or more of the first and second aspects, applying the TCI update to the first component carrier and the second component carrier comprises: applying the TCI update to all component carriers in the same component carrier list.

[0164] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the plurality of DCI communications comprises: selected plurality of DCI communications associated with a plurality of ACK messages received via a last PUCCH transmission of the plurality of PUCCH transmissions.

[0165] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the TCI state corresponds to a TCI state associated with a last DCI communication of the selected plurality of DCI communications.

[0166] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the last PUCCH transmission comprises: multiple ACK messages sent in the same symbol or the same time slot.

[0167] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, the multiple DCI communications include: a first DCI communication and a second DCI communication that overlap in time, and are associated with multiple ACK messages received via a last PUCCH transmission among the multiple PUCCH transmissions.

[0168] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, the TCI state is based at least in part on a component carrier identifier associated with sending the first DCI communication or the second DCI communication, or is based at least in part on a component carrier identifier included in the first DCI communication or the second DCI communication.

[0169] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the overlap associated with the overlap in time is a symbol-level overlap or a slot-level overlap.

[0170] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the overlap associated with the overlap in time is a partial overlap in time.

[0171] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the one or more rules indicate that the TCI state is applied to the first component carrier and the second component carrier according to component carrier identifier priority.

[0172] In the twelfth aspect, alone or in combination with one or more aspects from the first to the eleventh aspects, the one or more rules further indicate: at least in part based on the first component carrier and the second component carrier having the same component carrier identifier priority, the TCI state is applied to the first component carrier and the second component carrier according to the control resource set priority.

[0173] In the thirteenth aspect, alone or in combination with one or more aspects of the first to twelfth aspects, the one or more rules further indicate: at least in part based on the first component carrier and the second component carrier having the same component carrier identifier priority and the same control resource set priority, the TCI state is applied to the first component carrier and the second component carrier according to the search space priority.

[0174] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, applying the TCI state to the first component carrier and the second component carrier includes: using the first TCI state for downlink TCI or joint TCI, and using the second TCI state for uplink TCI.

[0175] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, process 1300 includes: determining timing information, component carrier priority information, control resource set priority information, or search space priority information for DCI transmission based on the last symbol in the last repetition of the repeated physical downlink control channel.

[0176] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, process 1300 includes: determining timing information, component carrier priority information, control resource set priority information, or search space priority information for ACK message reception based on the last part of the repeated PUCCH.

[0177] In the seventeenth aspect, alone or in combination with one or more aspects from the first to sixteenth aspects, process 1300 includes: determining timing information, component carrier priority information, control resource set priority information, or search space priority information for DCI transmission based on the last symbol in the first repetition of the repeated physical downlink control channel.

[0178] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, sending multiple DCI communications associated with the first component carrier and the second component carrier includes: sending a first DCI associated with the first component carrier indicating application of a first TCI state, sending a second DCI associated with the first component carrier indicating application of a second TCI state, sending a third DCI associated with the second component carrier indicating application of a third TCI state, and sending a fourth DCI associated with the second component carrier indicating application of a fourth TCI state.

[0179] In the nineteenth aspect, alone or in combination with one or more aspects from the first to the eighteenth aspects, receiving multiple ACK messages via multiple corresponding PUCCH transmissions includes: receiving a first ACK message corresponding to a first DCI via a first PUCCH transmission, receiving a second ACK message corresponding to the second DCI via a second PUCCH transmission, receiving a third ACK message corresponding to the third DCI via a third PUCCH transmission, and receiving a fourth ACK message corresponding to a fourth DCI via a fourth PUCCH transmission.

[0180] Although Fig.13 Example blocks of process 1300 are shown, but in some aspects, process 1300 may include Fig.13 In the example of FIG. 1300 , there may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the multiple blocks of process 1300 may be performed in parallel.

[0181] Fig.14 1400 is a schematic diagram of an example apparatus 1400 for wireless communication according to the present disclosure. Apparatus 1400 may be a UE, or a UE may include apparatus 1400. In some aspects, apparatus 1400 includes a receiving component 1402 and a sending component 1404, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a base station, or another wireless communication device) using receiving component 1402 and sending component 1404. As further shown, apparatus 1400 may include a communication manager 140. Communication manager 140 may include one or more of the following: an application component 1408, a determination component 1410, or an initiation component 1412, and the like.

[0182] In some aspects, the apparatus 1400 may be configured to perform the Figure 8-11 Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Fig.12 The process 1200. In some aspects, Fig.14 The apparatus 1400 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.14 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0183] The receiving component 1402 may receive communications from the apparatus 1406, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1402 may provide the received communications to one or more other components of the apparatus 1400. In some aspects, the receiving component 1402 may perform signal processing (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the apparatus 1400. In some aspects, the receiving component 1402 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a UE are described.

[0184] Transmit component 1404 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to device 1406. In some aspects, one or more other components of device 1406 may generate communications and may provide the generated communications to transmit component 1404 for transmission to device 1406. In some aspects, transmit component 1404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping or encoding, etc.) on the generated communications and may transmit the processed signals to device 1406. In some aspects, transmit component 1404 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1404 can be co-located with the receive component 1402 in a transceiver.

[0185] The receiving component 1402 may receive a plurality of DCI communications associated with a first component carrier and a second component carrier, the plurality of DCI communications indicating a plurality of respective TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one of the plurality of DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list. The sending component 1404 may send a plurality of ACK messages via a plurality of respective PUCCH transmissions, wherein the plurality of PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs. The applying component 1408 may apply a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the plurality of TCI states and according to one or more rules.

[0186] The receiving component 1402 may receive a plurality of other DCI communications associated with a third component carrier not included in the component carrier list, indicating a plurality of corresponding other TCI states. The sending component 1404 may send a plurality of other ACK messages via a plurality of corresponding other PUCCH transmissions included in another PUCCH, wherein each of the plurality of other ACK messages corresponds to a corresponding DCI communication in the plurality of other DCI communications. The applying component 1408 may apply a different TCI update to the third component carrier based at least in part on a TCI state in the plurality of other TCI states corresponding to a last DCI communication in the plurality of other DCI communications. The applying component 1408 may apply the different TCI updates to the third component carrier based at least in part on two or more of the plurality of DCI communications being received in the same symbol in the third component carrier according to a control resource set identifier or a component carrier identifier.

[0187] The determining component 1410 may determine the timing information, component carrier priority information, control resource set priority information, or search space priority information for DCI reception based on the last symbol in the last repetition of the repeated physical downlink control channel. The determining component 1410 may determine the timing information, component carrier priority information, control resource set priority information, or search space priority information for ACK message transmission based on the last part of the repeated PUCCH. The determining component 1410 may determine the timing information, component carrier priority information, control resource set priority information, or search space priority information for DCI reception based on the last symbol in the first repetition of the repeated physical downlink control channel. The initiating component 1412 may start a timer based at least in part on receiving DCI associated with the first component carrier or the second component carrier, and apply a TCI update based at least in part on the expiration of the timer.

[0188] Fig.14 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.14 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.14 Two or more components shown may be implemented in a single component, or Fig.14 The single components shown may be implemented as multiple, distributed components. Additionally or alternatively, Fig.14 The illustrated set (one or more) of components may perform the operations described as being performed by Fig.14 Another group of components shown performs one or more functions.

[0189] Fig.15 1 is a schematic diagram of an example apparatus 1500 for wireless communication according to the present disclosure. Apparatus 1500 may be a network node, or a network node may include apparatus 1500. In some aspects, apparatus 1500 includes a receiving component 1502 and a sending component 1504, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1500 may communicate with another apparatus 1506 (such as, a UE, a base station, or another wireless communication device) using receiving component 1502 and sending component 1504. As further shown, apparatus 1500 may include a communication manager 150. Communication manager 150 may include one or more of the following: an application component 1508 or a determination component 1510, etc.

[0190] In some aspects, the apparatus 1500 may be configured to perform the Figure 8-Figure 11Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as, Fig.13 The process 1300. In some aspects, Fig.15 The apparatus 1500 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.15 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0191] Receiving component 1502 may receive communications from device 1506, such as reference signals, control information, data communications, or a combination thereof. Receiving component 1502 may provide the received communications to one or more other components of device 1500. In some aspects, receiving component 1502 may perform signal processing (e.g., filtering, amplifying, demodulating, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of device 1500. In some aspects, receiving component 1502 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0192] Transmit component 1504 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to device 1506. In some aspects, one or more other components of device 1500 may generate communications and may provide the generated communications to transmit component 1504 for transmission to device 1500. In some aspects, transmit component 1504 may perform signal processing (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping or encoding, etc.) on the generated communications and may transmit the processed signals to device 1506. In some aspects, transmit component 1504 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 1504 can be co-located with the receive component 1502 in a transceiver.

[0193] The sending component 1504 may send a plurality of DCI communications associated with a first component carrier and a second component carrier, the plurality of DCI communications indicating a plurality of respective TCI states, wherein each of the first component carrier and the second component carrier is associated with at least one of the plurality of DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list. The receiving component 1502 may receive a plurality of ACK messages via a plurality of respective PUCCH transmissions, wherein the plurality of PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs. The applying component 1508 may apply a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the plurality of TCI states and according to one or more rules.

[0194] The sending component 1504 may send a plurality of other DCI communications associated with a third component carrier not included in the component carrier list, the plurality of other DCI communications indicating a plurality of corresponding other TCI states. The receiving component 1502 may receive a plurality of other ACK messages via a plurality of corresponding other PUCCH transmissions included in another PUCCH, wherein each of the plurality of other ACK messages corresponds to a corresponding DCI communication in the plurality of other DCI communications. The applying component 1508 may apply a different TCI update to the third component carrier based at least in part on a TCI state in the plurality of other TCI states corresponding to a last DCI communication in the plurality of other DCI communications. The applying component 1508 may apply the different TCI updates to the third component carrier based at least in part on two or more of the plurality of DCI communications being sent in the same symbol in the third component carrier according to a control resource set identifier or a component carrier identifier.

[0195] The determining component 1510 may determine the timing information, component carrier priority information, control resource set priority information, or search space priority information for DCI transmission based on the last symbol in the last repetition of the repeated physical downlink control channel. The determining component 1510 may determine the timing information, component carrier priority information, control resource set priority information, or search space priority information for ACK message reception based on the last part of the repeated PUCCH. The determining component 1510 may determine the timing information, component carrier priority information, control resource set priority information, or search space priority information for DCI transmission based on the last symbol in the first repetition of the repeated physical downlink control channel.

[0196] Fig.15 The number and arrangement of components shown in the figure are provided as examples. Fig.15There may be additional components, fewer components, different components, or components arranged differently than those shown. Fig.15 Two or more components shown in may be implemented in a single component, or Fig.15 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.15 A set (one or more) of components shown in the figure may perform the operations described as being performed by Fig.15 One or more functions performed by another set of components shown in FIG.

[0197] A summary of some aspects of the disclosure is provided below.

[0198] Aspect 1: A method for performing wireless communications by a user equipment (UE), comprising: receiving multiple downlink control information (DCI) communications associated with a first component carrier and a second component carrier, the multiple downlink control information (DCI) communications indicating multiple corresponding transmission configuration indicator (TCI) states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication in the multiple DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list; sending multiple confirmation (ACK) messages via multiple corresponding physical uplink control channel (PUCCH) transmissions, wherein the multiple PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs; and, applying a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the multiple TCI states and according to one or more rules.

[0199] Aspect 2: The method according to Aspect 1 also includes: receiving multiple other DCI communications associated with a third component carrier that is not included in the component carrier list, and the multiple other DCI communications indicate multiple corresponding other TCI states; sending multiple other ACK messages via multiple corresponding other PUCCH transmissions included in another PUCCH, wherein each ACK message in the multiple other ACK messages corresponds to a corresponding DCI communication in the multiple other DCI communications; and, at least in part based on a TCI state in the multiple other TCI states corresponding to the last DCI communication in the multiple other DCI communications, applying different TCI updates to the third component carrier.

[0200] Aspect 3: The method according to Aspect 2 also includes: applying the different TCI updates to the third component carrier according to a control resource set identifier or a component carrier identifier, at least in part based on the fact that two or more of the multiple DCI communications are received in the same symbol in the third component carrier.

[0201] Aspect 4: The method according to any one of aspects 1-3, wherein applying the TCI update to the first component carrier and the second component carrier includes: applying the TCI update to all component carriers in the same component carrier list.

[0202] Aspect 5: The method according to any one of aspects 1-4, wherein the multiple DCI communications include: selected multiple DCI communications associated with multiple ACK messages sent via a last PUCCH transmission of the multiple PUCCH transmissions.

[0203] Aspect 6: The method according to aspect 5, wherein the TCI state corresponds to a TCI state associated with a last DCI communication of the selected plurality of DCI communications.

[0204] Aspect 7: The method according to aspect 6, wherein the last PUCCH transmission includes multiple ACK messages sent in the same symbol or the same time slot.

[0205] Aspect 8: A method according to any one of Aspects 1-7, wherein the multiple DCI communications include: a first DCI communication and a second DCI communication that overlap in time, and are associated with multiple ACK messages sent via a last PUCCH transmission among the multiple PUCCH transmissions.

[0206] Aspect 9: A method according to Aspect 8, wherein the TCI state is at least partially based on a component carrier identifier associated with receiving the first DCI communication or the second DCI communication, or at least partially based on a component carrier identifier included in the first DCI communication or the second DCI communication.

[0207] Aspect 10: The method according to aspect 8, wherein the overlap associated with the temporal overlap is a symbol-level overlap or a slot-level overlap.

[0208] Aspect 11: The method according to aspect 8, wherein the overlap associated with the temporal overlap is a partial overlap in time.

[0209] Aspect 12: The method according to aspect 8, wherein the one or more rules indicate: applying the TCI state to the first component carrier and the second component carrier according to component carrier identifier priority.

[0210] Aspect 13: A method according to Aspect 12, wherein the one or more rules further indicate: applying the TCI state to the first component carrier and the second component carrier according to a control resource set priority, at least in part based on the fact that the first component carrier and the second component carrier have the same component carrier identifier priority.

[0211] Aspect 14: A method according to Aspect 13, wherein the one or more rules further indicate: applying the TCI state to the first component carrier and the second component carrier according to the search space priority, at least in part based on the fact that the first component carrier and the second component carrier have the same component carrier identifier priority and the same control resource set priority.

[0212] Aspect 15: A method according to any one of Aspects 1-14, wherein applying the TCI state to the first component carrier and the second component carrier includes: using a first TCI state for downlink TCI or joint TCI, and using a second TCI state for uplink TCI.

[0213] Aspect 16: The method according to Aspect 15 also includes: determining timing information, component carrier priority information, control resource set priority information, or search space priority information for DCI reception based on the last symbol in the last repetition of the repeated physical downlink control channel.

[0214] Aspect 17: The method according to aspect 15 further includes: determining timing information, component carrier priority information, control resource set priority information, or search space priority information for ACK message transmission according to the last part of the repeated PUCCH.

[0215] Aspect 18: The method according to Aspect 15 also includes: determining timing information, component carrier priority information, control resource set priority information or search space priority information for DCI reception based on the last symbol in the first repetition of the repeated physical downlink control channel.

[0216] Aspect 19: The method according to any one of Aspects 1-18 also includes: starting a timer at least in part based on receiving DCI associated with the first component carrier or the second component carrier, and applying the TCI update at least in part based on expiration of the timer.

[0217] Aspect 20: A method according to any one of Aspects 1-19, wherein receiving the multiple DCI communications associated with the first component carrier and the second component carrier includes: receiving a first DCI associated with the first component carrier indicating application of a first TCI state, receiving a second DCI associated with the first component carrier indicating application of a second TCI state, receiving a third DCI associated with the second component carrier indicating application of a third TCI state, and receiving a fourth DCI associated with the second component carrier indicating application of a fourth TCI state.

[0218] Aspect 21: A method according to Aspect 20, wherein sending the multiple ACK messages via the multiple corresponding PUCCH transmissions includes: sending a first ACK message corresponding to the first DCI via a first PUCCH transmission, sending a second ACK message corresponding to the second DCI via a second PUCCH transmission, sending a third ACK message corresponding to the third DCI via a third PUCCH transmission, and sending a fourth ACK message corresponding to the fourth DCI via a fourth PUCCH transmission, wherein the first PUCCH transmission, the second PUCCH transmission, the three PUCCH transmissions and the fourth PUCCH transmission are included in the single PUCCH or included in overlapping PUCCHs.

[0219] Aspect 22: A wireless communication method performed by a network node, comprising: sending multiple downlink control information (DCI) communications associated with a first component carrier and a second component carrier, the multiple downlink control information (DCI) communications indicating multiple corresponding transmission configuration indicator (TCI) states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication in the multiple DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list; receiving multiple acknowledgment (ACK) messages via multiple corresponding physical uplink control channel (PUCCH) transmissions, wherein the multiple PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs; and, applying a TCI update to at least one of the first component carrier or the second component carrier based at least in part on a TCI state in the multiple TCI states and according to one or more rules.

[0220] Aspect 23: The method according to Aspect 22 also includes: sending multiple other DCI communications associated with a third component carrier that is not included in the component carrier list, and the multiple other DCI communications indicate multiple corresponding other TCI states; receiving multiple other ACK messages via multiple corresponding other PUCCH transmissions included in another PUCCH, wherein each ACK message in the multiple other ACK messages corresponds to a corresponding DCI communication in the multiple other DCI communications; and, at least in part based on a TCI state in the multiple other TCI states corresponding to the last DCI communication in the multiple other DCI communications, applying different TCI updates to the third component carrier.

[0221] Aspect 24: The method according to Aspect 23 further includes: applying the different TCI updates to the third component carrier according to a control resource set identifier or a component carrier identifier, at least in part based on the fact that two or more of the multiple DCI communications are sent in the same symbol in the third component carrier.

[0222] Aspect 25: The method according to any one of aspects 22-24, wherein applying the TCI update to the first component carrier and the second component carrier includes: applying the TCI update to all component carriers in the same component carrier list.

[0223] Aspect 26: The method according to any one of aspects 22-25, wherein the plurality of DCI communications comprises: a selected plurality of DCI communications associated with a plurality of ACK messages received via a last PUCCH transmission of the plurality of PUCCH transmissions.

[0224] Aspect 27: The method according to Aspect 26, wherein the TCI state corresponds to a TCI state associated with a last DCI communication of the selected plurality of DCI communications.

[0225] Aspect 28: The method according to aspect 27, wherein the last PUCCH transmission includes multiple ACK messages sent in the same symbol or the same time slot.

[0226] Aspect 29: A method according to any one of aspects 22-28, wherein the multiple DCI communications include a first DCI communication and a second DCI communication that overlap in time and are associated with multiple ACK messages received via a last PUCCH transmission of the multiple PUCCH transmissions.

[0227] Aspect 30: A method according to Aspect 29, wherein the TCI state is based at least in part on a component carrier identifier associated with sending the first DCI communication or the second DCI communication, or at least in part on a component carrier identifier included in the first DCI communication or the second DCI communication.

[0228] Aspect 31: The method according to Aspect 30, wherein the overlap associated with the temporal overlap is a symbol-level overlap or a slot-level overlap.

[0229] Aspect 32: The method according to Aspect 30, wherein the overlap associated with the temporal overlap is a partial overlap in time.

[0230] Aspect 33: The method according to aspect 30, wherein the one or more rules indicate: applying the TCI state to the first component carrier and the second component carrier according to component carrier identifier priority.

[0231] Aspect 34: A method according to Aspect 33, wherein the one or more rules further indicate: applying the TCI state to the first component carrier and the second component carrier according to the control resource set priority, at least in part based on the fact that the first component carrier and the second component carrier have the same component carrier identifier priority.

[0232] Aspect 35: A method according to Aspect 34, wherein the one or more rules further indicate: applying the TCI state to the first component carrier and the second component carrier according to the search space priority, at least in part based on the fact that the first component carrier and the second component carrier have the same component carrier identifier priority and the same control resource set priority.

[0233] Aspect 36: A method according to any one of Aspects 22-35, wherein applying the TCI state to the first component carrier and the second component carrier includes: using a first TCI state for downlink TCI or joint TCI, and using a second TCI state for uplink TCI.

[0234] Aspect 37: The method according to Aspect 36 also includes: determining timing information, component carrier priority information, control resource set priority information, or search space priority information for DCI transmission based on the last symbol in the last repetition of the repeated physical downlink control channel.

[0235] Aspect 38: The method according to Aspect 37 further includes: determining timing information, component carrier priority information, control resource set priority information or search space priority information for ACK message reception based on the last part of the repeated PUCCH.

[0236] Aspect 39: The method according to Aspect 37 also includes: determining timing information, component carrier priority information, control resource set priority information or search space priority information for DCI transmission based on the last symbol in the first repetition of the repeated physical downlink control channel.

[0237] Aspect 40: A method according to any one of Aspects 22-39, wherein sending the multiple DCI communications associated with the first component carrier and the second component carrier includes: sending a first DCI associated with the first component carrier indicating application of a first TCI state, sending a second DCI associated with the first component carrier indicating application of a second TCI state, sending a third DCI associated with the second component carrier indicating application of a third TCI state, and sending a fourth DCI associated with the second component carrier indicating application of a fourth TCI state.

[0238] Aspect 41: A method according to Aspect 40, wherein receiving the multiple ACK messages via the multiple corresponding PUCCH transmissions includes: receiving a first ACK message corresponding to the first DCI via a first PUCCH transmission, receiving a second ACK message corresponding to the second DCI via a second PUCCH transmission, receiving a third ACK message corresponding to the third DCI via a third PUCCH transmission, and receiving a fourth ACK message corresponding to the fourth DCI via a fourth PUCCH transmission.

[0239] Aspect 42: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions, the instructions being stored in the memory and executable by the processor to cause the apparatus to implement the method according to one or more of Aspects 1-21.

[0240] Aspect 43: An apparatus for wireless communication, comprising: a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1-21.

[0241] Aspect 44: An apparatus for wireless communication, comprising at least one means for performing the method according to one or more of aspects 1-21.

[0242] Aspect 45: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to implement the method according to one or more of aspects 1-21.

[0243] Aspect 46: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1-21.

[0244] Aspect 47: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions, the instructions being stored in the memory and executable by the processor to cause the apparatus to implement a method according to one or more of aspects 22-41.

[0245] Aspect 48: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 22-41.

[0246] Aspect 49: An apparatus for wireless communication, comprising at least one means for performing the method according to one or more of aspects 22-41.

[0247] Aspect 50: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 22-41.

[0248] Aspect 51: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to implement a method according to one or more of aspects 22-41.

[0249] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0250] As used herein, the term "component" is intended to be interpreted broadly as hardware, and / or a combination of hardware and software. "Software" should be interpreted broadly as instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software groupings, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language or other. As used herein, a processor is implemented with a combination of hardware, and / or hardware and software. It should be clear that the system and / or method described herein can be implemented with a combination of hardware, and / or hardware and software in different forms. The actual special control hardware or software code for implementing these systems and / or methods is not to limit various aspects. Therefore, the operation and behavior of the system and / or method are described herein without citing a specific software code-because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0251] As used herein, "satisfying a threshold" may mean that the value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0252] Even if a specific combination of features is recorded in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically recorded in the claims and / or specifically disclosed in the specification. The disclosure of various aspects includes the combination of each dependent claim with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of those items, including a single member. For example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination of multiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c or any other ordering of a, b and c).

[0253] None of the elements, actions or instructions used herein should be interpreted as key or necessary, unless clearly described as such. In addition, as used herein, the articles "a" and "an" are intended to include one or more entries, and can be used interchangeably with "one or more". In addition, as used herein, the article "described" is intended to include one or more entries related to the article "described", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more entries, and can be used interchangeably with "one or more". In the case of only expecting an entry, phrases "only one" or similar language are used. In addition, as used herein, the terms "has", "have", "having" etc. are intended to be open terms, do not limit the elements (for example, "having" A elements can also have B) that they modify. In addition, unless otherwise clearly stated, phrase "based on" is intended to mean "based at least in part on". Furthermore, as used herein, the term "or" when used in series is intended to be open-ended and may be used interchangeably with "and / or" unless expressly stated otherwise (e.g., if used in conjunction with "either or" or "only one").

Claims

1. A user equipment (UE) for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors configured to: receiving a plurality of downlink control information (DCI) communications associated with a first component carrier and a second component carrier, the plurality of downlink control information (DCI) communications indicating a plurality of respective transmission configuration indicator (TCI) states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication of the plurality of DCI communications, and wherein the first component carrier and the second component carrier are included in a same component carrier list; sending multiple acknowledgement (ACK) messages via multiple respective physical uplink control channel (PUCCH) transmissions, wherein the multiple PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs; and Based at least in part on a TCI state in the plurality of TCI states and in accordance with one or more rules, a TCI update is applied to at least one of the first component carrier or the second component carrier.

2. The UE according to claim 1, wherein: The one or more processors are further configured to: receiving a plurality of other DCI communications associated with a third component carrier not included in the component carrier list, the plurality of other DCI communications indicating a plurality of respective other TCI states; sending a plurality of other ACK messages via a plurality of respective other PUCCH transmissions included in another PUCCH, wherein each ACK message of the plurality of other ACK messages corresponds to a respective DCI communication of the plurality of other DCI communications; and Based at least in part on a TCI state in the plurality of other TCI states corresponding to a last DCI communication in the plurality of other DCI communications, a different TCI update is applied to the third component carrier.

3. The UE according to claim 2, wherein: The one or more processors are also configured to apply the different TCI updates to the third component carrier based on a control resource set identifier or a component carrier identifier, at least in part based on two or more of the multiple DCI communications being received in the same symbol in the third component carrier.

4. The UE according to claim 1, wherein: To apply the TCI update to the first component carrier and the second component carrier, the one or more processors are configured to apply the TCI update to all component carriers in the same component carrier list.

5. The UE according to claim 1, wherein: The plurality of DCI communications includes a selected plurality of DCI communications associated with a plurality of ACK messages sent via a last PUCCH transmission of the plurality of PUCCH transmissions.

6. The UE according to claim 5, wherein: The TCI state corresponds to a TCI state associated with a last DCI communication of the selected plurality of DCI communications.

7. The UE according to claim 6, wherein: The last PUCCH transmission includes multiple ACK messages sent in the same symbol or the same time slot.

8. The UE according to claim 1, wherein: The plurality of DCI communications include a first DCI communication and a second DCI communication that overlap in time and are associated with a plurality of ACK messages sent via a last PUCCH transmission of the plurality of PUCCH transmissions.

9. The UE according to claim 8, wherein: The TCI state is based at least in part on a component carrier identifier associated with receiving the first DCI communication or the second DCI communication, or based at least in part on a component carrier identifier included in the first DCCI communication or the second DCCI communication.

10. The UE according to claim 8, wherein: The overlap associated with the overlap in time is a symbol-level overlap or a slot-level overlap.

11. The UE according to claim 8, wherein: The overlap associated with the temporal overlap is a partial overlap in time.

12. The UE according to claim 8, wherein: The one or more rules indicate that the TCI state is applied to the first component carrier and the second component carrier according to component carrier identifier priority.

13. The UE according to claim 12, wherein: The one or more rules further indicate that the TCI state is applied to the first component carrier and the second component carrier according to a control resource set priority based at least in part on the first component carrier and the second component carrier having the same component carrier identifier priority.

14. The UE according to claim 13, wherein: The one or more rules further indicate that the TCI state is applied to the first component carrier and the second component carrier according to a search space priority based at least in part on the first component carrier and the second component carrier having the same component carrier identifier priority and the same control resource set priority.

15. The UE according to claim 1, wherein: To apply the TCI state to the first component carrier and the second component carrier, the one or more processors are configured to use a first TCI state for downlink TCI or joint TCI and a second TCI state for uplink TCI.

16. The UE according to claim 15, wherein: The one or more processors are further configured to determine timing information, component carrier priority information, control resource set priority information, or search space priority information for DCI reception based on a last symbol in a last repetition of a repeated physical downlink control channel.

17. The UE according to claim 15, wherein: The one or more processors are further configured to determine timing information, component carrier priority information, control resource set priority information, or search space priority information for ACK message transmission based on a last portion of the repeated PUCCH.

18. The UE according to claim 15, wherein: The one or more processors are further configured to determine timing information, component carrier priority information, control resource set priority information, or search space priority information for DCI reception based on a last symbol in a first repetition of a repeated physical downlink control channel.

19. The UE according to claim 1, wherein: The one or more processors are further configured to start a timer based at least in part on receiving DCI associated with the first component carrier or the second component carrier, and apply the TCI update based at least in part on expiration of the timer.

20. The UE according to claim 1, wherein: In order to receive the multiple DCI communications associated with the first component carrier and the second component carrier, the one or more processors are configured to: receive a first DCI associated with the first component carrier indicating a first TCI state, receive a second DCI associated with the first component carrier indicating application of a second TCI state, receive a third DCI associated with the second component carrier indicating application of a third TCI state, and receive a fourth DCI associated with the second component carrier indicating application of a fourth TCI state.

21. The UE according to claim 20, wherein: In order to send the multiple ACK messages via the multiple corresponding PUCCH transmissions, the one or more processors are configured to: send a first ACK message corresponding to the first DCI via a first PUCCH transmission, send a second ACK message corresponding to the second DCI via a second PUCCH transmission, send a third ACK message corresponding to the third DCI via a third PUCCH transmission, and send a fourth ACK message corresponding to the fourth DCI via a fourth PUCCH transmission, wherein the first PUCCH transmission, the second PUCCH transmission, the three PUCCH transmissions and the fourth PUCCH transmission are included in the single PUCCH or included in overlapping PUCCHs.

22. A network node for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors being configured to: transmitting a plurality of downlink control information (DCI) communications associated with a first component carrier and a second component carrier, the plurality of downlink control information (DCI) communications indicating a plurality of respective transmission configuration indicator (TCI) states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication of the plurality of DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list; receiving a plurality of acknowledgement (ACK) messages via a plurality of respective physical uplink control channel (PUCCH) transmissions, wherein the plurality of PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs; and Based at least in part on a TCI state in the plurality of TCI states and in accordance with one or more rules, a TCI update is applied to at least one of the first component carrier or the second component carrier.

23. The network node according to claim 22, wherein: The one or more processors are further configured to: sending a plurality of other DCI communications associated with a third component carrier not included in the component carrier list, the plurality of other DCI communications indicating a plurality of respective other TCI states; receiving a plurality of other ACK messages via a plurality of respective other PUCCH transmissions included in another PUCCH, wherein each ACK message of the plurality of other ACK messages corresponds to a respective DCI communication of the plurality of other DCI communications; and A different TCI update is applied to the third component carrier based at least in part on a TCI state of the plurality of other TCI states corresponding to a last DCI communication of the plurality of other DCI communications.

24. The network node according to claim 23, wherein: The one or more processors are further configured to apply the different TCI updates to the third component carrier according to a control resource set identifier or a component carrier identifier based at least in part on two or more of the multiple DCI communications being sent in the same symbol in the third component carrier.

25. The network node according to claim 22, wherein: To apply the TCI update to the first component carrier and the second component carrier, the one or more processors are configured to apply the TC update to all component carriers in the same component carrier list.

26. The network node according to claim 22, wherein: The plurality of DCI communications include a selected plurality of DCI communications associated with a plurality of ACK messages received via a last PUCCH transmission of the plurality of PUCCH transmissions.

27. A method of wireless communication performed by a user equipment (UE), comprising: receiving a plurality of downlink control information (DCI) communications associated with a first component carrier and a second component carrier, the plurality of downlink control information (DCI) communications indicating a plurality of respective transmission configuration indicator (TCI) states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication of the plurality of DCI communications, and wherein the first component carrier and the second component carrier are included in a same component carrier list; sending multiple acknowledgement (ACK) messages via multiple respective physical uplink control channel (PUCCH) transmissions, wherein the multiple PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs; and Based at least in part on a TCI state in the plurality of TCI states and in accordance with one or more rules, a TCI update is applied to at least one of the first component carrier or the second component carrier.

28. The method according to claim 27, further comprising: receiving a plurality of other DCI communications associated with a third component carrier not included in the component carrier list, the plurality of other DCI communications indicating a plurality of respective other TCI states; sending a plurality of other ACK messages via a plurality of respective other PUCCH transmissions included in another PUCCH, wherein each ACK message of the plurality of other ACK messages corresponds to a respective DCI communication of the plurality of other DCI communications; and A different TCI update is applied to the third component carrier based at least in part on a TCI state of the plurality of other TCI states corresponding to a last DCI communication of the plurality of other DCI communications.

29. A method for performing wireless communication by a network node, comprising: transmitting a plurality of downlink control information (DCI) communications associated with a first component carrier and a second component carrier, the plurality of downlink control information (DCI) communications indicating a plurality of respective transmission configuration indicator (TCI) states, wherein each of the first component carrier and the second component carrier is associated with at least one DCI communication of the plurality of DCI communications, and wherein the first component carrier and the second component carrier are included in the same component carrier list; receiving a plurality of acknowledgement (ACK) messages via a plurality of respective physical uplink control channel (PUCCH) transmissions, wherein the plurality of PUCCH transmissions are included in a single PUCCH or in overlapping PUCCHs; and Based at least in part on a TCI state in the plurality of TCI states and in accordance with one or more rules, a TCI update is applied to at least one of the first component carrier or the second component carrier.

30. The method of claim 29, further comprising: sending a plurality of other DCI communications associated with a third component carrier not included in the component carrier list, the plurality of other DCI communications indicating a plurality of respective other TCI states; receiving a plurality of other ACK messages via a plurality of respective other PUCCH transmissions included in another PUCCH, wherein each ACK message of the plurality of other ACK messages corresponds to a respective DCI communication of the plurality of other DCI communications; and Based at least in part on a TCI state in the plurality of other TCI states corresponding to a last DCI communication in the plurality of other DCI communications, a different TCI update is applied to the third component carrier.

Images