WO2025208402A1

WO2025208402A1 - Processing criteria for event driven channel state reporting

Info

Publication number: WO2025208402A1
Application number: PCT/CN2024/085760
Authority: WO
Inventors: Doohyun SUNG; Wooseok Nam; Fang Yuan
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2024-04-03
Filing date: 2024-04-03
Publication date: 2025-10-09
Anticipated expiration: 2026-10-03

Abstract

Methods, systems, and devices for processing criteria for event driven channel state reporting are described. The described techniques provide for transmitting CSI reports based on when a UE determines that a trigger for an event condition has occurred. The trigger may be based on a determination that the channel associated with received reference signals is deficient in terms of quality. Upon determining that the trigger for the event condition has occurred, the UE may then generate a CSI report to transmit to the network entity. Additionally, the UE may determine an optimal CSI processing unit (CPU) value which may determine an amount of processing resources that the UE may utilize in generating the CSI reports.

Description

PROCESSING CRITERIA FOR EVENT DRIVEN CHANNEL STATE REPORTING

FIELD OF TECHNOLOGY

The following relates to wireless communications, including processing criteria for event driven channel state reporting.

BACKGROUND

Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the 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-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 spread orthogonal frequency division multiplexing (DFT-S-OFDM) . A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .

Channel state information (CSI) resources (e.g., CSI-RS) may be measured by a UE to estimate channel quality between a base station and UE, where the channel quality may be indicated by measured parameters (e.g., channel quality indicator (CQI) , precoding matrix indicator (PMI) , rank indicator (RI) , reference signal received power (RSRP) ) . The UE may transmit a CSI report to the base station indicating the channel quality information that the base station may use for data transmissions. The base station may want to use this report for scheduling in the future. Conventional CSI reporting techniques are deficient.

SUMMARY

The described techniques relate to improved methods, systems, devices, and apparatuses that support processing criteria for event driven channel state reporting. For example, the described techniques enable a user equipment (UE) to transmit channel state information (CSI) reports based on when (or if) a UE determines that a trigger for an event condition has occurred. The trigger may be based on a determination that the channel associated with received reference signals is deficient in terms of quality. Upon determining that the trigger for the event condition has occurred, the UE may then generate a CSI report to transmit to the base station. Additionally, the UE may determine an optimal CSI processing unit (CPU) value which may determine an amount of processing resources that the UE may utilize in generating the CSI reports. The CPU value may affect an amount of processing power in addition to providing a quantity of measurements and reports that it may generate.

A method for wireless communications by a user equipment (UE) is described. The method may include receiving, from a network entity, one or more reference signals via one or more beams, generating one or more channel state information (CSI) reports based on a first CSI processing unit (CPU) value and on one or more measurements of the one or more reference signals satisfying a measurement threshold that triggers an event condition, and transmitting, to the network entity, at least one of the one or more CSI reports in accordance with the first central processing unit (CPU) value and based on the one or more measurements satisfying the measurement threshold that triggers the event condition.

A UE for wireless communications is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the UE to receive, from a network entity, one or more reference signals via one or more beams, generate one or more CSI reports based on a first CSI processing unit (CPU) value and on one or more measurements of the one or more reference signals satisfying a measurement threshold that triggers an event condition, and transmit, to the network entity, at least one of the one or more CSI reports in accordance with the first CPU value and based on the one or more measurements satisfying the measurement threshold that triggers the event condition.

Another UE for wireless communications is described. The UE may include means for receiving, from a network entity, one or more reference signals via one or more beams, means for generating one or more CSI reports based on a first CSI processing unit (CPU) value and on one or more measurements of the one or more reference signals satisfying a measurement threshold that triggers an event condition, and means for transmitting, to the network entity, at least one of the one or more CSI reports in accordance with the first CPU value and based on the one or more measurements satisfying the measurement threshold that triggers the event condition.

A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to receive, from a network entity, one or more reference signals via one or more beams, generate one or more CSI reports based on a first CSI processing unit (CPU) value and on one or more measurements of the one or more reference signals satisfying a measurement threshold that triggers an event condition, and transmit, to the network entity, at least one of the one or more CSI reports in accordance with the first CPU value and based on the one or more measurements satisfying the measurement threshold that triggers the event condition.

Some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for applying a priority rule for transmission of the one or more CSI reports, where the priority rule indicates a priority ordering for transmission of event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and aperiodic CSI reports, where the at least one of the one or more CSI reports may be transmitted in accordance with the priority rule.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, transmitting the at least one of the one or more CSI reports may include operations, features, means, or instructions for transmitting one or more aperiodic CSI reports prior to one or more event-triggered CSI reports according to the priority ordering and transmitting one or more semi-persistent CSI reports or periodic CSI reports after the one or more event-triggered CSI reports according to the priority ordering.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, transmitting the at least one of the one or more CSI reports may include operations, features, means, or instructions for transmitting one or more event-triggered CSI reports prior to one or more aperiodic CSI reports, semi-persistent CSI reports, or periodic CSI reports according to the priority ordering.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, transmitting the at least one of the one or more CSI reports may include operations, features, means, or instructions for transmitting one or more aperiodic CSI reports, semi-persistent CSI reports, or periodic CSI reports prior to one or more event-triggered CSI reports in accordance with the priority ordering.

Some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from the network entity, one or more additional reference signals via the one or more beams, generating one or more additional CSI reports based on a second CPU value and on one or more additional measurements of the one or more additional reference signals satisfying the measurement threshold that triggers the event condition, where the second CPU value may be based on a quantity of CSI measurement-only instances and a quantity of measurement-and-reporting instances during a time period, and transmitting, to the network entity, at least one additional CSI report of the one or more additional CSI reports in accordance with the second CPU value and based on the one or more additional measurements satisfying the measurement threshold that triggers the event condition.

