Determining last DCI for TCI indication DCI

Abstract

A method and apparatus for determining the last DCI for TCI indication. The apparatus receives one or more DCIs, the one or more DCIs including TCI code points for one or more component carriers. The apparatus transmits a PUCCH, the PUCCH including an ACK or a NACK corresponding to each of the one or more DCIs. The apparatus determines, from the one or more DCIs, at least one DCI including an effective TCI indication for each of the one or more component carriers. The apparatus applies the TCI code point to the one or more component carriers based at least on the at least one DCI including the valid TCI indication.

Description

Technical Field

[0001] The present disclosure relates generally to communication systems, and more particularly to a configuration for determining a last downlink control information (DCI) indicated by a transmission configuration indicator (TCI). Background Art

[0002] 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.

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5GNR is part of the continuous 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 communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0004] 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 neither identifies the key or important elements of all aspects, nor describes 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.

[0005] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an apparatus at a UE. The apparatus may be a processor and / or a modem at a UE or the UE itself. The apparatus receives one or more downlink control indicators (DCIs), the one or more DCIs including a transmission configuration indicator (TCI) code point for one or more component carriers. The apparatus sends a physical uplink control channel (PUCCH), the PUCCH including an acknowledgment (ACK) or a negative acknowledgment (NACK) corresponding to each of the one or more DCIs. The apparatus determines from the one or more DCIs at least one DCI including a valid TCI indication for each of the one or more component carriers. The apparatus applies the TCI code point to the one or more component carriers based at least on the at least one DCI including the valid TCI indication.

[0006] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a network entity. The apparatus may be a processor and / or a modem at a network entity or the network entity itself. The apparatus outputs one or more downlink control indicators (DCIs), the one or more DCIs including a transmission configuration indicator (TCI) code point for one or more component carriers. The apparatus obtains a physical uplink control channel (PUCCH), the PUCCH including an acknowledgment (ACK) or a negative acknowledgment (NACK) corresponding to each of the one or more DCIs, wherein the PUCCH indicates a TCI code point applied to the one or more component carriers based at least on at least one DCI including a valid TCI indication.

[0007] 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 indicate only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0010] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

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

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

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

[0014] FIG. 4A to FIG. 4B is a diagram illustrating an example of applying TCI.

[0015] Figure 5 is a call flow diagram of signaling between UE and base station.

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

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

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

[0019] Fig. 9 is a flow chart of a wireless communication method.

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

[0021] In wireless communications, DCI including TCI indication needs to be acknowledged before TCI is applied. However, in some cases, there may be multiple ACKs in the PUCCH that may correspond to multiple DCIs, each of which may include TCI indication. The UE needs to determine which of the multiple DCIs includes a valid TCI indication.

[0022] Aspects presented herein provide configurations for determining a DCI including a valid TCI indication.For example, a UE may transmit a PUCCH including multiple ACKs corresponding to multiple DCIs, wherein the UE may determine a DCI including a valid TCI indication from the multiple DCIs.

[0023] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in 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 cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0024] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus 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 such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0025] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes 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, gating 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, executables, threads of execution, procedures, functions, or any combination thereof.

[0026] 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. As an 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.

[0027] 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 / or 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 may 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 actual settings, the equipment combined 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 various 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.

[0028] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR 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) performing base station functions can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NRBS, 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.

[0029] 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).

[0030] 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 used 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 functions across two or more units at various physical locations, as well as virtually distributing the functions of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0031] 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 disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated 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.

[0032] 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 referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface 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 or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units via a wireless transmission medium.

[0033] 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 that is 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 signal transmission.

[0034] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 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 and demodulation, etc.) at least in part according to a functional split such as those 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.

[0035] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the 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 at least in part 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 specific 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, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0036] 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 to instantiate 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. In addition, 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 .

[0037] 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 communicate 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.

[0038] 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 adjust RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0039] 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 Yx MHz (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. These 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 for DL ​​compared to UL). Component carriers 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).

