Unified transmission configuration indicator acknowledgement based on downlink control information

Abstract

Methods, systems, and devices for wireless communication are described. A unified transmission configuration indicator (TCI) framework that can be implemented by a wireless communication system can support a common TCI state for a joint of downlink and uplink channels or reference signals associated with communications between devices. A base station can transmit, to a user equipment (UE), a downlink control information (DCI) indicating one or more TCI states and a scheduling of a downlink channel. The UE can transmit an acknowledgment message (as an explicit acknowledgment or an implicit acknowledgment) to confirm whether the one or more TCI states are successfully received in the DCI.

Description

Technical Field

[0001] The following generally refers to wireless communication, including the reception of the Unified Transport Configuration Indicator (TCI) based on downlink control information (DCI). Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems, which may be referred to as New Radio (NR) systems. These systems can employ various technologies, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each of which simultaneously supports communication from multiple communication devices, which may also be referred to as User Equipment (UE).

[0003] Some wireless communication networks can utilize the Unified Transmission Configuration Indicator (TCI) framework to support beamforming communication between devices. Conventional techniques associated with the reception and implementation of such TCI information can be flawed, potentially leading to invalid implementations of the TCI information.

[0004] Overview

[0005] The described technology relates to improved methods, systems, devices, and apparatuses for supporting the reception of a Unified Transport Configuration Indicator (TCI) based on downlink control information (DCI). Generally, the described technology allows wireless devices (such as user equipment) to explicitly or implicitly receive one or more TCI states of a unified TCI framework implemented by a wireless communication system. The unified TCI framework can support a joint shared TCI state indicating a shared beam for at least one downlink channel (or downlink reference signal transmission) and at least one uplink channel (or uplink reference signal transmission). The downlink shared TCI state can indicate a shared beam for at least two downlink channels, and the uplink shared TCI state can indicate a shared beam for at least two uplink channels. In some examples, a base station can transmit a DCI to a user equipment (UE) to indicate the unified TCI framework and the scheduling of downlink channels.

[0006] In some examples, the UE may successfully decode the DCI of the scheduled downlink channel but may fail to decode the scheduled downlink channel, or the UE may partially decode the scheduled downlink channel. In such examples, the UE may transmit an acknowledgment (ACK) message (as an explicit ACK or implicit ACK) to confirm whether the indication to the unified TCI framework was successfully received (e.g., in the DCI). For example, to explicitly acknowledge the reception of the TCI framework, the UE may transmit an explicit ACK message for the scheduled downlink channel, such as one or more affirmative ACK bits, dedicated ACK bits, or enhanced ACK information. In some examples, the UE may transmit an implicit ACK. For example, this implicit acknowledgment may be a transmission of Hybrid Automatic Repeat Request (HARQ) feedback for the downlink channel indicated in the same DCI as the beam indication. Based on the transmission of this ACK, the UE may apply the received TCI framework.

[0007] A method for wireless communication at a user equipment (UE) is described. The method may include: receiving downlink control information (DCI) from a base station for scheduling a downlink shared channel, the DCI including a transmission configuration indicator (TCI) state indicating a shared beam for at least one channel; transmitting a feedback message to the base station for the downlink shared channel, wherein the feedback message acknowledges receipt of the TCI state; and applying the TCI state after transmitting the feedback message acknowledging receipt of the TCI state.

[0008] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. These instructions are executable by the processor to cause the apparatus to: receive from a base station a Distributed Controlled Instruction (DCI) for scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel; transmit to the base station a feedback message for the downlink shared channel, wherein the feedback message acknowledges receipt of the TCI state; and apply the TCI state after transmitting the feedback message acknowledging receipt of the TCI state.

[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving from a base station a Distributed Controlled Indicator (DCI) for scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel; means for transmitting to the base station a feedback message for the downlink shared channel, wherein the feedback message acknowledges receipt of the TCI state; and means for applying the TCI state after transmitting the feedback message acknowledging receipt of the TCI state.

[0010] A non-transient computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by a processor to: receive from a base station a DCI for scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel; transmit to the base station a feedback message for the downlink shared channel, wherein the feedback message acknowledges receipt of the TCI state; and apply the TCI state after transmitting the feedback message acknowledging receipt of the TCI state.

[0011] Examples of methods, apparatuses, and non-transient computer-readable media described herein may further include operations, features, means, or instructions for: determining that the payload of the downlink shared channel comprises a single transport block; and based on that determination, transmitting a single positive ACK bit for the downlink shared channel to the base station to acknowledge receipt of the TCI state.

[0012] Examples of methods, apparatuses, and non-transient computer-readable media described herein may further include operations, features, means, or instructions for: determining that the payload of the downlink shared channel comprises more than one transport block; and based on that determination, transmitting at least one positive ACK bit for the downlink shared channel to the base station to acknowledge receipt of the TCI state.

[0013] Examples of methods, apparatuses, and non-transient computer-readable media described herein may further include operations, features, means, or instructions for: determining that the downlink shared channel may be configured with one or more code block groups; and based on the determination, transmitting at least one positive ACK bit for the downlink shared channel to the base station to acknowledge receipt of the TCI state.

[0014] Examples of methods, apparatuses, and nontransient computer-readable media described herein may further include operations, features, means, or instructions for: generating the feedback message as an enhanced ACK message, the enhanced ACK message including a set of affirmative ACK bits; and transmitting the enhanced ACK message to the base station based on the generation to acknowledge receipt of the TCI state.

[0015] In some examples of the methods, apparatuses, and non-transient computer-readable media described herein, the enhanced ACK message may be associated with a Hybrid Automatic Repeat Request (HARQ) Type II codebook.

[0016] Examples of methods, apparatuses, and non-transient computer-readable media described herein may further include operations, features, means, or instructions for receiving from the base station via radio resource control messages an indication of reception of a feedback message for the downlink shared channel, including an ACK bit set and an additional padded bit set to acknowledge the TCI state.

[0017] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, transmitting the feedback message may include operations, features, means, or instructions for: allocating an additional padded set of bits to a portion of the codebook used for the downlink shared channel, the additional padded set of bits indicating a positive ACK value; and transmitting to the base station at least the additional padded set of bits allocated to that portion of the codebook to acknowledge receipt of the TCI state.

[0018] In some examples of the methods, apparatuses, and nontransient computer-readable media described herein, the payload of the downlink shared channel includes more than one transport block, and the methods, apparatuses, and nontransient computer-readable media may further include operations, features, means, or instructions for: transmitting to the base station a first affirmative ACK bit for a first transport block, the first affirmative ACK bit indicating reception of the downlink shared channel; and transmitting to the base station a second affirmative ACK bit for a second transport block, the second affirmative ACK bit indicating reception of both the downlink shared channel and the DCI.

[0019] Some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein may further include operations, features, means or instructions for: generating a single positive ACK bit dedicated to the DCI based on a HARQ Type I codebook; and transmitting a feedback message, including the single positive ACK bit, to the base station based on the generation to acknowledge receipt of the TCI state.

[0020] Examples of methods, apparatuses, and nontransient computer-readable media described herein may further include operations, features, means, or instructions for: transmitting the feedback message to the base station using an uplink control channel resource set associated with the downlink shared channel, wherein the feedback message includes a first confirmation of receipt of the downlink shared channel and a second confirmation of receipt of the TCI state; and applying the TCI state after transmitting the feedback message, wherein the feedback message indicates receipt of the TCI state.

[0021] In some examples of the methods, apparatuses, and non-transient computer-readable media described herein, the uplink control channel resource set may be configured with a set of HARQ bits for transmitting feedback messages associated with the downlink shared channel.

[0022] In some examples of the methods, apparatuses, and non-transient computer-readable media described herein, the uplink control channel resource set may be indicated by the DCI.

[0023] In some examples of the methods, apparatus (devices), and non-transient computer-readable media described herein, transmitting the feedback message may include operations, features, means, or instructions for: determining a TCI state in the DCI that may indicate the shared beam; identifying an uplink control channel resource set in the DCI for transmitting the feedback message based on the TCI state; and using the uplink control channel resource set to transmit the feedback message to the base station to acknowledge receipt of the TCI state.

[0024] Examples of methods, apparatuses, and nontransient computer-readable media described herein may further include operations, features, means, or instructions for: determining a TCI state that may include an indication of the shared beam in the DCI and the at least one other DCI; and using the uplink control channel resource set to transmit the feedback message to the base station to confirm reception of the TCI state, or using a separate uplink control channel resource set to transmit the feedback message to the base station to confirm reception of the at least one other DCI.

[0025] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, the DCI may include a TCI state indicating the shared beam, based on the fact that the DCI is received after at least one other DCI.

[0026] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, the TCI status indication is a joint indication or a separate indication for the at least one channel.

[0027] In some examples of the methods, apparatuses, and non-transient computer-readable media described herein, the TCI state indicating the shared beam includes layer 1-based beam indication.

[0028] A method for wireless communication at a base station is described. The method may include: transmitting to a UE a scheduling DCI for a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel; and receiving from the UE a feedback message for the downlink shared channel, wherein the feedback message acknowledges the UE's reception of the TCI state.

[0029] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. These instructions are executable by the processor to cause the apparatus to: transmit a DCI (Distributed Controlled Instruction) for scheduling a downlink shared channel to a UE, the DCI including a TCI (Tracking Controlled Instruction) state indicating a shared beam for at least one channel; and receive a feedback message from the UE for the downlink shared channel, wherein the feedback message acknowledges the UE's reception of the TCI state.

[0030] Another apparatus for wireless communication at a base station is described. The apparatus may include: means for transmitting to a UE a Distributed Controlled Instruction (DCI) scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel; and means for receiving from the UE a feedback message for the downlink shared channel, wherein the feedback message acknowledges the UE's receipt of the TCI state.

[0031] A non-transient computer-readable medium is described, storing code for wireless communication at a base station. The code may include instructions executable by a processor to: transmit to a UE a DCI scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel; and receive from the UE a feedback message for the downlink shared channel, wherein the feedback message acknowledges the UE's reception of the TCI state.

[0032] Examples of methods, apparatuses, and non-transient computer-readable media described herein may further include operations, features, means, or instructions for transmitting the downlink shared channel in a single transport block; and receiving, based on the transmission, a single affirmative ACK bit from the UE to acknowledge receipt of the TCI state for the downlink shared channel.

[0033] Examples of methods, apparatuses, and nontransient computer-readable media described herein may further include operations, features, means, or instructions for transmitting the downlink shared channel in more than one transport block; and, based on the transmission, receiving by the UE at least one positive ACK bit for acknowledging the TCI state of the downlink shared channel.

[0034] Examples of methods, apparatuses, and non-transient computer-readable media described herein may further include operations, features, means, or instructions for: transmitting the downlink shared channel in one or more code block groups; and receiving from the UE, based on the transmission, at least one positive ACK bit for acknowledging the TCI state of the downlink shared channel.

[0035] Some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein may further include operations, features, means or instructions for receiving the feedback message from the UE as an enhanced ACK message including a set of affirmative ACK bits, wherein the enhanced ACK message acknowledges the reception of the TCI state.

[0036] In some examples of the methods, apparatus, and non-transient computer-readable media described herein, the enhanced ACK message may be associated with a HARQ Type II codebook.

[0037] Examples of methods, apparatuses, and non-transient computer-readable media described herein may further include operations, features, means, or instructions for transmitting to the UE via radio resource control messages an indication of reception of a feedback message for the downlink shared channel, including an ACK bit set and an additional padded bit set to acknowledge the TCI state.

[0038] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, transmitting the feedback message may include operations, features, means, or instructions for receiving an additional padded set of bits from the UE in a portion of the codebook for the downlink shared channel, the additional padded set of bits indicating a positive ACK value for acknowledging the reception of the TCI state.

[0039] In some examples of the methods, apparatuses, and nontransient computer-readable media described herein, the payload of the downlink shared channel includes more than one transport block, and the methods, apparatuses, and nontransient computer-readable media may further include operations, features, means, or instructions for: receiving from the UE a first affirmative ACK bit for a first transport block, the first affirmative ACK bit indicating reception of the downlink shared channel; and receiving from the UE a second affirmative ACK bit for a second transport block, the second affirmative ACK bit indicating reception of both the downlink shared channel and the DCI.

[0040] Some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein may further include operations, features, devices or instructions for receiving from the UE, according to a HARQ Type I codebook, a feedback message including a single positive ACK bit dedicated to the DCI, wherein the single positive ACK bit acknowledges the reception of the TCI state.

[0041] Some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein may further include operations, features, means or instructions for receiving the feedback message from the UE on an uplink control channel resource set associated with the downlink shared channel, wherein the feedback message includes a first confirmation of receipt of the downlink shared channel and a second confirmation of receipt of the TCI state.

[0042] In some examples of the methods, apparatuses, and non-transient computer-readable media described herein, the uplink control channel resource set may be configured with a set of HARQ bits for transmitting feedback messages associated with the downlink shared channel.

[0043] In some examples of the methods, apparatuses, and non-transient computer-readable media described herein, the uplink control channel resource set may be indicated by the DCI.

[0044] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, transmitting the feedback message may include operations, features, means, or instructions for: transmitting, based on the DCI including the TCI state, an indication of the shared beam and an indication of the uplink control channel resource set for the feedback message in the DCI; and receiving the feedback message from the UE on the uplink control channel resource set to acknowledge receipt of the TCI state.

[0045] Examples of methods, apparatuses, and nontransient computer-readable media described herein may further include operations, features, means, or instructions for: transmitting a TCI state indicating the shared beam in the DCI and the at least one other DCI; and receiving the feedback message from the UE on the uplink control channel resource set to confirm reception of the TCI state, or receiving the feedback message from the UE on a separate uplink control channel resource set to confirm reception of the at least one other DCI.

[0046] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, the DCI may include a TCI state indicating the shared beam, based on the fact that the DCI is transmitted after at least one other DCI.

[0047] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, the TCI status indication is a joint indication or a separate indication for the at least one channel.

[0048] In some examples of the methods, apparatuses, and non-transient computer-readable media described herein, the TCI state indicating the shared beam includes layer 1-based beam indication. Brief description of the attached diagram

[0050] Figure 1 Examples of wireless communication systems supported by the unified transmission configuration indicator based on downlink control information, according to various aspects of this disclosure, are explained.

[0051] Figure 2 Examples of wireless communication networks supported by the unified transmission configuration indicator based on downlink control information, according to various aspects of this disclosure, are explained.

[0052] Figures 3 to 7 An example of a timeline for the receipt of a unified transport configuration indicator based on downlink control information, supported by various aspects of this disclosure, is explained.

[0053] Figure 8 and 9 A block diagram of a device supporting the reception of a unified transport configuration indicator based on downlink control information, according to various aspects of this disclosure, is shown.

[0054] Figure 10 A block diagram of a communication manager that supports the reception of a unified transport configuration indicator based on downlink control information, according to various aspects of this disclosure, is shown.

[0055] Figure 11 A diagram of a system including a device supporting the reception of a unified transport configuration indicator based on downlink control information, according to various aspects of this disclosure, is shown.

[0056] Figure 12 and 13 A block diagram of a device supporting the reception of a unified transport configuration indicator based on downlink control information, according to various aspects of this disclosure, is shown.

[0057] Figure 14 A block diagram of a communication manager that supports the reception of a unified transport configuration indicator based on downlink control information, according to various aspects of this disclosure, is shown.

[0058] Figure 15 A diagram of a system including a device supporting the reception of a unified transport configuration indicator based on downlink control information, according to various aspects of this disclosure, is shown.

[0059] Figures 16 to 22 A flowchart illustrating a method for receiving a unified transport configuration indicator based on downlink control information, according to various aspects of this disclosure, is shown.

[0060] Detailed description

[0061] Some wireless communication networks may employ a Unified Transmission Configuration Indicator (TCI) framework to support beamforming communication between devices within the network. According to the unified TCI framework, a joint shared TCI state can indicate a shared beam for at least one downlink channel (or downlink reference signal transmission) and at least one uplink channel (or uplink reference signal transmission). A downlink shared TCI state can indicate a shared beam for at least two downlink channels, or an uplink shared TCI state can indicate a shared beam for at least two uplink channels. In some examples, the base station may transmit downlink control information (DCI) to the user equipment (UE) to indicate the unified TCI framework. In some cases, an acknowledgment (ACK) message for a downlink channel scheduled by a DCI carrying the unified TCI framework indication can also be used as an ACK (again for that DCI) to indicate successful reception indicated by the unified TCI framework.

[0062] However, associating an ACK for the DCI with an ACK for the scheduled downlink channel can lead to problems. For example, the UE might successfully decode the DCI but fail to decode the scheduled downlink channel, or the UE might partially decode the scheduled downlink channel. In such examples, the UE can transmit an ACK message, but the ACK message may not accurately convey whether the DCI was successfully received.

[0063] The various aspects generally involve using a unified TCI framework for communication between two devices, and more specifically involve transmitting explicit and implicit ACKs before using the unified TCI framework to confirm whether the indication for the unified TCI framework has been successfully received (e.g., in a DCI). Upon receiving an indication for the unified TCI framework (e.g., a beam indication) from a base station in a DCI (where the DCI also corresponds to at least one uplink transmission), the UE may apply the unified TCI framework to communication with the base station after ACKing the unified TCI framework. In some examples, ACKing the unified TCI framework may include transmitting an explicit ACK message for a scheduled downlink channel, such as one or more affirmative ACK bits, dedicated ACK bits, or enhanced ACK information, to explicitly indicate that at least the beam indication for the unified TCI framework has been correctly received by the UE.

[0064] In some other examples, the ACK can be implicit. For example, implicit indication of DCI reception may include transmitting a Hybrid Automatic Repeat Request (HARQ) feedback for the downlink channel indicated in the same DCI as the beam indication. In some examples, the UE may receive multiple DCIs, and the UE may transmit implicit indication of DCI reception by transmitting feedback for the downlink channel indicated in the same DCI as the beam indication.

[0065] Various aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. The techniques employed by the described communication devices can provide benefits and enhancements to the operation of the communication devices, including increased reliability from using a shared beam (e.g., unified TCI state) for communication between these communication devices. For example, operations performed by the described communication devices can provide improvements in confirming a combined downlink / uplink beam indication or a separate downlink / uplink beam indication (e.g., unified TCI framework). In some implementations, operations performed by the described communication devices to confirm the indication may include transmitting an uplink transmission or feedback message indicated by the same control message (e.g., a DCI message) including a combined downlink / uplink beam indication or a separate downlink / uplink beam indication. By explicitly or implicitly confirming the indication by transmitting uplink messages, the communication devices can more efficiently confirm indications for control messages carrying combined downlink / uplink beam indications, thereby reducing latency and improving communication reliability, etc.

[0066] The aspects of this disclosure are initially described in the context of wireless communication systems. These aspects are further illustrated and described by reference to apparatus diagrams, system diagrams, process flows, and flowcharts relating to DCI-based unified TCI reception.

[0067] Figure 1 Examples of a wireless communication system 100 supporting DCI-based unified TCI acceptance according to various aspects of this disclosure are described. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-APro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low latency communication, communication with low-cost and low-complexity devices, or any combination thereof.

[0068] Base station 105 can be distributed across a geographical area to form wireless communication system 100, and can be different types of devices or devices with different capabilities. Base station 105 and UE 115 can communicate wirelessly via one or more communication links 125. Each base station 105 can provide a coverage area 110, and UE 115 and base station 105 can establish one or more communication links 125 on the coverage area 110. Coverage area 110 can be an example of a geographical area over which base station 105 and UE 115 can support signal communication according to one or more radio access technologies.

[0069] Each UE 115 can be distributed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. Each UE 115 can be a different type of device or a device with different capabilities. Figure 1 The document describes some example UE 115s. The UE 115 described herein can communicate with various types of devices, such as other UE 115s, base station 105, or network equipment (e.g., core network nodes, relay equipment, integrated access and backhaul (IAB) nodes, or other network equipment). Figure 1 As shown in the image.

[0070] Each base station 105 may communicate with the core network 130, or with each other, or both. For example, base station 105 may interface with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base stations 105 may communicate with each other directly (e.g., directly between base stations 105), indirectly (e.g., via the core network 130), or directly and indirectly on backhaul links 120 (e.g., via X2, Xn, or other interfaces). In some examples, backhaul link 120 may be or include one or more radio links.

[0071] One or more of the base stations 105 described herein may include, or may be referred to by those skilled in the art as, base transceiver station, radio base station, access point, radio transceiver, B node, evolved B node (eNB), next-generation B node or gigabit B node (any of which may be referred to as gNB), home B node, home evolved B node, or other suitable terms.

[0072] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0073] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, as well as base station 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 As shown in the image.

