Indication of predicted transmission configuration indicator status

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive a first control signal indicating a first transmit configuration indicator (TCI) state for a first time domain window and a second TCI state for a second time domain window after the first time domain window, the second TCI state including a predicted TCI state. The UE may receive a second control signal that triggers activation of the first TCI state for communication during the first time domain window based at least in part on the first control signal. The UE may switch to a second TCI state for communication during a second time domain window according to a second control signal based at least in part on the first control signal and expiration of the first time domain window.

Description

Technical Field

[0001] The following content relates to wireless communication, including indications of the state of the predicted transmission configuration indicator. Background Technology

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

[0003] The described aspects of the technology relate to improved methods, systems, devices, and apparatuses supporting indications of predicted Transmission Configuration Indicator (TCI) states. For example, the described technology provides a network entity that can send a first control signal (e.g., a Media Access Control-Control Element (MAC-CE) TCI activation signal) to a User Equipment (UE) indicating or otherwise identifying multiple TCI states to be used for communication with the UE. The multiple TCI states may include at least the first TCI state to be used for communication with the UE, wherein the first TCI state is associated with a corresponding first time-domain window during which the UE will use or otherwise apply the first TCI state. The multiple TCI states may also include one or more additional TCI states (e.g., second TCI states), each of which is a predicted TCI state for a corresponding second time-domain window. The network entity can send a second control signal (e.g., a Downlink Control Information (DCI) TCI switching signal) to the UE, triggering activation of the first TCI state. The UE may use or otherwise apply a first TCI state during a first time-domain window, and when the first time-domain window expires, switch to a second TCI state (e.g., a predicted TCI state) during a second time-domain window for communication. The UE may continue to switch to an additional predicted TCI state during the corresponding time-domain window.

[0004] A method for wireless communication at a UE is described. The method may include: receiving a first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state; receiving a second control signal triggering activation of the first TCI state for communication during the first time-domain window based on the first control signal; and switching to the second TCI state for communication during the second time-domain window based on the first control signal and the expiration of the first time-domain window, according to the second control signal.

[0005] An apparatus for wireless communication at a UE is described. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. These instructions may be executed by the processor to cause the apparatus to: receive a first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state; receive a second control signal triggering activation of the first TCI state for communication during the first time-domain window based on the first control signal; and switch to the second TCI state for communication during the second time-domain window based on the second control signal and the expiration of the first time-domain window.

[0006] Another apparatus for wireless communication at a UE is described. The apparatus may include: components for receiving a first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state; components for receiving a second control signal triggering activation of the first TCI state for communication during the first time-domain window based on the first control signal; and components for switching to the second TCI state for communication during the second time-domain window based on the first control signal and the expiration of the first time-domain window, according to the second control signal.

[0007] A non-transitory computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by a processor to: receive a first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state; receive a second control signal triggering activation of the first TCI state for communication during the first time-domain window based on the first control signal; and switch to the second TCI state for communication during the second time-domain window based on the second control signal and the expiration of the first time-domain window.

[0008] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the first control signal may include operations, features, components, or instructions for receiving an indication of a time offset between a first end time of the first time-domain window and a second end time of the second time-domain window, wherein the expiration of the first time-domain window may be based on the time offset.

[0009] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the first control signal may include operations, features, components, or instructions for receiving a radio resource control (RRC) signal that semi-statically defines the time offset between the first time-domain window and the second time-domain window.

[0010] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the first control signal may include operations, features, components, or instructions for receiving a DCI that dynamically defines the time offset between the first time-domain window and the second time-domain window.

[0011] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the first control signal may include operations, features, components, or instructions for receiving an indication of a set of a plurality of second time-domain windows, wherein the second time-domain window is one of a set of second time-domain windows, wherein each time-domain window in the set of a plurality of second time-domain windows is associated with a corresponding predicted TCI state, and wherein the last time-domain window in the set of a plurality of second time-domain windows may be associated with an undefined end point.

[0012] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the duration of the second time-domain window may be based on the duration of the first time-domain window according to a defined ratio.

[0013] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the first time-domain window and the second time-domain window are equal in duration.

[0014] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the first time-domain window and the second time-domain window are not equal in duration.

[0015] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving one or more TCI status code points via the first control signal, each TCI status code point identifying a predicted set of TCI states during a corresponding second time-domain window set, the predicted set of TCI states being based on the second TCI state; and receiving TCI status code points from the one or more TCI status code points via the second control signal, wherein switching to the second TCI state may be based on receiving the TCI status code points.

[0016] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of the number of predicted TCI states for each of the one or more TCI status code points via the first control signal.

[0017] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, each of the one or more TCI status code points includes a common number of predicted TCI states.

[0018] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, via the second control signal, an indication of the duration of a time-domain window for each predicted TCI state in the set of predicted TCI states for each of the one or more TCI status code points, wherein the second time-domain window may be based on the duration.

[0019] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the second time-domain window includes the equal duration.

[0020] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving the first control signal via a group common MAC-CE, wherein the UE belongs to a UE group associated with the group common MAC-CE.

[0021] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving the second control signal via a group common DCI, wherein the UE belongs to a UE group associated with the group common DCI.

[0022] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the first control signal indicates that the UE belongs to the UE group.

[0023] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving the second control signal via a UE-specific DCI.

[0024] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a third control signal prior to the second time-domain window, the third control signal triggering the activation of an updated TCI state during the second time-domain window; and, based on the third control signal, overwriting a switch to the second TCI state during the second time-domain window and switching to the updated TCI state.

[0025] A method for wireless communication at a network entity is described. The method may include: sending a first control signal to a UE, the first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state; sending a second control signal to the UE, the second control signal triggering activation of the first TCI state for communication during the first time-domain window based on the first control signal; and communicating with the UE during the second time-domain window using the second TCI state according to the second control signal based on the first control signal and the expiration of the first time-domain window.

[0026] An apparatus for wireless communication at a network entity is described. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. These instructions may be executed by the processor to cause the apparatus to: send a first control signal to a UE, the first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state; send a second control signal to the UE, the second control signal triggering activation of the first TCI state for communication during the first time-domain window based on the first control signal; and communicate with the UE during the second time-domain window using the second TCI state according to the second control signal based on the first control signal and the expiration of the first time-domain window.

[0027] Another apparatus for wireless communication at a network entity is described. The apparatus may include: components for transmitting a first control signal to a UE, the first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state; components for transmitting a second control signal to the UE, the second control signal triggering the activation of the first TCI state for communication during the first time-domain window based on the first control signal; and components for communicating with the UE during the second time-domain window using the second TCI state according to the second control signal based on the first control signal and the expiration of the first time-domain window.

[0028] A non-transitory computer-readable medium is described, storing code for wireless communication at a network entity. The code may include instructions executable by a processor to: send a first control signal to a UE indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state; send a second control signal to the UE triggering activation of the first TCI state for communication during the first time-domain window based on the first control signal; and communicate with the UE using the second TCI state during the second time-domain window based on the first control signal and the expiration of the first time-domain window, according to the second control signal.

[0029] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, sending the first control signal may include operations, features, components, or instructions for sending an indication of a time offset between a first end time of the first time domain window and a second end time of the second time domain window, wherein the expiration of the first time domain window may be based on the time offset.

[0030] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, sending the first control signal may include operations, features, components, or instructions for sending an RRC signal that semi-statically defines the time offset between the first time-domain window and the second time-domain window.

[0031] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, sending the first control signal may include operations, features, components, or instructions for sending a DCI that dynamically defines the time offset between the first time-domain window and the second time-domain window.

[0032] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, sending the first control signal may include operations, features, components, or instructions for sending an instruction to a set of a plurality of second time-domain windows, wherein the second time-domain window is one of a set of a plurality of second time-domain windows, wherein each time-domain window in the set of a plurality of second time-domain windows is associated with a corresponding predicted TCI state, and wherein the last time-domain window in the set of a plurality of second time-domain windows may be associated with an undefined end point.

[0033] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the duration of the second time-domain window may be based on the duration of the first time-domain window according to a defined ratio.

[0034] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the first time-domain window and the second time-domain window are equal in duration.

[0035] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the first time-domain window and the second time-domain window are not equal in duration.

[0036] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: transmitting one or more TCI status code points via the first control signal, each TCI status code point identifying a predicted set of TCI states during a corresponding second time-domain window set, the predicted set of TCI states being based on the second TCI state; and transmitting TCI status code points from the one or more TCI status code points via the second control signal, wherein communication with the UE using the second TCI state may be based on transmitting the TCI status code points.

[0037] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication of the number of predicted TCI states for each of the one or more TCI status code points via the first control signal.

[0038] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, each of the one or more TCI status code points includes a common number of predicted TCI states.

[0039] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication of the duration of a time-domain window for each predicted TCI state in the set of predicted TCI states via the second control signal for each of the one or more TCI status code points, wherein the second time-domain window may be based on the duration.

[0040] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the second time-domain window includes the equal duration.

[0041] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting the first control signal via a group common MAC-CE, wherein the UE belongs to a UE group associated with the group common MAC-CE.

[0042] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting the second control signal via a group common DCI, wherein the UE belongs to a UE group associated with the group common DCI.

[0043] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the first control signal indicates that the UE belongs to the UE group.

[0044] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting the second control signal via a UE-specific DCI.

[0045] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: sending a third control signal prior to the second time-domain window, the third control signal triggering the activation of an updated TCI state during the second time-domain window; and, based on the third control signal, overwriting a switch to the second TCI state during the second time-domain window and switching to the updated TCI state. Attached Figure Description

[0046] Figure 1 An example of a wireless communication system is shown that supports one or more aspects of this disclosure in providing an indication of the state of a predictive transmission configuration indicator.

[0047] Figure 2 An example of a wireless communication system is shown that supports one or more aspects of this disclosure in providing an indication of the state of a predictive transmission configuration indicator.

[0048] Figure 3 An example of a TCI scheme for predicting the state of a transmission configuration indicator is shown, in support of one or more aspects of this disclosure.

[0049] Figure 4A and Figure 4B An example of a TCI scheme for predicting the state of a transmission configuration indicator is shown, in support of one or more aspects of this disclosure.

[0050] Figure 5A and Figure 5B An example of a TCI scheme for predicting the state of a transmission configuration indicator is shown, in support of one or more aspects of this disclosure.

[0051] Figure 6 An example of a TCI scheme for predicting the state of a transmission configuration indicator is shown, in support of one or more aspects of this disclosure.

[0052] Figure 7 An example of a TCI scheme for predicting the state of a transmission configuration indicator is shown, in support of one or more aspects of this disclosure.

[0053] Figure 8 and Figure 9 A block diagram of an apparatus for predicting the state of a configuration indicator to be sent, in accordance with one or more aspects of this disclosure, is shown.

[0054] Figure 10A block diagram of a communication manager that provides an indication of the state of a predictive transmission configuration indicator in support of one or more aspects of this disclosure is shown.

[0055] Figure 11 A diagram of a system including a device that supports indication of the state of a predictive transmission configuration indicator, according to one or more aspects of this disclosure, is shown.

[0056] Figure 12 and Figure 13 A block diagram of an apparatus for predicting the state of a configuration indicator to be sent, in accordance with one or more aspects of this disclosure, is shown.