[0040] 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 sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). 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.

[0041] 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.

[0042] 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 referred to (interchangeably) 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, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) that is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0043] 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 thus 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.

[0044] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, 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 specified, if the term "millimeter wave" is used herein, 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.

[0045] 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 of the base station 102 may be the same or may not be the same. The transmit direction and receive direction of the UE 104 may be the same or may not be the same.

[0046] 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 transmit receive point (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 decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0047] 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, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may determine the location of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, position estimation, and optional speed calculation based on these measurements. Signal measurements may be performed by UE 104 and / or 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 / positioning 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.

[0048] 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 computers, 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 terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device cluster arrangement. One or more of these devices may access the network collectively and / or individually.

[0049] See again Figure 1 In certain aspects, the UE 104 may include a TCI component 198 configured to: receive one or more downlink control indicators (DCIs) including a transmission configuration indicator (TCI) code point for one or more component carriers; send a physical uplink control channel (PUCCH) including an acknowledgement (ACK) or a negative acknowledgement (NACK) corresponding to each of the one or more DCIs; determine at least one DCI from the one or more DCIs including a valid TCI indication for each of the one or more component carriers; and apply the TCI code point to the one or more component carriers based at least on the at least one DCI including the valid TCI indication.

[0050] See again Figure 1 In certain aspects, the base station 102 may include a TCI component 199 configured to: output one or more downlink control indicators (DCIs), the one or more DCIs including a transmission configuration indicator (TCI) code point for one or more component carriers; and obtain a physical uplink control channel (PUCCH), the PUCCH including an acknowledgement (ACK) or a negative acknowledgement (NACK) corresponding to each of the one or more DCIs, wherein the PUCCH indicates the TCI code point applied to the one or more component carriers based at least on at least one DCI including a valid TCI indication.

[0051] 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.

[0052] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram 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), where 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), where 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 with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-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). Note that the following description also applies to the 5G NR frame structure as TDD.

[0053] FIG. 2A to FIG. 2DThe frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (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 normal or extended. For a normal CP, each time slot may include 14 symbols, and for an 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 (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The numerology defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled with 1 / SCS.

[0054]

[0055] Table 1: Parameter set, SCS and CP

[0056] 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. Thus, 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 is provided for a normal CP with 14 symbols per slot and a parameter set μ=2 with 4 slots per subframe. 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 may have a specific parameter set and CP (normal or extended).

[0057] A resource grid may be used to represent the 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 number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0058] 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 one 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).

[0059] 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 identification. 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 system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent over the PBCH (such as the system information block (SIB)), and paging messages.

[0060] 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 comb structures in the comb structure. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0061] 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.

[0062] Figure 3375. The Controller / Processor 375 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 transfer 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.

[0063] 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) coding / 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 coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together 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 from reference signals and / or channel state 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 for transmission using a corresponding spatial stream.

[0064] 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 symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates 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 base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0065] 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.

[0066] 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.

[0067] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select the 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.

[0068] 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 respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0069] 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.

[0070] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The TCI component 198 combines various aspects.

[0071] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The TCI component 199 combines various aspects.

[0072] In wireless communications, DCI including a TCI indication needs to be acknowledged before applying the TCI. However, in some cases, there may be multiple ACKs in the PUCCH that may correspond to multiple DCIs, each of which may include a TCI indication. In some cases, the base station may update the TCI indication from time to time so that different DCIs may include different TCI indications. The UE needs to determine which of the multiple DCIs includes a valid TCI indication.

[0073] Aspects presented herein provide configurations for determining a DCI that includes a valid TCI indication. For example, a UE may send a PUCCH that includes multiple ACKs corresponding to multiple DCIs, where the UE may determine the DCI that includes a valid TCI indication from the multiple DCIs. At least one advantage of the present disclosure is that, in the case where the PUCCH includes multiple ACKs for multiple TCI indications, the UE may be configured to determine which DCI from one or more DCIs includes a valid TCI indication.

