Methods for configuring, activating, and indicating transmission configuration indicator (TCI) states associated with beam prediction

Abstract

Example methods, systems, and techniques for configuring, activating, and indicating Transmission Configuration Indicator (TCI) states associated with different beam prediction scenarios—such as configurations with or without beam prediction. An example method for wireless communication by a user equipment (UE) includes: receiving a first control signaling from a network entity, the first control signaling indicating: at least one beam prediction TCI state associated with a first delay, and at least one non-beam prediction TCI state associated with a second delay. The UE receives a second control signaling activating one or more of the at least one beam prediction TCI state and the at least one non-beam prediction TCI state. The UE then communicates with the network entity at an action time associated with the first delay or the second delay based on the one or more TCI states.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, and more specifically to configuring, activating, and indicating the state of a Transport Configuration Indicator (TCI). Background Technology

[0002] This background description is provided for the purpose of presenting the general context of this disclosure. The work of the currently attributed inventors (to the extent described in this background section) and aspects of the specification that would not have been considered prior art at the time of filing are neither expressly nor impliedly acknowledged as prior art to this disclosure.

[0003] User equipment (UE) and network entities can use simulated beamforming to increase link budget. To use simulated beamforming, network entities and UEs can maintain multiple beams or beam pairs. Good network-UE beam pairs can significantly increase link budget, thus providing substantial coverage gain. The beam selection process is defined to typically be performed in two steps: 1) beam measurement and reporting; 2) beam indication. Network entities can indicate a beam by indicating a TCI state from the Transmission Configuration Indicator (TCI) state list configured via Radio Resource Control (RRC) signaling sent from the network entity to the UE. The network can configure different quasi-co-located (QCL) sources for different TCI states.

[0004] For beam indication based on a unified TCI, network entities can instruct a joint TCI to update the beams of both the uplink and downlink channels, or instruct a downlink TCI to update the downlink channel beams and / or instruct an uplink TCI to update the uplink channel beams. Network entities can configure the TCI list for the bandwidth portion via RRC signaling and activate a subset of TCI states via a Media Access Control (MAC) control element (CE). The activated TCI states correspond to different TCI code points in the downlink control information (DCI). Then, if an activated TCI state corresponds to more than one TCI code point, the network entity can send a DCI to select the TCI state corresponding to one TCI code point for further communication.

[0005] Currently, the configuration, activation, and indication of TCI states are not adapted to beams (pairs) that have not yet been applied to downlink reference signals (DL RS). The control signaling used for TCI states may also differ when TCI activation or indication is associated with or unrelated to beam prediction, leading to potential configuration issues. Summary of the Invention

[0006] This disclosure provides methods, systems, and techniques for configuring, activating, and indicating Transmission Configuration Indicator (TCI) states associated with different beam prediction scenarios—such as configurations with or without beam prediction. Beamforming techniques enable network entities and user equipment (UEs) to focus radio signals in a specific direction to increase link budget. For example, a UE performs beam measurements and reports the results to the network, which then indicates a specific beam direction (e.g., TCI state) to the UE for subsequent communication. In some cases, network entities indicate a joint TCI state to update the beams of both uplink and downlink channels, or to indicate the corresponding downlink TCI state and uplink TCI state for the respective downlink and / or uplink channels.

[0007] According to a general aspect of this disclosure, a method for wireless communication by a user equipment (UE) includes: receiving a first control signaling from a network entity, the first control signaling indicating: at least one beam prediction TCI state associated with a first delay, and at least one non-beam prediction TCI state associated with a second delay. The UE receives a second control signaling activating one or more of the at least one beam prediction TCI state and the at least one non-beam prediction TCI state. The UE then communicates with the network entity at an action time associated with the first delay or the second delay based on the one or more TCI states.

[0008] In all respects, the first control signaling indicates parameters for activating or indicating the at least one beam prediction TCI state.

[0009] In each respect, the at least one beam prediction TCI state includes a first TCI state list for TCI activation or indication with beam prediction, the first TCI state list corresponding to a first delay of the beam prediction window. The at least one non-beam prediction TCI state includes a second TCI state list for TCI activation or indication without beam prediction for the second delay.

[0010] In all respects, the at least one beam prediction TCI state is the same as the at least one non-beam prediction TCI state.

[0011] In various respects, this second control signaling includes a Media Access Control (MAC) control element (CE). In some cases, the MAC CE indicates whether each or all of one or more active TCI states are used for beam prediction, and whether one or more active TCI states corresponding to a Transmit Receive Point (TRP) are used for beam prediction. The UE can identify whether the MAC CE is used for beam prediction based on the Logical Channel Identifier (LCID) or Extended LCID of the MAC CE.

[0012] In all aspects, the UE receives from the network entity one or more activated TCI states in the MAC CE for one or more beam predictions.

[0013] In various aspects, the UE receives downlink control information (DCI), which indicates one or more TCI states (referred to as the "TCI state set") that have been activated by a second control signaling. In some cases, the DCI indicates whether one or more TCI states are used for beam prediction via at least one of the following: the location of the physical downlink control channel (PDCCH) with the DCI; or the format of the DCI.

[0014] In some cases, the UE receives multiple indicated TCI states from a network entity for one or more beam prediction windows. The UE identifies the action time for applying the TCI state set based on at least one of the following: a predefined time slot; a predefined time after the first last symbol of the PDCCH with DCI; or a time slot configured by the network entity.

[0015] In each respect, the first control signaling further indicates at least one of the following for each beam prediction TCI state: a first downlink reference signal (DL RS) associated with a quasi-co-location type D (QCL-type D) for spatial reception parameter indication; a second DL RS associated with a path loss reference signal (PL-RS); or a third DL RS associated with a QCL type A for average delay, delay spread, Doppler shift, and Doppler spread indication.

[0016] In some cases, the UE monitors the first DL RS, the second DL RS, and the third DL RS after receiving the second control signaling or after sending an acknowledgment (ACK) for the second control signaling. The UE avoids monitoring the first DL RS, the second DL RS, or the third DL RS after switching to another active TCI state.

[0017] In some cases, the UE receives at least one of the following for one or more TCI states: a first aperiodic DL RS resource set, which is associated with a first DL RS quasi-co-address (QCL) and a QCL-typeD indication; a second aperiodic DL RS resource set, which is associated with a second DL RS quasi-co-address and a PL-RS; or a third DL RS resource set, which is associated with a third DL RS quasi-co-address and a QCL-typeA indication.

[0018] In various aspects, the UE determines the first delay and the second delay based on at least one of the following: the delay from receiving the second control signaling to sending an acknowledgment (ACK) for the second control signaling; the delay for quasi-co-location (QCL) parameter tracking; the delay for UE beam tracking based on whether the associated TCI state is known or unknown; the delay for path loss measurement based on whether the UE maintains path loss operation; or the beam prediction window.

[0019] According to a general aspect of this disclosure, a wireless communication method performed by a network entity includes sending a first control signaling to a UE, the first control signaling indicating at least one beam prediction transmission configuration indicator (TCI) state associated with a first delay and at least one non-beam prediction TCI state associated with a second delay. The network entity sends a second control signaling activating one or more of the at least one beam prediction TCI state and the at least one non-beam prediction TCI state. The network entity communicates with the UE at an action time associated with the first delay or the second delay based on the one or more TCI states.

[0020] In each respect, the at least one beam prediction TCI state includes a first TCI state list for TCI activation or indication with beam prediction, the first TCI state list corresponding to a first delay of the beam prediction window. The at least one non-beam prediction TCI state includes a second TCI state list for TCI activation or indication without beam prediction for the second delay. In some cases, the network entity sends to the UE at least one of the following for each beam prediction TCI state: a first downlink reference signal (DL RS) associated with or configured as the DL RS of Quasi-Co-location (QCL) type D for spatial reception parameter indication in the beam prediction TCI state; a second DL RS associated with or configured as the Path Loss Reference Signal (PL-RS) for the beam prediction TCI state; or a third DL RS associated with or configured as the DL RS of QCL type A for average delay, delay spread, Doppler shift, and Doppler spread indication in the beam prediction TCI state.

[0021] According to a general aspect of this disclosure, an apparatus includes: one or more radio frequency (RF) modems; a processor coupled to the one or more RF modems; and at least one memory storing executable instructions. These executable instructions manipulate the processor or at least one of the one or more RF modems to perform the methods discussed in detail herein. Attached Figure Description

[0022] Figure 1 The illustration shows a wireless communication system according to various aspects of this disclosure, which includes multiple user equipment (UEs) and network entities communicating through one or more cells.

[0023] Figure 2a An example illustration of a Transmission Configuration Indicator (TCI) indication for Single Transmitter Receiver Point (sTRP) operation according to various aspects of this disclosure is shown.

[0024] Figure 2b An example illustration of a TCI indication for multiple transmit / receive point (mTRP) operation according to various aspects of this disclosure is shown.

[0025] Figure 3 An example illustration of robust TCI activation / indication based on beam prediction is shown according to various aspects of this disclosure.

[0026] Figure 4 An example illustration of UE behavior in robust TCI activation / indication based on beam prediction is shown in accordance with various aspects of this disclosure.

[0027] Figure 5 An example illustration of network entity behavior in robust TCI activation / indication based on beam prediction is shown according to various aspects of this disclosure.

[0028] Figure 6a Examples of individual TCI configurations for TCI activation / indication with / without beam prediction are shown according to various aspects of this disclosure.

[0029] Figure 6b Examples of common TCI configurations for TCI activation / indication with / without beam prediction are shown according to various aspects of this disclosure.

[0030] Figure 7a Examples of TCI activation / indication based on MAC CE with / without beam prediction are shown according to various aspects of this disclosure.

[0031] Figure 7b An example of a MACCE-based TCI activation / indication with beam prediction for multiple prediction windows is shown according to various aspects of this disclosure.

[0032] Figure 8a Examples of TCI indications based on a public DCI format with / without beam prediction are shown according to various aspects of this disclosure.

[0033] Figure 8bAn example of a TCI indicator with beam prediction for multiple beam prediction windows is shown according to various aspects of this disclosure.

[0034] Figure 8c An example of a TCI indication based on the activated TCI state at the time of action for a TCI indication, according to various aspects of this disclosure, is shown.

[0035] Figure 9a An example of TCI activation / indication based on a periodic downlink (DL) reference signal (RS) according to various aspects of this disclosure is shown.

[0036] Figure 9b An example of a semi-persistent DL RS-based QCL / path loss measurement for an activated / indicated TCI state, according to various aspects of this disclosure, is shown.

[0037] Figure 9c Examples of QCL / path loss measurements based on periodic, semi-persistent, and / or aperiodic DL RS according to various aspects of this disclosure are shown.

[0038] Figure 10a An example of QCL / path loss measurement for TCI activation / indication with beam prediction prior to the beam prediction window is shown, according to various aspects of this disclosure.

[0039] Figure 10b An example of QCL / path loss measurement for TCI activation / indication with beam prediction after the beam prediction window is shown, according to various aspects of this disclosure.

[0040] Figure 10c An example of QCL / path loss measurement for TCI activation / indication with beam prediction is shown, three time slots after the transmission of the ACK for TCI activation / indication signaling, according to various aspects of this disclosure.

[0041] Figure 10d An example of the TCI action time of the first prediction window according to various aspects of this disclosure after the second beam prediction window is shown.

[0042] Figure 11 An example flowchart of a method performed by a UE according to various aspects of this disclosure is shown.

[0043] Figure 12 An example flowchart of a method performed by a network entity according to various aspects of this disclosure is shown.

[0044] Figure 13 This is a diagram illustrating the hardware implementation for an example UE device.

[0045] Figure 14 This is a diagram illustrating the hardware implementation for one or more example network entities.

[0046] The same number indicates the same component. Detailed Implementation

[0047] This disclosure provides methods, systems, and techniques for configuring, activating, and indicating Transmission Configuration Indicator (TCI) states associated with different beam prediction scenarios—such as configurations with or without beam prediction. Beamforming techniques enable network entities and user equipment (UEs) to focus radio signals in a specific direction to increase link budget. For example, a UE performs beam measurements and reports the results to the network, which then indicates a specific beam direction (e.g., TCI state) to the UE for subsequent communication. In some cases, network entities indicate a joint TCI state to update the beams of both uplink and downlink channels, or to indicate the corresponding downlink TCI state and uplink TCI state for the respective downlink and / or uplink channels.

[0048] Upon receiving a beam report from the UE, network entities can predict the beam (e.g., spatial beam prediction) of any downlink reference signals (DL RS) that may not yet be applied to the beam report. Therefore, this disclosure provides methods for performing or acknowledging time offset, frequency offset, beam tracking, or path loss measurements on an activated or indicated (activated / indicated) TCI state based on the predicted beam. Additionally, when beam prediction is based on historical beam reports (e.g., time beam prediction), this disclosure provides methods for determining the action time and action delay that cause the network and UE to cease communication based on a previously activated / indicated TCI and begin measuring time offsets, frequency offsets, etc., for communication based on a newly activated / indicated TCI state. Furthermore, because the network and UE may or may not use beam prediction in different scenarios, the techniques herein enable network entities and UEs to configure, activate, and indicate TCI states with or without beam prediction in a flexible and robust manner (e.g., related to different action delays and other operating parameters).

[0049] In beamforming, network entities can perform spatial or temporal (e.g., temporal) beam prediction. For example, in spatial beam prediction, a network entity can predict network beams (e.g., in the desired direction) based on received beam reports for a subset of beams. A network entity can predict beams that have been or have not yet been applied to any DL RS (e.g., SSB / CSI-RS). A network entity can provide TCI activation / indication based on the predicted beams. This disclosure provides methods and techniques for determining time offset, frequency offset, UE beam tracking, and / or path loss measurements for activated / indicated TCI based on predicted beams when a network entity has not yet transmitted or configured any DL RS based on the predicted beams.

[0050] In time-based beam prediction, network entities can predict future network beams based on received historical beam reports. A network entity can predict at least one beam within a beam prediction window, for example, X ms after a TCI activation / indication used for beam prediction, or X ms after receiving a TCI activation / indication command from the network, or X ms after receiving an ACK for the TCI activation / indication command within the PDSCH. Network entities can predict beams that have been or have not yet been applied to any DL RS. Regarding time offset, frequency offset, and UE beam tracking used for beam prediction, determining the action time and action delay of the activated / indicated TCI used for beam prediction (e.g., when to stop communication based on previously activated / indicated TCI, when to start measuring time offset, frequency offset, UE beam tracking, and / or path loss, and when to start communication based on a newly activated / indicated TCI) can become a problem.

[0051] To achieve robust operation, network entities can send TCI activation / indication with or without beam prediction. Depending on whether beam prediction is involved, the UE can apply different action delays to the TCI activation / indication signaling. This disclosure provides for identifying whether TCI activation / indication is used for beam prediction. Furthermore, this disclosure provides for determining which channel(s)(s) should be the target channel(s)(s) for applying the activated / indicated TCI with beam prediction. Thus, this disclosure proposes example methods and techniques for providing control signaling to distinguish between TCI activation / indication with or without beam prediction, providing new parameters for DL ​​RS configuration and transmission—such as time offset, frequency offset, UE beam tracking and / or path loss measurements for the activated / indicated TCI state based on beam prediction—and determining the action delay and action time for the TCI state based on beam prediction.

[0052] At a high level, aspects of this disclosure for configuring, activating, and indicating TCI states include wireless communication methods performed by a UE. An example method includes receiving a first control signaling from the network entity, the first control signaling indicating at least one beam-predicted TCI state associated with a first delay, and at least one non-beam-predicted TCI state associated with a second delay. The UE receives a second control signaling activating one or more of the at least one beam-predicted TCI state and the at least one non-beam-predicted TCI state. The UE then communicates with the network entity at an action time associated with the first delay or the second delay based on the one or more TCI states.

