Per resource element energy offset indication for beam prediction

Abstract

Methods, systems, and devices for wireless communication are described. The described techniques enable a user equipment (UE) to identify energy per resource element (EPRE) offsets associated with channel resources and reference signals sharing an active transmit configuration indicator (TCI) state. In some cases, the UE may use an EPRE offset to confirm whether the difference between predicted channel characteristics and measured channel characteristics is due to inaccuracy at the UE or adjustment at the network entity, thereby improving the input quality of an artificial intelligence (AI) or machine learning (ML) model. In some cases, a UE may identify an EPRE offset according to a predefined value, a signal from a network entity indicating one or more EPRE offsets, a response to a request for an EPRE offset from the UE, or any combination thereof.

Description

Technical Field

[0001] The following relates to wireless communication, including per-resource-element energy offset indication for beam prediction. Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems 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 of communication devices, which may be referred to as User Equipment (UE).

[0003] In some wireless communication systems, wireless devices can use performance monitoring techniques to manage one or more communication beams (e.g., transmit and receive beams). In some cases, wireless devices can compare predicted measurements of the beams with actual measurements of the beams to monitor the accuracy of the wireless device's predictions. Summary of the Invention

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting per-resource element energy (EPRE) offset indication for beam prediction. For example, the described techniques enable user equipment (UE) to identify EPRE offsets associated with channel resources and reference signals sharing an Active Transmit Configuration Indicator (TCI) state. In some cases, the UE can use the EPRE offset to determine whether the difference between predicted channel characteristics (e.g., predicted Layer 1 Reference Signal Received Power (L1-RSRP)) and measured channel characteristics (e.g., measured L1-RSRP) is due to inaccuracies at the UE or adjustments at network entities, thereby improving the input quality of artificial intelligence (AI) or machine learning (ML) models. In some cases, the UE may identify the EPRE offset based on predefined values, signals from network entities indicating one or more EPRE offsets, responses to requests for EPRE offsets from the UE, or any combination thereof. Additionally or alternatively, the UE may identify a corresponding offset for each transmit and receive point (TRP) associated with the UE.

[0005] A method for wireless communication by a user equipment (UE) is described. The method may include: predicting a first channel characteristic associated with channel resources; receiving a reference signal via a downlink channel, wherein the channel resources and the reference signal are associated with a first transmit configuration indicator (TCI) state; measuring a second channel characteristic associated with the reference signal; and verifying the prediction accuracy of the UE based on the first channel characteristic, the second channel characteristic, and the EPRE offset between the channel resources and the reference signal.

[0006] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the memories. The processors are capable of operating individually or jointly to execute the code so that the UE: predicts a first channel characteristic associated with channel resources; receives a reference signal via a downlink channel, wherein the channel resources and the reference signal are associated with a first TCI state; measures a second channel characteristic associated with the reference signal; and verifies the prediction accuracy of the UE based on the first channel characteristic, the second channel characteristic, and the EPRE offset between the channel resources and the reference signal.

[0007] Another UE for wireless communication is described. The UE may include: components for predicting a first channel characteristic associated with channel resources; components for receiving a reference signal via a downlink channel, wherein the channel resources and the reference signal are associated with a first TCI state; components for measuring a second channel characteristic associated with the reference signal; and components for verifying the prediction accuracy of the UE based on the first channel characteristic, the second channel characteristic, and the EPRE offset between the channel resources and the reference signal.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: predict a first channel characteristic associated with channel resources; receive a reference signal via a downlink channel, wherein the channel resources and the reference signal are associated with a first TCI state; measure a second channel characteristic associated with the reference signal; and verify the prediction accuracy of the UE based on the first channel characteristic, the second channel characteristic, and the EPRE offset between the channel resources and the reference signal.

[0009] In the methods described herein, and in some examples of UEs and nontransitory computer-readable media, the EPRE offset may be associated with the type of channel resource, the type of downlink channel, a first waveform associated with a reference signal, a second waveform associated with the channel resource, or any combination thereof.

[0010] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for determining an EPRE offset from a set of multiple potential EPRE offsets based on whether a signal indicating an EPRE offset can be received from a network entity.

[0011] The methods described herein, examples of UEs and nontransitory computer-readable media may also include operations, features, components or instructions for receiving a message indicating one or more EPRE offsets, including at least an EPRE offset, wherein the message includes a Radio Resource Control (RRC) message, a Media Access Control Control Element (MAC-CE), a Downlink Control Information (DCI) message or any combination thereof.

[0012] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, EPRE offsets may be associated with a set of multiple types of channel resources, a set of multiple types of downlink channels, a set of multiple waveforms associated with a reference signal, a set of multiple waveforms associated with channel resources, or any combination thereof, based on the number of one or more EPRE offsets indicated in the message.

[0013] In the methods described herein, in some examples of UEs and nontransitory computer-readable media, each of one or more EPRE offsets may be associated with a set of multiple types of channel resources, a set of multiple types of downlink channels, a set of multiple waveforms associated with a reference signal, or a corresponding combination of a set of multiple waveforms associated with channel resources.

[0014] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, the message includes a resource identifier that can be associated with channel resources.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, one or more EPRE offsets comprise a subset of a set of multiple EPRE offsets, and the message selects one or more EPRE offsets downward from the set of multiple EPRE offsets.

[0016] In the methods described herein, and in some examples of UEs and non-transitory computer-readable media, the EPRE offset is overwritten based on the receipt of the message to override the default EPRE offset.

[0017] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving a downlink-granted DCI message indicating an EPRE offset and including scheduling downlink transmission, wherein a reference signal may be associated with the downlink transmission.

[0018] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving an RRC message indicating a configuration for semi-persistent scheduling downlink transmission and including at least one or more EPRE offsets, wherein a reference signal may be associated with semi-persistent scheduling downlink transmission.

[0019] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving a DCI message that includes a trigger for semi-persistent scheduling of downlink transmission and indicates an EPRE offset, wherein the DCI message selects an EPRE offset downward from one or more EPRE offsets.

[0020] In the methods described herein, in some examples of UEs and nontransitory computer-readable media, the EPRE offset may be one of a group of EPRE offsets that can be associated with a reference signal and the corresponding transmit and receive points.

[0021] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for: sending a request for an EPRE offset; and receiving an EPRE offset in response to the request, wherein verification of the UE's prediction accuracy may be based on the received EPRE offset.

[0022] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, the request indicates channel resources.

[0023] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, the request includes RRC messages, MAC-CE, uplink control information messages, scheduling requests, or any combination thereof.

[0024] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, verifying the prediction accuracy of the UE may include operations, features, components, or instructions for: comparing a first channel characteristic and a second channel characteristic to identify a first value corresponding to the difference between the first channel characteristic and the second channel characteristic; and verifying the prediction accuracy of the UE based on the first value and the EPRE offset.

[0025] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first channel characteristic and the second channel characteristic include at least one of L1-RSRP or L1-SINR.

[0026] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, channel resources include synchronization signal blocks (SSBs), channel state information reference signals (CSI-RS), virtual resources, or any combination thereof.

[0027] In the methods described herein, in some examples of UEs and nontransitory computer-readable media, reference signals and channel resources may be quasi-co-located according to enhanced Type D quasi-co-location (QCL) or Type E QCL.

[0028] A method for wireless communication by a network entity is described. The method may include: transmitting a reference signal to a UE via a downlink channel, wherein the reference signal is associated with a first TCI state; and transmitting to the UE a message indicating an EPRE offset between the reference signal and channel resources associated with the first TCI state, wherein the EPRE offset indicates input at the UE to a process used to verify the prediction accuracy of the UE.

[0029] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the memories. The processors are capable of operating individually or jointly to execute the code so that the network entity: transmits a reference signal to a UE via a downlink channel, wherein the reference signal is associated with a first TCI state; and transmits a message to the UE indicating an EPRE offset between the reference signal and channel resources associated with the first TCI state, wherein the EPRE offset indicates input at the UE to a process used to verify the prediction accuracy of the UE.

[0030] Another network entity for wireless communication is described. This network entity may include: components for transmitting a reference signal to a UE via a downlink channel, wherein the reference signal is associated with a first TCI state; and components for transmitting to the UE a message indicating an EPRE offset between the reference signal and channel resources associated with the first TCI state, wherein the EPRE offset indicates input at the UE to a process used to verify the prediction accuracy of the UE.

[0031] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: transmit a reference signal to a UE via a downlink channel, wherein the reference signal is associated with a first TCI state; and transmit to the UE a message indicating an EPRE offset between the reference signal and a channel resource associated with the first TCI state, wherein the EPRE offset indicates input at the UE to a process for verifying the prediction accuracy of the UE.

[0032] In some examples of the methods, network entities, and nontransient computer-readable media described herein, the EPRE offset may be associated with the type of channel resource, the type of downlink channel, a first waveform associated with a reference signal, a second waveform associated with the channel resource, or any combination thereof.

[0033] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the message includes RRC messages, MAC-CE, DCI messages, or any combination thereof.

[0034] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting a downlink-granted DCI message that indicates the EPRE offset and includes scheduling downlink transmission, wherein a reference signal may be associated with the downlink transmission.