Some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for applying a first offset to the quantity of CSI measurement-only instances and a second offset to the quantity of measurement-and-reporting instances, where the second CPU value may be based on application of the first offset, the second offset, or both.

Some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for applying a same offset to the quantity of CSI measurement-only instances and to the quantity of measurement-and-reporting instances, where the second CPU value may be based on application of the same offset.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, a CPU value associated with measurement-only instances may be set to a weighted CPU value associated with measurement-and-reporting instances and the second CPU value may be based on the CPU value associated with measurement-only instances and the weighted CPU value associated with measurement-and-reporting instances.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, a CPU value associated with measurement-and-reporting instances may be set to a weighted CPU value associated with one or more aperiodic, semi-persistent, or periodic CSI report instances and the second CPU value may be based on the CPU value associated with measurement-and reporting-instances and the weighted CPU value associated with the one or more aperiodic, semi-persistent, or periodic CSI report instances.

Some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the network entity, an indication of a capability of the UE, the capability indicating a set of multiple CPU values capable of implementation by the UE.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the set of multiple CPU values includes one or more fractional values.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example of a wireless communications system that supports processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure.

FIG. 2 shows an example of a wireless communications system that supports processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure.

FIG. 3A and FIG. 3B show an example of CSI processing configuration that support processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure.

FIG. 4 shows an example of a process flow that supports processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure.

FIGs. 5 and 6 show block diagrams of devices that support processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure.

FIG. 7 shows a block diagram of a communications manager that supports processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure.

FIG. 8 shows a diagram of a system including a device that supports processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure.

FIG. 9 shows a flowchart illustrating methods that support processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure.

DETAILED DESCRIPTION

A user equipment (UE) may use reference signals, such as channel state information (CSI) reference signals (CSI-RSs) to estimate channel quality between a base station and UE, and the UE may transmit a CSI report to a network entity indicating the channel quality information. In some systems (e.g., a new radio (NR) wireless communication system) , there may be a CSI processing unit (CPU) value, where the CPU value may be equal to the number of simultaneous CSI calculations supported by the UE. The CPU value may be a calculation engine capable of performing CSI calculations or measurements that are reported in or indicated by the CSI report, which may be aperiodic, semi-persistent, periodic, event driven, etc.

CSI reporting may be performed on a periodic, semi-persistent, or an aperiodic basis when a network entity signals to a UE to transmit a report. This may lead to the CSI reporting periodicity being too long, which may result in outdated channel information. However, if CSI reporting is done too frequently, this may result in higher overhead and latency issues. Additionally, when generating a CSI report, the UE may allocate some portion of available CPUs to perform one or more CSI calculations for the CSI report. In some cases, there may not be enough CPUs available because the UE has already allocated some of the CPUs for performing ongoing CSI calculations for generating one or more other CSI reports. In other cases, there may an excess of CPUs allocated which does not utilize resources effectively.

To mitigate these issues, processing criteria for event driven channel state reporting may be employed. A UE may initiate a CSI reporting procedure based on its own determination that channel measurements have deteriorated such that a measurement threshold is satisfied (e.g., is exceeded or falls below) thus resulting in an CSI reporting event condition. Additionally, the UE may determine a CPU value which may determine an amount of processing resources that the UE may utilize in generating the CSI reports. The CPU value may affect an amount of processing power in addition to providing a quantity of measurements and reports that it may generate.

Particular aspects of the subject matter described herein may be implemented to realize one or more advantages. The described techniques may support improvements in CSI processing, decrease processing time, and improve data throughput, among other advantages. As such, supported techniques may include improved network operations and, in some examples, may promote network efficiencies, among other benefits.

Aspects of the disclosure are initially described in the context of wireless communications systems. Further examples are then provided that illustrate CSI processing techniques in transmitting CSI reports. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to processing criteria for event driven channel state reporting.

FIG. 1 shows an example of a wireless communications system 100 that supports processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network entities 105) , one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via communication link (s) 125 (e.g., a radio frequency (RF) access link) . For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link (s) 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .

The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105) , as shown in FIG. 1.

As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described herein) , a network controller, an apparatus, a device, a 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 a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

In some examples, network entities 105 may communicate with a core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via backhaul communication link (s) 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) . In some examples, network entities 105 may communicate with one another via backhaul communication link (s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via the core network 130) . In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof. The backhaul communication link (s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.

One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) . In some examples, a network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140) .

In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 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, a network entity 105 may include one or more of a central unit (CU) , such as a CU 160, a distributed unit (DU) , such as a DU 165, a radio unit (RU) , such as an RU 170, a RAN Intelligent Controller (RIC) , such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) . In some examples, one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .

The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaptation protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU 160 (e.g., one or more CUs) may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs) , or some combination thereof, and the DUs 165, RUs 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 the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170) . In some cases, a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) . A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) . In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.

In some wireless communications systems (e.g., the wireless communications system 100) , infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) . In some cases, in an IAB network, one or more of the network entities 105 (e.g., network entities 105 or IAB node (s) 104) may be partially controlled by each other. The IAB node (s) 104 may be referred to as a donor entity or an IAB donor. A DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base station 140 (such as a donor network entity or a donor base station) . The one or more donor entities (e.g., IAB donors) may be in communication with one or more additional devices (e.g., IAB node (s) 104) via supported access and backhaul links (e.g., backhaul communication link (s) 120) . IAB node (s) 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor. An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node (s) 104 used for access via the DU 165 of the IAB node (s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) . In some examples, the IAB node (s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node (s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) . In such cases, one or more components of the disaggregated RAN architecture (e.g., the IAB node (s) 104 or components of the IAB node (s) 104) may be configured to operate according to the techniques described herein.

In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support test as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180) .

A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.

The UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.

The UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link (s) 125 (e.g., one or more access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link (s) 125. For example, a carrier used for the communication link (s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated 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 that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105) .

Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) . In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.