[0053] Supplemental aspects of this disclosure include an example method for a network entity to configure CSI reports. The example method includes sending a first control signaling to a UE indicating at least one beam prediction transmission configuration indication (TCI) state associated with a first delay and at least one non-beam prediction TCI state associated with a second delay. The network entity sends a second control signaling activating one or more of the at least one beam prediction TCI state and the at least one non-beam prediction TCI state. The network entity communicates with the UE at an action time associated with the first delay or the second delay based on the one or more TCI states.

[0054] Figure 1 A diagram 100 illustrates a wireless communication system associated with multiple cells 190. The wireless communication system includes user equipment (UE) 102 and base station / network entity 104. Some base stations may include an aggregated base station architecture, and others may include a decomposed base station architecture. The aggregated base station architecture utilizes a radio protocol stack physically or logically integrated within a single radio access network (RAN) node. The decomposed base station architecture utilizes a protocol stack physically or logically distributed across two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110). For example, CU 110 is implemented within a RAN node, and one or more DU 108s may be located in the same location as CU 110, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DU 108 may be implemented to communicate with one or more RU 106s. Any of RU 106, DU 108, and CU 110 can be implemented as a virtual unit, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). Base station / network entity 104 (e.g., an aggregated base station or a decomposed unit of a base station, such as RU 106 or DU 108) can be referred to as a transmit / receive point (TRP).