[0035] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting an RRC message indicating a configuration for semi-persistent scheduling downlink transmission and including at least one or more EPRE offsets, wherein a reference signal may be associated with semi-persistent scheduling downlink transmission.

[0036] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting a message comprising an EPRE offset group, wherein the EPRE offset group comprises at least an EPRE offset and a second EPRE offset, and wherein the EPRE offset may be associated with a first transmission and reception point at the UE, and the second EPRE offset may be associated with a second transmission and reception point at the UE.

[0037] The methods, network entities, and some examples of non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a request for an EPRE offset, wherein sending the message may be based on receiving the request.

[0038] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, channel resources include SSBs, CSI-RSs, virtual resources, or any combination thereof. Attached Figure Description

[0039] Figure 1 An example of a wireless communication system supporting per-resource element energy (EPRE) offset indication for beam prediction is shown, according to one or more aspects of this disclosure.

[0040] Figure 2An example of a wireless communication system supporting EPRE offset indication for beam prediction according to one or more aspects of this disclosure is shown.

[0041] Figure 3 An example of a signaling diagram supporting EPRE offset indication for beam prediction, according to one or more aspects of this disclosure, is shown.

[0042] Figure 4 An example of a process flow supporting EPRE offset indication for beam prediction, according to one or more aspects of this disclosure, is shown.

[0043] Figure 5 and Figure 6 A block diagram of an apparatus for supporting EPRE offset indication for beam prediction, according to one or more aspects of this disclosure, is shown.

[0044] Figure 7 A block diagram of a communication manager supporting EPRE offset indication for beam prediction, according to one or more aspects of this disclosure, is shown.

[0045] Figure 8 A diagram of a system including an EPRE offset indicator for beam prediction, according to one or more aspects of this disclosure, is shown.

[0046] Figure 9 and Figure 10 A block diagram of an apparatus for supporting EPRE offset indication for beam prediction, according to one or more aspects of this disclosure, is shown.

[0047] Figure 11 A block diagram of a communication manager supporting EPRE offset indication for beam prediction, according to one or more aspects of this disclosure, is shown.

[0048] Figure 12 A diagram of a system including an EPRE offset indicator for beam prediction, according to one or more aspects of this disclosure, is shown.

[0049] Figure 13 and Figure 14 A flowchart illustrating a method for supporting EPRE offset indication for beam prediction according to one or more aspects of this disclosure is shown. Detailed Implementation

[0050] In some wireless communication systems, wireless devices (e.g., user equipment (UE) or network entities) can use beamforming communication to communicate. For example, a transmitting wireless device can transmit signals via a transmit beam, and a receiving wireless device can receive signals via a corresponding receive beam. In some cases, wireless devices can use one or more beam management techniques to select the beam used for communication, which can be enhanced using artificial intelligence (AI) or machine learning (ML) models. For example, a UE can perform UE-side channel prediction by predicting a first channel characteristic of a channel resource (e.g., a synchronization signal block (SSB), channel state information reference signal (CSI-RS), virtual resources, or any combination thereof) and measuring a second channel characteristic of a received reference signal (e.g., a demodulation reference signal (DMRS)). In some cases, if the channel resource and the reference signal share an active transmit configuration indicator (TCI) state (e.g., associated with a similar beam), the UE can compare the first and second channel characteristics to verify the accuracy of the prediction. For example, if the values ​​of the first and second channel characteristics are relatively close, the UE can input the prediction into an AI or ML model, indicating that the prediction is relatively accurate.

[0051] In some examples, network entities may adjust the transmit power used to transmit reference signals, such as by reducing the transmit power of nearby UEs. However, a UE using such a reference signal to verify prediction accuracy may not be aware of the adjusted transmit power and may not adjust its prediction accuracy criterion accordingly. For example, a UE may identify that the measured channel characteristics are significantly different from the predicted channel characteristics and may input inaccurate predictions into an AI or ML model, even though the difference is due to adjustments at the network entity (e.g., not incorrect predictions).

[0052] To support prediction accuracy verification, the UE can identify the Energy Per Resource Element (EPRE) offset associated with channel resources and reference signals sharing an active TCI state. In some cases, the UE can use the EPRE offset to determine whether the difference between predicted channel characteristics (e.g., predicted Layer 1 Reference Signal Received Power (L1-RSRP) or L1 Signal-to-Interference-plus-Noise Ratio (L1-SINR)) and measured channel characteristics (e.g., measured L1-RSRP) is due to inaccuracies at the UE or adjustments at network entities, thereby improving the input quality of AI or ML models. In some cases, the UE can identify the EPRE offset based on predefined values ​​(e.g., default offset, predefined offsets for one or more combinations of channel resources and reference signals, or both), signals from network entities indicating one or more EPRE offsets, responses to requests for EPRE offsets from the UE, or any combination thereof. Additionally or alternatively, the UE can identify the offset per transmit and receive point (TRP) associated with the UE.

[0053] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are further illustrated by signaling diagrams and process flows, and described with reference to these diagrams. The aspects of this disclosure are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to EPRE offset indication for beam prediction, and described with reference to these diagrams.

[0054] Figure 1 An example of a wireless communication system 100 supporting EPRE offset indication for beam prediction according to one or more aspects of this disclosure is shown. 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.

[0055] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having 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, etc. 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).

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

[0057] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), 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. Furthermore, 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.

[0058] In some examples, network entity 105 may communicate with core network 130, communicate 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 entities 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 entities 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.

[0059] 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 evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

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

[0061] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities 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)) functionalities 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, a protocol stack functional split 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) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 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 communicating via such communication links.

[0062] In a wireless communication system (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.

[0063] 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 EPRE offset indication for beam prediction as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may 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).

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

[0065] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, 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.

[0066] 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 having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the 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 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers 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’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0067] 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 modulation scheme order 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 may increase the data rate or data integrity used for communication with UE 115.

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

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

[0070] A subframe, time slot, micro-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)).

[0071] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for 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.

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

[0073] 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 prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

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

[0075] 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 a combination of these. Vehicles may signal 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.

[0076] 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), which 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 manages 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 delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity 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.

[0077] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band 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).

[0078] Wireless communication system 100 may utilize both 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 with unlicensed RF spectrum, 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 with licensed frequency bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

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

[0080] 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), for which multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

[0081] 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 along a specific orientation 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 specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0082] 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 along 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.

[0083] 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 the 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 along 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.

[0084] 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) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

[0085] 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 transmitting 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 (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array; 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).

[0086] 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 can perform packet segmentation and reassembly for transmission via logical channels. The MAC layer can perform priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer can provide 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 can map transport channels to physical channels.

