Downlink beam performance report measured by ue

Abstract

Methods, systems, and apparatus for conducting wireless communication are described. A user equipment (UE) can receive signaling instructing the configuration of a downlink beam performance report for a set of predicted target resources based on a set of performance monitoring resources. The configuration may include an error rate threshold for triggering predicted failure instances, a time window, and a threshold for the number of predicted failure instances that trigger a predicted failure event within the time window. The UE can measure one or more reference signals associated with one or more performance monitoring resources in the set of performance monitoring resources and generate a performance monitoring report based on the number of performance failure instances occurring within the time window. The UE can identify beam space information for the set of performance monitoring resources based on beam space information for one or more predicted target resources from previous performance monitoring reports.

Description

Technical Field

[0001] The following content pertains to wireless communication, including downlink beam performance reports measured by the UE. 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). Summary of the Invention

[0003] The described technology relates to improved methods, systems, devices, and apparatuses for supporting downlink beam performance reporting measured by a user equipment (UE). For example, the described technology allows a network entity to configure an error rate threshold, a time window, and a threshold for the number of predicted failure instances that trigger a predicted failure event within that time window for the UE. The UE can measure one or more reference signals (RS) and determine the error rate for each of the one or more RSs. The UE can generate a performance monitoring report based on the number of performance failure instances occurring within the time window and can send the performance monitoring report based on the number of performance failure instances exceeding a threshold for the number of predicted failure instances. Additionally or alternatively, the UE can identify beamspace information, a received beamspace filter, or both for a set of performance monitoring resources based on beamspace information for a subset of the predicted target resources from previous performance monitoring reports. Such downlink beam performance prediction measured by the UE can yield several benefits superior to alternative methods. For example, predictions measured by the UE can experience lower latency and improved reliability compared to network-based monitoring methods.

[0004] A method performed by a UE is described. The method may include: receiving signaling instructing a configuration for a downlink beam performance report for a set of predicted target resources based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering predicted failure instances, a time window, and a threshold for the number of predicted failure instances that trigger a predicted failure event within the time window; measuring one or more RSs associated with one or more performance monitoring resources in the set of performance monitoring resources; and generating a performance monitoring report based on the number of performance failure instances occurring within the time window.

[0005] A UE is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code so that the UE: receives signaling instructing a configuration for a downlink beam performance report for a set of predicted target resources based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering predicted failure instances, a time window, and a threshold for the number of predicted failure instances that trigger predicted failure events within the time window; measures one or more RSs associated with one or more performance monitoring resources in the set of performance monitoring resources; and generates a performance monitoring report based on the number of performance failure instances occurring within the time window.

[0006] Another type of UE is described. This UE may include: components for receiving signaling instructing a configuration for a downlink beam performance report for a set of predicted target resources based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering predicted failure instances, a time window, and a threshold for the number of predicted failure instances that trigger predicted failure events within the time window; components for measuring one or more RSs associated with one or more performance monitoring resources in the set of performance monitoring resources; and components for generating a performance monitoring report based on the number of performance failure instances occurring within the time window.

[0007] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to: receive signaling instructions for configuring a downlink beam performance report for a set of UE measurements against a set of target resources based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering prediction failure instances, a time window, and a threshold for the number of prediction failure instances that trigger prediction failure events within the time window; measure one or more RSs associated with one or more performance monitoring resources in the set of performance monitoring resources; and generate a performance monitoring report based on the number of performance failure instances occurring within the time window.

[0008] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for identifying beamspace information for a set of performance monitoring resources based on beamspace information of a subset of the set of predicted target resources from previous performance monitoring reports.

[0009] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, beamspace information for a set of performance monitoring resources includes quasi-co-located source RS information for the set of performance monitoring resources, and beamspace information for a subset of a set of predicted target resources from previous performance monitoring reports includes quasi-co-located source RS information for a subset of a set of predicted target resources from previous performance monitoring reports.

[0010] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for identifying a set of performance monitoring resources based on a receive beam spatial filter for a subset of the set of predicted target resources from previous performance monitoring reports.

[0011] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for receiving beamspace information indicating a set of performance monitoring resources, receiving signaling for beamspace filters, or both.

[0012] In some examples of the methods described herein, UEs, and nontransitory computer-readable media, performance monitoring reports include indications of one or more error rate values ​​exceeding an error rate threshold, timing information associated with one or more predicted failure instances within a time window, additional RS measurement information associated with one or more performance monitoring resources, or any combination thereof.

[0013] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for receiving signaling including a preemption indication that configures the UE to suppress one or more performance measurement opportunities associated with a set of one or more performance measurement resources.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving signaling may include an instruction for receiving a beam prediction report identifier that may be associated with an error rate threshold, a time window, a threshold for the number of prediction failure instances, or a combination thereof.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving signaling may include operations, features, components, or instructions for receiving an indication of a serving cell or bandwidth portion that may be associated with an error rate threshold, a time window, a predicted number of failed instances threshold, or a combination thereof.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving signaling may include operations, features, components, or instructions for receiving an indication of the number of consecutive time slots, subframes, frames, or other time periods within a defined time window, wherein the time window includes a sliding window or a non-sliding window.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving signaling may include operations, features, components, or instructions for receiving an indication of a timer that identifies a time window, wherein the indication includes the start point of the timer, the end point of the timer, the duration of the timer, or any combination thereof.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, generating a performance monitoring report may include operations, features, components, or instructions for sending a performance monitoring report based on the number of predicted failure instances exceeding a threshold for the number of predicted failure instances, wherein each predicted failure instance may be based on one or more measured RSs associated with one or more performance monitoring resources in a set of performance monitoring resources exceeding an error rate threshold.

[0019] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, each prediction failure instance may be based on all measured RSs associated with one or more performance monitoring resources in a set of performance monitoring resources exceeding an error rate threshold.

[0020] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, transmitting reports may include operations, features, components, or instructions for transmitting performance monitoring reports via a Media Access Control-Control Element (MAC-CE), Radio Resource Control (RRC), one or more Channel State Information (CSI) reports, or a combination thereof.

[0021] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, generating a performance monitoring report may include operations, features, components, or instructions for suppressing report transmission based on the premise that the number of predicted failed instances does not exceed a threshold for the number of predicted failed instances.

[0022] In the methods described herein, and in some examples of UEs and nontransitory computer-readable media, the error rate threshold indicates the hypothetical block error rate value that triggers a prediction failure instance.

[0023] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the configuration may be associated with a request from a network entity for the UE to perform a prediction of a set of quality metrics for predicting target resources, and the predicted quality metrics may be determined by the UE based on measurements of one or more RSs individually scheduled by the network entity.

[0024] A method performed by a network entity is described. The method may include: outputting a first signaling indicating a configuration for a downlink beam performance report for a set of UE measurements targeting a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering prediction failure instances, a time window, and a threshold for the number of prediction failure instances triggering prediction failure events within the time window; obtaining a performance monitoring report based on the number of prediction failure instances occurring within the time window; and outputting a second signaling indicating adjustments to one or more parameters based on the performance monitoring report.

[0025] A network entity is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code so that the network entity: outputs first signaling instructs a configuration for a downlink beam performance report for a set of UE measurements against a set of target resources based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering prediction failure instances, a time window, and a threshold for the number of prediction failure instances that trigger prediction failure events within the time window; obtains a performance monitoring report based on the number of prediction failure instances occurring within the time window; and outputs second signaling instructing adjustments to one or more parameters based on the performance monitoring report.

[0026] Another network entity is described. This network entity may include: components for outputting first signaling indicating a configuration for a downlink beam performance report for a set of predicted target resources based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering prediction failure instances, a time window, and a threshold for the number of prediction failure instances that trigger prediction failure events within the time window; components for obtaining a performance monitoring report based on the number of prediction failure instances occurring within the time window; and components for outputting second signaling indicating adjustments to one or more parameters based on the performance monitoring report.

[0027] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to: output first signaling instructions for configuring a downlink beam performance report for a set of UE measurements against a set of target resources based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering prediction failure instances, a time window, and a threshold for the number of prediction failure instances triggering prediction failure events within the time window; obtain a performance monitoring report based on the number of prediction failure instances occurring within the time window; and output second signaling instructing adjustments to one or more parameters based on the performance monitoring report.

[0028] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for outputting beamspace information indicating a set of performance monitoring resources, receiving signaling for beamspace filters, or both. Attached Figure Description

[0029] Figure 1 An example of a wireless communication system that supports downlink beam performance reporting for UE measurements according to one or more aspects of this disclosure is shown.

[0030] Figure 2 An example of a wireless communication system that supports downlink beam performance reporting for UE measurements according to one or more aspects of this disclosure is shown.

[0031] Figure 3 An example of a resource graph for a downlink beam performance report supporting UE measurements, according to one or more aspects of this disclosure, is shown.

[0032] Figure 4 An example of a process flow for a downlink beam performance report that supports UE measurements, according to one or more aspects of this disclosure, is shown.

[0033] Figure 5 and Figure 6A block diagram of an apparatus supporting downlink beam performance reporting for UE measurements is shown, according to one or more aspects of this disclosure.

[0034] Figure 7 A block diagram of a communication manager supporting downlink beam performance reporting for UE measurements, according to one or more aspects of this disclosure, is shown.

[0035] Figure 8 A diagram of a system including a downlink beam performance report supporting UE measurements is shown, according to one or more aspects of this disclosure.

[0036] Figure 9 and Figure 10 A block diagram of an apparatus supporting downlink beam performance reporting for UE measurements is shown, according to one or more aspects of this disclosure.

[0037] Figure 11 A block diagram of a communication manager supporting downlink beam performance reporting for UE measurements, according to one or more aspects of this disclosure, is shown.

[0038] Figure 12 A diagram of a system including a downlink beam performance report supporting UE measurements is shown, according to one or more aspects of this disclosure.

[0039] Figures 13 to 15 A flowchart illustrating a method for reporting downlink beam performance in support of UE measurements according to one or more aspects of this disclosure is shown. Detailed Implementation

