Default conditions for unified TCI state

Abstract

An apparatus, a method, and a computer program product for wireless communication are provided. An example method may include receiving downlink control information (DCI) indicating at least a first transmission configuration indicator (TCI) state from a network entity at a first time. The example method may also include applying a second TCI state or a third TCI state to receive the scheduled downlink transmission based on a difference between the first time and a second time associated with the scheduled downlink transmission and based on a default TCI state condition, wherein the difference is less than a threshold.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application serial number 17 / 813,263, filed on July 18, 2022, entitled “DEFAULT CONDITION FOR UNIFIEDTCI STATE,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to a wireless communication system having a transmit configuration indicator (TCI) state. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, or even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

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

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and at least one processor coupled to the memory may be configured to receive downlink control information (DCI) indicating at least a first transmission configuration indicator (TCI) state from a network entity at a first time. The memory and at least one processor coupled to the memory may be further configured to: apply a second TCI state or a third TCI state to receive a scheduled downlink transmission based on a difference between the first time and a second time associated with a scheduled downlink transmission being less than a threshold and based on a default TCI state condition.

[0008] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and at least one processor coupled to the memory may be configured to send downlink control information (DCI) indicating at least a first transmission configuration indicator (TCI) state for a user equipment (UE) at a first time. The memory and at least one processor coupled to the memory may be further configured to: apply a second TCI state or a third TCI state to send a scheduled downlink transmission based on a difference between the first time and a second time associated with the scheduled downlink transmission being less than a threshold and based on a default TCI state condition to send the scheduled downlink transmission.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2Bis a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4 is a diagram illustrating that a base station communicates with a UE via a beam set.

[0017] Figure 5 is a diagram illustrating example communications between network entities and a UE.

[0018] Figure 6 is a flow chart of a method of wireless communication.

[0019] Figure 7 is a flow chart of a method of wireless communication.

[0020] Figure 8 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0021] Fig. 9 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0022] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

[0023] Several aspects of the telecommunication system are also presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0024] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0025] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. For example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0026] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some practical environments, the equipment in conjunction with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0027] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5GNR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

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

[0029] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0030] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more decomposed base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both). The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links (such as an F1 interface). The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0031] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals on a wired transmission medium or send signals to one or more of the other units. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals on a wireless transmission medium or send signals to one or more of the other units, or both.

[0032] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 110. CU110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0033] DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RU 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.) according to a functional split (such as that defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0034] Lower layer functionality may be implemented by one or more RUs 140. In some deployments, a RU 140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based on functional splitting such as lower layer functional splitting. In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, such a configuration may enable the DU 130 and the CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0035] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle 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 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0036] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

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

[0038] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to YxMHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0039] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0040] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0041] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0042] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features 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 to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0043] In view of the above, unless otherwise specifically stated, if the term "below 6 GHz" or the like is used in this document, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" or the like is used in this document, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0044] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction for the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0045] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU.

[0046] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, the positioning determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the positioning of the UE 104. The NG-RAN may determine the positioning of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, positioning estimates, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0047] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terms. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0048] Reference again Figure 1 In some aspects, the UE 104 may include a TCI component 198. In some aspects, the TCI component 198 may be configured to receive downlink control information (DCI) indicating at least a first transmission configuration indicator (TCI) state from a network entity at a first time. In some aspects, the TCI component 198 may be further configured to apply a second TCI state or a third TCI state to receive the scheduled downlink transmission based on a difference between the first time and a second time associated with the scheduled downlink transmission being less than a threshold and based on a default TCI state condition.

[0049] In certain aspects, the base station 102 may include a TCI component 199. In some aspects, the TCI component 199 may be configured to transmit downlink control information (DCI) indicating at least a first transmission configuration indicator (TCI) state for a user equipment (UE) at a first time. In some aspects, the TCI component 199 may be further configured to apply a second TCI state or a third TCI state to transmit the scheduled downlink transmission based on a difference between the first time and a second time associated with the scheduled downlink transmission being less than a threshold and based on a default TCI state condition to transmit the scheduled downlink transmission.

[0050] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0051] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. For another example, the network node may be a base station or a network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, apparatus, device, computing system, etc. may include disclosure of UE, base station, apparatus, device, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE configured to receive information, a first base station, a first apparatus, a first device, a first computing system, a first group of one or more components, a first processing entity, etc.; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second group of one or more components, a second processing entity, etc.

[0052] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicated, or sent by the first network node.

[0053] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL), or may be time division duplex (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL). Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured to have any of the various available slot formats 0 to 61. Slot formats 0 and 1 are DL and UL, respectively. Other slot formats 2 to 61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling).

[0054] FIG. 2A to FIG. 2DThe frame structure is illustrated, and various aspects of the present disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) can be divided into 10 subframes of the same size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4 or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is conventional or extended. For conventional CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0055]

[0056] Table 1

[0057] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ 15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific parameter set and CP (normal or extended).

[0058] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0059] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0060] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as a system information block (SIB)), and paging messages.

[0061] like Figure 2CAs illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0062] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0063] Figure 3370 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0064] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be split into parallel streams. Subsequently, each stream can be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived based on reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0065] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbol on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on the channel estimate calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0066] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0067] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0068] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0069] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0070] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0071] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The TCI component 198 is used to perform various aspects.

[0072] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The TCI component 199 is used to perform various aspects.

[0073] Figure 4 4 is a diagram 400 illustrating communication between a base station 402 and a UE 404. Figure 4 , the base station 402 may send a beamformed signal to the UE 404 in one or more directions 402a, 402b, 402c, 402d, 402e, 402f, 402g, 402h. The UE 404 may receive the beamformed signal from the base station 402 in one or more reception directions 404a, 404b, 404c, 404d. The UE 404 may also send a beamformed signal to the base station 402 in one or more directions 404a-404d. The base station 402 may receive the beamformed signal from the UE 404 in one or more reception directions 402a-402h. The base station 402 / UE 404 may perform beam training to determine the best reception direction and transmission direction for each of the base station 402 / UE 404. The transmission direction and the reception direction for the base station 402 may be the same or may be different. The transmission direction and the reception direction for the UE 404 may be the same or may be different. The term “beam” may be alternatively referred to as a “spatial filter.” Beamforming may be alternatively referred to as “spatial filtering.”

[0074] In response to different conditions, UE 404 may determine to switch beams, for example, between beams 402a-402h. The beam at UE 404 may be used for reception of downlink communications and / or transmission of uplink communications. In some examples, base station 402 may transmit a transmission that triggers beam switching of UE 404. The TCI state may include quasi-co-location (QCL) information, which the UE may use to derive timing / frequency errors and / or transmit / receive spatial filtering for transmitting / receiving signals. If the properties of the channel for transmitting symbols on one antenna port can be inferred from the channel for transmitting symbols on another antenna port, the two antenna ports are referred to as quasi-co-location. The base station may indicate the TCI state to the UE as a transmission configuration, which indicates the QCL relationship between a signal (e.g., a reference signal) and a signal to be transmitted / received. For example, the TCI state may indicate the QCL relationship between a DL RS in an RS set and a PDSCH / PDCCH DM-RS port. The TCI state may provide information about different beam selections used by the UE to transmit / receive various signals. For example, the base station 402 may indicate a TCI state change, and in response, the UE 404 may switch to a new beam according to the new TCI state indicated by the base station 402 (which may be otherwise referred to as performing beam switching).

