Processing criteria for event-driven channel state reporting

Abstract

Methods, systems, and devices are described for processing criteria for event-driven channel state reporting. The described techniques allow for sending a CSI report based on when a UE determines that a trigger of an event condition has occurred. The trigger can be based on determining that there is a deficiency in quality of a channel associated with a received reference signal. Upon determining that the trigger of the event condition has occurred, the UE can then generate a CSI report to send to a network entity. Additionally, the UE can determine an optimal CSI processing unit (CPU) value, which can determine an amount of processing resources that the UE can utilize when generating the CSI report.

Description

Technical Field

[0001] The following pertains to wireless communications, including processing guidelines for event-driven channel state reporting. Background Technology

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

[0003] Channel State Information (CSI) resources (e.g., CSI-RS) can be measured by the UE to estimate the channel quality between the base station and the UE, where channel quality can be indicated by measured parameters (e.g., Channel Quality Indicator (CQI), Pre-decoding Matrix Indicator (PMI), Rank Indicator (RI), Reference Signal Received Power (RSRP)). The UE can send a CSI report to the base station indicating the channel quality information that the base station can use for data transmission. The base station may want to use this report for future scheduling. Conventional CSI reporting techniques have limitations. Summary of the Invention

[0004] The described technology relates to methods, systems, devices, and apparatuses that support improved processing criteria for event-driven channel state reporting. For example, the described technology enables a user equipment (UE) to send a channel state information (CSI) report based on when (or whether) the UE determines that an event condition has been triggered. This trigger may be based on determining that the channel associated with a received reference signal has quality deficiencies. Upon determining that the event condition has been triggered, the UE can then generate a CSI report to send to a base station. Additionally, the UE can determine an optimal CSI processing unit (CPU) value, which determines the amount of processing resources available to the UE when generating the CSI report. Besides providing the number of measurements and reports the UE can generate, the CPU value can also affect the amount of processing capacity.

[0005] A method for wireless communication by a user equipment (UE) is described. The method may include: receiving one or more reference signals from a network entity via one or more beams; generating one or more CSI reports based on a first channel state information (CSI) processing unit (CPU) value and a measurement threshold based on one or more measurements of the one or more reference signals satisfying a trigger event condition; and transmitting at least one of the one or more CSI reports to the network entity based on the first CPU value and the measurement threshold based on the one or more measurements satisfying the trigger event condition.

[0006] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute code to cause the UE to: receive one or more reference signals from a network entity via one or more beams; generate one or more CSI reports based on a first CSI processing unit (CPU) value and a measurement threshold based on one or more measurements of the one or more reference signals satisfying a trigger event condition; and transmit at least one of the one or more CSI reports to the network entity based on the first CPU value and the measurement threshold based on the one or more measurements satisfying the trigger event condition.

[0007] Another UE for wireless communication is described. The UE may include: components for receiving one or more reference signals from a network entity via one or more beams; components for generating one or more CSI reports based on a first CSI processing unit (CPU) value and a measurement threshold based on one or more measurements of the one or more reference signals satisfying a trigger event condition; and components for sending at least one of the one or more CSI reports to the network entity based on the first CPU value and the measurement threshold based on one or more measurements satisfying the trigger event condition.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive one or more reference signals from a network entity via one or more beams; generate one or more CSI reports based on a first CSI processing unit (CPU) value and a measurement threshold based on one or more measurements of the one or more reference signals satisfying a trigger event condition; and transmit at least one of the one or more CSI reports to the network entity based on the first CPU value and the measurement threshold based on the one or more measurements satisfying the trigger event condition.

[0009] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include features, components, or instructions for performing the following operations: applying priority rules to the transmission of one or more CSI reports, wherein the priority rules indicate the priority ordering of the transmission of event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and non-periodic CSI reports, wherein at least one of the one or more CSI reports may be transmitted according to the priority rules.

[0010] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, sending at least one of one or more CSI reports may include operations, features, components, or instructions for: sending one or more non-periodic CSI reports prior to one or more event-triggered CSI reports in order of priority; and sending one or more semi-persistent or periodic CSI reports after one or more event-triggered CSI reports in order of priority.

[0011] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, sending at least one of one or more CSI reports may include operations, features, components, or instructions for sending one or more event-triggered CSI reports prior to one or more non-periodic, semi-persistent, or periodic CSI reports in a priority order.

[0012] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, sending at least one of one or more CSI reports may include operations, features, components, or instructions for sending one or more non-periodic CSI reports, semi-persistent CSI reports, or periodic CSI reports in order of priority prior to one or more event-triggered CSI reports.

[0013] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing: receiving one or more additional reference signals from a network entity via one or more beams; generating one or more additional CSI reports based on a second CPU value and a measurement threshold based on one or more additional measurements of the one or more additional reference signals satisfying a trigger event condition, wherein the second CPU value may be based on the number of CSI-only measurement instances and the number of measurement and reporting instances during a time period; and sending at least one of the one or more additional CSI reports to the network entity based on the second CPU value and the measurement threshold based on one or more additional measurements satisfying a trigger event condition.