[0040] In wireless communication systems, network entities and user equipment (UEs) may expect to use wireless communication resources associated with high power and high quality. To determine the highest quality resource, the network entity may transmit one or more reference signals (RS), and the UE may measure one or more performance monitoring metrics associated with the transmitted RS, such as the reference signal received power (RSRP). The UE may predict the RSRP associated with another resource set (e.g., beam set A) based on measurements for one resource set (e.g., beam set B). In some examples, the network entity may request the UE to monitor the difference (e.g., in decibels (dB)) between the measured RSRP and the predicted RSRP associated with the target resource. In some examples, the network entity may configure a threshold RSRP difference for the UE, allowing the UE to determine whether to report a monitoring message to the network entity based on the difference between the measured RSRP and the predicted RSRP exceeding the RSRP difference threshold.

[0041] In some instances, the RSRP difference threshold may depend on the RSRP region. For example, in a high RSRP region (e.g., the cell center), a few dB of RSRP difference may not significantly impact throughput performance, and a high RSRP difference threshold may be appropriate. In another example, in a low RSRP region (e.g., the cell edge), a few dB of RSRP difference may significantly impact throughput performance, and a low RSRP difference threshold may be appropriate. Furthermore, different UEs may have different receive sensitivities and decoding algorithms with varying levels of complexity. Therefore, an RSRP region-specific RSRP difference threshold may be insufficient for some UEs within the RSRP region, or overly complex for others. In other words, more UE-specific performance monitoring of direct throughput performance may be desired.

[0042] In some examples, network entities can configure an error rate threshold, a time window, and a threshold for the number of predicted failure instances that trigger a predicted failure event within that time window for the UE. The UE can measure one or more RSs and determine the error rate for each of the one or more RSs. The UE can generate a performance monitoring report based on the number of performance failure instances occurring within the time window, and can send the performance monitoring report based on the number of performance failure instances exceeding a predicted failure instance number threshold. Additionally or alternatively, the UE can identify the beamspace information, received beamspace filter, or both for the set of performance monitoring resources based on beamspace information for a subset of the predicted target resources from previous performance monitoring reports.

[0043] Downlink beam performance prediction using this type of UE measurement can offer several advantages over alternative methods. For example, alternative network-based monitoring methods can access the UE-side predicted performance using the error rate of Physical Downlink Shared Channel (PDSCH) decoding, where corresponding PDSCH transmissions can be sent based on the transmit beams reported via the UE prediction results report. However, based on the frequency of PDSCH scheduling, such methods may introduce latency. That is, if PDSCH transmissions are not scheduled sufficiently (e.g., if there are long gaps between PDSCH bursts), network entities may be unable to identify potential performance degradation in UE-side beam prediction. For these and other reasons, prediction and monitoring of UE measurements, used as a complement to or alternative to network-based monitoring, can experience improved communication reliability, reduced latency, more efficient use of communication resources, and improved coordination between devices compared to network-based monitoring methods.

[0044] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are then described in the context of resource diagrams and process flows. The aspects of this disclosure are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to downlink beam performance reports measured by the UE, and are further described with reference to these apparatus diagrams, system diagrams, and flowcharts.

[0045] Figure 1 An example of a wireless communication system 100 supporting downlink beam performance reporting for UE measurements according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 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.

[0046] 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 communication link 125 (e.g., a radio frequency (RF) access link). 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 communication link 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).

[0047] 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 Examples of UE 115 are illustrated herein. The UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including UE 115 or network entity 105), such as... Figure 1 As shown.

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

[0049] 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 backhaul communication link 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 link 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) or 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.

[0050] One or more network entities in network entity 105 or network equipment 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, evolved 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 evolved node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in a converged (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 (e.g., network entity 105 or a single RAN node, such as base station 140).

[0051] 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 a protocol stack physically or logically distributed across multiple network entities (e.g., network entity 105) such as an Integrated Access and 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) such as CU 160, a distributed unit (DU) such as DU 165, a radio unit (RU) such as RU 170, a RAN intelligent controller (RIC) such as RIC 175 (e.g., a near real-time RIC (near RTRIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system such as SMO system 180, or any combination thereof. RU 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0052] 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, or 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 (e.g., one or more CUs) may connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or some combination thereof, and DU 165, RU 170, or both may 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 may each be at least partially controlled by CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between DU 165 and RU 170, such that DU 165 may support one or more layers of the protocol stack, and RU 170 may support one or more different layers of the protocol stack. DU 165 may (e.g., via one or more different RUs, such as RU 170) support one or more different cells. 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 DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to 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 is supported by the corresponding network entities (e.g., one or more network entities in network entity 105) communicating via such communication links.

[0053] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities in network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor entities (e.g., IAB donors) may communicate with one or more additional devices (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 one or more DUs (e.g., DU 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., referred to as a virtual IAB-MT (vIAB-MT)) for access to IAB node 104 via DU 165 of IAB node 104 (e.g., of RU 170). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) that support 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., IAB node 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0054] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support the tests 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., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

[0055] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some 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 a variety of objects such as appliances, vehicles, or meters.

[0056] The UE 115 described herein can communicate with various types of devices, such as the UE 115 which sometimes operates as a relay, and network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0057] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more 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 PHY 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 PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, 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, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0058] 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, where 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 may 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.

[0059] 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, in response This can represent the supported subcarrier spacing, and The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for 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).

[0060] 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 also be 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, such as wireless communication system 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.

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

[0062] 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 public search space set configured to transmit control information to UE115 (e.g., one or more UEs), or it may include a UE-specific search space set configured to transmit control information to UE115 (e.g., a particular UE).

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

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

[0065] In some examples, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as D2D communication link 135) (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group performing D2D communication 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 UEs 115 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, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to one or more UEs within the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

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

[0067] 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 High 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 distances (e.g., less than one hundred kilometers).

[0068] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). 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 based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

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

[0070] 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 by the transmitting or receiving 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).

[0071] 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, RS, 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.

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

[0073] 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 a combined beam 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 RS (e.g., cell-specific RS, channel state information RS (CSI-RS)), which may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) in one or more directions, UE 115 may use similar techniques to transmit signals multiple times in different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0074] 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, RS, 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 applied to signals received at multiple antenna elements of the antenna array (e.g., different directional listening weight sets); or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0075] In wireless communication system 100, network entity 105 and UE 115 may wish to use wireless communication resources associated with high power and high quality. To determine the highest quality resource, network entity 105 may transmit one or more RSs, and UE 115 may measure the RSRP associated with the transmitted RSs. UE 115 may predict the RSRP associated with another resource set (e.g., beam set A) based on measurements for one resource set (e.g., beam set B). In some examples, network entity 105 may request UE 115 to monitor the difference (e.g., in decibels dB) between the measured RSRP and the predicted RSRP associated with the target resource. In some examples, network entity 105 may configure a threshold RSRP difference for UE 115, such that UE 115 may determine whether to report a monitoring message to network entity 105 based on the difference between the measured RSRP and the predicted RSRP exceeding the RSRP difference threshold.

[0076] In some instances, the RSRP difference threshold may depend on the RSRP region. For example, in a high RSRP region (e.g., the cell center), a few dB of RSRP difference may not significantly impact throughput performance, and a high RSRP difference threshold may be appropriate. In another example, in a low RSRP region (e.g., the cell edge), a few dB of RSRP difference may significantly impact throughput performance, and a low RSRP difference threshold may be appropriate. Furthermore, different UEs 115 may have different receive sensitivities and decoding algorithms with varying levels of complexity. Therefore, an RSRP region-specific RSRP difference threshold may be insufficient for some UEs 115 within the RSRP region, or overly complex for others. In other words, more UE-specific performance monitoring of direct throughput performance may be desired.

[0077] In some examples, network entity 105 can configure UE 115 with an error rate threshold for triggering predicted failure instances, a time window, and a threshold for the number of predicted failure instances that trigger a predicted failure event within that time window. UE 115 can measure one or more RSs and determine the error rate for each of the one or more RSs. UE 115 can generate a performance monitoring report based on the number of performance failure instances occurring within the time window and can send the performance monitoring report to network entity 105 based on the number of performance failure instances exceeding the predicted failure instance number threshold. Additionally or alternatively, UE 115 can identify the beamspace information, received beamspace filter, or both for the set of performance monitoring resources based on beamspace information, received beamspace filter, or both from a subset of the predicted target resources in previous performance monitoring reports. Such UE-measured downlink beam performance prediction can yield several benefits over alternative methods. For example, UE-measured predictions can experience lower latency and improved reliability compared to network-based monitoring methods.

[0078] Figure 2 An example of a wireless communication system 200 supporting downlink beam performance reporting for UE measurements according to one or more aspects of this disclosure is shown. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100. For example, the wireless communication system 200 includes a UE 115-a and a network entity 105-a, which may be references Figure 1 Examples of the corresponding devices described herein. Additionally or alternatively, UE 115-a and network entity 105-a may each be examples of other types of wireless devices (such as IAB nodes or other types of transmitters or receivers). Therefore, although aspects of this disclosure have been described with reference to UE 115 and network entity 105, it should be understood that the described techniques may be performed by wireless devices other than UE 115 and network entity 105. As described herein, operations performed by UE 115-a and network entity 105-a may be performed by UE 115, network entity 105, or another wireless device, respectively, and the examples shown should not be construed as limiting.

[0079] Network entity 105-a and UE 115-a can use downlink transmit beam prediction (e.g., UE-side model or network-side model) as part of beam management operations. For example, spatial domain downlink transmit beam prediction can predict the beam quality (e.g., RSRP value) of a first set of beams (e.g., beam set A) based on measurements of a second set of beams (e.g., beam set B). In another example, temporal downlink transmit beam prediction can predict the beam quality (e.g., RSRP value) of beam set A based on historical measurements of beam set B. That is, a certain number of predictions for a certain number of future time instances can be obtained based on the output of an artificial intelligence (AI) or machine learning (ML) model, where each prediction is for each time instance. Signaling and mechanisms can be used to facilitate lifecycle management operations for beam management use cases. Methods (if identified) for ensuring consistency between training and inference regarding inference at UE 115-a, as well as a common framework design for supporting both spatial domain downlink transmit beam prediction and temporal downlink transmit beam prediction, may be desired.