[0075] In some wireless communication systems, such as wireless communication systems under the unified TCI framework, a joint DL / UL TCI state pool may be used for a joint DL / UL TCI state update for a beam indication. For example, the base station 402 may send a joint DL / UL TCI state pool to the UE 404. The UE 404 may determine to switch the transmit beam and / or receive beam based on the joint DL / UL TCI state. In some aspects, a TCI state pool for separate DL TCI state updates and UL TCI state updates may be used. In some aspects, the base station 402 may configure the TCI state pool using RRC signaling. In some aspects, the joint TCI may include or may not include UL specific parameters, such as UL PC / timing parameters, PLRS, panel related indications, etc. If the joint TCI includes UL specific parameters, these parameters may be used for UL transmissions in the DL and UL transmissions to which the joint TCI is applied. The TCI state under the unified TCI framework may be referred to as a "unified TCI state". The TCI state not under the unified TCI framework may be referred to as a "non-unified TCI state" and may be a DL TCI state.

[0076] Under the unified TCI framework, different types of unified TCI states can be indicated. For example, the first type of TCI can be a joint DL / UL TCI state to indicate a beam for at least one DL channel or RS and at least one UL channel or RS. The second type of TCI can be a separate DL TCI state (e.g., separate from the UL) to indicate a beam for at least one DL channel or RS. The second type of TCI can be a separate UL TCI state to indicate a beam for at least one UL channel / RS. Example RSs can be SSBs, tracking reference signals (TRS) and associated CSI-RS for tracking, CSI-RS for beam management, CSI-RS for CQI management, DM-RS associated with non-UE-dedicated reception on PDSCH, and a subset of the control resource set (CORESET) (which can be the full set), etc.

[0077] The TCI state may be defined to represent at least one source RS to provide a reference (eg, UE assumption) for determining a quasi co-location (QCL) or spatial filter. For example, the TCI state may define a QCL assumption between a source RS and a target RS.

[0078] The UE may receive a MAC control element (MAC-CE) activating one or more (e.g., one to eight) TCI state code points associated with one or more TCI states; subsequently receive downlink control information (DCI) indicating a TCI state code point associated with one of the one or more TCI states (which may alternatively be referred to as indicating a TCI state), and the UE may continue to use the one TCI state until a separate DCI indicating another TCI state is received. DCIs of different formats may provide different scheduling. For example, DCI format 0_0 may be a fallback format that may provide scheduling for a PUSCH in one cell. DCI format 0_1 ​​may be a non-fallback format that may provide scheduling for a PUSCH in one cell. DCI format 1_0 may be a fallback DCI format for allocating downlink resources for a PDSCH. DCI format 1_1 may be a non-fallback DCI format for allocating downlink resources for a PDSCH. DCI format 2_0 may be used to notify time slot format information (to dynamically change the time slot format). DCI format 2_1 may be used to notify PRBs and OFDM symbols in which the UE may assume that there are no transmissions intended for the UE. DCI format 2_2 may be used to send transmit power control (TPC) commands for PUCCH and PUSCH. DCI format 2_3 may be used to send a set of TPC commands for SRS transmission for one or more UEs. DCI format 2_4 may be used (such as dedicated to) provide cancellation of UL transmission. In some aspects, in order to indicate a TCI state code point representing (1) a pair of UL TCI state and DL TCI state or (2) a single DL TCI state, UL TCI state, or joint TCI state, DCI format 1_1 or format 1_2 may be used. In some aspects, in the case of DL assignment, in order to indicate the TCI state, the TCI field in the DCI may represent a TCI state ID.

[0079] Table 2 below may provide examples of channels / RSs associated with different types of TCI states (once activated):

[0080]

[0081]

[0082] Table 2

[0083] Prior to receiving a TCI state, the UE may assume that antenna ports of one DM-RS port group of the PDSCH are spatially quasi co-located (QCL) with the SSB determined in the initial access procedure for one or more of the following: Doppler shift, Doppler spread, average delay, delay spread, a set of spatial Rx parameters, etc. After receiving a new TCI state, the UE may assume that antenna ports of one DM-RS port group of the PDSCH of the serving cell are QCLed with RSs in the RS set for the QCL type parameter given by the indicated TCI state. Regarding QCL types, QCL type A may include Doppler shift, Doppler spread, average delay, and delay spread; QCL type B may include Doppler shift and Doppler spread; QCL type C may include Doppler shift and average delay; and QCL type D may include spatial Rx parameters (e.g., associated with beam information such as beamforming properties used to find a beam). In some aspects, the maximum number of TCI states may be 128.

[0084] To accommodate the situation where the beam indications for UL and DL are separated, two separate TCI states (one for DL ​​and the other for UL) may be utilized. For a separate DL TCI, the source reference signals in M ​​(M is an integer) TCIs may provide QCL information for at least UE-specific reception on PDSCH and for UE-specific reception on all CORESETs or a subset thereof in a CC. For a separate UL TCI, the source reference signals in N (N is an integer) TCIs provide references for determining UL transmit (TX) spatial filters at least for PUSCH based on dynamic grant or configuration grant and all dedicated PUCCH resources or a subset thereof in a CC.

[0085] In some aspects, the UL TX spatial filter may also be applied to all SRS resources in a resource set configured for antenna switching, codebook based (CB), or non-codebook based (NCB) UL transmission.

[0086] In some aspects, each of the following DL RSs may share the same indicated TCI state with UE-dedicated reception on PDSCH and UE-dedicated reception on all CORESETs or a subset thereof in a CC: CSI-RS resources for CSI, some or all CSI-RS resources for beam management, CSI-RS for tracking, and DM-RS associated with UE-dedicated reception on PDSCH and all CORESETs / subsets thereof. Some SRS resources or resource sets for beam management may share the same indicated TCI state with PUSCH, all dedicated PUCCH resources in a CC or a subset thereof, which are granted based on dynamic grants / configurations. In some wireless communication systems, several QCL rules and / or conditions may be defined. For example, a first rule and / or condition may define that the TCI of the DM-RS to the UE-dedicated PDSCH and PDCCH may not have SSB as the source RS to provide QCL type D information. A second and / or condition may define that the TCI to a certain DL RS (such as a CSI-RS) may have SSB as the source RS to provide QCL type D information. A third rule may define that TCI to some UL RSs (such as SRS) may have SSB as the source RS to provide spatial filter information.

[0087] In some wireless communication systems, in order to facilitate TCI state ID update and activation to provide QCL information for at least UE-specific PDCCH / PDSCH (e.g., common to UE-specific PDCCH and UE-specific PDSCH) or at least UL TX spatial filters for UE-specific PUSCH / PUCCH across configured CC / BWP sets (e.g., common to multiple PUSCH / PUCCH across configured CC / BWPs), several configurations may be provided. For example, an RRC-configured TCI state pool may be configured as part of the PDSCH configuration for each BWP or CC (such as in the PDSCH-Config parameter). The RRC-configured TCI state pool may not be present in the PDSCH configuration for each BWP / CC and may be replaced by a reference to the RRC-configured TCI state pool in the reference BWP / CC. For BWP / CCs where the PDSCH configuration includes a reference to the RRC-configured TCI state pool in the reference BWP / CC, the UE may apply the RRC-configured TCI state pool in the reference BWP / CC. When there is no BWP / CC identifier (ID) for a QCL type A or type D source RS (e.g., for a cell) in the QCL information of the TCI state (such as in the QCL information parameter), the UE may assume that the QCL type A or type D source RS is in the BWP / CC to which the TCI state applies. In addition, the UE may report UE capabilities indicating the maximum number of TCI state pools that the UE can support across BWPs and CCs in the frequency band.