[0074] UE 115 and base station 105 can wirelessly communicate with each other via one or more communication links 125 on one or more carriers. The term "carrier" can refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the radio spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used in conjunction with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0075] In some examples (e.g., in a carrier aggregation configuration), the carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. The carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be located according to a channel grid for discovery by UE 115. The carrier may operate in an autonomous mode in which initial acquisition and connection can be performed by UE 115 via that carrier, or in a non-autonomous mode in which the carrier may connect to carriers anchored using different carriers (e.g., different carriers of the same or different radio access technologies).

[0076] The communication link 125 shown in the wireless communication system 100 may include uplink transmission from UE 115 to base station 105, or downlink transmission from base station 105 to UE 115. The carrier may carry downlink or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0077] A carrier may be associated with a bandwidth of the radio frequency spectrum, and in some examples, this carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of several defined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz) of a carrier for a particular radio access technology. Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) may have a hardware configuration that supports communication on a specific carrier bandwidth, or may be configurable to support communication on a single carrier bandwidth within a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, BWP) or all of the carrier bandwidth.

[0078] The signal waveform transmitted on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the code rate of the modulation scheme, or both). Thus, the more resource elements the UE 115 receives and the higher the order of the modulation scheme, the higher the data rate the UE 115 can achieve. Wireless communication resources can refer to a combination of radio frequency spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and using multiple spatial layers can further improve the data rate or data integrity of communication with the UE 115.

[0079] One or more sets of parameters can be supported for a carrier, where the parameter set may include the subcarrier spacing (Δf) and the cyclic prefix. A carrier can be divided into one or more BWPs with the same or different parameter designs. In some examples, the UE 115 can be configured with multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and communication for the UE 115 can be limited to one or more active BWPs.

[0080] The time interval of base station 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period T. s =1 / (Δf) max ·N f ) seconds, where Δf max This can represent the maximum supported subcarrier spacing, while N f This can represent the maximum supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0081] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into several time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include several symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple mini-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N) symbols. f (Number) sampling periods. The duration of a symbol period can depend on the subcarrier interval or the operating frequency band.

[0082] A subframe, time slot, mini-slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0083] Physical channels can be multiplexed on a carrier using various techniques. Physical control channels and physical data channels can be multiplexed on a downlink carrier, for example, using one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for physical control channels can be defined by the number of symbol periods and can extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more of the UEs 115 can monitor or search control regions for control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for control channel candidates can refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information in a control information format having a given payload size. The search space set may include a common search space set configured to send control information to multiple UEs 115 and a UE-specific search space set configured to send control information to a specific UE 115.

[0084] Each base station 105 may provide communication coverage via one or more cells (e.g., macrocells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with base station 105 (e.g., on a carrier) and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or others). In some examples, a cell may also refer to a geographic coverage area 110 or a portion of geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. The extent of such cells may vary from smaller areas (e.g., structures, subsets of structures) to larger areas depending on various factors such as the capabilities of base station 105. For example, a cell may be or include buildings, subsets of buildings, or external space between or overlapping geographic coverage areas 110, among other examples.

[0085] Macrocells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access for UEs 115 that have service subscriptions with a network provider supporting the macrocell. Small cells may be associated with a lower-power base station 105 (compared to macrocells) and may operate in the same or different (e.g., licensed or unlicensed) frequency bands as macrocells. Small cells may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a Closed Subscriber Group (CSG), or UEs 115 associated with a user in a home or office). Base station 105 may support one or more cells and may also support communication on one or more cells using one or more component carriers.

[0086] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0087] In some examples, base station 105 may be mobile, and thus provide communication coverage to mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. Wireless communication system 100 may include, for example, a heterogeneous network, in which different types of base stations 105 use the same or different radio access technologies to provide coverage to various geographic coverage areas 110.

[0088] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, base stations 105 can have similar frame timing, and transmissions from different base stations 105 can be approximately time-aligned. For asynchronous operation, base stations 105 can have different frame timing, and transmissions from different base stations 105 may not be time-aligned in some examples. The techniques described herein can be used for both synchronous and asynchronous operation.

[0089] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with base station 105 without human intervention. In some examples, M2M communication or MTC may include communication from devices that have integrated sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or automate the behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wilderness survival monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial toll collection.

[0090] Some UEs 115 can be configured to operate in reduced-power modes, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but not simultaneous transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communication, operating on limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., subcarriers or resource block (RB) set) within the carrier, within the carrier's guard band, or outside the carrier.

[0091] Wireless communication system 100 may be configured to support ultra-reliable communication or low latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low latency communication (URLLC) or mission-critical communication. UE 115 may be designed to support ultra-reliable, low latency, or mission-critical functions (e.g., mission-critical functions). Ultra-reliable communication may include private or group communication and may be supported by one or more mission-critical services, such as Mission-Critical Talk-to-Talk (MCPTT), Mission-Critical Video (MCVideo), or Mission-Critical Data (MCData)). Support for mission-critical functions may include prioritization of services, and mission-critical services may be used for public safety or general business applications. The terms ultra-reliable, low latency, mission-critical, and ultra-reliable low latency are used interchangeably herein.

[0092] In some examples, UE 115 may also be able to communicate directly with other UE 115 on a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UE 115s utilizing D2D communication may be within the geographic coverage area 110 of base station 105. Other UE 115s in such a group may be outside the geographic coverage area 110 of base station 105 or may be unable to receive transmissions from base station 105 for other reasons. In some examples, groups of UE 115s communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE 115 transmits to every other UE 115 in the group. In some examples, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between the individual UE 115s without involving base station 105.

[0093] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these communications. Vehicles may signal information related to traffic conditions, signaling, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate via vehicle-to-network (V2N) communication through one or more network nodes (e.g., base station 105) with roadside infrastructure (such as roadside units), or with the network, or with both.

[0094] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC). The EPC or 5GC may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by base station 105 associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may be connected to one or more network operator IP services 150. The IP service 150 may include access to the Internet, intranet, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0095] Some network devices (such as base station 105) may include sub-components (such as access network entity 140), which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with each UE 115 through one or more other access network transport entities 145, which may be referred to as a radio headend, smart radio headend, or transmit / receive point (TRP). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio headends and ANCs) or combined into a single network device (e.g., base station 105).

[0096] Wireless communication system 100 can operate using one or more frequency bands, typically in the range of 300 MHz to 300 GHz. Generally, the 300 MHz to 3 GHz band is referred to as a UHF band or decimeter band because the wavelengths range from approximately 1 decimeter to 1 meter. UHF waves can be blocked or redirected by buildings and environmental features, but these waves can penetrate various structures sufficiently for macrocells to provide service to UE 115 located indoors. Compared to transmissions using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, UHF wave transmission can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0097] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) zoning using a frequency band from 3 GHz to 30 GHz (also known as the centimeter band) or in the extremely high frequency (EHF) zoning using a spectrum (e.g., from 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, this can facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may suffer even greater atmospheric attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein can be employed across transmissions using one or more different frequency zonings, and the frequency band usage specified across these frequency zonings may vary by country or regulatory authority.

[0098] Wireless communication system 100 may utilize both licensed and unlicensed radio spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating in unlicensed radio spectrum bands, devices (such as base station 105 and UE 115) may employ carrier sensing for collision detection and avoidance. In some examples, operation in unlicensed frequency bands may be coordinated with component carriers operating in licensed frequency bands based on carrier aggregation configurations (e.g., LAA). Operation in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, etc.

[0099] Base station 105 or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels that can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with base station 105 may be located in different geographical locations. Base station 105 may have an antenna array with several rows and columns of antenna ports that base station 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.

[0100] Base station 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. For example, a transmitting device may transmit multiple signals via different antennas or different combinations of antennas. Similarly, a receiving device may receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0101] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., base station 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array, such that some signals propagating relative to a particular orientation of the antenna array experience constructive interference, while others experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include the transmitting or receiving device applying amplitude offset, phase offset, or both to the signals carried via the antenna elements associated with that device. The adjustments associated with each antenna element may be defined by a beamforming weight set associated with a particular orientation (e.g., the antenna array relative to the transmitting or receiving device, or relative to some other orientation).

[0102] Base station 105 or UE 115 may use beamsweeping techniques as part of beamforming operations. For example, base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by base station 105 in different directions. For example, base station 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmissions in different beam directions may be used (e.g., by the transmitting device (such as base station 105) or the receiving device (such as UE 115)) to identify the beam direction that base station 105 will use for later transmission or reception.

[0103] Some signals (such as data signals associated with a specific receiving device) may be transmitted by base station 105 in a single beam direction (e.g., the direction associated with the receiving device (such as UE 115)). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted in one or more beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions and may report to base station 105 an indication of the signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0104] In some examples, transmissions performed by a device (e.g., by base station 105 or UE 115) may be executed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate combined beams for transmission (e.g., from base station 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and this feedback may correspond to a configured number of beams across the system bandwidth or one or more subbands. Base station 105 may transmit reference signals that may be precoded or unprecoded (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)). UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may use similar techniques to transmit signals multiple times in different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0105] A receiver device (e.g., UE 115) may attempt multiple receive configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105. For example, the receiver device may attempt multiple receive directions by: receiving via different antenna subarrays; processing received signals according to different antenna subarrays; receiving according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different directional listening weight sets); or processing received signals according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of the antenna array, any of which may be referred to as "listening" according to different receive configurations or receive directions. In some examples, the receiver device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration may be aligned on a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0106] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer can be IP-based. The Radio Link Control (RLC) layer performs packet segmentation and reassembly for communication on logical channels. The Media Access Control (MAC) layer performs priority handling and multiplexes logical channels into transport channels. The MAC layer can also use error detection, error correction, or both to support MAC layer retransmissions to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and the base station 105 or core network 130 that support user plane data radio bearers. At the physical layer, transport channels can be mapped to physical channels.

[0107] UE 115 and base station 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data on communication link 125. HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve MAC layer throughput in poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support simultaneous time-slot HARQ feedback, where the device can provide HARQ feedback in a specific time slot for data received in previous symbols within that time slot. In other cases, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0108] In some wireless communication systems, two devices may use different TCI states for communication with each other, for example, for beamforming transmission between two devices in the system. In some examples, two devices may use a unified TCI framework for communication. A unified TCI framework may include a joint shared TCI state for uplink and downlink communication, a separate uplink shared TCI state, a separate downlink shared TCI state, or a combination thereof. For example, a joint shared TCI state for uplink and downlink communication may indicate a shared beam for at least one downlink channel (or downlink reference signal) plus at least one uplink channel (or uplink reference signal); a separate downlink shared TCI state may indicate a shared beam for at least two downlink channels (or downlink reference signals); and a separate uplink shared TCI state may indicate a shared beam for at least two uplink channels (or uplink reference signals). With a unified TCI framework, UE 115 may support joint TCI for downlink and uplink communication based on the downlink TCI framework. In some implementations, the term "TCI" may include a TCI state that includes at least one source reference signal to provide the device with a reference for determining a quasi-co-location (QCL), a spatial filter, or both for communication with additional devices (e.g., for UE assumptions).