The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of T_s=1/ (Δf_max·N_f) seconds, for which Δf_max may represent a supported subcarrier spacing, and N_f may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) . Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .

Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) . In some wireless communications systems, such as the wireless communications system 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N_f) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

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

Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET) ) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to UEs 115 (e.g., one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE) .

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

The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) . The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication 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 commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

In some examples, a UE 115 may be configured to support communicating directly with other UEs (e.g., one or more of the UEs 115) via a device-to-device (D2D) communication link, such as a D2D communication link 135 (e.g., in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) . In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to one or more of the UEs 115 in the group. In some examples, a network entity 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.

The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.

The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) . Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from 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 the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) . Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations 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, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .

UE 115 may measure CSI-RS resources to estimate channel quality of a channel and that may be indicated by measured channel quality parameters (e.g., CQI, PMI, RI, RSRP) . UE 115 may transmit a CSI report to network entity 105 indicating the measured channel quality parameters for the CSI reference resource slot. Network entity 105 may use the CSI report for scheduling in the future. Additionally, or alternatively, UE 115 may initiate a CSI reporting procedure based on its own determination that channel measurements have deteriorated such that a measurement threshold is triggered thus resulting in an CSI reporting event condition. the channel associated with received reference signals is deficient in terms of quality. Upon determining that the trigger for the event condition has occurred, the UE may then generate a CSI report to transmit to the network entity 105. Additionally, the UE 115 may determine a CPU value which may correspond to an amount of processing resources that the UE may utilize in generating the CSI reports. The CPU value may affect an amount of processing power in addition to providing a quantity of measurements and reports that the UE 115 may generate.

FIG. 2 shows an example of a wireless communications system 200 that supports processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure. The wireless communications system 200 may include network entity 105-a and UE 115-a, which may be examples of network entities 105 and UEs 115 as described with reference to FIG. 1. Network entity 105-a may serve a geographic coverage area 110-a. In some examples, network entity 105-a and UE 115-a may communicate via communication link 205. In some cases, UE-115-a may implement an event driven channel state reporting to transmit to network entity 105-a a CSI report based on a triggered event condition and in accordance with a CPU value.

Network entity 105-a may transmit CSI reference signals 210 within one or more CSI resources for measurement by UE 115-a to estimate a channel quality of communication link 205 between network entity 105-a and UE 115-a. UE 115-a may transmit a CSI report 220 to network entity 105-a indicating the channel quality information that network entity 105-a may use for scheduling subsequent data transmissions. In some examples, UE 115-a may transmit CSI report 220 periodically, aperiodically, or on a semi-persistent basis to network entity 105-a. In other examples, UE 115-a may send CSI report 220 based on a triggered event condition at a UE. For example, UE 115-a may determine that reference signals 210 indicate that the channel is below a signal power or quality threshold. This power or quality threshold may be determined from various measurements such as signal-to-noise ratio (SNR) , reference signal received power (RSRP) , reference signal received quality (RSRQ) , or a combination thereof. Once UE 115-a determines that the measurement threshold has been satisfied, it may also indicate that an event condition has been triggered which initiates a CSI reporting procedure. This procedure may include UE 115-a signaling to network entity 105-a to signal uplink resources for UE 115-a to transmit a CSI report or it may include UE 115-a transmitting a CSI report utilizing previously scheduled resources.

UE 115-a may apply a priority rule for transmission of one or more CSI reports. This priority rule may be used by UE 115-a to prioritize the transmission of event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and aperiodic CSI reports. For example, a first prioritization rule may prioritize the transmission of aperiodic CSI reports, then event-triggered CSI reports, and then semi-persistent/periodic CSI reports. A second prioritization rule may prioritize the transmission of event-triggered CSI reports followed by any aperiodic CSI reports, semi-persistent CSI reports, and periodic CSI reports. A third prioritization rule may prioritize the transmission of any aperiodic CSI reports, semi-persistent CSI reports, and periodic CSI reports followed by event-triggered CSI reports. After determining the transmission priority, UE 115-a may then transmit the one or more CSI reports.

UE capability regarding configured CPU values 225 may also impact CSI reporting. A CPU value 225 may be equal to the number of simultaneous CSI calculations UE 115-a is capable of supporting at the same time. UE 115-a may be capable of a fixed amount of CSI calculations. UE 115-a may transmit to network entity 105-a an indication of a UE capability, where the capability indicates a plurality of CPU values 225 that UE 115-a is capable of implementing. CPU value 225 may be include both integer and fractional values. UE 115-a may determine an optimal CPU value 225 to utilize for the measurement of channel conditions and for the generation and transmission of CSI reports. For example, UE 115-a may utilize a lower CPU value 225 in instances where fewer measurements and CSI reports are sufficient, and may utilize a higher CPU value 225 in instances where greater measurements and CSI reports are required. UE 115-a may utilize different CPU values 225 in different instances of channel state measurement and CSI reporting based on varying circumstances. For example, CPU consumption may be less when the trigger for the event condition has not occurred as resources are only needed for measurement and not for reporting. Conversely, CPU consumption may be more when the trigger for the event condition has occurred and resources are requested for both measurement and for reporting.

FIG. 3A and FIG. 3B show examples of CSI processing configurations 300 and 350 that support processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure. The CPU processing configurations 300 and 350 may illustrate various instances of determining CPU values according to different channel state measurement scenarios.

CPU processing configuration 300 may illustrate two different scenarios for channel state measurement procedures. For example, scenario 310 may illustrate a scenario where UE 115 may only be conducting channel state measurements of a channel without generating any corresponding CSI reports. Under scenario 310, a corresponding CPU value, O_{CPU_meas_only}, may indicate the CPU value that UE 115 may utilize during this given time period.