[0088] In some aspects, the UE may receive a signal from the base station that is configured to trigger a TCI state change via, for example, a medium access control (MAC) control element (CE) (MAC-CE), a DCI, or a radio resource control (RRC) signal. The TCI state change may enable the UE to find the best or most appropriate UE receive beam corresponding to the TCI state indicated by the base station and switch to such a beam. Switching beams may allow enhanced or improved connectivity between the UE and the base station by ensuring that the transmitter and receiver communicate using the same configured set of beams. The DCI may include one or more TCI code points, which may each represent one or more TCI states.

[0089] In some aspects, a spatial relationship change (such as a spatial relationship update) may trigger the UE to switch beams. Beamforming may be applied to uplink channels (such as PUSCH, PUCCH, or SRS) or downlink channels (such as PDCCH, PDSCH, etc.). Beamforming may be based on configuring one or more spatial relationships between uplink signals and downlink signals. The spatial relationship indicates that the UE may use the same beam used to receive the corresponding downlink signal to send an uplink signal.

[0090] In some aspects, joint TCI for DL ​​and UL may be supported. The source reference signals in M ​​(M is a positive integer) TCIs may provide QCL information for at least PDSCH and UE-specific reception on all control resource sets (CORESET) in a component carrier (CC) or a subset thereof. The source reference signals in N (N is a positive integer) TCIs may provide a reference for determining a common UL TX spatial filter for at least PUSCH based on dynamic grant / configuration grant, all dedicated PUCCH resources in a CC or a subset thereof. The UL TX spatial filter may also be applied to all SRS resources in a resource set configured for antenna switching, codebook-based or non-codebook-based UL transmission.

[0091] In some wireless communication systems, two separate TCI states may be used, one for DL ​​and one for UL. For a separate DL TCI, the source reference signals in the M TCIs may provide QCL information for at least UE-specific reception on PDSCH and for UE-specific reception on all CORESETs or a subset thereof in the CC. For a separate UL TCI, the source reference signals in the N TCIs may provide a reference for determining a common UL TX spatial filter for at least PUSCH based on a dynamic grant / configuration grant, all dedicated PUCCH resources in the CC, or a subset thereof. The UL TX spatial filter may also be applied to all SRS resources in a resource set configured for antenna switching, codebook-based, or non-codebook-based UL transmission.

[0092] Figure 5 5 is a diagram 500 illustrating communication between a UE 502 and a network entity 504 (e.g., a base station). The network entity 504 may be a network node. The network node may be implemented as a converged base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, etc. The network entity may be implemented in a converged or monolithic base station architecture, or alternatively in a disaggregated base station architecture, and may include one or more of a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC.

[0093] like Figure 5, UE 502 may receive a MAC-CE 506 activating one or more (e.g., one to eight) TCI state code points associated with one or more TCI states. After receiving MAC-CE 506, UE 502 may then receive DCI 507 indicating one TCI state code point associated with at least one TCI state of the one or more TCI states (which may alternatively be referred to as indicating at least one TCI state). UE 502 may continue to use one TCI state until a separate DCI (e.g., 508) indicating another TCI state is received (in the case where one TCI state is a unified TCI state). In some aspects, DCI 508 may indicate a non-uniform TCI state, and UE 502 may not continue to use one TCI state until a separate DCI (e.g., 508) indicating another TCI state is received. In some aspects, DCI 508 may indicate a non-uniform TCI state or a unified TCI state. If DCI 508 indicates a unified TCI state, UE 502 may apply the TCI state indicated by DCI 508 to subsequent transmissions (which may or may not be scheduled by DCI 508) until another DCI is received. In some aspects, DCI 508 may be received and DCI 507 may not be present.

[0094] After receiving the DCI 508, the UE 502 may prepare an RX configuration for the TCI state indicated in the DCI 508, and such preparation may take time. In some aspects, the scheduling offset between the DCI 508 and the scheduled downlink transmission 514 (e.g., with scheduled PDSCH / AP-CSI) scheduled by the DCI 508 may be less than a threshold. In some aspects, the threshold may be based on the time available for the UE 502 to prepare the RX configuration for the TCI state indicated in the DCI 508. Because the scheduling offset is less than the threshold, the UE 502 may not be able to apply the TCI state indicated in the DCI 508 (and switch to the associated beam) for the scheduled downlink transmission 514. The terms "using the TCI state" and "applying the TCI state" may be used interchangeably. The default TCI state may be used by the UE 502 at 510 or by the network entity at 510 for the scheduled downlink transmission 514, respectively. As used herein, the term "default TCI state rule" or "default TCI state condition" may refer to one or more rules or conditions indicating which TCI state to use when the scheduling offset between the DCI indicating the TCI state and the scheduled downlink transmission is less than a threshold. In some aspects, the UE 502 may not be able to apply the TCI state indicated in the DCI 508 for the scheduled downlink transmission 514 scheduled by the DCI 508, because the scheduling offset is less than the threshold, so the UE 502 may apply the TCI state indicated in the DCI 507 or another TCI state. The threshold may correspond to the length of the beam application time (e.g., the duration between the ACK for the DCI and the time when the TCI becomes valid).

[0095] In some aspects, the default TCI state condition may indicate that the default TCI state is a TCI state associated with a CORESET ID (e.g., such as a lowest CORESET ID) in the last monitored time slot. In some aspects, the default TCI state condition may indicate that the default TCI state is a TCI state indicated by the DCI 507. In some aspects, the default TCI state condition may indicate that the default TCI state may be a TCI state indicated by the DCI 507 or a TCI state associated with a CORESET ID (e.g., such as a lowest CORESET ID) in the last monitored time slot based on the configuration 505 performed by the network entity 504. The TCI indicated by the DCI may take a certain time before it takes effect, and the later indicated TCI may replace the earlier indicated TCI after the later TCI takes effect. The default TCI is the indicated TCI that may be valid during the time slot in which the PDSCH is scheduled. The configuration 505 may be dynamically updated by the network entity 504. In some aspects, the default TCI state is a TCI state indicated by the DCI 507. In some aspects, the default TCI state condition can indicate that the default TCI state can be the TCI state indicated by the DCI 507 or the TCI state associated with the CORESET ID in the last monitored timeslot (e.g., such as the lowest CORESETID) based on one or more of the following: (1) information about the TCI state configured in the DCI 507, (2) whether the TCI state configured in the DCI 507 is for intra-cell or inter-cell, (3) whether the scheduled downlink transmission 514 is dedicated to the UE 502 or non-UE-dedicated, or (4) whether the scheduled downlink transmission 514 is for groupcast or broadcast.

[0096] In some aspects, the default TCI state condition may be based on whether the TCI state indicated in the DCI 507 is a unified TCI state for a CC or BWP or a non-uniform TCI state for a CC or BWP. In some aspects, whether the TCI state indicated in the DCI 507 is a unified TCI state or a non-uniform TCI state may be determined based on signaling from the network entity 504 or based on configuration. In some aspects, whether the TCI state indicated in the DCI 507 is a unified TCI state or a non-unified TCI state may be determined based on one or more of the following: (1) whether the unified TCI state has been configured in the RRC (e.g., a joint DL / UL or UL TCI state), (2) whether a flag indicating the use of the unified TCI state (e.g., a useUnifiedTCI flag) is configured with a CORESET for the UE 502 for a channel or a reference signal (RS), (3) whether a reference TCI state configuration has been configured in the PDSCH configuration for the UE 502 (e.g., and the CC is not configured with a TCI state pool), (4) whether a common updated CC list for the unified TCI state has been configured in the RRC and the CC is included in the CC list, (5) whether a common updated CC list for the legacy TCI state (non-unified TCI state) has been configured and the CC is included in the list. The determination may be based on a CC or BWP associated with the DCI 507 or another CC or BWP. In some aspects, the default TCI state condition may indicate that if the TCI state indicated in the DCI 507 is a unified TCI state, then the TCI state indicated in the DCI 507 may be the default TCI state. In some aspects, the default TCI state condition may indicate that if the TCI state indicated in the DCI 507 is a non-uniform TCI state, then the TCI state is associated with a CORESET ID (e.g., such as a lowest CORESETID) in the last monitored timeslot.