[0087] UE 115 can perform beam management to access, maintain, and recover beams used for communication within the wireless communication system 100. For example, UE 115 can perform beam management for obstruction due to changing environments (e.g., changes in UE 115's mobility, obstruction, and orientation). Beam management can be defined as a set of L1 (e.g., physical layer) and L2 (e.g., media access control) procedures to acquire and maintain a set of beam-pair links (e.g., beams used at one or more network-side TRPs) paired with the beams used at UE 115.

[0088] When UE 115 transitions out of an RRC idle or RRC inactive state (e.g., where UE 115 is still receiving tracking reference signaling) and performs an initial access procedure, the beam management procedure can begin. The initial access procedure may include beam scanning (e.g., SSB transmission and reception) and contention-based random access, where UE 115 transitions to an RRC connected state. UE 115 can then perform beam measurements and reporting to select candidate beams, and may then perform one or more beam management procedures. Some possible beam management procedures may include P1 / P2 / P3 (e.g., SSB / CSI-RS tracking) procedures, U1 / U2 / U3 (e.g., SRS tracking) procedures, L1-RSRP reporting, TCI status configuration indication, L1-SINR reporting, overhead and latency reduction techniques (such as component carrier group beam updates and enhanced uplink beam updates), unified TCI status implementation, L1 / L2 center mobility, dynamic TCI status updates, uplink multi-panel selection, maximum permissible exposure mitigation, beam management latency reduction, high-speed and single-frequency network implementation, multi-TRP beam management, AI-based and machine learning-based beam management, and other beam management procedures.

[0089] In some examples, UE 115 can perform measurements during beam management to detect potential beam failures and initiate beam recovery. For instance, UE 115 can perform various beam failure recovery techniques, such as beam failure detection and recovery for PCell and PSCell, beam failure detection via beam failure detection reference signal and PDCCH block error rate, beam failure detection based on contention-free random access, link recovery request via scheduling request, and MAC-CE based beam failure recovery, AI-based and machine learning-based beam failure recovery techniques, and other beam failure recovery procedures. In some examples, if beam failure recovery fails, UE 115 can support radio link failure recovery to re-establish active connectivity with the network.

[0090] In some cases, UE 115 can support AI- or ML-based beam management for specific air interface implementations. For example, UE 115 can leverage machine learning and artificial intelligence techniques to perform beam prediction in the time domain, spatial domain, or both, which can reduce signaling overhead and latency, and improve beam selection accuracy. In some examples, AI and machine learning models can be trained, deployed, inferred, monitored, and updated by the network based on quality of service or other network requirements. In some examples, network entity 105 can configure one or more sets of beams to be measured (e.g., as a reference set of beams) based on machine learning and AI-based models. In some other examples, network entity 105 can use machine learning and AI-based models to predict the set of “optimal” beams (e.g., beams with the highest relative signal strength) and can compare the predicted beams with the set of L1-RSRP measurements to efficiently identify and select the optimal beams.

[0091] In some cases, UE 115 can identify EPRE offsets associated with channel resources and reference signals sharing an active TCI state. In some cases, UE 115 can use EPRE offsets to determine whether the difference between predicted channel characteristics (e.g., predicted L1-RSRP or L1-SINR) and measured channel characteristics (e.g., measured L1-RSRP or L1-SINR) is due to inaccuracies at UE 115 or external factors (e.g., adjustments at network entity 105), thereby improving the input quality of AI or ML models. In some cases, UE 115 can identify EPRE offsets based on predefined values, signals from network entity 105 indicating one or more EPRE offsets, responses to requests for EPRE offsets from UE 115, or any combination thereof.

[0092] Figure 2An example of a wireless communication system 200 supporting EPRE offset indication for beam prediction according to one or more aspects of this disclosure is shown. Wireless communication system 200 may implement one or more aspects of wireless communication system 100. For example, wireless communication system 200 may include signaling between network entity 105-a and UE 115-a, which may be reference... Figure 1 Examples of corresponding devices described. In some cases, the wireless communication system 200 may support UE 115-a in verifying the accuracy of predicted channel characteristics based on the EPRE offset. In some cases, channel characteristics may be understood to include channel statistics.

[0093] In some cases, network entity 105-a and UE 115-a can communicate using beamforming communication. For example, network entity 105-a can use a transmit beam to transmit downlink communication and a receive beam to receive uplink communication, and UE 115-a can use a receive beam to receive downlink communication and a transmit beam to transmit uplink communication. To select a beam for such communication (e.g., from a set of candidate beams), network entity 105-a and UE 115-a can use AI or ML models to implement beam management techniques. For example, UE 115-a can predict the channel characteristics of channel resource 205 (e.g., L1-RSRP or L1-SINR), measure the actual channel characteristics after receiving reference signal 210 (e.g., DMRS), and input the prediction accuracy into the AI ​​or ML model (e.g., to improve subsequent beam selection accuracy). In some cases, channel resource 205 may be an SSB, CSI-RS, or virtual resource (e.g., a resource that is not actually sent by network entity 105-a, but is used as a prediction target by UE 115-a and referenced by UE 115-a when reporting resource ID, predicting channel characteristics, or both).

[0094] In some cases, channel resource 205 and reference signal 210 may share an active TCI state (e.g., using similar beams for transmission), which can allow UE 115-a to compare channel resource 205 predictions with reference signal 210 measurements. Channel resource 205 can be considered an L1-RSRP prediction target (e.g., for one or more sets of A beams) or used as a measurement resource to derive prediction results (e.g., for one or more sets of B beams). Additionally or alternatively, UE 115-a may identify quasi-co-addressable reference signal 210 and channel resource 205, which may instruct network entity 105-a to use the same transmit spatial filter to transmit reference signal 210 and channel resource 205. For example, UE 115-a may receive an indication from network entity 105-a (e.g., via a TCI status indication associated with reference signal 210), or may identify a pre-configuration rule (e.g., predefined in the standard) that instructs reference signal 210 and channel resource 205 to be quasi-co-located according to a quasi-co-location (QCL) relationship (such as type E QCL or enhanced type D QCL relationship (e.g., sharing the same transmit space filter)).

[0095] In some cases, UE 115-a can use the EPRE offset to support performance monitoring of beam prediction. In some such cases, the difference between the predicted channel characteristics and the measured channel characteristics may not be due to inaccuracies at UE 115-a (e.g., if the transmit power is modified by network entity 105-a), and UE 115-a can use the EPRE offset to verify prediction accuracy. For example, if the predicted L1-RSRP of channel resource 205 differs from the measured L1-RSRP of reference signal 210, then if the EPRE offset corresponds to the difference between the predicted L1-RSRP and the measured L1-RSRP (e.g., based on the correlation between EPRE and L1-RSRP or L1-SINR), then UE 115-a can determine that the prediction is accurate.

[0096] UE 115-a can identify the EPRE offset between channel resource 205 (e.g., SSB, CSI-RS, virtual resource) and reference signal 210 (e.g., DMRS) based on one or more pre-configured offset values, signaling indicating offset values ​​from network entity 105-a, sending a request for offset values, or any combination thereof.

[0097] For example, UE 115-a can identify one or more pre-configured EPRE offsets (e.g., predefined in the standard) to determine the EPRE offset between channel resource 205 and reference signal 210. In some cases, UE 115-a can select the EPRE offset based on the type of channel resource, the type of downlink channel carrying reference signal 210, the waveform associated with reference signal 210, the waveform associated with channel resource 205, or any combination thereof. For example, when channel resource 205 is an SSB, CSI-RS, or virtual resource and reference signal 210 is transmitted via physical downlink control channel (PDCCH) (e.g., PDCCH-DMRS) or via physical downlink shared channel (PDSCH) (e.g., PDSCH-DMRS), a dedicated EPRE offset can be associated with various sub-cases (e.g., combinations). For example, corresponding EPRE offsets can be defined for PDCCH-DMRS and SSB or CSI-RS, PDCCH-DMRS and virtual resource, PDSCH-DMRS and SSB or CSI-RS, and PDSCH-DMRS and virtual resource. In some cases, a single EPRE offset may be defined jointly for multiple combinations (e.g., all sub-cases) of the type of channel resource 205 and the type of downlink channel carrying reference signal 210, or it may be defined specifically by combination. It should be noted that the EPRE offset may be defined for any combination of the type of channel resource 205 and the type of downlink channel carrying reference signal 210, and is not limited to the examples provided herein.

[0098] In some examples, a corresponding EPRE offset can be defined when channel resource 205 is considered a measurement resource for prediction (e.g., L1-RSRP or L1-SINR prediction) and when channel resource 205 is considered a prediction target for prediction. Additionally or alternatively, an ERPE offset can be defined when reference signal 210 is based on a first type of waveform and channel resource 205 is based on a second type of waveform (e.g., from a set of candidate waveforms including at least one of cyclic prefix OFDM (CP-OFDM), DFT-s-OFDM, frequency modulated continuous wave (FMCW), orthogonal time-frequency space (OTFS), or combinations thereof, and other examples). In such examples, a corresponding EPRE offset can be defined for various combinations of candidate waveforms.

[0099] In some cases, UE 115-a may select a pre-configured EPRE offset based on not receiving offset indication 215 (e.g., a signal indicating an EPRE offset) from network entity 105-a. For example, UE 115-a may make a selection without considering one or more pre-configured EPRE offsets until it is determined that network entity 105-a has not yet sent offset indication 215 (e.g., after a threshold duration). Additionally or alternatively, network entity 105-a may select (e.g., down-select) an EPRE offset from a set of multiple pre-configured EPRE offsets (e.g., jointly or by sub-cases) and may indicate the selected EPRE offset to the UE via offset indication 215.

[0100] For example, UE 115-a can identify the EPRE offset between channel resource 205 and reference signal 210 based on signaling received from network entity 105-a. For instance, network entity 105-a can send an offset indication 215 to UE 115-a, which can indicate one or more EPRE offsets. In some cases, offset indication 215 can indicate a single EPRE offset (e.g., explicitly), or it can indicate a subset of one or more pre-configured EPRE offsets (e.g., a down-selection of predefined offset values). Offset indication 215 can indicate such an offset value jointly across one or more sub-cases (e.g., across all sub-cases), or it can indicate such an offset value individually for each sub-case or combination of sub-cases. Additionally or alternatively, the EPRE offset indicated by offset indication 215 can override the default ERPE offset (e.g., in the case of a predefined single offset value). In some examples, offset indication 215 can indicate the resource ID of channel resource 205.

[0101] Network entity 105-a can send offset indication 215 based on one or more types of control messages (such as RRC messages, MAC-CE, or DCI messages). In some cases, based on hierarchical selection, a first type of control message can indicate a subset of offset values ​​indicated by a second type of control message. For example, when offset indication 215 is an RRC message, offset indication 215 can indicate one or more EPRE offsets that are a subset of a plurality of pre-configured EPRE offsets. Similarly, when offset indication 215 is a MAC-CE, offset indication 215 can indicate one or more EPRE offsets that are a subset of EPRE offsets indicated by RRC messages (e.g., and pre-configured EPRE offsets). Again, when offset indication 215 is a DCI message, offset indication 215 can indicate one or more EPRE offsets that are a subset of EPRE offsets indicated by MAC-CE (e.g., and EPRE offsets indicated by RRC messages and pre-configured EPRE offsets).

[0102] In some examples, UE 115-a may request network entity 105-a to send an offset indication 215 to UE 115-a. For example, UE 115-a may send an offset request 220 to network entity 105-a, thereby requesting EPRE information associated with reference signal 210 (e.g., PDCCH-DMRS or PDSCH-DMRS). In some cases, offset request 220 may indicate one or more signaling schemes for sending offset indication 215, such as explicit indication, selection from pre-configured EPRE offsets, indicating EPRE offsets jointly across multiple sub-cases, indicating EPRE offsets individually for each sub-case or combination of sub-cases, or any combination thereof. Additionally or alternatively, offset request 220 may indicate channel resource 205 (e.g., for predicting values ​​to be compared with measurements based on EPRE offsets). In some cases, UE 115-a may send offset request 220 as an RRC message, MAC-CE, UCI message, scheduling request (SR), or any combination thereof.

[0103] In some cases, UE 115-a may include multiple TRPs (e.g., multiple antenna panels) for receiving reference signal 210. For example, reference signal 210 may include multiple ports (e.g., multiple DMRS ports) received by a corresponding TRP of UE 115-a. In some examples, each DMRS port of reference signal 210 may be quasi-co-located with a corresponding channel resource 205 (e.g., different SSBs, CSI-RS, or virtual resources). To identify EPRE offsets for different TRPs of UE 115-a, UE 115-a may identify one or more EPRE offset groups, which include EPRE offsets for multiple QCL sources (e.g., multiple channel resources 205) of the reference signal (e.g., reference signal 210, a single PDSCH-DMRS). For example, UE 115-a may identify a pre-configured EPRE offset group (e.g., predefined in the standard), or may receive signaling from network entity 105-a indicating an EPRE offset group, which may include a first EPRE offset for a first TRP of UE 115-a (e.g., an EPRE offset for a first beam associated with a first DMRS port of reference signal 210) and a second EPRE offset for a second TRP of UE 115-a (e.g., an EPRE offset for a second beam associated with a second DMRS port of reference signal 210).

[0104] Figure 3An example of a signaling diagram 300 supporting EPRE offset indication for beam prediction according to one or more aspects of this disclosure is shown. Signaling diagram 300 may implement or be implemented by one or more aspects of wireless communication systems 100 and 200. For example, signaling diagram 300 may be an example of signaling from network entity 105 to UE 115 indicating an EPRE offset, the UE being a reference... Figure 1 and Figure 2 Examples of the corresponding devices described.

[0105] As described herein, network entity 105 may send offset indication 305 to UE 115 to indicate one or more EPRE offsets between channel resources (e.g., SSB, CSI-RS, virtual resources) and DMRS 310. In some cases, DMRS 310 may be associated with PDSCH 315 (e.g., a reference signal used for associated data transmission).

[0106] For example, network entity 105 may send a DCI message that includes downlink permission for scheduling PDSCH 315. In some cases, network entity 105 may also include offset indication 305 in the DCI message (e.g., to indicate EPRE offset information associated with DMRS 310). Such DCI messages may be based on a dedicated DCI format (e.g., a new DCI format), may be associated with a dedicated radio network temporary identifier (RNTI) (e.g., a new RNTI), or both.

[0107] For example, network entity 105 may send an RRC configuration message to configure a semi-persistent scheduling PDSCH (e.g., PDSCH 315). In some cases, network entity 105 may include an offset indication 305 in the RRC configuration message (e.g., the RRC configuration indication of EPRE offset information associated with DMR 310). Additionally or alternatively, network entity 105 may include an offset indication 305 in a DCI message that triggers the semi-persistent scheduling PDSCH. In some such examples, a first offset indication 305 in the RRC configuration message may include multiple EPRE offsets, and a second offset indication 305 in the DCI trigger message may select (e.g., down-select) one or more EPRE offsets from the multiple EPRE offsets. Such a DCI message may be based on a dedicated DCI format (e.g., a new DCI format), may be associated with a dedicated radio network temporary identifier (RNTI) (e.g., a new RNTI), or both.

[0108] Figure 4An example of a process flow 400 supporting EPRE offset indication for beam prediction according to one or more aspects of this disclosure is shown. Process flow 400 may implement or be implemented by one or more aspects of wireless communication systems 100 and 200 and signaling diagram 300. For example, process flow 400 may include signaling between network entity 105-b and UE 115-b, which may be reference... Figures 1 to 3 Examples of corresponding devices described herein. Process flow 400 may support UE 115-b in using the techniques described herein to identify the EPRE offset used to verify the prediction accuracy of UE 115-b. Alternative examples of the following may be implemented, some of which may be performed in a different order than described or not performed at all. In some cases, the process may include additional features not mentioned below, or additional processes may be added.

[0109] At 405, UE 115-b can predict a first channel characteristic (e.g., channel statistics) associated with the channel resource. For example, at a certain time-domain timing, UE 115-b can predict the L1-RSRP or L1-SINR (e.g., the first channel characteristic) of the channel resource for a later time-domain timing. In some cases, the channel resource can be associated with a first TCI state (e.g., an indication of the beam used to transmit the channel resource). The channel resource can be an example of an SSB, CSI-RS, virtual resource (e.g., a resource that is not actually transmitted by network entity 105-b, but is used as a prediction target by UE 115-b and referenced by UE 115-b when reporting resource ID, predicting channel characteristics, or both) or any combination thereof.

[0110] At 410, UE 115-b can identify the EPRE offset between the channel resource and the reference signal. In some cases, network entity 105-b can indicate to UE 115-b that the scheduling reference signal (e.g., PDSCH-DMRS or PDCCH-DMRS) is associated with a first TCI state. Additionally or alternatively, network entity 105-b can indicate that the channel resource and the reference signal are quasi-co-located based on an enhanced type D QCL or type E QCL relationship. In some cases, UE 115-b can verify the accuracy of the predicted first channel characteristic by comparing the first channel characteristic with a second channel characteristic measured from the reference signal. The EPRE offset can be used to support such verification, which allows UE 115-b to identify whether the difference between the first and second channel characteristics is due to inaccurate prediction (e.g., rather than external factors).

[0111] In some cases, UE 115-b can identify EPRE offsets from one or more pre-configured (e.g., predefined in the standard) EPRE offsets. In some cases, one or more pre-configured EPRE offsets may include EPRE offsets associated with various combinations of the type of channel resource (e.g., SSB, CSI-RS, or virtual resource), the type of downlink channel carrying the reference signal (e.g., PDCCH or PDSCH), a first waveform associated with the reference signal (e.g., CP-OFD, DFT-s-OFDM, FMCW, OTFS, or any combination thereof), and a second waveform associated with the channel resource. Additionally or alternatively, one or more EPRE offsets may include EPRE offsets used when the channel resource is considered a measurement resource for prediction and when the channel resource is considered a prediction target for prediction. In some cases, a single EPRE offset may be defined commonly for multiple sub-cases, or individual EPRE offsets may be defined by sub-case.

[0112] In some cases, UE 115-b may select an EPRE offset from one or more pre-configured offsets based on whether it receives a signal indicating an EPRE offset from network entity 105-b (e.g., if no offset indication is received, UE 115-b may consider a predefined EPRE offset). In some examples, the EPRE offset may be one of a group of EPRE offsets, each associated with a reference signal and a corresponding TRP of UE 115-b (e.g., if UE 115-b includes multiple TRPs).

[0113] At 415, UE 115-b can send a request for the EPRE offset between the channel resources and the reference signal. In some cases, UE 115-b can indicate the channel resources associated with the reference signal in the request. In some cases, UE 115-b can send the request as an RRC message, MAC-CE, UCI message, SR, or any combination thereof.

[0114] At 420, UE 115-b may receive an offset indication from network entity 105-b. For example, UE 115-b may receive a message from network entity 105-b indicating one or more EPRE offsets that include at least an EPRE offset. In some cases, one or more EPRE offsets may be associated with one or more types of channel resources, one or more types of downlink channels, one or more waveforms associated with a reference signal, one or more waveforms associated with channel resources, or any combination thereof. For example, if the message indicates a single EPRE offset, the EPRE offset may be indicated jointly for multiple sub-cases. Additionally or alternatively, if the message indicates multiple EPRE offsets, each EPRE offset may be associated with a corresponding sub-case. In some examples, the EPRE offset indicated in the message may override the default EPRE at UE 115-b and may include a resource ID associated with a channel resource. In some cases, the message may indicate one or more EPRE offsets as a subset of multiple EPRE offsets, wherein the message downselects one or more EPRE offsets from the multiple EPRE offsets. This downselection may be based on the message type (e.g., reference). Figure 2 (Description of hierarchical selection downwards).

[0115] For example, UE 115-b can receive offset indications as DCI messages. In some cases, network entity 105-b can send DCI messages indicating EPRE offsets and including downlink permission for scheduling downlink transmissions associated with a reference signal. For example, a DCI message can schedule a PDSCH and indicate the EPRE offset associated with the DMRS of the PDSCH. Such DCI messages can be based on a dedicated DCI format (e.g., a new DCI format), can be associated with a dedicated radio network temporary identifier (RNTI) (e.g., a new RNTI), or both.

[0116] For example, UE 115-b may receive offset indications as RRC messages. In some cases, network entity 105-b may send an RRC message indicating a configuration for semi-persistent scheduling of downlink transmissions and including at least one or more EPRE offsets, such as an EPRE offset. For example, the RRC message may configure semi-persistent scheduling of the PDSCH and may indicate one or more potential EPRE offsets associated with the DMRS of the PDSCH. Additionally or alternatively, UE 115-b may receive offset indications as DCI messages that trigger semi-persistent scheduling of the PDSCH. For example, the DCI message may include a trigger for the semi-persistent scheduling of the PDSCH and may indicate a single EPRE offset selected downwards from one or more EPRE offsets indicated by the RRC configuration. Such DCI messages may be based on a dedicated DCI format (e.g., a new DCI format), may be associated with a dedicated radio network temporary identifier (RNTI) (e.g., a new RNTI), or both.

[0117] At 425, UE 115-b can receive a reference signal from network entity 105-b. For example, network entity 105-b can transmit DMRS via a downlink channel (e.g., PDCCH or PDSCH), where the DMRS is associated with a first TCI state (e.g., with channel resource sharing).

[0118] At 430, UE 115-b can measure a second channel characteristic associated with a reference signal. In some cases, the second channel characteristic can be a measurement of the reference signal, either L1-RSRP or L1-SINR.

[0119] At 435, UE 115-b can verify its prediction accuracy based on a first channel characteristic, a second channel characteristic, and the EPRE offset between the channel resource and the reference signal. For example, UE 115-b can compare the first and second channel characteristics to identify a first value corresponding to the difference between the first and second channel characteristics. UE 115-b can then verify its prediction accuracy based on the first value and the EPRE offset. For example, the EPRE offset can indicate whether the first value indicates an error at UE 115-b (e.g., due to the correlation between EPRE and L1-RSRP or L1-SINR). In some cases, UE 115-b can use accuracy verification as input to an AI or ML model used for beam management. Verification using the EPRE offset can improve the input quality of the AI ​​or ML model, thereby improving subsequent beam selection.

[0120] Figure 5A block diagram 500 is shown of a device 505 supporting EPRE offset indication for beam prediction according to one or more aspects of this disclosure. Device 505 may be an example of various aspects of UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505 or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0121] Receiver 510 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, and information channels associated with EPRE offset indication for beam prediction). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0122] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to EPRE offset indication for beam prediction, including packets, user data, control information, or any combination thereof. In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0123] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of EPRE offset indication for beam prediction as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof or components thereof may be able to perform one or more of the functions described herein.