[0057] Figure 14 A block diagram of a communication manager that provides an indication of the state of a predictive transmission configuration indicator in support of one or more aspects of this disclosure is shown.

[0058] Figure 15 A diagram of a system including a device that supports indication of the state of a predictive transmission configuration indicator, according to one or more aspects of this disclosure, is shown.

[0059] Figures 16 to 20 A flowchart illustrating a method for predicting the state of a transmission configuration indicator in support of one or more aspects of this disclosure is shown. Detailed Implementation

[0060] Wireless networks can use control signaling to configure various parameters of user equipment (UE). For example, a network entity can send control signaling that identifies configuration parameters to be used for communication with the UE (e.g., uplink and downlink communication). The UE and the network entity perform communication based on the control signaling. This can include configuring each UE using separate control signaling, which includes both initial configuration and configuration updates as needed. This resource-intensive control signaling approach consumes significant airspace resources and processing power and power consumption at the UE.

[0061] Therefore, aspects of the described technology relate to improved methods, systems, devices, and apparatuses supporting indications of predicted Transmission Configuration Indicator (TCI) states. For example, the described technology provides a network entity that can send a first control signal (e.g., a Media Access Control-Control Element (MAC-CE) TCI activation signal) to a UE, the first control signal indicating or otherwise identifying multiple TCI states to be used for communication with the UE. The multiple TCI states may include at least the first TCI state to be used for communication with the UE, wherein the first TCI state is associated with a corresponding first time-domain window during which the UE will use or otherwise apply the first TCI state. The multiple TCI states may also include one or more additional TCI states (e.g., second TCI states), each of which is a predicted TCI state for a corresponding second time-domain window. The network entity can send a second control signal (e.g., a Downlink Control Information (DCI) TCI switching signal) to the UE, the second control signal triggering activation of the first TCI state. The UE may use or otherwise apply a first TCI state during a first time-domain window, and when the first time-domain window expires, switch to a second TCI state (e.g., a predicted TCI state) during a second time-domain window for communication. The UE may continue to switch to an additional predicted TCI state during the corresponding time-domain window.

[0062] The various aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to indications of the state of a predictive transmission configuration indicator.

[0063] Figure 1 An example of a wireless communication system 100 is shown that supports an indication of the state of a predicted transmission configuration indicator according to one or more aspects of this disclosure. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0064] Network entity 105 may be distributed across a geographical area to form wireless communication system 100 and may include devices in different forms or with different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, among other names. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0065] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0066] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Alternatively, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0067] In some examples, network entity 105 may communicate with core network 130 or with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entity 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entity 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0068] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home eNodeB, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, self-contained) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0069] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105 (such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0070] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, protocol stack functional splitting can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165s via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170s via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 that communicate via these communication links.

[0071] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0072] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be part of a backhaul link) and may communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0073] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay for UE transmissions via one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB node 104 to send signaling notifications to child IAB node 104 or UE 115.

[0074] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, the IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. The IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data may be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication with IAB node 104 can be scheduled by DU 165 of the IAB donor, and communication with IAB node 104 can be scheduled by DU 165 of IAB node 104.

[0075] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support indication of the state of a predicted transmission configuration indicator as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) can additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

[0077] The UE 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0078] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources that define the physical layer structure used to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0079] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be made by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0080] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0081] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0082] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high-order modulation scheme can correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources can increase the data rate or data integrity used for communication with UE 115.

[0083] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0084] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which This can represent the supported subcarrier spacing, while The supported Discrete Fourier Transform (DFT) size can be represented. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0085] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

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

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

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

[0089] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

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

[0091] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0092] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

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

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

[0095] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0096] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by network entity 105. In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

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

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

[0099] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the region from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0100] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) using the spectrum. In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmission, EHF transmission may experience even greater attenuation and a shorter range. The techniques disclosed herein can be adopted for transmission across one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory authority.

[0101] Wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be combined with component carriers operating using licensed frequency bands in a carrier aggregation configuration (e.g., LAA). Operations using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0102] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

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

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

[0105] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 in different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

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

[0107] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate combined beams for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a set of beams configured across the system bandwidth or one or more sub-bands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback on beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) in one or more directions, UE 115 may use similar techniques to transmit signals multiple times in different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

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

[0109] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmissions to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0110] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to some other time interval.

[0111] UE 115 may receive a first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state. UE 115 may receive a second control signal triggering activation of the first TCI state for communication during the first time-domain window, at least partially based on the first control signal. UE 115 may switch to the second TCI state for communication during the second time-domain window, at least partially based on the first control signal and the expiration of the first time-domain window, according to the second control signal.

[0112] Network entity 105 may send a first control signal to UE 115, the first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state. Network entity 105 may send a second control signal to UE 115, the second control signal triggering activation of the first TCI state for communication during the first time-domain window, at least in part based on the first control signal. Network entity 105 may communicate with UE 115 during the second time-domain window using the second TCI state, at least in part based on the first control signal and the expiration of the first time-domain window, according to the second control signal.

[0113] Figure 2 An example of a wireless communication system 200 supporting an indication of a predicted TCI state according to one or more aspects of this disclosure is shown. Wireless communication system 200 may implement aspects of wireless communication system 100. Wireless communication system 200 may include UE 205 and network entity 210, which may be examples of corresponding devices described herein.

[0114] Wireless networks use control signaling to signal or otherwise identify various parameters to be used for wireless communication between the network and the UE. For example, network entity 210 may send control signaling that dynamically and / or persistently identifies configuration parameters. For example, dynamic control signaling may include MAC-CE signaling and / or DCI signaling. Examples of more persistent signaling (e.g., semi-persistent and / or persistent) may include RRC signaling and / or other higher-layer signaling. Control signaling typically uses air resources as well as the processing power and energy consumption of the transmitting and receiving wireless devices.

[0115] An example of such parameters includes network configuration of TCI states for the UE. TCI states typically define QCL relationships between signals (e.g., QCL type relationships between reference signals, Physical Downlink Control or Shared Channel (PDxCH), Sound Reference Signal (SRS), and / or Physical Uplink Control or Shared Channel (PUxCH) signals). The network can typically identify the available TCI states for the UE via RRC signaling and then activate one or both specific TCI states for the UE using a MAC-CE TCI activation signal. The network can then dynamically instruct the UE to "turn on" the DCI TCI handover signal for the active TCI state to be used for communication. The network typically selects TCI states for activation and handover based on the communication being performed with the UE. That is, the network identifies the beams to be used for uplink and / or downlink communication with the UE and then activates / turns on based on the relationships between the identified beams / signals.

[0116] In some respects, this can lead to inefficient resource utilization and unnecessary processing and power consumption by wireless devices. As a non-limiting example, a UE may be traveling along or otherwise traversing a planned path. As the UE travels along the path, the directional beam used for communication with the UE may change periodically (e.g., due to UE movement). Since different beams are used for communication with the UE at different points along the path, this triggers the activation and switching of multiple TCI states for the UE. In some examples, multiple UEs may be traveling along the same planned path (e.g., along a highway, on a train, on a waterway, etc.). This situation can trigger a large amount of control signaling between the network and each UE, as separate control signaling is used to activate and switch the TCI state of each UE at different points along the path. When multiple UEs are traveling along a planned path at high mobility rates, such numerous and frequent updates become unsustainable in terms of resource utilization, processing power, and energy consumption.

[0117] Therefore, the aspects of the techniques described herein provide various mechanisms to improve the efficiency of control signaling, such as utilizing predictions to activate and switch TCI states of UEs (such as UEs traveling along known or expected paths or routes). The network can learn or otherwise identify certain patterns or historical usage of the UE over time, such as using machine learning (ML), artificial intelligence (AI), or other learning or data-driven methods and techniques. A non-limiting example may include the network (e.g., network entity 210) identifying a set of predicted TCI states of the UE for a corresponding set of time-domain windows (each predicted TCI state may be referred to as a second TCI state). The network can identify the confidence level of the predicted TCI states based on such a learning model, and, for example, enable the use of the predicted TCI states during the corresponding time-domain window when the confidence level of the predicted TCI states meets a confidence threshold. Instead of indicating a single instantaneous TCI state, network entity 210 may alternatively signal a series of TCI states predicted via AI / ML for multiple future time-domain moments. In some examples, such indication may be based on UE group common signaling, further reducing the overhead of indicating TCI state switching.