[0109] To accommodate separate beam indications for uplink and downlink communications under a unified TCI framework, UE 115 can utilize two separate TCI states (e.g., one TCI state for downlink communications and one TCI state for uplink communications). For a separate downlink shared TCI state, source reference signals in M ​​TCIs can provide QCL information for dedicated reception on the downlink shared channel (e.g., the Physical Downlink Shared Channel (PDSCH)) and for dedicated reception on all or a subset of the CORESET in the component carriers. For a separate uplink shared TCI state, source reference signals in N TCIs can provide references for determining one or more shared uplink transport space filters, based on dynamically granted or configured granted uplink shared channels (e.g., the Physical Uplink Shared Channel PUSCH) or dedicated uplink control channel resources (e.g., the Physical Uplink Control Channel PUCCH resources) in the component carriers. In some cases, the uplink transmission spatial filter can also be applied to all probe reference signal (SRS) resources in one or more resource sets configured for antenna switching, codebook-based uplink transmission, non-codebook-based uplink transmission, or a combination thereof.

[0110] For a unified TCI framework (e.g., a shared beam TCI state), the UE 115 may be explicitly or implicitly indicated to it that each type of TCI state can be applied to at least one set of multiple applicable channels (or reference signals). Additionally, TCI states may include the following types: A first TCI type may include a combined shared TCI state for uplink and downlink communication as described herein (e.g., a combined DL / UL shared TCI state) (e.g., to indicate a shared beam for at least one downlink channel or downlink reference signal plus at least one uplink channel or uplink reference signal). A second TCI type may include a separate downlink shared TCI state as described herein (e.g., to indicate a shared beam for at least two downlink channels or downlink reference signals). A third TCI type may include a separate uplink shared TCI state as described herein (e.g., to indicate a shared beam for at least two uplink channels or uplink reference signals). A fourth TCI type may include a separate downlink single-channel or downlink reference signal TCI state to indicate a beam for a single downlink channel or downlink reference signal. The fifth TCI type may include a separate uplink single channel or uplink reference signal RS TCI state to indicate the beam used for a single uplink channel or uplink reference signal.

[0111] In some cases, channels, reference signals, or both may be associated with a common beam TCI (e.g., a unified TCI framework). Channels and reference signals applicable to each TCI type may include the following candidates: UE-specific or UE-independent Physical Downlink Control Channel (PDCCH), PDSCH, PUCCH, PUSCH; Synchronization Signal / Physical Broadcast Channel Block (SSB), Periodic Channel State Information (CSI) Reference Signal (RS), Semi-periodic CSI-RS, Aperiodic CSI-RS, Periodic Positioning Reference Signal (PRS), Semi-periodic PRS, Aperiodic PRS; Periodic SRS, Semi-periodic SRS, Aperiodic SRS; or any combination thereof.

[0112] PDSCH, PUCCH, and PUSCH can be dynamically scheduled (e.g., via DCI), semi-statically activated (e.g., via DCI or MAC control element (CE)), or semi-statically configured (e.g., via RRC). PDSCH can implement a scheduling offset between DCI and PDSCH equal to or greater than a beam switching wait time threshold, or a scheduling offset less than a beam switching wait time threshold. Additionally, PDCCH can be carried by all or a subset of CORESET. CSI-RS can be used for CSI measurements and CSI reporting (when higher-level parameters such as Tracking Reference Signal (TRS) information or repetition parameters are not indicated), for beam measurements and reporting (when higher-level parameters for repetition are included), for TRS measurements (when higher-level parameters for TRS information are included), or combinations thereof. SRS can be used for antenna switching, beam management, codebook-based PUSCH, and non-codebook-based PUSCH. In some cases, PUCCH, SSB, CSI-RS, PRS, SRS, or combinations thereof can be all or a subset of the corresponding configured resources.

[0113] In some scenarios, base station 105 may use a DCI-based beam indication framework to indicate one or more TCI states for use by UE 115. For example, in a beam indication signaling medium used to support joint or individual downlink or uplink beam indication for a unified TCI framework, base station 105 and UE 115 may use at least UE-specific (e.g., unicast) DCIs to support Layer 1 (L1) based beam indication to indicate joint or individual downlink or uplink beam indications from active TCI states of UE 115. In some examples, DCI formats 1_1 and 1_2 may be used for this beam indication. Additionally, UE 115 may support mechanisms for confirming successful decoding of the beam indication. For example, confirmation feedback (e.g., positive ACK or negative ACK (NACK)) for a PDSCH scheduled by a DCI carrying the beam indication may be used as confirmation feedback also for the DCI.

[0114] Additionally or alternatively, base station 105 and UE 115 may support DCI-based carrier aggregation beam indication. For example, for a unified TCI framework, base station 105 and UE 115 may support shared TCI state identifier (ID) updates and activations to provide shared QCL information across configured component carrier sets, shared uplink transmission spatial filters, or both. This shared TCI state ID update and activation may be applied to in-band carrier aggregation, inter-band carrier aggregation, joint downlink / uplink beam indication, separate downlink and uplink beam indications, or combinations thereof. Furthermore, the shared TCI state ID may indicate that the same or a single reference signal determined according to the TCI states indicated by the shared TCI state ID can be used to provide QCL indication (e.g., QCL type D indication) and determine uplink transmission spatial filters across configured component carrier sets.

[0115] In some scenarios, base station 105 and UE 115 may use a timeline for the beam indication frame based on the DCI to determine when to begin using the beam indication frame (e.g., TCI state or beam) indicated by the DCI. For example, if a beam indication is received in the DCI, UE 115 may begin using one or more beams indicated by that beam indication in a first time slot (or a TTI of different lengths), the first time slot being at least X ms or Y symbols later than the DCI in which the beam indication (e.g., a combined downlink / uplink beam indication or a separate downlink / uplink beam indication) is received. Alternatively, if a beam indication is received in the DCI, UE 115 may begin using one or more beams indicated by that beam indication in a first time slot, the first time slot being at least X ms or Y symbols later than the UE 115 transmitting confirmation of the combined or separate downlink / uplink beam indication. Existing timing defined for DCI-based TCI or spatial relationship updates can be used for X and Y, or new timing can be defined for X and Y. Additionally, UE 115 and base station 105 may apply this delay in some scenarios (e.g., minimum indication delay) but not in others. For example, UE 115 and base station 105 may use this delay when the newly indicated beam is different from the previously indicated beam.

[0116] Additionally, UE 115 can use several padded NACK bits for feedback information transmission. If PDSCH parameters for the serving cell (e.g., PDSCH - Code Block Group Transmission) are provided to UE 115, UE 115 can receive the corresponding PDSCH including the code block group (CBG) of the transport block, scheduled by DCI format 1_1. Parameters configuring the number of available code blocks (e.g., maxCodeBlockGroupsPerTransportBlock) can also be provided to UE 115. The number of available code blocks indicates the maximum number of CBGs used to generate the corresponding HARQ-ACK information bits for the transport block received for the serving cell (e.g., ...).