[0097] In some aspects, the default TCI state condition may be based on whether the scheduled downlink transmission 514 is for groupcast or broadcast, or whether the scheduled downlink transmission 514 is dedicated to the UE 502 or non-UE-specific. In some aspects, whether the scheduled downlink transmission 514 is dedicated to the UE 502 or non-UE-specific may be determined by the DCI format of the DCI 507 and the associated scrambled random network temporary identifier (RNTI). For example, if the DCI 507 is based on format 1_2 or format 1_2 and is scrambled with a cell RNTI, the scheduled downlink transmission 514 is dedicated to the UE 502. If the DCI 507 is based on another format (such as format 4_2) and is scrambled with a group RNTI, the scheduled downlink transmission 514 is non-UE-specific. In some aspects, based on the scheduled downlink transmission 514 being dedicated to the UE 502, the default TCI state condition may indicate that the TCI state indicated in the DCI 507 may be the default TCI state. In some aspects, based on the scheduled downlink transmission 514 not being dedicated to the UE 502, the default TCI state condition may indicate that the TCI state dedicated to the UE 502 may be the default TCI state, or the TCI state associated with the PDCCH transmission may be the default TCI state. In some aspects, based on the scheduled downlink transmission 514 not being dedicated to the UE 502, the default TCI state condition may indicate that the default TCI state may be the TCI state indicated by the DCI 507. In some aspects, based on the scheduled downlink transmission 514 not being dedicated to the UE 502, the default TCI state condition may indicate that the default TCI state may be the TCI state indicated by the DCI 507 based on the configuration 505 performed by the network entity 504 based on the default TCI state condition may indicate that the default TCI state may be the TCI state associated with the CORESET ID (e.g., such as the lowest CORESETID) in the last monitoring time slot. In some aspects, based on the scheduled downlink transmission 514 not being dedicated to the UE 502, the default TCI state condition may indicate that the default TCI state may be based on the configuration performed by the network entity 504. In some aspects, if the source RS corresponding to the TCI state of the PDSCH is not associated with the serving cell PCI, it is not desirable for the UE 502 to receive the non-UE dedicated channel.

[0098] In some aspects, based on the scheduled downlink transmission 514 being a broadcast or multicast PDSCH, the default TCI state condition may indicate that a default TCI state may be configured by the network entity 504 for the broadcast or multicast PDSCH (e.g., such that the default TCI state for different UEs in the broadcast or multicast may be the same).

[0099] In some aspects, the default TCI state condition may be based on whether the TCI state indicated by the DCI 507 is for intra-cell beam management (BM) or for inter-cell beam management (BM). For example, the TCI state indicated by the DCI 507 may be associated with a non-serving cell RS as its source RS, and the TCI state may be configured for inter-cell beam management (e.g., such as layer 1 or layer 2 mobility). In some aspects, based on the TCI state indicated by the DCI 507 being for intra-cell, the default TCI state condition may indicate that the default TCI state may be the TCI state associated with the CORESET ID (e.g., such as the lowest CORESET ID) in the last monitored timeslot. In some aspects, based on the TCI state indicated by the DCI 507 being for inter-cell, the default TCI state condition may indicate that the default TCI state may be the TCI state indicated by the DCI 507. In some aspects, whether the TCI state indicated by the DCI 507 is configured for inter-cell or intra-cell can be determined based on: (1) if no additional physical cell ID (PCI) is configured for the UE 502, then the TCI state indicated by the DCI 507 is configured for intra-cell, (2) if there is no additional PCI associated with the TCI state indicated by the DCI 507, then the TCI state indicated by the DCI 507 is configured for intra-cell, (3) if there is no additional PCI associated with the TCI state indicated by the DCI 507, then the TCI state indicated by the DCI 507 is configured for intra-cell, or (4) otherwise the TCI state indicated by the DCI 507 is configured for inter-cell.

[0100] In some aspects, as an example, the UE 502 may behave according to the following: if the scheduling offset is less than a threshold (e.g., which may be represented by a timeDurationForQCL parameter), if in each CC, the indicated TCI is associated with a PCI that is different from the serving cell PCI (i.e., between cells), then for CCs in each band, the default TCI state may be the TCI state associated with the CORESET ID in the last monitored timeslot (e.g., such as the lowest CORESET ID), and if the QCL type D characteristics of the default QCL assumptions for CCs in the band are different in the timeslots, then the default QCL assumption for the CC with the lowest ID in the band may be applied to all CCs in the band in that timeslot.

[0101] In some aspects, the default TCI state condition may indicate that the default TCI state is the TCI state associated with the CORESET ID (e.g., such as the lowest CORESET ID) in the last monitored timeslot. In some aspects, a group of CCs in a frequency band may be configured to share a common TCI configuration, and these CCs may also share the same TCI update signaling, and the UE 502 may apply the same TCI. Thus, it is possible that in different CCs, different default TCI states may be selected for different CCs based on the default TCI state condition based on when the last CORESET on the CC was monitored and which CORESETs were subsequently monitored. For example, on CC1, the last monitored timeslot is timeslot N, and CORESET1 is monitored, and on CC2, the last monitored timeslot is timeslot N-5, and CORESETs 2 and 3 are monitored. Thus, the TCI state of CORESET1 during timeslot N may be the default TCI state for CC1, and the TCI state of CORESET 2 during timeslot N-5 may be the default TCI state for CC2. In some aspects, the default TCI state condition may further indicate that the same default TCI state may be used for all CCs based on one of the following: (1) the default TCI state is selected using a CC with a CC ID (such as the lowest CC ID or a CC ID configured by the network entity 504), and the selected default TCI state is applied to all CCs, (2) the default TCI state is selected using the CC in which the CORESET was last monitored and the monitored CORESET ID was the lowest CORESET ID during the last monitoring occasion.

[0102] In some aspects, if the MAC-CE 506 includes a TCI state (such as DLorJointTCIState and / or UL-TCIState) that is mapped to one TCI code point but not to other TCI code points (e.g., the MAC-CE 506 activates one TCI state but not other TCI states), the UE 502 may apply the activated TCI state for one CC / DL BWP or for a set of CC / DL BWPs after a certain time (e.g., 3 milliseconds after the timeslot including the ACK for the MAC-CE), and the DCI 507 or DCI 508 may not indicate the TCI state.

[0103] Figure 6 600 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104, UE 502; device 804).

[0104] At 602, the UE may receive DCI indicating a first TCI state from a network entity at a first time. For example, the UE 502 may receive DCI 508 indicating a first TCI state from the network entity 504 at a first time. In some aspects, 602 may be performed by the TCI component 198.