[0074] In some cases, when the UE sends a PUCCH including one or more ACK / NACKs for multiple DCIs, each of which includes a TCI code point, the UE may be configured to apply TCI based on at least one of the following: the last DCI in time for each component carrier, or the last DCI in time for each direction of each component carrier.

[0075] In the case where the UE applies TCI based on the last DCI in time for each component carrier, the UE may identify the last DCI in time for each component carrier. The UE may then apply the TCI code point indicated in the identified last DCI to each component carrier. In such a case, the TCI in the TCI code point may include at least one of a joint TCI, an uplink TCI, or a downlink TCI. Figure 4A400, a UE may receive multiple DCIs (e.g., DCI1 402, DCI2 404, DCI3 406, DCI4 408) and may send PUCCHs corresponding to the multiple DCIs (e.g., 410). The UE may apply TCI to each component carrier (CC) based on the last DCI in time. Figure 4A In the example of , the UE may apply TCI3 corresponding to DCI3 to the first CC, and may apply TCI4 corresponding to DCI4 to the second CC. TCI3 and TCI4 may be applied because they are associated with the last DCI of the respective component carriers in time.

[0076] In the case where the UE applies TCI based on the last DCI in time for each direction of each component carrier, the UE may identify the last DCI in time of TCI applicable to the downlink for each component carrier (if any), and the last DCI in time of TCI applicable to the uplink for each component carrier (if any). The UE may then apply the TCI indicated in the identified last DCI to each component carrier. In some aspects, the TCI applicable to the downlink may include a joint TCI or a downlink TCI. In some aspects, the TCI applicable to the uplink may include a joint TCI or a downlink TCI. Reference Figure 4B 420, a UE may receive multiple DCIs (e.g., DCI1 422, DCI2 424, DCI3 426, DCI4 428, DCI5 430, DCI6 432) and may send PUCCHs (e.g., 434) corresponding to the multiple DCIs. The UE may apply TCI to each direction (e.g., uplink or downlink) of each component carrier based on the last DCI in time. Figure 4B In the example of , the UE may apply TCI1 to the uplink of the first component carrier corresponding to DCI1. The UE may apply TCI6 to the uplink of the second component carrier corresponding to DCI6. The UE may apply TCI5 to the downlink of the first component carrier corresponding to DCI5. The UE may apply TCI2 to the downlink of the second component carrier corresponding to DCI2. TCI1 and TCI6 are applicable to the uplink because they are associated with the last DCI in time for the uplink of their respective component carriers. TCI2 and TCI5 are applicable to the downlink because they are associated with the last DCI in time for the downlink of their respective component carriers.

[0077] When the UE is about to send the last symbol of the PUCCH with HARQ-ACK information corresponding to the last DCI in time carrying the TCI state indication and no DL assignment, or corresponding to PDSCH scheduling by DCI carrying the TCI state indication for each component carrier, and if the indicated TCI state is different from the previously indicated TCI state, the indicated DLorJointTCIState or UL-TCIstate shall be applied starting from the first time slot at least a number of symbols (e.g., the number of symbols is determined by BeamAppTime_r17) after the last symbol of the PUCCH. Both the first time slot and the number of BeamAppTime_r17 symbols are determined on the carrier with the smallest SCS among the carriers to which the beam indication is applied.

[0078] Figure 5 5 is a call flow diagram 500 of signaling between a UE 502 and a base station 504. The base station 504 may be configured to provide at least one cell. The UE 502 may be configured to communicate with the base station 504. For example, in Figure 1 In the context of , base station 504 may correspond to base station 102. In addition, UE 502 may correspond to at least UE 104. In another example, in Figure 3 In the context of , base station 504 may correspond to base station 310 and UE 502 may correspond to UE 350.