[0118] At 215, network entity 210 may send or otherwise provide (and UE 205 may receive or otherwise obtain) a first control signal carrying or otherwise conveying an indication of a first TCI state (TCI state #0) for a first time-domain window (e.g., TD window #0), such as via TCI state indication 230. The first control signal may further indicate a second TCI state (e.g., a predicted TCI state, TCI state #1) for a second time-domain window (TD window #1) following the first time-domain window. That is, the second time-domain window may begin at the end of the first time-domain window, with or without a gap between time-domain windows. In some examples, the first control signal may be a MAC-CE control signal conveying TCI state indication 230. The MAC-CE control signal may be a TCI state activation signal that can be activated at a TCI state that may have been previously (pre)configured for UE 205 RRC. The first control signal can be a UE-specific MAC-CE or a group-common MAC-CE (e.g., UE 205 may belong to a UE group associated with a group-common MAC-CE).

[0119] At 220, network entity 210 may send or otherwise provide (and UE 205 may receive or otherwise obtain) a second control signal that triggers the activation of a first TCI state for communication during a first time-domain window. The second control signal may identify the first TCI state that UE 205 switches to for communication during the first time-domain window. In some examples, the second control signal may be a DCI control signal (e.g., DCI format 1_1 or other DCI format) that delivers a TCI switching command. That is, the second control signal may indicate or otherwise identify a first TCI state previously activated for UE 205 to switch to for communication during the first time-domain window, for example, due to signals, beams, etc., being used for communication during the first time-domain window. UE 205 may switch to or otherwise transition to the first TCI state for communication at 225 during the first time-domain window. Communication using the first TCI state during the first time-domain window may include, but is not limited to, PDxCH communication received during the first time-domain window and / or SR / PUxCH communication transmitted during the first time-domain window.

[0120] exist Figure 2 In the illustrated non-limiting example, TCI state indication 230 identifies a first TCI state and one to N predicted TCI states corresponding to one to N subsequent time-domain windows, where N is a positive integer. In some aspects, N may refer to the number of second TCI states (e.g., predicted TCI states) indicated by UE 205 with corresponding second time-domain windows. That is, Figure 2The second TCI state in the illustrated non-limiting example may include N second TCI states (e.g., TCI state #1, TCI state #2, ..., TCI state #N) during a corresponding second time-domain window (e.g., TD window #1, TD window #2, ..., TD window #N). The first and second time-domain windows may follow each other (e.g., the next time-domain window may begin when the current time-domain window expires). For example, a second control signal that triggers activation of the first TCI state during the first time-domain window may be used to trigger the UE to switch to the second TCI state when the first time-domain window expires. That is, UE 205 may switch to TCI state #1 when TD window #0 expires. UE 205 may communicate with network entity 210 during TD window #1. When TD window #1 expires, UE 205 may switch to TCI state #2 during TD window #2 for communication. UE 205 may continue to switch to the predicted TCI state during their corresponding TD window N. This use of the predicted TCI state allows the network to switch the TCI state of UE 205 for multiple time-domain windows (e.g., a second time-domain window for the predicted TCI state) without additional control signaling for activating and / or switching the TCI state of UE 205. UE 205 can apply the QCL relationship associated with the TCI state to its communications with network entity 210 during their respective time-domain windows.

[0121] Therefore, network entity 210 may send or otherwise provide (and UE 205 may receive or otherwise obtain) indications of multiple second time-domain windows, including a second time-domain window (e.g., N second time-domain windows). In some examples, the durations of the first and second time-domain windows may be equal or different. In some examples, the duration of the second time-domain window may be based on the duration of the first time-domain window, for example, based on a ratio or other weighting factor applied to the first time-domain window to determine the second time-domain window. In some examples, the last time-domain window in the second time-domain windows (e.g., TD window #N) may have an undefined end point.

[0122] Therefore, the wireless communication system 200 illustrates a non-limiting example of network entity 210 indicating predicted TCI states for multiple future TD windows. UE 205 receives a TCI state switching indication signaled by network entity 210, wherein the indication message carries or otherwise conveys indications of multiple TCI states respectively applied to multiple future time-domain windows. The start point of the first time-domain window may follow a regular TCI state switching time. The last time-domain window (e.g., TD window #N) may not include an end point. UE 205 may apply QCL information included in the TCI state associated with a certain future time-domain window, such as PDxCH for reception during such time-domain window and / or SRS / PUxCH for transmission during such time-domain window.

[0123] In some aspects, the first control signaling and / or the second control signaling may be based on a UE group common indication, wherein UE 205 belongs to or is otherwise associated with a UE group. Such UE group common signaling may be based on signaling corresponding to multiple UEs. The group common signaling may carry or otherwise indicate the same set of such multiple TCI states (e.g., predicted TCI states) associated with a corresponding future time-domain window. UEs within the group may all apply QCL information included in or otherwise associated with a TCI state associated with a future time-domain window, such as PDxCH for reception during such time-domain window and / or SRS / PUxCH for transmission during such time-domain window.

[0124] Figure 3 An example of a TCI scheme 300 supporting an indication of a predicted TCI state according to one or more aspects of this disclosure is shown. Aspects of the TCI scheme 300 may be implemented by or by aspects of the wireless communication system 100 and the wireless communication system 200. Aspects of the TCI scheme 300 may be implemented at or by a UE and / or network entity, which may be examples of the corresponding devices described herein.

[0125] As discussed above, the techniques described herein provide a network signaling multiple predicted TCI states to be applied by the UE during corresponding time windows, where each predicted TCI state refers to a second TCI state, and the corresponding time window refers to a second time window. A network entity may send a first control signal (e.g., a MAC-CE TCI activation signal) to the UE, which identifies the first TCI state and the second TCI state. The first TCI state can be applied during the corresponding first time window, and the second TCI state can be applied during the corresponding second time window.

[0126] A network entity may send a second control signal (e.g., a TCI state switching command 305) to the UE, which triggers the UE to activate (e.g., switch) to a first TCI state during a first time window. When the first time window expires, the UE may switch to a second TCI state for communication during a second time window. When the second time window expires, the UE may switch to the next predicted TCI state (e.g., TCI state #2) for communication during the corresponding time window. This switching may continue for the N second TCI states during the corresponding N second time window periods without transmitting an additional TCI state switching command. For example, the UE may apply QCL information associated with the TCI state during the corresponding time window period.

[0127] As discussed above, the duration (e.g., T) of each time-domain window for the first TCI state and N second TCI states may be equal (e.g., the same duration) or unequal (e.g., different durations). TCI scheme 300 illustrates a non-limiting example of how an indication of a time-domain window can be provided to the UE. That is, TCI scheme 300 illustrates a non-limiting example of how network entities and / or the UE can communicate or otherwise determine the identification of the time-domain window associated with multiple predicted TCI states.

[0128] For time-domain windows (i.e., T0, T1, T2, ..., T1) associated with multiple TCI states indicated by network entities N The identifier (value) can be based on different options. The first option 310 may include whether the time offset is fixed or otherwise known to the wireless device, such as being (pre)defined in the relevant standard. For example, the UE may apply the previous TCI state (e.g., the first TCI state) immediately after receiving the TCI state switching command 305, and the remaining TCI states should be switched based on a standard-predefined time-domain offset. In some examples, the time-domain offset may be standard-defined in different ways for different remaining TCI states.

[0129] The second option at 315 may include an indication of the time offset between the first and second time domain windows, sent or otherwise provided by the network entity (and received or otherwise obtained by the UE). For example, the time offset (T) between the first and second time domain windows may be based on the start time of the first time domain window (e.g., a first start time) and the start time of the second time domain window (e.g., a second start time), the end time of the first time domain window (e.g., a first end time), and the end time of the second time domain window (e.g., a second end time), or a combination of the start and end times. In some examples, the time offset (T) may refer to the respective duration of the first time domain window and / or the duration of each second time domain window within the second time domain window. The expiration of the first time domain window may be based on the time offset at least in some respects. For example, the network entity may use RRC signaling to semi-statically (pre)configure the value of the time offset (e.g., T). For example, the time offset discussed with respect to the first option 310 may be (pre)configured by the network for the UE RRC. Such a time offset may be (pre)configured by RRC in different ways for different remaining TCI states.

[0130] A third option at 320 may include the network entity dynamically defining the time offsets of the first and second time domain windows. For example, the time offsets may be dynamically indicated via MAC-CE and / or DCI signaling. That is, in some examples, the first control signal may be a DCI signal that identifies or otherwise indicates the duration (e.g., the value of T) of each time domain window for which the UE is active in the TCI state, and the DCI signal may also include a predicted TCI state in addition to the first time domain window.

[0131] Therefore, the UE can switch to a first TCI state (TCI state #0) for communication during a first time-domain window with duration T0 based on TCI state switching command 305. When the first time-domain window expires, the UE can switch to a second TCI state (e.g., TCI state #1) for communication during a second time-domain window with duration T1. When the current time-domain window expires, the UE can continue to switch to the next TCI state (e.g., TCI state #2) during the corresponding time-domain window with duration T2, and so on, until the UE reaches a second TCI state with duration T1. N During the last time-domain window, the system switches to the final predicted TCI state (e.g., TCI state #N) for communication. For example, TCI state switching can be enabled at the UE without additional control signaling for activation and / or switching to each TCI state.

[0132] Figure 4A and Figure 4BAn example of a TCI scheme 400 supporting an indication of a predicted TCI state according to one or more aspects of this disclosure is shown. The TCI scheme 400 may be implemented by or by aspects of wireless communication system 100 or wireless communication system 200 and / or TCI scheme 300. The aspects of the TCI scheme 400 may be implemented by or by a UE and / or network entity, which may be an example of the corresponding device described herein. Figure 4A The TCI scheme 400-a illustrates a non-limiting example of the number of predicted TCI states per TCI code point. Figure 4B The TCI scheme 400-b illustrates a non-limiting example where the number of predicted TCI states per TCI code point is fixed or otherwise known to the wireless device.

[0133] As discussed above, the techniques described herein provide a network signaling multiple predicted TCI states to be applied by the UE during corresponding time windows, where each predicted TCI state refers to a second TCI state, and the corresponding time window refers to a second time window. A network entity may send a first control signal (e.g., MAC-CE TCI activation signal 405) to the UE, which identifies the first TCI state and the second TCI state. The first TCI state can be applied during the corresponding first time window, and the second TCI state can be applied during the corresponding second time window.

[0134] A network entity may send a second control signal (e.g., a TCI state switching command via DCI 415) to the UE, triggering the UE to activate (e.g., switch) to a first TCI state during a first time window. When the first time window expires, the UE may switch to a second TCI state for communication during a second time window. When the second time window expires, the UE may switch to the next predicted TCI state (e.g., TCI state #2) for communication during the corresponding time window. This switching may continue for N second TCI states during corresponding N second time windows without transmitting an additional TCI state switching command. For example, the UE may apply QCL information associated with the TCI state during the corresponding time window.

[0135] In some aspects, the MAC-CE TCI activation signal 405 may include one or more code points of the UE (e.g., TCI code point #0, TCI code point #1, ..., TCI code point #M). Each TCI code point may typically point to a set of bits (e.g., multiple bits), where each bit corresponds to a TCI state that is activated (e.g., using a "1" bit) or deactivated (e.g., using a "0" bit) for the UE. In some aspects, each TCI code point may activate or deactivate a first TCI state and a second TCI state for the UE. For example, TCI code point #0 may activate a first TCI state (e.g., TCI state #0 in this example) during a first time-domain window (e.g., TD window #0), and activate a second TCI state (e.g., TCI state #4, TCI state #1, and TCI state #8) for the UE during a corresponding second time-domain window (e.g., TD window #1, TD window #2, and TD window #3 in this example). TCI code point #1 can activate a first TCI state (e.g., TCI state #3 in this example) during a first time-domain window (e.g., TD window #0), and activate a second TCI state (e.g., TCI state #9, TCI state #7, TCI state #2, and TCI state #1) for the UE during corresponding second time-domain windows (e.g., TD window #1, TD window #2, TD window #3, and TD window #4 in this example). A final TCI code point (e.g., TCI code point #M in this example) can activate a first TCI state (e.g., TCI state #8 in this example) during a first time-domain window (e.g., TD window #0), and activate a second TCI state (e.g., TCI state #6 and TCI state #3 in this example) during corresponding second time-domain windows (e.g., TD window #1 and TD window #2 in this example).

[0136] Therefore, TCI scheme 400-a illustrates a non-limiting example where the TCI state activation MAC-CE is enhanced to deliver or otherwise indicate multiple TCI states (e.g., predicted TCI states) for each TCI code point relative to corresponding but not time-domain windows. For example, the network entity indication may be further based on the MAC-CE of the activation TCI state, where each TCI code point includes multiple TCI states relative to corresponding multiple time-domain windows. The actual TCI state switching command can be received via DCI 415 by indicating the TCI code point from the most recently received TCI state activation MAC-CE, for example, the UE filters the TCI code point indicated in the DCI based on the TCI code point indicated in the TCI state activation MAC-CE.

[0137] TCI state activation MAC-CE can be based on a separate MAC-CE activating other conventional types of TCI states. If so, the DCI for switching TCI states can include an additional field indicating which MAC-CE to reference when indicating the TCI state to switch to. In some examples, the network entity can use RRC signaling to (pre)configure, or a separate MAC-CE can be used to instruct the UE which MAC-CE to reference when receiving this DCI. In some examples, the UE may not expect to receive this new MAC-CE as well as conventional types of MAC-CEs. When this TCI state activation MAC-CE is used to jointly activate predicted TCI states and other types of TCI states, the conventional joint / downlink / uplink TCI state switching DCI format can be reused.

[0138] Therefore, the network may transmit or otherwise provide (and the UE may receive or otherwise obtain) one or more TCI code points in a first control signal (e.g., TCI State Activation MAC-CE). Each TCI code point may identify a predicted set of TCI states (e.g., a second TCI state) during a corresponding time-domain window set (e.g., a second time-domain window). The network may transmit or otherwise provide (and the UE may receive or otherwise obtain) an indication of the TCI code point in a second control signal (e.g., DCI 415). The TCI code point indicated in the TCI handover DCI may be from the set of TCI code points indicated in the TCI State Activation MAC-CE. Therefore, the UE may use the TCI code point indicated in the TCI handover command to identify or otherwise select the corresponding TCI code point indicated in the TCI State Activation MAC-CE. Based on the identified TCI code point indicated in the TCI handover DCI, the UE may identify or otherwise determine a first TCI state and a second TCI state to be used for communication with network entities during the first and second time-domain windows, respectively.

[0139] Figure 4A The TCI scheme 400-a illustrates a non-limiting example of a network including an indication 410 for the number of predicted TCI states for each TCI code point. This indication 410 may include a variable TCI state number for each TCI code point and an associated number of time-domain windows. Each TCI code point in the MAC-CE may (e.g., in the foremost portion of the TCI code point) further carry or otherwise transmit a field indicating the number of TCI states for the corresponding TCI code point and thus the number of associated time-domain windows. The remaining fields of the TCI code point may sequentially indicate the corresponding number of TCI state identifiers configured by the RRC (e.g., using bits or other information).

[0140] Figure 4BThe TCI scheme 400-b illustrates a non-limiting example where the number of TCI states per TCI code point indicated in the TCI state activation MAC CE is fixed or otherwise known. For example, there may be a common (e.g., the same) number of predicted TCI states per TCI code point. In some aspects, there is a fixed TCI state number and an associated time-domain window number per TCI code point. The number of TCI states per TCI code point may be based on a standard (e.g., (pre)defined) or RRC (pre)configured. The number of TCI states may be fixed (e.g., the same) across all TCI code points in the MAC-CE.

[0141] Figure 5A and Figure 5B An example of a TCI scheme 500 supporting an indication of a predicted TCI state according to one or more aspects of this disclosure is shown. The TCI scheme 500 may be implemented by aspects of wireless communication system 100 or wireless communication system 200 and / or aspects of TCI scheme 300 or TCI scheme 400, or these aspects. The aspects of the TCI scheme 500 may be implemented by or by a UE and / or network entity, which may be an example of the corresponding device described herein. Figure 5A The TCI scheme 500-a illustrates a non-limiting example of indicating different time-domain windows for each TCI code point in the TCI state-activated MAC-CE. Figure 5B The TCI scheme 500-b illustrates a non-limiting example of indicating equal duration time-domain windows in a MAC-CE activated in TCI state.

[0142] As discussed above, the techniques described herein provide a network signaling multiple predicted TCI states to be applied by the UE during corresponding time windows, where each predicted TCI state refers to a second TCI state, and the corresponding time window refers to a second time window. For example, a network entity may send a first control signal (e.g., MAC-CE TCI activation signal 505) to the UE, which identifies the first TCI state and the second TCI state. The first TCI state can be applied during the corresponding first time window, and the second TCI state can be applied during the corresponding second time window.

[0143] A network entity may send a second control signal (e.g., a TCI state switching command) to the UE, triggering the UE to activate (e.g., switch) to a first TCI state during a first time window. When the first time window expires, the UE may switch to a second TCI state for communication during a second time window. When the second time window expires, the UE may switch to the next predicted TCI state for communication during the corresponding time window. This switching can continue for N second TCI states during corresponding N second time windows without transmitting an additional TCI state switching command. For example, the UE may apply QCL information associated with the TCI state during the corresponding time window.

[0144] In some aspects, the MAC-CE TCI activation signal 505 may include one or more code points of the UE (e.g., TCI code point #0, TCI code point #1, ..., TCI code point #M). Each TCI code point may typically point to a set of bits (e.g., multiple bits), where each bit corresponds to a TCI state that is activated (e.g., using a "1" bit) or deactivated (e.g., using a "0" bit) for the UE. In some aspects, each TCI code point may activate or deactivate a first TCI state and a second TCI state for the UE.

[0145] TCI scheme 500 illustrates a non-limiting example of TCI state-activated MAC-CE enhancement for different time-domain windows for each TCI code point. Figure 5A The TCI scheme 500-a illustrates an example where a first control signal (e.g., TCI state activation MAC-CE) carries or otherwise conveys an indication of the duration of a time-domain window for each predicted TCI state.

[0146] That is, the time-domain window can also be activated by the TCI state to indicate each TCI code point in the MAC-CE, or for each TCI code point. For example, each TCI code point in the MAC-CE may include an indication as discussed above (T0, T1, T2, ..., T...). N The field containing the value of (T0, T1, T2, ..., T) allows the duration of the time-domain window associated with the TCI state in the TCI code point to be identified based on such values. In some examples, (T0, T1, T2, ..., T) N The multiple options for TCI code point selection can be pre-configured by RRC, while one option is available for TCI code point selection. In some examples, the TCI code point can explicitly indicate a single value. This makes T0, T1, T2, ..., T N = In some examples, TCI code points can indicate (T0, T1, T2, ..., T...). N( ) has multiple options, while TCI state switching DCI includes an additional field that filters one of the options from such multiple options.

[0147] Figure 5B The TCI scheme 500-b illustrates an example where a first control signal (e.g., TCI state activation MAC-CE 510) carries or otherwise transmits an indication of an equal duration for a time-domain window for each predicted TCI state. That is, the TCI state activation MAC-CE 515 may also include an indication (T0, T1, T2, ..., T...). N The field containing the value of a TCI code point allows time-domain windows associated with all TCI code points to be identified in the same way (e.g., with equal or unequal durations) based on such values. For example, the TCI state activation MAC-CE 515 can explicitly indicate a single value. This makes T0, T1, T2, ..., T N = It should be applied to all TCI code points.

[0148] Figure 6 An example of a TCI scheme 600 supporting an indication of a predicted TCI state according to one or more aspects of this disclosure is shown. The TCI scheme 600 may implement, or be implemented by, aspects of wireless communication system 100 or wireless communication system 200 and / or aspects of TCI scheme 300, TCI scheme 400 or TCI scheme 500. The aspects of the TCI scheme 600 may be implemented by, or be implemented by, a UE and / or network entity, which may be an example of the corresponding device described herein.

[0149] As discussed above, the techniques described herein provide a network signaling multiple predicted TCI states to be applied by the UE during corresponding time windows, where each predicted TCI state refers to a second TCI state, and the corresponding time window refers to a second time window. A network entity may send a first control signal (e.g., a MAC-CE TCI activation signal) to the UE, which identifies the first TCI state and the second TCI state. The first TCI state can be applied during the corresponding first time window, and the second TCI state can be applied during the corresponding second time window.

[0150] A network entity may send a second control signal (e.g., a TCI state switching command 605) to the UE, triggering the UE to activate (e.g., switch) to a first TCI state during a first time window. When the first time window expires, the UE may switch to a second TCI state for communication during a second time window. When the second time window expires, the UE may switch to the next predicted TCI state for communication during the corresponding time window. This switching may continue for the N second TCI states during the corresponding N second time window periods without transmitting an additional TCI state switching command. For example, the UE may apply QCL information associated with the TCI state during the corresponding time window period.

[0151] TCI scheme 600 illustrates a non-limiting example of using a UE group common TCI state switching DCI command as a second control signal. That is, the UE can receive the second control signal via the group common DCI. The UE can belong to a group associated with the group common DCI. In other examples, it should be understood that the first control signal (e.g., TCI state activation MAC-CE) can carry or otherwise convey an indication that the UE belongs to the group common DCI. Although not shown, in other examples, the second control signal can be received in a UE-specific DCI.

[0152] Therefore, TCI scheme 600 illustrates a non-limiting example of using a UE group common TCI state switching DCI command to trigger activation (e.g., switching) of a first TCI state. The UE may receive a group common DCI comprising N blocks (e.g., a new DCI format and / or a new RNTI). Each block may refer to a TCI code point in the most recently received MAC-CE (e.g., the most recently activated TCI state MAC-CE). The UE may identify RRC (pre)configured parameters (e.g., Block-ID-TCI-Predict) such that the UE can refer to the Block-ID-TCI-Predict block within the group common DCI to identify the TCI state to which it wants to switch.

[0153] As discussed, in some examples, the first control signal (e.g., TCI State Activation MAC-CE) may carry or otherwise convey an indication that the UE belongs to a group common DCI. Therefore, the block ID can be updated via the MAC-CE. For example, the RRC (pre)configured parameter Block-ID-TCI-Predict can be dynamically updated by the MAC-CE (e.g., TCI State Activation MAC-CE or a different MAC-CE). The MAC-CE may include an additional field that includes the updated value of Block-ID-TCI-Predict, thereby assigning the UE to a different UE group for subsequent group common TCI state switching commands.

[0154] Figure 7 An example of a TCI scheme 700 supporting an indication of a predicted TCI state according to one or more aspects of this disclosure is shown. The TCI scheme 700 may implement, or be implemented by, aspects of wireless communication system 100 or wireless communication system 200 and / or aspects of TCI scheme 300, TCI scheme 400, TCI scheme 500 or TCI scheme 600. The aspects of the TCI scheme 700 may be implemented by, or be implemented by, a UE and / or network entity, which may be an example of the corresponding device described herein.

[0155] As discussed above, the techniques described herein provide a network signaling multiple predicted TCI states to be applied by the UE during corresponding time windows, where each predicted TCI state refers to a second TCI state, and the corresponding time window refers to the second time window. A network entity may send a first control signal (e.g., a MAC-CE TCI activation signal) to the UE, identifying a first TCI state 705 and a second TCI state (e.g., TCI states 710, 715, 720, and 725). The first TCI state 705 may be applied during the corresponding first time window (e.g., during TD window #0), and the second TCI state may be applied during the corresponding second time windows (e.g., during TD windows #1, #2, #3, and #4, respectively).

[0156] A network entity may send a second control signal (e.g., a TCI state switching command) to the UE, triggering the UE to activate (e.g., switch) to a first TCI state 705 during a first time window. When the first time window expires, the UE may switch to a second TCI state (e.g., TCI state 710) during a second time window for communication. When the second time window expires, the UE may switch to the next predicted TCI state (e.g., TCI state 715 in this example) during the corresponding time window for communication. This switching can continue for N second TCI states during corresponding N second time windows without transmitting an additional TCI state switching command, wherein... Figure 7 In the non-limiting example shown, N = four. For example, the UE can apply QCL information associated with the TCI state during the corresponding time window.

[0157] TCI scheme 700 illustrates a non-limiting example of a previously activated and switched predicted TCI state being overwritten by the network. For example, before a second time-domain window (e.g., TD window #1, TD window #2, TD window #3, or TD window #4), the UE may receive or otherwise acquire a third control signal that triggers the activation of an updated TCI state during the second time-domain window. In response, the UE overwrites the second TCI state during the corresponding second time-domain window. Alternatively, the UE may switch to the updated TCI state during the second time-domain window for communication with network entities.

[0158] Therefore, TCI scheme 700 illustrates a non-limiting example of predicting TCI state overwriting by instantaneous switching. A TCI state activated via MAC-CE (e.g., in the first control signal) and then switched by a regular DCI or group common DCI (e.g., the second control signal) can be overwritten by a regular single-shot TCI state switching command. For example, consider the K time-domain window (where 0 ≤ K ≤ K) concerning the Kth TCI state. Figure 7 In the illustrated non-limiting example, the Kth time-domain window corresponds to TD window #2, during which TCI state 715 has previously been activated and switched. If the UE receives a TCI state switching command (e.g., a DCI-based TCI state switching command) that triggers immediate activation (e.g., switching) to the updated TCI state, the UE should immediately switch to this TCI state and ignore the Kth TCI state associated with the Kth time-domain window.

[0159] In a non-limiting example, this could include the UE switching to an updated TCI state 730 (e.g., TCI state #4 in this example) during TD window #2, instead of switching to the previously predicted TCI state #6 for TD window #2. In this example, the UE could continue to apply the updated TCI state (e.g., TCI state #4) for the remaining time-domain window (e.g., during TD window #3 and TD window #4) in response to an instruction to switch to an updated TCI state.

[0160] In another non-limiting example, this could include the UE switching to an updated TCI state 735 (e.g., TCI state #4 in this example) during TD window #2, instead of switching to the previously predicted TCI state #6 for TD window #2. However, in this example, the UE could return to (e.g., switch to) a previously configured predicted TCI state (e.g., a second TCI state) during the corresponding time window. For example, the UE could switch to TCI state #9 during TD window #3 and to TCI state #12 during TD window #4.

[0161] Whether the UE resumes handover to the predicted TCI state for the (k+1)th time window, the (k+2)th time window, ..., the tth time window can be further based on standard (pre)definition and / or on further configuration / indication from network entities.

[0162] For example, relevant standards may predefine that the UE should resume using the predicted TCI state once it reaches the (K+1)th time-domain window, the (K+2)th time-domain window, ..., the Kth time-domain window. As another example, relevant standards may predefine that the UE should ignore the remaining predicted TCI states related to the (K+1)th time-domain window, the (K+2)th time-domain window, ..., the Kth time-domain window.

[0163] In another example, the network entity can pre-configure the UE (with RRC) whether it should resume or ignore the predicted TCI state during a corresponding time window. For example, the network entity can use MAC-CE and / or DCI signaling to dynamically indicate whether the UE should resume or ignore the predicted TCI state. The MAC-CE signaling may include the first control signal discussed above, or it may be a different MAC-CE.

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

[0165] Receiver 810 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to indications of predicted TCI states). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

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

[0167] The communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of indicative indications of the predicted TCI state as described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

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

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

[0171] According to the examples disclosed herein, the communication manager 820 can support wireless communication at the UE. For example, the communication manager 820 can be configured or operable to support components for receiving a first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state. The communication manager 820 can be configured or operable to support components for receiving a second control signal triggering the activation of a first TCI state for communication during the first time-domain window based on the first control signal. The communication manager 820 can be configured or operable to support components for switching to a second TCI state for communication during the second time-domain window based on the first control signal and the expiration of the first time-domain window, according to the second control signal.

[0172] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., control receiver 810, transmitter 815, communication manager 820 or a combination thereof or a processor otherwise coupled to them) can support techniques for reducing control signaling overhead by indicating a set of predicted TCI states to be applied to communications by the UE and the network during corresponding time-domain windows.

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

[0174] Receiver 910 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to indications of predicted TCI states). The information may be passed to other components of device 905. Receiver 910 may utilize a single antenna or a collection of antennas.

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

[0176] Device 905 or its various components may be examples of parts used to perform various aspects of indicating a predicted TCI state as described herein. For example, communication manager 920 may include TCI activation manager 925, TCI switching manager 930, TCI communication manager 935, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use or otherwise cooperate with receiver 910, transmitter 915, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or be integrated in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0177] According to the examples disclosed herein, the communication manager 920 can support wireless communication at the UE. The TCI activation manager 925 is capable of, configured to, or operable to support components for receiving a first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state. The TCI switching manager 930 is capable of, configured to, or operable to support components for receiving a second control signal triggering the activation of a first TCI state for communication during the first time-domain window based on the first control signal. The TCI communication manager 935 is capable of, configured to, or operable to support components for switching to a second TCI state for communication during the second time-domain window based on the first control signal and the expiration of the first time-domain window, according to the second control signal.

[0178] Figure 10A block diagram 1000 is shown of a communication manager 1020 supporting indication of a predicted TCI state according to one or more aspects of this disclosure. The communication manager 1020 may be an example of aspects of a communication manager 820, a communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of components for performing various aspects of indicating a predicted TCI state as described herein. For example, the communication manager 1020 may include a TCI activation manager 1025, a TCI switching manager 1030, a TCI communication manager 1035, a time-domain window manager 1040, a TCI code point manager 1045, an indication manager 1050, a TCI state overwrite manager 1055, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0179] According to the examples disclosed herein, communication manager 1020 can support wireless communication at the UE. TCI activation manager 1025 is capable of, configured to, or operable to support components for receiving a first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state. TCI switching manager 1030 is capable of, configured to, or operable to support components for receiving a second control signal triggering the activation of a first TCI state for communication during the first time-domain window based on the first control signal. TCI communication manager 1035 is capable of, configured to, or operable to support components for switching to a second TCI state for communication during the second time-domain window based on the first control signal and the expiration of the first time-domain window, according to the second control signal.

[0180] In some examples, in order to support receiving a first control signal, the time domain window manager 1040 is capable of, configured to, or operable to support components for receiving an indication of a time offset between a first end time of a first time domain window and a second end time of a second time domain window, wherein the expiration of the first time domain window is based on the time offset.

[0181] In some examples, in order to support the reception of the first control signal, the time-domain window manager 1040 is capable of, configured to, or operable to support components for receiving an RRC signal that semi-statically defines the time offset between the first and second time-domain windows.

[0182] In some examples, in order to support the reception of the first control signal, the time domain window manager 1040 can be configured or operable to support components for receiving downlink control information that dynamically defines the time offset between the first and second time domain windows.

[0183] In some examples, to support receiving a first control signal, the time-domain window manager 1040 is capable of, configured to, or operable to support components for receiving instructions on a set of multiple time-domain windows, including a first time-domain window and a second time-domain window, wherein the last time-domain window in the set is associated with an undefined end point. In some examples, the duration of the second time-domain window is based on the duration of the first time-domain window according to a defined ratio. In some examples, the first and second time-domain windows are equal in duration. In some examples, the first and second time-domain windows are not equal in duration.

[0184] In some examples, the TCI code point manager 1045 is capable of, configured to, or operable to support components for receiving one or more TCI status code points via a first control signal, each TCI status code point identifying a predicted set of TCI states during a corresponding second time-domain window set, the predicted set of TCI states being based on a second TCI state. In some examples, the TCI code point manager 1045 is capable of, configured to, or operable to support components for receiving TCI status code points from one or more TCI status code points via a second control signal, wherein switching to the second TCI state is based on receiving a TCI status code point.

[0185] In some examples, the TCI code point manager 1045 is capable of, configured to, or operable to support components for receiving an indication of the number of predicted TCI states for each of one or more TCI status code points via a first control signal. In some examples, each of the one or more TCI status code points includes a common number of predicted TCI states.

[0186] In some examples, the TCI code point manager 1045 is capable of, configured to, or operable to support components for receiving, via a second control signal, an indication of the duration of a time-domain window for each predicted TCI state in a set of predicted TCI states for each of one or more TCI state code points, wherein the second time-domain window is based on the duration. In some examples, the second time-domain window comprises equal durations.

[0187] In some examples, the instruction manager 1050 is capable of, configured to, or operable to support components for receiving a first control signal via a group common MAC-CE, wherein the UE belongs to a UE group associated with the group common MAC-CE.

[0188] In some examples, the instruction manager 1050 is capable of, configured to, or operable to support components for receiving a second control signal via the group common DCI, wherein the UE belongs to a UE group associated with the group common DCI. In some examples, the first control signal indicates that the UE belongs to a UE group.

[0189] In some examples, the indicator manager 1050 is capable of, configured to, or operable to support components for receiving a second control signal via a UE-specific DCI.

[0190] In some examples, the TCI state overwrite manager 1055 is capable of, configured to, or operable to support components for receiving a third control signal prior to a second time-domain window, which triggers the activation of an updated TCI state during the second time-domain window. In some examples, the TCI state overwrite manager 1055 is capable of, configured to, or operable to support components for overwriting a switch to a second TCI state during the second time-domain window based on the third control signal and switching to the updated TCI state.

[0191] Figure 11 A diagram of a system 1100 including device 1105 supporting indication of predicted TCI state is shown according to one or more aspects of this disclosure. Device 1105 may be an example of device 805, device 905, or UE 115 as described herein, or a component including such devices. Device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1105 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, a memory 1130, a code 1135, and a processor 1140. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 1145).

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

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

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

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

[0196] According to the examples disclosed herein, the communication manager 1120 may support wireless communication at the UE. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for receiving a first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state. The communication manager 1120 may be capable of, configured to, or operable to support components for receiving a second control signal triggering the activation of a first TCI state for communication during the first time-domain window based on the first control signal. The communication manager 1120 may be capable of, configured to, or operable to support components for switching to a second TCI state for communication during the second time-domain window based on the first control signal and the expiration of the first time-domain window, according to the second control signal.

[0197] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support techniques for reducing control signaling overhead by indicating a set of predicted TCI states to be applied to communications by the UE and the network during corresponding time-domain windows.

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

[0199] Figure 12 A block diagram 1200 of a device 1205 supporting an indication of a predicted TCI state according to one or more aspects of this disclosure is shown. Device 1205 may be an example of aspects of network entity 105 as described herein. Device 1205 may include receiver 1210, transmitter 1215, and communication manager 1220. Device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0200] Receiver 1210 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1205. In some examples, receiver 1210 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0201] Transmitter 1215 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1205. For example, transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1215 and receiver 1210 may be co-located in a transceiver, which may include or be coupled to a modem.

[0202] The communication manager 1220, receiver 1210, transmitter 1215, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of indicating the predicted TCI state as described herein. For example, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

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

[0205] In some examples, the communication manager 1220 may be configured to use or otherwise coordinate with the receiver 1210, transmitter 1215, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1220 may receive information from the receiver 1210, transmit information to the transmitter 1215, or be integrated in combination with the receiver 1210, transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0206] According to the examples disclosed herein, the communication manager 1220 can support wireless communication at a network entity. For example, the communication manager 1220 can be configured or operable to support components for sending a first control signal to the UE, the first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state. The communication manager 1220 can be configured or operable to support components for sending a second control signal to the UE, the second control signal triggering the activation of a first TCI state for communication during the first time-domain window based on the first control signal. The communication manager 1220 can be configured or operable to support components for communicating with the UE using a second TCI state during a second time-domain window based on the first control signal and the expiration of the first time-domain window, according to the second control signal.

[0207] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 (e.g., controlling receiver 1210, transmitter 1215, communication manager 1220, or a combination thereof, or a processor otherwise coupled to them) can support techniques for reducing control signaling overhead by instructing the UE and network to apply a set of predicted TCI states to communications during corresponding time-domain windows.

[0208] Figure 13 A block diagram 1300 of a device 1305 supporting an indication of a predicted TCI state according to one or more aspects of this disclosure is shown. Device 1305 may be an example of aspects of device 1205 or network entity 105 as described herein. Device 1305 may include a receiver 1310, a transmitter 1315, and a communications manager 1320. Device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0209] Receiver 1310 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1305. In some examples, receiver 1310 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1310 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0210] Transmitter 1315 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1305. For example, transmitter 1315 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1315 and receiver 1310 may be co-located in a transceiver, which may include or be coupled to a modem.

[0211] Device 1305 or its various components may be examples of parts used to perform various aspects of indicating a predicted TCI state as described herein. For example, communication manager 1320 may include TCI activation manager 1325, TCI switching manager 1330, TCI communication manager 1335, or any combination thereof. Communication manager 1320 may be examples of aspects of communication manager 1220 as described herein. In some examples, communication manager 1320 or its various components may be configured to use or otherwise cooperate with receiver 1310, transmitter 1315, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1320 may receive information from receiver 1310, transmit information to transmitter 1315, or be integrated in combination with receiver 1310, transmitter 1315, or both to acquire information, output information, or perform various other operations as described herein.

[0212] According to the examples disclosed herein, communication manager 1320 can support wireless communication at network entities. TCI activation manager 1325 is capable of, configured to, or operable to support components for sending a first control signal to the UE, the first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state. TCI switching manager 1330 is capable of, configured to, or operable to support components for sending a second control signal to the UE, the second control signal triggering the activation of a first TCI state for communication during the first time-domain window based on the first control signal. TCI communication manager 1335 is capable of, configured to, or operable to support components for communicating with the UE using a second TCI state during a second time-domain window based on the first control signal and the expiration of the first time-domain window, according to the second control signal.

[0213] Figure 14 A block diagram 1400 is shown of a communication manager 1420 supporting indication of a predicted TCI state according to one or more aspects of this disclosure. The communication manager 1420 may be an example of aspects of the communication manager 1220, communication manager 1320, or both as described herein. The communication manager 1420 or its various components may be examples of components for performing various aspects of indicating a predicted TCI state as described herein. For example, the communication manager 1420 may include a TCI activation manager 1425, a TCI switching manager 1430, a TCI communication manager 1435, a time-domain window manager 1440, a TCI code point manager 1445, an indication manager 1450, a TCI state overwrite manager 1455, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between the protocol layers of the protocol stack, within devices, components or virtualization components associated with network entity 105, between devices, components or virtualization components associated with network entity 105), or any combination thereof.

[0214] According to the examples disclosed herein, the communication manager 1420 can support wireless communication at a network entity. The TCI activation manager 1425 is capable of, configured to, or operable to support components for sending a first control signal to the UE, the first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state. The TCI handover manager 1430 is capable of, configured to, or operable to support components for sending a second control signal to the UE, the second control signal triggering the activation of the first TCI state for communication during the first time-domain window based on the first control signal. The TCI communication manager 1435 is capable of, configured to, or operable to support components for communicating with the UE using a second TCI state during a second time-domain window based on the first control signal and the expiration of the first time-domain window, according to the second control signal.

[0215] In some examples, in order to support the transmission of a first control signal, the time domain window manager 1440 is capable of, configured to, or operable to support components for transmitting an indication of a time offset between a first end time of a first time domain window and a second end time of a second time domain window, wherein the expiration of the first time domain window is based on the time offset.

[0216] In some examples, in order to support the transmission of the first control signal, the time domain window manager 1440 is capable of, configured to, or operable to support components for transmitting an RRC signal that semi-statically defines the time offset between the first and second time domain windows.

[0217] In some examples, in order to support the transmission of the first control signal, the time domain window manager 1440 can be configured or operable to support components for transmitting downlink control information that dynamically defines the time offset between the first and second time domain windows.

[0218] In some examples, to support the transmission of a first control signal, the time-domain window manager 1440 is capable of, configured to, or operable to support components for transmitting instructions to a set of multiple time-domain windows, including a first time-domain window and a second time-domain window, wherein the last time-domain window in the set is associated with an undefined end point. In some examples, the duration of the second time-domain window is based on the duration of the first time-domain window according to a defined ratio. In some examples, the first and second time-domain windows are equal in duration. In some examples, the first and second time-domain windows are not equal in duration.

[0219] In some examples, the TCI code point manager 1445 is capable of, configured to, or operable to support components for transmitting one or more TCI status code points via a first control signal, each TCI status code point identifying a predicted set of TCI states during a corresponding second time-domain window set, the predicted set of TCI states being based on a second TCI state. In some examples, the TCI code point manager 1445 is capable of, configured to, or operable to support components for transmitting TCI status code points from one or more TCI status code points via a second control signal, wherein communication with the UE using the second TCI state is based on transmitting the TCI status code points.

[0220] In some examples, the TCI code point manager 1445 is capable of, configured to, or operable to support components for sending an indication of the number of predicted TCI states for each of one or more TCI status code points via a first control signal. In some examples, each of the one or more TCI status code points includes a common number of predicted TCI states.

[0221] In some examples, the TCI code point manager 1445 is capable of, configured to, or operable to support components for sending an indication of the duration of a time-domain window for each predicted TCI state in a set of predicted TCI states via a second control signal for each of one or more TCI state code points, wherein the second time-domain window is based on the duration. In some examples, the second time-domain window comprises equal durations.

[0222] In some examples, the instruction manager 1450 is capable of, configured to, or operable to support components for transmitting a first control signal via the group common MAC-CE, wherein the UE belongs to a UE group associated with the group common MAC-CE.

[0223] In some examples, the instruction manager 1450 is capable of, configured to, or operable to support components for transmitting a second control signal via the group common DCI, wherein the UE belongs to a UE group associated with the group common DCI. In some examples, the first control signal indicates that the UE belongs to a UE group.

[0224] In some examples, the indicator manager 1450 is capable of, configured to, or operable to support components for transmitting a second control signal via a UE-specific DCI.

[0225] In some examples, the TCI state overwrite manager 1455 is capable of, configured to, or operable to support components for sending a third control signal prior to a second time-domain window, which triggers the activation of an updated TCI state during the second time-domain window. In some examples, the TCI state overwrite manager 1455 is capable of, configured to, or operable to support components for overwriting a switch to a second TCI state during the second time-domain window based on the third control signal and switching to the updated TCI state.

[0226] Figure 15 A diagram of a system 1500 including a device 1505 supporting indication of a predicted TCI state, according to one or more aspects of this disclosure, is shown. Device 1505 may be an example of device 1205, device 1305, or network entity 105 as described herein, or may include components thereof. Device 1505 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1505 may include components supporting output and acquisition of communication, such as a communication manager 1520, a transceiver 1510, an antenna 1515, a memory 1525, code 1530, and a processor 1535. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 1540).