[0055] The operation and / or network design of base station (BS) 104 can be based on the aggregation characteristics of base station functionality. For example, a decomposed base station architecture can be utilized in an Integrated Access Backhaul (IAB) network, an Open Radio Access Network (O-RAN) network, or a Virtual Radio Access Network (vRAN) (which may also be referred to as a Cloud Radio Access Network (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing functionality for at least one unit, which allows for flexibility in network design. Various units in a decomposed base station architecture or a decomposed RAN architecture can be configured to communicate with at least one other unit via wired or wireless communication. For example, base stations (BS) 104d, 104e and / or RUs 106a, 106b, 106c, 106d can communicate with UEs 102a, 102b, 102c, 102d and / or 102s via one or more radio frequency (RF) access links based on a Uu interface. In the example, multiple RU 106 and / or BS 104 can simultaneously serve UE 102, such as through intra-cell and / or inter-cell access links between UE 102 and RU 106 / BS 104.

[0056] RU 106, DU 108, and CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via wired or wireless transmission media. For example, a wired interface may be configured to transmit or receive information / signals via a wired transmission media, such as a fronthaul link 160 between RU 106d and the baseband unit (BBU) 112 of BS 104d associated with cell 190d. BBU 112 includes DU 108 and CU 110, and may also have a wired interface (e.g., a midhaul link) configured between DU 108 and CU 110 to transmit or receive information / signals between DU 108 and CU 110. In a further example, a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) is configured to transmit and / or receive information / signals via a wireless transmission medium, such as information transmitted between RU 106a in cell 190a and BS 104e in cell 190e via inter-cell communication beams 136 to 138 of RU 106a and BS 104e.

[0057] RU 106 can be configured to implement low-level functionality. For example, RU 106 is controlled by DU 108 and can correspond to a logical node that manages RF processing functions or low-level PHY functionality, such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction, and filtering. The functionality of RU 106 can be based on functional partitioning, such as low-level functional partitioning.

[0058] RU 106 can transmit or receive over-the-air (OTA) communications with one or more UEs 102. For example, RU 106b of cell 190b communicates with UE 102b of cell 190b via a first communication beamset 132 of RU 106b and a second communication beamset 134b of UE 102b, which may correspond to inter-cell communication beamsets or, in some examples, inter-cell communication beamsets. For example, UE 102b of cell 190b can communicate with RU 106a of cell 190a via a third communication beamset 134a of UE 102b and a fourth communication beamset 136 of RU 106a. DU 108 can control the real-time and non-real-time characteristics of control plane and user plane communications of RU 106.

[0059] Any combination or individual reference to RU 106, DU 108, and CU 110 may correspond to BS 104. Therefore, BS 104 may include at least one of RU 106, DU 108, or CU 110. BS 104 provides UE 102 with access to the core network. BS 104 may relay communication between UE 102 and the core network (not shown). BS 104 may be associated with macro cells of high-power cellular base stations and / or small cells of low-power cellular base stations. For example, cell 190e may correspond to a macro cell, while cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network including at least one macro cell and at least one small cell may be referred to as a "heterogeneous network".

[0060] Transmissions from UE 102 to BS 104 / RU 106 are called uplink (UL) transmissions, while transmissions from BS 104 / RU 106 to UE 102 are called downlink (DL) transmissions. Uplink transmissions can also be called reverse link transmissions, and downlink transmissions can also be called forward link transmissions. For example, RU 106d uses the antenna of BS 104d in cell 190d to send downlink / forward link communication to UE 102d, or receive uplink / reverse link communication from UE 102d, based on the Uu interface associated with the access link between UE 102d and BS 104d / RU 106d.

[0061] The communication link between UE 102 and BS 104 / RU 106 can be based on multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be associated with one or more carriers. UE 102 and BS 104 / RU 106 can utilize a per-carrier Y MHz spectral bandwidth (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, 800 MHz, 1600 MHz, 2000 MHz, etc.) allocated in carrier aggregation up to a total of Yx MHz, where x component carriers (CCs) are used for communication in each of the uplink and downlink directions. Carriers can be adjacent to each other along the spectrum or can be non-adjacent. In the example, uplink and downlink carriers can be allocated asymmetrically, with more or fewer carriers allocated for the uplink or downlink. Component carriers can include a primary component carrier and one or more secondary component carriers. The primary component carrier can be associated with the primary cell (Pcell), and the secondary component carrier can be associated with the secondary cell (Scell).

[0062] Some UEs, such as UEs 102a and 102s, can perform device-to-device (D2D) communication via sidelinks. For example, sidelink communication / D2D links utilize the spectrum of the Wireless Wide Area Network (WWAN) associated with uplink and downlink communication. Such sidelink / D2D communication can be performed by various wireless communication systems, such as Wi-Fi, Bluetooth, LTE, and NR systems.

[0063] UE 102 and BS 104 / RU 106 may each include multiple antennas. These multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that facilitate beamforming operation. For example, RU 106b transmits downlink beamforming signals to UE 102b in one or more transmit directions of RU 106b based on a first communication beamset 132. UE 102b may receive downlink beamforming signals from RU 106b in one or more receive directions of UE 102b based on a second communication beamset 134b. In a further example, UE 102b may also transmit uplink beamforming signals (e.g., sounding reference signals (SRS)) to RU 106b in one or more transmit directions of UE 102b based on the second communication beamset 134b. RU 106b may receive uplink beamforming signals from UE 102b in one or more receive directions of RU 106b. UE 102b can perform beamforming to determine the optimal reception and transmission directions for beamforming signals. The transmission and reception directions of UE 102 and BS 104 / RU 106 can be the same or different.

[0064] In a further example, the beamforming signal can be transmitted between the first base station / RU 106a and the second BS 104e. For example, BS 104e of cell 190e can transmit the beamforming signal to RU 106a in one or more transmit directions of BS 104e based on communication beam 138. RU 106a can receive the beamforming signal from BS 104e of cell 190e in one or more receive directions of RU 106a based on RU communication beam 136. In a further example, BS 104e transmits a downlink beamforming signal to UE 102e in one or more transmit directions of BS 104e based on communication beam 138. UE 102e receives the downlink beamforming signal from BS 104e in one or more receive directions of UE 102e based on UE communication beam 130. UE 102e can also transmit uplink beamforming signals to BS 104e in one or more transmission directions of UE 102e based on UE communication beam 130, so that BS 104e can receive uplink beamforming signals from UE 102e in one or more reception directions of BS 104e.

[0065] BS 104 may include and / or be referred to as a network entity. That is, a "network entity" may refer to BS 104 or at least one element of BS 104, such as RU 106, DU 108, and / or CU 110. BS 104 may also include and / or be referred to as Next Generation Evolved Node B (ng-eNB), Next Generation NB (gNB), Evolved NB (eNB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP, network node, network device, or other related terms. Entities at BS 104 may be implemented as IAB nodes, relay nodes, sidelink nodes, aggregated (monolithic) base stations, or decomposed base stations including one or more RU 106, DU 108, and / or CU 110. Aggregated or decomposed base station sets may be referred to as Next Generation Radio Access Network (NG-RAN). In some examples, UE 102a operates in dual connectivity (DC) with BS 104e and base station / RU 106a. In such cases, BS 104e can be the primary node, while base station / RU 160a can be the secondary node.

[0066] Uplink / downlink signaling can also be communicated via a Satellite Positioning System (SPS) 114. In the example, the SPS 114 associated with cell 190c can communicate with one or more UEs 102 (such as UE 102c) and one or more BS 104 / RU 106 (such as RU 106c). The SPS 114 can correspond to one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN), or other satellite positioning / location systems. The SPS 114 can be associated with LTE signals, NR signals (e.g., based on round-trip time (RTT) and / or multiple RTT), wireless local area network (WLAN) signals, terrestrial beacon systems (TBS), sensor-based information, NR Enhanced Cell ID (NR E-CID) technology, downlink angle of departure (DL-AoD), downlink time difference of arrival (DL-TDOA), uplink time difference of arrival (UL-TDOA), uplink angle of arrival (UL-AoA), and / or other systems, signals, or sensors.

[0067] exist Figure 1In this configuration, any of UEs 102 may include a TCI state component 140 configured to receive a first control signaling from BS 104 indicating at least one beam prediction TCI state associated with a first delay and at least one non-beam prediction TCI state associated with a second delay. TCI state component 140 receives a second control signaling activating one or more of the at least one beam prediction TCI state and the at least one non-beam prediction TCI state. UE 102 then communicates with BS 104 at an action time associated with either the first or second delay based on one or more TCI states. BS 104 includes a TCI state component 150 configured to perform supplementary operations to the example methods described herein in conjunction with TCI state component 140.

[0068] therefore, Figure 1 A wireless communication system that can be implemented in conjunction with aspects of one or more other accompanying figures described herein is described. Furthermore, although the following description may focus on 5G NR, the concepts described herein are applicable to other similar fields, such as 5G Advanced and future versions, LTE, LTE Advanced (LTE-A), and other wireless technologies such as 6G.

[0069] Figure 2a Example illustration 200 shows a joint TCI indication for single transmit-receive point (sTRP) operation according to various aspects of this disclosure.

[0070] exist Figure 2a In this configuration, the network entity indicates only one TCI state. As shown in the figure, the network can first send a list 210 of TCI states configured by RRC to the UE. The network entity then sends MAC CE 220 to the UE to activate a subset of TCI states in the list 210 of TCI states configured by RRC. The network entity sends DCI 230 to indicate the TCI state corresponding to the selected or desired beam used for communication with the UE (e.g., for downlink and uplink communication).

[0071] Figure 2bExample illustration 240 of TCI indication for multi-transmitter-receiver point (mTRP) operation according to various aspects of this disclosure is shown. As shown, the network can indicate multiple TCI states, and each indicated TCI state corresponds to a signal of a TRP. The network entity sends an RRC signal that configures a TCI state list 250 for the UE. The network entity then sends a MAC CE 260 to the UE to activate a subset of the TCI states in the RRC-configured TCI state list 250. The network entity sends a DCI 270 to indicate multiple TCI states for the corresponding signal for each TRP. The indicated uniform TCI state can be applied to multiple channels. Table 1 shows example target channels for the indicated uniform TCI state. For other channels where the indicated uniform TCI state is not applied, the network entity can send dedicated signaling, such as a dedicated MAC CE, for beam indication.

[0072]

[0073] Table 1: Target / Applicable Channel / RS of the Indicated Uniform TCI Status

[0074] The UE begins applying the activated / indicated downlink TCI state after a first processing delay. The first processing delay may include processing delays for MAC CE decoding and ACK preparation, TCI time and frequency offset tracking delays, and / or UE beam tracking delays when the downlink TCI state is unknown. The UE begins applying the activated / indicated uplink TCI state after a second processing delay, which may include processing delays for MAC CE decoding and ACK preparation, path loss measurement delays for TCI when the UE has not yet tracked or maintained path loss for TCI, and UE beam tracking delays when the uplink TCI state is unknown. The UE begins applying the activated / indicated joint TCI state after the maximum of the first and second processing delays. Alternatively, the UE begins applying the activated / indicated joint TCI state after the first processing delay, which may include path loss measurement. Known and unknown TCI state conditions can generally be understood with reference to Sections 8.15.2 and 8.16.2 of 3GPP Technical Specification (TS) 38.133.

[0075] In one example (see, for example, sections 8.15.3 and 8.16.3 of 3GPP TS 38.133), for a TCI activation / indication based on MAC CE transmitted in slot n, the UE applies the activated / indicated TCI state at slot n+N. The network entity and the UE determine the value of T based on whether the TCI state is known or unknown. If the TCI state is known, the network entity and the UE apply the first TCI activation / indication delay for the DL TCI state and the UL TCI state, respectively. and The action delay of the activated / indicated TCI is determined; otherwise, the network entity and the UE determine the action delay based on the first TCI activation / indication delay used for the DL TCI state and UL TCI state, respectively. and To determine the action delay of the activated / indicated TCI. Activated / indicated TCI activation / indication delay. , , and The time unit is For example, the slot length based on the NR subcarrier spacing (SCS). express .

[0076]

[0077] in Indicates the number of time slots between DL data transmission with MAC CE and acknowledgment (ACK); Indicates the number of time slots in the subframe; if the activated / indicated TCI state is not in the list of active TCI states, then If the value is 1, otherwise 0; when the TCI state switching involves QCL-TypeD, if the activated / indicated TCI state is used for CSI-RS based L1-RSRP measurement, then It is 1 if the activated / indicated TCI state is used for SSB-based L1-RSRP measurements, and 0 if the TCI state switching only involves other QCL types. =1; It is the time from after the UE decodes the MAC CE to the first SSB transmission, where the SSB is quasi-co-located (QCL) with the source reference signal (RS) (e.g., CSI-RS) in the TCI state or is configured as the source reference signal (RS); This is the SSB processing delay, for example, 2 milliseconds (ms); This is the duration of the time slot, measured in milliseconds (ms). Indicates the delay of UE beam tracking, where the UE can measure the quasi-co-addressable source RS in TCI state or the SSB or CSI-RS configured as the source RS; NM is 1 if the UE does not maintain the target path loss reference signal (PL-RS), otherwise it is 0; When the TCI state is unknown, it is the time from the first PL-RS transmission after the Level 1 Reference Signal Received Power (L1-RSRP) measurement, or when the TCI state is known, it is the time from the first PL-RS transmission after the UE decodes the MAC CE to the first PL-RS associated with the activated / indicated TCI state. It is the periodicity of the target PL-RS.

[0078] Figure 3 Example illustration 300 of robust TCI activation / indication based on beam prediction according to various aspects of this disclosure is shown. As shown, the UE may optionally report 302 UE capabilities to network entity 104, indicating the supported configurations for beam prediction-based TCI activation / indication. For example, the UE may report at least one of the following UE capabilities: whether the UE supports beam prediction-based TCI activation / indication; the maximum number of configured TCI states for beam prediction; the maximum number of activated TCI states for beam prediction within a beam prediction window; the maximum number of activated TCI states across beam prediction windows; and the maximum number of beam prediction windows.

[0079] Based on the received UE capabilities, the network entity sends a 304 RRC signaling configuration of at least one of the following parameters: a first TCI state list for TCI activation / indication without beam prediction, a second TCI state list for TCI activation / indication with beam prediction, parameters for implementing TCI activation / indication with beam prediction, a first action delay for TCI state activation / indication without beam prediction, and a second action delay for TCI state activation / indication with beam prediction. The network entity may configure the TCI state list based on, for example, a downlink / joint TCI state list such as dl-OrJoint-TCIStateList and / or an uplink TCI state list such as ul-TCI-StateList. In some implementations, the first and second TCI state lists may be the same.

[0080] Then, the network entity sends a 306 Media Access Control (MAC) control element (CE), which indicates the set of active TCI states in either a configured first TCI state list or a second TCI state list. The network entity may optionally indicate at least one of the following: whether the active TCI state is based on beam prediction; activation / deactivation of the first DL RS for QCL parameter measurement; activation / deactivation of the second DL RS for path loss measurement; and the action delay of the active TCI state. Upon receiving a PDSCH with the MAC CE, the UE sends a 308 ACK to the network entity.

[0081] When a network entity activates a TCI state corresponding to multiple TCI code points via MAC CE, the network entity can send a 310 DCI indicating the TCI state for one of the TCI code points. The network entity can also indicate at least one of the following via the DCI: whether the activated TCI state was selected from a TCI state with beam prediction or a TCI state without beam prediction; and the action delay of the indicated TCI state. The network entity can schedule the PDSCH via the DCI. After receiving the DCI or the PDSCH scheduled by the DCI, the UE can send a 312 ACK to the network entity.

[0082] Then, the network entity and the UE can determine the timing of the action of the TCI state activated / indicated by 314, and conduct further communication (e.g., downlink communication or uplink communication) based on the activated or indicated TCI state.

[0083] Figure 4 Example illustration 400 of UE behavior in robust TCI activation / indication based on beam prediction according to various aspects of this disclosure is shown. As shown, the UE may optionally send 402 information about UE capabilities in supported TCI activation / indication configurations based on beam prediction.

[0084] The UE then receives a 404 RRC signaling configuration of at least one of the following: a first TCI state list for TCI activation / indication without beam prediction, a second TCI state list for TCI activation / indication with beam prediction, parameters for implementing TCI activation / indication with beam prediction, a first action delay for TCI state activation / indication without beam prediction, and a second action delay for TCI state activation / indication with beam prediction.

[0085] The UE receives a 406 MAC CE-based TCI activation / indication, which indicates the set of activated TCI states in a configured first or second TCI state list and optionally indicates at least one of the following: whether the activated TCI state is based on beam prediction; activation / deactivation of the first DL RS for QCL parameter measurement; activation / deactivation of the second DL RS for path loss measurement; and the action delay of the activated TCI state. The UE sends a 408 ACK for the PDSCH with MAC CE.

[0086] The UE may optionally receive a 410 DCI indicating at least one of the activated TCI states and optionally indicating at least one of the following: whether the activated TCI state was selected from a TCI state with beam prediction or a TCI state without beam prediction; and the action delay of the indicated TCI state. The UE may optionally send a 412 acknowledgment of the DCI or a PDSCH scheduled by the DCI.

[0087] Then, the UE determines the action time of the TCI state activated / indicated by 414, and performs further communication based on the activated / indicated TCI state (e.g., receiving downlink channels / signals or sending uplink channels / signals).

[0088] Figure 5 Example illustration 500 shows network entity behavior in robust TCI activation / indication based on beam prediction according to various aspects of this disclosure. Network entity behavior and... Figure 4 This corresponds to the UE behavior. As shown in the figure, the network entity can optionally receive 502 regarding the UE capabilities of the supported TCI activation / indication configuration based on beam prediction.

[0089] The network entity then sends a 504 RRC signaling configuration of at least one of the following: a first TCI state list for TCI activation / indication without beam prediction, a second TCI state list for TCI activation / indication with beam prediction, parameters for implementing TCI activation / indication with beam prediction, a first action delay for TCI state activation / indication without beam prediction, and a second action delay for TCI state activation / indication with beam prediction.

[0090] The network entity sends a 506 MAC CE-based TCI activation / indication, which indicates the set of activated TCI states in a configured first or second TCI state list and optionally indicates at least one of the following: whether the activated TCI state is based on beam prediction; activation / deactivation of the first DL RS for QCL parameter measurement; activation / deactivation of the second DL RS for path loss measurement; and the action delay of the activated TCI state. The UE receives a 508 ACK for the PDSCH with MAC CE.

[0091] The network entity may optionally send a 510 DCI indicating at least one of the activated TCI states and optionally indicating at least one of the following: whether the activated TCI state was selected from a TCI state with beam prediction or a TCI state without beam prediction; and the action delay of the indicated TCI state. The network entity may optionally receive 512 acknowledgments of the DCI or a PDSCH scheduled by the DCI.

[0092] The network entity then determines the timing of the action of the TCI state activated / indicated by 414, and performs further communication (e.g., sending downlink channels / signals or receiving uplink channels / signals) based on the activated / indicated TCI state.

[0093] In this disclosure, unless otherwise stated, RRC signaling from a network entity to a UE may indicate an RRC reconfiguration message or a System Information Block (SIB), wherein the SIB may be an existing SIB (e.g., SIB1) or a new SIB sent by the network entity (e.g., SIB J, where J is an integer greater than 21). RRC signaling from a UE to a UE may indicate an RRC reconfiguration message forwarded by the UE.

[0094] In this disclosure, unless otherwise stated, network entities may receive UE capabilities from the UE or from the core network (e.g., the Access and Mobility Management Function (AMF)) or another network entity.

[0095] Figure 6aExample 600 of a separate TCI configuration for TCI activation / indication with / without beam prediction, according to various aspects of this disclosure, is shown. As shown, a network entity can send a list 610 of non-beam prediction TCI states configured with RRC (or a list of TCI states without beam prediction), and then the MAC CE activates one or more of the TCI states 620. The network entity can also send a list 630 of beam prediction TCI states configured with RRC (or a list of TCI states with beam prediction). The MAC CE then activates one or more of the TCI states 640 with beam prediction.

[0096] In this embodiment, the network entity configures TCI states with and without beam prediction in a configured TCI state list or in different TCI state lists for TCI states with and without beam prediction. The UE can apply a first action delay to the activated / indicated TCI state without beam prediction and a second action delay to the activated / indicated TCI state with beam prediction, wherein the first delay and / or the second delay can be predefined or configured by the network entity, and the first action delay can be less than, equal to or greater than the second action delay.

[0097] In one example, the network entity can be configured to use a TCI state, such as TCI-State or TCI-UL-State, for beam prediction. Then, for TCI activation / indication without beam prediction, the network entity can indicate a TCI state configured not for beam prediction. For TCI activation / indication with beam prediction, the network entity can indicate a TCI state configured for beam prediction.

[0098] In another example, the network entity can configure a first TCI state list for TCI activation / indication without beam prediction and a second TCI state list for TCI activation / indication with beam prediction. Then, for TCI activation / indication without beam prediction, the network entity can indicate the TCI state in the first TCI state list. For TCI activation / indication with beam prediction, the network entity can indicate the TCI state in the second TCI state list.

[0099] Figure 6b An example 650 of a common TCI configuration for TCI activation / indication with / without beam prediction, according to various aspects of this disclosure, is shown. As shown, a network entity can send a general TCI state list 660 of RRC configuration, where the TCI states include beam prediction TCI states and non-beam prediction TCI states. The MAC CE can then activate a subset 670 of TCI states without beam prediction. Another subset 690 of TCI states with beam prediction can also be activated.

[0100] In some embodiments, the network entity can configure common TCI states for TCI activation / indication with or without beam prediction. In one example, the network entity can configure a common downlink / joint TCI state list and / or a common uplink TCI state list. The network entity can then configure via MAC CE or DCI whether the activated / indicated TCI state is based on beam prediction, for example, whether a first action delay or a second action delay is applied.

[0101] Figure 7a An example 700 of TCI activation / indication based on MAC CE with / without beam prediction according to various aspects of this disclosure is illustrated. As shown, the network entity sends MAC CE 710 to the UE in the PDSCH at time 715 for TCI activation or indication. The UE sends an ACK to the PDSCH to the network entity at time 720. When a parameter or flag (e.g., "F") in the MAC CE indicates no beam prediction, the UE applies the activated TCI state at time 725. Alternatively, when a parameter or flag (e.g., "F") in the MAC CE indicates beam prediction, the UE applies the activated TCI state at time 730. The time period between time 720 and time 725 is a first action delay 740. The time period between time 720 and time 730 is a second action delay 745.

[0102] In this embodiment, the network entity can send a MAC CE for TCI activation with or without beam prediction. The network entity can configure whether the activated TCI state in the MAC CE is based on beam prediction. The UE can apply a first action delay to the activated / indicated TCI state without beam prediction and a second action delay to the activated / indicated TCI state with beam prediction, wherein the first delay and / or the second delay can be predefined or configured by the network entity.

[0103] In some implementations, the network entity configures whether each activated TCI state is based on beam prediction. In one example, the network entity may indicate a bitmap in the MAC CE, where one bit is used to indicate whether an activated TCI state is based on beam prediction, or whether the UE should apply a first predefined / configured action delay or a second predefined / configured action delay to TCI activation / indication.

[0104] In some implementations, the network entity configures whether each activated TCI state is based on beam prediction according to the TCI code point group in the MAC CE. In one example, the network entity may consider the first four TCI code points as the first TCI code point group for activated TCI states with beam prediction, and the last four TCI code points as the second TCI code point group for activated TCI states without beam prediction. In another example, the network entity may configure X (e.g., 1, 2, 3, 4) TCI code points as the first TCI code point group for activated TCI states without beam prediction, and Y (e.g., 5, 6, 7, 8) TCI code points as the second TCI code point group for activated TCI states with beam prediction, where X+Y equals the total number of TCI code points. The UE should apply a first predefined / configured action delay or a second predefined / configured action delay to TCI activation / indication based on which TCI code point group it belongs to.

[0105] In some other implementations, the network entity configures via MAC CE whether the activated TCI state corresponding to a TRP indicated by the MAC CE is based on beam prediction, for example, whether a first action delay or a second action delay is applied. In one example, the network entity and the UE can determine that a first TCI state for all TCI code points corresponds to a first TRP, and a second TCI state for all TCI code points corresponds to a second TRP. In another example, the network entity and the UE can determine that TCI states for the same control resource set (CORESET) pool index correspond to one TRP, while TCI states for different CORESET pool indices correspond to different TRPs.

[0106] In some other implementations, the network entity configures whether the active TCI states of all TRPs, as indicated by the MAC CE, are based on beam prediction, for example, whether a first action delay or a second action delay is applied. In one example, the network entity provides this configuration via a field in the MAC CE.

[0107] In some implementations, after the UE applies an activated TCI state, the network entity and / or the UE can determine that the indicated TCI state is an activated TCI state corresponding to a TCI code point, which can be predefined—e.g., a first TCI code point—or configured or indicated by the network entity via RRC signaling, MAC CE, or DCI. The network entity and the UE can communicate based on the determined indicated TCI state until they receive further TCI activation / indication signaling.

[0108] Figure 7bAn example 750 of beam prediction-based TCI activation / indication with MACCE for multiple prediction windows according to aspects of this disclosure is illustrated. As shown, at time 765, the network entity sends a MAC CE 760 to the UE in the PDSCH for TCI activation or indication. The MAC CE 760 includes beam prediction TCI states (e.g., TCI states 5 and 8) and non-beam prediction TCI states (e.g., TCI states 1 and 3). At time 770, the UE sends an ACK to the PDSCH to the network entity. At time 775, the UE applies the activated TCI states (e.g., TCI states 1 and 3) unrelated to beam prediction. Alternatively, at time 780, the UE applies the activated TCI states (e.g., TCI states 5 and 8) associated with beam prediction. The time period between time 770 and time 775 is a first action delay 785 based on a first prediction window configured by the MAC CE 760. The time interval between time 770 and time 780 is based on the second action delay 790 of the second prediction window configured by MAC CE 760.

[0109] In this embodiment, the network entity provides TCI activation / indication without beam prediction via a first type of MAC CE (e.g., TCI states 1 and 3 of MAC CE 760), and provides TCI activation / indication with beam prediction via a second type of MAC CE (e.g., TCI states 5 and 8 of MAC CE 760). The first type of MAC CE may be based on a first logical channel identifier (LCID) or an extended LCID (eLCID), and the second type of MAC CE may be based on a second LCID or an eLCID, wherein the first LCID / eLCID and the second LCID / eLCID may be predefined or configured by the network entity.

[0110] In some implementations, a network entity can configure the activated / indicated TCI state for a prediction window via a single MAC CE. The network entity can further configure the action delay of the TCI state. The network entity can send multiple MAC CEs to configure the activated / indicated TCI state for multiple prediction windows.

[0111] In some other implementations, the network entity can configure the activated / indicated TCI state for multiple prediction windows through a single MAC CE. The network entity can configure the TCI state for different prediction windows corresponding to one or more TCI code points. A value indicating the TCI state can be reserved to indicate that the network entity did not predict a TCI state within a given prediction window.

[0112] In some implementations, after the UE applies an activated TCI state, the network entity and / or the UE can determine that the indicated TCI state is an activated TCI state corresponding to a TCI code point, which can be predefined—e.g., a first TCI code point—or configured or indicated by the network entity via RRC signaling, MAC CE, or DCI. The network entity and the UE can communicate based on the determined indicated TCI state until they receive further TCI activation / indication signaling.

[0113] Figure 8a An example 800 of a TCI indication with / without beam prediction based on a common DCI format is illustrated according to various aspects of this disclosure. As shown, when a non-beam prediction TCI state 802 (e.g., TCI states 1, 3, 5, and 8) and a beam prediction TCI state 804 (e.g., TCI states 13, 20, 21, and 23) are activated, the network entity sends a DCI 810 for the TCI indication (e.g., TCI code point 0, corresponding to TCI state 1 (without beam prediction) and TCI state 13 (with beam prediction)). The UE sends an ACK 812 for a PDSCH scheduled by either the DCI used for beam prediction or the DCI not used for beam prediction. When the DCI is not used for beam prediction, the UE applies the indicated TCI state 1 at time 814. When the DCI is used for beam prediction, the UE applies the indicated TCI state 13 at time 816. The time period between time 812 and time 814 is a first action delay 820. The time interval between time 812 and time 816 is the second action delay 822.

[0114] In an embodiment, the network entity may send a DCI for a TCI indication with or without beam prediction. The network entity indicates whether the indicated TCI state in the DCI is based on beam prediction. The UE may apply a first action delay to the indicated TCI state without beam prediction and a second action delay to the indicated TCI state with beam prediction, wherein the first delay and / or the second delay may be predefined or configured by the network entity, and the first action delay may be less than, equal to, or greater than the second action delay.

[0115] In some implementations, the network entity indicates whether the indicated TCI state is based on beam prediction via a DCI field, for example, whether a first action delay or a second action delay is applied. In one example, a 1-bit DCI field can indicate whether the indicated TCI state is used for beam prediction. In another example, the network entity can individually indicate whether each indicated TCI state is used for beam prediction. In yet another example, the network entity can indicate the prediction window index of the indicated TCI state, where a state of the field (e.g., a first state) can indicate that the indicated TCI state is for a TCI indication without beam prediction.

[0116] In some other implementations, the network entity indicates whether the indicated TCI state is based on beam prediction by indicating the TCI code points corresponding to the TCI states with or without beam prediction; for example, whether a first action delay or a second action delay is applied. For each TCI state corresponding to a TCI code point, the network entity can configure whether each or all TCI states are based on beam prediction. The network entity can configure whether the TCI states are based on beam prediction based on a group of TCI code points, for example, a first group of TCI code points with X (e.g., 1, 2, 3, 4) TCI code points for TCI states with beam prediction and a second group of TCI code points with Y (e.g., 5, 6, 7, 8) TCI code points for TCI states without beam prediction, where X + Y equals the total number of TCI code points.

[0117] In some other implementations, network entities indicate whether the indicated TCI state is based on beam prediction, for example, whether a first action delay or a second action delay is applied, via a Radio Network Time Identifier (RNTI) associated with the DCI. In one example, one RNTI can be configured or predefined for TCI indication with beam prediction, while another RNTI can be configured or predefined for TCI indication without beam prediction.

[0118] In some other implementations, network entities indicate whether the indicated TCI state is based on beam prediction, such as applying a first action delay or a second action delay, by the position of the PDCCH with DCI (e.g., the starting control channel element (CCE) index). In one example, a PDCCH with an odd-numbered starting CCE index can be used for TCI indication with beam prediction, while a PDCCH with an even-numbered starting CCE index can be used for TCI indication without beam prediction.

[0119] Figure 8bAn example 830 of a TCI indication with beam prediction for multiple beam prediction windows according to aspects of this disclosure is shown. As shown, when TCI state 832 (e.g., TCI states 1, 3, 5, and 8) is activated for prediction window 1 and TCI state 834 (e.g., TCI states 13, 20, 21, and 23) is activated for prediction window 2, the network entity sends a DCI 840 for the TCI indication (e.g., TCI code point 0, corresponding to TCI state 1 (without beam prediction) and TCI state 13 (with beam prediction)). The UE sends an ACK 842 for a PDSCH scheduled by a DCI used for beam prediction or a DCI not used for beam prediction. When the DCI is not used for beam prediction, the UE applies the indicated TCI state 1 at time 844. When the DCI is used for beam prediction, the UE applies the indicated TCI state 13 at time 846. The time interval between time 842 and time 844 is the first action delay of 850. The time interval between time 842 and time 846 is the second action delay of 855.

[0120] In embodiments, network entities can indicate TCI states with or without beam prediction using different DCI formats. In one example, a network entity can indicate a TCI state without beam prediction using DCI formats 1_1 and 1_2. A network entity can indicate a TCI state with beam prediction using another DCI format, such as DCI format 1_4 or 2_10. A network entity can indicate TCI states for one or more prediction windows. In one example, a network entity indicates the TCI state for one prediction window using a single DCI field. In another example, a network entity indicates the TCI state for multiple prediction windows using a single DCI field, wherein the network entity can configure the TCI states for multiple prediction windows corresponding to a single TCI code point via MAC CE.

[0121] Figure 8cAn example 860 of TCI indication based on the activated TCI state at the time of action for TCI indication according to aspects of this disclosure is shown. As shown, when non-TCI states 862 (e.g., TCI states 1, 3, 5, and 8) and 864 (e.g., TCI states 13, 20, 21, and 23) have been activated, the network entity sends a DCI 870 for TCI indication (e.g., TCI code point 0, which corresponds to TCI state 1 (without beam prediction) and TCI state 13 (with beam prediction)). The UE sends an ACK 872 for a PDSCH scheduled by a DCI used for beam prediction or a DCI not used for beam prediction. When the DCI is not used for beam prediction, the UE applies the indicated TCI state 1 at time 874. When the DCI is used for beam prediction, the UE applies the indicated TCI state 13 at time 876 (or continues to use TCI state 1). The time interval between time 872 and time 874 is the first action delay of 880.

[0122] In another embodiment, the network entity indicates the TCI state via DCI based on the activated TCI state at a certain time, where the time can be a predefined first time slot for applying the indicated TCI state or the first / last symbol of the DCI, or configured by the network entity via RRC signaling or MAC CE or DCI.

[0123] In some implementations, after the UE applies an active TCI state from a TCI indication with or without beam prediction, the UE can continue using the previously indicated TCI state until the UE receives another TCI indication. In other implementations, after the UE applies an active TCI state from a TCI indication with or without beam prediction, the UE can update the indicated TCI state based on the active TCI state and / or the TCI code point indicated by the DCI. In one example, the UE can apply the indicated TCI based on the active TCI state corresponding to the indicated TCI code point. In another example, the UE can apply the indicated TCI based on the active TCI state corresponding to a predefined TCI code point—e.g., a first TCI code point.

[0124] Figure 9aExample 900 of TCI activation / indication based on periodic downlink (DL) reference signals (RS) according to various aspects of this disclosure is illustrated. For a TCI state with beam prediction, the network entity can configure a first periodic DL RS (e.g., SSB or CSI-RS) quasi-co-located in the TCI state or with a DL RS used for QCL indication in the TCI state, and the network entity can configure a second periodic DL RS (e.g., SSB or CSI-RS) in the TCI state or associated with the TCI state as a PL-RS. The network entity can provide the configuration via RRC signaling, MAC CE, or DCI. The network entity can configure the same DL RS as the first periodic DL RS and the second periodic DL RS or different DL RS. The UE can then measure the first periodic DL RS for QCL measurement and measure the second periodic DL RS for path loss measurement for the activated / indicated TCI state.

[0125] like Figure 9a As shown, the UE first receives a PDSCH with a MAC CE for TCI activation / indication at time 910. Then, the UE sends an ACK for the PDSCH at time 912. The UE performs path loss measurement using the second periodic DL RS resource at time 914. The UE performs QCL measurement using the first periodic DL RS resource at time 916. The UE performs path loss measurement using the second periodic DL RS resource at time 918. The UE performs path loss measurement using the second periodic DL RS resource at time 920. From time 910 until time 920, an action delay of 922 is used for the activated / indicated TCI.

[0126] Figure 9bExamples of QCL / path loss measurements based on semi-persistent DL RSs for an activated / indicated TCI state are shown according to various aspects of this disclosure. A network entity may activate a first semi-persistent DL RS, such as a dynamically activated / deactivated semi-persistent CSI-RS or SSB, which is quasi-co-located with or configured as a DL RS for QCL-Type D (Spatial Receiver Parameters) indication in the TCI state. A network entity may activate a second semi-persistent DL RS—such as a dynamically activated / deactivated semi-persistent CSI-RS or SSB—as a PL-RS associated with or configured in the TCI state. A network entity may activate a third semi-persistent DL RS, such as a dynamically activated / deactivated semi-persistent CSI-RS or SSB, which is quasi-co-located with or configured as a DL RS for QCL-Type A (Average Delay, Delay Spread, Doppler Shift, and Doppler Spread) indication. Network entities can configure the same or different DL RS as the first semi-persistent DL RS, the second semi-persistent DL RS, and / or the third semi-persistent DL RS. The UE can then measure the first semi-persistent DL RS for QCL-Type D measurements, measure the second DL RS for path loss measurements, and measure the third semi-persistent DL RS for QCL-Type A measurements for the activated / indicated TCI state.

[0127] In some implementations, a network entity can activate the first / second / third semi-persistent DL RS via the same MAC CE used for TCI activation / indication. In one example, the network entity can configure the first semi-persistent DL RS as a DL RS for QCL-TypeD indication or quasi-co-located with a DL RS for QCL-TypeD indication in the TCI state; the network entity can configure the second semi-persistent DL RS as a PL-RS in or associated with the TCI state; and the network entity can configure the third semi-persistent DL RS as a DL RS for QCL-TypeA indication or quasi-co-located with a DL RS for QCL-TypeA indication in the TCI state. The first / second / third DL RS can be activated when the corresponding TCI state is activated and deactivated when the corresponding TCI state is deactivated.

[0128] In some other implementations, network entities can activate the first / second / third semi-persistent DL RS via a MAC CE other than the MAC CE used for TCI activation / indication.

[0129] like Figure 9bAs shown, the UE first receives a PDSCH with a MAC CE for TCI activation / indication at time 932. Then, the UE sends an ACK for the PDSCH at time 934. At time 936, the UE performs a QCL-Type D measurement using the first half-persistent DL RS resource. At time 938, the UE performs a QCL-Type A measurement using the third half-persistent DL RS resource. At time 940, the UE performs a path loss measurement using the second half-persistent DL RS resource. The UE performs a path loss measurement using the second half-persistent DL RS resource at time 942. From time 910 until time 942, an action delay of 950 is applied to the activated / indicated TCI.

[0130] Figure 9c Example 960 of QCL / path loss measurement based on periodic, semi-persistent, and / or aperiodic DL RSs according to various aspects of this disclosure is illustrated. A network entity may configure a first periodic / semi-persistent DL RS, such as a CSI-RS or SSB, which is quasi-co-located with or configured as the DL RS used for QCL-Type D indication in a TCI state. A network entity may configure a second periodic / semi-persistent DL RS—such as a CSI-RS or SSB—as a PL-RS associated with or configured in a TCI state. A network entity may configure a third periodic / semi-persistent DL RS, such as a CSI-RS or SSB, which is quasi-co-located with or configured as the DL RS used for QCL-Type A indication. The network entity may configure the same DL RS as the first, second, and / or third DL RS or different DL RSs.

[0131] In some implementations, for an unknown TCI state, the network entity can trigger a first aperiodic DL RS resource set for QCL-TypeD, such as aperiodic CSI-RS resources. The network entity can configure the CSI-RS resources to originate from the same antenna port, for example, repeating to 'on', and the CSI-RS resources are quasi-co-located with the DL RS used for QCL indication in the activated / indicated TCI state. The network entity can trigger the first aperiodic DL RS resource set via a MAC CE for TCI activation / indication or a separate DCI. The network entity can trigger at least N aperiodic DL RS resources for UE beam tracking, where N can be predefined—e.g., N=8—or reported by the UE capability.

[0132] In some implementations, for TCI states where path loss is not maintained, the network entity can trigger a second set of aperiodic DL RS resources, such as aperiodic CSI-RS resources, for path loss measurement. The network entity can configure the CSI-RS resources to originate from the same antenna port, for example, repeatedly set to 'on', and the CSI-RS resources are quasi-co-located with or associated with the PL-RS in the activated / indicated TCI state. The network entity can trigger the second set of aperiodic DL RS resources via a MAC CE used for TCI activation / indication. The network entity can trigger at least N aperiodic DL RS resources for path loss measurement, where M can be predefined, for example, M=5, or reported by UE capabilities.

[0133] In some implementations, a network entity can trigger a third set of aperiodic DL RS resources, such as aperiodic CSI-RS resources, for QCL-Type A measurements. The network entity can configure the CSI-RS resources as Tracking Reference Signals (TRS), for example, CSI-RS resources in a CSI-RS resource set configured with TRS-Info, and the CSI-RS resources are quasi-co-located with the DL RS used for QCL indication in the activated / indicated TCI state. The network entity can trigger the third set of aperiodic DL RS resources via a MACCE for TCI activation / indication or a separate DCI.

[0134] The network entity may send the first aperiodic DL RS resource set X symbols before the second / third aperiodic DL RS resource set, where X is a certain amount of time reserved for UE processing for beam measurement and UE beam identification of the first aperiodic DL RS resource set, and the value of X may be predefined, for example, 14 symbols, or reported by UE capability.

[0135] Then, the UE can measure the first / second / third aperiodic DL RS resource set after receiving the TCI activation / indication signaling and before applying the activated / indicated TCI state for QCL-Type A / QCL-Type D / path loss measurement. After applying the activated / indicated TCI state, the UE measures the first / second / third periodic / semi-persistent DL RS for QCL-Type A / QCL-Type D / path loss measurement.

[0136] like Figure 9cAs shown, the UE first receives a PDSCH with a MAC CE for TCI activation / indication at time 962. Then, at time 964, the UE performs QCL-Type D measurement using the first aperiodic DL RS resource set. At time 966, the UE performs path loss measurement using the second aperiodic DL RS resource set. At time 968, the UE performs QCL-Type A measurement using the third aperiodic DL RS resource set. The UE sends an ACK for the PDSCH at time 970.

[0137] The UE applies the activated TCI state at time 972. At time 974, the UE performs further QCL-Type D measurements using the first periodic / semi-persistent DL RS resource. At time 976, the UE performs further path loss measurements using the second periodic DL RS resource. At time 978, the UE performs QCL-Type A measurements using the third DL RS resource. The time interval between time 970 and time 972 is the action delay 980 for the activated / indicated TCI.

[0138] In this embodiment, network entities and / or UEs can determine the action time and / or action delay of the activated / indicated TCI state based on whether the TCI state is unknown, known, or predicted. Network entities and / or UEs can determine different action delays for unknown / known / predicted TCI states. For a predicted TCI state, network entities and / or UEs can further determine whether the predicted TCI state is unknown or known. Network entities and / or UEs can determine different action delays for unknown / known predicted TCI states.

[0139] In one example, network entities and / or UEs can determine the known / unknown state of the predicted downlink TCI state based on the following: The downlink TCI state used for beam prediction is known if / when the following conditions are met: - During the following time periods ○ The handover from the last transmission of RS resources used for L1-RSRP measurement reports for the target downlink TCI state to the completion of the active downlink TCI state handover, wherein the RS resources used for L1-RSRP measurements are RS resources in the target downlink TCI state or quasi-co-located with the target downlink TCI state. ○ Receive downlink TCI state switching instruction, and / or the beam prediction window for the target downlink TCI state is within Z ms after the last transmission of RS resources for beam reporting or measurement with or without UE-side beam prediction (e.g., Z=1280). ○ Before the downlink TCI state switching command or the beam prediction window for the target downlink TCI state, the UE has sent at least one measured or predicted L1-RSRP report for the target downlink TCI state. ○ During the downlink TCI state transition period, the target downlink TCI state remains detectable. During the downlink TCI handover period, the SSB associated with the downlink TCI state remains detectable. SNR ≥ -3 dB in downlink TCI state SSB can be associated with the serving cell PCI or a PCI that is different from the serving cell PCI.

[0140] Otherwise, the downlink TCI status is unknown.

[0141] In one example, network entities and / or UEs can determine the known / unknown state of the predicted uplink TCI state as follows: The uplink TCI state used for beam prediction is known if the following conditions are met: - During the period from the last transmission of RS resources used for L1-RSRP measurement reports for the target uplink TCI state to the completion of the active uplink TCI state handover, wherein the RS resources used for L1-RSRP measurements are RS resources in the target uplink TCI state or quasi-co-located with the target uplink TCI state. ○ Upon receiving an uplink TCI state switching instruction, and / or within Z ms after the last transmission of RS resources for beam reporting or measurement with or without UE-side beam prediction (e.g., Z=1280), the beam prediction window for the target uplink TCI state is determined. ○ Before the uplink TCI state switching command or the beam prediction window of the target uplink TCI state, the UE has sent at least one measured or predicted L1-RSRP report for the target uplink TCI state. ○ During the uplink TCI state transition period, the RS configured in the target uplink TCI state remains detectable. The SNR of the RS configured in the target uplink TCI state is ≥ -3 dB. ○ During the uplink TCI state transition period, the target uplink TCI state remains detectable. ○ During the uplink TCI handover period, the SSB associated with the uplink TCI state remains detectable. Uplink TCI state SNR ≥ -3 dB SSB can be associated with the serving cell PCI or a PCI that is different from the serving cell PCI.

[0142] Otherwise, the uplink TCI status is unknown.

[0143] In some implementations, in the L1-RSRP report, the UE can report whether the L1-RSRP is the measured L1-RSRP or the predicted L1-RSRP. The NE can configure the UE to report this information. Alternatively, the NE can configure the UE to report either the measured L1-RSRP or the predicted L1-RSRP for each reported SSB or CSI-RS in the L1-RSRP, or for the L1-RSRP report itself. The conditions used to determine the aforementioned unknown / known TCI can be based solely on beam reports with the measured L1-RSRP.

[0144] In some other implementations, the network entity and the UE can determine the predicted TCI state as an unknown TCI state. Therefore, the network entity and the UE can determine the action delay of the predicted TCI state as the action delay of the unknown TCI state.

[0145] In some other implementations, the starting point of the beam prediction window Tpred ms may come from any of the following: Tpred1: Time slot for receiving TCI activation / indication signaling Tpred2: Time slot for ACK transmission of TCI activation / indication signaling In an embodiment, for TCI activation / indication with beam prediction, the UE can measure QCL / path loss before or after the beam prediction window indicated by the network entity. The network entity can configure the beam prediction window based on Tpred1 and the associated list of predicted TCI states {TCIp#1,TCIp#2,…}, and send TCI activation / indication signaling to the UE. For an older or previous activated / indicated TCI state in the list of predicted TCI states, the UE begins QCL / path loss measurement for the target activated / indicated TCI state after the prediction window. In some implementations, if a UE capability bit is indicated to the network to support QCL / path loss measurement for the target activated / indicated TCI state before the prediction window (e.g., while the prediction window is still active), the UE can begin QCL / path loss measurement for the target activated / indicated TCI state before the prediction window (e.g., while the prediction window is still active). For older or previous TCI states not in the predicted TCI state list {TCIp#1,TCIp#2,…}, the UE may or may not initiate QCL / path loss measurement for the target active / indicated TCI state before the prediction window, depending on whether the UE capability bit for supporting QCL / path loss measurement for the target active / indicated TCI state has been indicated to the network. Before the beam prediction window expires, the UE may communicate with the network entity based on the older or previous active / indicated TCI state. The network entity and the UE then determine the action delay for the target active / indicated TCI based on at least one of the following: Tpred1: Beam prediction window, where the starting point is the time slot where TCI activation / indication signaling is received. Tpred2: Beam prediction window, where the starting point is the time slot of the ACK transmission for TCI activation / indication signaling. Are old or previously activated / indicated TCI states in the predicted TCI state list? Does the UE begin QCL / path loss measurement for the target activation / indication TCI state before or after the prediction window? Is the TCI state of the target activation / indication known or unknown? Number of time slots between DL data transmission and acknowledgment (ACK) with MAC CE Number of time slots in a subframe The time from the predicted time window for the activated / indicated TCI or from the time the UE decodes the TCI activation / indication signaling to the first SSB transmission. : When the target activation / indication TCI state is known, is the target activation / indication TCI state not included in the list of active TCI states? : When the target activation / indication TCI state is unknown, is the target activation / indication TCI state not included in the list of active TCI states? SSB processing delay : Duration of time slot, in milliseconds : UE beam tracking delay, where the UE can measure the quasi-co-address of the source RS in the activated / indicated TCI state or the SSB or CSI-RS configured as that source RS. NM: Is the target path loss reference signal (PL-RS) maintained? : When the TCI state is unknown, the time from the measurement of the first layer reference signal received power (L1-RSRP) to the first PL-RS transmission is... Or, when the TCI state is known, the time from after the UE decodes the TCI activation / indication signaling to the first PL-RS associated with the activated / indicated TCI state; Periodicity of the target PL-RS In some implementations, if the network is indicated with a UE capability bit to support QCL / path loss measurement for the target activation / indication TCI state before the prediction window, the UE can begin QCL / path loss measurement for the target activation / indication TCI state after receiving the TCI activation / indication signaling.

[0146] In some implementations, if the UE capability bit is indicated to the network to support QCL / path loss measurement for the target activation / indication TCI state before the prediction window, the UE can begin QCL / path loss measurement for the target activation / indication TCI state after sending an ACK for the TCI activation / indication signaling.

[0147] In some implementations, the NE can configure whether the UE should begin QCL / path loss measurement before or after the beam prediction window. The NE can transmit the configuration via RRC signaling, MAC CE, or DCI. The NE can provide the configuration by TCI status, by bandwidth portion, by serving cell, or by serving cell group.

[0148] In one example, for TCI activation / indication with beam prediction, if it is assumed that both the start point of the beam prediction window Tpred1 and the time of receiving the PDSCH with the MAC CE for TCI activation / indication in the target TCI state are transmitted in time slot n', then the UE applies the activated / indicated TCI state at time slot n'+K. The network entity and the UE determine the value of K based on whether the target activated / indicated TCI state is known or unknown. If the TCI state is known, the network entity and the UE determine the first TCI activation / indication delay based on the DL TCI state and the UL TCI state, respectively. and The action delay K for TCI activation / indication of the target is determined; otherwise, the network entity and UE determine the second TCI activation / indication delay based on the DL TCI state and UL TCI state, respectively. and To determine the action delay K of the TCI that the target is activated / indicated.

[0149] In some implementations, It is determined in the following ways. In some implementations, this can be based on one of the following conditions: The old or previous activated / indicated TCI state is in the list of predicted TCI states, and no UE capability bit is indicated to support QCL / path loss measurement for the target activated / indicated TCI state before the prediction window, or the NE configures the UE to start QCL / path loss measurement for the target activated / indicated TCI state after the prediction window. The old or previous activated / indicated TCI state is not in the list of predicted TCI states, and no UE capability bit is indicated to support QCL / path loss measurement for the target activated / indicated TCI state before the prediction window, or the NE configures the UE to start QCL / path loss measurement for the target activated / indicated TCI state after the prediction window.

[0150]

[0151] in, Tpred1: Beam prediction window, with The unit is denoted by , where the starting point is the time slot in which the PDSCH with MAC CE for TCI activation / indication is received. It is the time after the prediction time window used for the activated / indicated TCI or after the UE decodes the MAC CE until the first SSB transmission, where the SSB is quasi-co-located with or configured as the DL RS used for QCL indication in the TCI state. When the TCI state is unknown, it is the time from the first PL-RS transmission after the Level 1 Reference Signal Received Power (L1-RSRP) measurement, and when the TCI state is known, it is the time from the predicted time window for the activated / indicated TCI or from the time the UE decodes the MAC CE to the first PL-RS associated with the activated / indicated TCI state. It is the periodicity of the target PL-RS : Whether the target activation / indication TCI state is not in the list of active TCI states; 1: Not in the activity status list 0: In the activity status list : When the target activation / indication TCI state is unknown, is the target activation / indication TCI state not included in the list of active TCI states? When TCI state switching involves QCL-TypeD, it is 1 if the activated / indicated TCI state is used for CSI-RS based L1-RSRP, and 0 if the activated / indicated TCI state is used for SSB based L1-RSRP measurement. If the TCI state transition only involves other QCL types, then it is 1. NM: Whether the target path loss reference signal (PL-RS) is maintained; 1: The target PL-RS was not maintained. 0: Target PL-RS is maintained In some implementations, It is determined in the following ways. In some implementations, this can be based on one of the following conditions: The old or previous activated / indicated TCI state is in the list of predicted TCI states, and indicates the UE capability bit for supporting QCL / path loss measurement for the target activated / indicated TCI state before the prediction window, or the NE configures the UE to start QCL / path loss measurement for the target activated / indicated TCI state before the prediction window. The old or previous activated / indicated TCI state is not in the list of predicted TCI states, and indicates the UE capability bit for supporting QCL / path loss measurement for the target activated / indicated TCI state before the prediction window, or the NE configures the UE to start QCL / path loss measurement for the target activated / indicated TCI state before the prediction window.

[0152]

[0153] In some implementations, if the UE supports AI / ML models on the UE side for time beam prediction of DL beams and UE Rx / Tx beam pairs, then at least one of the following conditions can be applied to determine :

[0154] In some implementations, the UE can report whether it supports applying the activated / indicated TCI state without additional UE beam measurements, QCL measurements, and / or path loss measurements. Therefore, the UE may have already identified the UE beam, QCL information, and / or path loss measurements used for the activated / indicated TCI state. The UE can report this information via UE capabilities or uplink control information (UCI) or MAC CE on the PUCCH or PUSCH.

[0155] In one example, if the UE supports AI / ML models on the UE side for time beam prediction of DL beams and UE Rx / Tx beam pairs, then It can be determined as or .

[0156] Figure 10a Example 1000 of a QCL / path loss measurement for a TCI activation / indication with beam prediction prior to a beam prediction window is illustrated according to aspects of this disclosure. As shown, the UE may first communicate with a network entity based on a previously activated / indicated TCI state in time period 1010, and then in time period 1012, the UE may determine a QCL / path loss measurement for the activated / indicated TCI state in the TCI activation / indication for beam prediction. Then, in time period 1014, the UE communicates with the network entity based on the activated / indicated TCI state in the TCI activation / indication for beam prediction. During time period 1010, the UE receives a TCI activation / indication with beam prediction at time 1002. The UE sends an ACK for the TCI activation / indication with beam prediction at time 1004. Time period 1012 includes a prediction window 1006 and is separate from time period 1014, in which the UE applies the activated / indicated TCI state at time 1008.

[0157] Figure 10b Example 1030 illustrates a QCL / path loss measurement for TCI activation / indication with beam prediction after the beam prediction window, according to various aspects of this disclosure. For TCI activation / indication with beam prediction, if it is assumed that both the start point of the beam prediction window Tpred2 and the time of receiving the PDSCH with the MAC CE for TCI activation / indication in the target TCI state are transmitted in time slot n, then the UE applies the activated / indicated TCI state at time slot n+M. The network entity and the UE determine the value of M based on whether the TCI state is known or unknown. If the TCI state is known, the network entity and the UE determine the first TCI activation / indication delay based on the DL TCI state and the UL TCI state, respectively. and The action delay M of the activated / indicated TCI is determined; otherwise, the network entity and the UE determine the second TCI activation / indication delay based on the DL TCI state and the ULTCI state, respectively. and To determine the action delay M of the activated / indicated TCI.

[0158] In some implementations, It is determined in the following ways. In some implementations, this can be based on one of the following conditions: The old or previous activated / indicated TCI state is in the list of predicted TCI states, and no UE capability bit is indicated to support QCL / path loss measurement for the target activated / indicated TCI state before the prediction window, or the NE configures the UE to start QCL / path loss measurement for the target activated / indicated TCI state after the prediction window. The old or previous activated / indicated TCI state is not in the list of predicted TCI states, and no UE capability bit is indicated to support QCL / path loss measurement for the target activated / indicated TCI state before the prediction window, or the NE configures the UE to start QCL / path loss measurement for the target activated / indicated TCI state after the prediction window.

[0159] in, Tpred2: Beam prediction window, with The unit is the time slot for the ACK transmission of the PDSCH with MAC CE for TCI activation / indication. In some implementations, It is determined in the following ways. In some implementations, this can be based on one of the following conditions: The old or previous activated / indicated TCI state is in the list of predicted TCI states, and indicates the UE capability bit for supporting QCL / path loss measurement for the target activated / indicated TCI state before the prediction window, or the NE configures the UE to start QCL / path loss measurement for the target activated / indicated TCI state before the prediction window. The old or previous activated / indicated TCI state is not in the predicted TCI state list, and the UE capability bit indicating the ability to support QCL / path loss measurement for the target activated / indicated TCI state before the prediction window, or the NE configures the UE to start QCL / path loss measurement for the target activated / indicated TCI state before the prediction window.

[0160] In some implementations, if the UE supports AI / ML models on the UE side for time beam prediction of DL beams and UE Rx / Tx beam pairs, then at least one of the following conditions can be applied to determine :

[0161] In some implementations, the UE can report whether it supports applying the activated / indicated TCI state without additional UE beam measurements, QCL measurements, and / or path loss measurements. Therefore, the UE may have already identified the UE beam, QCL information, and / or path loss measurements used for the activated / indicated TCI state. The UE can report this information via UE capabilities or uplink control information (UCI) or MAC CE on the PUCCH or PUSCH.

[0162] In one example, if the UE supports AI / ML models on the UE side for time beam prediction of DL beams and UE Rx / Tx beam pairs, then It can be determined as or .

[0163] In some implementations, after the beam prediction window and before the TCI state activated / indicated by the UE application, the network entity can avoid scheduling downlink / uplink channels for the UE, such as PDCCH / PDSCH / PUSCH / PUCCH, and the UE can avoid receiving downlink channels or sending uplink channels, such as PDCCH / PDSCH / PUSCH / PUCCH.

[0164] In some other implementations, after the beam prediction window and before the TCI state activated / indicated by the UE application, the network entity and the UE can communicate based on the previously activated / indicated TCI state. In these additional implementations, the network entity can avoid scheduling the UE to receive downlink signals or transmit uplink signals based on multilayer transmission and / or modulation and coding schemes (MCS) exceeding a threshold, where the threshold can be predefined or reported by the UE capability. In one example, the network entity can schedule uplink or downlink signals in DCI format 0_0 or 1_0 respectively.

[0165] Figure 10b Example 1030 illustrates a QCL / path loss measurement for a TCI activation / indication with beam prediction after the beam prediction window. As shown, the UE can first communicate with a network entity based on the previously activated / indicated TCI state in time period 1040, and then in time period 1042, the UE can determine the QCL / path loss measurement for the activated / indicated TCI state in the TCI activation / indication for beam prediction. Then, in time period 1044, the UE communicates with the network entity based on the activated / indicated TCI state in the TCI activation / indication for beam prediction. During time period 1040, the UE receives the TCI activation / indication with beam prediction at time 1032. The UE sends an ACK for the TCI activation / indication with beam prediction at time 1034. Time period 1042 includes the prediction window 1036 and is separate from time period 1044, where the UE applies the activated / indicated TCI state at time 1038.

[0166] Figure 10c Example 1060 illustrates a QCL / path loss measurement for TCI activation / indication with beam prediction, performed three time slots after sending an ACK for TCI activation / indication signaling, according to aspects of this disclosure. For TCI activation / indication with beam prediction, the network entity can configure a beam prediction window for the activated / indicated TCI state, and the UE begins QCL / path loss measurement X time slots after receiving the TCI activation / indication signaling or Y time slots after sending an ACK for the TCI activation / indication signaling, where X and Y can be predefined or configured by the network entity or reported by the UE capability. The UE then determines the action time of the TCI activation / indication based on the action delay and the beam prediction window. The UE can communicate with the network entity before the beam prediction window or the action time of the activated / indicated TCI state, based on the previously activated / indicated TCI state.

[0167] In another example, for a TCI activation / indication with beam prediction sent in time slot n, the UE applies the activated / indicated TCI state at time slot n+P, where P=min(N,N') or P=max(N,N') and N' indicates the time from the TCI activation / indication signaling to the end of the beam prediction window.

[0168] Figure 10c An example of QCL / path loss measurement for TCI activation / indication with beam prediction is shown, three time slots after sending an ACK for TCI activation / indication signaling. As shown, the UE receives TCI activation or indication with beam prediction at time 1062. The UE sends an ACK for TCI activation / indication with beam prediction at time 1064. Subsequently, an action delay of 1070 applies the TCI activation / indication signaling. After action delay 1070, during time period 1072, the UE determines the QCL / path loss measurement for the activated / indicated TCI state in the beam-predicted TCI activation / indication. Time period 1072 includes a prediction window 1066. The UE applies the activated / indicated TCI state at time 1068, following time period 1072.

[0169] In this embodiment, the network entity can configure the UE to begin QCL / path loss measurement for the activated / indicated TCI state either after the beam prediction window, or after X time slots after receiving the TCI activation / indication signaling, or after Y time slots after sending the ACK for the TCI activation / indication signaling. The network entity can provide this configuration via RRC signaling, MAC CE, or DCI.

[0170] In some implementations, the UE can report UE capabilities indicating whether the UE supports starting QCL / path loss measurement for the activated / indicated TCI state after the beam prediction window and / or after X time slots after receiving the TCI activation / indication signaling and / or after Y time slots after sending the ACK for the TCI activation / indication signaling.

[0171] In some implementations, the network entity and the UE can determine whether the UE should begin QCL / path loss measurement for the activated / indicated TCI state after the beam prediction window, or after X time slots after receiving the TCI activation / indication signaling, or after Y time slots after sending the ACK for the TCI activation / indication signaling, based on at least one of the following factors: whether the TCI state is known or unknown, the beam prediction window length, the number of previously and newly activated TCI states, and the maximum number of supported UEs capable of activating TCI states.

[0172] In one example, if the TCI state is unknown, the UE can start QCL / path loss measurement after receiving the TCI activation / indication signaling or after sending an ACK for the TCI activation / indication signaling; otherwise, the UE can start QCL / path loss measurement after the beam prediction window.

[0173] In one example, if the beam measurement window is larger than a threshold, the UE can begin QCL / path loss measurement after receiving TCI activation / indication signaling or after sending an ACK for TCI activation / indication signaling; otherwise, the UE can begin QCL / path loss measurement after the beam prediction window. The threshold can be predefined, for example, 320 ms, or configured by a network entity or reported by the UE.

[0174] In one example, if the number of previously and newly activated TCI states is less than or equal to the maximum number of supported active TCI states supported by the UE, the UE may begin QCL / path loss measurement after receiving TCI activation / indication signaling or after sending an ACK for TCI activation / indication signaling; otherwise, the UE may begin QCL / path loss measurement after the beam prediction window.

[0175] Figure 10d Example 1080 illustrates the TCI action time of the first prediction window according to various aspects of this disclosure after the second beam prediction window. If the action time of the activated / indicated TCI state for the first beam prediction window is after the second beam prediction window, the UE may not apply the activated / indicated TCI state corresponding to the first beam prediction window, and the UE may use the previously activated / indicated TCI state to communicate with network entities. Alternatively, the UE may not apply the activated / indicated TCI state corresponding to the second beam prediction window, and the UE may continue to use the activated / indicated TCI state to communicate with network entities until a new activated / indicated TCI state is applied in the third beam prediction window or from new signaling. Alternatively, the UE may begin QCL / path loss measurement for the TCI state corresponding to the second beam prediction window after Z time slots following the action time of the TCI state corresponding to the first beam prediction window, where Z may be predefined or configured by the network entity or reported by the UE.

[0176] Figure 10dAn example is shown where the TCI action time for the first prediction window is after the second beam prediction window. As shown, an action delay of 1090 is provided for the TCI state of the first prediction window. The UE can ignore the TCI state of either the first or second prediction window, or the UE can begin QCL / path loss measurement for the TCI state of the second prediction window after time slot 153. The UE receives a TCI activation or indication with beam prediction at time 1082. The UE sends an ACK for the TCI activation / indication with beam prediction at time 1084. The UE includes the first prediction window at time 1086 (e.g., time slot 111) and the second prediction window at time 1088 (e.g., time slot 152).

[0177] In this embodiment, the network entity and the UE can determine the common target channels / RS for activated / indicated TCIs with and without beam prediction. Therefore, for a first set of channels / RSs, such as those in the first row of Table 1, the network entity and the UE can always apply the activated / indicated TCI state. For a second set of channels / RSs, such as those in the second row of Table 1, the network entity can be configured to apply the activated / indicated TCI state via RRC signaling, MAC CE, or DCI. For a third set of channels / RSs, such as those in the third row of Table 1, the network entity and the UE can determine that activated / indicated TCI states with and without beam prediction are not applied, and the network entity can configure TCI states with and without beam prediction based on separate signaling, such as RRC or MAC CE.

[0178] In this embodiment, the network entity and the UE can determine different target channels / RSs for TCI activation / indication with / without beam prediction. The network entity and the UE can determine that a first set of target channels / RSs always applies the activated / indicated TCI state with beam prediction. In one example, the first set of target channels / RSs may be the same as the channels / RSs in the first row of Table 1. The network entity can configure whether a second set of target channels / RS applies the activated / indicated TCI state with beam prediction. In one example, the second set of target channels / RSs may be the same as the channels / RSs in the second row of Table 1. For each channel / RS in the second set of target channels / RSs, the network entity can configure individually to not apply, apply one, or apply multiple activated / indicated TCI states with and without beam prediction.

[0179] In some implementations, to prevent the application of the activated / indicated TCI state for beam prediction to a channel / RS, the network entity can configure the activated / indicated TCI state with beam prediction via a separate MAC CE; in other implementations, the network entity can avoid configuring the activated / indicated TCI state with beam prediction. In one example, the network entity can send MAC CEs for multiple channels—such as the channels / RS configured to share the activated / indicated TCI state in the first and second rows of Table 1—to activate / indicate the TCI state with beam prediction, and the network entity can send another MAC CE for channels that do not share the activated / indicated TCI state to activate / indicate the TCI state with beam prediction.

[0180] Figure 11 A flowchart of a wireless communication method 1100 at the UE is shown. (Reference) Figure 1 A, Figures 3 to 5 and Figure 13 The method can be executed by UE 102, UE device 1302, etc., which may include memories 1326', 1306', 1316 and may correspond to the entire UE 102 or the entire UE device 1302, or components of UE 102 or UE device 1302 (e.g., TCI state component 140) (such as wireless baseband processor 1326 and / or application processor 1306).

[0181] like Figure 11 As shown, the UE can optionally send 1102 pairs of indications to the network entity regarding the capability of supported TCI activation or indication configuration based on beam prediction (similar to...). Figure 3 and Figure 4 Operations 302 and 402 in the code.

[0182] The UE receives a first control signaling message (1104) from a network entity, which indicates: at least one beam prediction transmission configuration indicator (TCI) state associated with a first delay and at least one non-beam prediction TCI state associated with a second delay (similar to...). Figure 3 and Figure 4 Operations 304 and 404 in the code.

[0183] The UE receives a second control signaling message 1106 from a network entity, which activates one or more TCI states among the at least one beam prediction TCI state and the at least one non-beam prediction TCI state (similar to...). Figure 3 and Figure 4 Operations 306 and 406 in the code.

[0184] The UE may optionally receive a 1110 DCI from a network entity, which indicates one or more TCI states (similar to) activated by a second control signaling. Figure 3 and Figure 4 (Operations 310 and 410 in the text). One or more TCI states indicated by the DCI in the TCI state activated by the second control signaling are referred to herein as a “TCI state set”. In some cases, the DCI may indicate a TCI state in the TCI state set. In some cases, if the MAC CE receives 1106 and activates a TCI state (or a TCI state corresponding to a TCI code point used for mTRP, such as...) Figure 2b As shown in the figure, the UE can directly apply the activated TCI state without receiving 1110 DCI.

[0185] The UE communicates with network entities at the action time associated with the first delay or the second delay based on one or more TCI states 1114 (similar to Figure 3 and Figure 4 Operations 314 and 414 in the text.

[0186] In all respects, the first control signaling indicates parameters for activating or indicating the at least one beam prediction TCI state.

[0187] In each respect, the at least one beam prediction TCI state includes a first TCI state list for TCI activation or indication with beam prediction, the first TCI state list corresponding to a first delay of the beam prediction window. The at least one non-beam prediction TCI state includes a second TCI state list for TCI activation or indication without beam prediction for the second delay.

[0188] In all respects, the at least one beam prediction TCI state is the same as the at least one non-beam prediction TCI state.

[0189] In various respects, this second control signaling includes a Media Access Control (MAC) control element (CE). In some cases, the MAC CE indicates whether each or all of one or more active TCI states are used for beam prediction, and whether one or more active TCI states corresponding to a Transmit Receive Point (TRP) are used for beam prediction. The UE can identify whether the MAC CE is used for beam prediction based on the Logical Channel Identifier (LCID) or Extended LCID of the MAC CE.

[0190] In all aspects, the UE receives from the network entity one or more activated TCI states in the MAC CE for one or more beam predictions.

[0191] In various aspects, the UE receives downlink control information (DCI), which indicates a set of TCI states in one or more TCI states activated by a second control signaling. In some cases, the DCI indicates whether the set of TCI states is used for beam prediction via at least one of the following: the location of the physical downlink control channel (PDCCH) with the DCI; or the format of the DCI.

[0192] In some cases, the UE receives multiple indicated TCI states from a network entity for one or more beam prediction windows. The UE identifies the action time for applying the TCI state set based on at least one of the following: a predefined time slot; a predefined time after the first last symbol of the PDCCH with DCI; or a time slot configured by the network entity.

[0193] In each respect, the first control signaling further indicates at least one of the following for each beam prediction TCI state: a first downlink reference signal (DL RS) associated with a quasi-co-location type D (QCL-type D) for spatial reception parameter indication; a second DL RS associated with a path loss reference signal (PL-RS); or a third DL RS associated with a QCL type A for average delay, delay spread, Doppler shift, and Doppler spread indication.

[0194] In some cases, the UE monitors the first DL RS, the second DL RS, and the third DL RS after receiving the second control signaling or after sending an acknowledgment (ACK) for the second control signaling. The UE avoids monitoring the first DL RS, the second DL RS, or the third DL RS after switching to another active TCI state.

[0195] In some cases, the UE receives at least one of the following for one or more TCI states: a first aperiodic DL RS resource set, which is associated with a first DL RS quasi-co-address (QCL) and a QCL-typeD indication; a second aperiodic DL RS resource set, which is associated with a second DL RS quasi-co-address and a PL-RS; or a third DL RS resource set, which is associated with a third DL RS quasi-co-address and a QCL-typeA indication.

[0196] In various aspects, the UE determines the first delay and the second delay based on at least one of the following: the delay from receiving the second control signaling to sending an acknowledgment (ACK) for the second control signaling; the delay for quasi-co-location (QCL) parameter tracking; the delay for UE beam tracking based on whether the associated TCI state is known or unknown; the delay for path loss measurement based on whether the UE maintains path loss operation; or the beam prediction window.

[0197] Figure 12 This is a flowchart of method 1200 for wireless communication at a network entity. Method 1200 and... Figure 11 Method 1100 is complementary. (Reference) Figure 1 , Figure 3 , Figure 4 and Figure 14 Method 1200 can be performed by one or more network entities 104, which may correspond to a base station or a unit of a base station (such as RU 106, DU 108, CU 110, RU processor 1406, DU processor 1426, CU processor 1446, etc.). One or more network entities 104 may include memories 1406' / 1426' / 1446', which may correspond to the entirety of one or more network entities 104, or components of one or more network entities 104 (such as RU processor 1406, DU processor 1426, or CU processor 1446).

[0198] like Figure 12 As shown, the network entity receives 1202 from the UE an indication of the capability to configure supported TCI activation or indication based on beam prediction (similar to...). Figure 3 and Figure 5 Operations 302 and 502 in the code.

[0199] The network entity sends a 1204 first control signaling message to the UE, which indicates: at least one beam prediction transmission configuration indicator (TCI) state associated with a first delay and at least one non-beam prediction TCI state associated with a second delay (similar to...). Figure 3 and Figure 5 Operations 304 and 504 in the code.

[0200] The network entity sends a 1206 second control signaling to the UE, which activates one or more TCI states among the at least one beam prediction TCI state and the at least one non-beam prediction TCI state (similar to...). Figure 3 and Figure 4 Operations 306 and 406 in the code.

[0201] The network entity may optionally send a 1210 DCI to the UE, which indicates one or more TCI states (similar to) activated by a second control signaling. Figure 3 and Figure 5 Operations 310 and 510 in the middle).

[0202] The network entity communicates with the network entity based on one or more TCI states at the action time associated with the first delay or the second delay 1214 (similar to Figure 3 and Figure 5 Operations 314 and 514 in the text.

[0203] In each respect, the at least one beam prediction TCI state includes a first TCI state list for TCI activation or indication with beam prediction, the first TCI state list corresponding to a first delay of the beam prediction window. The at least one non-beam prediction TCI state includes a second TCI state list for TCI activation or indication without beam prediction for the second delay. In some cases, the network entity sends to the UE at least one of the following for each beam prediction TCI state: a first downlink reference signal (DL RS) associated with or configured as the DL RS of Quasi-Co-location (QCL) type D for spatial reception parameter indication in the beam prediction TCI state; a second DL RS associated with or configured as the Path Loss Reference Signal (PL-RS) for the beam prediction TCI state; or a third DL RS associated with or configured as the DL RS of QCL type A for average delay, delay spread, Doppler shift, and Doppler spread indication in the beam prediction TCI state.

[0204] like Figure 13 The UE device 1302 described herein can perform method 1100. For example... Figure 14 One or more network entities (or BSs) 104 described herein may execute method 1200.

[0205] Figure 13Illustration 1300 illustrates an example of a hardware implementation for UE device 1302. UE device 1302 may be UE 102, a component of UE 102, or may implement UE functionality. UE device 1302 may include application processor 1306, which may have on-chip memory 1306'. In the example, application processor 1306 may be coupled to secure digital (SD) card 1308 and / or display 1310. Application processor 1306 may also be coupled to sensor module 1312, power supply 1314, additional memory module 1316, camera 1318, and / or other related components. For example, sensor module 1312 may control barometric pressure sensor / altimeter, motion sensor (such as inertial management unit (IMU)), gyroscope, accelerometer, light detection and ranging (LIDAR) device, radio-assisted detection and ranging (RADAR) device, sound navigation and ranging (SONAR) device, magnetometer, audio device, and / or other technologies for positioning.

[0206] UE device 1302 may further include a wireless baseband processor 1326, which may be referred to as a modem. The wireless baseband processor 1326 may have on-chip memory 1326'. Together with and similarly to application processor 1306, the wireless baseband processor 1326 may also be coupled to sensor module 1312, power supply 1314, additional memory module 1316, camera 1318, and / or other related components. The wireless baseband processor 1326 may additionally be coupled to one or more subscriber identity module (SIM) cards 1320 and / or one or more transceivers 1330 (e.g., wireless RF transceivers).

[0207] Within one or more transceivers 1330, the UE device 1302 may include a Bluetooth module 1332, a WLAN module 1334, an SPS module 1336 (e.g., a GNSS module), and / or a cellular module 1338. The Bluetooth module 1332, WLAN module 1334, SPS module 1336, and cellular module 1338 may each include an on-chip transceiver (TRX), or in some cases, only a transmitter (TX) or only a receiver (RX). The Bluetooth module 1332, WLAN module 1334, SPS module 1336, and cellular module 1338 may each include a dedicated antenna and / or utilize antenna 1340 to communicate with one or more other nodes. For example, UE device 1302 can communicate with another UE 102 (e.g., sidelink communication) and / or with network entity 104 (e.g., uplink / downlink communication) via transceiver 1330 and antenna 1340, wherein network entity 104 may correspond to a base station or a unit of a base station, such as RU 106, DU 108 or CU 110.

[0208] The wireless baseband processor 1326 and application processor 1306 may each include computer-readable media / memory 1326' and 1306', respectively. An additional memory module 1316 may also be considered a computer-readable media / memory. Each computer-readable media / memory 1326', 1306', and 1316 may be non-transitory. The wireless baseband processor 1326 and application processor 1306 may each be responsible for general processing, including executing software stored on the computer-readable media / memory 1326', 1306', and 1316. When executed by the wireless baseband processor 1326 / application processor 1306, this software causes the wireless baseband processor 1326 / application processor 1306 to perform the various functions described herein. The computer-readable media / memory may also be used to store data manipulated by the wireless baseband processor 1326 / application processor 1306 during software execution. The wireless baseband processor 1326 / application processor 1306 may be a component of UE 102. UE device 1302 may be a processor chip (e.g., a modem and / or an application) and includes only the wireless baseband processor 1326 and / or the application processor 1306. In other examples, UE device 1302 may be the entire UE 102 and may include additional modules for device 1302.

[0209] like Figure 1 China discusses and about Figure 3 and Figure 4 In implementation, the TSI state component 140 is configured to receive a first control signaling from a network entity, the first control signaling indicating at least one beam prediction TCI state associated with a first delay and at least one non-beam prediction TCI state associated with a second delay. The TSI state component 140 then receives a second control signaling that activates one or more of the at least one beam prediction TCI state and the at least one non-beam prediction TCI state. The UE 102 then communicates with the network entity at an action time associated with the first delay or the second delay based on the one or more TCI states.

[0210] TSI state component 140 may be located within application processor 1306 (e.g., at 140a), wireless baseband processor 1326 (e.g., at 140b), or both application processor 1306 and wireless baseband processor 1326. TSI state components 140a to 140b may be one or more hardware components specifically configured to implement the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or a combination thereof.

[0211] Figure 14This is a diagram 1400 illustrating an example of a hardware implementation for one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functionality. The one or more network entities 104 may include or correspond to at least one of RU 106, DU 108, or CU 110. CU 110 may include a CU processor 1446, which may have on-chip memory 1446'. In some aspects, CU 110 may further include an additional memory module 1456 and / or a communication interface 1448, both of which may be coupled to the CU processor 1446. CU 110 may communicate with DU 108 via a midhaul link 162 (such as an F1 interface between the communication interface 1448 of CU 110 and the communication interface 1428 of DU 108).

[0212] DU 108 may include a DU processor 1426, which may have on-chip memory 1426'. In some aspects, DU 108 may further include an additional memory module 1436 and / or a communication interface 1428, both of which may be coupled to the DU processor 1426. DU 108 may communicate with RU 106 via a frontlink 160 between DU 108's communication interface 1428 and RU 106's communication interface 1408.

[0213] RU 106 may include an RU processor 1406, which may have on-chip memory 1406'. In some aspects, RU 106 may further include an additional memory module 1416, a communication interface 1408, and one or more transceivers 1430, all of which may be coupled to the RU processor 1406. RU 106 may further include an antenna 1440, which may be coupled to one or more transceivers 1430, enabling RU 106 to communicate with UE 102 via the antenna 1440 through one or more transceivers 1430.

[0214] On-chip memories 1406', 1426', 1446' and additional memory modules 1416, 1436, 1456 can each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1406, 1426, 1446 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor 1406, 1426, 1446, the software causes the processor 1406, 1426, 1446 to perform the various functions described herein. The computer-readable medium / memory can also be used to store data manipulated by the processors 1406, 1426, 1446 during software execution. In the example, the TSI state component 150 may be located at any of one or more network entities 104, such as at CU 110; at both CU 110 and DU 108; at each of CU 110, DU 108 and RU 106; at DU 108; at both DU 108 and RU 106; or at RU 106.

[0215] TSI status component 150 can perform various operations and signaling (such as) according to the examples provided in this document. Figure 3 A, Figure 3 B and Figure 5 The TSI state components 150a to 150c may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors 1406, 1426, 1446 configured to perform the stated process / algorithm, and stored in a computer-readable medium for use by one or more processors 1406, 1426, 1446, or a combination thereof.

[0216] The specific order or hierarchy of the boxes in the processes and flowcharts disclosed herein is an illustration of the exemplary methods. Therefore, the specific order or hierarchy of the boxes in the processes and flowcharts can be rearranged. Some boxes can also be combined or deleted. Dashed lines may indicate exemplary / optional elements in the illustrations. The appended method claims present the elements of each box in the exemplary order and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0217] The detailed descriptions presented herein, in conjunction with accompanying drawings, depict various configurations, but do not imply that only these configurations are suitable for practicing the concepts described herein. These detailed descriptions include specific details used to provide a comprehensive explanation of the various concepts. However, these concepts can be practiced without using these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0218] Various aspects of wireless communication systems (such as telecommunications systems) are presented with reference to various devices and methods. These devices and methods are described in the following detailed description and are shown in the accompanying drawings by various boxes, components, circuits, processes, call flows, systems, algorithms, etc. (collectively, "elements"). These elements can be implemented using electronic hardware, computer software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design constraints imposed on the system as a whole.

[0219] An element, or any part of an element, or any combination of elements, can be implemented as a “processing system” including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system can execute software, which may be referred to as software, firmware, middleware, microcode, hardware description languages, or others. Software can be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0220] If the functionality described herein is implemented in software, then such functionality may be stored on or encoded as one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage medium. Computer-readable media include computer storage media and may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of computer-accessible instructions or data structures. The storage medium can be any available medium that is computer-accessible.