[0117] If UE 115 correctly receives all code blocks of CBG, UE 115 can generate an ACK for the HARQ-ACK information bits of CBG; conversely, if the UE incorrectly receives at least one code block of CBG, UE 115 can generate a NACK for the HARQ-ACK information bits of CBG. In some examples, UE 115 can receive two transport blocks and can concatenate the HARQ-ACK information bits for the CBG of the second transport block after the HARQ-ACK information bits for the CBG of the first transport block. The HARQ-ACK codebook associated with PDSCH may include HARQ-ACK information bits (e.g., The total number of HARQ-ACK information bits, and if, for a transport block, the number of code block groups actually received by UE 115 is less than the total number (e.g., If this is the case, UE 115 can generate several HARQ-ACK information bits in the HARQ-ACK codebook to indicate incorrect reception of this transport block. The NACK value is (in bits). In some cases, the UE 115 may transmit such feedback to indicate the success or failure of the DCI-based TCI indication.

[0118] However, in some cases, the reception of joint or individual downlink / uplink beam indications (e.g., TCI from DCI) may be unclear due to the following issues. In some examples, UE 115 may successfully decode DCI, but decoding PDSCH may fail, such that a NACK bit transmitted for PDSCH does not necessarily mean that UE 115 failed to decode DCI. Alternatively, UE 115 may decode some portions of PDSCH while losing other portions (e.g., when PDSCH has multiple transport blocks (TBs) or code block groups (CBGs)). In other examples, UE 115 may transmit ACK for PDSCH, but base station 105 may fail to decode uplink control information carrying ACK (e.g., PUCCH failure or false detection of the last DCI). Alternatively, UE 115 may use other uplink transmissions (e.g., SRS or PUSCH) for scheduling. In these different scenarios, UE 115 may transmit a confirmation message that does not accurately convey whether the DCI carrying the beam indication has been successfully received.

[0119] The wireless communication system 100 may support techniques for the UE 115 to implicitly or explicitly acknowledge (e.g., in a DCI message) receiving a beam indication (or an indication of one or more TCI states), and subsequently, in addition to scheduling for receiving downlink channels, may use one or more beams indicated by the beam indication, along with other information. In some examples, the base station 105 may transmit a DCI message to the UE 115, the DCI message including a first indication of one or more TCI states for the UE 115 to use in communicating with the base station 105.

[0120] In some cases, UE 115 may transmit an ACK message for a downlink channel scheduled by a DCI carrying a unified TCI framework indication, to indicate successful reception of one or more TCI states. However, in some cases, UE 115 may successfully decode the DCI but may fail to decode the scheduled downlink channel, or the UE may partially decode the scheduled downlink channel.

[0121] To more accurately and reliably report the reception of one or more TCI indications, UE 115 may transmit an explicit or implicit ACK to base station 105 to confirm whether the indication for the unified TCI framework has been successfully received. In some examples, an ACK for the unified TCI framework may include transmitting an explicit ACK message, such as one or more ACK bits for a scheduled downlink channel, a dedicated ACK bit, or enhanced ACK information. In some other examples, the ACK may be an implicit ACK. For example, the implicit ACK may include transmitting ACK / NACK feedback for a downlink channel indicated in the same DCI as the beam indication. In some examples, the UE may receive multiple DCIs, and the UE may transmit an implicit indication of DCI reception by transmitting feedback for a PDSCH indicated in the same DCI as the beam indication.

[0122] Figure 2 Examples of a wireless communication network 200 supporting DCI-based unified TCI reception according to various aspects of this disclosure are explained. The wireless communication system 200 may implement various aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a base station 105-a and a UE 115-a, which may respectively represent as referred to in... Figure 1 Examples of base station 105 and UE 115 described. Additionally, base station 105-a and UE 115-a may support beamforming transmission (e.g., the beams used for beamforming transmission may correspond to different TCI states).

[0123] To support multi-beam-based operation for DCI transmission, wireless communication system 200 may support higher-layer configurations indicating one or more TCI states for each Control Resource Set (CORESET). UE 115-a may monitor a specific search space set associated with a CORESET, and UE 115-a may receive DCI (DCI) 205 on the Physical Downlink Control Channel (PDCCH) in that CORESET based on the TCI states configured for that CORESET. In some examples, DCI 205 may indicate scheduling of the Physical Downlink Shared Channel (PDSCH) 210 for communicating downlink data to UE 115-a. In some examples, DCI 205 may contain TCI states that UE 115-a can use to communicate with base station 105-b or other devices in the wireless network.

[0124] In some examples, UE 115-a may use the TCI state indicated in DCI 205 to determine beam information via the quasi-co-location (QCL) relationship between the downlink reference signal of the PDCCH (e.g., channel state information RS (CSI-RS) associated with the beam) and the demodulation reference signal (DMRS). In some cases, UE 115-a may be configured with multiple TCI states for CORESET. Each TCI state contains parameters for reference signal resources and the QCL relationship between the reference signal of the PDCCH and the DMRS port. For example, a TCI state may include at least one source reference signal to provide a reference for determining QCL assumptions or spatial filter information (e.g., UE assumptions). To receive DCI 205, UE 115-a uses the receiver beam configured by the previously applied TCI state activated for UE 115-a, or monitors the PDCCH during the monitoring of the search space set by using the beam used during the initial access procedure.

[0125] In some cases, the wireless communication network 200 may support reference Figure 1 The described unified TCI framework, wherein UE115-a can receive indications for one or more communication channels or reference signals that support different types of TCI states, such as a unified TCI state indicating a beam shared (e.g., shared) for at least one downlink channel or reference signal in addition to at least one uplink channel or reference signal.

[0126] like Figure 2 As shown in the example, base station 105-a may transmit DCI 205, which includes indications of one or more TCI states 220 for UE 115-a to use in communicating with base station 105-a (e.g., beam indication, unified TCI framework indication, combined downlink / uplink beam indication, individual downlink / uplink beam indication). DCI 205 may indicate which TCI states 220 are available for use by UE 115-a and may correspond to one or more uplink transmissions transmitted by UE 115-a. For example, uplink transmissions may be one or more PUCCH transmissions, one or more SRS transmissions, one or more CSI reports, ACK / NACK feedback for PDSCH, acknowledgment message transmissions for configured permission activation indications, configured permission PUSCH transmissions, or combinations thereof.

[0127] In some examples, the wireless communication system 200 may support various explicit or implicit acknowledgments for a unified TCI indication (or a unified TCI framework indication). For example, for a beam indication (e.g., an L1-based beam indication) that uses at least a UE-specific (e.g., unicast) DCI (e.g., DCI 205) to indicate the active TCI state of UE 115-a, either a joint or individual downlink / uplink beam indication (e.g., a unified TCI indication or a unified TCI framework indication), UE 115-a may apply the beam indication after transmitting an acknowledgment 215 for the joint or individual downlink / uplink beam indication. For example, acknowledgment 215 may include transmitting one or more ACK bits for PDSCH 210 to explicitly indicate that at least DCI 205 was correctly received by UE 115-a. In some other examples, UE 115-a can indicate successful reception of DCI 205 by using several padded ACK bits configured for PDSCH 210 to explicitly indicate that at least DCI 205 has been correctly received by UE 115-a. In some examples, UE 115-a can use dedicated ACK bits associated with the HARQ Type 1 codebook (e.g., ACK bits specific to acknowledging DCI 205) to explicitly indicate that at least DCI 205 has been correctly received by UE 115-a.

[0128] In some other examples, acknowledgment 215 can be implicit. For example, implicit indication of DCI reception may include transmitting ACK / NACK feedback for the PDSCH indicated in the same DCI as the beam indication. In some examples, UE 115-a may receive multiple DCIs 205, and UE 115-a may transmit implicit indication of reception of DCI 205 by transmitting feedback for the PDSCH indicated in the same DCI as the beam indication. By providing explicit or implicit acknowledgment 215 for the combined downlink / uplink beam indication or individual downlink / uplink beam indications, UE 115-a and base station 105-a can more efficiently detect whether the corresponding beam indication has been successfully received. Accordingly, incorporating both explicit and implicit acknowledgment of TCI state 220 reception as described herein can reduce latency and improve communication reliability, among other benefits.

[0129] Figure 3 An example of a process flow 300 supporting DCI-based unified TCI recognition, based on various aspects of this disclosure, is explained. Process flow 300 can implement... Figure 1-2 All aspects. For example, UE 115-b and base station 105-a (they can be references) Figure 1-2The described example of UE 115 and base station 105 enables the process of process flow 300 to determine when UE 115-b begins using one or more TCI states (e.g., beams) indicated by base station 105-b for communicating with base station 105-b. In some examples, the one or more TCI states may correspond to a unified TCI framework indicating a shared beam that can be used by UE 115-b for at least one uplink channel (or uplink reference signal) and for at least one downlink channel (or downlink reference signal), a shared beam that can be used by UE 115-b for at least two downlink channels (or downlink reference signals), or a shared beam that can be used by UE 115-b for at least two uplink channels (or uplink reference signals). UE 115-b may begin using the one or more TCI states after receiving confirmation of the DCI and the one or more TCI states.

[0130] At 305, UE 115-b can operate according to a first TCI state. For example, UE 115-b can operate using a TCI state indicated by a first DCI received from base station 105-b during a previous transmission time interval.

[0131] At 310, base station 105-b may transmit a DCI to UE 115-b, and the DCI may include a first indication of one or more TCI states for UE 115-b to use in communicating with base station 105-b, such as an indication of a unified TCI state. In some examples, the DCI may further include additional indications of scheduled downlink channel transmissions (e.g., PDSCH) or one or more uplink channels scheduled for transmission by UE 115. Based on the indications received in the DCI, at 315, UE 115-b may receive (or attempt to receive) downlink transmissions (e.g., PDSCH) from base station 105-b on several transport blocks or code block groups configured for downlink transmissions.

[0132] In some cases, UE 115-b may correctly receive both the DCI indicating the state of one or more TCIs and the PDSCH, or in other cases, UE 115-b may correctly receive the DCI indicating the state of one or more TCIs while incorrectly receiving the PDSCH. In either case, UE 115-a may transmit an acknowledgment (e.g., a positive ACK bit) at 320 to explicitly acknowledge the reception of the DCI, including the state of one or more TCIs.

[0133] In the first scenario, the PDSCH can be transmitted within a single transport block (e.g., a single TB PDSCH), and UE 115-b can transmit a positive ACK bit 325 as an acknowledgment of reception of the PDSCH scheduled by that DCI. In this scenario, the single positive ACK bit 325 associated with the PDSCH can at least explicitly indicate reception of the DCI and one or more TCI states indicated in the same DCI. In some examples, the single positive ACK bit 325 can be transmitted on a PUCCH scheduled by that DCI. In some other examples, the single positive ACK bit 325 can be multiplexed on a PUSCH. For example, the positive ACK bit 325 can be a positive acknowledgment (ACK) where the HARQ-ACK information bit value is 1.

[0134] In the second scenario, PDSCH can be transmitted across multiple transport blocks (e.g., multiple TB PDSCHs), and UE 115-b can transmit at least one positive ACK bit 325 for the PDSCH scheduled by the DCI. This at least one positive ACK bit can be an acknowledgment of reception for any of the multiple transport blocks scheduled by the DCI, which also indicates the one or more TCI states. In such a scenario, the at least one positive ACK bit 325 associated with the PDSCH can explicitly indicate at least reception of the DCI and the one or more TCI states. In some examples, the number of ACK bits 325 transmitted by UE 115-b can depend on the number of transport blocks transmitting the PDSCH. In some examples, at least one positive ACK bit 325 can be transmitted on the PUCCH scheduled by the DCI. In some other examples, a single positive ACK bit 325 can be multiplexed on the PUSCH. For example, the positive ACK bit 325 can be a positive acknowledgment (ACK) where the HARQ-ACK information bit value is 1.

[0135] In the third scenario, the PDSCH may be configured with multiple CBGs (e.g., multi-CBG PDSCH), and the UE 115-b may transmit at least one positive ACK bit 325 for the PDSCH scheduled by the DCI. This at least one positive ACK bit may be an acknowledgment of reception for any of the multiple CBGs scheduled by the DCI, which also indicates one or more TCI states. In this scenario, the at least one positive ACK bit 325 associated with the PDSCH may explicitly indicate at least reception of the DCI and the one or more TCI states. In some examples, the number of ACK bits 325 transmitted by the UE 115-b may depend on the number of CBGs configured for the PDSCH. In some examples, at least one positive ACK bit 325 may be transmitted on the PUCCH scheduled by the DCI. In some other examples, a single positive ACK bit 325 may be multiplexed on the PUSCH. For example, the positive ACK bit 325 may be a positive acknowledgment (ACK) where the HARQ-ACK information bit value is 1.

[0136] In the fourth scenario, UE 115-b may indicate the DCI detection status in enhanced ACK information associated with a Type 2 HARQ codebook (e.g., enhanced ACK PDSCH). In this scenario, the enhanced ACK information may include an indication of successful DCI reception, explicitly acknowledging the one or more TCI states (via one or more fields or other portions of the ACK information). In some examples, the enhanced ACK information may be transmitted based on a Type 2 HARQ codebook associated with the PDSCH. In some examples, the enhanced ACK information may be transmitted on a PUCCH scheduled by the DCI. In some other examples, the enhanced ACK information may be multiplexed on a PUSCH.

[0137] Additionally or alternatively, UE 115-b may use multiple padded ACK bits to explicitly acknowledge successful DCI reception, including the one or more TCI states. For example, UE 115-b may receive parameters from base station 105-b via RRC signaling that enable padded ACK bits associated with the HARQ codebook (e.g., "ACK-padding-forTCI"). In cases where one or more code block groups are used to transmit PDCCH (e.g., ACK padding into CBG), when PDSCH is configured with a number of... When HARQ-ACK information bits are used, if for a transport block in the scheduled PDSCH, The padded ACK bits can then be associated with the PDSCH. If a beam indication is received, the UE 115-b can generate the final transport block for the scheduled PDSCH in the HARQ-ACK codebook. The ACK value of each HARQ-ACK information bit.

[0138] In some other cases, UE 115-b may monitor PDCCH with DCI format 1_0 or DCI format 1_0 in the active downlink bandwidth portion of the serving cell or other allocated resources, or the timing for candidate PDSCH reception may be in response to PDCCH with DCI format 1_1. In such a scenario, if no higher-level parameter (e.g., harq-ACK-SpatialBundlingPUCCH) is provided associated with the spatial bundle of HARQ information bits and a maximum number of two codewords is configured (e.g., by maxNrofCodeWordsScheduledByDCI = 2), then UE 115-b can use one transport block to receive PDSCH to explicitly indicate the reception of DCI and one or more associated TCI states. HARQ-ACK information can be associated with the first transport block, and UE 115-b can generate an ACK value for a second transport block of PDSCH to send to base station 105-b.

[0139] At 330, UE 115-b may apply the one or more TCI states (e.g., including at least a second TCI state different from the first TCI state) after transmitting an ACK 325 indicating successful reception of the DCI and the one or more TCI states via PDSCH.

[0140] Figure 4 An example of a process flow 400 supporting DCI-based unified TCI recognition, based on various aspects of this disclosure, is explained. Process flow 400 can implement... Figure 1-3 All aspects. For example, UE 115-c and base station 105-c (they can be referenced) Figure 1-3The described example of UE 115 and base station 105 enables the process of process flow 300 to determine when UE 115-c begins using one or more TCI states (e.g., beams) indicated by base station 105-c for communicating with base station 105-c. In some examples, the one or more TCI states may correspond to a unified TCI framework indicating a shared beam that can be used by UE 115-c for at least one uplink channel (or uplink reference signal) and for at least one downlink channel (or downlink reference signal), a shared beam that can be used by UE 115-c for at least two downlink channels (or downlink reference signals), or a shared beam that can be used by UE 115-c for at least two uplink channels (or uplink reference signals). UE 115-c may begin using the one or more TCI states after receiving confirmation of the DCI and the one or more TCI states.

[0141] At 405, UE 115-c can operate according to a first TCI state. For example, UE 115-c can operate using a TCI state indicated by a first DCI received from base station 105-c during a previous transmission time interval.

[0142] At 410, base station 105-c may transmit a DCI to UE 115-c, and the DCI may include a first indication of one or more TCI states for UE 115-c to use in communicating with base station 105-c, such as an indication of a unified TCI state. In some examples, the DCI may further include additional indications of scheduled downlink channel transmissions (e.g., PDSCH) or one or more uplink channels scheduled for transmission by UE 115-c. Based on the indications received in the DCI, at 415, UE 115-c may receive (or attempt to receive) downlink transmissions (e.g., PDSCH) from base station 105-c on several transport blocks or code block groups configured for downlink transmissions.

[0143] In some cases, UE 115-c may correctly receive both the DCI indicating the state of one or more TCIs and the PDSCH, or in other cases, UE 115-c may correctly receive the DCI indicating the state of one or more TCIs while incorrectly receiving the PDSCH. In either case, UE 115-c may transmit an acknowledgment (e.g., a positive ACK bit) at 320 to explicitly acknowledge the reception of the DCI, including the state of one or more TCIs.

[0144] At 420, UE 115-c can transmit confirmation 425 for a combined or individual downlink / uplink beam indication of one or more TCI states received in the DCI. In some examples, this confirmation may be a dedicated ACK bit associated with the one or more TCI states (e.g., the ACK bit may specifically indicate successful reception of the one or more TCI states). Confirmation 425 can be transmitted according to the Type I HARQ codebook of the scheduled PDSCH. In some cases, for the timing of scheduled PDSCH reception, a dedicated ACK bit is indicated in one or more DCI formats (e.g., DCI 1_1 or DCI 1_2) to indicate confirmation of the TCI indication in the DCI.

[0145] At 430, UE 115-c may apply the one or more TCI states (e.g., including at least a second TCI state different from the first TCI state) after transmitting an ACK 425 indicating successful reception of the DCI and one or more TCI states indicated in the same DCI.

[0146] Figure 5 An example of process flow 500 based on DCI and supporting unified TCI recognition is explained according to various aspects of this disclosure. Process flow 500 can implement Figure 1-4 All aspects. For example, UE 115-d and base station 105-d (they can be references) Figure 1-4 The described example of UE 115 and base station 105 enables a process flow 500 to determine when UE 115-d begins using one or more TCI states (e.g., beams) indicated by base station 105-d for communicating with base station 105-d. In some examples, the one or more TCI states may correspond to a unified TCI framework indicating a shared beam that can be used by UE 115-d for at least one uplink channel (or uplink reference signal) and for at least one downlink channel (or downlink reference signal), a shared beam that can be used by UE 115-d for at least two downlink channels (or downlink reference signals), or a shared beam that can be used by UE 115-d for at least two uplink channels (or uplink reference signals). UE 115-d may begin using the one or more TCI states after receiving confirmation of the DCI and the one or more TCI states.

[0147] At 505, UE 115-d can operate according to a first TCI state. For example, UE 115-d can operate using a TCI state indicated by a first DCI received from base station 105-d during a previous transmission time interval.

[0148] At 510, base station 105-d may transmit a DCI to UE 115-d, and the DCI may include a first indication of one or more TCI states for UE 115-d to use in communicating with base station 105-d, such as an indication of a unified TCI state. In some examples, the DCI may further include additional indications of scheduled downlink channel transmissions (e.g., PDSCH), and downlink assignment indices associated with the downlink channels, or one or more uplink channels scheduled for transmission by UE 115-d (e.g., PUCCH). Based on the indications received in the DCI, at 515, UE 115-d may receive (or attempt to receive) downlink transmissions (e.g., PDSCH) from base station 105-d.

[0149] In some cases, UE 115-d may correctly receive both the DCI indicating the state of one or more TCIs and the PDSCH; in other cases, UE 115-d may correctly receive the DCI indicating the state of one or more TCIs while incorrectly receiving the PDSCH. In either case, UE 115-d may transmit an acknowledgment at 520, which implicitly acknowledges the reception of the DCI, including the state of one or more TCIs.

[0150] In some scenarios, UE 115-d and base station 105-d may use PUCCH transmissions as implicit acknowledgments of successful reception of one or more TCI states. For example, the DCI may indicate resources used for PUCCH transmissions carrying a HARQ codebook associated with PDSCH feedback. In some scenarios, the HARQ codebook carried by the PUCCH transmission includes ACK / NACK bits 525 associated with the scheduled PDSCH. In such examples, base station 105-d may interpret any PUCCH transmission for the PDSCH (e.g., regardless of whether ACK / NACK bits 525 are ACK or NACK bits) as implicit acknowledgments of successful reception of the DCI.

[0151] Alternatively, the resources used for PUCCH transmission may be uniquely indicated based on a DCI carrying one or more TCI states. For example, if base station 105-d receives a PUCCH on one or more resources indicated by the DCI, base station 105-d may interpret the received PUCCH as an implicit acknowledgment of successful reception of one or more TCI states.

[0152] At 530, UE 115-d may apply the one or more TCI states (e.g., including at least a second TCI state different from the first TCI state) after transmitting a NACK 525 of the PDSCH indicating successful reception of the DCI and the one or more TCI states.

[0153] Figure 6 An example of a process flow 600 supporting DCI-based unified TCI recognition, based on various aspects of this disclosure, is explained. Process flow 600 can implement... Figure 1-5 All aspects. For example, UE 115-e and base station 105-e (they can be references) Figure 1-5 The described example of UE 115 and base station 105 enables a process flow 600 to determine when UE 115-e begins using one or more TCI states (e.g., beams) indicated by base station 105-e for communicating with base station 105-e. In some examples, the one or more TCI states may correspond to a unified TCI framework indicating a shared beam that can be used by UE 115-e for at least one uplink channel (or uplink reference signal) and for at least one downlink channel (or downlink reference signal), a shared beam that can be used by UE 115-e for at least two downlink channels (or downlink reference signals), or a shared beam that can be used by UE 115-e for at least two uplink channels (or uplink reference signals). UE 115-e may begin using the one or more TCI states after receiving confirmation of the DCI and the one or more TCI states.

[0154] At 605, UE 115-e can operate according to a first TCI state. For example, UE 115-e can operate using a TCI state indicated by a first DCI received from base station 105-e during a previous transmission time interval.

[0155] At 610, base station 105-e may transmit a first DCI to UE 115-e, and at 615, base station 105-e may transmit a second DCI. In some cases, the second DCI may include a first indication of one or more TCI states for UE 115-e to communicate with base station 105-e, such as an indication of a unified TCI state. In some examples, the second DCI may further include additional indications of one or more uplink channels scheduled for transmission on downlink channels (e.g., PDSCH) and associated downlink assignment indices, or scheduled for transmission by UE 115-e (e.g., PUCCH). Based on the indication received in the DCI, at 620, UE 115-e may receive (or attempt to receive) downlink transmissions (e.g., PDSCH) from base station 105-e. In some examples, in addition to the first and second DCIs, base station 105-e may also transmit additional DCIs. In some cases, a second DCI may refer to the "last" received DCI among the DCIs indicating the same transmission resource used for HARQ codebook information, or the latest received DCI among the received DCIs.

[0156] In some cases, UE 115-e may correctly receive the PDSCH and the second DCI indicating the state of the one or more TCIs, or in other cases, UE 115-e may correctly receive the DCI indicating the state of the one or more TCIs while incorrectly receiving the PDSCH. In either case, UE 115-e may transmit an acknowledgment at 625, which may implicitly acknowledge the reception of the second DCI, including the state of the one or more TCIs.

[0157] In some scenarios, UE 115-e and base station 105-e may use PUCCH transmissions as implicit acknowledgments of successful reception of one or more TCI states included in the second DCI. For example, the second DCI may indicate resources used for PUCCH transmissions and the HARQ codebook associated with PDSCH feedback. In some scenarios, the HARQ codebook of the PUCCH transmission carries ACK / NACK bits 630 associated with the scheduled PDSCH. In such examples, base station 105-e may interpret any PUCCH transmission (e.g., ACK or NACK) for the PDSCH as an implicit acknowledgment of successful reception of the second DCI and the one or more TCI states.

[0158] Additionally or alternatively, the resources used for PUCCH transmission may be uniquely indicated based on a second DCI carrying one or more TCI states. For example, if base station 105-e receives a PUCCH on one or more resources indicated by the second DCI, base station 105-e may interpret the received PUCCH as an implicit acknowledgment of successful reception of one or more TCI states. In some cases, base station 105-e may further identify DCI false detections to correctly receive the HARQ codebook sent by the UE associated with the PDSCH.

[0159] At 635, UE 115-e may apply the one or more TCI states (e.g., including at least a second TCI state different from the first TCI state) after transmitting a NACK 630 to PDSCH indicating successful reception of the second DCI and the one or more TCI states.

[0160] Figure 7 An example of a process flow 700 supporting DCI-based unified TCI recognition, based on various aspects of this disclosure, is explained. Process flow 700 can implement... Figure 1-6 All aspects. For example, UE 115-f and base station 105-f (they can be references) Figure 1-6 The described example of UE 115 and base station 105 enables a process flow 700 to determine when UE 115-f begins using one or more TCI states (e.g., beams) indicated by base station 105-f for communicating with base station 105-f. In some examples, the one or more TCI states may correspond to a unified TCI framework indicating a shared beam that can be used by UE 115-f for at least one uplink channel (or uplink reference signal) and for at least one downlink channel (or downlink reference signal), a shared beam that can be used by UE 115-f for at least two downlink channels (or downlink reference signals), or a shared beam that can be used by UE 115-f for at least two uplink channels (or uplink reference signals). UE 115-f may begin using the one or more TCI states after receiving confirmation of the DCI and the one or more TCI states.

[0161] At 705, UE 115-f can operate according to a first TCI state. For example, UE 115-f can operate using a TCI state indicated by a first DCI received from base station 105-f during a previous transmission time interval.

[0162] In some scenarios, UE 115-f may receive multiple DCIs (e.g., DCI1, DCI2, DCI3) from base station 105-f. These DCIs may be associated with several different downlink assignment indices, TCI states, HARQ codebooks, and other information. UE 115-f can determine the last transmitted DCI (e.g., DCI3) and can use the information in the last DCI to transmit feedback to base station 105-f. However, in some scenarios, UE 115-f may experience false detection of the last DCI and may transmit PUCCH and HARQ codebooks based on previously received DCIs (e.g., DCI2 or DCI1). If UE 115-f determines to send feedback associated with (e.g., on associated PDSCH1) the first DCI, such feedback may prompt UE 115-f to apply the TCI indication associated with the first DCI (e.g., TCI1). In such scenarios, base station 105-f may not be able to determine whether the first DCI has been received. Base station 105-f can reschedule PDSCH, including rescheduling the last DCI (e.g., DCI3) which includes the TCI indication associated with the last DCI (e.g., TCI3). However, such scenarios may pose challenges for UE 115-f in determining which TCI state to apply (e.g., TCI1 or TCI3) or which TCI state is valid.

[0163] For Layer 1 beamforming, which uses at least a UE-specific (e.g., unicast) DCI to indicate joint or individual downlink / uplink beamforming for active TCI states, base station 105-f can determine reception failure for one or more TCI states across multiple DCIs. Additionally, base station 105-f can indicate these one or more TCI states in the DCIs that schedule the initial transmission and retransmission of the PDSCH. In some examples, base station 105-f can transmit the same uniform TCI state in different DCIs until acknowledgment is received from UE 115-f.

[0164] Base station 105-f may transmit a first DCI (DCI1) with a unified TCI state at 710, followed by a second DCI (DCI2) with a unified TCI state at 715, and a third DCI (DCI3) with a unified TCI state at 720. In some examples, in addition to the first, second, and third DCIs, base station 105-f may also transmit additional DCIs. Based on the indication received in this DCI, at 725, UE 115-f may receive (or attempt to receive) downlink transmissions (e.g., PDSCH) from base station 105-f.

[0165] At 730, UE 115-f may transmit an acknowledgment (e.g., implicit or explicit acknowledgment as described herein) to acknowledge receipt of at least one DCI. In some cases, this acknowledgment may be a HARQ message 735 for DCI1, DCI2, or DCI3.

[0166] In 735, UE 115-f may apply one or more TCI states (e.g., including at least a second TCI state different from the first TCI state) after successful reception of transmission indication at least one DCI and one or more TCI states.

[0167] Figure 8 A block diagram 800 of a device 805 supporting DCI-based Unified TCI reception is shown according to various aspects of this disclosure. Device 805 may be an example of various aspects of UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communications manager 820. Device 805 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0168] Receiver 810 may provide means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to DCI-based Unified TCI reception). The information may be transmitted to other components of device 805. Receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0169] Transmitter 815 may provide means for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to DCI-based Unified TCI acknowledgment), user data, control information, or any combination thereof. In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0170] The communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of DCI-based unified TCI reception as described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or components thereof, may support methods for performing one or more functions described herein.