[0079] At 506, the base station 504 may output one or more DCIs including TCI code points for one or more component carriers. The base station 504 may output the one or more DCIs to the UE 502. The UE 502 may receive the one or more DCIs including TCI code points for the one or more component carriers from the base station 504. In some aspects, the TCI code points may include at least one of a joint TCI, an uplink TCI, or a downlink TCI.

[0080] At 508, UE 502 may send a PUCCH including an ACK or NACK corresponding to each of the one or more DCIs. UE 502 may send the PUCCH including the ACK or NACK to base station 504. Base station 504 may obtain the PUCCH including the ACK or NACK corresponding to each of the one or more DCIs from UE 502.

[0081] At 510, the UE 502 may determine at least one DCI including a valid TCI indication. The UE may determine at least one DCI from the one or more DCIs, the at least one DCI including a valid TCI indication for each of the one or more component carriers.

[0082] In some aspects, the UE 502 may identify the last DCI in time for each of the one or more component carriers to determine at least one DCI including a valid DCI from the one or more DCIs, e.g., at 512. The TCI code point associated with the last DCI may be applicable to each component carrier. In some aspects, the TCI code point may include at least one of a joint TCI, an uplink TCI, or a downlink TCI.

[0083] In some aspects, for example at 514, to determine at least one DCI including a valid DCI from the one or more DCIs, the UE 502 may identify the last DCI in time for each direction of each component carrier of the one or more component carriers. The TCI code point associated with the last DCI may be applicable to each component carrier. In some aspects, the last DCI in time may include the last DCI of the downlink applicable TCI for each component carrier. The downlink applicable TCI may include at least one of a joint TCI or a downlink TCI. In some aspects, the last DCI in time may include the last DCI of the uplink applicable TCI for each component carrier. The uplink applicable TCI may include at least one of a joint TCI or an uplink TCI.

[0084] At 516, the UE 502 may apply the TCI code point to the one or more component carriers. The UE may apply the TCI code point to the one or more component carriers based at least on the at least one DCI including the valid TCI indication.

[0085] At 518, UE 502 may communicate with base station 504 based on the TCI code points applied to the one or more component carriers.

[0086] Figure 6 600 is a flow chart of a wireless communication method. The method may be performed by a UE (eg, UE 104; device 804). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow the UE to determine at least one DCI including a valid TCI indication.

[0087] At 602, the UE may receive one or more DCIs. For example, 602 may be performed by the TCI component 198 of the device 804. The UE may receive one or more DCIs from a network entity. The one or more DCIs may include TCI code points for one or more component carriers.

[0088] At 604, the UE may send a PUCCH including an ACK or a NACK. For example, 604 may be performed by the TCI component 198 of the apparatus 804. The UE may send a PUCCH including an ACK or a NACK corresponding to each of the one or more DCIs.

[0089] At 606, the UE may determine at least one DCI including a valid TCI indication. For example, 606 may be performed by the TCI component 198 of the device 804. The UE may determine at least one DCI from the one or more DCIs, the at least one DCI including a valid TCI indication for each component carrier of the one or more component carriers.

[0090] At 608, the UE may apply the TCI code point to the one or more component carriers. For example, 608 may be performed by the TCI component 198 of the device 804. The UE may apply the TCI code point to the one or more component carriers based at least on at least one DCI including a valid TCI indication.

[0091] Figure 7 700 is a flow chart of a wireless communication method. The method may be performed by a UE (eg, UE 104; device 804). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow the UE to determine at least one DCI including a valid TCI indication.

[0092] At 702, the UE may receive one or more DCIs. For example, 702 may be performed by the TCI component 198 of the device 804. The UE may receive one or more DCIs from a network entity. The one or more DCIs may include TCI code points for one or more component carriers.

[0093] At 704, the UE may send a PUCCH including an ACK or a NACK. For example, 704 may be performed by the TCI component 198 of the apparatus 804. The UE may send a PUCCH including an ACK or a NACK corresponding to each of the one or more DCIs.