In another example, scenario 320 may illustrate a scenario where UE 115 may be conducting channel state measurements of a channel in addition to generating one or more corresponding CSI reports. Under scenario 320, a corresponding CPU value, O_{CPU_meas_and_report}, may indicate the CPU value that UE 115 may utilize during this given time period. As illustrated relative to scenario 310, scenario 320 may require a higher CPU value than that of scenario 310 due to the additional processing resources required for generating the CSI reports. The CPU values utilized by UE 115 may be both integer values and fractional values. Serving only as possible examples, CPU values may be 0, 1/2, 2/3, 1, 3/2, etc. Other CPU values may be available to UE 115.

CPU processing configuration 350 may illustrate a scenario 360 where UE 115 conducts channel state measurements of a channel, detects an event condition 370 being met, and then generates one or more corresponding CSI reports due to event condition 370 being satisfied. Under scenario 360, corresponding CPU values, O_{CPU_meas} and O_{CPU_report}, may indicate CPU values that UE 115 may utilize during this given time period. Here, the CPU value for conducting channel state measurements of a channel in addition to generating one or more corresponding CSI reports may be defined as two different CPU values. CPU value O_{CPU_meas} may be utilized by UE 115 prior to event condition 370, and O_{CPU_report} may be utilized by UE 115 after event condition 370 is detected.

In some examples, a total CPU value given a scenario where a UE 115 both conducts channel state measurements of a channel and then generates one or more corresponding CSI reports due to event condition being satisfied may be derived based on a quantity of CSI measurement-only instances (M) and a quantity of measurement-and-reporting instances (N) during a time period as follows:

In this example, a total CPU value is determined by combining separately calculated CPU values of a measurement only scenario with a measurement and report scenario.

In another example, a total CPU value given a quantity of CSI measurement-only instances (M) and a quantity of measurement-and-reporting instances (N) during a time period may be determined as follows:

In this example, a total CPU value is determined by jointly calculating CPU values of a measurement only scenario with a measurement and report scenario.

In some examples, one or more offsets may be introduced in calculating a total CPU value given a quantity of CSI measurement-only instances (M) and a quantity of measurement-and-reporting instances (N) during a time period. In this scenario, the two respective CPU values for O_{CPU_meas_only} and O_{CPU_meas_and_report} may be defined to be integers (i.e., O_{CPU_meas_only} = o_meas and O_{CPU_meas_and_report} = o_report (where o_meas∈ {0, 1, 2, . . . } , o_report∈ {0, 1, 2, . . . } ) , where the offset values, denoted as Offset_meas for measurement only and Offset_report for measurement &report, can be applied when the final CPU value is computed:
O_(Total_CPU_event_triggered) =O_ (CPU_meas_only) *M+Offset_meas+O_ (CPU_meas_and_report) *N+Offset_report
=o_meas*M+〖Offset〗_meas+o_report*N+〖Offset〗_report

In a first example of how the offsets may be utilized in determining a total CPU value based on a quantity of CSI measurement-only instances (M) and a quantity of measurement-and-reporting instances (N) during a time period:

In a second example of how the offsets may be utilized in determining a total CPU value based on a quantity of CSI measurement-only instances (M) and a quantity of measurement-and-reporting instances (N) during a time period:

In another example of utilizing offset values in calculating a total CPU value, a single CPU value and a single offset value may be defined where a single CPU is denoted O_{CPU_event_driven} (= O_{CPU_meas_only} = O_{CPU_meas_and_report}) and an offset is represented as a function of both a quantity of CSI measurement-only instances (M) and a quantity of measurement-and-reporting instances (N) (i.e., Offset=func (M, N) ) , where the total CPU value is based on applying the same offset value to both the CSI measurement-only instances and the measurement-and-reporting instances.

In some examples, CPU values for OCPU_meas_only and OCPU_meas_and_report may be weighted in relation to one another. For example, a relationship between the two may exist such that O_{CPU_meas_only} = ɑ *O_{CPU_meas_and_report} where an instance if ɑ <=1 could be considered to put more weight towards the CPU value associated with measurement-and-reporting instances.

In other examples, in scenarios where periodic, semi-persistent, and aperiodic CSI reporting (legacy reporting) coincide with an event-driven CSI report, a relationship between the two may exist such that O_{CPU_meas_and_report} = β *O_{CPU_legacy} where β is a weight that may be based on UE capability.

FIG. 4 shows an example of a process flow 400 that supports processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure. The process flow 400 may illustrate an example CSI processing procedure.

At 405, network entity 105-b may transmit, and UE 115-b may receive one or more reference signals via one or more beams of network entity 105-b.

At 410, UE 115-b may generate one or more CSI reports based on a triggered event condition at a UE 115-b. For example, UE 115-a may determine that the reference signals indicate that the channel is below a signal power or quality threshold. Once UE 115-b determines that the measurement threshold has been satisfied, it may also indicate that an event condition has been triggered which initiates the CSI report being generated. UE 115-b may generate the CSI report based on a first CPU value.

At 415, UE 115-b may transmit, and network entity 105-b may receive, the generated CSI reports in accordance with the first CPU value and the triggered event condition occurring.

At 420, network entity 105-b may transmit, and UE 115-b may receive one or more additional reference signals via one or more beams of network entity 105-b.

At 425, UE 115-b may generate one or more additional CSI reports based on an event condition at a UE 115-b occurring based on the measuring the one more additional reference signals. UE 115-b may have determined a second CPU value to utilize in generating the one or more additional CSI reports, where the second CPU value is different than the first CPU value.

At 430, UE 115-b may transmit, and network entity 105-b may receive, the additional generated CSI reports in accordance with the second CPU value and the triggered event condition occurring.

FIG. 5 shows a block diagram 500 of a device 505 that supports processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure. The device 505 may be an example of aspects of a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505, or one or more components of the device 505 (e.g., the receiver 510, the transmitter 515, the communications manager 520) , may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to processing criteria for event driven channel state reporting) . Information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.