[0221] The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, form factors, sizes, and package arrangements. For example, aspects, implementations, and / or use cases can be generated via integrated chip implementations and other devices based on non-modular components, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement devices, medical devices, devices supporting artificial intelligence (AI), devices supporting machine learning (ML), etc. The scope of aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein.

[0222] Apparatus incorporating the aspects and features described herein may also include additional components and features for implementing and practicing the claimed and described aspects and features. For example, the transmission and reception of wireless signals necessarily include numerous components for analog and digital purposes, such as hardware components, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc. The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user devices, etc., in various configurations.

[0223] The description herein is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein, but should be interpreted in light of the full scope of this disclosure consistent with the language of the claims.

[0224] Unless explicitly stated otherwise, references to singular elements do not imply "one and only one," but rather "one or more." Terms such as "if," "when," and "at" do not imply an immediate temporal relationship or response. That is, phrases such as "when" do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply that an action will occur if a certain condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The terms "may," "may," and "can" as used in this disclosure generally carry certain connotations. For example, "may" refers to a permissible feature that may or may not occur, "may" refers to a feature that may occur, and "can" refers to a capability (e.g., being able to). The phrase "for example" generally carries a similar connotation to "may," and therefore, "may" is sometimes excluded from sentences that include "for example" or other similar phrases.