[0171] In some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). This hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to serve as or otherwise support means for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory by the processor).

[0172] Additionally or alternatively, in some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented by processor-executable code (e.g., as communication management software or firmware). If implemented by processor-executable code, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by a general-purpose processor, DSP, central processing unit (CPU), ASIC, FPGA, or any combination of these or other programmable logic devices (e.g., means configured or otherwise supported for performing the functions described in this disclosure).

[0173] In some examples, the communication manager 820 may be configured to use or otherwise cooperate with the receiver 810, transmitter 815, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, the communication manager 820 may receive information from the receiver 810, send information to the transmitter 815, or be integrated with the receiver 810, transmitter 815, or both to receive information, transmit information, or perform various other operations described herein.

[0174] According to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. For example, the communication manager 820 may be configured or otherwise support means for: receiving from a base station a DCI scheduling downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel. The communication manager 820 may be configured or otherwise support means for: transmitting to the base station a feedback message for the downlink shared channel, wherein the feedback message acknowledges receipt of the TCI state. The communication manager 820 may be configured or otherwise support means for: applying the TCI state after transmitting the feedback message acknowledging receipt of the TCI state.

[0175] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., a processor that controls or otherwise couples to receiver 810, transmitter 815, communication manager 820, or a combination thereof) can support technologies for more efficient use of communication resources and higher reliability associated with the reception of TCI information transmitted in DCI.

[0176] Figure 9 A block diagram 900 of a device 905 supporting DCI-based Unified TCI reception is shown according to various aspects of this disclosure. Device 905 may be an example of a device 805 or a UE 115 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. Device 905 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0177] Receiver 910 may provide means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to DCI-based Unified TCI reception). The information may be transmitted to other components of device 905. Receiver 910 may utilize a single antenna or a collection of multiple antennas.

[0178] Transmitter 915 may provide means for transmitting signals generated by other components of device 905. For example, transmitter 915 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to DCI-based Unified TCI acknowledgment), user data, control information, or any combination thereof. In some examples, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0179] Device 905 or its various components may be examples of means for performing various aspects of unified TCI acknowledgment based on DCI as described herein. For example, communication manager 920 may include DCI receiving component 925, feedback transmission component 930, TCI status application component 935, or any combination thereof. Communication manager 920 may be examples of various aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use or otherwise cooperate with receiver 910, transmitter 915, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, communication manager 920 may receive information from receiver 910, send information to transmitter 915, or be integrated with receiver 910, transmitter 915, or both to receive information, transmit information, or perform various other operations described herein.

[0180] According to the examples disclosed herein, the communication manager 920 can support wireless communication at the UE. The DCI receiving component 925 can be configured or otherwise supported to support means for receiving from a base station a DCI scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel. The feedback transmission component 930 can be configured or otherwise supported to transmit to the base station a feedback message for the downlink shared channel, wherein the feedback message acknowledges the reception of the TCI state. The TCI state application component 935 can be configured or otherwise supported to apply the TCI state after transmitting the feedback message acknowledging the reception of the TCI state.

[0181] Figure 10 A block diagram 1000 of a communication manager 1020 supporting DCI-based unified TCI acknowledgment according to various aspects of this disclosure is shown. The communication manager 1020 may be an example of the communication manager 820, communication manager 920, or aspects thereof described herein. The communication manager 1020 or its various components may be examples of means for performing various aspects of DCI-based unified TCI acknowledgment as described herein. For example, the communication manager 1020 may include a DCI receiving component 1025, a feedback transmission component 1030, a TCI status application component 1035, a PDSCH payload component 1040, a feedback generation component 1045, an RRC component 1050, a TCI status identification component 1055, an uplink resource identification component 1060, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0182] According to the examples disclosed herein, the communication manager 1020 can support wireless communication at the UE. The DCI receiving component 1025 can be configured or otherwise supported to support means for receiving from a base station a DCI scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel. The feedback transmission component 1030 can be configured or otherwise supported to transmit to the base station a feedback message for the downlink shared channel, wherein the feedback message acknowledges the reception of the TCI state. The TCI state application component 1035 can be configured or otherwise supported to apply the TCI state after transmitting the feedback message acknowledging the reception of the TCI state.

[0183] In some examples, the PDSCH payload component 1040 may be configured or otherwise supported as means for determining that the payload of the downlink shared channel comprises a single transport block. In some examples, the feedback transmission component 1030 may be configured or otherwise supported as means for transmitting a single affirmative acknowledgment bit for the downlink shared channel to the base station based on the determination to acknowledge receipt of the TCI state.

[0184] In some examples, the PDSCH payload component 1040 may be configured or otherwise supported for determining that the payload of the downlink shared channel includes more than one transport block. In some examples, the feedback transmission component 1030 may be configured or otherwise supported for transmitting at least one positive confirmation bit for the downlink shared channel to the base station based on the determination to confirm reception of the TCI state.

[0185] In some examples, the PDSCH payload component 1040 may be configured or otherwise support means for determining that the downlink shared channel is configured with one or more code block groups. In some examples, the feedback transmission component 1030 may be configured or otherwise support means for transmitting at least one positive confirmation bit for the downlink shared channel to the base station based on the determination to confirm reception of the TCI state.

[0186] In some examples, the feedback generation component 1045 may be configured or otherwise supported as an means for generating the feedback message as an enhanced confirmation message, the enhanced confirmation message including a set of affirmative confirmation bits. In some examples, the feedback transmission component 1030 may be configured or otherwise supported as an means for transmitting the enhanced confirmation message to the base station based on the generation to confirm the reception of the TCI state. In some examples, the enhanced confirmation message is associated with a HARQ Type II codebook.

[0187] In some examples, the RRC component 1050 may be configured or otherwise support means for receiving from the base station via radio resource control messages an indication of reception of the feedback message for the downlink shared channel, including an acknowledgement bit set and an additional padded bit set to acknowledge the TCI state.

[0188] In some examples, to support the transmission of the feedback message, the feedback generation component 1045 may be configured or otherwise supported to allocate an additional padded bit set to a portion of the codebook used for the downlink shared channel, the additional padded bit set indicating a confirmed reception value. In some examples, to support the transmission of the feedback message, the feedback transmission component 1030 may be configured or otherwise supported to transmit to the base station at least an additional padded bit set allocated to a portion of the codebook to confirm the reception of the TCI state.

[0189] In some examples, the payload of the downlink shared channel includes more than one transport block, and the feedback transmission component 1030 may be configured or otherwise support means for transmitting to the base station a first affirmative acknowledgment bit for a first transport block, the first affirmative acknowledgment bit indicating reception of the downlink shared channel. In some examples, the payload of the downlink shared channel includes more than one transport block, and the feedback transmission component 1030 may be configured or otherwise support means for transmitting to the base station a second affirmative acknowledgment bit for a second transport block, the second affirmative acknowledgment bit indicating reception of both the downlink shared channel and the DCI.

[0190] In some examples, the feedback generation component 1045 may be configured or otherwise supported as an means for generating a single affirmative acknowledgment bit dedicated to the DCI based on a HARQ Type I codebook. In some examples, the feedback transmission component 1030 may be configured or otherwise supported as an means for transmitting a feedback message, including the single affirmative acknowledgment bit, to the base station based on the generation to acknowledge receipt of the TCI state.

[0191] In some examples, the feedback transmission component 1030 may be configured or otherwise support means for transmitting the feedback message to the base station using an uplink control channel resource set associated with the downlink shared channel, wherein the feedback message includes a first acknowledgment of reception of the downlink shared channel and a second acknowledgment of reception of the TCI state. In some examples, the TCI state application component 1035 may be configured or otherwise support means for applying the TCI state after transmitting the feedback message, wherein the feedback message indicates reception of the TCI state.

[0192] In some examples, the uplink control channel resource set is configured with a set of HARQ bits for transmitting feedback messages associated with the downlink shared channel. In some examples, the uplink control channel resource set is indicated by the DCI.

[0193] In some examples, to support the transmission of the feedback message, the TCI status identification component 1055 may be configured or otherwise supported to determine whether the DCI includes a TCI status indicating the shared beam. In some examples, to support the transmission of the feedback message, the uplink resource identification component 1060 may be configured or otherwise supported to identify the uplink control channel resource set in the DCI for transmitting the feedback message based on the inclusion of the TCI status in the DCI. In some examples, to support the transmission of the feedback message, the feedback transmission component 1030 may be configured or otherwise supported to transmit the feedback message to the base station using the uplink control channel resource set to acknowledge receipt of the TCI status.

[0194] In some examples, the TCI status identification component 1055 may be configured or otherwise supported as means for determining whether a TCI status indicating the shared beam is included in the DCI and the at least one other DCI. In some examples, the feedback transmission component 1030 may be configured or otherwise supported as means for transmitting the feedback message to the base station using the uplink control channel resource set to acknowledge receipt of the TCI status, or using a separate uplink control channel resource set to transmit the feedback message to the base station to acknowledge receipt of the at least one other DCI.

[0195] In some examples, the DCI includes a TCI state indicating the shared beam, based on the fact that the DCI is received after at least one other DCI. In some examples, the TCI state indicates a joint indication or a separate indication for the at least one channel. In some examples, the TCI state indicating the shared beam includes a Layer 1 (L1) based beam indication.

[0196] Figure 11 A diagram of a system 1100 including device 1105 supporting DCI-based Unified TCI reception is shown according to various aspects of this disclosure. Device 1105 may be an example of device 805, device 905, or UE 115 as described herein, or a component including device 805, device 905, or UE 115. Device 1105 may wirelessly communicate with one or more base stations 105, UE 115, or any combination thereof. Device 1105 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, a memory 1130, a code 1135, and a processor 1140. These components may be in electronic communication or otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1145).

[0197] I / O controller 1110 manages the input and output signals of device 1105. I / O controller 1110 can also manage peripheral devices not integrated into device 1105. In some cases, I / O controller 1110 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1110 may utilize an operating system, such as... MS- MS- Or another known operating system. Additionally or alternatively, the I / O controller 1110 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1110 may be implemented as part of a processor (such as processor 1140). In some cases, a user may interact with device 1105 via the I / O controller 1110 or via hardware components controlled by the I / O controller 1110.

[0198] In some cases, device 1105 may include a single antenna 1125. However, in other cases, device 1105 may have more than one antenna 1125, which may be capable of transmitting or receiving multiple wireless transmissions concurrently. Transceiver 1115 may communicate bidirectionally via one or more antennas 1125, wired or wireless links, as described herein. For example, transceiver 1115 may represent a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. Transceiver 1115 may also include a modem for modulating packets and providing modulated packets to one or more antennas 1125 for transmission, and for demodulating packets received from one or more antennas 1125. Transceiver 1115, or transceiver 1115 and one or more antennas 1125, may be an example of transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination thereof or components thereof as described herein.