[0094] At 706, the UE may determine at least one DCI including a valid TCI indication. For example, 606 may be performed by the TCI component 198 of the device 804. The UE may determine at least one DCI from the one or more DCIs, the at least one DCI including a valid TCI indication for each component carrier of the one or more component carriers.

[0095] At 708, to determine at least one DCI including a valid DCI from the one or more DCIs, the UE may identify the last DCI in time for each of the one or more component carriers. For example, 708 may be performed by the TCI component 198 of the device 804. The TCI code point associated with the last DCI may be applied to each component carrier. In some aspects, the TCI code point may include at least one of a joint TCI, an uplink TCI, or a downlink TCI.

[0096] At 710, in order to determine at least one DCI including a valid DCI from the one or more DCIs, the UE may identify the last DCI in time for each direction of each component carrier of the one or more component carriers. For example, 710 may be performed by the TCI component 198 of the device 804. The TCI code point associated with the last DCI may be applicable to each component carrier. In some aspects, the last DCI in time may include the last DCI of the TCI applicable to the downlink for each component carrier. The TCI applicable to the downlink may include at least one of a joint TCI or a downlink TCI. In some aspects, the last DCI in time may include the last DCI of the TCI applicable to the uplink for each component carrier. The TCI applicable to the uplink may include at least one of a joint TCI or an uplink TCI.

[0097] At 712, the UE may apply the TCI code point to the one or more component carriers. For example, 712 may be performed by the TCI component 198 of the device 804. The UE may apply the TCI code point to the one or more component carriers based at least on at least one DCI including a valid TCI indication.

[0098] 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, an SPS 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 measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 826, a power source 830, and / or a camera 832. The Bluetooth module 812, the WLAN module 814, and the SPS module 816 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 812, the WLAN module 814, and the SPS module 816 may include their own dedicated antennas and / or communicate using an antenna 880. 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 a computer-readable medium / memory. The software enables the cellular baseband processor 824 / application processor 806 to perform the various functions described above when executed by the cellular baseband processor 824 / application processor 806. The computer-readable medium / memory can 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 the memory 360 and / or at least one of 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 applications) and include only the cellular baseband processor 824 and / or the application processor 806, and in another configuration, the device 804 may be an entire UE (eg, see. Figure 3 350) and includes additional modules of device 804.

[0099] As discussed above, component 198 is configured to: receive one or more DCIs, the one or more DCIs including TCI code points for one or more component carriers; send a PUCCH including an ACK or NACK corresponding to each of the one or more DCIs; determine at least one DCI including a valid TCI indication for each of the one or more component carriers from the one or more DCIs; and apply the TCI code point to the one or more component carriers based at least on the at least one DCI including the valid TCI indication. 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. Component 198 may be one or more hardware components specifically configured to perform the stated process / algorithms, implemented by one or more processors configured to perform the stated process / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. As shown, the device 804 may include a variety of components configured for various functions. In one configuration, the apparatus 804 (particularly the cellular baseband processor 824 and / or the application processor 806) includes a component for receiving one or more DCIs, the one or more DCIs including TCI code points for one or more component carriers. The apparatus includes a component for sending a PUCCH, the PUCCH including an ACK or NACK corresponding to each of the one or more DCIs. The apparatus includes a component for determining at least one DCI from the one or more DCIs, the at least one DCI including a valid TCI indication for each of the one or more component carriers. The apparatus includes a component for applying the TCI code point to the one or more component carriers based at least on at least one DCI including a valid TCI indication. The apparatus also includes a component for identifying the last DCI in time for each of the one or more component carriers. The TCI code point associated with the last DCI is applied to each component carrier. The apparatus also includes a component for identifying the last DCI in time for each direction of each of the one or more component carriers. The TCI code point associated with the last DCI is applied to each component carrier. A means may be a component 198 of the apparatus 804 configured to perform the functions recited by the means. As described above, the apparatus 804 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, a 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.