[0227] Transceiver 1510 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1510 may include a wired transceiver and be able to communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1510 may include a wireless transceiver and be able to communicate bidirectionally with another wireless transceiver. In some examples, device 1505 may include one or more antennas 1515 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1510 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1515, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1515, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1515 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1515 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1510 may include one or more processor or memory components or be configured to couple to one or more processor or memory components operable to perform or support operations based on received or acquired information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1510, or transceiver 1510 and one or more antennas 1515, or transceiver 1510 and one or more antennas 1515 and one or more processor or memory components (e.g., processor 1535 or memory 1525 or both) may be included in a chip or chip assembly mounted in device 1505. In some examples, the transceiver may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

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

[0229] Processor 1535 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, processor 1535 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1535. Processor 1535 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1525) to cause device 1505 to perform various functions (e.g., functions or tasks supporting indications of predictive TCI states). For example, device 1505 or components of device 1505 may include processor 1535 and memory 1525 coupled to processor 1535, processor 1535 and memory 1525 being configured to perform the various functions described herein. Processor 1535 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that can host functions for (e.g., by executing code 1530) performing the functions of device 1505. Processor 1535 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1505 (such as in memory 1525). In some embodiments, processor 1535 may be a component of a processing system. A processing system generally refers to a system or series of machines or components that receive inputs and process those inputs to produce a set of outputs that can be passed to, for example, other systems or components of device 1505. For example, the processing system of device 1505 may refer to a system that includes various other components or sub-components of device 1505 (such as processor 1535, or transceiver 1510, or communication manager 1520, or other components or combinations of components of device 1505). The processing system of device 1505 may interface with other components of device 1505 and may process information received from other components (such as inputs or signals) or output information to other components. For example, a chip or modem of device 1505 may include a processing system and one or more interfaces for outputting information or for receiving information or both. One or more interfaces may be implemented as, or otherwise include, a first interface configured to output information and a second interface configured to receive information, or the same interface configured to both output and receive information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between the processing system of the chip or modem and the transmitter, enabling device 1505 to transmit information output from the chip or modem. Additionally or alternatively, in some specific implementations, one or more interfaces may refer to an interface between the processing system of the chip or modem and the receiver, enabling device 1505 to receive information or signal input, and such information may be transmitted to the processing system.Those skilled in the art will readily recognize that the first interface can also receive information or signal input, and the second interface can also output information or signal output.