[0199] Memory 1130 may include random access memory (RAM) and read-only memory (ROM). Memory 1130 may store computer-readable, computer-executable code 1135, including instructions that, when executed by processor 1140, cause device 1105 to perform the various functions described herein. Code 1135 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, code 1135 may not be directly executable by processor 1140, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, memory 1130 may, in particular, include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0200] Processor 1140 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1140 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1140. Processor 1140 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1130) to cause device 1105 to perform various functions (e.g., supporting various functions or tasks of DCI-based unified TCI recognition). For example, device 1105 or components thereof may include processor 1140 and memory 1130 coupled to processor 1140, wherein processor 1140 and memory 1130 are configured to perform the various functions described herein.

[0201] According to the examples disclosed herein, the communication manager 1120 may support wireless communication at the UE. For example, the communication manager 1120 may be configured or otherwise support means for: receiving from a base station a DCI scheduling downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel. The communication manager 1120 may be configured or otherwise support means for: transmitting to the base station a feedback message for the downlink shared channel, wherein the feedback message acknowledges the reception of the TCI state. The communication manager 1120 may be configured or otherwise support means for: applying the TCI state after transmitting the feedback message acknowledging the reception of the TCI state.

[0202] By including or configuring a UE communication manager 1120 according to an example as described herein, device 1105 can support techniques for improved communication reliability, reduced latency, more efficient utilization of communication resources, and improved inter-device coordination. For example, excessive retransmissions of DCI can be reduced based on implicit or explicit acknowledgment of the reception of TCI in DCI.

[0203] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the transceiver 1115, one or more antennas 1125, or any combination thereof. Although the communication manager 1120 is described as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the processor 1140, memory 1130, code 1135, or any combination thereof. For example, code 1135 may include instructions that can be executed by the processor 1140 to cause the device 1105 to perform various aspects of the DCI-based Unified TCI acknowledgment as described herein, or the processor 1140 and memory 1130 may be otherwise configured to perform or support such operations.

[0204] Figure 12 A block diagram 1200 of a device 1205 supporting DCI-based Unified TCI reception is shown according to various aspects of this disclosure. Device 1205 may be an example of various aspects of base station 105 as described herein. Device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. Device 1205 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0205] Receiver 1210 may provide means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to DCI-based Unified TCI reception). The information may be transmitted to other components of device 1205. Receiver 1210 may utilize a single antenna or a collection of multiple antennas.

[0206] Transmitter 1215 may provide means for transmitting signals generated by other components of device 1205. For example, transmitter 1215 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to DCI-based Unified TCI acknowledgment), user data, control information, or any combination thereof. In some examples, transmitter 1215 may be co-located with receiver 1210 in a transceiver module. Transmitter 1215 may utilize a single antenna or a collection of multiple antennas.

[0207] The communication manager 1220, receiver 1210, transmitter 1215, or various combinations thereof, or various components thereof, may be examples of apparatuses for performing various aspects of DCI-based unified TCI reception as described herein. For example, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations thereof, or components thereof, may support methods for performing one or more functions described herein.

[0208] In some examples, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include processors, DSPs, ASICs, FPGAs, or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured or otherwise supported for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory by the processor).

[0209] Additionally or alternatively, in some examples, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be implemented by processor-executable code (e.g., as communication management software or firmware). If implemented by processor-executable code, the functionality of the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination of these or other programmable logic devices (e.g., means configured or otherwise supported for performing the functions described in this disclosure).

[0210] In some examples, the communication manager 1220 may be configured to use or otherwise cooperate with the receiver 1210, transmitter 1215, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, the communication manager 1220 may receive information from the receiver 1210, send information to the transmitter 1215, or be integrated with the receiver 1210, transmitter 1215, or both to receive information, transmit information, or perform various other operations described herein.

[0211] According to the examples disclosed herein, the communication manager 1220 may support wireless communication at a base station. For example, the communication manager 1220 may be configured or otherwise support means for transmitting a DCI (Distributed Control Information Center) for scheduling a downlink shared channel to a UE, the DCI including a TCI (Tracking Control Center Information Center) state indicating a shared beam for at least one channel. The communication manager 1220 may also be configured or otherwise support means for receiving a feedback message from the UE for the downlink shared channel, wherein the feedback message acknowledges the UE's receipt of the TCI state.

[0212] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 (e.g., a processor that controls or otherwise couples to receiver 1210, transmitter 1215, communication manager 1220, or a combination thereof) can support techniques for more efficient use of communication resources, improved device efficiency, reduced signaling overhead, etc.

[0213] Figure 13 A block diagram 1300 of a device 1305 supporting DCI-based Unified TCI reception according to various aspects of this disclosure is shown. Device 1305 may be an example of aspects of device 1205 or base station 105 as described herein. Device 1305 may include a receiver 1310, a transmitter 1315, and a communications manager 1320. Device 1305 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0214] Receiver 1310 may provide means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to DCI-based Unified TCI reception). The information may be transmitted to other components of device 1305. Receiver 1310 may utilize a single antenna or a collection of multiple antennas.

[0215] Transmitter 1315 may provide means for transmitting signals generated by other components of device 1305. For example, transmitter 1315 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to DCI-based Unified TCI acknowledgment), user data, control information, or any combination thereof. In some examples, transmitter 1315 may be co-located with receiver 1310 in a transceiver module. Transmitter 1315 may utilize a single antenna or a collection of multiple antennas.

[0216] Device 1305 or its various components may be examples of apparatuses for performing various aspects of DCI-based unified TCI reception as described herein. For example, communication manager 1320 may include DCI transmission component 1325, feedback reception component 1330, or any combination thereof. Communication manager 1320 may be examples of various aspects of communication manager 1220 as described herein. In some examples, communication manager 1320 or its various components may be configured to use or otherwise cooperate with receiver 1310, transmitter 1315, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, communication manager 1320 may receive information from receiver 1310, send information to transmitter 1315, or be integrated with receiver 1310, transmitter 1315, or both to receive information, transmit information, or perform various other operations described herein.

[0217] According to the examples disclosed herein, the communication manager 1320 may support wireless communication at a base station. The DCI transmission component 1325 may be configured or otherwise support means for transmitting to the UE a DCI scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel. The feedback reception component 1330 may be configured or otherwise support means for receiving from the UE a feedback message for the downlink shared channel, wherein the feedback message acknowledges the UE's reception of the TCI state.

[0218] Figure 14A block diagram 1400 is shown of a communication manager 1420 supporting DCI-based unified TCI acceptance according to various aspects of this disclosure. The communication manager 1420 may be an example of the communication manager 1220, communication manager 1320, or aspects of both described herein. The communication manager 1420 or its various components may be examples of means for performing various aspects of DCI-based unified TCI acceptance as described herein. For example, the communication manager 1420 may include a DCI transmission component 1425, a feedback receiving component 1430, an RRC transmission component 1435, a feedback identification component 1440, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0219] According to the examples disclosed herein, the communication manager 1420 may support wireless communication at a base station. The DCI transmission component 1425 may be configured or otherwise support means for transmitting to the UE a DCI scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel. The feedback reception component 1430 may be configured or otherwise support means for receiving from the UE a feedback message for the downlink shared channel, wherein the feedback message acknowledges the UE's reception of the TCI state.

[0220] In some examples, the DCI transmission component 1425 may be configured or otherwise support means for transmitting the downlink shared channel in a single transport block. In some examples, the feedback reception component 1430 may be configured or otherwise support means for receiving from the UE a single affirmative acknowledgement bit for acknowledging the TCI state of the downlink shared channel based on the transmission.

[0221] In some examples, the DCI transmission component 1425 may be configured or otherwise support means for transmitting the downlink shared channel in more than one transport block. In some examples, the feedback reception component 1430 may be configured or otherwise support means for receiving by the UE at least one positive confirmation bit for confirming the TCI state for the downlink shared channel based on the transmission.

[0222] In some examples, the DCI transmission component 1425 may be configured or otherwise support means for transmitting the downlink shared channel in one or more code block groups. In some examples, the feedback reception component 1430 may be configured or otherwise support means for receiving from the UE, based on the transmission, at least one positive confirmation bit confirming the reception of the TCI state for the downlink shared channel.

[0223] In some examples, the feedback receiving component 1430 may be configured or otherwise supported for receiving the feedback message from the UE as an enhanced confirmation message including a set of affirmative confirmation bits, wherein the enhanced confirmation message confirms the reception of the TCI state.

[0224] In some examples, this enhanced confirmation message is associated with a HARQ type II codebook.

[0225] In some examples, the RRC transmission component 1435 may be configured or otherwise support means for transmitting to the UE via radio resource control messages an indication of reception of the TCI state for the downlink shared channel, including an acknowledgement bit set and an additional padded bit set to acknowledge reception.

[0226] In some examples, to support receiving the feedback message, the feedback identification component 1440 may be configured or otherwise supported for receiving an additional padded bit set from the UE in a portion of the codebook for the downlink shared channel, the additional padded bit set indicating a positive confirmation value for the reception of the TCI state.

[0227] In some examples, the payload of the downlink shared channel includes more than one transport block, and the feedback receiving component 1430 may be configured or otherwise support means for receiving a first affirmative acknowledgement bit from the UE for a first transport block, the first affirmative acknowledgement bit indicating reception of the downlink shared channel. In some examples, the payload of the downlink shared channel includes more than one transport block, and the feedback receiving component 1430 may be configured or otherwise support means for receiving a second affirmative acknowledgement bit from the UE for a second transport block, the second affirmative acknowledgement bit indicating reception of both the downlink shared channel and the DCI.

[0228] In some examples, the feedback receiving component 1430 may be configured or otherwise support means for receiving from the UE, according to the HARQ Type I codebook, a feedback message including a single affirmative acknowledgement bit dedicated to the DCI, wherein the single affirmative acknowledgement bit acknowledges the reception of the TCI state.

[0229] In some examples, the feedback receiving component 1430 may be configured or otherwise support means for receiving the feedback message from the UE on an uplink control channel resource set associated with the downlink shared channel, wherein the feedback message includes a first confirmation of reception of the downlink shared channel and a second confirmation of reception of the TCI state.

[0230] In some examples, the uplink control channel resource set is configured with a set of HARQ bits for transmitting feedback messages associated with the downlink shared channel.

[0231] In some examples, the uplink control channel resource set is indicated by the DCI.

[0232] In some examples, to support receiving the feedback message, the DCI transmission component 1425 may be configured or otherwise supported to transmit, based on the DCI including the TCI state, an indication of the shared beam and an indication of the uplink control channel resource set for the feedback message. In some examples, to support receiving the feedback message, the feedback reception component 1430 may be configured or otherwise supported to receive, on the uplink control channel resource set, the feedback message from the UE to acknowledge receipt of the TCI state.

[0233] In some examples, the DCI transmission component 1425 may be configured or otherwise support means for transmitting a TCI state indicating the shared beam in the DCI and the at least one other DCI. In some examples, the feedback reception component 1430 may be configured or otherwise support means for receiving the feedback message from the UE on the uplink control channel resource set to acknowledge receipt of the TCI state, or receiving the feedback message from the UE on a separate uplink control channel resource set to acknowledge receipt of the at least one other DCI.

[0234] In some examples, the DCI is transmitted after at least one other DCI, and the DCI includes a TCI state indicating the shared beam.

[0235] In some examples, the TCI status indication is a joint indication or a separate indication for the at least one channel.

[0236] In some examples, the TCI state indicating the shared beam includes a layer 1-based beam indication.

[0237] Figure 15A diagram of a system 1500 including device 1505 supporting DCI-based unified TCI reception is shown according to various aspects of this disclosure. Device 1505 may be an example of device 1205, device 1305, or base station 105 as described herein, or a component including such devices. Device 1505 may wirelessly communicate with one or more base stations 105, UE 115, or any combination thereof. Device 1505 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1520, a network communication manager 1510, a transceiver 1515, an antenna 1525, a memory 1530, a code 1535, a processor 1540, and an inter-station communication manager 1545. These components may be in electronic communication or otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1550).

[0238] The network communication manager 1510 can manage communication with the core network 130 (e.g., via one or more wired backhaul links). For example, the network communication manager 1510 can manage the delivery of data communication to client devices (such as one or more UEs 115).

[0239] In some cases, device 1505 may include a single antenna 1525. However, in other cases, device 1505 may have more than one antenna 1525, which may be capable of transmitting or receiving multiple wireless transmissions concurrently. Transceiver 1515 may communicate bidirectionally via one or more antennas 1525, wired or wireless links, as described herein. For example, transceiver 1515 may represent a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. Transceiver 1515 may also include a modem for modulating packets and providing modulated packets to one or more antennas 1525 for transmission, and for demodulating packets received from one or more antennas 1525. Transceiver 1515, or transceiver 1515 and one or more antennas 1525, may be an example of transmitter 1215, transmitter 1315, receiver 1210, receiver 1310, or any combination thereof or components thereof as described herein.

[0240] Memory 1530 may include RAM and ROM. Memory 1530 may store computer-readable, computer-executable code 1535, including instructions that, when executed by processor 1540, cause device 1505 to perform the various functions described herein. Code 1535 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, code 1535 may not be directly executable by processor 1540, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, memory 1530 may, in particular, include a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0241] Processor 1540 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1540 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1540. Processor 1540 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1530) to cause device 1505 to perform various functions (e.g., supporting various functions or tasks of DCI-based unified TCI recognition). For example, device 1505 or components thereof may include processor 1540 and memory 1530 coupled to processor 1540, wherein processor 1540 and memory 1530 are configured to perform the various functions described herein.

[0242] Inter-site communication manager 1545 manages communication with other base stations 105 and may include a controller or scheduler for cooperating with other base stations 105 to control communication with UE 115. For example, inter-site communication manager 1545 may coordinate the scheduling of transmissions to UE 115 for various interference mitigation techniques, such as beamforming or joint transmission. In some examples, inter-site communication manager 1545 may provide an X2 interface within LTE / LTE-A wireless communication network technology to facilitate communication between base stations 105.

[0243] Based on the examples disclosed herein, the communication manager 1520 may support wireless communication at a base station. For example, the communication manager 1520 may be configured or otherwise support means for transmitting a DCI (Distributed Control Information Center) to a UE (User Equipment) scheduling a downlink shared channel, the DCI including a TCI (Tracking Control Center Information Center) state indicating a shared beam for at least one channel. The communication manager 1520 may also be configured or otherwise support means for receiving a feedback message from the UE for the downlink shared channel, wherein the feedback message acknowledges the UE's receipt of the TCI state.

[0244] By including or configuring a communication manager 1520 according to an example as described herein, device 1505 can support technologies for improved communication reliability, reduced latency, more efficient use of communication resources, improved coordination between devices, reduced signaling overhead, and other benefits.

[0245] In some examples, the communication manager 1520 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with transceiver 1515, one or more antennas 1525, or any combination thereof. Although the communication manager 1520 is described as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 may be supported or performed by processor 1540, memory 1530, code 1535, or any combination thereof. For example, code 1535 may include instructions that can be executed by processor 1540 to cause device 1505 to perform various aspects of DCI-based unified TCI recognition as described herein, or the processor 1540 and memory 1530 may be otherwise configured to perform or support such operations.