[0100] Fig. 9900 is a flow chart of a wireless communication method. The method may be performed by a base station (e.g., base station 102; network entity 1002). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow a network entity to receive an indication of a TCI code point applied based on at least one DCI including a valid TCI indication.

[0101] At 902, the network entity may output one or more DCIs. For example, 902 may be performed by the TCI component 199 of the network entity 1002. The network entity may output one or more DCIs, the one or more DCIs including TCI code points for one or more component carriers. In some aspects, the TCI code points may include at least one of a joint TCI, an uplink TCI, or a downlink TCI.

[0102] At 904, the network entity may obtain a PUCCH including an ACK or a NACK. For example, 904 may be performed by the TCI component 199 of the network entity 1002. The network entity may obtain a PUCCH including an ACK or a NACK corresponding to each of the one or more DCIs. The PUCCH may indicate a TCI code point applied to the one or more component carriers based at least on at least one DCI including a valid TCI indication.

[0103] Fig.101000 is a diagram illustrating an example of a hardware implementation for a network entity 1002. The network entity 1002 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1002 may include at least one of a CU 1010, a DU 1030, or a RU 1040. For example, depending on the layer functionality handled by the component 199, the network entity 1002 may include a CU 1010; both a CU 1010 and a DU 1030; each of the CU 1010, the DU 1030, and the RU 1040; the DU 1030; both a DU 1030 and a RU 1040; or a RU 1040. The CU 1010 may include a CU processor 1012. The CU processor 1012 may include an on-chip memory 1012'. In some aspects, the CU 1010 may also include an additional memory module 1014 and a communication interface 1018. CU 1010 communicates with DU 1030 via a midhaul link, such as an F1 interface. DU 1030 may include a DU processor 1032. DU processor 1032 may include on-chip memory 1032'. In some aspects, DU 1030 may also include additional memory modules 1034 and a communication interface 1038. DU 1030 communicates with RU 1040 via a fronthaul link. RU 1040 may include a RU processor 1042. RU processor 1042 may include on-chip memory 1042'. In some aspects, RU 1040 may also include additional memory modules 1044, one or more transceivers 1046, antenna 1080, and communication interface 1048. RU 1040 communicates with UE 104. On-chip memory 1012', 1032', 1042' and additional memory modules 1014, 1034, 1044 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of the processors 1012, 1032, 1042 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0104] As discussed above, component 199 is configured to output one or more DCIs, the one or more DCIs including TCI code points for one or more component carriers; and obtain a PUCCH, the PUCCH including an ACK or NACK corresponding to each of the one or more DCIs, wherein the PUCCH indicates the TCI code points applied to the one or more component carriers based on at least one DCI including a valid TCI indication. Component 199 may be within one or more processors of one or more of CU 1010, DU 1030, and RU 1040. Component 199 may be one or more hardware components that are specifically configured to perform the stated process / algorithms, implemented by one or more processors configured to perform the stated process / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. Network entity 1002 may include a variety of components configured for various functions. In one configuration, network entity 1002 includes a component for outputting one or more DCIs, the one or more DCIs including TCI code points for one or more component carriers. The network entity includes means for obtaining a PUCCH including an ACK or a NACK corresponding to each of the one or more DCIs, wherein the PUCCH indicates a TCI code point applicable to the one or more component carriers based at least on at least one DCI including a valid TCI indication. The means may be components 199 of the network entity 1002 configured to perform the functions recited by the means. As described above, the network entity 1002 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the means may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recited by the means.

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

[0106] 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 can 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, which 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, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will later be known to a person 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", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0107] 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.

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

[0109] Aspect 1 is a method for performing wireless communication at a UE, the method comprising: receiving one or more DCIs, the one or more DCIs comprising TCI code points for one or more component carriers; sending a PUCCH, the PUCCH comprising an ACK or NACK corresponding to each of the one or more DCIs; determining at least one DCI including a valid TCI indication for each of the one or more component carriers from the one or more DCIs; and applying the TCI code points to the one or more component carriers based at least on the at least one DCI including the valid TCI indication.