[0124] In some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: 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 individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0125] Additionally or alternatively, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

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

[0127] The communication manager 520 may support wireless communication according to examples disclosed herein. For example, the communication manager 520 may be capable of, configured to, or operable to support components for predicting a first channel characteristic associated with channel resources. The communication manager 520 may be capable of, configured to, or operable to support components for receiving a reference signal via a downlink channel, wherein the channel resources and the reference signal are associated with a first TCI state. The communication manager 520 may be capable of, configured to, or operable to support components for measuring a second channel characteristic associated with the reference signal. The communication manager 520 may be capable of, configured to, or operable to support components for verifying the prediction accuracy of the UE based on the first channel characteristic, the second channel characteristic, and the EPRE offset between the channel resources and the reference signal.

[0128] By including or configuring a communication manager 520 according to an example as described herein, device 505 (e.g., at least one processor that controls or otherwise couples to receiver 510, transmitter 515, communication manager 520, or a combination thereof) can improve beamforming communications by supporting techniques for improved beam prediction through enhanced input to an AI or ML model for beam management.

[0129] Figure 6 A block diagram 600 illustrates a device 605 supporting EPRE offset indication for beam prediction according to one or more aspects of this disclosure. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0130] Receiver 610 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, and information channels associated with EPRE offset indication for beam prediction). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0131] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with EPRE offset indication for beam prediction), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0132] Device 605 or its various components may be examples of parts used to perform various aspects of EPRE offset indication for beam prediction as described herein. For example, communication manager 620 may include channel prediction component 625, signal receiving component 630, signal measurement component 635, prediction verification component 640, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0133] The communication manager 620 may support wireless communication according to examples disclosed herein. The channel prediction component 625 is capable of, configured to, or operable to support components for predicting a first channel characteristic associated with channel resources. The signal receiving component 630 is capable of, configured to, or operable to support components for receiving a reference signal via a downlink channel, wherein the channel resources and the reference signal are associated with a first TCI state. The signal measurement component 635 is capable of, configured to, or operable to support components for measuring a second channel characteristic associated with the reference signal. The prediction verification component 640 is capable of, configured to, or operable to support components for verifying the prediction accuracy of the UE based on the first channel characteristic, the second channel characteristic, and the EPRE offset between the channel resources and the reference signal.