[0105] At 604, the UE may apply a second TCI state or a third TCI state to receive the scheduled downlink transmission based on a difference between the first time and the second time associated with the scheduled downlink transmission being less than a threshold and based on a default TCI state condition. For example, the UE 502 may apply (e.g., at 510) a second TCI state (e.g., a TCI state associated with a CORESET ID) or a third TCI state (e.g., a TCI state associated with DCI 507) to receive the scheduled downlink transmission 514 based on a difference between the first time and the second time associated with the scheduled downlink transmission being less than a threshold and based on a default TCI state condition. In some aspects, 604 may be performed by the TCI component 198. In some aspects, the default TCI state condition may indicate that applying the second TCI state or the third TCI state is based on the CORESET ID. In some aspects, the CORESET ID: (1) is configured without signaling from a network entity, (2) is associated with a CC indicated by a network entity, or (3) is associated with a last monitored CC. In some aspects, the default TCI state condition may indicate that applying the third TCI state. In some aspects, the default TCI state condition indicates that if the third TCI state is a unified TCI state associated with a configured CC or BWP, the third TCI state is applied, and if the third TCI state is not a unified TCI state associated with a configured CC or BWP, the second TCI state or the third TCI state is applied based on the CORESET ID. In some aspects, the default TCI state condition may indicate that if the scheduled downlink transmission is dedicated to the UE as indicated by the DCI format associated with the DCI or the scrambled RNTI associated with the DCI, the third TCI state is applied. In some aspects, the scheduled downlink transmission is not dedicated to the UE as indicated by the DCI format associated with the DCI or the scrambled RNTI associated with the DCI, and wherein the default TCI state condition is RRC configured. In some aspects, the default TCI state condition may indicate that applying the second TCI state based on the scheduled downlink transmission is based on groupcast or broadcast, and wherein the second TCI state is associated with groupcast or broadcast. In some aspects, the default TCI state condition may be based on whether the third TCI state or the second TCI state may be associated with inter-cell or intra-cell. In some aspects, the third TCI state may be associated with inter-cell based on the third TCI state being associated with an RS associated with a non-serving cell. In some aspects, the third TCI state or the second TCI state may be associated with intra-cell based on one or more of the following: (1) the physical cell ID (PCI) is not configured with the third TCI state, (2) the PCI is not configured with an activated TCI state associated with the UE, or (3) the PCI is not configured separately in the RS.In some aspects, the UE may receive a default TCI state condition from a network entity, wherein the default TCI state condition may indicate that applying a second TCI state or a third TCI state is based on a CORESET ID or may indicate that applying a third TCI state. In some aspects, the UE may receive a MAC-CE (e.g., 506) activating a TCI state set before receiving the DCI, and the UE may apply the joint TCI state or the UL TCI state based on the MAC-CE including the joint TCI state or the UL TCI state in the TCI state set and not having an additional joint TCI state or an additional UL TCI state.

[0106] Figure 7 700 is a flow chart of a method of wireless communication. The method may be performed by a network entity (eg, base station 102, network entity 504, network entity 802, network entity 902).

[0107] At 702, a network entity may send DCI indicating a first TCI state for a UE at a first time. For example, network entity 504 may send DCI 508 indicating a first TCI state for UE 502 at a first time. In some aspects, 702 may be performed by TCI component 199.

[0108] At 704, the network entity may apply a second TCI state (e.g., a TCI state associated with a CORESET ID) or a third TCI state (e.g., a TCI state associated with DCI 507) to transmit the scheduled downlink transmission based on a difference between the first time and a second time associated with the scheduled downlink transmission being less than a threshold and based on a default TCI state condition to transmit the scheduled downlink transmission. For example, the network entity 504 may apply a second TCI state or a third TCI state (e.g., 512) to transmit the scheduled downlink transmission based on a difference between the first time and a second time associated with the scheduled downlink transmission being less than a threshold and based on a default TCI state condition. In some aspects, 704 may be performed by the TCI component 199. In some aspects, the default TCI state condition may indicate that applying the second TCI state or the third TCI state is based on the CORESET ID. In some aspects, the CORESET ID: (1) is configured without signaling from the network entity, (2) is associated with a CC indicated by the network entity, or (3) is associated with a last monitored CC. In some aspects, the default TCI state condition may indicate that applying the third TCI state. In some aspects, the default TCI state condition indicates that if the third TCI state is a unified TCI state associated with a configured CC or BWP, the third TCI state is applied, and if the third TCI state is not a unified TCI state associated with a configured CC or BWP, the second TCI state or the third TCI state is applied based on the CORESET ID. In some aspects, the default TCI state condition may indicate that if the scheduled downlink transmission is dedicated to the UE as indicated by the DCI format associated with the DCI or the scrambled RNTI associated with the DCI, the third TCI state is applied. In some aspects, the scheduled downlink transmission is not dedicated to the UE as indicated by the DCI format associated with the DCI or the scrambled RNTI associated with the DCI, and wherein the default TCI state condition is RRC configured. In some aspects, the default TCI state condition may indicate that applying the second TCI state based on the scheduled downlink transmission is based on groupcast or broadcast, and wherein the second TCI state is associated with groupcast or broadcast. In some aspects, the default TCI state condition may be based on whether the third TCI state or the second TCI state may be associated with inter-cell or intra-cell. In some aspects, the third TCI state may be associated with inter-cell based on the third TCI state being associated with an RS associated with a non-serving cell. In some aspects, the third TCI state or the second TCI state may be associated with intra-cell based on one or more of the following: (1) the physical cell ID (PCI) is not configured with the third TCI state, (2) the PCI is not configured with an activated TCI state associated with the UE, or (3) the PCI is not configured separately in the RS.In some aspects, the network entity may send a default TCI state condition for the UE, where the default TCI state condition may indicate that a second TCI state or a third TCI state is applied based on a CORESET ID or may indicate that a third TCI state is applied. In some aspects, the network entity may send a MAC-CE (e.g., 506) activating a TCI state set before receiving the DCI.

[0109] Figure 8800 is a diagram illustrating an example of a hardware implementation for an apparatus 804. The apparatus 804 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 804 may include a cellular baseband processor 824 (also referred to as a modem) coupled to one or more transceivers 822 (e.g., a cellular RF transceiver). The cellular baseband processor 824 may include on-chip memory 824'. In some aspects, the apparatus 804 may also include one or more subscriber identity module (SIM) cards 820 and an application processor 806 coupled to a secure digital (SD) card 808 and a screen 810. The application processor 806 may include on-chip memory 806'. In some aspects, the device 804 may also include a Bluetooth module 812, a WLAN module 814, a satellite system module 816 (e.g., a GNSS module), one or more sensor modules 818 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; a light detection and ranging (LIDAR), a radio-aided detection and ranging (RADAR), a sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 826, a power supply 830, and / or a camera 832. The Bluetooth module 812, the WLAN module 814, and the satellite system module 816 may include an on-chip transceiver (TRX) / receiver (RX). The cellular baseband processor 824 communicates with the UE 104 and / or with the RU associated with the network entity 802 through the transceiver 822 via one or more antennas 880. The cellular baseband processor 824 and the application processor 806 may each include a computer-readable medium / memory 824', 806', respectively. The additional memory module 826 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 824', 806', 826 may be non-transitory. The cellular baseband processor 824 and the application processor 806 are each responsible for general processing, including executing software stored on the computer-readable medium / memory. The software enables the cellular baseband processor 824 / application processor 806 to perform various functions described herein when executed by the cellular baseband processor 824 / application processor 806. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 824 / application processor 806 when executing the software. The cellular baseband processor 824 / application processor 806 may be a component of the UE 350 and may include at least one of the memory 360 and / or the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 804 may be a processor chip (modem and / or application) and include only the cellular baseband processor 824 and / or the application processor 806, and in another configuration, the device 804 may be the entire UE (e.g., see Figure 3350) and includes additional modules of device 804.