[0110] Aspect 2 is a method according to Aspect 1, the method further comprising: determining at least one DCI including the valid TCI indication from the one or more DCIs, further comprising: identifying the last DCI in time for each of the one or more component carriers, wherein the TCI code point associated with the last DCI is applied to each component carrier.

[0111] Aspect 3 is a method according to any one of aspects 1 to 2, the method further comprising: the TCI code point includes at least one of a joint TCI, an uplink TCI or a downlink TCI.

[0112] Aspect 4 is a method according to any one of Aspects 1 to 3, the method further comprising: determining the at least one DCI including the valid TCI indication from the one or more DCIs, further comprising: identifying the last DCI in time for each direction of each component carrier in the one or more component carriers, wherein the TCI code point associated with the last DCI is applied to each component carrier.

[0113] Aspect 5 is a method according to any one of aspects 1 to 4, the method further comprising: the last DCI in time includes the last DCI of the TCI applicable to the downlink of each component carrier.

[0114] Aspect 6 is a method according to any one of aspects 1 to 5, the method further comprising: the TCI applicable to the downlink includes at least one of a joint TCI or a downlink TCI.

[0115] Aspect 7 is a method according to any one of aspects 1 to 6, the method further comprising: the last DCI in time includes the last DCI of the uplink applicable TCI for each component carrier.

[0116] Aspect 8 is a method according to any one of aspects 1 to 7, the method further comprising: the uplink applicable TCI comprises at least one of a joint TCI or an uplink TCI.

[0117] Aspect 9 is an apparatus for wireless communication at a network entity, the apparatus comprising at least one processor coupled to a memory and at least one transceiver, the at least one processor being configured to implement any one of aspects 1 to 8.

[0118] Aspect 10 is an apparatus for wireless communication at a network entity, the apparatus comprising means for implementing any one of aspects 1 to 8.

[0119] Aspect 11 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 8.

[0120] Aspect 12 is a method for performing wireless communications at a network entity, the method comprising: outputting one or more DCIs, the one or more DCIs comprising TCI code points for one or more component carriers; and obtaining a PUCCH, the PUCCH comprising an ACK or NACK corresponding to each of the one or more DCIs, wherein the PUCCH indication is applied to the TCI code points of the one or more component carriers based at least on at least one DCI comprising a valid TCI indication.

[0121] Aspect 13 is a method according to aspect 12, the method further comprising: the TCI code point comprises at least one of a joint TCI, an uplink TCI or a downlink TCI.

[0122] Aspect 14 is an apparatus for wireless communication at a network entity, the apparatus comprising at least one processor coupled to a memory and at least one transceiver, the at least one processor being configured to implement any one of aspects 12 to 13.

[0123] Aspect 15 is an apparatus for wireless communication at a network entity, the apparatus comprising means for implementing any one of aspects 12 to 13.

[0124] Aspect 16 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 12 to 13.

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 and based at least in part on the information stored in the memory, the at least one processor configured to: receiving one or more downlink control indicators (DCIs), the one or more DCIs comprising transmission configuration indicator (TCI) code points for one or more component carriers; transmitting a physical uplink control channel (PUCCH), the PUCCH including an acknowledgement (ACK) or a negative acknowledgement (NACK) corresponding to each of the one or more DCIs; determining, from the one or more DCIs, at least one DCI comprising a valid TCI indication for each of the one or more component carriers; as well as The TCI code point is applied to the one or more component carriers based at least on the at least one DCI including the valid TCI indication.

2. The device according to claim 1, further comprising: A transceiver is coupled to the at least one processor.

3. The apparatus of claim 1 , wherein to determine the at least one DCI including the valid TCI indication from the one or more DCIs, the at least one processor is configured to: A last DCI in time for each of the one or more component carriers is identified, wherein the TCI code point associated with the last DCI is applied to each component carrier.