[0134] Figure 7A block diagram 700 is shown of a communication manager 720 supporting EPRE offset indication for beam prediction according to one or more aspects of this disclosure. The communication manager 720 may be an example of aspects of the communication manager 520, communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of parts for performing various aspects of EPRE offset indication for beam prediction as described herein. For example, the communication manager 720 may include a channel prediction component 725, a signal receiving component 730, a signal measurement component 735, a prediction verification component 740, an offset identification component 745, a request transmission component 750, a statistical comparison component 755, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0135] The communication manager 720 can support wireless communication according to examples disclosed herein. The channel prediction component 725 is capable of, configured to, or operable to support components for predicting a first channel characteristic associated with channel resources. The signal receiving component 730 is capable of, configured to, or operable to support components for receiving a reference signal via a downlink channel, wherein the channel resources and the reference signal are associated with a first TCI state. The signal measurement component 735 is capable of, configured to, or operable to support components for measuring a second channel characteristic associated with the reference signal. The prediction verification component 740 is capable of, configured to, or operable to support components for verifying the prediction accuracy of the UE based on the first channel characteristic, the second channel characteristic, and the EPRE offset between the channel resources and the reference signal.

[0136] In some examples, the EPRE offset is associated with the type of channel resource, the type of downlink channel, a first waveform associated with a reference signal, a second waveform associated with the channel resource, or any combination thereof.

[0137] In some examples, the offset identification component 745 is capable of, configured to, or operable to support a component for determining an EPRE offset from a set of multiple potential EPRE offsets based on whether a signal indicating an EPRE offset is received from a network entity.

[0138] In some examples, the offset identification component 745 is capable of, configured to, or operable to support a component for receiving a message indicating one or more EPRE offsets that include at least an EPRE offset, wherein the message includes an RRC message, a MAC-CE message, a DCI message, or any combination thereof.

[0139] In some examples, the EPRE offset is associated with a set of multiple types of channel resources, a set of multiple types of downlink channels, a set of multiple waveforms associated with a reference signal, a set of multiple waveforms associated with channel resources, or any combination thereof, based on the number of one or more EPRE offsets indicated in the message.

[0140] In some examples, each of the one or more EPRE offsets is associated with a set of multiple types of channel resources, a set of multiple types of downlink channels, a set of multiple waveforms associated with a reference signal, or a corresponding combination of multiple waveforms associated with channel resources.

[0141] In some examples, the message includes a resource identifier associated with the channel resource.

[0142] In some examples, one or more EPRE offsets comprise a subset of a set of multiple EPRE offsets. In some examples, the message selects one or more EPRE offsets from a set of multiple EPRE offsets.

[0143] In some examples, the EPRE offset overrides the default EPRE offset based on the received message.

[0144] In some examples, the offset identification component 745 is capable of, configured to, or operable to support components for receiving a DCI message indicating the EPRE offset and including a downlink-granted message that schedules downlink transmission, wherein a reference signal is associated with the downlink transmission.

[0145] In some examples, the offset identification component 745 is capable of, configured to, or operable to support components for receiving RRC messages that indicate the configuration for semi-persistent scheduling downlink transmission and include at least one or more EPRE offsets, wherein the reference signal is associated with the semi-persistent scheduling downlink transmission.

[0146] In some examples, the offset identification component 745 is capable of, configured to, or operable to support a component for receiving a DCI message that includes a trigger for semi-persistent scheduling of downlink transmission and indicates an EPRE offset, wherein the DCI message selects an EPRE offset downward from one or more EPRE offsets.

[0147] In some examples, the EPRE offset is one of the EPRE offsets in a group of EPRE offsets associated with a reference signal and the corresponding transmit and receive points.

[0148] In some examples, the request sending component 750 is capable of, configured to, or able to operate to support components for sending a request for an EPRE offset. In some examples, the offset identification component 745 is capable of, configured to, or able to operate to support components for receiving an EPRE offset in response to the request, wherein the UE's prediction accuracy is verified based on the received EPRE offset.

[0149] In some examples, the request indicates channel resources.

[0150] In some examples, the request includes an RRC message, MAC-CE, uplink control information message, scheduling request, or any combination thereof.

[0151] In some examples, to support the verification of UE prediction accuracy, the statistical comparison component 755 is capable of, configured to, or operable to support components for comparing a first channel characteristic and a second channel characteristic to identify a first value corresponding to the difference between the first channel characteristic and the second channel characteristic. In some examples, to support the verification of UE prediction accuracy, the prediction verification component 740 is capable of, configured to, or operable to support components for verifying the UE prediction accuracy based on the first value and the EPRE offset.

[0152] In some examples, the first channel characteristic and the second channel characteristic include at least one of L1-RSRP or L1-SINR.