[0230] In some examples, bus 1540 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1540 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1505, or communication performed between different components of device 1505 that are co-addressable or located in different locations (e.g., where device 1505 may refer to a system in which one or more of communication manager 1520, transceiver 1510, memory 1525, code 1530, and processor 1535 may be located in one of the different components or partitioned between the different components).

[0231] In some examples, the communication manager 1520 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1520 can manage the transfer of data communication by client devices such as one or more UEs 115. In some examples, the communication manager 1520 can manage communication with other network entities 105 and may include a controller or scheduler for coordinating other network entities 105 to control communication with UE 115. In some examples, the communication manager 1520 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0232] According to the examples disclosed herein, the communication manager 1520 can support wireless communication at a network entity. For example, the communication manager 1520 can be configured or operable to support components for sending a first control signal to the UE, the first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state. The communication manager 1520 can be configured or operable to support components for sending a second control signal to the UE, the second control signal triggering the activation of a first TCI state for communication during the first time-domain window based on the first control signal. The communication manager 1520 can be configured or operable to support components for communicating with the UE using a second TCI state during a second time-domain window based on the first control signal and the expiration of the first time-domain window, according to the second control signal.

[0233] By including or configuring a communication manager 1520 according to an example as described herein, device 1505 can support techniques for reducing control signaling overhead by indicating a set of predicted TCI states to be applied to communications by the UE and the network during corresponding time-domain windows.