[0225] Unless otherwise expressly stated, the term "some" means one or more. Combinations such as "at least one of A, B, or C" or "one or more of A, B, or C" include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiple A, multiple B, and / or multiple C, or may include only A, only B, or only C. A set can be interpreted as a set of elements having a number of one or more elements.

[0226] Unless otherwise explicitly indicated, ordinal terms such as “first” and “second” do not necessarily imply order in time, sequence, numerical value, etc., but are used to distinguish different instances of the term or phrase following each ordinal term. As used in the specification and figures, reference numerals are sometimes cross-referenced between figures to indicate the same or similar features. Features that are identical in multiple figures may be labeled with the same reference numerals in multiple figures. Features that are similar but not identical in multiple figures may be labeled with reference numerals that have different leading numerals but share one or more of the same trailing numerals (e.g., 206, 306, 406, etc. may refer to similar features in the figures). Sometimes, “X” is used generally to indicate multiple variations of a feature. For example, “X06” may generally refer to all reference numbers ending in “06” (e.g., 206, 306, 406, etc.).

[0227] It should be noted that throughout this disclosure, "panel" can refer to an antenna (port) group or an antenna (port) assembly. More than one DL / UL beam may be associated with a single panel. When a transmitting node (UE or network entity) is performing a transmission via a panel, only one beam associated with that panel can be used to perform the transmission. For transmitters comprising more than one panel (e.g., two panels), it is possible that two beams, each associated with a separate panel, may be used to perform the transmission.