[0110] As discussed herein, the TCI component 198 may be configured to receive downlink control information (DCI) indicating at least a first transmission configuration indicator (TCI) state from a network entity at a first time. In some aspects, the TCI component 198 may be further configured to apply a second TCI state or a third TCI state to receive the scheduled downlink transmission based on a difference between the first time and a second time associated with the scheduled downlink transmission being less than a threshold and based on a default TCI state condition. The TCI component 198 may be within the cellular baseband processor 824, the application processor 806, or both the cellular baseband processor 824 and the application processor 806. The TCI component 198 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the foregoing. As shown, the device 804 may include a variety of components configured for various functions. In one configuration, the device 804 (and specifically, the cellular baseband processor 824 and / or the application processor 806) includes a component for receiving downlink control information (DCI) indicating at least a first transmission configuration indicator (TCI) state from a network entity at a first time. In some aspects, the device 804 may also include a component for applying a second TCI state or a third TCI state to receive a scheduled downlink transmission based on a difference between the first time and a second time associated with the scheduled downlink transmission being less than a threshold and based on a default TCI state condition. In some aspects, the device 804 may also include a component for receiving a default TCI state condition from the network entity, wherein the default TCI state condition may indicate that applying a second TCI state or a third TCI state is based on a control resource set (CORESET) identifier (ID) or may indicate applying a third TCI state. In some aspects, the device 804 may also include a component for receiving a medium access control (MAC) control element (MAC-CE) that activates a TCI state set before receiving the DCI. In some aspects, the apparatus 804 may also include means for applying a joint TCI state or a UL TCI state based on the MAC-CE containing a joint TCI state or a UL TCI state in a TCI state set and without an additional joint TCI state or an additional UL TCI state. These means may be the TCI component 198 of the apparatus 804 configured to perform the functions recited by the means. As described herein, the apparatus 804 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0111] Fig. 9 900 is a diagram illustrating an example of a hardware implementation for a network entity 902. The network entity 902 may be a BS, a component of a BS, or may implement BS functionality. The network entity 902 may include at least one of a CU 910, a DU 930, or a RU 940. For example, depending on the layer functionality handled by the component 199, the network entity 902 may include a CU 910; both the CU 910 and the DU 930; each of the CU 910, the DU 930, and the RU 940; the DU 930; both the DU 930 and the RU 940; or the RU 940. The CU 910 may include a CU processor 912. The CU processor 912 may include an on-chip memory 912'. In some aspects, the CU 910 may also include an additional memory module 914 and a communication interface 918. The CU 910 communicates with the DU 930 via a midhaul link such as an F1 interface. The DU 930 may include a DU processor 932. The DU processor 932 may include an on-chip memory 932'. In some aspects, the DU 930 may also include an additional memory module 934 and a communication interface 938. The DU 930 communicates with the RU 940 via a fronthaul link. The RU 940 may include a RU processor 942. The RU processor 942 may include an on-chip memory 942'. In some aspects, the RU 940 may also include an additional memory module 944, one or more transceivers 946, an antenna 980, and a communication interface 948. The RU 940 communicates with the UE 104. The on-chip memory 912', 932', 942' and the additional memory modules 914, 934, 944 may each be considered as a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each processor in the processors 912, 932, 942 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software enables the processor to perform various functions described herein when executed by the corresponding processor. The computer-readable medium / memory may also be used to store data that is manipulated by the processor when executing software.

[0112] As discussed herein, the TCI component 199 may be configured to transmit downlink control information (DCI) indicating at least a first transmission configuration indicator (TCI) state for a user equipment (UE) at a first time. In some aspects, the TCI component 199 may be further configured to apply a second TCI state or a third TCI state to transmit the scheduled downlink transmission based on a difference between the first time and a second time associated with the scheduled downlink transmission being less than a threshold and based on a default TCI state condition to transmit the scheduled downlink transmission. The TCI component 199 may be within one or more processors of one or more of the CU 910, DU 930, and RU 940. The TCI component 199 may be one or more hardware components that are specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination of these operations. The network entity 902 may include a variety of components configured for various functions. In one configuration, the network entity 902 includes a component for sending downlink control information (DCI) indicating at least a first transmission configuration indicator (TCI) state for a user equipment (UE) at a first time. In some aspects, the network entity 902 may also include a component for applying a second TCI state or a third TCI state to send a scheduled downlink transmission based on a difference between the first time and a second time associated with the scheduled downlink transmission being less than a threshold and based on a default TCI state condition to send a scheduled downlink transmission. In some aspects, the network entity 902 may also include a component for sending a default TCI state condition for the UE, wherein the default TCI state condition may indicate that the application of the second TCI state or the third TCI state is based on a control resource set (CORESET) identifier (ID) or may indicate that the application of the third TCI state. In some aspects, the network entity 902 may also include a component for sending a medium access control (MAC) control element (MAC-CE) for activating a TCI state set before receiving the DCI. These components may be a TCI component 199 of the network entity 902 configured to perform the functions recorded by the component. As described herein, the network entity 902 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, a component may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by that component.

[0113] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. Further, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not limited to the specific order or hierarchy provided.

[0114] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when ..." and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ...", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data can be directly received / sent between the first device and the second device, or data can be indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will be known later to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be interpreted as a functional component unless the element is explicitly recorded using the phrase "component for..."

[0115] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0116] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0117] Aspect 1 is a device for performing wireless communications at a user equipment (UE), the device comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receive downlink control information (DCI) indicating a first transmission configuration indicator (TCI) state from a network entity at a first time; and apply a second TCI state or a third TCI state to receive the scheduled downlink transmission based on a difference between the first time and a second time associated with a scheduled downlink transmission and based on a default TCI state condition, wherein the difference is less than a threshold.

[0118] Aspect 2 is an apparatus according to aspect 1, wherein the default TCI state condition indicates that applying the second TCI state or the third TCI state is based on a control resource set (CORESET) identifier (ID).

[0119] Aspect 3 is an apparatus according to any one of Aspects 1 to 2, wherein the CORESET ID: (1) is configured without signaling from the network entity, (2) is associated with a component carrier (CC) indicated by the network entity, or (3) is associated with a most recently monitored CC.

[0120] Aspect 4 is an apparatus according to any one of aspects 1 to 3, wherein the default TCI state condition indicates applying the third TCI state, wherein the third TCI state is indicated before the DCI.

[0121] Aspect 5 is an apparatus according to any one of Aspects 1 to 4, wherein the at least one processor is configured to: receive the default TCI state condition from the network entity, wherein the default TCI state condition indicates that the second TCI state or the third TCI state is applied based on a control resource set (CORESET) identifier (ID) or indicates that the third TCI state is applied.

[0122] Aspect 6 is an apparatus according to any one of aspects 1 to 5, wherein the default TCI state condition indicates that if the third TCI state is a unified TCI state associated with a configured component carrier (CC) or a configured bandwidth part (BWP), the third TCI state is applied, and if the third TCI state is not the unified TCI state associated with the configured CC or the configured BWP, the second TCI state or the third TCI state is applied based on a control resource set (CORESET) identifier (ID), and wherein the third TCI state is applied based on at least one of the following: The state is the unified TCI state: (1) whether the unified TCI state is configured in a radio resource control (RRC), (2) whether a flag indicating the unified TCI state is configured for a channel or reference signal associated with the CORESET, (3) whether a reference TCI state configuration is configured in a physical downlink shared channel configuration (PDSCH) for the UE, (4) whether a first CC list for common update of the unified TCI state is configured in the RRC, or (5) whether a second CC list for common update of a non-unified TCI state including the CC is configured.

[0123] Aspect 7 is an apparatus according to any one of Aspects 1 to 6, wherein the default TCI state condition indicates that the third TCI state is applied if the scheduled downlink transmission is dedicated to the UE as indicated by a DCI format associated with the DCI or a scrambled random network temporary identifier (RNTI) associated with the DCI.