[0014] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: applying a first offset to the number of CSI-only measurement instances and applying a second offset to the number of measurement and reporting instances, wherein the second CPU value may be based on the application of the first offset, the second offset, or both.

[0015] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: applying the same offset to the number of CSI-only measurement instances and the number of measurement and reporting instances, wherein a second CPU value may be based on the application of the same offset.

[0016] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, the CPU value associated with a measurement-only instance may be set as a weighted CPU value associated with a measurement and reporting instance, and a second CPU value may be based on the CPU value associated with the measurement-only instance and the weighted CPU value associated with the measurement and reporting instance.

[0017] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, the CPU value associated with a measurement and reporting instance may be set as a weighted CPU value associated with one or more aperiodic, semi-persistent, or periodic CSI reporting instances, and a second CPU value may be based on the CPU value associated with the measurement and reporting instance and the weighted CPU value associated with one or more aperiodic, semi-persistent, or periodic CSI reporting instances.

[0018] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication to a network entity of the UE's capabilities, which in turn indicate a set of multiple CPU values ​​that the UE can implement.

[0019] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the set of multiple CPU values ​​includes one or more fractional values. Attached Figure Description

[0020] Figure 1 An example of a wireless communication system is shown that supports processing guidelines for event-driven channel state reporting according to one or more aspects of this disclosure.

[0021] Figure 2An example of a wireless communication system is shown that supports processing guidelines for event-driven channel state reporting according to one or more aspects of this disclosure.

[0022] Figure 3A and Figure 3B An example of a CSI processing configuration supporting processing guidelines for event-driven channel state reporting, according to one or more aspects of this disclosure, is shown.

[0023] Figure 4 An example of a process flow supporting processing guidelines for event-driven channel state reporting, according to one or more aspects of this disclosure, is shown.

[0024] Figure 5 and Figure 6 A block diagram of an apparatus supporting processing criteria for event-driven channel state reporting, according to one or more aspects of this disclosure, is shown.

[0025] Figure 7 A block diagram of a communication manager supporting processing guidelines for event-driven channel state reporting, according to one or more aspects of this disclosure, is shown.

[0026] Figure 8 A diagram of a system including a device supporting processing criteria for event-driven channel state reporting, according to one or more aspects of this disclosure, is shown.

[0027] Figure 9 A flowchart illustrating a method for processing criteria for event-driven channel state reporting, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0028] User equipment (UE) can use reference signals (such as Channel State Information (CSI) Reference Signals (CSI-RS)) to estimate the channel quality between the base station and the UE, and the UE can send CSI reports indicating channel quality information to network entities. In some systems (e.g., New Radio (NR) wireless communication systems), there may be a CSI Processing Unit (CPU) value, where the CPU value may be equal to the number of CSI calculations that the UE supports performing simultaneously. The CPU value may be a computing engine capable of performing CSI calculations or measurements reported in or indicated by a CSI report, which may be aperiodic, semi-persistent, periodic, event-driven, etc.

[0029] When a network entity signals to the UE to send a report, CSI reporting can be performed on a periodic, semi-persistent, or aperiodic basis. This can lead to excessively long CSI reporting periods, potentially resulting in outdated channel information. However, excessively frequent CSI reporting can lead to higher overhead and latency issues. Additionally, when generating a CSI report, the UE can allocate a portion of its available CPU to perform one or more CSI calculations for that report. In some cases, there may not be enough CPU available because the UE has already allocated some CPU to perform ongoing CSI calculations to generate one or more additional CSI reports. In other cases, excessive CPU allocation may occur, resulting in inefficient resource utilization.

[0030] To mitigate these issues, processing criteria for event-driven channel state reporting can be employed. The UE can initiate a CSI reporting process based on its own determination that channel measurements have deteriorated to the point where a measurement threshold (e.g., exceeding or falling below the measurement threshold) is met, thus triggering a CSI reporting event condition. Additionally, the UE can determine a CPU value that determines the amount of processing resources available to the UE when generating a CSI report. Besides providing the number of measurements and reports the UE can generate, the CPU value can also influence the amount of processing capacity.

[0031] Specific aspects of the subject matter described herein can be implemented to achieve one or more advantages. The described techniques can support improved CSI processing, reduced processing time, and increased data throughput, among other things. Therefore, supported techniques may include improved network operation, and in some examples, improved network efficiency, etc.

[0032] The aspects of this disclosure are first described in the context of a wireless communication system. Further examples illustrating CSI processing techniques when transmitting CSI reports are then provided. The aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to processing guidelines for event-driven channel state reporting.