[0080] To determine high-quality resources for wireless communication, network entity 105-a may transmit one or more RSs, and UE 115-a may measure the RSRP associated with the transmitted RSs. UE 115-a may predict the RSRP associated with another resource set (e.g., beam set A) based on measurements for one resource set (e.g., beam set B). In some examples, network entity 105-a may request UE 115-a to monitor the difference (e.g., in dB) between the measured RSRP and the predicted RSRP associated with the predicted target resource. For example, UE 115-a may monitor the RSRP difference between the first K RSs (based on RSRP) and the first K predicted target resources (e.g., where K may be three). In some examples, network entity 105-a can configure a threshold RSRP difference for UE 115-a, so that UE 115-a can determine whether to report a monitoring message to network entity 105-a based on whether the difference between the measured RSRP and the predicted RSRP exceeds the RSRP difference threshold within the time window configured by the network.

[0081] Performance monitoring via relative RSRP difference can present several complexities and challenges. For example, the RSRP difference threshold can vary depending on the RSRP region. In a high RSRP region (e.g., cell center), a few dB difference in RSRP may not significantly impact throughput performance, and a high RSRP difference threshold might be appropriate. Conversely, in a low RSRP region (e.g., cell edge), a few dB difference in RSRP may significantly impact throughput performance, and a low RSRP difference threshold might be appropriate. Furthermore, different UEs may have different receive sensitivities and decoding algorithms with varying levels of complexity. Therefore, an RSRP region-specific RSRP difference threshold may be insufficient for some UEs within the RSRP region, or overly complex for others. In other words, more UE-specific performance monitoring of direct throughput performance may be desired.

[0082] In some specific implementations, network entity 105-a and UE 115-a can support downlink beam performance reporting operations measured by the UE based on error rates. For example, UE 115-a can convert the measured RSRP (e.g., L1-RSRP) on the transmitted RS into an error rate (e.g., assumed block error rate (BLER)), where the transmitted RS can be associated with a prediction target resource corresponding to the UE-side beam prediction operation. Network entity 105-a can configure UE 115-a to report instances where the error rate exceeds a threshold. UE 115-a can also adaptively identify the Transmission Configuration Indication (TCI) state associated with the transmitted RS based on the TCI state associated with the best prediction target resource (e.g., based on RSRP or BLER) that UE 115-a has already reported to network entity 105-a.

[0083] In some implementations, network entity 105-a may request UE 115-a to predict the L1-RSRP or L1-SINR of the top K resources (based on L1-RSRP or L1-Signal-to-Interference-plus-Noise Ratio (SINR)) of a set of candidate target resources (e.g., set A beam, via Synchronization Signal Block (SSB), CSI-RS, or virtual resources), and further report the prediction results for one or more of the candidate target resources (e.g., via CSI reporting, Media Access Control-Control Element (MAC-CE), or RRC). The prediction input may be based on measurements associated with measurement resources signaled by the network (e.g., set B beam, via SSB or CSI-RS resources). In some examples, the prediction may be associated with one or more time slots no later than the time slot carrying the prediction result report, and the measurement resources may not overlap with or only partially overlap with the target resources (e.g., purely spatial prediction). In some other examples, a prediction may be associated with one or more time slots later than the time slot carrying the prediction results report, where the target resource being predicted is the same as the measurement resource (e.g., purely temporal prediction). In still other examples, a prediction may be associated with one or more time slots later than the time slot carrying the prediction results report, where the measurement resource may not overlap with or only partially overlap with the target resource being predicted (e.g., spatial and temporal prediction).

[0084] In some implementations, network entity 105-a can output, and UE 115-a can receive, signaling instructing performance monitoring configuration 205 for downlink beam performance reporting for a set of predicted target resources based on a set of performance monitoring resources. In some examples, the performance monitoring resources can be SSB resources or CSI-RS resources. Performance monitoring resources can be scheduled based on the transmission periodicity of the predicted target resources (e.g., periodically or semi-periodically scheduled resources), or triggered based on the same transmission timing as the predicted target resources (e.g., for non-periodically scheduled resources). The performance reporting configuration may include an error rate threshold (e.g., a hypothetical BLER threshold) that can trigger a predicted failure instance, a time window, and a threshold for the number of predicted failure instances that can trigger a predicted failure event within that time window.

[0085] In some examples, UE 115-a may receive (e.g., as part of performance monitoring configuration 205) an indication of a beam prediction report identifier (ID) associated with an error rate threshold, a time window, a prediction failure instance count threshold, or a combination thereof. The beam prediction report ID may also be associated with beamspace information for a set of performance monitoring resources based on a subset of the set of prediction target resources from previous performance monitoring reports, receive beamspace filters for the set of performance monitoring resources based on a subset of the set of prediction target resources from previous performance monitoring reports, other parameters included in performance monitoring configuration 205, or combinations thereof. In some examples, the beam prediction report ID may be a CSI report setting ID, where a CSI report can be used as a prediction result report. Different beam prediction report IDs may be signaled in association with different sets of parameters (e.g., in different performance monitoring configurations 205).

[0086] In some examples, UE 115-b may receive (e.g., as part of signaling indicating configuration) an indication of a serving cell or BWP associated with an error rate threshold, a time window, a threshold for the number of predicted failed instances, or a combination thereof. The serving cell or BWP may also be associated with beamspace information for a set of performance monitoring resources based on a subset of the set of predicted target resources from previous performance monitoring reports, receive beamspace filters for the set of performance monitoring resources based on a subset of the set of predicted target resources from previous performance monitoring reports, other parameters included in performance monitoring configuration 205, or a combination thereof. The signaling parameter may be associated with any beam prediction report ID corresponding to the serving cell or BWP.

[0087] In some examples, network entity 105-a may output, and UE 115-a may receive (e.g., as part of performance monitoring configuration 205), an indication of the number of consecutive time slots, subframes, frames, or other time periods defining a time window. In some cases, the time window may be a sliding window. In other cases, the time window may be a non-sliding window, and the starting time slot, subframe, or frame of each time window may be included in performance monitoring configuration 205 or predefined in a standard. In some examples, network entity 105-a may output, and UE 115-a may receive (e.g., as part of performance monitoring configuration 205) an indication of a timer identifying a time window. This indication may include the start point of the timer, the end point of the timer, the duration of the timer, or any combination thereof. Network entity 105-a may activate the start of the timer (e.g., by signaling parameters in performance monitoring report 215). The timer may be reset when a prediction failure instance occurs.

[0088] In some examples, a set of candidate physical downlink control channel (PDCCH) and PDSCH (PDxCH) structure assumptions can be predefined (e.g., in a lookup table or in a standard). For example, combinations of modulation and decoding schemes, bandwidth, aggregation levels, number of symbols or slots, and energy per resource element (EPRE) offsets for reference SSBs or CSI-RS can be predefined. The target PDxCH structure assumptions can vary depending on the target throughput that network entity 105-a may expect UE 115-a to achieve. Therefore, performance monitoring configuration 205 may include options for selecting downwards from the predefined set of PDxCH assumptions, allowing UE 115-a to calculate error rate values ​​based on the signaled PDxCH assumptions.

[0089] Network entity 105-a can output, and UE 115-a can receive, one or more RS 210s associated with one or more performance monitoring resources in a set of performance monitoring resources. UE 115-a can measure one or more performance monitoring resources at one or more measurement times. In some examples, UE 115-a can calculate an error rate value based on the measurement results associated with one or more measurement times (e.g., assuming BLER). If the error rate value associated with all performance monitoring resources at a specific measurement time corresponding to a performance monitoring resource exceeds an error rate threshold (e.g., an error rate threshold configured via performance monitoring configuration 205, or an error rate threshold predefined in other ways), a predicted failure instance can be triggered. If, within a time window (e.g., a time window configured via performance monitoring configuration 205, or a time window predefined in other ways), the total number of predicted failure instances exceeds a predicted failure instance number threshold (e.g., a predicted failure instance number threshold configured via performance monitoring configuration 205, or a predicted failure instance number threshold predefined in other ways), a predicted failure event can be triggered.

[0090] To facilitate the measurement of RS 210 at a specific measurement time associated with a specific performance monitoring resource, UE115-a can identify information associated with the measurement time and performance monitoring resource. In some examples, the identified information may be TCI status or quasi-co-location (QCL) information (e.g., Type A, Type B, Type C, or Type D QCL information).

[0091] In the first example, UE 115-a can identify the beamspace information of the set of performance monitoring resources based on beamspace information of a subset of the set of predicted target resources from previous performance monitoring reports. That is, previous monitoring reports (e.g., prediction result reports, CSI reports, or signaling associated with CSI reports, such as CSI resource settings) are signaled between UE 115-a and network entity 105-a. CSI-AssociatedReportConfigInfoAlternatively, MAC-CE (or activation of CSI reporting) can be used to report prediction results from UE 115-a. Beamspace information for the set of performance monitoring resources may include QCL source RS information for the set of performance monitoring resources. Beamspace information for a subset of the set of predicted target resources from previous performance monitoring reports may include quasi-co-located source RS information for a subset of the set of predicted target resources from previous monitoring reports. The subset of the set of predicted target resources may be the top N predicted target resources based on predicted L1-RSRP or L1-SINRs associated with the most recent prediction result report from UE 115-a, such that the beamspace information can change over time as the top N predicted target resources change over time. The value of N (e.g., three) may be configured via performance monitoring configuration 205 or otherwise pre-configured. In some cases, a mapping between the top N predicted target resources and performance monitoring resources may be predefined (e.g., a one-to-one mapping based on ascending order of the two sets of resources).

[0092] Additionally or alternatively, in the second example, UE 115-a may identify the receive beamspace filter for the set of performance monitoring resources based on the receive beamspace filter for a subset of the set of predicted target resources from previous performance monitoring reports (e.g., prediction result reports sent by UE 115-a and obtained by network entity 105-a). The subset of the set of predicted target resources may be the top N predicted target resources based on the predicted L1-RSRP or L1-SINR associated with the most recent prediction result report from UE 115-a, such that the beamspace information can change over time as the top N predicted target resources change over time. The value of N (e.g., three) may be configured via performance monitoring configuration 205 or otherwise pre-configured. In some cases, a mapping between the top N predicted target resources and performance monitoring resources may be predefined (e.g., a one-to-one mapping based on ascending order of the two sets of resources). The identification of the receive beamspace filter can be based on the identification of the beamspace information in the first example, or it can be independent of the identification of the beamspace information in the first example. In some examples, the identification of the receive beamspace filter can be based on the fact that the performance monitoring resource and the corresponding predicted target resource from the most recent prediction results report are of type D QCL.