[0124] Aspect 8 is an apparatus according to any one of Aspects 1 to 7, wherein the scheduled downlink transmission is not dedicated to the UE, as indicated by a DCI format associated with the DCI or a scrambled random network temporary identifier (RNTI) associated with the DCI, and wherein the default TCI state condition is radio resource control (RRC) configured.

[0125] Aspect 9 is an apparatus according to any one of Aspects 1 to 8, wherein the default TCI state condition indicates that applying the second TCI state based on the scheduled downlink transmission is based on multicast or broadcast, and wherein the second TCI state is associated with the multicast or the broadcast.

[0126] Aspect 10 is an apparatus according to any one of Aspects 1 to 9, wherein the default TCI state condition is based on whether the third TCI state or the second TCI state is associated with inter-cell beam management or intra-cell beam management.

[0127] Aspect 11 is an apparatus according to any one of Aspects 1 to 10, wherein the third TCI state is associated with the inter-cell beam management based on that the third TCI state is associated with a reference signal (RS) associated with a non-serving cell.

[0128] Aspect 12 is an apparatus according to any one of Aspects 1 to 11, wherein the third TCI state or the second TCI state is associated with the intra-cell beam management based on one or more of the following: (1) the physical cell ID (PCI) is not configured with the third TCI state, (2) the PCI is not configured with an activated TCI state associated with the UE, or (3) the PCI is not separately configured in a reference signal (RS).

[0129] Aspect 13 is an apparatus according to any one of Aspects 1 to 12, wherein the DCI indicates the third TCI state in the TCI state set, and wherein the at least one processor is further configured to: receive a medium access control (MAC) control element (MAC-CE) activating the TCI state set before receiving the DCI; and apply the joint TCI state or the UL TCI state based on the MAC-CE containing the joint TCI state or the UL TCI state in the TCI state set and without an additional joint TCI state or an additional UL TCI state.

[0130] Aspect 14 is an apparatus according to any one of aspects 1 to 13, the apparatus further comprising a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to receive the DCI.

[0131] Aspect 15 is a device for performing wireless communications at a network entity, the device comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: send downlink control information (DCI) indicating a first transmission configuration indicator (TCI) state for a user equipment (UE) at a first time; and apply a second TCI state or a third TCI state to send the scheduled downlink transmission based on a difference between the first time and a second time associated with a scheduled downlink transmission and based on a default TCI state condition, wherein the difference is less than a threshold.

[0132] Aspect 16 is an apparatus according to aspect 15, wherein the default TCI state condition indicates that applying the second TCI state or the third TCI state is based on a control resource set (CORESET) identifier (ID).

[0133] Aspect 17 is an apparatus according to any one of aspects 15 to 16, wherein the CORESET ID: (1) is configured without signaling from the network entity, (2) is associated with a component carrier (CC) indicated by the network entity, or (3) is associated with a most recently monitored CC.

[0134] Aspect 18 is an apparatus according to any one of aspects 15 to 17, wherein the default TCI state condition indicates applying the third TCI state, wherein the third TCI state is indicated before the DCI.

[0135] Aspect 19 is an apparatus according to any one of Aspects 15 to 18, wherein the at least one processor is configured to: send the default TCI state condition for the UE, wherein the default TCI state condition indicates that the second TCI state or the third TCI state is applied based on a control resource set (CORESET) identifier (ID) or indicates that the third TCI state is applied.

[0136] Aspect 20 is an apparatus according to any one of aspects 15 to 19, wherein the default TCI state condition indicates that if the third TCI state is a unified TCI state associated with a configured component carrier (CC) or a configured bandwidth part (BWP), the third TCI state is applied, and if the third TCI state is not the unified TCI state associated with the configured CC or the configured BWP, the second TCI state or the third TCI state is applied based on a control resource set (CORESET) identifier (ID), and wherein the third TCI state is applied based on at least one of the following: The state is the unified TCI state: (1) whether the unified TCI state is configured in radio resource control (RRC), (2) whether a flag indicating the unified TCI state is configured for a channel or reference signal associated with the CORESET, (3) whether a reference TCI state configuration is configured in a physical downlink shared channel configuration (PDSCH) for the UE, (4) whether a first CC list for common update of the unified TCI state is configured in the RRC, or (5) whether a second CC list for common update of a non-unified TCI state including the CC is configured.

[0137] Aspect 21 is an apparatus according to any one of Aspects 15 to 20, wherein the default TCI state condition indicates that the third TCI state is applied if the scheduled downlink transmission is dedicated to the UE as indicated by a DCI format associated with the DCI or a scrambled random network temporary identifier (RNTI) associated with the DCI.

[0138] Aspect 22 is an apparatus according to any one of Aspects 15 to 21, wherein the scheduled downlink transmission is not dedicated to the UE, as indicated by a DCI format associated with the DCI or a scrambled random network temporary identifier (RNTI) associated with the DCI, and wherein the default TCI state condition is radio resource control (RRC) configured.

[0139] Aspect 23 is an apparatus according to any one of Aspects 15 to 22, wherein the default TCI state condition indicates that applying the second TCI state based on the scheduled downlink transmission is based on multicast or broadcast, and wherein the second TCI state is associated with the multicast or the broadcast.

[0140] Aspect 24 is an apparatus according to any one of Aspects 15 to 22, wherein the default TCI state condition is based on whether the third TCI state or the second TCI state is associated with inter-cell beam management or intra-cell beam management.

[0141] Aspect 25 is an apparatus according to any one of Aspects 15 to 24, wherein the third TCI state is associated with the inter-cell beam management based on that the third TCI state is associated with a reference signal (RS) associated with a non-serving cell.

[0142] Aspect 26 is an apparatus according to any one of Aspects 15 to 25, wherein the third TCI state or the second TCI state is associated with the intra-cell beam management based on one or more of the following: (1) a physical cell ID (PCI) is not configured with the third TCI state, (2) the PCI is not configured with an activated TCI state associated with the UE, or (3) the PCI is not configured separately in a reference signal (RS).

[0143] Aspect 27 is an apparatus according to any one of Aspects 15 to 26, wherein the DCI indicates the third TCI state in the TCI state set, and wherein the at least one processor is further configured to: send a medium access control (MAC) control element (MAC-CE) activating the TCI state set before sending the DCI.

[0144] Aspect 28 is an apparatus according to any one of aspects 15 to 27, the apparatus further comprising a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to transmit the DCI.

[0145] Aspect 29 is a method for wireless communication implementing any one of aspects 1 to 14.

[0146] Aspect 30 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 14.

[0147] Aspect 31 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 14.

[0148] Aspect 32 is a method for implementing wireless communication of any one of aspects 15 to 28.

[0149] Aspect 33 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 15 to 28.

[0150] Aspect 34 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 15 to 28.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving downlink control information (DCI) indicating a first transmission configuration indicator (TCI) state from a network entity at a first time; and Applying a second TCI state or a third TCI state to receive the scheduled downlink transmission based on a difference between the first time and a second time associated with the scheduled downlink transmission and based on a default TCI state condition, wherein the difference is less than a threshold.

2. The apparatus according to claim 1, wherein the default TCI state condition indicates that applying the second TCI state or the third TCI state is based on a control resource set (CORESET) identifier (ID).

3. The apparatus of claim 2, wherein the CORESET ID: (1) is configured without signaling from the network entity, (2) is associated with a component carrier (CC) indicated by the network entity, or (3) is associated with a most recently monitored CC.

4. The apparatus of claim 1, wherein the default TCI state condition indicates applying the third TCI state, wherein the third TCI state is indicated before the DCI.