[0234] In some examples, the communication manager 1520 may be configured to use or otherwise coordinate with the transceiver 1510, one or more antennas 1515 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receive, acquire, monitor, output, transmit). Although the communication manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 may be supported or performed by the transceiver 1510, processor 1535, memory 1525, code 1530, or any combination thereof. For example, code 1530 may include instructions that can be executed by the processor 1535 to cause the device 1505 to perform various aspects of the indication of the predicted TCI state as described herein, or the processor 1535 and memory 1525 may be otherwise configured to perform or support such operations.

[0235] Figure 16 A flowchart illustrating a method 1600 for indicating a predicted TCI state, illustrative of various aspects of this disclosure, is shown. Operation of method 1600 may be implemented by a UE or its components as described herein. For example, operation of method 1600 may be performed by, as referenced... Figures 1 to 11 The described UE 115 is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the wireless UE to perform the described function. Additionally or alternatively, the wireless UE can use dedicated hardware to perform aspects of the described function.

[0236] At 1605, the method may include: receiving a first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state. The operation of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to [reference needed]. Figure 10 The TCI Activation Manager 1025 described is used to perform this.

[0237] At 1610, the method may include: receiving a second control signal that triggers the activation of a first TCI state for communication during a first time-domain window based on a first control signal. The operation of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be provided by reference to [reference needed]. Figure 10 The TCI Switching Manager 1030 described herein is used to execute this.