[0093] When the number of target resources to be predicted is large, transmitting performance monitoring resources via all associated transmit beams may consume an excessive amount of transmit beams, thereby introducing latency and degrading communication quality between UE 115-a and network entity 105-a. Therefore, it may be desirable to more adaptively identify transmit beams by identifying beam space information in the first example and by identifying receive beam space filters in the second example.

[0094] In the third example, network entity 105-a may output, and UE 115-a may receive, signaling indicating beamspace information (e.g., TCI status or QCL source RS information) for a set of performance monitoring resources, receive beamspace filters, or both (e.g., via RRC, MAC-CE, or downlink control information (DCI)). For example, network entity 105-a may not be able to decode the latest beam prediction result report from UE 115-a, and therefore may use an alternative beam to send RS 210 via performance monitoring resources. In this case, UE 115-a may not be able to adaptively adopt beamspace information or receive beamspace filters (as in the first and second examples), and UE 115-a may rely on updated parameters signaled from network entity 105-a. For example, network entity 105-a may indicate a TCI status ID or (e.g., type A, type B, type C, or type D) QCL source RS to UE 115-a based on SSB resources or CSI-RS resources. In another instance, network entity 105-a may indicate one or more prediction target resource IDs associated with the UE-side beam prediction process. That is, UE 115-a may identify the receive beam spatial filter for the corresponding performance monitoring resource based on the predictive receive beam spatial filter from the most recent prediction result report associated with the prediction target resource ID indicated by network entity 105-a.

[0095] In some examples, network entity 105-a may output, and UE 115-a may receive, signaling including a preemption indication (e.g., via RRC, MAC-CE, or DCI) that configures UE 115-a to suppress one or more performance measurement opportunities associated with a set of one or more performance measurement resources. When determining the number of predicted failure instances within a time window, UE 115-a may remove (e.g., ignore) one or more indicated performance measurement opportunities. This could be when network entity 105-a signals the SSB or periodic or semi-periodic CSI-RS as a performance monitoring resource. In some examples, network entity 105-a may instruct UE 115-a to measure one or more alternative performance measurement resources instead of one or more performance measurement opportunities associated with a set of one or more performance measurement resources. A preemption indication may be included when network entity 105-a fails to decode a beam prediction result report sent by UE 115-a, resulting in uncertainty regarding the highest quality beam used to output the performance monitoring resource and potential inaccuracies in identifying predicted failure instances.

[0096] UE 115-a can generate performance monitoring report 215 based on the number of performance failure instances occurring within a time window. For example, UE 115-a can generate performance monitoring report 215 based on the occurrence of a prediction failure event triggered by the total number of predicted failure instances exceeding a prediction failure instance number threshold. In another example, UE 115-a can suppress the generation of performance monitoring report 215 based on the absence of prediction failure events due to the total number of predicted failure instances being below the prediction failure instance number threshold.

[0097] Based on the number of performance failure instances occurring within a time window and based on the performance monitoring report 215 generated by UE 115-a, UE 115-a can send and network entity 105-a can receive the performance monitoring report 215. For example, UE 115-a can send the performance monitoring report 215 based on the occurrence of a predicted failure event triggered by the total number of predicted failure instances exceeding a predicted failure instance number threshold. In another example, UE 115-a can suppress the sending of the performance monitoring report 215 based on the absence of a predicted failure event due to the total number of predicted failure instances being below the predicted failure instance number threshold. UE 115-a can send the performance monitoring report 215 via MAC-CE, RRC, or one or more CSI reports. For example, network entity 105-a can schedule P / SP / AP CSI reports for UE 115-a to provide feedback on information associated with the performance monitoring report 215, where UE 115-a can indicate whether it has determined that a predicted failure event occurred within the time window associated with the CSI report timing.

[0098] Performance monitoring report 215 may include at least an indication of a prediction failure event associated with a performance monitoring resource that occurred during a time window. In some examples, performance monitoring report 215 may include an indication of one or more error rate values ​​exceeding an error rate threshold (e.g., assuming BLER). For example, performance monitoring report 215 may include: all error rate values ​​associated with all prediction failure instances associated with the performance monitoring resource; only the top M error rate values ​​associated with all prediction failure instances (where the value of M is defined in signaling from network entity 105-a or predefined in a standard); only the error rate values ​​associated with the last L prediction failure instances (where the value of L is defined in signaling from network entity 105-a or predefined in a standard); the error rate difference between the measured performance monitoring resource with the highest RSRP and the performance monitoring resource associated with the prediction target resource predicted by UE 115-a to have the highest RSRP (which can be identified based on the receive beam spatial filter identifying the set of performance monitoring resources); or a combination thereof. In some examples, the performance monitoring report 215 may include timing information associated with one or more prediction failure instances within a time window, such as the logical performance monitoring resource measurement timing ID or the time slot, subframe, or frame ID in which the prediction failure instance occurred. In some examples, the performance monitoring report 215 may include additional RS measurement information associated with one or more performance monitoring resources, such as the measured L1-RSRP associated with the performance monitoring resource in which the prediction failure instance occurred. In some examples, the performance monitoring report 215 may include the RSRP of the performance monitoring resource with the highest RSRP and the RSRP of the performance monitoring resource associated with the prediction target resource predicted by UE 115-a to have the highest RSRP (which can be identified based on the receive beam spatial filter identifying the set of performance monitoring resources). In some examples, the performance monitoring report 215 may include an indication of a beam prediction report ID, serving cell, or BWP associated with an error rate threshold, a time window, a prediction failure instance number threshold, or a combination thereof.

[0099] In some examples, each prediction failure instance can be based on all measured RSs associated with one or more performance monitoring resources in a set of performance monitoring resources exceeding an error rate threshold within a time window (e.g., rather than each prediction failure instance based on a single measurement timing). In some examples, the physical layer can report the occurrence of a prediction failure instance to the upper layer within UE 115-a. The shortest interval between two adjacent prediction failure instance indications from the physical layer to the upper layer can be predefined (e.g., in the standard) or controlled by network entity 105-a (e.g., via performance monitoring configuration 205).

[0100] In some examples, UE 115-a may suppress the transmission of performance monitoring report 215 based on the prediction that the number of failed instances does not exceed a threshold for the number of predicted failed instances. In some examples, based on performance monitoring report 215, network entity 105-a may output and UE 115-a may receive a second signaling indicating adjustments to one or more parameters.

[0101] In some examples, based on performance monitoring reports, network entity 105-a can output, and UE 115-a can receive, a second signaling indicating the adjustment of one or more parameters. For example, network entity 105-a can adjust, based on performance monitoring reports obtained from UE 115-a, one or more performance monitoring resources in a set of performance monitoring resources, one or more prediction target resources in a set of prediction target resources, an error rate threshold that can trigger a prediction failure instance, a time window, a prediction failure instance quality threshold that can trigger a prediction failure event within that time window, or another parameter.

[0102] In an alternative network-based downlink beam performance monitoring and reporting scheme, network entity 105-a can access the UE-side beam prediction performance using one or more error rates from PDSCH decoding. In this scheme, one or more corresponding PDSCH transmissions can be sent based on one or more transmit beams reported via one or more UE prediction result reports. However, the latency of such a scheme can depend on the frequency of PDSCH scheduling. For example, PDSCH transmissions may not be scheduled frequently enough, and network entity 105-a may not identify potential performance degradation in UE-side beam prediction. That is, PDSCHs may arrive in bursts, and network entity 105-a has limited opportunities to perform downlink beam performance monitoring between such bursts. Such problematic beam prediction results may lead to a degraded PDSCH performance for upcoming bursts. Additionally or alternatively, the UE-measured downlink beam performance monitoring and reporting introduced in this disclosure can access beam performance independently of the PDSCH scheduling frequency, resulting in reduced latency, improved reliability, and improved performance.

[0103] Figure 3 An example of resource diagram 300 supporting downlink beam performance reporting for UE measurements according to one or more aspects of this disclosure is shown. Resource diagram 300 can be implemented with reference to, respectively Figure 1 and Figure 2 The described wireless communication system 100 and wireless communication system 200 may be, or be implemented by, one or more aspects thereof. For example, resource diagram 300 may be derived from, as referenced Figure 1 and Figure 2 The described network entity 105 and UE 115 implementations support downlink beam performance reporting measured by the UE.

[0104] For example, network entity 105 can configure a set 305 of prediction target resources for UE 115, such as prediction target resource 305-a associated with a first measurement timing, prediction target resource 305-b associated with a second measurement timing, prediction target resource 305-c associated with a third measurement timing, and prediction target resource 305-d associated with a fourth measurement timing. Network entity 105 can configure UE 115 to predict the RSRP, SINR, or error rate (e.g., assuming BLER) associated with each prediction target resource 305, and report the results in a prediction result report (which may be an example of a performance monitoring report).

[0105] In some examples, network entity 105 may output and UE 115 may receive signaling that instructs the configuration of downlink beam performance for UE measurements of the set 305 of the set of performance monitoring resources 310, which is at least in part based on the set of performance monitoring resources 310 (such as performance monitoring resource 310-a associated with prediction target resource 305-a, performance monitoring resource 310-b associated with prediction target resource 305-b, performance monitoring resource 310-c associated with prediction target resource 305-c, and performance monitoring resource 310-d associated with prediction target resource 305-d).

[0106] In some cases, performance monitoring resources 310 may be a subset of the predicted target resources 305. For example, performance monitoring resources 310-a may be the first K resources (e.g., according to RSRP) of the predicted target resources 305-a associated with the first monitoring timing, where K may be configured by network entity 105 (e.g., K=3). That is, UE 115 may have already indicated in a previous prediction result report that the second, fifth, and sixth resources of the predicted target resources 305-a are the first 3 resources according to RSRP, and these three resources may be performance monitoring resources 310-a used for the downlink beam performance report measured by the current UE.