[0246] Figure 16 A flowchart illustrating a method 1600 for supporting DCI-based unified TCI recognition according to various aspects of this disclosure is shown. Operation of method 1600 can be implemented by a UE or its components as described herein. For example, operation of method 1600 can be implemented by, as referred to... Figures 1 to 11 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0247] In 1605, the method may include receiving from a base station a DCI for scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel. Operation of 1605 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1605 may be provided by reference to... Figure 10 The described DCI receiving component 1025 is used to perform this.

[0248] In 1610, the method may include transmitting a feedback message to the base station for the downlink shared channel, wherein the feedback message acknowledges receipt of the TCI state. Operation of 1610 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1610 may be provided as referenced... Figure 10 The described feedback transmission component 1030 is used to perform this.

[0249] In 1615, the method may include applying the TCI state after transmitting a reception feedback message acknowledging receipt of the TCI state. The operation of 1615 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1615 may be provided by reference to... Figure 10 The TCI state application component 1035 is used to execute the described process.

[0250] Figure 17 A flowchart illustrating a method 1700 for supporting DCI-based unified TCI recognition according to various aspects of this disclosure is shown. Operation of method 1700 can be implemented by a UE or its components as described herein. For example, operation of method 1700 can be implemented by, as referred to... Figures 1 to 11 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0251] In 1705, the method may include receiving from a base station a DCI for scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel. Operation of 1705 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1705 may be provided by reference to... Figure 10 The described DCI receiving component 1025 is used to perform this.

[0252] In 1710, the method may include determining that the payload of the downlink shared channel comprises a single transport block. The operation of 1710 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1710 may be determined by reference to... Figure 10 The described PDSCH payload component 1040 is used to perform this.

[0253] In 1715, the method may include transmitting a single affirmative acknowledgement bit for the downlink shared channel to the base station based on the determination to acknowledge receipt of the TCI state. Operation of 1715 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1715 may be provided as referenced... Figure 10 The described feedback transmission component 1030 is used to perform this.

[0254] At 1720, the method may include transmitting a feedback message to the base station for the downlink shared channel, wherein the feedback message acknowledges receipt of the TCI state. Operation of 1720 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1720 may be provided as referenced... Figure 10 The described feedback transmission component 1030 is used to perform this.

[0255] In 1725, the method may include applying the TCI state after transmitting a reception feedback message acknowledging receipt of the TCI state. The operation of 1725 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1725 may be provided as referenced... Figure 10 The TCI state application component 1035 is used to execute the described process.

[0256] Figure 18 A flowchart illustrating a method 1800 for supporting DCI-based unified TCI recognition according to various aspects of this disclosure is shown. The operation of method 1800 can be implemented by a UE or its components as described herein. For example, the operation of method 1800 can be implemented by, as referred to... Figures 1 to 11 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0257] At 1805, the method may include receiving from a base station a DCI for scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel. Operation of 1805 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1805 may be provided by reference to... Figure 10 The described DCI receiving component 1025 is used to perform this.

[0258] In 1810, the method may include generating the feedback message as an enhanced confirmation message, the enhanced confirmation message including a set of positive confirmation bits. The operation of 1810 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1810 may be derived from, as referenced... Figure 10 The described feedback generation component 1045 is used to execute this.

[0259] In 1815, the method may include transmitting the enhanced confirmation message to the base station based on the generation to confirm the reception of the TCI state. The operation of 1815 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1815 may be derived from, as referenced... Figure 10The described feedback transmission component 1030 is used to perform this.

[0260] At 1820, the method may include transmitting a feedback message to the base station for the downlink shared channel, wherein the feedback message acknowledges receipt of the TCI state. Operation of 1820 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1820 may be provided as referenced... Figure 10 The described feedback transmission component 1030 is used to perform this.

[0261] In 1825, the method may include applying the TCI state after transmitting a reception feedback message acknowledging receipt of the TCI state. The operation of 1825 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1825 may be provided as referenced... Figure 10 The TCI state application component 1035 is used to execute the described process.

[0262] Figure 19 A flowchart illustrating a method 1900 supporting DCI-based unified TCI recognition according to various aspects of this disclosure is shown. Operation of method 1900 can be implemented by a UE or its components as described herein. For example, operation of method 1900 can be implemented by, as referred to... Figures 1 to 11 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0263] In 1905, the method may include receiving from a base station a DCI for scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel. Operation of 1905 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1905 may be provided by reference to... Figure 10 The described DCI receiving component 1025 is used to perform this.

[0264] In 1910, the method may include receiving from the base station via a radio resource control message an indication of reception of the feedback message for the downlink shared channel, including an acknowledgment bit set and an additional padded bit set to acknowledge the TCI state. Operation of 1910 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1910 may be provided by reference to... Figure 10 The described RRC component 1050 is used to execute this.

[0265] In 1915, the method may include allocating an additional padded set of bits to a portion of the codebook used for the downlink shared channel, the additional padded set of bits indicating a confirmed value. The operation of 1915 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1915 may be as described in reference... Figure 10 The described feedback generation component 1045 is used to execute this.

[0266] In 1920, the method may include transmitting to the base station at least an additional padded set of bits allocated to a portion of the codebook to confirm reception of the TCI state. Operation of 1920 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1920 may be provided as referenced... Figure 10 The described feedback transmission component 1030 is used to perform this.

[0267] In 1925, the method may include transmitting a feedback message to the base station for the downlink shared channel, wherein the feedback message acknowledges receipt of the TCI state. Operation of 1925 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1925 may be provided as referenced... Figure 10 The described feedback transmission component 1030 is used to perform this.

[0268] In 1930, the method may include applying the TCI state after transmitting a reception feedback message acknowledging receipt of the TCI state. The operation of 1930 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1930 may be provided as referenced. Figure 10 The TCI state application component 1035 is used to execute the described process.

[0269] Figure 20 A flowchart illustrating a method 2000 for supporting DCI-based unified TCI recognition according to various aspects of this disclosure is shown. The operation of method 2000 can be implemented by a UE or its components as described herein. For example, the operation of method 2000 can be implemented by, as referred to... Figures 1 to 11 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0270] In 2005, the method may include receiving from a base station a DCI for scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel. Operation of 2005 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 2005 may be provided by reference to... Figure 10 The described DCI receiving component 1025 is used to perform this.

[0271] In 2010, the method may include generating a single positive acknowledgment bit dedicated to the DCI based on a HARQ type I codebook. The operation of 2010 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2010 may be derived from, as referenced... Figure 10 The described feedback generation component 1045 is used to execute this.

[0272] In 2015, the method may include transmitting a feedback message, including the single affirmative acknowledgment bit, to the base station based on the generation to acknowledge receipt of the TCI state. Operation of 2015 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 2015 may be derived from, as referenced... Figure 10 The described feedback transmission component 1030 is used to perform this.

[0273] In 2020, the method may include transmitting a feedback message to the base station for the downlink shared channel, wherein the feedback message acknowledges receipt of the TCI state. Operation of 2020 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 2020 may be provided as referenced... Figure 10 The described feedback transmission component 1030 is used to perform this.

[0274] In 2025, the method may include applying the TCI state after transmitting a reception feedback message acknowledging receipt of the TCI state. Operation of 2025 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 2025 may be provided as referenced. Figure 10 The TCI state application component 1035 is used to execute the described process.

[0275] Figure 21 A flowchart illustrating a method 2100 for supporting DCI-based unified TCI recognition according to various aspects of this disclosure is shown. The operation of method 2100 can be implemented by a UE or its components as described herein. For example, the operation of method 2100 can be implemented by, as referred to... Figures 1 to 11 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0276] At 2105, the method may include receiving from a base station a DCI for scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel. Operation of 2105 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2105 may be provided by reference to... Figure 10 The described DCI receiving component 1025 is used to perform this.

[0277] In 2110, the method may include determining a TCI state in the DCI that indicates the shared beam. The operation of 2110 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2110 may be determined by reference to... Figure 10 The TCI status identification component 1055 described herein is used to perform this action.

[0278] In 2115, the method may include transmitting a feedback message to the base station for the downlink shared channel, wherein the feedback message acknowledges receipt of the TCI state. Operation of 2115 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2115 may be as described in reference to... Figure 10 The described feedback transmission component 1030 is used to perform this.

[0279] At 2120, the method may include identifying the set of uplink control channel resources in the DCI used for transmitting the feedback message based on the DCI including the TCI state. Operation of 2120 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2120 may be provided by reference to [reference needed]. Figure 10 The described uplink resource identification component 1060 is used to perform this.

[0280] In 2125, the method may include using the uplink control channel resource set to transmit the feedback message to the base station to acknowledge receipt of the TCI state. Operation of 2125 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 2125 may be provided as referenced... Figure 10 The described feedback transmission component 1030 is used to perform this.

[0281] At 2130, the method may include applying the TCI state after transmitting a reception feedback message acknowledging receipt of the TCI state. Operation of 2130 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2130 may be provided as referenced... Figure 10 The TCI state application component 1035 is used to execute the described process.

[0282] Figure 22 A flowchart illustrating a method 2200 for supporting DCI-based unified TCI recognition according to various aspects of this disclosure is shown. The operation of method 2200 can be implemented by a base station or its components as described herein. For example, the operation of method 2200 can be implemented by, as referred to... Figures 1 to 7 and Figures 12 to 15 The described base station 105 performs this function. In some examples, the base station may execute a set of instructions to control the functional elements of the base station to perform the described function. Alternatively or additionally, the base station may use dedicated hardware to perform aspects of the described function.

[0283] In 2205, the method may include transmitting to the UE a DCI for scheduling a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel. Operation of 2205 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2205 may be provided by reference to... Figure 14 The described DCI transport component 1425 is used to perform this.

[0284] In 2210, the method may include receiving a feedback message from the UE for the downlink shared channel, wherein the feedback message acknowledges the UE's reception of the TCI state. Operation of 2210 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2210 may be provided by reference to... Figure 14 The feedback receiving component 1430 described herein is used to perform this action.

[0285] Overview of all aspects

[0286] The following provides an overview of the various aspects of this disclosure:

[0287] Aspect 1: A method for wireless communication at a UE, comprising: receiving from a base station a scheduling DCI for a downlink shared channel, the DCI including a TCI state indicating a shared beam for at least one channel; transmitting to the base station a feedback message for the downlink shared channel, wherein the feedback message acknowledges receipt of the TCI state; and applying the TCI state after transmitting the feedback message acknowledging receipt of the TCI state.

[0288] Aspect 2: The method of Aspect 1 further includes: determining that the payload of the downlink shared channel comprises a single transport block; and transmitting a single positive ACK bit for the downlink shared channel to the base station at least in part based on the determination to acknowledge receipt of the TCI state.

[0289] Aspect 3: The method of any of Aspects 1 to 2 further includes: determining that the payload of the downlink shared channel includes more than one transport block; and transmitting at least one positive ACK bit for the downlink shared channel to the base station at least in part based on the determination to acknowledge receipt of the TCI state.

[0290] Aspect 4: The method of any of Aspects 1 to 3 further includes: determining that the downlink shared channel is configured with one or more code block groups; and transmitting at least one positive ACK bit for the downlink shared channel to the base station at least in part based on the determination to acknowledge receipt of the TCI state.

[0291] Aspect 5: The method of any of Aspects 1 to 4 further includes: generating the feedback message as an enhanced ACK message, the enhanced ACK message including a set of affirmative ACK bits; and transmitting the enhanced ACK message to the base station at least in part based on the generation to acknowledge receipt of the TCI state.

[0292] Aspect 6: The method of aspect 5, wherein the enhanced ACK message is associated with a HARQ type II codebook.

[0293] Aspect 7: The method of any of Aspects 1 to 6 further includes: receiving from the base station via a radio resource control message an indication of reception of a feedback message for the downlink shared channel, including an ACK bit set and an additional padded bit set to acknowledge the TCI state.

[0294] Aspect 8: The method of aspect 7, wherein the payload of the downlink shared channel includes a single transport block comprising one or more code block groups, wherein transmitting the feedback message further comprises: allocating an additional padded bit set to a portion of the codebook used for the downlink shared channel, the additional padded bit set indicating a positive ACK value; and transmitting at least the additional padded bit set allocated to the portion of the codebook to the base station to acknowledge receipt of the TCI state.

[0295] Aspect 9: The method of any of Aspects 7 to 8, wherein the payload of the downlink shared channel includes more than one transport block, the method further comprising: transmitting to the base station a first affirmative ACK bit for a first transport block, the first affirmative ACK bit indicating reception of the downlink shared channel; and transmitting to the base station a second affirmative ACK bit for a second transport block, the second affirmative ACK bit indicating reception of both the downlink shared channel and the DCI.

[0296] Aspect 10: The method of any of Aspects 1 to 9 further includes: generating a single positive ACK bit dedicated to the DCI based on a HARQ type I codebook; and transmitting a feedback message, including the single positive ACK bit, to the base station at least in part based on the generation to acknowledge receipt of the TCI state.

[0297] Aspect 11: The method of any of Aspects 1 to 10 further includes: transmitting the feedback message to the base station using an uplink control channel resource set associated with the downlink shared channel, wherein the feedback message includes a first confirmation of receipt of the downlink shared channel and a second confirmation of receipt of the TCI state; and applying the TCI state after transmitting the feedback message, wherein the feedback message indicates receipt of the TCI state.

[0298] Aspect 12: The method of aspect 11, wherein the uplink control channel resource set is configured with a set of HARQ bits for transmitting feedback messages associated with the downlink shared channel.

[0299] Aspect 13: The method of any of Aspects 11 to 12, wherein the uplink control channel resource set is indicated by the DCI.

[0300] Aspect 14: The method of any of Aspects 1 to 13, wherein the DCI is received after at least one other DCI, and wherein transmitting the feedback message further comprises: determining that the DCI includes a TCI state indicating the shared beam; identifying an uplink control channel resource set in the DCI for transmitting the feedback message based at least in part on the inclusion of the TCI state in the DCI; and using the uplink control channel resource set to transmit the feedback message to the base station to confirm receipt of the TCI state.

[0301] Aspect 15: The method of aspect 14 further includes: determining that the DCI and the at least one other DCI include a TCI state indicating the shared beam; and using the uplink control channel resource set to transmit the feedback message to the base station to confirm reception of the TCI state, or using a separate uplink control channel resource set to transmit the feedback message to the base station to confirm reception of the at least one other DCI.

[0302] Aspect 16: The method of any of Aspects 14 to 15, wherein the DCI is received at least in part based on the fact that the DCI is received after the at least one other DCI and includes a TCI state indicating the shared beam.

[0303] Aspect 17: The method of any of Aspects 1 to 16, wherein the TCI status indication is a joint indication or a separate indication for the at least one channel.

[0304] Aspect 18: The method of any of Aspects 1 to 17, wherein the TCI state indicating the shared beam includes a layer 1-based beam indication.

[0305] Aspect 19: A method for wireless communication at a base station, comprising: transmitting to a UE a DCI scheduling a downlink shared channel, the DCI including a Transmission Configuration Indicator (TCI) state indicating a shared beam for at least one channel; and receiving from the UE a feedback message for the downlink shared channel, wherein the feedback message acknowledges the UE's receipt of the TCI state.

[0306] Aspect 20: The method of aspect 19 further includes: transmitting the downlink shared channel in a single transport block; and receiving, at least in part, a single affirmative ACK bit from the UE confirming the TCI state of the downlink shared channel based on the transmission.

[0307] Aspect 21: The method of any of Aspects 19 to 20 further includes: transmitting the downlink shared channel in more than one transport block; and receiving by the UE at least one positive ACK bit for acknowledging the TCI state of the downlink shared channel, at least in part based on the transmission.

[0308] Aspect 22: The method of any of Aspects 19 to 21 further includes: transmitting the downlink shared channel in one or more code block groups; and receiving from the UE at least one positive ACK bit for acknowledging the TCI state of the downlink shared channel, at least in part based on the transmission.