[0228] It should be noted that throughout this disclosure, a UE may have one or more of the following attributes or behaviors. These attributes or behaviors of the UE may also imply associated attributes or behaviors of network entities.

[0229] The UE can be configured and / or served by network entities in the serving cell.

[0230] The UE can (be configured) communicate with network entities in the serving cell.

[0231] The UE can be configured by a network entity to include one or more serving cells that may include the serving cell.

[0232] The UE can be activated or instructed by a network entity to activate one or more serving cells that may include the serving cell.

[0233] The UE can be configured and / or instructed by a network entity to use one or more BWPs. The UE can be instructed and / or configured (in the serving cell) by a network entity to use BWPs.

[0234] In some cases, the BWP can be activated as the active BWP.

[0235] In some cases, this BWP can be referred to as an active BWP.

[0236] In some cases, the BWP can be an active DL BWP.

[0237] In some cases, the BWP can be an active UL BWP.

[0238] In some cases, the BWP can be the initial BWP.

[0239] In some cases, this BWP can be the default BWP.

[0240] In some cases, the BWP can be a dormant BWP.

[0241] The UE can be in one of the following states: RRC_CONNECTED, RRC_INACTIVE, or RRC_IDLE.

[0242] It should be noted that throughout this disclosure, adjacent cells may refer to or be replaced by one or more of the following: (1) a non-serving cell, (2) a cell with a PCI different from that of the serving cell, or (3) a TRP associated with a PCI different from that of the serving cell.