[0153] In some examples, channel resources include SSB, CSI-RS, virtual resources, or any combination thereof.

[0154] In some examples, reference signals and channel resources are quasi-co-located according to enhanced D-type QCL or E-type QCL.

[0155] Figure 8A diagram of a system 800 including device 805 supporting EPRE offset indication for beam prediction, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or may include components thereof. Device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, at least one memory 830, code 835, and at least one processor 840. These components may communicate electronically or be coupled in other ways (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 845).

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

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

[0158] At least one memory 830 may include random access memory (RAM) and read-only memory (ROM). At least one memory 830 may store computer-readable, computer-executable code 835, including instructions that, when executed by at least one processor 840, cause device 805 to perform the various functions described herein. Code 835 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 835 may not be directly executable by at least one processor 840, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 830 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0159] At least one processor 840 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, at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 840. At least one processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., at least one memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting EPRE offset indication for beam prediction). For example, device 805 or components of device 805 may include at least one processor 840 and at least one memory 830 coupled to or coupled to at least one processor 840, wherein at least one processor 840 and at least one memory 830 are configured to perform the various functions described herein. In some examples, at least one processor 840 may include multiple processors, and at least one memory 830 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein.

[0160] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for predicting a first channel characteristic associated with channel resources. The communication manager 820 may be capable of, configured to, or operable to support components for receiving a reference signal via a downlink channel, wherein the channel resources and the reference signal are associated with a first TCI state. The communication manager 820 may be capable of, configured to, or operable to support components for measuring a second channel characteristic associated with the reference signal. The communication manager 820 may be capable of, configured to, or operable to support components for verifying the prediction accuracy of the UE based on the first channel characteristic, the second channel characteristic, and the EPRE offset between the channel resources and the reference signal.

[0161] By including or configuring a communication manager 820 according to an example as described herein, device 805 can support techniques for improving beamforming communication and user experience by enhancing the input of AI or ML models used for beam management.

[0162] In some examples, the communication manager 820 may be configured to use or otherwise cooperate with transceiver 815, one or more antennas 825, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported by or performed by at least one processor 840, at least one memory 830, code 835, or any combination thereof. For example, code 835 may include instructions that can be executed by at least one processor 840 to cause device 805 to perform various aspects of EPRE offset indication for beam prediction as described herein, or at least one processor 840 and at least one memory 830 may be otherwise configured to perform or support such operations individually or jointly.

[0163] Figure 9 A block diagram 900 illustrates a device 905 supporting EPRE offset indication for beam prediction according to one or more aspects of this disclosure. Device 905 may be an example of aspects of network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0164] Receiver 910 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 delivered to other components of device 905. In some examples, receiver 910 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 910 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0165] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 905. For example, transmitter 915 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 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 915 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 915 and receiver 910 may be co-located in a transceiver, which may include or be coupled to a modem.

[0166] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of EPRE offset indication for beam prediction as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof or components thereof may be able to perform one or more of the functions described herein.

[0167] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0168] Additionally or alternatively, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

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

[0170] The communication manager 920 may support wireless communication according to examples disclosed herein. For example, the communication manager 920 may be capable of, configured to, or operable to support components for transmitting a reference signal to the UE via a downlink channel, wherein the reference signal is associated with a first TCI state. The communication manager 920 may be capable of, configured to, or operable to support components for transmitting to the UE a message indicating an EPRE offset between the reference signal and a channel resource associated with the first TCI state, wherein the EPRE offset indicates input at the UE to a process used to verify the prediction accuracy of the UE.

[0171] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., at least one processor that controls or otherwise couples to receiver 910, transmitter 915, communication manager 920, or a combination thereof) can improve beamforming communications by supporting techniques for improved beam prediction through enhanced input to AI or ML models used for beam management.

[0172] Figure 10A block diagram 1000 of a device 1005 supporting EPRE offset indication for beam prediction according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of device 905 or network entity 105 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005, or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0173] Receiver 1010 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 delivered to other components of device 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0174] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 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 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 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 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0175] Device 1005 or its various components may be examples of parts used to perform various aspects of EPRE offset indication for beam prediction as described herein. For example, communication manager 1020 may include signal transmission component 1025, offset indication component 1030, or any combination thereof. Communication manager 1020 may be examples of various aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in combination with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0176] The communication manager 1020 may support wireless communication according to examples disclosed herein. The signal transmission component 1025 is capable of, configured to, or operable to support components for transmitting a reference signal to the UE via a downlink channel, wherein the reference signal is associated with a first TCI state. The offset indication component 1030 is capable of, configured to, or operable to support components for transmitting to the UE a message indicating an EPRE offset between the reference signal and a channel resource associated with the first TCI state, wherein the EPRE offset indicates input at the UE for a process used to verify the prediction accuracy of the UE.

[0177] Figure 11 A block diagram 1100 is shown of a communication manager 1120 supporting EPRE offset indication for beam prediction according to one or more aspects of this disclosure. Communication manager 1120 may be an example of aspects of communication manager 920, communication manager 1020, or both as described herein. Communication manager 1120 or its various components may be examples of components for performing various aspects of EPRE offset indication for beam prediction as described herein. For example, communication manager 1120 may include signal transmission component 1125, offset indication component 1130, request reception component 1135, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between 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.

[0178] Communication manager 1120 may support wireless communication according to examples disclosed herein. Signal transmission component 1125 is capable of, configured to, or operable to support components for transmitting a reference signal to the UE via a downlink channel, wherein the reference signal is associated with a first TCI state. Offset indication component 1130 is capable of, configured to, or operable to support components for transmitting a message to the UE indicating an EPRE offset between the reference signal and a channel resource associated with the first TCI state, wherein the EPRE offset indicates input at the UE for a process used to verify the prediction accuracy of the UE.

[0179] In some examples, the EPRE offset is associated with the type of channel resource, the type of downlink channel, a first waveform associated with a reference signal, a second waveform associated with the channel resource, or any combination thereof.

[0180] In some examples, the messages include RRC messages, MAC-CE, DCI messages, or any combination thereof.

[0181] In some examples, the offset indication component 1130 is capable of, configured to, or operable to support components for transmitting a DCI message indicating the EPRE offset and including a downlink-granted message that schedules downlink transmission, wherein a reference signal is associated with the downlink transmission.

[0182] In some examples, the offset indication component 1130 is capable of, configured to, or operable to support components for sending an RRC message indicating a configuration for semi-persistent scheduling downlink transmission and including at least one or more EPRE offsets, wherein the reference signal is associated with the semi-persistent scheduling downlink transmission.

[0183] In some examples, the offset indication component 1130 is capable of, configured to, or able to operate to support components for transmitting messages including an EPRE offset group, wherein the EPRE offset group includes at least an EPRE offset and a second EPRE offset, and wherein the EPRE offset is associated with a first transmit and receive point at the UE, and the second EPRE offset is associated with a second transmit and receive point at the UE.

[0184] In some examples, the request receiving component 1135 is capable of, configured to, or able to operate to support components for receiving requests for EPRE offsets, wherein the message is sent based on the receipt of the request.

[0185] In some examples, channel resources include SSB, CSI-RS, virtual resources, or any combination thereof.

[0186] Figure 12A diagram of a system 1200 including device 1205 supporting EPRE offset indication for beam prediction, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or network entity 105 as described herein, or may include components thereof. Device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1205 may include components that support output and enable communication, such as a communication manager 1220, a transceiver 1210, an antenna 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1240).

[0187] Transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1210 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1210 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1205 may include one or more antennas 1215 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1210 may include one or more processors or one or more memory components or configured to couple to said one or more processors or one or more memory components, said one or more processors or memory components being operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1210, or transceiver 1210 and one or more antennas 1215, or transceiver 1210 and one or more antennas 1215 and one or more processors or one or more memory components (e.g., at least one processor 1235, at least one memory 1225, or both) may be included in a chip or chip assembly mounted in device 1205. In some examples, transceiver 1210 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).

[0188] At least one memory 1225 may include RAM, ROM, or any combination thereof. At least one memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by one or more of at least one processor 1235, cause device 1205 to perform the various functions described herein. Code 1230 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1230 may not be directly executable by one of the at least one processor 1235, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1225 may also include a BIOS, among other things, that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0189] At least one processor 1235 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof). In some cases, at least one processor 1235 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into one or more of the at least one processor 1235. At least one processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more memories in at least one memory 1225) to cause device 1205 to perform various functions (e.g., functions or tasks supporting EPRE offset indication for beam prediction). For example, device 1205 or components of device 1205 may include at least one processor 1235 and at least one memory 1225 coupled to one or more of the at least one processor 1235, wherein at least one processor 1235 and at least one memory 1225 are configured to perform the various functions described herein. At least one processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1230) host functions for performing the functions of device 1205. At least one processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1205 (such as within one or more memories of at least one memory 1225). In some implementations, at least one processor 1235 may be a component of a processing system. A processing system generally refers to a system or series of machines or components that receive input and process that input to produce a set of outputs (which may be passed to other systems or components of, for example, device 1205). For example, the processing system of device 1205 may refer to a system that includes various other components or sub-components of device 1205 (such as at least one processor 1235, transceiver 1210, communication manager 1220, or other components or combinations of components of device 1205). The processing system of device 1205 can interface with other components of device 1205 and can process information (such as inputs or signals) received from other components or output information to other components. For example, the chip or modem of device 1205 may include a processing system and one or more interfaces for outputting information or for acquiring information, or both. These one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to acquire information, or the same interface configured to both output and acquire information, and other specific implementations.In some embodiments, the one or more interfaces may refer to the interface between the processing system of the chip or modem and the transmitter, enabling device 1205 to send information output from the chip or modem. Additionally or alternatively, in some embodiments, the one or more interfaces may refer to the interface between the processing system of the chip or modem and the receiver, enabling device 1205 to receive information or signal input, and such information can be transmitted to the processing system. Those skilled in the art will readily recognize that the first interface may also receive information or signal input, and the second interface may also output information or signal output.