[0107] UE 115 can measure one or more RSs associated with one or more performance monitoring resources 310 and determine an error rate 315 for each of the one or more RSs. For example, error rate 315-a may correspond to an RS associated with performance monitoring resource 310-a, error rate 315-b may correspond to an RS associated with performance monitoring resource 310-b, error rate 315-c may correspond to an RS associated with performance monitoring resource 310-c, and error rate 315-d may correspond to an RS associated with performance monitoring resource 310-d.

[0108] In some examples, the configuration may include an error rate threshold 320 for triggering a predicted failure instance, a time window 325, and a threshold for the number of predicted failure instances that trigger a predicted failure event within that time window 325. The UE 115 may determine whether a predicted failure instance has occurred at each measurement time based on the error rate threshold 320. In some examples, a predicted failure instance may be triggered at a measurement time if any error rate 315 associated with the measurement time exceeds the error rate threshold 320, such that the predicted failure instance is associated with each of performance monitoring resources 310-a, 310-b, 310-c, and 310-d. In some examples, a predicted failure instance may be triggered at a measurement time if a specific number or percentage of the error rate 315 associated with the measurement time exceeds the error rate threshold 320, such that the predicted failure instance is associated with performance monitoring resources 310-b, 310-c, and 310-d, but not with performance monitoring resource 310-a. In some examples, a predicted failure instance can be triggered at the measurement time by all error rates 315 associated with the measurement time exceeding the error rate threshold 320, such that the predicted failure instance is associated with performance monitoring resources 310-b and 310-d, but not with performance monitoring resources 310-a and 310-c.

[0109] UE 115 can generate a performance monitoring report based on the number of performance failure instances occurring within time window 325, and can send a performance monitoring report based on the number of performance failure instances exceeding a predicted failure instance count threshold. In other words, UE 115 can generate and send a performance monitoring report based on the occurrence of a predicted failure event triggered by the number of performance failure instances within time window 325 exceeding a configured predicted failure instance count threshold. For example, if error rates 315-b and 315-d both trigger predicted failure instances within time window 325 and the predicted failure instance count threshold is one, then a predicted failure event can be triggered, and UE 115 can generate and send a performance monitoring report.

[0110] In some examples, UE 115 can suppress the sending of performance monitoring reports based on the fact that the number of performance failure instances in time window 325 does not exceed a configured threshold for the number of predicted failure instances. For example, if error rates 315-b and 315-d both trigger predicted failure instances in time window 325 and the threshold for the number of predicted failure instances is three, then the predicted failure event may not be triggered, and UE 115 can either generate or suppress the generation of performance monitoring reports or suppress the sending of performance monitoring reports.

[0111] In some examples, network entity 105 may output, and UE 115 may receive, signaling indicating beamspace information (e.g., TCI status or QCL source RS information) for a set 305 of performance monitoring resources, receive beamspace filters, or both (e.g., via RRC, MAC-CE, or DCI). For example, network entity 105 may not be able to decode a recent beam prediction result report from UE 115 regarding the predicted target resource 305-d, and therefore may use an alternative beam to transmit RS via performance monitoring resource 310-d. In this case, UE 115 may not be able to adaptively adopt beamspace information or receive beamspace filters, and UE 115 may rely on updated parameters signaled from network entity 105. For example, network entity 105 may indicate a TCI status ID or (e.g., type A, type B, type C, or type D) QCL source RS to UE 115 based on SSB resources or CSI-RS resources. In another instance, network entity 105 may indicate one or more prediction target resource IDs associated with the UE-side beam prediction process. That is, UE 115 may identify the receive beam spatial filter for the corresponding performance monitoring resource 310-d based on the predictive receive beam spatial filter from the most recent prediction result report associated with the prediction target resource ID indicated by network entity 105.

[0112] In some examples, network entity 105 may output, and UE 115 may receive (e.g., as part of a performance monitoring configuration), an indication of the number of consecutive time slots, subframes, frames, or other time periods defining time window 325. In some cases, time window 325 may be a sliding window. In other cases, time window 325 may be a non-sliding window, and the starting time slot, subframe, or frame for each time window 325 may be included in the performance monitoring configuration or predefined in a standard. In some examples, network entity 105 may output, and UE 115 may receive (e.g., as part of a performance monitoring configuration) an indication of a timer identifying time window 325. This indication may include the start point of the timer, the end point of the timer, the duration of the timer, or any combination thereof. Network entity 105 may activate the start of the timer (e.g., by signaling parameters in a performance monitoring report). The timer may be reset when a prediction failure instance occurs.

[0113] Alternatively or additionally, UE 115 may identify the beamspace information, received beamspace filter, or both for the set 310 of performance monitoring resources based on beamspace information for a subset of the predicted target resources 305 from previous performance monitoring reports. Such downlink beam performance prediction by UE measurements can yield several advantages over alternative methods. For example, predictions by UE measurements can experience lower latency and improved reliability compared to network-based monitoring methods.

[0114] Figure 4 An example of a process flow 400 supporting a downlink beam performance report for UE measurement according to one or more aspects of this disclosure is shown. In some examples, process flow 400 may be implemented by wireless communication system 100 and wireless communication system 200 and resource diagram 300, or aspects thereof may be implemented. For example, process flow 400 includes network entity 105-b (e.g., a first wireless device) and UE 115-b (e.g., a second wireless device), which may be references Figure 1 and Figure 2 Examples of the corresponding devices described. According to process flow 400, UE 115-b may perform an enhanced nonlinear correction process on the data signal. The following alternative examples may be implemented, some of which may be performed in a different order than described, or not at all. In some cases, steps may include additional features not mentioned below, or other steps may be added. Although UE 115-b and network entity 105-b are shown performing the operations of process flow 400, some aspects of some operations may also be performed by one or more other wireless devices.

[0115] At 405, network entity 105-b can output, and UE 115-b can receive, signaling instructing for the configuration (e.g., performance report configuration) of a downlink beam performance report for a set of UE measurements against a set of target resources based on a set of performance monitoring resources. The performance report configuration may include an error rate threshold that can trigger a prediction failure instance, a time window, and a threshold for the number of prediction failure instances that can trigger a prediction failure event within that time window. In some examples, the error rate threshold may indicate the hypothetical BLER value that triggers the prediction failure instance.

[0116] Network entity 105-b and UE 115-b can associate parameters in a specific configuration with an ID. For example, the network entity can output, and UE 115-b can receive (e.g., as part of signaling indicating configuration), an indication of a beam prediction report ID associated with an error rate threshold, a time window, a predicted failure instance count threshold, or a combination thereof. Additionally or alternatively, UE 115-b can receive (e.g., as part of signaling indicating configuration) an indication of a serving cell or BWP associated with an error rate threshold, a time window, a predicted failure instance count threshold, or a combination thereof.

[0117] Configuration can define a time window. For example, UE 115-b can receive (e.g., as part of signaling indicating configuration) an indication of the number of consecutive time slots, subframes, frames, or other time periods defining the time window. In some cases, the time window can be a sliding window, while in others it can be a non-sliding window. In another example, UE 115-b can receive (e.g., as part of signaling indicating configuration) an indication of a timer that identifies the time window. This indication may include the start point of the timer, the end point of the timer, the duration of the timer, or any combination thereof.

[0118] At 410, network entity 105-b can output and UE 115-b can receive one or more RSs associated with one or more performance monitoring resources in the set of performance monitoring resources.

[0119] At 415, UE 115-b can measure one or more RSs associated with one or more performance monitoring resources at one or more measurement times. To facilitate this measurement, UE 115-b can identify information associated with each measurement time and each performance monitoring resource. For example, UE 115-b can identify beamspace information for the set of performance monitoring resources based on beamspace information of a subset of the set of predicted target resources from previous performance monitoring reports. The beamspace information for the set of performance monitoring resources may include QCL source RS information for the set of performance monitoring resources. The beamspace information of a subset of the set of predicted target resources from previous performance monitoring reports may include QCL source RS information of a subset of the set of predicted target resources from previous monitoring reports.

[0120] In the second example, UE 115-b can identify the receive beamspace filter for the set of performance monitoring resources based on the receive beamspace filter for a subset of the set of predicted target resources from previous performance monitoring reports. In the third example, network entity 105-b can output, and UE 115-b can receive, signaling indicating beamspace information, receive beamspace filter, or both for the set of performance monitoring resources.

[0121] In some examples, network entity 105-b can output and UE 115-b can receive signaling including a preemption indication that configures UE 115-b to suppress one or more performance measurement opportunities associated with a set of one or more performance measurement resources.

[0122] At 420, UE 115-b can generate performance monitoring reports based on the number of performance failure instances occurring within a time window. For example, UE 115-b can generate performance monitoring reports based on the occurrence of predicted failure events, and can suppress the generation of performance monitoring reports based on the number of predicted failure instances occurring within a time window being lower than a predicted failure instance number threshold.

[0123] Performance monitoring reports may include indications of one or more error rate values ​​exceeding an error rate threshold (e.g., assuming BLER), timing information associated with one or more prediction failure instances within a time window, additional RS measurement information associated with one or more performance monitoring resources, or any combination thereof. In some examples, performance monitoring reports may include indications of beam prediction report IDs, serving cells, or BWPs associated with error rate thresholds, time windows, prediction failure instance count thresholds, or combinations thereof.

[0124] At point 425, UE 115-b can send, and network entity 105-b can receive, a performance monitoring report based on the number of predicted failure instances exceeding a predicted failure instance count threshold. Each predicted failure instance can be based on one or more measured RSs associated with one or more performance monitoring resources in the set of performance monitoring resources exceeding an error rate threshold. In some examples, each predicted failure instance can be based on all measured RSs associated with one or more performance monitoring resources in the set of performance monitoring resources exceeding an error rate threshold. The performance monitoring report can be sent via MAC-CE, RRC, one or more CSI reports, or a combination thereof. In some examples, UE 115-b can suppress report sending based on the number of predicted failure instances not exceeding a predicted failure instance count threshold.

[0125] In some examples, based on performance monitoring reports, network entity 105-b can output and UE 115-b can receive a second signaling indicating adjustments to one or more parameters.

[0126] Figure 5 A block diagram 500 of a device 505 supporting downlink beam performance reporting for UE measurements according to one or more aspects of this disclosure is shown. Device 505 may be an example of various aspects of a 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, 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).