[0033] Figure 1An example of a wireless communication system 100 supporting processing guidelines for event-driven channel state reporting according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include: one or more devices, such as one or more network devices (e.g., network entity 105); one or more UEs 115; and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

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

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

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

[0039] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed among multiple network entities (e.g., network entity 105), such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration advocated by O-RAN), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a central unit (CU) such as CU 160, a distributed unit (DU) such as DU 165, a radio unit (RU) such as RU 170, a RAN intelligent controller (RIC) such as RIC 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system such as SMO system 180, or any combination thereof. RU 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0059] UE 115 can measure CSI-RS resources to estimate channel quality, which can be indicated by measured channel quality parameters (e.g., CQI, PMI, RI, RSRP). UE 115 can send a CSI report to network entity 105 indicating the measured channel quality parameters for the CSI reference resource slot. Network entity 105 can use the CSI report for future scheduling. Additionally or alternatively, UE 115 can initiate the CSI reporting process based on its own determination that: channel measurements have deteriorated to the point of triggering a measurement threshold, resulting in a CSI reporting event condition; the channel associated with the received reference signal is of insufficient quality. Upon determining that the event condition has been triggered, the UE can then generate a CSI report to send to network entity 105. Additionally, UE 115 can determine a CPU value, which can correspond to the amount of processing resources available to the UE when generating the CSI report. In addition to providing the number of measurements and reports that UE 115 can generate, the CPU value can also affect the amount of processing capacity.

[0060] Figure 2 An example of a wireless communication system 200 supporting processing guidelines for event-driven channel state reporting, according to one or more aspects of this disclosure, is shown. The wireless communication system 200 may include a network entity 105-a and a UE 115-a, which may be as described in reference... Figure 1 Examples of network entity 105 and UE 115 described. Network entity 105-a may serve 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 event-driven channel state reporting to send CSI reports to network entity 105-a based on triggered event conditions and according to CPU values.

[0061] Network entity 105-a may transmit a CSI reference signal 210 within one or more CSI resources for UE 115-a to measure and estimate the channel quality of the communication link 205 between network entity 105-a and UE 115-a. UE 115-a may send a CSI report 220 to network entity 105-a indicating channel quality information that network entity 105-a can use to schedule subsequent data transmissions. In some examples, UE 115-a may send the CSI report 220 to network entity 105-a periodically, aperiodically, or semi-persistently. In other examples, UE 115-a may transmit the CSI report 220 based on event conditions triggered at the UE. For example, UE 115-a may determine that the reference signal 210 indicates that the channel is below a signal power or quality threshold. This power or quality threshold may be determined based on 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 met, it can also indicate that an event condition has been triggered, which initiates a CSI reporting procedure. This procedure may include UE 115-a signaling network entity 105-a to signal uplink resources available for UE 115-a to send a CSI report, or the procedure may include UE 115-a using previously scheduled resources to send a CSI report.

[0062] UE 115-a can apply priority rules to the transmission of one or more CSI reports. UE 115-a can use these priority rules to prioritize the transmission of event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and non-periodic CSI reports. For example, a first priority rule might prioritize the transmission of non-periodic CSI reports, followed by event-triggered CSI reports, and then semi-persistent / periodic CSI reports. A second priority rule might prioritize the transmission of event-triggered CSI reports, followed by any non-periodic, semi-persistent, and periodic CSI reports. A third priority rule might prioritize the transmission of any non-periodic, semi-persistent, and periodic CSI reports, followed by event-triggered CSI reports. After determining the transmission priorities, UE 115-a can then transmit one or more CSI reports.

[0063] The UE capability regarding the configured CPU value 225 can also affect CSI reporting. The CPU value 225 may be equal to the number of CSI calculations that UE 115-a can simultaneously support. UE 115-a may be capable of performing a fixed number of CSI calculations. UE 115-a may send an indication of its UE capability to network entity 105-a, where the capability indicates multiple CPU values ​​225 that UE 115-a can achieve. The CPU value 225 may include both integer and fractional values. UE 115-a can determine the optimal CPU value 225 for channel condition measurements and for the generation and transmission of CSI reports. For example, UE 115-a may utilize a lower CPU value 225 when fewer measurements and CSI reports are required, and a higher CPU value 225 when more measurements and CSI reports are required. UE 115-a may utilize different CPU values ​​225 in different instances of channel condition measurements and CSI reporting based on varying circumstances. For example, CPU consumption may be lower when the event condition has not yet been triggered because resources are only needed for measurement and not for reporting. Conversely, CPU consumption may be higher when the event condition has been triggered and resources are requested for both measurement and reporting.

[0064] Figure 3A and Figure 3B Examples of CSI processing configurations 300 and 350 supporting processing criteria for event-driven channel state reporting, according to one or more aspects of this disclosure, are shown. CPU processing configurations 300 and 350 may illustrate various instances of determining CPU values ​​based on different channel state measurement scenarios.