[0238] At 1615, the method may include: switching to a second TCI state for communication during a second time-domain window based on a first control signal and the expiration of a first time-domain window, according to a second control signal. The operation of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1615 may be provided by reference to [reference needed]. Figure 10 The TCI communication manager 1035 described is used to execute this.

[0239] Figure 17 A flowchart illustrating a method 1700 for indicating a predicted TCI state, exemplified by various aspects of this disclosure, is shown. Operation of method 1700 may be implemented by a UE or its components as described herein. For example, operation of method 1700 may be performed by, as referenced... Figures 1 to 11 The described UE 115 is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the wireless UE to perform the described function. Additionally or alternatively, the wireless UE can use dedicated hardware to perform aspects of the described function.

[0240] At 1705, the method may include: receiving a first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state. The operation of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1705 may be provided by reference to [reference needed]. Figure 10 The TCI Activation Manager 1025 described is used to perform this.

[0241] At 1710, the method may include: receiving an indication of a time offset between a first end time of a first time-domain window and a second end time of a second time-domain window, wherein the expiration of the first time-domain window is based on the time offset. The operation of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1710 may be derived from references... Figure 10 The described time-domain window manager 1040 is used to execute this.

[0242] At 1715, the method may include: receiving a second control signal that triggers the activation of a first TCI state for communication during a first time-domain window based on a first control signal. The operation of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1715 may be provided by reference to [reference needed]. Figure 10 The TCI Switching Manager 1030 described herein is used to execute this.

[0243] At 1720, the method may include: switching to a second TCI state for communication during a second time-domain window based on a first control signal and the expiration of a first time-domain window, according to a second control signal. The operation of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1720 may be provided by reference to [reference needed]. Figure 10 The TCI communication manager 1035 described is used to execute this.

[0244] Figure 18 A flowchart illustrating a method 1800 for indicating a predicted TCI state, illustrative of various aspects of this disclosure, is shown. Operation of method 1800 may be implemented by a UE or its components as described herein. For example, operation of method 1800 may be performed by, as referenced... Figures 1 to 11 The described UE 115 is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the wireless UE to perform the described function. Additionally or alternatively, the wireless UE can use dedicated hardware to perform aspects of the described function.

[0245] At 1805, the method may include: receiving a first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state. The operation of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1805 may be provided by reference to [reference needed]. Figure 10 The TCI Activation Manager 1025 described is used to perform this.

[0246] At 1810, the method may include: receiving an indication of a set of multiple time-domain windows, including a first time-domain window and a second time-domain window, wherein the last time-domain window in the set of multiple time-domain windows is associated with an undefined end point. The operation of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1810 may be provided by reference to [reference needed]. Figure 10 The described time-domain window manager 1040 is used to execute this.

[0247] At 1815, the method may include: receiving a second control signal that triggers the activation of a first TCI state for communication during a first time-domain window based on a first control signal. The operation of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1815 may be provided by reference to [reference needed]. Figure 10 The TCI Switching Manager 1030 described herein is used to execute this.

[0248] At 1820, the method may include: switching to a second TCI state for communication during a second time-domain window based on a first control signal and the expiration of a first time-domain window, according to a second control signal. The operation of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1820 may be provided by reference to [reference needed]. Figure 10 The TCI communication manager 1035 described is used to execute this.

[0249] Figure 19 A flowchart illustrating a method 1900 for predicting TCI status, supported by various aspects of this disclosure, is shown. The operation of method 1900 can be implemented by a network entity or its components as described herein. For example, the operation of method 1900 can be implemented by, as referenced... Figures 1 to 7 as well as Figures 12 to 15 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the wireless network entity to perform the described function. Additionally or alternatively, the wireless network entity may use dedicated hardware to perform aspects of the described function.

[0250] At 1905, the method may include: sending a first control signal to the UE, the first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state. The operation at 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1905 may be provided by reference to [reference needed]. Figure 14 The TCI Activation Manager 1425 described is used to perform this.

[0251] At 1910, the method may include: sending a second control signal to the UE, the second control signal triggering the activation of a first TCI state for communication during a first time-domain window based on the first control signal. The operation of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1910 may be derived from references... Figure 14 The TCI Switch Manager 1430 described herein is used to perform this action.

[0252] At point 1915, the method may include: communicating with the UE using a second TCI state during a second time-domain window based on a first control signal and the expiration of a first time-domain window, according to a second control signal. The operation at point 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at point 1915 may be derived from references... Figure 14 The TCI Communication Manager 1435 described is used to execute this.

[0253] Figure 20A flowchart illustrating a method 2000 for predicting TCI status, supported by various aspects of this disclosure, is shown. The operation of method 2000 can be implemented by a network entity or its components as described herein. For example, the operation of method 2000 can be implemented by, as referenced... Figures 1 to 7 as well as Figures 12 to 15 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the wireless network entity to perform the described function. Additionally or alternatively, the wireless network entity may use dedicated hardware to perform aspects of the described function.

[0254] At 2005, the method may include: sending a first control signal to the UE, the first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state. Operation of 2005 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2005 may be provided by reference to [reference needed]. Figure 14 The TCI Activation Manager 1425 described is used to perform this.

[0255] At 2010, the method may include: sending a third control signal before a second time-domain window, the third control signal triggering activation of an updated TCI state during the second time-domain window. The operation of 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2010 may be derived from references... Figure 14 The TCI state overwrite manager 1455 described is used to perform this.

[0256] At 2015, the method may include: overwriting a switch to a second TCI state during a second time-domain window based on a third control signal and switching to the updated TCI state. The operation of 2015 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2015 may be provided by reference to [reference needed]. Figure 14 The TCI state overwrite manager 1455 described is used to perform this.

[0257] At 2020, the method may include: sending a second control signal to the UE, the second control signal triggering the activation of a first TCI state for communication during a first time-domain window based on a first control signal. The operation of 2020 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2020 may be provided by reference to [reference needed]. Figure 14 The TCI Switch Manager 1430 described herein is used to perform this action.

[0258] At 2025, the method may include: communicating with the UE using a second TCI state during a second time-domain window based on a first control signal and the expiration of a first time-domain window, according to a second control signal. Operation of 2025 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2025 may be provided by reference to... Figure 14 The TCI Communication Manager 1435 described is used to execute this.

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

[0260] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state; receiving a second control signal triggering activation of the first TCI state for communication during the first time-domain window based at least in part on the first control signal; and switching to the second TCI state for communication during the second time-domain window based at least in part on the first control signal and the expiration of the first time-domain window, according to the second control signal.

[0261] Aspect 2: According to the method of aspect 1, receiving the first control signal includes: receiving an indication of a time offset between a first end time of the first time domain window and a second end time of the second time domain window, wherein the expiration of the first time domain window is at least partially based on the time offset.

[0262] Aspect 3: According to the method of aspect 2, receiving the first control signal includes: receiving an RRC signal that semi-statically defines the time offset between the first time domain window and the second time domain window.

[0263] Aspect 4: The method of claim 2, wherein receiving the first control signal comprises: receiving a DCI that dynamically defines the time offset between the first time-domain window and the second time-domain window.

[0264] Aspect 5: The method according to any one of Aspects 1 to 4, wherein receiving the first control signal comprises: receiving an indication of a plurality of second time-domain windows, wherein the second time-domain window is one of the plurality of second time-domain windows, wherein each of the plurality of second time-domain windows is associated with a corresponding predicted TCI state, wherein the last time-domain window in sequence among the plurality of second time-domain windows is associated with an undefined end point.

[0265] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the duration of the second time-domain window is based on the duration of the first time-domain window according to a defined ratio.

[0266] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the first time-domain window and the second time-domain window are equal in duration.

[0267] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the first time-domain window and the second time-domain window are not equal in duration.

[0268] Aspect 9: The method according to any one of Aspects 1 to 8, the method further comprising: receiving one or more TCI status code points via the first control signal, each TCI status code point identifying a predicted TCI status set during a corresponding second time-domain window set, the predicted TCI status set being based at least in part on the second TCI state; and receiving TCI status code points from the one or more TCI status code points via the second control signal, wherein switching to the second TCI state is based at least in part on receiving the TCI status code points.

[0269] Aspect 10: The method according to aspect 9, the method further comprising: receiving, via the first control signal, an indication of the number of predicted TCI states for each of the one or more TCI status code points.

[0270] Aspect 11: The method according to any one of Aspects 9 to 10, wherein each of the one or more TCI status code points includes a common number of predicted TCI states.

[0271] Aspect 12: The method according to any one of aspects 9 to 11, the method further comprising: receiving, via the second control signal, an indication of the duration of a time-domain window for each predicted TCI state in the set of predicted TCI states for each of the one or more TCI state code points, wherein the second time-domain window is at least partially based on the duration.

[0272] Aspect 13: In the method according to any one of Aspects 9 to 12, each time-domain window of each predicted TCI state in the predicted TCI state set has an equal duration, wherein the second time-domain window includes the equal duration.

[0273] Aspect 14: The method according to any one of Aspects 1 to 13, the method further comprising: receiving the first control signal via a group common MAC-CE, wherein the UE belongs to a UE group associated with the group common MAC-CE.

[0274] Aspect 15: The method according to any one of Aspects 1 to 14, the method further comprising: receiving the second control signal via a group common DCI, wherein the UE belongs to a UE group associated with the group common DCI.

[0275] Aspect 16: According to the method of aspect 15, wherein the first control signal indicates that the UE belongs to the UE group.

[0276] Aspect 17: The method according to any one of aspects 1 to 16, the method further comprising: receiving the second control signal via a UE-specific DCI.

[0277] Aspect 18: The method according to any one of Aspects 1 to 17, the method further comprising: receiving a third control signal before the second time-domain window, the third control signal triggering the activation of an updated TCI state during the second time-domain window; and overwriting a switch to the second TCI state during the second time-domain window and switching to the updated TCI state based at least in part on the third control signal.

[0278] Aspect 19: A method for wireless communication at a network entity, the method comprising: sending a first control signal to a UE, the first control signal indicating a first TCI state for a first time-domain window and a second TCI state for a second time-domain window following the first time-domain window, the second TCI state including a predicted TCI state; sending a second control signal to the UE, the second control signal triggering activation of the first TCI state for communication during the first time-domain window based at least in part on the first control signal; and communicating with the UE using the second TCI state during the second time-domain window based at least in part on the first control signal and the expiration of the first time-domain window, according to the second control signal.

[0279] Aspect 20: According to the method of aspect 19, sending the first control signal includes: sending an indication of a time offset between a first end time of the first time domain window and a second end time of the second time domain window, wherein the expiration of the first time domain window is at least partially based on the time offset.