[0190] In some examples, bus 1240 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1240 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 1205, or communication performed between different components of device 1205 that are co-addressable or may be located in different locations (e.g., where device 1205 may refer to a system in which one or more of communication manager 1220, transceiver 1210, at least one memory 1225, code 1230 and at least one processor 1235 may be located in one component of different components or partitioned between different components).

[0191] In some examples, the communication manager 1220 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 1220 can manage the transfer of data communication between client devices (such as one or more UEs 115). In some examples, the communication manager 1220 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 1220 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0192] The communication manager 1220 may support wireless communication according to examples disclosed herein. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for transmitting a reference signal to the UE via a downlink channel, wherein the reference signal is associated with a first TCI state. The communication manager 1220 may be capable of, configured to, or operable to support components for transmitting to the UE a message indicating an EPRE offset between the reference signal and a channel resource associated with the first TCI state, wherein the EPRE offset indicates input at the UE to a process used to verify the prediction accuracy of the UE.

[0193] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 can support techniques for improving beamforming communication and user experience by enhancing the input of AI or ML models used for beam management.

[0194] In some examples, the communication manager 1220 may be configured to use or otherwise coordinate with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the transceiver 1210, one or more processors in at least one processor 1235, one or more memories in at least one memory 1225, code 1230, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1235, at least one memory 1225, code 1230, or any combination thereof). For example, code 1230 may include instructions that can be executed by one or more processors in at least one processor 1235 to cause the device 1205 to perform various aspects of EPRE offset indication for beam prediction as described herein, or at least one processor 1235 and at least one memory 1225 may be otherwise configured to perform or support such operations individually or jointly.

[0195] Figure 13 A flowchart illustrating a method 1300 for supporting EPRE offset indication for beam prediction according to various aspects of this disclosure is shown. Operation of method 1300 can be implemented by a UE or its components as described herein. For example, operation of method 1300 can be performed by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0196] At 1305, the method may include predicting a first channel characteristic associated with channel resources. The operation of block 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1305 may be derived from references... Figure 7 The described channel prediction component 725 is used to perform this.

[0197] At 1310, the method may include receiving a reference signal via a downlink channel, wherein the channel resources and the reference signal are associated with a first TCI state. Operation of block 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be determined by reference... Figure 7 The described signal receiving component 730 performs this function.

[0198] At 1315, the method may include measuring a second channel characteristic associated with a reference signal. The operation of block 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1315 may be determined by, as in the reference... Figure 7 The described signal measurement component 735 is used to perform this.

[0199] At 1320, the method may include verifying the prediction accuracy of the UE based on a first channel characteristic, a second channel characteristic, and an EPRE offset between the channel resources and a reference signal. The operation of block 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1320 may be determined by reference... Figure 7 The described prediction verification component 740 is executed.

[0200] Figure 14 A flowchart illustrating a method 1400 for supporting EPRE offset indication for beam prediction according to various aspects of this disclosure is shown. The operation of method 1400 can be implemented by a network entity or its components as described herein. For example, the operation of method 1400 can be implemented by, as referenced... Figures 1 to 4 as well as Figures 9 to 12 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 network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0201] At 1405, the method may include transmitting a reference signal to the UE via a downlink channel, wherein the reference signal is associated with a first TCI state. Operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be determined by reference... Figure 11 The described signal transmitting component 1125 performs this function.

[0202] At 1410, the method may include sending a message to the UE indicating an EPRE offset between a reference signal and channel resources associated with a first TCI state, wherein the EPRE offset indicates input at the UE to a process used to verify the prediction accuracy of the UE. Operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be determined by reference to... Figure 11The described offset instruction component 1130 is used to perform this.

[0203] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication by a UE, the method comprising: predicting a first channel characteristic associated with channel resources; receiving a reference signal via a downlink channel, wherein the channel resources and the reference signal are associated with a first TCI state; measuring a second channel characteristic associated with the reference signal; and verifying the prediction accuracy of the UE based at least in part on the first channel characteristic, the second channel characteristic, and an EPRE offset between the channel resources and the reference signal.

[0204] Aspect 2: According to the method of aspect 1, wherein the EPRE offset is associated with the type of the channel resource, the type of the downlink channel, a first waveform associated with the reference signal, a second waveform associated with the channel resource, or any combination thereof.

[0205] Aspect 3: The method according to any one of Aspects 1 to 2, the method further comprising: determining the EPRE offset from a plurality of potential EPRE offsets based at least in part on whether a signal indicative of the EPRE offset is received from a network entity.

[0206] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: receiving a message indicating one or more EPRE offsets including at least the EPRE offset, wherein the message includes an RRC message, a MAC-CE message, a DCI message, or any combination thereof.

[0207] Aspect 5: According to the method of aspect 4, wherein the EPRE offset is associated, at least in part, with a number of one or more EPRE offsets indicated in the message, with multiple types of channel resources, multiple types of downlink channels, multiple waveforms associated with the reference signal, multiple waveforms associated with the channel resources, or any combination thereof.

[0208] Aspect 6: The method according to any one of Aspects 4 to 5, wherein each of the one or more EPRE offsets is associated with a variety of types of channel resources, a variety of types of downlink channels, a variety of waveforms associated with the reference signal, or a corresponding combination of a variety of waveforms associated with the channel resources.

[0209] Aspect 7: The method according to any one of Aspects 4 to 6, wherein the message includes a resource identifier associated with the channel resource.

[0210] Aspect 8: The method according to any one of Aspects 4 to 7, wherein the one or more EPRE offsets comprise a subset of a plurality of EPRE offsets, and the message selects the one or more EPRE offsets downward from the plurality of EPRE offsets.

[0211] Aspect 9: The method according to any one of Aspects 4 to 8, wherein the EPRE offset is overwritten at least in part based on the receipt of the message to override the default EPRE offset.

[0212] Aspect 10: The method according to any one of Aspects 1 to 9, the method further comprising: receiving a DCI message indicating the EPRE offset and including a downlink grant for scheduling downlink transmission, wherein the reference signal is associated with the downlink transmission.

[0213] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: receiving an RRC message indicating a configuration for semi-persistent scheduling downlink transmission and including at least one or more EPRE offsets of the EPRE offset, wherein the reference signal is associated with the semi-persistent scheduling downlink transmission.

[0214] Aspect 12: The method according to aspect 11, the method further comprising: receiving a DCI message including a trigger for the semi-persistent scheduling downlink transmission and indicating the EPRE offset, wherein the DCI message selects the EPRE offset downward from the one or more EPRE offsets.

[0215] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the EPRE offset is one of an EPRE offset in a group of EPRE offsets associated with the reference signal and the corresponding transmit and receive points.

[0216] Aspect 14: The method according to any one of Aspects 1 to 13, the method further comprising: sending a request for the EPRE offset; and receiving the EPRE offset in response to the request, wherein verifying the prediction accuracy of the UE is based at least in part on receiving the EPRE offset.

[0217] Aspect 15: The method according to aspect 14, wherein the request indicates the channel resource.

[0218] Aspect 16: The method according to any one of Aspects 14 to 15, wherein the request includes an RRC message, MAC-CE, uplink control information message, scheduling request, or any combination thereof.

[0219] Aspect 17: The method according to any one of Aspects 1 to 16, wherein verifying the prediction accuracy of the UE comprises: comparing the first channel characteristic and the second channel characteristic to identify a first value corresponding to the difference between the first channel characteristic and the second channel characteristic; and verifying the prediction accuracy of the UE based at least in part on the first value and the EPRE offset.

[0220] Aspect 18: The method according to any one of Aspects 1 to 17, wherein the first channel characteristic and the second channel characteristic include at least one of L1-RSRP or L1-SINR.

[0221] Aspect 19: The method according to any one of Aspects 1 to 18, wherein the channel resources include SSB, CSI-RS, virtual resources or any combination thereof.

[0222] Aspect 20: The method according to any one of Aspects 1 to 19, wherein the reference signal and the channel resources are quasi-co-located according to an enhanced D-type QCL or an E-type QCL.

[0223] Aspect 21: A method for wireless communication by a network entity, the method comprising: transmitting a reference signal to a UE via a downlink channel, wherein the reference signal is associated with a first TCI state; and transmitting to the UE a message indicating an EPRE offset between the reference signal and channel resources associated with the first TCI state, wherein the EPRE offset indicates input at the UE to a process for verifying the prediction accuracy of the UE.