5. The apparatus of claim 1 , wherein the at least one processor is configured to: The default TCI state condition is received from the network entity, wherein the default TCI state condition indicates that applying the second TCI state or the third TCI state is based on a control resource set (CORESET) identifier (ID) or indicates applying the third TCI state.

6. The apparatus of claim 1 , wherein the default TCI state condition indicates that if the third TCI state is a unified TCI state associated with a configured component carrier (CC) or a configured bandwidth part (BWP), the third TCI state is applied, and if the third TCI state is not the unified TCI state associated with the configured CC or the configured BWP, the second TCI state or the third TCI state is applied based on a control resource set (CORESET) identifier (ID), and wherein the third TCI state is the unified TCI state based on at least one of: (1) whether the unified TCI state is configured in a radio resource control (RRC), (2) whether a flag indicating the unified TCI state is configured for a channel or a reference signal associated with the CORESET, (3) whether the reference TCI state configuration is configured in the physical downlink shared channel configuration (PDSCH) for the UE, (4) whether the first CC list for public update of the unified TCI state is configured in the RRC, or (5) whether the second CC list for public update of the non-uniform TCI state including the CC is configured.

7. The apparatus of claim 1, wherein the default TCI state condition indicates that the third TCI state is applied if the scheduled downlink transmission is dedicated to the UE as indicated by a DCI format associated with the DCI or a scrambled random network temporary identifier (RNTI) associated with the DCI.

8. The apparatus of claim 1 , wherein the scheduled downlink transmission is not dedicated to the UE as indicated by a DCI format associated with the DCI or a scrambled random network temporary identifier (RNTI) associated with the DCI, and wherein the default TCI state condition is radio resource control (RRC) configured.

9. The apparatus of claim 1, wherein the default TCI state condition indicates that applying the second TCI state based on the scheduled downlink transmission is based on multicast or broadcast, and wherein the second TCI state is associated with the multicast or the broadcast.

10. The apparatus of claim 1, wherein the default TCI state condition is based on whether the third TCI state or the second TCI state is associated with inter-cell beam management or intra-cell beam management.

11. The apparatus of claim 10, wherein the third TCI state is associated with the inter-cell beam management based on the third TCI state being associated with a reference signal (RS) associated with a non-serving cell.

12. An apparatus according to claim 10, wherein the third TCI state or the second TCI state is associated with the intra-cell beam management based on one or more of the following: (1) a physical cell ID (PCI) is not configured with the third TCI state, (2) the PCI is not configured with an activated TCI state associated with the UE, or (3) the PCI is not separately configured in a reference signal (RS).

13. The apparatus of claim 1 , wherein the DCI indicates the third TCI state in a TCI state set, and wherein the at least one processor is further configured to: receiving a medium access control (MAC) control element (MAC-CE) activating the TCI state set before receiving the DCI; and The joint TCI state or the UL TCI state is applied based on that the MAC-CE includes a joint TCI state or a UL TCI state in the TCI state set and has no additional joint TCI state or additional UL TCI state.

14. The apparatus of claim 1, further comprising a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to receive the DCI.

15. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: transmitting downlink control information (DCI) indicating a first transmission configuration indicator (TCI) state for a user equipment (UE) at a first time; and Applying a second TCI state or a third TCI state to send the scheduled downlink transmission based on a difference between the first time and a second time associated with the scheduled downlink transmission and based on a default TCI state condition, wherein the difference is less than a threshold.

16. The apparatus of claim 15, wherein the default TCI state condition indicates that applying the second TCI state or the third TCI state is based on a control resource set (CORESET) identifier (ID).

17. The apparatus of claim 16, wherein the CORESETID: (1) is configured without signaling from the network entity, (2) is associated with a component carrier (CC) indicated by the network entity, or (3) is associated with a most recently monitored CC.

18. The apparatus of claim 15, wherein the default TCI state condition indicates applying the third TCI state, wherein the third TCI state is indicated before the DCI.

19. The apparatus of claim 15, wherein the at least one processor is configured to: The default TCI state condition for the UE is sent, wherein the default TCI state condition indicates that applying the second TCI state or the third TCI state is based on a control resource set (CORESET) identifier (ID) or indicates applying the third TCI state.

20. The apparatus of claim 15, wherein the default TCI state condition indicates that if the third TCI state is a unified TCI state associated with a configured component carrier (CC) or a configured bandwidth part (BWP), the third TCI state is applied, and if the third TCI state is not the unified TCI state associated with the configured CC or the configured BWP, the second TCI state or the third TCI state is applied based on a control resource set (CORESET) identifier (ID), and wherein the third TCI state is the unified TCI state based on at least one of: (1) whether the unified TCI state is configured in a radio resource control (RRC), (2) whether a flag indicating the unified TCI state is configured for a channel or a reference signal associated with the CORESET, (3) whether the reference TCI state configuration is configured in the physical downlink shared channel configuration (PDSCH) for the UE, (4) whether the first CC list for public update of the unified TCI state is configured in the RRC, or (5) whether the second CC list for public update of the non-uniform TCI state including the CC is configured.

21. The apparatus of claim 15, wherein the default TCI state condition indicates that the third TCI state is applied if the scheduled downlink transmission is dedicated to the UE as indicated by a DCI format associated with the DCI or a scrambled random network temporary identifier (RNTI) associated with the DCI.

22. The apparatus of claim 15, wherein the scheduled downlink transmission is not dedicated to the UE as indicated by a DCI format associated with the DCI or a scrambled random network temporary identifier (RNTI) associated with the DCI, and wherein the default TCI state condition is radio resource control (RRC) configured.

23. The apparatus of claim 15, wherein the default TCI state condition indicates that applying the second TCI state based on the scheduled downlink transmission is based on a multicast or a broadcast, and wherein the second TCI state is associated with the multicast or the broadcast.

24. The apparatus of claim 15, wherein the default TCI state condition is based on whether the third TCI state or the second TCI state is associated with inter-cell beam management or intra-cell beam management.

25. The apparatus of claim 24, wherein the third TCI state is associated with the inter-cell beam management based on the third TCI state being associated with a reference signal (RS) associated with a non-serving cell.

26. An apparatus according to claim 24, wherein the third TCI state or the second TCI state is associated with the intra-cell beam management based on one or more of the following: (1) a physical cell ID (PCI) is not configured with the third TCI state, (2) the PCI is not configured with an activated TCI state associated with the UE, or (3) the PCI is not separately configured in a reference signal (RS).

27. The apparatus of claim 15, wherein the DCI indicates the third TCI state in a TCI state set, and wherein the at least one processor is further configured to: A medium access control (MAC) control element (MAC-CE) activating the TCI state set is sent before sending the DCI.

28. The apparatus of claim 15, further comprising a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to transmit the DCI.

29. A method of wireless communication at a user equipment (UE), the method comprising: receiving, at a first time, downlink control information (DCI) from a network entity indicating at least a first transmit configuration indicator (TCI) state; as well as Applying a second TCI state or a third TCI state to receive the scheduled downlink transmission based on a difference between the first time and a second time associated with the scheduled downlink transmission and based on a default TCI state condition, wherein the difference is less than a threshold.

30. A method for wireless communication at a network entity, the method comprising: transmitting downlink control information (DCI) indicating at least a first transmission configuration indicator (TCI) state for a user equipment (UE) at a first time; as well as Applying a second TCI state or a third TCI state to send the scheduled downlink transmission based on a difference between the first time and a second time associated with the scheduled downlink transmission and based on a default TCI state condition, wherein the difference is less than a threshold.

Images