[0309] Aspect 23: The method of any of Aspects 19 to 22 further includes: receiving the feedback message from the UE as an enhanced ACK message including a set of affirmative ACK bits, wherein the enhanced ACK message acknowledges the reception of the TCI state.

[0310] Aspect 24: The method of aspect 23, wherein the enhanced ACK message is associated with a HARQ type II codebook.

[0311] Aspect 25: The method of any of Aspects 19 to 24 further includes: transmitting to the UE via a radio resource control message an indication of reception of the TCI state, including an ACK bit set and an additional padded bit set, for the downlink shared channel.

[0312] Aspect 26: The method of aspect 25, wherein the payload of the downlink shared channel includes a single transport block comprising one or more code block groups, wherein receiving the feedback message further comprises: receiving an additional padded bit set from the UE in a portion of the codebook for the downlink shared channel, the additional padded bit set indicating an affirmative ACK value for acknowledging the reception of the TCI state.

[0313] Aspect 27: The method of any of Aspects 25 to 26, wherein the payload of the downlink shared channel includes more than one transport block, the method further comprising: receiving from the UE a first affirmative ACK bit for a first transport block, the first affirmative ACK bit indicating reception of the downlink shared channel; and receiving from the UE a second affirmative ACK bit for a second transport block, the second affirmative ACK bit indicating reception of both the downlink shared channel and the DCI.

[0314] Aspect 28: The method of any of Aspects 19 to 27 further includes: receiving from the UE a feedback message including a single affirmative ACK bit dedicated to the DCI according to a HARQ Type I codebook, wherein the single affirmative ACK bit acknowledges the reception of the TCI state.

[0315] Aspect 29: The method of any of Aspects 19 to 28 further includes: receiving the feedback message from the UE on an uplink control channel resource set associated with the downlink shared channel, wherein the feedback message includes a first confirmation of receipt of the downlink shared channel and a second confirmation of receipt of the TCI state.

[0316] Aspect 30: The method of aspect 29, wherein the uplink control channel resource set is configured with a set of HARQ bits for transmitting feedback messages associated with the downlink shared channel.

[0317] Aspect 31: The method of any of Aspects 29 to 30, wherein the uplink control channel resource set is indicated by the DCI.

[0318] Aspect 32: The method of any of Aspects 19 to 31, wherein the DCI is transmitted after at least one other DCI, and wherein receiving the feedback message further comprises: transmitting in the DCI an indication of the shared beam state and an indication of an uplink control channel resource set for the feedback message, based at least in part on the DCI including the TCI state; and receiving the feedback message from the UE on the uplink control channel resource set to acknowledge receipt of the TCI state.

[0319] Aspect 33: The method of aspect 32 further includes: transmitting a TCI state indicating the shared beam in the DCI and the at least one other DCI; and receiving the feedback message from the UE on the uplink control channel resource set to confirm reception of the TCI state, or receiving the feedback message from the UE on a separate uplink control channel resource set to confirm reception of the at least one other DCI.

[0320] Aspect 34: The method of any of Aspects 32 to 33, wherein the DCI is transmitted after at least one other DCI and the DCI includes a TCI state indicating the shared beam.

[0321] Aspect 35: The method of any of Aspects 19 to 34, wherein the TCI status indication is a joint indication or a separate indication for the at least one channel.

[0322] Aspect 36: The method of any of Aspects 19 to 35, wherein the TCI state indicating the shared beam includes a layer 1-based beam indication.

[0323] Aspect 37: An apparatus for wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as described in any of Aspects 1 to 18.

[0324] Aspect 38: An apparatus for wireless communication at a UE, comprising at least one means for performing the method of any one of aspects 1 to 18.

[0325] Aspect 39: A non-transient computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by a processor to perform methods as described in any of Aspects 1 to 18.

[0326] Aspect 40: An apparatus for wireless communication at a base station, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as described in any of Aspects 19 to 36.

[0327] Aspect 41: An apparatus for wireless communication at a base station, comprising at least one means for performing the method of any of aspects 19 to 36.

[0328] Aspect 42: A non-transient computer-readable medium storing code for wireless communication at a base station, the code including instructions executable by a processor to perform methods as described in any of Aspects 19 to 36.

[0329] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0330] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein can also be applied to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques can be applied to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0331] The information and signals described herein can be represented using any of a wide variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout this description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0332] The various illustrative boxes and components described herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternatives, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, or any other such configuration).

[0333] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored or transmitted as one or more instructions or code on a computer-readable medium. Other examples and implementations fall within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed such that different parts of the function are implemented at different physical locations.

[0334] Computer-readable media includes both non-transient computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transient storage media can be any available medium accessible to a general-purpose or special-purpose computer. By way of example and not limitation, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transient medium that can be used to carry or store desired program code in the form of instructions or data structures and is accessible to a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Similarly, any connection is also legitimately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then that coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable media. As used in this article, disk and disc include CDs, laser discs, optical discs, DVDs, floppy disks, and Blu-ray discs, where disks often magnetically reproduce data while discs optically reproduce data using lasers. Combinations of these media are also included within the scope of computer-readable media.

[0335] As used herein (including in the claims), the word "or" in an enumeration of items (e.g., an enumeration of items accompanied by phrases such as "at least one of" or "one or more of") indicates an inclusive enumeration, such that an enumeration of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Similarly, as used herein, the phrase "based on" should not be interpreted as referring to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0336] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, components of the same type may be distinguished by a dash following the reference numeral and a second reference numeral used to differentiate between similar components. If only the first reference numeral is used in the description, the description may apply to any of the similar components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0337] The descriptions herein, illustrated with reference to the accompanying drawings, depict exemplary configurations and are not representative of all examples that may be implemented or fall within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and does not imply "superior" or "outperforming" other examples. This detailed description includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0338] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the universal principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for conducting wireless communication at a user equipment (UE), comprising: Receive downlink control information (DCI) for scheduling downlink shared channels, the DCI including a transmission configuration indicator (TCI) status indicating a shared beam for at least one channel; Transmit a feedback message for the downlink shared channel, wherein the feedback message acknowledges receipt of the TCI state; and After transmitting the feedback message confirming receipt of the TCI state, the TCI state is applied after an indication delay, the indication delay being at least in part based on the beam switching indicated by the TCI state.

2. The method of claim 1, further comprising: The payload of the downlink shared channel is determined to include a single transport block; as well as A single positive confirmation bit for the downlink shared channel is transmitted, at least in part, based on the determination, to confirm the reception of the TCI state.

3. The method of claim 1, further comprising: The payload of the downlink shared channel is determined to include more than one transport block; as well as At least one positive confirmation bit for the downlink shared channel is transmitted based at least in part on the determination to confirm the reception of the TCI state.

4. The method of claim 1, further comprising: It is determined that the downlink shared channel is configured with one or more code block groups; as well as At least one positive confirmation bit for the downlink shared channel is transmitted based at least in part on the determination to confirm the reception of the TCI state.

5. The method of claim 1, further comprising: The feedback message is generated as an enhanced confirmation message, which includes a set of confirmed bits. as well as The enhanced acknowledgement message is transmitted at least in part based on the generation to acknowledge receipt of the TCI state.

6. The method of claim 5, wherein the enhanced receipt message is associated with a Hybrid Automatic Repeat Request (HARQ) Type II codebook.

7. The method of claim 1, further comprising: The feedback message received via radio resource control messages for the downlink shared channel includes an indication of the received acknowledgment bit set and an additional padded bit set to confirm the reception of the TCI state.

8. The method of claim 7, wherein the payload of the downlink shared channel comprises a single transport block, the single transport block comprising one or more code block groups, wherein transmitting the feedback message further comprises: The additional padded bit set is allocated to a portion of the codebook used for the downlink shared channel, the additional padded bit set indicating a confirmed value; as well as At least the additional padded bit set allocated to the portion of the codebook is transmitted to confirm receipt of the TCI state.

9. The method of claim 7, wherein the payload of the downlink shared channel includes more than one transport block, the method further comprising: Transmit a first affirmative bit for the first transport block, the first affirmative bit indicating reception of the downlink shared channel; as well as Transmit a second acknowledgment bit for the second transport block, the second acknowledgment bit indicating reception of both the downlink shared channel and the DCI.

10. The method of claim 1, further comprising: A single positive confirmation bit is generated specifically for the DCI based on the Hybrid Automatic Repeat Request (HARQ) Type I codebook; as well as The feedback message, including the single affirmative acknowledgement bit, is transmitted at least in part based on the generation to acknowledge the reception of the TCI state.

11. The method of claim 1, further comprising: The feedback message is transmitted using an uplink control channel resource set associated with the downlink shared channel, wherein the feedback message includes a first confirmation of reception of the downlink shared channel and a second confirmation of reception of the TCI state; and The feedback message therein indicates the receipt of the TCI status.

12. The method of claim 11, wherein the uplink control channel resource set is configured with a hybrid automatic repeat request (HARQ) bit set for transmitting the feedback message associated with the downlink shared channel.

13. The method of claim 11, wherein the uplink control channel resource set is indicated by the DCI.

14. The method of claim 1, wherein the DCI is received after at least one other DCI, and wherein transmitting the feedback message further comprises: Determine that the TCI state, which indicates the shared beam, is included in the DCI; The uplink control channel resource set used for transmitting the feedback message is identified in the DCI at least in part based on the DCI including the TCI state; as well as The feedback message is transmitted using the uplink control channel resource set to acknowledge receipt of the TCI status.

15. The method of claim 14, further comprising: Determine that the TCI state, which indicates the shared beam, is included in the DCI and the at least one other DCI; as well as The feedback message can be transmitted using the uplink control channel resource set to confirm the reception of the TCI state, or the feedback message can be transmitted using a separate uplink control channel resource set to confirm the reception of the at least one other DCI.

16. The method of claim 14, wherein the DCI is received at least in part after the at least one other DCI and the DCI includes the TCI state indicating the shared beam.

17. The method of claim 1, wherein the TCI status indication is a joint indication or a separate indication for the at least one channel.

18. The method of claim 1, wherein the TCI state indicating the shared beam includes layer 1-based beam indication.

19. A method for wireless communication at a component of a base station, comprising: Transmit downlink control information (DCI) for scheduling downlink shared channels, the DCI including a transmission configuration indicator (TCI) status indicating a shared beam for at least one channel; as well as Receive a feedback message for the downlink shared channel, wherein the feedback message acknowledges the user equipment (UE)'s reception of the TCI state, wherein the TCI state is applied after an indication delay, the indication delay being at least in part based on a beam switching indicated by the TCI state.

20. The method of claim 19, further comprising: The downlink shared channel is transmitted in a single transport block; as well as A single positive confirmation bit is received, at least in part, based on the transmission, confirming the TCI status of the downlink shared channel.

21. The method of claim 19, further comprising: The downlink shared channel is transmitted in more than one transport block; as well as At least one positive confirmation bit is received for the confirmation of the TCI state for the downlink shared channel, based at least in part on the transmission.

22. The method of claim 19, further comprising: Transmit the downlink shared channel in one or more code block groups; as well as At least one positive confirmation bit is received for the confirmation of the TCI state for the downlink shared channel, based at least in part on the transmission.

23. The method of claim 19, further comprising: The feedback message transmitted via radio resource control messages for the downlink shared channel includes an indication of receipt of a set of confirmed bits and an additional set of padded bits to confirm the reception of the TCI state.

24. The method of claim 23, wherein the payload of the downlink shared channel comprises a single transport block, the single transport block comprising one or more code block groups, wherein receiving the feedback message further comprises: The additional padded bit set is received in a portion of the codebook used for the downlink shared channel, the additional padded bit set indicating a positive confirmation value for the reception of the TCI state.

25. The method of claim 23, wherein the payload of the downlink shared channel comprises more than one transport block, the method further comprising: Receive a first affirmative bit for the first transport block, the first affirmative bit indicating reception of the downlink shared channel; as well as Receive a second acknowledgment bit for the second transport block, the second acknowledgment bit indicating the reception of both the downlink shared channel and the DCI.

26. The method of claim 19, further comprising: The feedback message, which includes a single affirmative acknowledgement bit dedicated to the DCI, is received according to the Hybrid Automatic Repeat Request (HARQ) Type I codebook, wherein the single affirmative acknowledgement bit acknowledges the reception of the TCI state.

27. The method of claim 19, further comprising: The feedback message is received on the uplink control channel resource set associated with the downlink shared channel, wherein the feedback message includes a first confirmation of the downlink shared channel and a second confirmation of the reception of the TCI state.

28. The method of claim 27, wherein the uplink control channel resource set is configured with a hybrid automatic repeat request (HARQ) bit set for transmitting the feedback message associated with the downlink shared channel.

29. The method of claim 27, wherein the uplink control channel resource set is indicated by the DCI.

30. The method of claim 19, wherein the DCI is transmitted after at least one other DCI, and wherein receiving the feedback message further comprises: The DCI transmits, at least in part, the TCI state indicating the shared beam and an indication of the uplink control channel resource set for the feedback message, based on the DCI including the TCI state; and The feedback message is received on the uplink control channel resource set to confirm the reception of the TCI state.

31. The method of claim 30, further comprising: The TCI state indicating the shared beam is transmitted in the DCI and the at least one other DCI; as well as The feedback message is received on the uplink control channel resource set to confirm the reception of the TCI state, or the feedback message is received on a separate uplink control channel resource set to confirm the reception of the at least one other DCI.

32. The method of claim 30, wherein the DCI includes the TCI state indicating the shared beam, based at least in part on the fact that the DCI is transmitted after the at least one other DCI.

33. An apparatus for wireless communication at a user equipment (UE), comprising: processor; Memory coupled to the processor; as well as Instructions stored in the memory and executable by the processor to cause the device to perform the following operations: Receive downlink control information (DCI) for scheduling downlink shared channels, the DCI including a transmission configuration indicator (TCI) status indicating a shared beam for at least one channel; Transmit a feedback message for the downlink shared channel, wherein the feedback message acknowledges receipt of the TCI state; and After transmitting the feedback message confirming receipt of the TCI state, the TCI state is applied after an indication delay, the indication delay being at least in part based on the beam switching indicated by the TCI state.

34. The apparatus of claim 33, wherein the instructions are further executable by the processor to cause the apparatus to perform the method of any one of claims 2-18.

35. An apparatus for wireless communication at a component of a base station, comprising: processor; Memory coupled to the processor; as well as Instructions stored in the memory and executable by the processor to cause the device to perform the following operations: Transmit downlink control information (DCI) for scheduling downlink shared channels, the DCI including a transmission configuration indicator (TCI) status indicating a shared beam for at least one channel; as well as Receive a feedback message for the downlink shared channel, wherein the feedback message acknowledges the user equipment (UE)'s reception of the TCI state, wherein the TCI state is applied after an indication delay, the indication delay being at least in part based on a beam switching indicated by the TCI state.

36. The apparatus of claim 35, wherein the instructions are further executable by the processor to cause the apparatus to perform the method of any one of claims 20-32.

37. An apparatus for wireless communication at a user equipment (UE), comprising: A means for receiving downlink control information (DCI) for scheduling a downlink shared channel, the DCI including a transmission configuration indicator (TCI) state indicating a shared beam for at least one channel. A means for transmitting a feedback message for the downlink shared channel, wherein the feedback message acknowledges the receipt of the TCI state; as well as A means for applying the TCI state after an indication delay following the transmission of a feedback message confirming receipt of the TCI state, the indication delay being at least in part based on a beam switching indicated by the TCI state.

38. The apparatus of claim 37, further comprising means for performing the method of any one of claims 1-18.

Images