The transmitter 515 may provide a means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to processing criteria for event driven channel state reporting) . In some examples, the transmitter 515 may be co-located with a receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a set of multiple antennas.

The communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be examples of means for performing various aspects of processing criteria for event driven channel state reporting as described herein. For example, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

In some examples, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include at least one of a processor, a digital signal processor (DSP) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .

Additionally, or alternatively, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .

In some examples, the communications manager 520 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both. For example, the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 520 is capable of, configured to, or operable to support a means for receiving, from a network entity, one or more reference signals via one or more beams. The communications manager 520 is capable of, configured to, or operable to support a means for generating one or more CSI reports based on a first CSI processing unit (CPU) value and on one or more measurements of the one or more reference signals satisfying a measurement threshold that triggers an event condition. The communications manager 520 is capable of, configured to, or operable to support a means for transmitting, to the network entity, at least one of the one or more CSI reports to the network entity in accordance with the first CPU value and based on the one or more measurements satisfying the measurement threshold that triggers the event condition.

By including or configuring the communications manager 520 in accordance with examples as described herein, the device 505 (e.g., at least one processor controlling or otherwise coupled with the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof) may support improvements in CSI processing, decrease processing time, and improve data throughput, among other advantages. As such, supported techniques may include improved network operations and, in some examples, may promote network efficiencies, among other benefits.

FIG. 6 shows a block diagram 600 of a device 605 that supports processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure. The device 605 may be an example of aspects of a device 505 or a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605, or one of more components of the device 605 (e.g., the receiver 610, the transmitter 615, the communications manager 620) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

The receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to processing criteria for event driven channel state reporting) . Information may be passed on to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.

The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to processing criteria for event driven channel state reporting) . In some examples, the transmitter 615 may be co-located with a receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.

The device 605, or various components thereof, may be an example of means for performing various aspects of processing criteria for event driven channel state reporting as described herein. For example, the communications manager 620 may include a reference signal component 625 a CSI component 630, or any combination thereof. The communications manager 620 may be an example of aspects of a communications manager 520 as described herein. In some examples, the communications manager 620, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The reference signal component 625 is capable of, configured to, or operable to support a means for receiving, from a network entity, one or more reference signals via one or more beams. The CSI component 630 is capable of, configured to, or operable to support a means for generating one or more CSI reports based on a first CPU value and on one or more measurements of the one or more reference signals satisfying a measurement threshold that triggers an event condition. The CSI component 630 is capable of, configured to, or operable to support a means for transmitting, to the network entity, at least one of the one or more CSI reports to the network entity in accordance with the first CPU value and based on the one or more measurements satisfying the measurement threshold that triggers the event condition.

FIG. 7 shows a block diagram 700 of a communications manager 720 that supports processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure. The communications manager 720 may be an example of aspects of a communications manager 520, a communications manager 620, or both, as described herein. The communications manager 720, or various components thereof, may be an example of means for performing various aspects of processing criteria for event driven channel state reporting as described herein. For example, the communications manager 720 may include a reference signal component 725, a CSI component 730, a prioritization component 735, a capability component 740, an offset component 745, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (e.g., via one or more buses) .

The communications manager 720 may support wireless communications in accordance with examples as disclosed herein. The reference signal component 725 is capable of, configured to, or operable to support a means for receiving, from a network entity, one or more reference signals via one or more beams. The CSI component 730 is capable of, configured to, or operable to support a means for generating one or more CSI reports based on a first CPU value and on one or more measurements of the one or more reference signals satisfying a measurement threshold that triggers an event condition. In some examples, the CSI component 730 is capable of, configured to, or operable to support a means for transmitting, to the network entity, at least one of the one or more CSI reports to the network entity in accordance with the first CPU value and based on the one or more measurements satisfying the measurement threshold that triggers the event condition.

In some examples, the prioritization component 735 is capable of, configured to, or operable to support a means for applying a priority rule for transmission of the one or more CSI reports, where the priority rule indicates a priority ordering for transmission of event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and aperiodic CSI reports, where the at least one of the one or more CSI reports is transmitted in accordance with the priority rule.

In some examples, to support transmitting the at least one of the one or more CSI reports, the CSI component 730 is capable of, configured to, or operable to support a means for transmitting one or more aperiodic CSI reports prior to one or more event-triggered CSI reports according to the priority ordering. In some examples, to support transmitting the at least one of the one or more CSI reports, the CSI component 730 is capable of, configured to, or operable to support a means for transmitting one or more semi-persistent CSI reports or periodic CSI reports after the one or more event-triggered CSI reports according to the priority ordering.

In some examples, to support transmitting the at least one of the one or more CSI reports, the CSI component 730 is capable of, configured to, or operable to support a means for transmitting one or more event-triggered CSI reports prior to one or more aperiodic CSI reports, semi-persistent CSI reports, or periodic CSI reports according to the priority ordering.

In some examples, to support transmitting the at least one of the one or more CSI reports, the CSI component 730 is capable of, configured to, or operable to support a means for transmitting one or more aperiodic CSI reports, semi-persistent CSI reports, or periodic CSI reports prior to one or more event-triggered CSI reports in accordance with the priority ordering.

In some examples, the reference signal component 725 is capable of, configured to, or operable to support a means for receiving, from the network entity, one or more additional reference signals via the one or more beams. In some examples, the CSI component 730 is capable of, configured to, or operable to support a means for generating one or more additional CSI reports based on a second CPU value and on one or more additional measurements of the one or more additional reference signals satisfying the measurement threshold that triggers the event condition, where the second CPU value is based on a quantity of CSI measurement-only instances and a quantity of measurement-and-reporting instances during a time period. In some examples, the CSI component 730 is capable of, configured to, or operable to support a means for transmitting, to the network entity, at least one additional CSI report of the one or more additional CSI reports in accordance with the second CPU value and based on the one or more additional measurements satisfying the measurement threshold that triggers the event condition.