[0127] 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, information channels related to downlink beam performance reports measured by the UE). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0128] 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 (e.g., control channels, data channels, information channels related to downlink beam performance reports measured by the UE), such as 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.

[0129] The communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be examples of components used to perform various aspects of a downlink beam performance report as described herein for UE measurements. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be able to perform one or more of the functions described herein.

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

[0131] Additionally or alternatively, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor (e.g., referred to as processor executable code). 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).

[0132] In some examples, the communication manager 520 may be configured to use or otherwise cooperate with the receiver 510, 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 be integrated in combination with the receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0133] For example, the communication manager 520 can, is configured, or is operable to support components for receiving signaling that instructs the configuration of a downlink beam performance report for a set of predicted target resources for UE measurements based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering predicted failure instances, a time window, and a threshold for the number of predicted failure instances that trigger predicted failure events within the time window. The communication manager 520 can, is configured, or is operable to support components for measuring one or more RSs associated with one or more performance monitoring resources in the set of performance monitoring resources. The communication manager 520 can, is configured, or is operable to support components for generating performance monitoring reports based on the number of performance failure instances occurring within a time window.

[0134] By including or configuring a communication manager 520 according to an example as described herein, device 505 (e.g., controlling receiver 510, transmitter 515, communication manager 520 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for more efficient use of communication resources.

[0135] Figure 6 A block diagram 600 of a device 605 supporting downlink beam performance reporting for UE measurements according to one or more aspects of this disclosure is shown. 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, 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).

[0136] 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, information channels related to downlink beam performance reports measured by the UE). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0137] 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 related to downlink beam performance reports measured by the UE), 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.

[0138] Device 605 or its various components may be examples of various aspects of a downlink beam performance report for performing UE measurements as described herein. For example, communication manager 620 may include configuration component 625, RS component 630, performance monitoring and reporting component 635, 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 in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0139] Configuration component 625 is capable of, configured to, or operable to support components for receiving signaling that instructs configuration for a downlink beam performance report for a set of predicted target resources for UE measurements based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering predicted failure instances, a time window, and a threshold for the number of predicted failure instances that trigger predicted failure events within the time window. RS component 630 is capable of, configured to, or operable to support components for measuring one or more RSs associated with one or more performance monitoring resources in the set of performance monitoring resources. Performance monitoring reporting component 635 is capable of, configured to, or operable to support components for generating a performance monitoring report based on the number of performance failure instances occurring within a time window.

[0140] Figure 7A block diagram 700 of a communication manager 720 supporting downlink beam performance reporting for UE measurements according to one or more aspects of this disclosure is shown. The communication manager 720 may be an example of a communication manager 520, a communication manager 620, or aspects thereof as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of downlink beam performance reporting for UE measurements as described herein. For example, the communication manager 720 may include a configuration component 725, an RS component 730, a performance monitoring and reporting component 735, a beam space information component 740, a preemption component 745, 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).

[0141] Configuration component 725 is capable of, configured to, or operable to support components for receiving signaling that instructs configuration for a downlink beam performance report for a set of predicted target resources for UE measurements based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering predicted failure instances, a time window, and a threshold for the number of predicted failure instances that trigger predicted failure events within the time window. RS component 730 is capable of, configured to, or operable to support components for measuring one or more RSs associated with one or more performance monitoring resources in the set of performance monitoring resources. Performance monitoring reporting component 735 is capable of, configured to, or operable to support components for generating performance monitoring reports based on the number of performance failure instances occurring within a time window.

[0142] In some examples, the beam space information component 740 is capable of, configured to, or operable to support components for identifying beam space information for a set of performance monitoring resources based on a subset of beam space information from previous performance monitoring reports for a set of predicted target resources.

[0143] In some examples, beamspace information for a set of performance monitoring resources includes quasi-co-located source RS information for the set of performance monitoring resources. In some examples, beamspace information for a subset of the set of predicted target resources from previous performance monitoring reports includes quasi-co-located source RS information for a subset of the set of predicted target resources from previous performance monitoring reports.

[0144] In some examples, the beam space information component 740 is capable of, configured to, or operable to support a component for identifying a set of receive beam space filters for a set of performance monitoring resources based on a subset of the set of predicted target resources from previous performance monitoring reports.

[0145] In some examples, the beam space information component 740 is capable of, configured to, or operable to support components for receiving beam space information indicating a set of performance monitoring resources, receiving signaling for beam space filters, or both.

[0146] In some examples, performance monitoring reports include indications of one or more error rate values ​​that exceed an error rate threshold, timing information associated with one or more predicted failure instances within a time window, additional RS measurement information associated with one or more performance monitoring resources, or any combination thereof.

[0147] In some examples, the preemption component 745 is capable of, configured to, or able to operate to support components for receiving signaling including a preemption indication that configures the UE to suppress one or more performance measurement opportunities associated with a set of one or more performance measurement resources.

[0148] In some examples, to support receiving signaling, the performance monitoring and reporting component 735 is capable of, configured to, or able to operate to support components for receiving indications of beam prediction report IDs associated with an error rate threshold, a time window, a threshold for the number of prediction failure instances, or a combination thereof.

[0149] In some examples, in order to support receiving signaling, configuration component 725 is capable of, can be configured to, or is able to operate to support components for receiving indications of a serving cell or BWP associated with an error rate threshold, a time window, a predicted number of failed instances threshold, or a combination thereof.

[0150] In some examples, in order to support the reception of signaling, configuration component 725 is capable of, can be configured to, or is operable to support components for receiving an indication of the number of consecutive time slots, subframes, frames, or other time periods within a defined time window, wherein the time window includes a sliding window or a non-sliding window.

[0151] In some examples, in order to support receiving signaling, configuration component 725 is capable of, can be configured to, or is operable to support components for receiving indications of a timer that identifies a time window, wherein the indications include the start point of the timer, the end point of the timer, the duration of the timer, or any combination thereof.

[0152] In some examples, to support the generation of performance monitoring reports, the performance monitoring report component 735 is capable of, configured to, or operable to support components for sending performance monitoring reports based on the number of predicted failed instances exceeding a threshold, wherein each predicted failed instance is based on one or more measured RSs associated with one or more performance monitoring resources in a set of performance monitoring resources exceeding an error rate threshold.

[0153] In some examples, each prediction failure instance is based on all measured RSs associated with one or more performance monitoring resources in the set of performance monitoring resources exceeding the error rate threshold.

[0154] In some examples, to support the sending of reports, the performance monitoring report component 735 is capable of, configured to, or able to operate to support components for sending performance monitoring reports via MAC-CE, RRC, one or more CSI reports, or a combination thereof.

[0155] In some examples, to support the generation of performance monitoring reports, the performance monitoring report component 735 can be configured or operated to support a component for suppressing the sending of reports based on the prediction that the number of failed instances does not exceed a threshold for the number of failed instances.

[0156] In some examples, the error rate threshold indicates the hypothetical BLER value that triggers the prediction of failed instances.

[0157] In some examples, the configuration is associated with a request from a network entity for the UE to perform a prediction of a set of quality metrics used to predict target resources. In some examples, the predicted quality metrics are determined by the UE based on measurements of one or more reference signals individually scheduled by the network entity.

[0158] Figure 8 A diagram of a system 800 including a device 805 supporting downlink beam performance reporting for UE measurements, 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 other devices (e.g., network entity 105, UE 115, or a 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 (e.g., I / O controller 810), a transceiver 815, one or more antennas 825, at least one memory 830, code 835, and at least one processor 840. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 845).

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

[0160] In some cases, device 805 may include a single antenna. However, in other cases, device 805 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 815 may communicate bidirectionally via one or more antennas 825 using a wired or wireless link as described herein. For example, transceiver 815 may represent a wireless transceiver and be capable of bidirectional communication 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.

[0161] 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 code, computer-executable code, or processor-executable code, such as code 835. Code 835 may include 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 (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, at least one memory 830 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0162] At least one processor 840 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 840 may be configured to use a memory controller to operate a memory array. 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 memory (e.g., at least one memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting downlink beam performance reporting for UE measurements). 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 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. In some examples, at least one processor 840 may be a component of a processing system, which may refer to a system of machines, circuits (including, for example, one or both of processor circuitry (which may include at least one processor 840) and memory circuitry (which may include at least one memory 830)) or components that receive or obtain inputs and process those inputs to produce, generate, or obtain outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 840 or a processing system including at least one processor 840 may be configured, capable of being configured, or operable to cause device 805 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code 835 (e.g., processor-executable code) stored in at least one memory 830 or otherwise.

[0163] For example, the communication manager 820 can, is configured, or is operable to support components for receiving signaling that instructs the configuration of a downlink beam performance report for a set of predicted target resources for UE measurements based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering predicted failure instances, a time window, and a threshold for the number of predicted failure instances that trigger predicted failure events within the time window. The communication manager 820 can, is configured, or is operable to support components for measuring one or more RSs associated with one or more performance monitoring resources in the set of performance monitoring resources. The communication manager 820 can, is configured, or is operable to support components for generating performance monitoring reports based on the number of performance failure instances occurring within a time window.

[0164] By including or configuring a communication manager 820 according to an example as described herein, device 805 can support techniques for improving communication reliability, reducing latency, utilizing communication resources more efficiently, and improving coordination between devices.

[0165] In some examples, the communication manager 820 may be configured to use or otherwise coordinate 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 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 a downlink beam performance report as described herein by the UE, 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.

[0166] Figure 9 A block diagram 900 of a device 905 supporting downlink beam performance reporting for UE measurements according to one or more aspects of this disclosure is shown. 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, 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).

[0167] 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 passed 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.

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

[0169] The communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be examples of components used to perform various aspects of a downlink beam performance report as described herein for UE measurements. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be able to perform one or more of the functions described herein.

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

[0171] Additionally or alternatively, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor (e.g., referred to as processor executable code). 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).

[0172] In some examples, the communication manager 920 may be configured to use or otherwise cooperate with the receiver 910, 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 be integrated in combination with the receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0173] For example, the communication manager 920 can, is configured, or is operable to support components for outputting a first signaling that indicates a configuration for a downlink beam performance report for a set of predicted target resources based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering predicted failure instances, a time window, and a threshold for the number of predicted failure instances that trigger predicted failure events within the time window. The communication manager 920 can, is configured, or is operable to support components for obtaining a performance monitoring report based on the number of predicted failure instances occurring within the time window. The communication manager 920 can, is configured, or is operable to support components for outputting a second signaling that indicates adjustments to one or more parameters based on the performance monitoring report.