[0065] CPU processing configuration 300 can illustrate two different scenarios for the channel state measurement process. For example, scenario 310 can illustrate a scenario where UE 115 can perform channel state measurements without generating any corresponding CSI reports. In scenario 310, the corresponding CPU value... O CPU_meas_only It can indicate the CPU value available to UE 115 during a given time period.

[0066] In another example, scenario 320 illustrates a scenario where UE 115, in addition to generating one or more corresponding CSI reports, can also perform channel state measurements of the channel. Under scenario 320, the corresponding CPU value... O CPU_meas_and_reportThis indicates the CPU value available to UE 115 during a given time period. As illustrated in scenario 310, scenario 320 may require a higher CPU value than scenario 310 due to the additional processing resources needed to generate the CSI report. The CPU value utilized by UE 115 can be either an integer or a fraction. As possible examples only, the CPU value could be 0, 1 / 2, 2 / 3, 1, 3 / 2, etc. UE 115 may also use other CPU values.

[0067] CPU processing configuration 350 can exemplify a scenario 360 in which UE 115 performs channel state measurement, detects that event condition 370 is met, and then generates one or more corresponding CSI reports due to the meeting of event condition 370. In scenario 360, the corresponding CPU value... O CPU_meas and O CPU_report This indicates the CPU value available to UE 115 during a given time period. Here, the CPU value used for channel state measurements, in addition to generating one or more corresponding CSI reports, can be defined as two distinct CPU values. O CPU_meas It can be utilized by UE 115 prior to event condition 370, and O CPU_report It can be utilized by UE 115 after event condition 370 is detected.