In some examples, the offset component 745 is capable of, configured to, or operable to support a means for applying a first offset to the quantity of CSI measurement-only instances and a second offset to the quantity of measurement-and-reporting instances, where the second CPU value is based on application of the first offset, the second offset, or both.

In some examples, the offset component 745 is capable of, configured to, or operable to support a means for applying a same offset to the quantity of CSI measurement-only instances and to the quantity of measurement-and-reporting instances, where the second CPU value is based on application of the same offset.

In some examples, a CPU value associated with measurement-only instances is set to a weighted CPU value associated with measurement-and-reporting instances. In some examples, the second CPU value is based on the CPU value associated with measurement-only instances and the weighted CPU value associated with measurement-and-reporting instances.

In some examples, a CPU value associated with measurement-and-reporting instances is set to a weighted CPU value associated with one or more aperiodic, semi-persistent, or periodic CSI report instances. In some examples, the second CPU value is based on the CPU value associated with measurement-and reporting-instances and the weighted CPU value associated with the one or more aperiodic, semi-persistent, or periodic CSI report instances.

In some examples, the capability component 740 is capable of, configured to, or operable to support a means for transmitting, to the network entity, an indication of a capability of the UE, the capability indicating a set of multiple CPU values capable of implementation by the UE.

In some examples, the set of multiple CPU values includes one or more fractional values.

FIG. 8 shows a diagram of a system 800 including a device 805 that supports processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure. The device 805 may be an example of or include components of a device 505, a device 605, or a UE 115 as described herein. The device 805 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof) . The device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 820, an input/output (I/O) controller, such as an 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 be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845) .

The I/O controller 810 may manage input and output signals for the device 805. The I/O controller 810 may also manage peripherals not integrated into the device 805. In some cases, the I/O controller 810 may represent a physical connection or port to an external peripheral. In some cases, the I/O controller 810 may utilize an operating system such as or another known operating system. Additionally, or alternatively, the I/O controller 810 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller 810 may be implemented as part of one or more processors, such as the 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.

In some cases, the device 805 may include a single antenna. However, in some other cases, the device 805 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bi-directionally via the one or more antennas 825 using wired or wireless links as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 815 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 825 for transmission, and to demodulate packets received from the one or more antennas 825. The transceiver 815, or the transceiver 815 and one or more antennas 825, may be an example of a transmitter 515, a transmitter 615, a receiver 510, a receiver 610, or any combination thereof or component thereof, as described herein.

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

The 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 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, one or more discrete hardware components, or any combination thereof) . In some cases, the at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 840. The at least one processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting processing criteria for event driven channel state reporting) . For example, the device 805 or a component of the device 805 may include at least one processor 840 and at least one memory 830 coupled with or to the at least one processor 840, the at least one processor 840 and the at least one memory 830 configured to perform various functions described herein.

In some examples, the at least one processor 840 may include multiple processors and the at least one memory 830 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein. In some examples, the at least one processor 840 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 840) and memory circuitry (which may include the at least one memory 830) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 840 or a processing system including the at least one processor 840 may be configured to, configurable to, or operable to cause the device 805 to perform one or more of the functions described herein. Further, as described herein, being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 835 (e.g., processor-executable code) stored in the at least one memory 830 or otherwise, to perform one or more of the functions described herein.

The communications manager 820 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for receiving, from a network entity, one or more reference signals via one or more beams. The communications manager 820 is capable of, configured to, or operable to support a means for generating one or more CSI reports based on a first CSI processing unit (CPU) value and on one or more measurements of the one or more reference signals satisfying a measurement threshold that triggers an event condition. The communications manager 820 is capable of, configured to, or operable to support a means for transmitting, to the network entity, at least one of the one or more CSI reports to the network entity in accordance with the first CPU value and based on the one or more measurements satisfying the measurement threshold that triggers the event condition.

By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 may support improvements in CSI processing, decrease processing time, and improve data throughput, among other advantages. As such, supported techniques may include improved network operations and, in some examples, may promote network efficiencies, among other benefits.

In some examples, the communications manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 815, the one or more antennas 825, or any combination thereof. Although the communications manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 820 may be supported by or performed by the at least one processor 840, the at least one memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions executable by the at least one processor 840 to cause the device 805 to perform various aspects of processing criteria for event driven channel state reporting as described herein, or the at least one processor 840 and the at least one memory 830 may be otherwise configured to, individually or collectively, perform or support such operations.

FIG. 9 shows a flowchart illustrating a method 900 that supports processing criteria for event driven channel state reporting in accordance with one or more aspects of the present disclosure. The operations of the method 900 may be implemented by a UE or its components as described herein. For example, the operations of the method 900 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At 905, the method may include receiving, from a network entity, one or more reference signals via one or more beams. The operations of 905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 905 may be performed by a reference signal component 725 as described with reference to FIG. 7.

At 910, the method may include generating one or more CSI reports based on a first CPU value and on one or more measurements of the one or more reference signals satisfying a measurement threshold that triggers an event condition. The operations of 910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 910 may be performed by a CSI component 730 as described with reference to FIG. 7.

At 915, the method may include transmitting, to the network entity, at least one of the one or more CSI reports to the network entity in accordance with the first CPU value and based on the one or more measurements satisfying the measurement threshold that triggers the event condition. The operations of 915 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 915 may be performed by a CSI component 730 as described with reference to FIG. 7.

The following provides an overview of aspects of the present disclosure:

Aspect 1: A method for wireless communications at a UE, comprising: receiving, from a network entity, one or more reference signals via one or more beams; generating one or more CSI reports based at least in part on a first CPU value and on one or more measurements of the one or more reference signals satisfying a threshold that triggers an event condition; transmitting, to the network entity, at least one of the one or more CSI reports in accordance with the first CPU value and based at least in part on the one or more measurements satisfying the measurement threshold that triggers the event condition.

Aspect 2: The method of aspect 1, further comprising: applying a priority rule for transmission of the one or more CSI reports, wherein the priority rule indicates a priority ordering for transmission of event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and aperiodic CSI reports, wherein the at least one of the one or more CSI reports is transmitted in accordance with the priority rule.

Aspect 3: The method of aspect 2, wherein the priority ordering indicates an order in which event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and aperiodic CSI reports utilize one or more CPUs corresponding to the first CPU value, wherein transmitting the at least one of the one or more CSI reports comprises: transmitting one or more aperiodic CSI reports prior to one or more event-triggered CSI reports according to the priority ordering; and transmitting one or more semi-persistent CSI reports or periodic CSI reports after the one or more event-triggered CSI reports according to the priority ordering.

Aspect 4: The method of any of aspects 2 through 3, wherein the priority ordering indicates an order in which event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and aperiodic CSI reports utilize one or more CPUs corresponding to the first CPU value, wherein transmitting the at least one of the one or more CSI reports comprises: transmitting one or more event-triggered CSI reports prior to one or more aperiodic CSI reports, semi-persistent CSI reports, or periodic CSI reports according to the priority ordering.

Aspect 5: The method of any of aspects 2 through 4, wherein the priority ordering indicates an order in which event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and aperiodic CSI reports utilize one or more CPUs corresponding to the first CPU value, wherein transmitting the at least one of the one or more CSI reports comprises: transmitting one or more aperiodic CSI reports, semi-persistent CSI reports, or periodic CSI reports prior to one or more event-triggered CSI reports in accordance with the priority ordering.

Aspect 6: The method of any of aspects 1 through 5, further comprising: receiving, from the network entity, one or more additional reference signals via the one or more beams; generating one or more additional CSI reports based at least in part on a second CPU value and on one or more additional measurements of the one or more additional reference signals satisfying the measurement threshold that triggers the event condition, wherein the second CPU value is based at least in part on a quantity of CSI measurement-only instances and a quantity of measurement-and-reporting instances during a time period; and transmitting, to the network entity, at least one additional CSI report of the one or more additional CSI reports in accordance with the second CPU value and based at least in part on the one or more additional measurements satisfying the measurement threshold that triggers the event condition.

Aspect 7: The method of aspect 6, wherein further comprising: applying a first offset to the quantity of CSI measurement-only instances and a second offset to the quantity of measurement-and-reporting instances, wherein the second CPU value is based at least in part on application of the first offset, the second offset, or both.

Aspect 8: The method of any of aspects 6 through 7, further comprising: applying a same offset to the quantity of CSI measurement-only instances and to the quantity of measurement-and-reporting instances, wherein the second CPU value is based at least in part on application of the same offset.

Aspect 9: The method of any of aspects 6 through 8, wherein a CPU value associated with measurement-only instances is set to a weighted CPU value associated with measurement-and-reporting instances, and the second CPU value is based at least in part on the CPU value associated with measurement-only instances and the weighted CPU value associated with measurement-and-reporting instances.

Aspect 10: The method of any of aspects 6 through 9, wherein a CPU value associated with measurement-and-reporting instances is set to a weighted CPU value associated with one or more aperiodic, semi-persistent, or periodic CSI report instances, and the second CPU value is based at least in part on the CPU value associated with measurement-and reporting-instances and the weighted CPU value associated with the one or more aperiodic, semi-persistent, or periodic CSI report instances.

Aspect 11: The method of any of aspects 1 through 10, further comprising: transmitting, to the network entity, an indication of a capability of the UE, the capability indicating a plurality of CPU values capable of implementation by the UE.

Aspect 12: The method of aspect 11, wherein the plurality of CPU values comprises one or more fractional values.

Aspect 13: A UE for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 12.

Aspect 14: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 12.

Aspect 15: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 12.

It should be noted that the methods described herein describe possible implementations. The operations and the steps may be rearranged or otherwise modified and other implementations are possible. Further, aspects from two or more of the methods may be combined.

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.

Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a graphics processing unit (GPU) , a neural processing unit (NPU) , an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the 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 in conjunction with a DSP core, or any other such configuration) . Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.

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

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed 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, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.

As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” ) indicates an inclusive list such that, for example, a list of at least one of 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) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ”

As used herein, including in the claims, the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. For example, if a claim recites “acomponent” that performs 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 “acomponent” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components, ” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ”

The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure) , ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) , and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label or other subsequent reference label.

The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration” and not “preferred” or “advantageous over other examples. ” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

A user equipment (UE) , comprising:

one or more memories storing processor-executable code; and

one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to:

receive, from a network entity, one or more reference signals via one or more beams;

generate one or more channel state information (CSI) reports based at least in part on a first CSI processing unit (CPU) value and on one or more measurements of the one or more reference signals satisfying a measurement threshold that triggers an event condition;

transmit, to the network entity, at least one of the one or more CSI reports to the network entity in accordance with the first CPU value and based at least in part on the one or more measurements satisfying the measurement threshold that triggers the event condition.
The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

apply a priority rule for transmission of the one or more CSI reports, wherein the priority rule indicates a priority ordering for transmission of event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and aperiodic CSI reports, wherein the at least one of the one or more CSI reports is transmitted in accordance with the priority rule.
The UE of claim 2, wherein, to transmit the at least one of the one or more CSI reports, the one or more processors are individually or collectively operable to execute the code to cause the UE to:

transmit one or more aperiodic CSI reports prior to one or more event-triggered CSI reports according to the priority ordering; and