4. The apparatus of claim 3, wherein the TCI code point comprises at least one of a joint TCI, an uplink TCI, or a downlink TCI.

5. The apparatus of claim 1 , wherein to determine the at least one DCI including the valid TCI indication from the one or more DCIs, the at least one processor is configured to: A last DCI in time for each direction of each of the one or more component carriers is identified, wherein the TCI code point associated with the last DCI is applied to each component carrier.

6. The apparatus of claim 5, wherein the last DCI in time comprises the last DCI of downlink-applicable TCI for each component carrier.

7. The apparatus of claim 6, wherein the downlink-applicable TCI comprises at least one of a joint TCI or a downlink TCI.

8. The apparatus of claim 5, wherein the last DCI in time comprises the last DCI of uplink-applicable TCI for each component carrier.

9. The apparatus of claim 8, wherein the uplink-applicable TCI comprises at least one of a joint TCI or an uplink TCI.

10. A method of wireless communication at a user equipment (UE), the method comprising: receiving one or more downlink control indicators (DCIs), the one or more DCIs comprising transmission configuration indicator (TCI) code points for one or more component carriers; transmitting a physical uplink control channel (PUCCH), the PUCCH including an acknowledgement (ACK) or a negative acknowledgement (NACK) corresponding to each of the one or more DCIs; determining, from the one or more DCIs, at least one DCI comprising a valid TCI indication for each of the one or more component carriers; as well as The TCI code point is applied to the one or more component carriers based at least on the at least one DCI including the valid TCI indication.

11. The method of claim 10, wherein determining the at least one DCI including the valid TCI indication from the one or more DCIs further comprises: A last DCI in time for each of the one or more component carriers is identified, wherein the TCI code point associated with the last DCI is applied to each component carrier.

12. The method of claim 11, wherein the TCI code point comprises at least one of a joint TCI, an uplink TCI, or a downlink TCI.

13. The method of claim 10, wherein determining the at least one DCI including the valid TCI indication from the one or more DCIs further comprises: A last DCI in time for each direction of each of the one or more component carriers is identified, wherein the TCI code point associated with the last DCI is applied to each component carrier.

14. The method of claim 13, wherein the last DCI in time comprises the last DCI of downlink-applicable TCI for each component carrier.

15. The method of claim 14, wherein the downlink-applicable TCI comprises at least one of a joint TCI or a downlink TCI.

16. The method of claim 13, wherein the last DCI in time comprises the last DCI of uplink applicable TCI for each component carrier.

17. The method of claim 16, wherein the uplink-applicable TCI comprises at least one of a joint TCI or an uplink TCI.

18. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: outputting one or more downlink control indicators (DCIs), the one or more DCIs comprising transmission configuration indicator (TCI) code points for one or more component carriers; as well as A physical uplink control channel (PUCCH) is obtained, the PUCCH including an acknowledgement (ACK) or a negative acknowledgement (NACK) corresponding to each of the one or more DCIs, wherein the PUCCH indicates a TCI code point applied to the one or more component carriers based on at least one DCI including a valid TCI indication.

19. The apparatus according to claim 18, further comprising: A transceiver is coupled to the at least one processor.

20. The apparatus of claim 18, wherein the TCI codepoint comprises at least one of a joint TCI, an uplink TCI, or a downlink TCI.

21. A method for wireless communication at a network entity, the method comprising: outputting one or more downlink control indicators (DCIs), the one or more DCIs comprising transmission configuration indicator (TCI) code points for one or more component carriers; as well as A physical uplink control channel (PUCCH) is obtained, the PUCCH including an acknowledgement (ACK) or a negative acknowledgement (NACK) corresponding to each of the one or more DCIs, wherein the PUCCH indicates a TCI code point applied to the one or more component carriers based on at least one DCI including a valid TCI indication.

22. The method of claim 21, wherein the TCI code point comprises at least one of a joint TCI, an uplink TCI, or a downlink TCI.

Images