[0068] In some examples, given a scenario where UE 115 performs channel state measurements and then generates one or more corresponding CSI reports due to the fulfillment of event conditions, the number of CSI-only measurement instances during a time period can be used as a basis. M ) and the number of measured and reported instances ( N To export the total CPU value, use the following command: In this example, the total CPU value is determined by combining the CPU values ​​of the measurement-only scenario with those of the separately calculated measurement and reporting scenarios.

[0069] In another example, given the number of CSI-only measurement instances during a time period ( M ) and the number of measured and reported instances ( N The total CPU value can be determined as follows: In this example, the total CPU value is determined by jointly calculating the CPU values ​​of the measurement-only scenario and the measurement and reporting scenario.

[0070] In some examples, given the number of CSI measurement instances only during a time period (M ) and the number of measured and reported instances ( N One or more offsets can be introduced when calculating the total CPU value. In this scenario, O CPU_meas_only and O CPU_meas_and_report The two corresponding CPU values ​​can be defined as integers (i.e., O CPU_meas_only = as well as O CPU_meas_and_report = (in ∈{0, 1, 2, ...} ∈{0, 1, 2, ...}), where these offset values ​​can be applied when calculating the final CPU value (for measurements only, represented as...). And for measurement and reporting, it is expressed as ):

[0071] The number of CSI measurement instances based on a time period ( M ) and the number of measured and reported instances ( N In the first example, how can offsets be used to determine the total CPU value?

[0072] The number of CSI measurement instances based on a time period ( M ) and the number of measured and reported instances ( N In the second example, how can offsets be used to determine the total CPU value?

[0073] In another example of calculating the total CPU value using offset values, a single CPU value and a single offset value can be defined, where a single CPU is represented as... O CPU_event_driven (= O CPU_meas_only = O CPU_meas_and_report ), and the offset is expressed as the number of CSI measurement instances only ( M ) and the number of measured and reported instances ( N The functions of both (i.e., The total CPU value is based on applying the same offset value to both CSI measurement instances and measurement and reporting instances.

[0074] In some examples, O CPU_meas_only andO CPU_meas_and_report The CPU values ​​can be weighted relative to each other. For example, there can be a relationship between them such that... O CPU_meas_only = ɑ O CPU_meas_and_report Instances where a <= 1 can be considered to have more weight placed on the CPU value associated with the measurement and reporting instance.

[0075] In other examples, in scenarios where periodic, semi-persistent, and non-periodic CSI reports (legacy reports) are consistent with event-driven CSI reports, a relationship may exist between the two, such that... O CPU_meas_and_report = β O CPU_legacy , where β is a weight that can be based on UE capabilities.

[0076] Figure 4 An example of a process flow 400 supporting processing guidelines for event-driven channel state reporting, according to one or more aspects of this disclosure, is shown. Process flow 400 may exemplify an example CSI processing procedure.

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

[0078] At 410, UE 115-b can generate one or more CSI reports based on event conditions triggered at UE 115-b. For example, UE 115-a can determine that the reference signal indicates the channel is below a signal power or quality threshold. Once UE 115-b determines that the measurement threshold has been met, it can also indicate that an event condition has been triggered, which initiates the generation of a CSI report. UE 115-b can generate a CSI report based on a first CPU value.

[0079] At 415, UE 115-b can send the generated CSI report based on the first CPU value and the event conditions that triggered it, and network entity 105-b can receive the generated CSI report.

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

[0081] At 425, based on event conditions occurring at UE 115-b due to the measurement of one or more additional reference signals, UE 115-b may generate one or more additional CSI reports. UE 115-b may have determined a second CPU value to be used when generating one or more additional CSI reports, wherein the second CPU value is different from the first CPU value.

[0082] At 430, UE 115-b can send the generated additional CSI report based on the second CPU value and the event conditions that triggered it, and network entity 105-b can receive the generated additional CSI report.

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

[0084] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels, and processing criteria for event-driven channel state reporting). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

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

[0086] The communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be examples of components used to perform various aspects of the processing criteria for event-driven channel state reporting as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be able to perform one or more of the functions described herein.

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

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

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

[0090] The communication manager 520 may support wireless communication according to examples disclosed herein. For example, the communication manager 520 may be capable of, configured to, or operable to support components for receiving one or more reference signals from a network entity via one or more beams. The communication manager 520 may be capable of, configured to, or operable to support components for generating one or more CSI reports based on a first CSI processing unit (CPU) value and a measurement threshold based on one or more measurements of one or more reference signals satisfying a trigger event condition. The communication manager 520 may be capable of, configured to, or operable to support components for sending at least one of the one or more CSI reports to a network entity based on a first CPU value and a measurement threshold based on one or more measurements satisfying a trigger event condition.

[0091] By including or configuring a communication manager 520 according to an example as described herein, device 505 (e.g., at least one processor that controls or otherwise couples to receiver 510, transmitter 515, communication manager 520, or a combination thereof) can support improved CSI processing, reduced processing time, and increased data throughput, etc. Therefore, supported technologies may include improved network operation, and in some examples, improved network efficiency, etc.

[0092] Figure 6 A block diagram 600 of a device 605 supporting processing guidelines for event-driven channel state reporting according to one or more aspects of this disclosure is shown. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605 or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0093] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels, and processing criteria for event-driven channel state reporting). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

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

[0095] Device 605 or its various components may be examples of parts for performing various aspects of the processing criteria for event-driven channel state reporting as described herein. For example, communication manager 620 may include reference signal component 625, CSI component 630, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use receiver 610, transmitter 615, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0096] Communication manager 620 may support wireless communication according to examples disclosed herein. Reference signal component 625 is capable of, configured to, or operable to support components for receiving one or more reference signals from a network entity via one or more beams. CSI component 630 is capable of, configured to, or operable to support components for generating one or more CSI reports based on a first CPU value and a measurement threshold based on one or more measurements of one or more reference signals satisfying a trigger event condition. CSI component 630 is capable of, configured to, or operable to support components for sending at least one of the one or more CSI reports to a network entity based on a first CPU value and a measurement threshold based on one or more measurements satisfying a trigger event condition.

[0097] Figure 7A block diagram 700 of a communication manager 720 supporting processing criteria for event-driven channel state reporting according to one or more aspects of this disclosure is shown. The communication manager 720 may be an example of aspects of the communication manager 520, communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of parts for implementing various aspects of the processing criteria for event-driven channel state reporting as described herein. For example, the communication manager 720 may include a reference signal component 725, a CSI component 730, a priority ordering component 735, a capability component 740, an offset component 745, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0098] Communication manager 720 may support wireless communication according to examples disclosed herein. Reference signal component 725 is capable of, configured to, or operable to support components for receiving one or more reference signals from a network entity via one or more beams. CSI component 730 is capable of, configured to, or operable to support components for generating one or more CSI reports based on a first CPU value and a measurement threshold based on one or more measurements of one or more reference signals satisfying a trigger event condition. In some examples, CSI component 730 is capable of, configured to, or operable to support components for sending at least one of the one or more CSI reports to a network entity based on a first CPU value and a measurement threshold based on one or more measurements satisfying a trigger event condition.

[0099] In some examples, the priority ordering component 735 is capable of, configured to, or operable to support components for applying priority rules to the transmission of one or more CSI reports, wherein the priority rules indicate the priority ordering of the transmission of event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and non-periodic CSI reports, wherein at least one of the one or more CSI reports is transmitted according to the priority rules.

[0100] In some examples, to support the transmission of at least one CSI report among one or more CSI reports, CSI component 730 is capable of, configured to, or operable to support components for prioritizing the transmission of one or more non-periodic CSI reports before one or more event-triggered CSI reports. In some examples, to support the transmission of at least one CSI report among one or more CSI reports, CSI component 730 is capable of, configured to, or operable to support components for prioritizing the transmission of one or more semi-persistent or periodic CSI reports after one or more event-triggered CSI reports.

[0101] In some examples, in order to support the transmission of at least one CSI report among one or more CSI reports, CSI component 730 is capable of, configured to, or can operate to support components for prioritizing the transmission of one or more event-triggered CSI reports before one or more non-periodic, semi-persistent, or periodic CSI reports.

[0102] In some examples, in order to support the transmission of at least one of one or more CSI reports, CSI component 730 is capable of, configured to, or can operate to support components for prioritizing the transmission of one or more non-periodic CSI reports, semi-persistent CSI reports, or periodic CSI reports before one or more event-triggered CSI reports.

[0103] In some examples, the reference signal component 725 is capable of, configured to, or operable to support components for receiving one or more additional reference signals from a network entity via one or more beams. In some examples, the CSI component 730 is capable of, configured to, or operable to support components for generating one or more additional CSI reports based on a second CPU value and a measurement threshold based on one or more additional measurements of one or more additional reference signals satisfying a trigger event condition, wherein the second CPU value is based on the number of CSI measurement instances only during a time period and the number of measurement and reporting instances. In some examples, the CSI component 730 is capable of, configured to, or operable to support components for sending at least one additional CSI report from one or more additional CSI reports to a network entity based on a second CPU value and a measurement threshold based on one or more additional measurements satisfying a trigger event condition.

[0104] In some examples, the offset component 745 is capable of, configured to, or able to operate to support components for applying a first offset to the number of CSI-only measurement instances and a second offset to the number of measurement and reporting instances, wherein the second CPU value is based on the application of the first offset, the second offset, or both.

[0105] In some examples, the offset component 745 is capable of, can be configured to, or is operable to support components for applying the same offset to the number of CSI-only measurement instances as well as the number of measurement and reporting instances, wherein the second CPU value is based on the application of the same offset.

[0106] In some examples, the CPU value associated with the measurement-only instance is set to the weighted CPU value associated with the measurement and reporting instances. In some examples, the second CPU value is based on both the CPU value associated with the measurement-only instance and the weighted CPU value associated with the measurement and reporting instances.

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

[0108] In some examples, capability component 740 is capable of, configured to, or able to operate to support components for sending an indication of a UE's capabilities to a network entity, the capability indication being a set of multiple CPU values ​​that can be implemented by the UE.

[0109] In some examples, the set of multiple CPU values ​​includes one or more score values.

[0110] Figure 8 A diagram of a system 800 including a device 805 supporting processing criteria for event-driven channel state reporting, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or may include components thereof. Device 805 may (e.g., wirelessly) communicate with one or more other devices (e.g., network entity 105, UE 115, or any combination thereof). Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 820, an input / output (I / O) controller (e.g., I / O controller 810), a transceiver 815, one or more antennas 825, at least one memory 830, code 835, and at least one processor 840. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 845).

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

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

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

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

[0115] In some examples, at least one processor 840 may include multiple processors, and at least one memory 830 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 840 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 840) and memory circuitry (which may include at least one memory 830)) or components that receive or receive input and process the input 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, at least one processor 840 or a processing system including at least one processor 840 may be configured, capable of being configured, or operable to cause device 805 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” can be used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code 835 (e.g., processor-executable code) stored in at least one memory 830 or otherwise.