[0174] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., controlling receiver 910, transmitter 915, communication manager 920 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for more efficient use of communication resources.

[0175] Figure 10 A block diagram 1000 of a device 1005 supporting downlink beam performance reporting for UE measurements 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, 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).

[0176] 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 passed 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.

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

[0178] Device 1005 or its various components may be examples of various aspects of a downlink beam performance report for performing UE measurements as described herein. For example, communication manager 1020 may include configuration manager 1025, performance monitoring report manager 1030, parameter adjustment manager 1035, or any combination thereof. Communication manager 1020 may be examples of 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., receiving, acquiring, monitoring, outputting, transmitting). 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.

[0179] Configuration manager 1025 is capable of, configured to, or operable to support components for outputting first signaling that indicates a configuration for a downlink beam performance report for a set of predicted target resources based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering predicted failure instances, a time window, and a threshold for the number of predicted failure instances that trigger predicted failure events within the time window. Performance monitoring report manager 1030 is capable of, configured to, or operable to support components for obtaining a performance monitoring report based on the number of predicted failure instances occurring within the time window. Parameter adjustment manager 1035 is capable of, configured to, or operable to support components for outputting second signaling that indicates adjustments to one or more parameters based on the performance monitoring report.

[0180] Figure 11A block diagram 1100 of a communication manager 1120 supporting downlink beam performance reporting for UE measurements according to one or more aspects of this disclosure is shown. The communication manager 1120 may be an example of a communication manager 920, a communication manager 1020, or aspects thereof as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of downlink beam performance reporting for UE measurements as described herein. For example, the communication manager 1120 may include a configuration manager 1125, a performance monitoring report manager 1130, a parameter tuning manager 1135, 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). Communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of the protocol stack, within a device, component, or virtualization component associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0181] Configuration manager 1125 is capable of, configured to, or operable to support components for outputting first signaling that indicates a configuration for a downlink beam performance report for a set of predicted target resources based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering predicted failure instances, a time window, and a threshold for the number of predicted failure instances that trigger predicted failure events within the time window. Performance monitoring report manager 1130 is capable of, configured to, or operable to support components for obtaining a performance monitoring report based on the number of predicted failure instances occurring within the time window. Parameter adjustment manager 1135 is capable of, configured to, or operable to support components for outputting second signaling that indicates adjustments to one or more parameters based on the performance monitoring report.

[0182] In some examples, the configuration manager 1125 is capable of, can be configured to, or is operable to support components for outputting beamspace information indicating a set of performance monitoring resources, receiving signaling for beamspace filters, or both.

[0183] Figure 12A diagram of a system 1200 including a device 1205 supporting downlink beam performance reporting for UE measurements, 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 other network devices or network equipment, such as one or more network entities in network entity 105, UE 115, or any combination thereof. Communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1205 may include components supporting output and enabling communication, such as a communication manager 1220, a transceiver 1210, one or more antennas 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0184] 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 may be 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., by one or more antennas 1215, by 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 be configured to couple to said one or more processors or one or more memory components, said one or more processors or one or more 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).

[0185] At least one memory 1225 may include RAM, ROM, or any combination thereof. At least one memory 1225 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1230. Code 1230 may include instructions that, when executed by one or more processors 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 a processor of at least one processor 1235, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, at least one memory 1225 may include a BIOS, etc., which 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).

[0186] At least one processor 1235 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1235 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1235. At least one processor 1235 may be configured to execute computer-readable instructions stored in 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 downlink beam performance reporting for UE measurements). For example, device 1205 or components thereof 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, the at least one processor 1235 and the at least one memory 1225 being configured to perform the various functions described herein. The 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 may (e.g., by executing code 1230) host functions for performing the functions of device 1205. The 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 examples, the at least one processor 1235 may include multiple processors, and the 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, the multiple memories being configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1235 may be a component of a processing system, which can refer to a system of machines, circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1235) and memory circuitry (which may include at least one memory 1225)) or components that receive or obtain inputs and process those inputs to produce, generate, or obtain outputs. The processing system may be configured to perform one or more of the functions described herein.For example, at least one processor 1235 or a processing system including at least one processor 1235 may be configured, configured to, or operated to cause device 1205 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “configurable to,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1225 or otherwise.

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

[0188] 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 delivery of data communications by client devices, such as one or more UEs 115. In some examples, the communication manager 1220 can manage communication with one or more other network devices 105 and may include a controller or scheduler for (e.g., coordinating one or more other network devices) controlling communication with UE 115. In some examples, the communication manager 1220 may support the X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0189] For example, the communication manager 1220 can be configured or operated to support components for outputting a first signaling that indicates a configuration for a downlink beam performance report for a set of predicted target resources based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering predicted failure instances, a time window, and a threshold for the number of predicted failure instances that trigger predicted failure events within the time window. The communication manager 1220 can be configured or operated to support components for obtaining a performance monitoring report based on the number of predicted failure instances occurring within the time window. The communication manager 1220 can be configured or operated to support components for outputting a second signaling that indicates adjustments to one or more parameters based on the performance monitoring report.

[0190] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 can support techniques for improving communication reliability, reducing latency, utilizing communication resources more efficiently, and improving coordination between devices.

[0191] 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 a downlink beam performance report as described herein by the UE, 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.

[0192] Figure 13 A flowchart illustrating a method 1300 for supporting downlink beam performance reporting for a UE according to one or more 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.

[0193] At 1305, the method may include receiving signaling instructing configuration for a downlink beam performance report for a set of UE measurements against a set of prediction target resources based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering prediction failure instances, a time window, and a threshold for the number of prediction failure instances that trigger prediction failure events within the time window. Operation of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1305 may be provided by reference to [reference needed]. Figure 7 The configuration component 725 described is used to execute this.

[0194] At 1310, the method may include measuring one or more RSs associated with one or more performance monitoring resources in a set of performance monitoring resources. The operation of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be provided by reference to [reference needed]. Figure 7 The RS component 730 described is used to perform this.

[0195] At point 1315, the method may include generating a performance monitoring report based on the number of performance failure instances occurring within a time window. The operation at 1315 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1315 may be derived from references... Figure 7 The performance monitoring and reporting component 735 is described and used to perform this.

[0196] Figure 14 A flowchart illustrating a method 1400 for supporting downlink beam performance reporting for a UE according to one or more aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 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.

[0197] At 1405, the method may include receiving signaling instructing configuration for a downlink beam performance report for a set of UE measurements against a set of prediction target resources based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering prediction failure instances, a time window, and a threshold for the number of prediction failure instances that trigger prediction failure events within the time window. Operation of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1405 may be provided by reference to [reference needed]. Figure 7 The configuration component 725 described is used to execute this.

[0198] At 1410, the method may include measuring one or more RSs associated with one or more performance monitoring resources in a set of performance monitoring resources. The operation of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be provided by reference to [reference needed]. Figure 7 The RS component 730 described is used to perform this.

[0199] At point 1415, the method may include generating a performance monitoring report based on the number of performance failure instances occurring within a time window. The operation at 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1415 may be derived from references... Figure 7The performance monitoring and reporting component 735 is described and used to perform this.

[0200] At 1420, the method may include sending a performance monitoring report based on the number of predicted failed instances exceeding a threshold, wherein each predicted failed instance is based on one or more measured RSs associated with one or more performance monitoring resources in a set of performance monitoring resources exceeding an error rate threshold. The operation of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1420 may be provided by reference to [reference needed]. Figure 7 The performance monitoring and reporting component 735 is described and used to perform this.

[0201] Figure 15 A flowchart illustrating a method 1500 for supporting downlink beam performance reporting for a UE according to one or more aspects of this disclosure is shown. Operation of method 1500 may be implemented by a network entity or its components as described herein. For example, operation of method 1500 may 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.

[0202] At 1505, the method may include outputting a first signaling indicating a configuration for a downlink beam performance report for a set of UE measurements against a set of prediction target resources based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering prediction failure instances, a time window, and a threshold for the number of prediction failure instances that trigger prediction failure events within the time window. The operation of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to [reference needed]. Figure 11 The configuration manager 1125 described is used to execute this.

[0203] At point 1510, the method may include obtaining a performance monitoring report based on the number of predicted failure instances occurring within a time window. The operation of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be derived from references... Figure 11 The performance monitoring report manager 1130 described is used to perform this.

[0204] At point 1515, the method may include outputting a second signaling instruction for adjustment of one or more parameters based on a performance monitoring report. The operation of point 1515 may be performed according to examples disclosed herein. In some examples, aspects of the operation of point 1515 may be provided by reference to [reference needed]. Figure 11 The parameter adjustment manager 1135 described is used to perform this.

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

[0206] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving signaling indicating a configuration for a downlink beam performance report for a set of predicted target resources measured by the UE, at least in part based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering predicted failure instances, a time window, and a threshold for the number of predicted failure instances that trigger a predicted failure event within the time window; measuring one or more reference signals associated with one or more performance monitoring resources in the set of performance monitoring resources; and generating a performance monitoring report based at least in part on the number of performance failure instances occurring within the time window.

[0207] Aspect 2: According to the method of aspect 1, the method further includes: identifying the beam space information of the set of performance monitoring resources based at least in part on beam space information of a subset of the set of predicted target resources from previous performance monitoring reports.

[0208] Aspect 3: According to the method of aspect 2, wherein the beam space information for the set of performance monitoring resources includes quasi-co-located source reference signal information for the set of performance monitoring resources, and the beam space information for the subset of the set of predicted target resources from the previous performance monitoring report includes quasi-co-located source reference signal information for the subset of the set of predicted target resources from the previous performance monitoring report.

[0209] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: identifying the receive beam spatial filter for the set of performance monitoring resources based at least in part on the receive beam spatial filter for a subset of the set of predicted target resources from previous performance monitoring reports.