transmit one or more semi-persistent CSI reports or periodic CSI reports after the one or more event-triggered CSI reports according to the priority ordering.
The UE of claim 2, wherein, to transmit the at least one of the one or more CSI reports, the one or more processors are individually or collectively operable to execute the code to cause the UE to:

transmit one or more event-triggered CSI reports prior to one or more aperiodic CSI reports, semi-persistent CSI reports, or periodic CSI reports according to the priority ordering.
The UE of claim 2, wherein, to transmit the at least one of the one or more CSI reports, the one or more processors are individually or collectively operable to execute the code to cause the UE to:

transmit one or more aperiodic CSI reports, semi-persistent CSI reports, or periodic CSI reports prior to one or more event-triggered CSI reports in accordance with the priority ordering.
The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

receive, from the network entity, one or more additional reference signals via the one or more beams;

generate one or more additional CSI reports based at least in part on a second CPU value and on one or more additional measurements of the one or more additional reference signals satisfying the measurement threshold that triggers the event condition, wherein the second CPU value is based at least in part on a quantity of CSI measurement-only instances and a quantity of measurement-and-reporting instances during a time period; and

transmit, to the network entity, at least one additional CSI report of the one or more additional CSI reports in accordance with the second CPU value and based at least in part on the one or more additional measurements satisfying the measurement threshold that triggers the event condition.
The UE of claim 6, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

apply a first offset to the quantity of CSI measurement-only instances and a second offset to the quantity of measurement-and-reporting instances, wherein the second CPU value is based at least in part on application of the first offset, the second offset, or both.
The UE of claim 6, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

apply a same offset to the quantity of CSI measurement-only instances and to the quantity of measurement-and-reporting instances, wherein the second CPU value is based at least in part on application of the same offset.
The UE of claim 6, wherein:

a CPU value associated with measurement-only instances is set to a weighted CPU value associated with measurement-and-reporting instances, and

the second CPU value is based at least in part on the CPU value associated with measurement-only instances and the weighted CPU value associated with measurement-and-reporting instances.
The UE of claim 6, wherein:

a CPU value associated with measurement-and-reporting instances is set to a weighted CPU value associated with one or more aperiodic, semi-persistent, or periodic CSI report instances, and

the second CPU value is based at least in part on the CPU value associated with measurement-and reporting-instances and the weighted CPU value associated with the one or more aperiodic, semi-persistent, or periodic CSI report instances.
The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

transmit, to the network entity, an indication of a capability of the UE, the capability indicating a plurality of CPU values capable of implementation by the UE.
The UE of claim 11, wherein:

the plurality of CPU values comprises one or more fractional values.
A method for wireless communications at a user equipment (UE) , comprising:

receiving, from a network entity, one or more reference signals via one or more beams;

generating one or more channel state information (CSI) reports based at least in part on a first CSI processing unit (CPU) value and on one or more measurements of the one or more reference signals satisfying a measurement threshold that triggers an event condition;

transmitting, to the network entity, at least one of the one or more CSI reports to the network entity in accordance with the first CPU value and based at least in part on the one or more measurements satisfying the measurement threshold that triggers the event condition.
The method of claim 13, further comprising:

applying a priority rule for transmission of the one or more CSI reports, wherein the priority rule indicates a priority ordering for transmission of event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and aperiodic CSI reports, wherein the at least one of the one or more CSI reports is transmitted in accordance with the priority rule.
The method of claim 14, wherein the priority ordering indicates an order in which event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and aperiodic CSI reports utilize one or more CPUs corresponding to the first CPU value, wherein transmitting the at least one of the one or more CSI reports comprises:

transmitting one or more aperiodic CSI reports prior to one or more event-triggered CSI reports according to the priority ordering; and

transmitting one or more semi-persistent CSI reports or periodic CSI reports after the one or more event-triggered CSI reports according to the priority ordering.
The method of claim 14, wherein the priority ordering indicates an order in which event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and aperiodic CSI reports utilize one or more CPUs corresponding to the first CPU value, wherein transmitting the at least one of the one or more CSI reports comprises:

transmitting one or more event-triggered CSI reports prior to one or more aperiodic CSI reports, semi-persistent CSI reports, or periodic CSI reports according to the priority ordering.
The method of claim 14, wherein the priority ordering indicates an order in which event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and aperiodic CSI reports utilize one or more CPUs corresponding to the first CPU value, wherein transmitting the at least one of the one or more CSI reports comprises:

transmitting one or more aperiodic CSI reports, semi-persistent CSI reports, or periodic CSI reports prior to one or more event-triggered CSI reports in accordance with the priority ordering.
The method of claim 13, further comprising:

receiving, from the network entity, one or more additional reference signals via the one or more beams;

generating one or more additional CSI reports based at least in part on a second CPU value and on one or more additional measurements of the one or more additional reference signals satisfying the measurement threshold that triggers the event condition, wherein the second CPU value is based at least in part on a quantity of CSI measurement-only instances and a quantity of measurement-and-reporting instances during a time period; and

transmitting, to the network entity, at least one additional CSI report of the one or more additional CSI reports in accordance with the second CPU value and based at least in part on the one or more additional measurements satisfying the measurement threshold that triggers the event condition.
The method of claim 13, further comprising:

transmitting, to the network entity, an indication of a capability of the UE, the capability indicating a plurality of CPU values capable of implementation by the UE, wherein the plurality of CPU values comprises one or more fractional values.
A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to:

receive, from a network entity, one or more reference signals via one or more beams;

generate one or more channel state information (CSI) reports based at least in part on a first CSI processing unit (CPU) value and on one or more measurements of the one or more reference signals satisfying a measurement threshold that triggers an event condition;

transmit, to the network entity, at least one of the one or more CSI reports to the network entity in accordance with the first CPU value and based at least in part on the one or more measurements satisfying the measurement threshold that triggers the event condition.