[0116] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for receiving one or more reference signals from a network entity via one or more beams. The communication manager 820 may be capable of, configured to, or operable to support components for generating one or more CSI reports based on a first CSI processing unit (CPU) value and a measurement threshold based on one or more measurements of one or more reference signals satisfying a trigger event condition. The communication manager 820 may be capable of, configured to, or operable to support components for sending at least one of the one or more CSI reports to a network entity based on a first CPU value and a measurement threshold based on one or more measurements satisfying a trigger event condition.

[0117] By including or configuring a communication manager 820 according to an example as described herein, device 805 can support improved CSI processing, reduced processing time, and increased data throughput, etc. Therefore, supported technologies may include improved network operation, and in some examples, improved network efficiency, etc.

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

[0119] Figure 9 A flowchart illustrating a method 900 for processing criteria for event-driven channel state reporting, according to one or more aspects of this disclosure, is shown. The operation of method 900 can be implemented by a UE or its components as described herein. For example, the operation of method 900 can be implemented by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0120] At 905, the method may include receiving one or more reference signals from a network entity via one or more beams. Operation of 905 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 905 may be derived from, as in the reference... Figure 7 The reference signal component 725 described herein is executed.

[0121] At 910, the method may include generating one or more CSI reports based on a first CPU value and a measurement threshold based on one or more measurements of one or more reference signals satisfying a trigger event condition. The operation of 910 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 910 may be derived from, as referenced... Figure 7 The CSI component 730 is described and used for execution.

[0122] At point 915, the method may include sending at least one CSI report from one or more CSI reports to a network entity based on a first CPU value and a measurement threshold that satisfies a trigger event condition based on one or more measurements. The operation of point 915 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of point 915 may be provided by reference to [reference needed]. Figure 7 The CSI component 730 is described and used for execution.

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