[0210] Aspect 5: The method according to any one of Aspects 1 to 4, the method further comprising: receiving beamspace information indicating the set of performance monitoring resources, receiving signaling of a beamspace filter or both.

[0211] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the performance monitoring report includes an indication of one or more error rate values ​​exceeding the error rate threshold, time information associated with one or more predicted failure instances within the time window, additional reference signal measurement information associated with the one or more performance monitoring resources, or any combination thereof.

[0212] Aspect 7: The method according to any one of Aspects 1 to 6, the method further comprising: receiving signaling including a preemption indication, the preemption indication configuring the UE to suppress one or more performance measurement opportunities associated with a set of one or more performance measurement resources.

[0213] Aspect 8: The method according to any one of Aspects 1 to 7, wherein receiving the signaling further comprises: receiving an indication of a beam prediction report identifier associated with the error rate threshold, the time window, the number of prediction failure instances threshold, or a combination thereof.

[0214] Aspect 9: The method according to any one of Aspects 1 to 8, wherein receiving the signaling further comprises: receiving an indication of a serving cell or bandwidth portion associated with the error rate threshold, the time window, the predicted number of failed instances threshold, or a combination thereof.

[0215] Aspect 10: The method according to any one of Aspects 1 to 9, wherein receiving the signaling further comprises: receiving an indication of the number of consecutive time slots, subframes, frames or other time periods defining the time window, wherein the time window includes a sliding window or a non-sliding window.

[0216] Aspect 11: The method according to any one of Aspects 1 to 10, wherein receiving the signaling further comprises: receiving an indication of a timer identifying the time window, wherein the indication includes the start point of the timer, the end point of the timer, the duration of the timer, or any combination thereof.

[0217] Aspect 12: The method according to any one of Aspects 1 to 11, wherein generating the performance monitoring report further comprises: sending the performance monitoring report at least in part based on the number of predicted failure instances exceeding the predicted failure instance number threshold, wherein each predicted failure instance is at least in part based on one or more measured reference signals associated with one or more performance monitoring resources in the set of performance monitoring resources exceeding the error rate threshold.

[0218] Aspect 13: The method according to aspect 12, wherein each prediction failure instance is based at least in part on all measured reference signals associated with one or more performance monitoring resources in the set of performance monitoring resources exceeding the error rate threshold.

[0219] Aspect 14: The method according to any one of Aspects 12 to 13, wherein sending the report further includes sending the performance monitoring report via a Media Access Control-Control Element (MAC-CE), RRC, one or more CSI reports, or a combination thereof.

[0220] Aspect 15: The method according to any one of Aspects 1 to 11, wherein generating the performance monitoring report further includes: suppressing the sending of the report based at least in part on the premise that the number of predicted failed instances does not exceed the threshold for the number of predicted failed instances.

[0221] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the error rate threshold indicates the hypothetical block error rate value that triggers the prediction failure instance.

[0222] Aspect 17: The method according to any one of Aspects 1 to 16, wherein the configuration is associated with a request from a network entity for the UE to perform a prediction of the set of quality metrics for predicting target resources, the predicted quality metrics being determined by the UE at least in part based on measurements of one or more reference signals individually scheduled by the network entity.

[0223] Aspect 18: A method for wireless communication at a network entity, the method comprising: outputting a first signaling, the first signaling indicating a configuration for a downlink beam performance report for a set of UE measurements against a set of target resources, at least in part based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering prediction failure instances, a time window, and a threshold for the number of prediction failure instances that trigger prediction failure events within the time window; obtaining a performance monitoring report at least in part based on the number of prediction failure instances occurring within the time window; and outputting a second signaling indicating adjustment of one or more parameters, at least in part based on the performance monitoring report.

[0224] Aspect 19: The method according to aspect 18 further includes: outputting beamspace information indicating the set of performance monitoring resources, receiving signaling of a beamspace filter or both.

[0225] Aspect 20: A 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 to enable the UE to perform a method according to any one of aspects 1 to 17.

[0226] Aspect 21: A UE comprising at least one component for performing the method according to any one of aspects 1 to 17.

[0227] Aspect 22: A non-transitory computer-readable medium storing code, said code comprising instructions executable by one or more processors to perform the method according to any one of aspects 1 to 17.

[0228] Aspect 23: A 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 to cause the network entity to perform a method according to any one of Aspects 18 to 19.

[0229] Aspect 24: A network entity comprising at least one component for performing the method according to any one of aspects 18 to 19.

[0230] Aspect 25: A non-transitory computer-readable medium storing code, said code comprising instructions executable by one or more processors to perform the method according to any one of aspects 18 to 19.

[0231] It should be noted that the methods described herein describe possible specific implementations. 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.

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

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

[0234] The various exemplary blocks and components described in connection with this disclosure can be implemented or performed using general-purpose processors, DSPs, ASICs, CPUs, graphics processing units (GPUs), neural processing units (NPUs), FPGAs or other programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternatives, 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 working in conjunction 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.

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

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

[0237] 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".

[0238] 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” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as 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” can 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".

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

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

[0241] 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," and 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 figures, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0242] 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: Receive signaling, the signaling indicating a configuration for a downlink beam performance report for a set of UE measurements against a set of prediction target resources, at least in part based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering prediction failure instances, a time window, and a threshold for the number of prediction failure instances that trigger prediction failure events within the time window; One or more reference signals associated with one or more performance monitoring resources in the set of measurement and performance monitoring resources; as well as The performance monitoring report is generated based at least in part on the number of performance failure instances that occur within the time window.

2. 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 beam space information for the set of performance monitoring resources is identified at least in part based on beam space information of a subset of the set of predicted target resources from previous performance monitoring reports.

3. The UE according to claim 2, wherein: The beam space information for the set of performance monitoring resources includes quasi-co-located source reference signal information for the set of performance monitoring resources, and The beam space information of the subset of the set of predicted target resources from the previous performance monitoring report includes quasi-co-located source reference signal information of the subset of the set of predicted target resources from the previous performance monitoring report.

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: The receive beam spatial filter for the set of performance monitoring resources is identified at least in part based on the receive beam spatial filter for a subset of the set of predicted target resources from previous performance monitoring reports.

5. 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 signaling indicating beamspace information for the set of performance monitoring resources, receive beamspace filter, or both.

6. The UE of claim 1, wherein the performance monitoring report includes an indication of one or more error rate values ​​exceeding the error rate threshold, time information associated with one or more predicted failure instances within the time window, additional reference signal measurement information associated with the one or more performance monitoring resources, or any combination thereof.

7. 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 system receives signaling including a preemption indication that configures the UE to suppress one or more performance measurement opportunities associated with a set of one or more performance measurement resources.

8. The UE of claim 1, wherein, in order to receive the signaling, the one or more processors are capable of further operating individually or jointly to execute the code to cause the UE to: Receive an indication of a beam prediction report identifier associated with the error rate threshold, the time window, the number of prediction failure instances threshold, or a combination thereof.

9. The UE of claim 1, wherein, in order to receive the signaling, the one or more processors are capable of further operating individually or jointly to execute the code to cause the UE to: Receive an indication of a serving cell or bandwidth portion associated with the error rate threshold, the time window, the predicted number of failed instances threshold, or a combination thereof.

10. The UE of claim 1, wherein, in order to receive the signaling, the one or more processors are capable of further operating individually or jointly to execute the code to cause the UE to: Receive an indication of the number of consecutive time slots, subframes, frames, or other time periods that define the time window, wherein the time window includes a sliding window or a non-sliding window.

11. The UE of claim 1, wherein, in order to receive the signaling, the one or more processors are capable of further operating individually or jointly to execute the code to cause the UE to: Receive an indication to a timer that identifies the time window, wherein the indication includes the start point of the timer, the end point of the timer, the duration of the timer, or any combination thereof.

12. The UE of claim 1, wherein, in order to generate the performance monitoring report, the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The performance monitoring report is sent at least in part based on the number of predicted failed instances exceeding the predicted failed instance number threshold, wherein each predicted failed instance is at least in part based on one or more measured reference signals associated with one or more performance monitoring resources in the set of performance monitoring resources exceeding the error rate threshold.

13. The UE of claim 12, wherein each prediction failure instance is based at least in part on all measured reference signals in the measured reference signals associated with one or more performance monitoring resources in the set of performance monitoring resources exceeding the error rate threshold.

14. The UE of claim 12, wherein, in order to send the report, the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The performance monitoring report is transmitted via Media Access Control-Control Element (MAC-CE), Radio Resource Control (RRC), one or more Channel State Information (CSI) reports, or a combination thereof.

15. The UE of claim 1, wherein, in order to generate the performance monitoring report, the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The sending of the report is suppressed at least in part based on the fact that the number of predicted failed instances does not exceed the threshold for the number of predicted failed instances.

16. The UE of claim 1, wherein the error rate threshold indicates the assumed block error rate value that triggers the prediction failure instance.

17. The UE of claim 1, wherein the configuration is associated with a request from a network entity to perform a prediction of a quality metric for predicting the set of target resources on the UE, wherein the predicted quality metric is determined by the UE based at least in part on measurements of one or more reference signals individually scheduled by the network entity.

18. 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: Output a first signaling, the first signaling indicating a configuration for a downlink beam performance report for a set of user equipment (UE) measurements against a set of prediction target resources, at least in part based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering prediction failure instances, a time window, and a threshold for the number of prediction failure instances that trigger prediction failure events within the time window; The performance monitoring report is obtained based at least in part on the number of predicted failure instances that occur within the time window; as well as The second signaling, indicating the adjustment of one or more parameters, is output based at least in part on the performance monitoring report.

19. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive signaling, the signaling indicating a configuration for a downlink beam performance report for a set of UE measurements against a set of prediction target resources, at least in part based on a set of performance monitoring resources, wherein the configuration includes an error rate threshold for triggering prediction failure instances, a time window, and a threshold for the number of prediction failure instances that trigger prediction failure events within the time window; One or more reference signals associated with one or more performance monitoring resources in the set of measurement and performance monitoring resources; as well as The performance monitoring report is generated based at least in part on the number of performance failure instances that occur within the time window.

20. The method according to claim 19, further comprising: The beam space information for the set of performance monitoring resources is identified at least in part based on beam space information of a subset of the set of predicted target resources from previous performance monitoring reports.

Images