[0224] Aspect 22: According to the method of aspect 21, wherein the EPRE offset is associated with the type of the channel resource, the type of the downlink channel, a first waveform associated with the reference signal, a second waveform associated with the channel resource, or any combination thereof.

[0225] Aspect 23: The method according to any one of Aspects 21 to 22, wherein the message includes an RRC message, a MAC-CE message, a DCI message, or any combination thereof.

[0226] Aspect 24: The method according to any one of Aspects 21 to 23, the method further comprising: transmitting a DCI message indicating the EPRE offset and including a downlink grant for scheduling downlink transmission, wherein the reference signal is associated with the downlink transmission.

[0227] Aspect 25: The method according to any one of Aspects 21 to 24, the method further comprising: sending an RRC message indicating a configuration for semi-persistent scheduling downlink transmission and including at least one or more EPRE offsets of the EPRE offset, wherein the reference signal is associated with the semi-persistent scheduling downlink transmission.

[0228] Aspect 26: The method according to any one of Aspects 21 to 25, the method further comprising: sending a message including an EPRE offset group, wherein the EPRE offset group includes at least the EPRE offset and a second EPRE offset, and wherein the EPRE offset is associated with a first transmission and reception point at the UE, and the second EPRE offset is associated with a second transmission and reception point at the UE.

[0229] Aspect 27: The method according to any one of aspects 21 to 26, the method further comprising: receiving a request for the EPRE offset, wherein sending the message is at least in part based on receiving the request.

[0230] Aspect 28: The method according to any one of Aspects 21 to 27, wherein the channel resources include SSB, CSI-RS, virtual resources or any combination thereof.

[0231] Aspect 29: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the UE performs a method according to any one of aspects 1 to 20.

[0232] Aspect 30: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 20.

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

[0234] Aspect 32: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the network entity performs a method according to any one of aspects 21 to 28.

[0235] Aspect 33: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 21 to 28.

[0236] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of aspects 21 to 28.

[0237] 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 of these methods can be combined.

[0238] 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 other than 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.

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

[0240] 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. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A 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 cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0241] The functionality described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functionality 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 functionality described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functionality can also be physically located in various locations, including portions distributed such that the functionality is implemented at different physical locations.

[0242] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing 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 multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0243] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list 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). Furthermore, 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".

[0244] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and subsequent reference to “the component” in a claim may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” may refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0245] 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, obtaining, selecting, choosing, building, and other similar actions.

[0246] 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 reference numeral to differentiate them. If only the first reference numeral is used in the description, 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.

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

[0248] The description herein is provided 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. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Predict the first channel characteristics associated with channel resources; A reference signal is received via a downlink channel, wherein the channel resources and the reference signal are associated with a first transmit configuration indicator state; Measure the second channel characteristics associated with the reference signal; as well as The prediction accuracy of the UE is verified at least in part based on the first channel characteristics, the second channel characteristics, and the per-resource element energy offset between the channel resources and the reference signal.

2. The UE of claim 1, wherein the per-resource-element energy offset is associated with the type of the channel resource, the type of the downlink channel, a first waveform associated with the reference signal, a second waveform associated with the channel resource, or any combination thereof.

3. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The per-resource-element energy offset is determined from a plurality of potential per-resource-element energy offsets, at least in part, based on whether a signal indicating the per-resource-element energy offset is received from a network entity.

4. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive a message indicating at least one or more per-resource-element energy offsets, wherein the message includes radio resource control messages, media access control control elements, downlink control information messages, or any combination thereof.

5. The UE of claim 4, wherein the per-resource-element energy offset is at least in part based on the number of one or more per-resource-element energy offsets indicated in the message being one, and is associated with multiple types of channel resources, multiple types of downlink channels, multiple waveforms associated with the reference signal, multiple waveforms associated with the channel resources, or any combination thereof.

6. The UE of claim 4, wherein each of the one or more per resource element energy offsets is associated with a plurality of types of channel resources, a plurality of types of downlink channels, a plurality of waveforms associated with the reference signal, or a corresponding combination of a plurality of waveforms associated with the channel resources.

7. The UE of claim 4, wherein the message includes a resource identifier associated with the channel resource.

8. The UE according to claim 4, wherein: The one or more per-resource-element energy offsets include multiple subsets of per-resource-element energy offsets, and The message selects one or more per-resource-element energy offsets from the plurality of per-resource-element energy offsets.

9. The UE of claim 4, wherein the per-resource-element energy offset is at least partially based on receiving the message to override the default per-resource-element energy offset.

10. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive a downlink control information message indicating the energy offset of each resource element and including downlink permission for scheduling downlink transmission, wherein the reference signal is associated with the downlink transmission.

11. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive a radio resource control message indicating the configuration for semi-persistent scheduling downlink transmission and including at least one or more per-resource-element energy offsets, wherein the reference signal is associated with the semi-persistent scheduling downlink transmission.

12. The UE of claim 11, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive a downlink control information message that includes a trigger for the semi-persistent scheduling downlink transmission and indicates the per-resource element energy offset, wherein the downlink control information message selects the per-resource element energy offset downward from one or more per-resource element energy offsets.

13. The UE of claim 1, wherein the per-resource-element energy offset is one of a group of per-resource-element energy offsets associated with the reference signal and the corresponding transmit and receive points.

14. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Send a request for the energy offset of each resource element; and In response to the request, the per-resource-element energy offset is received, wherein the prediction accuracy of the UE is verified at least in part based on the received per-resource-element energy offset.

15. The UE of claim 14, wherein the request indicates the channel resource.

16. The UE of claim 14, wherein the request includes a radio resource control message, a media access control element, an uplink control information message, a scheduling request, or any combination thereof.

17. The UE according to claim 1, wherein, To verify the prediction accuracy of the UE, the one or more processors can operate individually or jointly to execute the code to make the UE: The first channel characteristic and the second channel characteristic are compared to identify a first value corresponding to the difference between the first channel characteristic and the second channel characteristic; as well as The prediction accuracy of the UE is verified at least in part based on the first value and the energy offset per resource element.

18. The UE of claim 1, wherein the first channel characteristic and the second channel characteristic include at least one of layer 1 reference signal received power or layer 1 signal-to-interference-plus-noise ratio.

19. The UE of claim 1, wherein the channel resources include synchronization signal blocks, channel state information reference signals, virtual resources, or any combination thereof.

20. The UE of claim 1, wherein the reference signal and the channel resources are quasi-co-located according to enhanced type D quasi-co-location or type E quasi-co-location.

21. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: A reference signal is transmitted to the user equipment (UE) via a downlink channel, wherein the reference signal is associated with a first transmission configuration indicator state; as well as A message is sent to the UE indicating the per-resource-element energy offset between the reference signal and the channel resources associated with the state of the first transmission configuration indicator, wherein the per-resource-element energy offset indicates the input at the UE to the process used to verify the prediction accuracy of the UE.

22. The network entity of claim 21, wherein the per-resource-element energy offset is associated with the type of the channel resource, the type of the downlink channel, a first waveform associated with the reference signal, a second waveform associated with the channel resource, or any combination thereof.

23. The network entity of claim 21, wherein the message includes a radio resource control message, a media access control element, a downlink control information message, or any combination thereof.

24. The network entity of claim 21, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: Send a downlink control information message indicating the energy offset of each resource element and including downlink permission for scheduling downlink transmission, wherein the reference signal is associated with the downlink transmission.

25. The network entity of claim 21, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: The system transmits a configuration for semi-persistent scheduling downlink transmission and a radio resource control message that includes at least one or more per-resource-element energy offsets, wherein the reference signal is associated with the semi-persistent scheduling downlink transmission.

26. The network entity of claim 21, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: Send a message including a per-resource-element energy offset group, wherein the per-resource-element energy offset group includes at least the per-resource-element energy offset and a second per-resource-element energy offset, wherein the per-resource-element energy offset is associated with a first transmit and receive point at the UE, and the second per-resource-element energy offset is associated with a second transmit and receive point at the UE.

27. The network entity of claim 21, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: Receive a request for energy offset for each resource element, wherein sending the message is based at least in part on receiving the request.

28. The network entity of claim 21, wherein the channel resources include synchronization signal blocks, channel state information reference signals, virtual resources, or any combination thereof.

29. A method for wireless communication by a user equipment (UE), the method comprising: Predict the first channel characteristics associated with channel resources; A reference signal is received via a downlink channel, wherein the channel resources and the reference signal are associated with a first transmit configuration indicator state; Measure the second channel characteristics associated with the reference signal; as well as The prediction accuracy of the UE is verified at least in part based on the first channel characteristics, the second channel characteristics, and the per-resource element energy offset between the channel resources and the reference signal.

30. A method for wireless communication by a network entity, the method comprising: A reference signal is transmitted to the user equipment (UE) via a downlink channel, wherein the reference signal is associated with a first transmission configuration indicator state; as well as A message is sent to the UE indicating the per-resource-element energy offset between the reference signal and the channel resources associated with the state of the first transmission configuration indicator, wherein the per-resource-element energy offset indicates the input at the UE to the process used to verify the prediction accuracy of the UE.

Images