[0243] It should be noted that throughout this disclosure, when a process or description relates to a serving cell, it may mean that the process or description relates to an activity (DL / UL) BWP in the serving cell.

[0244] It should be noted that throughout this disclosure, CSI reports for target cells or candidate cells may be replaced with or referred to as CSI reports for LTM.

[0245] It should be noted that throughout this disclosure, CSI reports for the serving cell may be replaced by or referred to as “CSI reports other than those for LTM” or Type 1 / 2 CSI reports.

[0246] It should be noted that throughout this disclosure, the serving cell index of the CSI report may be referred to as or represent the serving cell index on which the CSI report is sent, or the serving cell to which the CSI report is configured, or the serving cell on which the report configuration of the CSI report is configured.

[0247] It should be noted that throughout this disclosure, "panel" can refer to an antenna (port) group or an antenna (port) assembly. More than one DL / UL beam may be associated with a single panel. When a transmitting node (UE or network entity) is performing a transmission via a panel, only one beam associated with that panel can be used to perform the transmission. For transmitters comprising more than one panel (e.g., two panels), it is possible that two beams, each associated with a separate panel, may be used to perform the transmission.

[0248] It should be noted that throughout this disclosure, the TRP identifier can refer to or be referred to as a (candidate) value of the TRP identifier. The first TRP identifier can be a first candidate value or a first TRP identifier value. The second TRP identifier can be a second candidate value or a second TRP identifier value.

[0249] It should be noted that throughout this disclosure, a panel identifier may refer to or be referred to as a (candidate) value of a panel identifier. A first panel identifier may be a first candidate value or a first panel identifier value. A second panel identifier may be a second candidate value or a second panel identifier value.

[0250] It should be noted that throughout this disclosure, when a process or description relates to a serving cell, it may mean that the process or description relates to an activity (DL / UL) BWP in the serving cell.

[0251] It should be noted that throughout this disclosure, the expression "X / Y" can include the meaning of "X or Y". It should be noted that throughout this disclosure, the expression "X / Y" can include the meaning of "X and Y". It should be noted that throughout this disclosure, the expression "X / Y" can include the meaning of "X and / or Y". It should be noted that throughout this disclosure, the expression "(A) B" or "B (A)" can include the concept of "B only". It should be noted that throughout this disclosure, the expression "(A) B" or "B (A)" can include the concept of "A+B" or "B+A".

[0252] It should be noted that some or all of the embodiments described above or below may be combined or formed into new or another embodiment.

[0253] It should be noted that the foregoing or following embodiments can be used to solve at least (but not limited to) the problems or scenarios mentioned in this disclosure.

[0254] The following additional considerations may apply to the foregoing and the following discussion.

[0255] It should be noted that any two or more of the foregoing or following paragraphs, (sub)bullets, points, actions or claims described in each method / example / implementation may be logically, reasonably and appropriately combined to form a particular method.

[0256] It should be noted that any sentence, paragraph, (sub)bulb, point, action, or claim described in the foregoing or following embodiments / implementations / concepts can be implemented independently and separately to form a particular method. Dependencies such as "based on," "more specifically," and "wherein" in the embodiments / implementations / concepts mentioned in this disclosure are merely one possible embodiment and do not limit a particular method.

[0257] It should be noted that some or all of the following terms and assumptions may be used below. A BS may include a network central unit or network node in an NR for controlling one or more TRPs associated with one or more cells. Communication between the BS and the TRP is via fronthaul. The BS may be referred to as a Central Unit (CU), eNB, gNB, or NodeB. A TRP may include: a transmit and receive point that provides network coverage and communicates directly with the UE. A TRP may be referred to as a Distributed Unit (DU) or network node. A cell may include one or more associated TRPs; for example, the coverage of a cell consists of the coverage of all associated TRPs. A cell is controlled by a BS or network entity. A cell may be referred to as a TRP group (TRPG). A serving beam may include a beam generated by a network node (e.g., a TRP) and configured to communicate with the UE (e.g., for transmission and / or reception). A candidate beam for the UE is a candidate for the serving beam. The serving beam may or may not be a candidate beam.

[0258] The user device in which the technologies of this disclosure are implemented (e.g., UE 102) can be any suitable device capable of wireless communication, such as a smartphone, tablet computer, laptop computer, mobile game console, point-of-sale (POS) terminal, health monitoring device, drone, camera, media streaming dongle or other personal media device, wearable device such as a smartwatch, wireless hotspot, femtocell, or broadband router. Furthermore, in some cases, the user device can be embedded in an electronic system (such as the main unit of a vehicle or an advanced driver assistance system (ADAS)). Even further, the user device can operate as an Internet of Things (IoT) device or a mobile Internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, computer-readable storage, a user interface, one or more network interfaces, one or more sensors, etc.