[0280] Aspect 21: According to the method of aspect 20, sending the first control signal includes: sending an RRC signal that semi-statically defines the time offset between the first time domain window and the second time domain window.

[0281] Aspect 22: The method of claim 20, wherein sending the first control signal comprises: sending a DCI that dynamically defines the time offset between the first time-domain window and the second time-domain window.

[0282] Aspect 23: The method according to any one of Aspects 19 to 22, wherein sending the first control signal comprises: sending an indication to a plurality of second time-domain windows, wherein the second time-domain window is one of the plurality of second time-domain windows, wherein each of the plurality of second time-domain windows is associated with a corresponding predicted TCI state, wherein the last time-domain window in sequence among the plurality of second time-domain windows is associated with an undefined end point.

[0283] Aspect 24: The method according to any one of aspects 19 to 23, wherein the duration of the second time-domain window is based on the duration of the first time-domain window according to a defined ratio.

[0284] Aspect 25: The method according to any one of aspects 19 to 24, wherein the first time-domain window and the second time-domain window are equal in duration.

[0285] Aspect 26: The method according to any one of aspects 19 to 25, wherein the first time-domain window and the second time-domain window are not equal in duration.

[0286] Aspect 27: The method according to any one of Aspects 19 to 26, the method further comprising: transmitting one or more TCI status code points via the first control signal, each TCI status code point identifying a predicted TCI status set during a corresponding second time-domain window set, the predicted TCI status set being based at least in part on the second TCI status; and transmitting TCI status code points from the one or more TCI status code points via the second control signal, wherein using the second TCI status to communicate with the UE is based at least in part on transmitting the TCI status code points.

[0287] Aspect 28: The method according to aspect 27, the method further comprising: sending an indication of the number of predicted TCI states for each of the one or more TCI status code points via the first control signal.

[0288] Aspect 29: The method according to any one of Aspects 27 to 28, wherein each of the one or more TCI status code points includes a common number of predicted TCI states.

[0289] Aspect 30: The method according to any one of aspects 27 to 29, the method further comprising: sending, via the second control signal, an indication of the duration of a time-domain window for each predicted TCI state in the set of predicted TCI states for each of the one or more TCI state code points, wherein the second time-domain window is at least partially based on the duration.

[0290] Aspect 31: In the method according to any one of Aspects 27 to 30, each time-domain window of each predicted TCI state in the predicted TCI state set has an equal duration, wherein the second time-domain window includes the equal duration.

[0291] Aspect 32: The method according to any one of aspects 19 to 31, the method further comprising: transmitting the first control signal via a group common MAC-CE, wherein the UE belongs to a UE group associated with the group common MAC-CE.

[0292] Aspect 33: The method according to any one of aspects 19 to 32, the method further comprising: transmitting the second control signal via a group common DCI, wherein the UE belongs to a Ue group associated with the group common DCI.

[0293] Aspect 34: According to the method of aspect 33, wherein the first control signal indicates that the UE belongs to the Ue group.

[0294] Aspect 35: The method according to any one of aspects 19 to 34, the method further comprising: transmitting the second control signal via a UE-specific DCI.

[0295] Aspect 36: The method according to any one of aspects 19 to 35, the method further comprising: sending a third control signal before the second time-domain window, the third control signal triggering the activation of an updated TCI state during the second time-domain window; and overwriting a switch to the second TCI state and switching to the updated TCI state during the second time-domain window based at least in part on the third control signal.

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

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

[0298] Aspect 39: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by a processor to perform the method according to any one of aspects 1 to 18.

[0299] Aspect 40: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of aspects 19 to 36.

[0300] Aspect 41: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing the method according to any one of aspects 19 to 36.

[0301] Aspect 42: A non-transitory computer-readable medium storing code for wireless communication at a network entity, said code including instructions executable by a processor to perform the method according to any one of aspects 19 to 36.

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

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

[0304] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

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

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

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

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

[0309] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0310] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0311] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

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

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; A memory coupled to the processor; and Instructions, which are stored in the memory and can be executed by the processor, to cause the device to: Receive a first control signal, the first control signal indicating a first transmit configuration indicator (TCI) state for a first time domain window and a second TCI state for a second time domain window following the first time domain window, the second TCI state including a predicted TCI state; Receive a second control signal, the second control signal triggering the activation of the first TCI state for communication during the first time-domain window, at least in part based on the first control signal; as well as The second control signal is used to switch to the second TCI state for communication during the second time domain window, based at least in part on the first control signal and the expiration of the first time domain window.

2. The apparatus of claim 1, wherein the instruction for receiving the first control signal is executable by the processor to cause the apparatus to: Receive an indication of a time offset between a first end time of the first time domain window and a second end time of the second time domain window, wherein the expiration of the first time domain window is at least partially based on the time offset.

3. The apparatus of claim 2, wherein the instruction for receiving the first control signal is executable by the processor to cause the apparatus to: Receive a Radio Resource Control (RRC) signal that semi-statically defines the time offset between the first time-domain window and the second time-domain window.

4. The apparatus of claim 2, wherein the instruction for receiving the first control signal is executable by the processor to cause the apparatus to: Receive downlink control information that dynamically defines the time offset between the first time domain window and the second time domain window.

5. The apparatus of claim 1, wherein the instruction for receiving the first control signal is executable by the processor to cause the apparatus to: Receive an instruction for a plurality of second time-domain windows, wherein the second time-domain window is one of the plurality of second time-domain windows, wherein each of the plurality of second time-domain windows is associated with a corresponding predicted TCI state, and wherein the last time-domain window in sequence among the plurality of second time-domain windows is associated with an undefined end point.

6. The apparatus of claim 1, wherein the duration of the second time-domain window is based on the duration of the first time-domain window according to a defined ratio.

7. The apparatus of claim 1, wherein the first time-domain window and the second time-domain window are equal in duration.

8. The apparatus of claim 1, wherein the first time-domain window and the second time-domain window are not equal in duration.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: One or more TCI status code points are received via the first control signal, each TCI status code point identifying a set of predicted TCI states during a corresponding second time-domain window set, the set of predicted TCI states being at least partially based on the second TCI states; and TCI status code points are received from the one or more TCI status code points via the second control signal, wherein switching to the second TCI state is based at least in part on receiving the TCI status code points.

10. The apparatus of claim 9, wherein the instructions are further executable by the processor to cause the apparatus to: The first control signal is used to receive an indication of the number of predicted TCI states for each of the one or more TCI state code points.

11. The apparatus of claim 9, wherein each of the one or more TCI status code points includes a common number of predicted TCI states.

12. The apparatus of claim 9, wherein the instructions are further executable by the processor to cause the apparatus to: The second control signal is received for each of the one or more TCI status code points to indicate the duration of a time-domain window for each predicted TCI state in the set of predicted TCI states, wherein the second time-domain window is at least partially based on the duration.

13. The apparatus of claim 9, wherein the second time-domain window comprises an equal duration.

14. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The first control signal is received via a group common media access control-control element (MAC-CE), wherein the UE belongs to a Ue group associated with the group common MAC-CE.

15. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The second control signal is received via Group Common Downlink Control Information (DCI), wherein the UE belongs to a Ue group associated with the Group Common DCI.

16. The apparatus of claim 15, wherein the first control signal indicates that the UE belongs to the UE group.

17. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The second control signal is received via UE-specific downlink control information (DCI).

18. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A third control signal is received before the second time-domain window, the third control signal triggering the activation of an updated TCI state during the second time-domain window; and The switching to the second TCI state is overwritten during the second time-domain window and switched to the updated TCI state, at least in part based on the third control signal.

19. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; A memory coupled to the processor; and Instructions, which are stored in the memory and can be executed by the processor, to cause the device to: Send a first control signal to the user equipment (UE), the first control signal indicating a first transmission configuration indicator (TCI) state for a first time domain window and a second TCI state for a second time domain window following the first time domain window, the second TCI state including a predicted TCI state; A second control signal is sent to the UE, the second control signal triggering the activation of the first TCI state for communication during the first time-domain window, at least in part based on the first control signal; as well as The second control signal is used to communicate with the UE during the second time domain window, based at least in part on the first control signal and the expiration of the first time domain window.

20. The apparatus of claim 19, wherein the instruction for sending the first control signal is executable by the processor to cause the apparatus to: Send an indication of the time offset between a first end time of the first time domain window and a second end time of the second time domain window, wherein the expiration of the first time domain window is at least partially based on the time offset.

21. The apparatus of claim 20, wherein the instruction for sending the first control signal is executable by the processor to cause the apparatus to: Transmit a radio resource control (RRC) signal that semi-statically defines the time offset between the first time-domain window and the second time-domain window.

22. The apparatus of claim 20, wherein the instruction for sending the first control signal is executable by the processor to cause the apparatus to: Send downlink control information that dynamically defines the time offset between the first time domain window and the second time domain window.

23. The apparatus of claim 19, wherein the instruction for sending the first control signal is executable by the processor to cause the apparatus to: Sending instructions for a plurality of second time-domain windows, wherein the second time-domain window is one of the plurality of second time-domain windows, wherein each of the plurality of second time-domain windows is associated with a corresponding second TCI state, wherein the last time-domain window in sequence among the plurality of second time-domain windows is associated with an undefined end point.

24. The apparatus of claim 19, wherein the duration of the second time-domain window is based on the duration of the first time-domain window according to a defined ratio.

25. The apparatus of claim 19, wherein the first time-domain window and the second time-domain window are equal in duration.

26. The apparatus of claim 19, wherein the first time-domain window and the second time-domain window are not equal in duration.

27. The apparatus of claim 19, wherein the instructions are further executable by the processor to cause the apparatus to: One or more TCI status code points are transmitted via the first control signal, each TCI status code point identifying a set of predicted TCI states during a corresponding second time-domain window set, the set of predicted TCI states being at least partially based on the second TCI states; and TCI status code points from the one or more TCI status code points are transmitted via the second control signal, wherein communication with the UE using the second TCI status is based at least in part on transmitting the TCI status code points.

28. The apparatus of claim 27, wherein the instructions are further executable by the processor to cause the apparatus to: The first control signal sends an indication of the number of predicted TCI states for each of the one or more TCI state code points.

29. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive a first control signal, the first control signal indicating a first transmit configuration indicator (TCI) state for a first time domain window and a second TCI state for a second time domain window following the first time domain window, the second TCI state including a predicted TCI state; Receive a second control signal, the second control signal triggering the activation of the first TCI state for communication during the first time-domain window, at least in part based on the first control signal; as well as The second control signal is used to switch to the second TCI state for communication during the second time domain window, based at least in part on the first control signal and the expiration of the first time domain window.

30. A method for conducting wireless communication at a network entity, the method comprising: Send a first control signal to the user equipment (UE), the first control signal indicating a first transmission configuration indicator (TCI) state for a first time domain window and a second TCI state for a second time domain window following the first time domain window, the second TCI state including a predicted TCI state; A second control signal is sent to the UE, the second control signal triggering the activation of the first TCI state for communication during the first time-domain window, at least in part based on the first control signal; as well as The second control signal is used to communicate with the UE during the second time domain window, based at least in part on the first control signal and the expiration of the first time domain window.

Images