[0124] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving one or more reference signals from a network entity via one or more beams; generating one or more CSI reports based at least in part on a first CPU value and on a threshold based on one or more measurements of the one or more reference signals satisfying a trigger event condition; and sending at least one of the one or more CSI reports to the network entity based on the first CPU value and at least in part on the measurement threshold based on the one or more measurements satisfying the trigger event condition.

[0125] Aspect 2: According to the method of aspect 1, the method further includes: applying a priority rule for the transmission of the one or more CSI reports, wherein the priority rule indicates the priority order of transmission of event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports and non-periodic CSI reports, wherein the at least one CSI report among the one or more CSI reports is transmitted according to the priority rule.

[0126] Aspect 3: According to the method of Aspect 2, wherein the priority ordering indicates that event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports and non-periodic CSI reports utilize the order of one or more CPUs corresponding to the first CPU value, wherein sending the at least one CSI report among the one or more CSI reports includes: sending one or more non-periodic CSI reports before the one or more event-triggered CSI reports according to the priority ordering; and sending 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.

[0127] Aspect 4: The method according to any one of Aspects 2 to 3, wherein the priority ordering indicates that event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports and non-periodic CSI reports utilize the order of one or more CPUs corresponding to the first CPU value, wherein sending the at least one CSI report among the one or more CSI reports comprises: sending one or more event-triggered CSI reports before one or more non-periodic CSI reports, semi-persistent CSI reports or periodic CSI reports according to the priority ordering.

[0128] Aspect 5: The method according to any one of Aspects 2 to 4, wherein the priority ordering indicates that event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports and non-periodic CSI reports utilize the order of one or more CPUs corresponding to the first CPU value, wherein sending the at least one CSI report among the one or more CSI reports comprises: sending one or more non-periodic CSI reports, semi-persistent CSI reports or periodic CSI reports before the one or more event-triggered CSI reports according to the priority ordering.

[0129] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: receiving one or more additional reference signals from the network entity 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 a measurement threshold based on one or more additional measurements of the one or more additional reference signals satisfying the event condition, wherein the second CPU value is at least in part based on the number of CSI-only measurement instances and the number of measurement and reporting instances during a time period; and sending at least one of the one or more additional CSI reports to the network entity based on the second CPU value and at least in part on the measurement threshold based on the one or more additional measurements satisfying the event condition.

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

[0131] Aspect 8: The method according to any one of Aspects 6 to 7, the method further comprising: applying the same offset to the number of CSI-only measurement instances and the number of measurement and reporting instances, wherein the second CPU value is based at least in part on the application of the same offset.

[0132] Aspect 9: The method according to any one of Aspects 6 to 8, wherein the CPU value associated with the measurement-only instance is set as a weighted CPU value associated with the measurement and reporting instance, and the second CPU value is based at least in part on the CPU value associated with the measurement-only instance and the weighted CPU value associated with the measurement and reporting instance.

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

[0134] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: sending to the network entity an indication of the capabilities of the UE, the capability indication being a plurality of CPU values ​​that can be implemented by the UE.

[0135] Aspect 12: According to the method of aspect 11, the plurality of CPU values ​​includes one or more fractional values.

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

[0137] Aspect 14: A UE for wireless communication, the UE comprising at least one component for performing a method according to any one of aspects 1 to 12.

[0138] Aspect 15: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of Aspects 1 to 12.

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Receive one or more reference signals from a network entity via one or more beams; One or more CSI reports are generated, at least in part based on the value of the first channel state information (CSI) processing unit (CPU) and based on a measurement threshold that satisfies the trigger event condition for one or more measurements of the one or more reference signals; At least one of the one or more CSI reports is sent to the network entity based on the first CPU value and at least in part on the measurement threshold that the one or more measurements satisfy the conditions for triggering the event.

2. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: A priority rule is applied to the transmission of the one or more CSI reports, wherein the priority rule indicates the priority order of transmission of event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and non-periodic CSI reports, wherein at least one of the one or more CSI reports is transmitted according to the priority rule.

3. The UE of claim 2, wherein, in order to send the at least one CSI report in the one or more CSI reports, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: Based on the aforementioned priority order, one or more non-periodic CSI reports are sent prior to one or more event-triggered CSI reports; and One or more semi-persistent CSI reports or periodic CSI reports are sent after the CSI reports triggered by the one or more events, according to the priority order.

4. The UE of claim 2, wherein, in order to send the at least one CSI report in the one or more CSI reports, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: Based on the aforementioned priority order, one or more event-triggered CSI reports are sent before one or more non-periodic, semi-persistent, or periodic CSI reports.

5. The UE of claim 2, wherein, in order to send the at least one CSI report in the one or more CSI reports, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: Based on the aforementioned priority order, one or more non-periodic CSI reports, semi-persistent CSI reports, or periodic CSI reports are sent before one or more event-triggered CSI reports.

6. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive one or more additional reference signals from the network entity via the one or more beams; One or more additional CSI reports are generated based at least in part on a second CPU value and on a measurement threshold that triggers the event condition based on one or more additional measurements of the one or more additional reference signals, wherein the second CPU value is based at least in part on the number of CSI measurement instances only and the number of measurement and reporting instances during a time period; as well as At least one additional CSI report from the one or more additional CSI reports is sent to the network entity based on the second CPU value and at least in part on the measurement threshold that the one or more additional measurements satisfy the conditions for triggering the event.

7. The UE of claim 6, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The first offset is applied to the number of CSI-only measurement instances, and the second offset is applied to the number of measurement and reporting instances, wherein the second CPU value is based at least in part on the application of the first offset, the second offset, or both.

8. The UE of claim 6, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The same offset is applied to the number of CSI-only measurement instances and the number of measurement and reporting instances, wherein the second CPU value is based at least in part on the application of the same offset.

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

10. The UE according to claim 6, wherein: The CPU value associated with the measurement and reporting instance is set to a weighted CPU value associated with one or more aperiodic, semi-persistent, or periodic CSI reporting instances, and The second CPU value is based at least in part on the CPU value associated with the measurement and reporting instance and the weighted CPU value associated with the one or more non-periodic, semi-persistent, or periodic CSI reporting instances.

11. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Send an indication of the UE's capabilities to the network entity, the capability indication including multiple CPU values ​​that the UE can implement.

12. The UE according to claim 11, wherein: The multiple CPU values ​​include one or more score values.

13. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive one or more reference signals from a network entity via one or more beams; One or more CSI reports are generated, at least in part based on the value of the first channel state information (CSI) processing unit (CPU) and based on a measurement threshold that satisfies the trigger event condition for one or more measurements of the one or more reference signals; At least one of the one or more CSI reports is sent to the network entity based on the first CPU value and at least in part on the measurement threshold that the one or more measurements satisfy the conditions for triggering the event.

14. The method according to claim 13, further comprising: A priority rule is applied to the transmission of the one or more CSI reports, wherein the priority rule indicates the priority order of transmission of event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and non-periodic CSI reports, wherein at least one of the one or more CSI reports is transmitted according to the priority rule.

15. The method of claim 14, wherein the priority ordering of event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and non-periodic CSI reports utilizes the order of one or more CPUs corresponding to the first CPU value, wherein sending the at least one CSI report among the one or more CSI reports comprises: Based on the aforementioned priority order, one or more non-periodic CSI reports are sent before one or more event-triggered CSI reports; as well as One or more semi-persistent CSI reports or periodic CSI reports are sent after the CSI reports triggered by the one or more events, according to the priority order.

16. The method of claim 14, wherein the priority ordering of event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and non-periodic CSI reports utilizes the order of one or more CPUs corresponding to the first CPU value, wherein sending the at least one CSI report among the one or more CSI reports comprises: Based on the aforementioned priority order, one or more event-triggered CSI reports are sent before one or more non-periodic, semi-persistent, or periodic CSI reports.

17. The method of claim 14, wherein the priority ordering of event-triggered CSI reports, periodic CSI reports, semi-persistent CSI reports, and non-periodic CSI reports utilizes the order of one or more CPUs corresponding to the first CPU value, wherein sending the at least one CSI report among the one or more CSI reports comprises: Based on the aforementioned priority order, one or more non-periodic CSI reports, semi-persistent CSI reports, or periodic CSI reports are sent before one or more event-triggered CSI reports.

18. The method according to claim 13, further comprising: Receive one or more additional reference signals from the network entity via the one or more beams; One or more additional CSI reports are generated based at least in part on a second CPU value and on a measurement threshold that triggers the event condition based on one or more additional measurements of the one or more additional reference signals, wherein the second CPU value is based at least in part on the number of CSI measurement instances only and the number of measurement and reporting instances during a time period; as well as At least one additional CSI report from the one or more additional CSI reports is sent to the network entity based on the second CPU value and at least in part on the measurement threshold that the one or more additional measurements satisfy the conditions for triggering the event.

19. The method according to claim 13, further comprising: The network entity sends an indication of the UE's capabilities, the capability indication being a plurality of CPU values ​​that the UE can achieve, wherein the plurality of CPU values ​​includes one or more fractional values.

20. A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to: Receive one or more reference signals from a network entity via one or more beams; One or more CSI reports are generated, at least in part based on the value of the first channel state information (CSI) processing unit (CPU) and based on a measurement threshold that satisfies the trigger event condition for one or more measurements of the one or more reference signals; At least one of the one or more CSI reports is sent to the network entity based on the first CPU value and at least in part on the measurement threshold that the one or more measurements satisfy the conditions for triggering the event.

Images