[0259] Some embodiments described in this disclosure include logic or multiple components or modules. A module can be a software module (e.g., code stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit capable of performing certain operations and can be configured or arranged in a certain way. A hardware module may include a dedicated circuit system or logic that is permanently configured (e.g., as a dedicated processor, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also include programmable logic or a circuit system (e.g., included within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in a dedicated and permanently configured circuit system or in a temporarily configured circuit system (e.g., configured by software) may be driven by cost and time considerations.

[0260] When implemented in software, these technologies can be provided as part of an operating system, a library used by multiple applications, or a specific software application. The software can be executed by one or more general-purpose processors or one or more dedicated processors.

[0261] Structural and functional equivalents of elements of all aspects described throughout this disclosure, known or subsequently learned by those skilled in the art, are expressly incorporated herein by reference and are covered by the claims. The terms “module,” “mechanism,” “element,” “device,” etc., may not be substitutes for the term “component.” Therefore, no claim element may be construed as means plus function unless explicitly stated using the phrase “component for…”. As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, unless expressly stated otherwise, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) may be construed as “at least based on A”.

[0262] Example

[0263] Example 1 is a device comprising: a processor configured to enable a user equipment (UE): Receive Radio Resource Control (RRC) signaling configured with at least one of the following: A first TCI state list for activation or indication of a Transmission Configuration Indicator (TCI) without beam prediction, the first TCI state list corresponding to a first action delay; A second TCI state list for TCI activation or indication with beam prediction, the second TCI state list corresponding to a second action delay of the beam prediction window; or Implement parameters for TCI activation or indication with beam prediction; Receive a physical downlink shared channel (PDSCH) with a media access control (MAC) control element (CE), which activates at least one TCI state from a TCI state list in a configured TCI state list; Based on the activated TCI state, communication is made with the base station at the action time corresponding to the first action delay or the second action delay corresponding to the activated TCI state.

[0264] Example 2 is the device according to Example 1, wherein the UE transmits UE capabilities indicating at least one of the following: Does the UE support beam prediction-based TCI activation or indication? The maximum number of configured TCI states used for beam prediction; The maximum number of activated TCI states used for beam prediction within a beam prediction window. The maximum number of activated TCI states across the beam prediction window; The maximum number of beam prediction windows.

[0265] Example 3 is a device according to Example 1, wherein the UE receives the configuration of the same TCI states in the first TCI state list and the second TCI state list.

[0266] Example 4 is a device according to Example 1, wherein the UE receives the configuration of different TCI states in the first TCI state list and the second TCI state list.

[0267] Example 5 is a device according to Examples 1 to 4, wherein the UE receives the MAC CE, which indicates whether all active TCI states in the MAC CE are used for beam prediction.

[0268] Example 6 is a device according to Examples 1 to 4, wherein the UE receives the MAC CE, which indicates whether all active TCI states corresponding to the Transmit Receive Point (TRP) in the MAC CE are used for beam prediction.

[0269] Example 7 is a device according to Examples 1 to 4, wherein the UE receives the MAC CE, the MAC CE indicating whether each of the activated TCI states in the MAC CE is used for beam prediction.

[0270] Example 8 is a device according to Examples 1 through 4, wherein the UE determines whether the MAC CE is used for beam prediction based on the Logical Channel Identifier (LCID) or Extended LCID used for MAC CE.

[0271] Example 9 is a device according to Examples 5 through 8, wherein the UE receives an activated TCI state for a beam prediction window in a MAC CE.

[0272] Example 10 is a device according to Examples 5 through 8, wherein the UE receives the activated TCI state for multiple beam prediction windows in the MAC CE.

[0273] Example 11 is a device according to Examples 1 through 10, wherein the UE receives downlink control information (DCI) indicating at least one of the activated TCI states.

[0274] Example 12 is a device according to Example 11, wherein the UE receives from the DCI an indication of whether the indicated TCI state is used for beam prediction.

[0275] Example 13 is the device according to Example 11, wherein the UE determines whether the TCI state indicated in the DCI is used for beam prediction based on the location of the physical downlink control channel (PDCCH) with the DCI.

[0276] Example 14 is a device according to Example 11, wherein the UE determines whether the TCI state indicated in the DCI is used for beam prediction based on the DCI format.

[0277] Example 15 is a device according to Examples 11 through 14, wherein the UE receives an indicated TCI state for a beam prediction window.

[0278] Example 16 is a device according to Examples 11 to 14, wherein the UE receives an indicated TCI state for multiple beam prediction windows.

[0279] Example 17 is a device according to Example 11, wherein the UE determines at one of the following times that the DCI indicates the TCI state from the activated TCI state: The first time slot used for applying the indicated TCI state; The first or last symbol of the PDCCH containing the DCI; or Time slots configured by network entities.

[0280] Example 18 is a device according to Example 1, wherein the UE receives at least one of the following configurations for each TCI state used for beam prediction: A first downlink reference signal (DL RS), which is associated with or configured as the DL RS of Quasi-co-location (QCL) type D for spatial reception parameter indication in the TCI state; A second downlink reference signal (DL RS), which is associated with or configured as the path loss reference signal (PL-RS) for the TCI state; A third downlink reference signal (DL RS) is associated with or configured as the DL RS of quasi-co-location (QCL) type A in the TCI state for average delay, delay spread, Doppler shift and Doppler spread indication.

[0281] Example 19 is a device according to Example 18, wherein the first DL RS, the second DL RS and / or the third DL RS are periodic DL RS.

[0282] Example 20 is the device according to Example 18, wherein the first DL RS, the second DL RS and / or the third DL RS are semi-persistent DL RS.

[0283] Example 21 is a device according to Example 20, wherein the UE determines to activate the first DL RS, the second DL RS, and / or the third DL RS after receiving the TCI activation signaling or after sending the ACK for the TCI activation signaling.

[0284] Example 22 is a device according to Example 20, wherein the UE determines to deactivate the first DL RS, the second DL RS, and / or the third DL RS after switching to another activated TCI state.

[0285] Example 23 is a device according to Example 18, wherein the UE receives at least one of the following configurations for the TCI state.

[0286] A first aperiodic DL RS resource set, which is co-located with the DL RS quasi-co-addressable for QCL-typeD indication in the TCI state; A second aperiodic DL RS resource set, which is quasi-co-located with the DL RS quasi-co-addressable PL-RS configured for the TCI state; The third DL RS resource set is co-located with the DL RS quasi-co-addressable in the TCI state for QCL-typeA indication.

[0287] Example 24 is a device according to Example 1, wherein the UE determines the first action delay and the second action delay based on at least one of the following factors: The first delay from receiving the TCI activation signal to sending an acknowledgment (ACK) for the TCI activation signaling; A second delay is used for tracking quasi-co-located (QCL) parameters; The third delay used for UE beam tracking; A fourth delay used for path loss measurement; or Beam prediction window.

[0288] Example 25 is a device according to Example 24, wherein the UE determines the third delay based on whether the TCI state is known or unknown.

[0289] Example 26 is the device according to Example 24, wherein the UE determines the fourth delay based on whether the UE maintains path loss.

[0290] Example 27 is a device according to Example 1, wherein the UE receives a configuration of a second target applicable channel and RS set for an activated or indicated TCI state with and without beam prediction.

[0291] Example 28 is a device according to Example 27, wherein the UE applies activated or indicated TCI states with and without beam prediction to a first target applicable channel and RS set and a configured second target applicable channel and RS set.

[0292] Example 29 is a device according to Example 28, wherein the first target applicable channel and RS set are predefined.

[0293] Example 30 is a device comprising: a processor configured to enable a base station (BS): Send Radio Resource Control (RRC) signaling configuring at least one of the following: A first TCI state list for activation or indication of a Transmission Configuration Indicator (TCI) without beam prediction, the first TCI state list corresponding to a first action delay; A second TCI state list for TCI activation or indication with beam prediction, the second TCI state list corresponding to a second action delay of the beam prediction window; or Implement parameters for TCI activation or indication with beam prediction; Transmit a Physical Downlink Shared Channel (PDSCH) with a Media Access Control (MAC) Control Element (CE), which activates at least one TCI state from a configured TCI state list. Based on the activated TCI state, communication is conducted with the user equipment (UE) at the action time corresponding to the first action delay or the second action delay corresponding to the activated TCI state.

[0294] Example 31 is a device according to Example 30, wherein the BS receives UE capabilities indicating at least one of the following: Does the UE support beam prediction-based TCI activation or indication? The maximum number of configured TCI states used for beam prediction; The maximum number of activated TCI states used for beam prediction within a beam prediction window. The maximum number of activated TCI states across the beam prediction window; The maximum number of beam prediction windows.

[0295] Example 32 is a device according to Example 30, wherein the BS sends the configuration of the same TCI status in the first TCI status list and the second TCI status list.

[0296] Example 33 is a device according to Example 30, wherein the BS sends the configuration of different TCI states in the first TCI state list and the second TCI state list.

[0297] Example 34 is a device according to Examples 30 to 33, wherein the BS sends the MAC CE, which indicates whether all activated TCI states in the MAC CE are used for beam prediction.

[0298] Example 35 is a device according to Examples 30 to 33, wherein the BS transmits the MAC CE, which indicates whether all active TCI states corresponding to the transmit-receive point (TRP) in the MAC CE are used for beam prediction.

[0299] Example 36 is a device according to Examples 30 to 33, wherein the BS sends the MAC CE, the MAC CE indicating whether each of the activated TCI states in the MAC CE is used for beam prediction.

[0300] Example 37 is a device according to Examples 30 to 33, wherein the BS configures whether the MAC CE is used for beam prediction based on the Logical Channel Identifier (LCID) used for the MAC CE.

[0301] Example 38 is a device according to Examples 34 through 37, wherein the BS is configured in the MAC CE for an activated TCI state for a beam prediction window.

[0302] Example 39 is a device according to Examples 34 through 37, wherein the BS is configured in the MAC CE for the activated TCI states of multiple beam prediction windows.

[0303] Example 40 is a device according to Examples 30 to 39, wherein the BS sends downlink control information (DCI) indicating at least one of the activated TCI states.

[0304] Example 41 is the device according to Example 40, wherein the BS sends an indication from the DCI indicating whether the indicated TCI state is used for beam prediction.

[0305] Example 42 is the device according to Example 40, wherein the BS configures whether the TCI state indicated in the DCI is used for beam prediction based on the location of the physical downlink control channel (PDCCH) with the DCI.

[0306] Example 43 is a device according to Example 40, wherein the BS configures whether the TCI state indicated in the DCI is used for beam prediction based on the DCI format.

[0307] Example 44 is a device according to Examples 40 through 43, wherein the BS transmits an indicated TCI state for a beam prediction window.

[0308] Example 45 is a device according to Examples 40 to 43, wherein the BS transmits indicated TCI states for multiple beam prediction windows.

[0309] Example 46 is a device according to Example 40, wherein the BS determines at one of the following times that the DCI indicates the TCI state from the activated TCI state: The first time slot used for applying the indicated TCI state; The first or last symbol of the PDCCH containing the DCI; or Time slots configured by network entities.

[0310] Example 47 is the device according to Example 30, wherein the BS transmits at least one of the following configurations for each TCI state used for beam prediction: A first downlink reference signal (DL RS), which is associated with or configured as the DL RS of Quasi-co-location (QCL) type D for spatial reception parameter indication in the TCI state; A second downlink reference signal (DL RS), which is associated with or configured as the path loss reference signal (PL-RS) for the TCI state; A third downlink reference signal (DL RS) is associated with or configured as the DL RS of quasi-co-location (QCL) type A in the TCI state for average delay, delay spread, Doppler shift and Doppler spread indication.

[0311] Example 48 is the device according to Example 47, wherein the first DL RS, the second DL RS and / or the third DL RS are periodic DL RS.

[0312] Example 49 is the device according to Example 47, wherein the first DL RS, the second DL RS and / or the third DL RS are semi-persistent DL RS.

[0313] Example 50 is the device according to Example 49, wherein the BS determines to activate the first DL RS, the second DL RS, and / or the third DL RS after receiving the TCI activation signaling or after sending the ACK for the TCI activation signaling.

[0314] Example 51 is a device according to Example 49, wherein the BS determines to deactivate the first DL RS, the second DL RS, and / or the third DL RS after switching to another activated TCI state.

[0315] Example 52 is the device according to Example 47, wherein the BS sends at least one of the following configurations for the TCI state.

[0316] A first aperiodic DL RS resource set, which is co-located with the DL RS quasi-co-addressable for QCL-typeD indication in the TCI state; A second aperiodic DL RS resource set, which is quasi-co-located with the DL RS quasi-co-addressable PL-RS configured for the TCI state; The third DL RS resource set is co-located with the DL RS quasi-co-addressable in the TCI state for QCL-typeA indication.

[0317] Example 53 is the device according to Example 30, wherein the BS determines the first action delay and the second action delay based on at least one of the following factors: The first delay from receiving the TCI activation signal to sending an acknowledgment (ACK) for the TCI activation signaling; A second delay is used for tracking quasi-co-located (QCL) parameters; The third delay used for UE beam tracking; The fourth delay used for path loss measurement; Beam prediction window.

[0318] Example 54 is the device according to Example 53, wherein the BS determines the third delay based on whether the TCI state is known or unknown.

[0319] Example 55 is the device according to Example 53, wherein the BS determines the fourth delay based on whether the UE maintains path loss.

[0320] Example 56 is the device according to Example 30, wherein the BS transmits a configuration of a second target applicable channel and RS set for activated or indicated TCI states with and without beam prediction.

[0321] Example 57 is the device according to Example 56, wherein the BS applies activated or indicated TCI states with and without beam prediction to a first target applicable channel and RS set and a configured second target applicable channel and RS set.

[0322] Example 58 is a device according to Example 57, wherein the first target applicable channel and RS set are predefined.

Claims

1. A method for wireless communication by a user equipment (UE), the method comprising: Receive (304) a first control signaling from the network entity, the first control signaling indicating: At least one beam prediction transmission configuration indicator (TCI) state associated with the first delay, and At least one non-beam predicted TCI state associated with the second delay; Receive (306) a second control signaling, the second control signaling activating one or more of the at least one beam prediction TCI state and the at least one non-beam prediction TCI state; and Based on the one or more TCI states, communicate with the network entity at the action time associated with the first delay or the second delay (314).

2. The method of claim 1, wherein the first control signaling indicates parameters for activating or indicating the at least one beam prediction TCI state.

3. The method of claim 1 or 2, wherein the at least one beam prediction TCI state includes a first TCI state list for TCI activation or indication with beam prediction, the first TCI state list corresponding to the first delay of the beam prediction window; and wherein the at least one non-beam prediction TCI state includes a second TCI state list for TCI activation or indication without beam prediction for the second delay.

4. The method of any one of claims 1 to 3, wherein the at least one beam prediction TCI state is the same as the at least one non-beam prediction TCI state.

5. The method of any one of claims 1 to 4, wherein the second control signaling includes a Media Access Control (MAC) control element (CE).

6. The method of claim 5, wherein the MAC CE indicates: Whether each or all of the one or more activated TCI states are used for beam prediction, and Whether the one or more activated TCI states corresponding to the transmit / receive point (TRP) are used for beam prediction.

7. The method of claim 5, further comprising: Whether the MAC CE is used for beam prediction is identified based on the logical channel identifier (LCID) or extended LCID of the MAC CE.

8. The method of any one of claims 1 to 7, further comprising: Receive (310) downlink control information (DCI), the DCI indicating one or more TCI states activated by the second control signaling – referred to as the "TCI state set".

9. The method of claim 8, wherein the DCI indicates whether the TCI state set is used for beam prediction via at least one of the following: Location of the Physical Downlink Control Channel (PDCCH) with the DCI; or The format of the DCI.

10. The method of any one of claims 8 to 9, further comprising identifying the action time for applying the TCI state set based on at least one of the following: Predefined time slots; The predefined time following the first last symbol of the PDCCH with the DCI; or The time slot configured by the network entity.

11. The method of any one of claims 1 to 10, wherein the first control signaling further indicates at least one of the following for each beam prediction TCI state: A first downlink reference signal DL RS, the first DL RS being associated with a quasi-co-location type D QCL-typeD for spatial reception parameter indication; A second DL RS, which is associated with the path loss reference signal PL-RS; or The third DL RS is associated with QCL type A for average delay, delay spread, Doppler frequency shift, and Doppler spread indication.

12. The method of claim 11, further comprising: After receiving the second control signaling or after sending an ACK acknowledgment for the second control signaling, monitor the first DL RS, the second DL RS, and the third DL RS; and Avoid monitoring the first DL RS, the second DL RS, or the third DL RS after switching to another activated TCI state.

13. The method of claim 12, further comprising receiving at least one of the following for the one or more TCI states: A first aperiodic DL RS resource set, the first aperiodic DL RS resource set being associated with the first DL RS quasi-co-address QCL and the QCL-typeD indication; A second aperiodic DL RS resource set, the second aperiodic DL RS resource set being quasi-co-located with the second DL RS associated with the PL-RS; or The third DL RS resource set, the third DL RS resource set being associated with the third DL RS quasi-co-addressing associated with the QCL-typeA indication.

14. The method of any one of claims 2 to 13, further comprising determining the first delay and the second delay based on at least one of the following: The delay from receiving the second control signaling to sending the acknowledgment (ACK) for the second control signaling; Delay used for quasi-co-located QCL parameter tracking; Delay for UE beam tracking based on whether the associated TCI state is known or unknown; Based on whether the UE maintains the delay for path loss measurement during path loss operation; or The beam prediction window.

15. The method of any one of claims 1 to 14, further comprising: Send (302) to the network entity an indication of the capability to enable or indicate the configuration of supported TCI based on beam prediction.

16. A method for wireless communication by a network entity, the method comprising: Send (304) first control signaling to the user equipment (UE), the first control signaling indicating: At least one beam prediction transmission configuration indicator (TCI) state associated with the first delay, and At least one non-beam predicted TCI state associated with the second delay; Send (306) a second control signaling, the second control signaling activating one or more TCI states among the at least one beam prediction TCI state and the at least one non-beam prediction TCI state; and Based on the one or more TCI states, communicate with the UE at the action time associated with the first delay or the second delay (314).

17. The method of claim 1, wherein the at least one beam prediction TCI state includes a first TCI state list for TCI activation or indication with beam prediction, the first TCI state list corresponding to a first delay of the beam prediction window; and wherein the at least one non-beam prediction TCI state includes a second TCI state list for TCI activation or indication without beam prediction for the second delay.

18. The method of claim 16 or 17, further comprising, for each beam predicting TCI state, sending to the UE at least one of the following: A first downlink reference signal DL RS, which is associated with or configured as the DL RS of quasi-co-located QCL type D for spatial reception parameter indication in the beam prediction TCI state. A second DL RS, which is associated with or configured as the path loss reference signal PL-RS used for the beam prediction TCI state; or The third DL RS is associated with or configured as the DL RS of QCL type A in the beam prediction TCI state for average delay, delay spread, Doppler shift and Doppler spread indication.

19. An apparatus comprising: One or more radio frequency (RF) modems; Processor, the processor being coupled to the one or more RF modems; as well as At least one memory storing executable instructions for manipulating at least one of the processor or the one or more RF modems to perform the method as claimed in any one of claims 1 to 18.

Images