Techniques for reporting capacity gap metrics in multiple incremental redundancy schemes

Abstract

Methods, systems, and devices for wireless communication are described. Techniques described herein provide for reporting a capacity gap (G2C metric in a multiple incremental redundancy scheme (MIRS). The receiver may transmit information to the transmitter indicative of thermal noise or interference associated with the G2C metric. The transmitter may transmit a number of coding bits to the receiver based on the G2C metric and noise or interference associated with the G2C metric. In some examples, a transmitter may transmit signaling to a receiver indicating a configuration for reporting a G2C metric, noise data associated with the G2C metric, and interference data.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of Israel Patent Application No. 308189, filed November 1, 2023, entitled “TECHNIQUES FORREPORTING A GAP TO CAPACITY METRIC IN A MULTIPLE INCREMENTAL REDUNDANCYSCHEME”, which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including techniques for reporting capacity gap metrics in multi-incremental redundancy schemes. Background Technology

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

[0005] The described technology relates to improved methods, systems, devices, and apparatuses for supporting techniques used to report capacity gap (G2C) metrics in multi-incremental redundancy schemes. For example, the described technology enables a receiver to send information to a transmitter indicating thermal noise or interference associated with the G2C metric. The transmitter may send (and retransmit) a number of decoded bits to the receiver based on the G2C metric and the noise or interference associated with it. In some examples, the transmitter may send signaling to the receiver indicating a configuration for reporting the G2C metric, noise data associated with the capacity gap metric, interference data, or both. To report information indicating thermal noise, the receiver may send the value of the noise covariance matrix. In addition to the G2C metric, the receiver may also report the G2C metric and a hypothetical G2C where only thermal noise exists and no interference is present.

[0006] A method for wireless communication by a network entity is described. The method may include: sending signaling to a user equipment (UE) instructing the configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics; sending a transport block to the UE; receiving from the UE a feedback message indicating that reception of a portion of the transport block was unsuccessful, the G2C metrics, and the noise data, interference data, or both; and sending from the network entity a transport block having a number of one or more decoded bits, wherein the number of one or more decoded bits is based on the G2C metrics and the noise data, interference data, or both.

[0007] A network entity for wireless communication is described. The network entity may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be operable individually or collectively to execute code that causes the network entity to: send signaling to a UE instructing the network entity to: transmit signaling to the UE indicating a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics; transmit a transport block to the UE; receive from the UE a feedback message indicating that reception of a portion of the transport block was unsuccessful, along with the G2C metrics and the noise data, interference data, or both; and transmit a transport block having a number of one or more decoded bits, wherein the number of one or more decoded bits is based on the G2C metrics and the noise data, interference data, or both.

[0008] Another network entity for wireless communication is described. This network entity may include: components for sending to a UE signaling indicating a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics; components for sending transport blocks to the UE; components for receiving from the UE a feedback message indicating that reception of a portion of the transport block was unsuccessful, the G2C metrics, and noise data, interference data, or both; and components for sending from the network entity a transport block having a number of one or more decoded bits, wherein the number of one or more decoded bits is based on the G2C metrics and noise data, interference data, or both.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: send signaling to a UE instructing a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics; send a transport block to the UE; receive from the UE a feedback message indicating that reception of a portion of the transport block was unsuccessful, along with the G2C metrics and the noise data, interference data, or both; and send from a network entity a transport block having a number of one or more decoded bits, wherein the number of one or more decoded bits is based on the G2C metrics and the noise data, interference data, or both.

[0010] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include features, components, or instructions for receiving one or more values ​​of the noise covariance matrix from the UE.

[0011] In some examples of the methods, network entities, and nontransient computer-readable media described herein, one or more values ​​of the noise covariance matrix include one or more eigenvalues ​​of the noise covariance matrix.

[0012] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, one or more eigenvalues ​​include all eigenvalues ​​of the noise covariance matrix, a subset of the eigenvalues ​​of the noise covariance matrix, the strongest eigenvalue of the noise covariance matrix, or the weakest eigenvalue of the noise covariance matrix.

[0013] In some examples of the methods, network entities, and nontransient computer-readable media described herein, one or more values ​​of the noise covariance matrix include the condition number of the noise covariance matrix, one or more combined weights of the noise covariance matrix, or a combination thereof.

[0014] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving from a UE an indication of a noise covariance matrix and an indication of one or more combined weights of the noise covariance matrix.

[0015] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: receiving from the UE a feedback message indicating a second G2C metric, wherein the second G2C metric removes observed interference.

[0016] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the number of one or more decoded bits may be based in part on a second G2C metric.

[0017] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, configurations indicate frequency resources, time resources, or combinations thereof, and G2C metrics may be associated with frequency resources, time resources, or combinations thereof.

[0018] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, configuration indicates frequency resources, time resources, or combinations thereof, and noise data, interference data, or both may be associated with frequency resources, time resources, or combinations thereof.

[0019] A method for wireless communication by a UE is described. The method may include: receiving from a network entity signaling an indication of a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics; receiving a transport block from the network entity; sending to the network entity a feedback message indicating that reception of a portion of the transport block was unsuccessful, along with the G2C metrics and the noise data, interference data, or both; and receiving from the network entity a transport block having a number of one or more decoded bits, wherein the number of one or more decoded bits is based on the G2C metrics and the noise data, interference data, or both.

[0020] 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 be operable individually or collectively to execute code that causes the UE to: receive signaling from a network entity indicating a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics; receive a transport block from the network entity; send a feedback message to the network entity indicating that reception of a portion of the transport block was unsuccessful, along with the G2C metrics and the noise data, interference data, or both; and receive a transport block from the network entity having a number of one or more decoded bits, wherein the number of one or more decoded bits is based on the G2C metrics and the noise data, interference data, or both.

[0021] Another UE for wireless communication is described. The UE may include: components for receiving from a network entity signaling for a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics; components for receiving transport blocks from the network entity; components for sending to the network entity a feedback message indicating that reception of a portion of the transport block was unsuccessful, along with the G2C metrics and noise data, interference data, or both; and components for receiving from the network entity a transport block having a number of one or more decoded bits, wherein the number of one or more decoded bits is based on the G2C metrics and the noise data, interference data, or both.

[0022] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: receive from a network entity signaling an indication of a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics; receive a transport block from the network entity; send to the network entity a feedback message indicating that reception of a portion of the transport block was unsuccessful, along with the G2C metrics and the noise data, interference data, or both; and receive from the network entity a transport block having a number of one or more decoded bits, wherein the number of one or more decoded bits is based on the G2C metrics and the noise data, interference data, or both.

[0023] 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 operations such as sending one or more values ​​of the noise covariance matrix to a network entity.

[0024] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, one or more values ​​of the noise covariance matrix include one or more eigenvalues ​​of the noise covariance matrix.

[0025] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, one or more eigenvalues ​​include all eigenvalues ​​of the noise covariance matrix, a subset of the eigenvalues ​​of the noise covariance matrix, the strongest eigenvalue of the noise covariance matrix, or the weakest eigenvalue of the noise covariance matrix.

[0026] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, one or more values ​​of the noise covariance matrix include the condition number of the noise covariance matrix, one or more combined weights of the noise covariance matrix, or a combination thereof.

[0027] 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 of a noise covariance matrix and an indication of one or more combined weights of the noise covariance matrix to a network entity.

[0028] 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: sending a feedback message to a network entity indicative of a second G2C metric, wherein the second G2C metric removes the observed interference.

[0029] 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: estimating the variance of additive white Gaussian noise (AWGN) in part based on zero-power channel state information reference signal transmission or noise covariance matrix, wherein the second G2C may be based on one or more of the AWGN variance, the noise covariance matrix, the demodulator characteristics of the UE, or any combination thereof.

[0030] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the number of one or more decoded bits may be based in part on a second G2C metric.

[0031] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, the configuration indicates frequency resources, time resources, or a combination thereof, and G2C metrics may be associated with frequency resources, time resources, or a combination thereof.

[0032] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, configuration indicates frequency resources, time resources, or combinations thereof, and noise data, interference data, or both may be associated with frequency resources, time resources, or combinations thereof.

[0033] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and manner of operation) and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each figure in the drawings is provided for illustrative and descriptive purposes and not as a limitation of the definitions in the claims.

[0034] While aspects and implementations have been described in this application by way of example, those skilled in the art will understand that additional implementations and use cases can arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, various implementations and / or devices can be produced via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, AI-enabled devices, etc.). While some examples may or may not specifically point to a use case or application, the applicability of various types of the described innovations is evident. The scope of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for the implementation and practice of the embodiments protected and described in the claims. For example, the transmission and reception of wireless signals necessarily involve multiple components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) for analog and digital purposes. The innovations described herein are intended to be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user equipment, etc., with different sizes, shapes, and constructions. Attached Figure Description

[0035] Figure 1 An example of a wireless communication system is shown that supports techniques for reporting capacity gap (G2C) metrics in a multi-incremental redundancy scheme, according to one or more aspects of this disclosure.

[0036] Figure 2 An example of a wireless communication system is shown that supports techniques for reporting G2C metrics in a multi-incremental redundancy scheme, according to one or more aspects of this disclosure.

[0037] Figure 3 An example of a transmission diagram is shown that supports one or more aspects of this disclosure for reporting G2C metrics in a multi-incremental redundancy scheme.

[0038] Figure 4 An example of a process flow supporting techniques for reporting G2C metrics in multi-incremental redundancy schemes, according to one or more aspects of this disclosure, is shown.

[0039] Figure 5 and Figure 6 A block diagram of an apparatus supporting techniques for reporting G2C metrics in a multi-incremental redundancy scheme, according to one or more aspects of this disclosure, is shown.

[0040] Figure 7 A block diagram of a communication manager supporting techniques for reporting G2C metrics in a multi-incremental redundancy scheme, according to one or more aspects of this disclosure, is shown.

[0041] Figure 8 A diagram of a system including a device for supporting techniques for reporting G2C metrics in a multi-incremental redundancy scheme, according to one or more aspects of this disclosure, is shown.

[0042] Figure 9 and Figure 10 A block diagram of an apparatus supporting techniques for reporting G2C metrics in a multi-incremental redundancy scheme, according to one or more aspects of this disclosure, is shown.

[0043] Figure 11 A block diagram of a communication manager supporting techniques for reporting G2C metrics in a multi-incremental redundancy scheme, according to one or more aspects of this disclosure, is shown.

[0044] Figure 12 A diagram of a system including a device for supporting techniques for reporting G2C metrics in a multi-incremental redundancy scheme, according to one or more aspects of this disclosure, is shown.

[0045] Figures 13 to 14 A flowchart illustrating a method for reporting G2C metrics in a multi-incremental redundancy scheme, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0046] In some wireless communication systems, wireless devices may operate according to a Multiple Incremental Redundancy Scheme (MIRS). MIRS can be used to determine the modulation and decoding scheme (MCS) for communication between a network entity and a user equipment (UE) at or near channel capacity. For example, a network entity may send a transport block to the UE. The UE may send feedback indicating that reception of a portion of the transport block was unsuccessful (this is Hybrid Automatic Repeat Request (HARQ) feedback) and may send feedback indicating a certain number of parity bits or a small portion of the transport block for successful reception. The network entity may finely and dynamically adapt the decoding rate based on feedback from the receiving wireless device (e.g., ACK or NACK messages) using multiple small retransmissions (e.g., incremental retransmission of Hybrid Automatic Repeat Request (IR-HARQ)). When the UE sends a feedback (NACK), the network entity can adjust the next transmission of the transport block by including a certain number of additional decoding bits. However, multiple retransmissions increase the overall latency and the HARQ buffer size.

[0047] To mitigate the number of retransmissions in MIRS, the UE can report a capacity gap (G2C) metric to the network entity. The G2C metric indicates the size of the next retransmission based on mutual information calculated per bit. The network entity can evaluate the next transmission size based on the G2C metric and can retransmit a transport block including a certain number of additional decoded bits based on the G2C metric. That is, the next transmission can include a transport block reflecting the target code rate in the number of decoded bits based on the G2C metric. In some examples, the G2C metric may be limited by thermal noise or interference, and the determination of the next retransmission size may be adversely affected by thermal noise or interference.

[0048] The techniques described in this paper provide a process for reporting G2C metrics in MIRS. These techniques reduce the number of retransmissions in MIRS. The UE can report information indicating thermal noise and interference in the feedback, and network entities can determine the next transmission size based on the G2C metrics and the information indicating thermal noise and interference.

[0049] In some examples, the network entity may send signaling to the UE indicating configuration for reporting G2C metrics and indicating noise, interference, or both. Additionally, the network entity may send signaling to the UE requesting frequency-selective, time-selective, or a combination of frequency- and time-selective G2C metrics. The network entity may send a transport block to the UE. The UE may send a feedback message to the network entity indicating that reception of a portion of the transport block was unsuccessful, a G2C metric, noise data associated with the G2C metric, interference data associated with the G2C metric, or both noise and interference data associated with the G2C metric. In some examples, the feedback message may include HARQ-related feedback (e.g., regular HARQ feedback) indicating that, for transport block-based MIRS, the transport block was not successfully received, or indicating that, for block group-based MIRS, a portion of a code block was not successfully received. To report information indicating noise, the UE may send the values ​​of the noise covariance matrix in the feedback. For example, the UE may send the eigenvalues ​​of the noise covariance matrix. In another example, the UE may send the condition number of the noise covariance matrix or the combined weights of the noise covariance matrix. The network entity may send transport blocks and a number of additional decoding bits to the UE based on the G2C metric and on noise data, interference data, or both. In some examples, in addition to the G2C metric, the UE may also report a hypothetical G2C indicating the presence of only noise and no interference, and the network entity may send transport blocks and a number of additional decoding bits based on the hypothetical G2C metric.

[0050] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are also described in the context of transmission diagrams and process flows. The aspects of this disclosure are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to techniques for reporting G2C metrics in MIRS, and are described with reference to these diagrams.

[0051] Figure 1 An example of a wireless communication system 100 supporting techniques for reporting G2C metrics in a multi-incremental redundancy scheme, according to one or more aspects of this disclosure, is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

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

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

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

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

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

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

[0060] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support techniques as described herein for reporting G2C metrics in multi-incremental redundancy schemes. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

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

[0063] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to utilize 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 105).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0078] In some wireless communication systems, wireless devices may operate according to MIRS. MIRS can be used to determine the MCS for communication between network entity 105 and UE 115 at or near channel capacity. For example, network entity 105 may send a transport block to UE 115. UE 115 may send feedback indicating that reception of a portion of the transport block was unsuccessful (which is Hybrid Automatic Repeat Request (HARQ) feedback) and may send feedback indicating a certain number of parity bits or a small portion of the transport block for successful reception. Network entity 105 may finely and dynamically adapt the decoding rate using multiple small retransmissions (e.g., IR-HARQ) based on feedback from the receiving wireless device (e.g., ACK or NACK messages). When UE 115 sends feedback (NACK), network entity 105 may adjust the next transmission of the transport block by including a certain number of additional decoding bits. However, multiple retransmissions increase the overall latency and HARQ buffer size.

[0079] To mitigate the number of retransmissions in MIRS, UE 115 may report a G2C metric to network entity 105. The G2C metric can indicate the size of the next retransmission based on mutual information calculated per information bit. Network entity 105 can evaluate the next transmission size based on the G2C metric and can retransmit a transport block including a certain number of additional decoded bits based on the G2C metric. That is, the next transmission can include a transport block based on the G2C metric to reflect the target code rate in the number of decoded bits. In some examples, the G2C metric may be limited by thermal noise or interference, and the determination of the next retransmission size may be adversely affected by thermal noise or interference.

[0080] The techniques described herein provide a process for reporting G2C metrics in MIRS. These techniques reduce the number of retransmissions in MIRS. UE 115 can report information indicating thermal noise and interference in the feedback, and network entity 105 can determine the next transmission size based on the G2C metrics and the information indicating thermal noise and interference.

[0081] In some examples, network entity 105 may send signaling to UE 115 instructing the configuration for reporting G2C metrics and indicating noise, interference, or both. Additionally, network entity 105 may send signaling to UE 115 instructing the configuration for requesting frequency-selective, time-selective, or a combination of frequency and time-selective G2C metrics. Network entity 105 may send transport blocks to UE 115. UE 115 may, depending on its configuration, send a feedback message to network entity 105 indicating that reception of a portion of the transport block was unsuccessful, a G2C metric, noise data associated with the G2C metric, interference data associated with the G2C metric, or both noise and interference data associated with the G2C metric. In some examples, the feedback message may include HARQ-related feedback (e.g., regular HARQ feedback) indicating that, for transport block-based MIRS, the transport block was not successfully received, or indicating that, for block group-based MIRS, a portion of a block was not successfully received. To report information indicating noise, UE 115 may, depending on its configuration, send or otherwise indicate the value of the noise covariance matrix in the feedback (e.g., the configuration instructs UE 115 to provide feedback indicating one or more eigenvalues). For example, UE 115 may send one or more eigenvalues ​​of the noise covariance matrix. In another example, UE 115 may send the condition number of the noise covariance matrix or the combined weights of the noise covariance matrix. Network entity 105 may send transport blocks and a number of additional decoding bits to UE 115 based on G2C metrics and based on noise data, interference data, or both noise data and interference data. In some examples, in addition to G2C metrics, UE 115 may also report a hypothetical G2C indicating the presence of only noise and no interference, and network entity 105 may send transport blocks and a number of additional decoding bits based on the hypothetical G2C metric.

[0082] Figure 2 Examples of wireless communication system 200 supporting techniques for reporting G2C metrics in MIRS, according to one or more aspects of this disclosure, are shown. In some examples, wireless communication system 200 may implement aspects of wireless communication system 100. For example, wireless communication system 200 may include network entity 105-a and UE 115-a, which may be respectively as referenced herein. Figure 1 Examples of network entity 105 and UE 115 described.

[0083] Network entity 105-a and UE 115-a can be in wireless communication and can implement rate adaptation schemes for NR-based systems. In some examples, MIRS-based rate adaptation schemes can improve the gap between defined (e.g., optimal) link adaptations compared to link adaptation based on Channel State Information Reference Signal (CSI-RS). CSI-RS-based channel capacity tracking schemes may not be suitable for instantaneous optimal MCS because CSI-RS-based link adaptation does not utilize the full available channel capacity. Instantaneous optimal MCS can be the highest MCS that UE 115-a can successfully decode on a given TTI. One reason why CSI-RS-based link adaptation does not achieve instantaneous optimal MCS is that CSI-RS estimation may not accurately model the receiver's performance. Additionally, since the channel state is sampled at discrete times (e.g., CSI-RS slots) and the channel is variable, the optimal MCS and decoding rate may vary significantly between sampling slots. The channel may change when UE 115-a is stationary, and the channel may also change due to the movement of UE 115-a, with greater channel changes at high speeds. Optimal MCS between CSI time slots cannot be achieved using a link adaptation scheme based on CSI-RS because the optimal MCS between CSI time slots may change due to the speed of UE 115-a.

[0084] In CSI-RS-based link adaptation schemes, the implemented MCS (and specifically, the decoding rate) is set on the first transmission and may not be dynamically adapted. If the first transmission fails, approximately the same number of decoded bits are retransmitted. In a regular HARQ IR retransmission, the MCS remains the same, meaning that each allocated bit of the same size is retransmitted, and each allocated bit of the same size is added to the previous transmission, thus reducing the rate. The retransmission scheme provides a small set of redundant versions of the bits to be retransmitted. These bits are either the same decoded bits as the first transmission providing the same code rate (e.g., Chase combination) or new decoded bits that halve the effective decoding rate in the second retransmission (e.g., incremental redundancy). Therefore, the choice of decoding rate on the first transmission can significantly impact the outcome. An overestimated decoding rate can lead to decoding errors and potentially throughput loss. An underestimated decoding rate can lead to throughput loss because a larger payload may have already been transmitted on the same channel resources. Outer-loop link adaptation (OLLA) between CSI-RS slots is possible, but OLLA may not accurately track changes to the optimal MCS. Even with or without OLLA implementation, using the optimally selected MCS on the CSI slot for best CSI estimation may result in throughput performance that is less than the achievable performance per slot MCS selection.

[0085] MIRS can bridge the gap with the optimal MCS selection, and MIRS can achieve communication at high code rates regardless of the UE115-a's mobility and speed. (Reference) Figure 2 Network entity 105-a and UE 115-a can be in wireless communication and operate according to MIRS. For example, network entity 105-a can use MIRS to determine an efficient MCS and achieve communication with UE 115-a at or near the capacity code rate. For example, network entity 105-a can select an overestimated MCS to ensure that throughput is not lost due to an underestimated rate. Network entity 105-a can rely on extensive use of small retransmissions (e.g., IR-HARQ) based on feedback (e.g., NACK) to the transmitted UE 115-a to finely and dynamically adapt the decoding rate. That is, each time UE 115-a sends a NACK to network entity 105-a (or alternatively, does not send an ACK), network entity 105-a can add a small number of additional redundant bits to the transmission. In some examples, network entity 105-a can use per-block (CB) feedback to further improve channel utilization.

[0086] In some examples, to implement MIRS, a transmitter (such as network entity 105-a (e.g., gNobeB)) may select the MCS on the first transmission that is expected to cause MCS failure or overestimation. For example, network entity 105-a may send an initial transmission 205 to UE 115-a. The selection of the first transmission MCS determines the decoding parameters (e.g., rate and transport block size) used for all subsequent retransmissions. For each decoding failure, a receiver (such as UE 115-a) may send an enhanced feedback message 210 with the decoding result per CB or transport block. In some examples, the receiver (such as UE 115-a) may deliver additional information to enable the transmitter (e.g., network entity 105-a) to converge to an actually acceptable rate more quickly. For each failure indicated by the enhanced feedback message 210 from the receiver (UE 115-a), the transmitter (e.g., network entity 105-a) can schedule retransmissions at the desired rate, such that the combined rate after the HARQ IR combination will provide the same rate as the instantaneous condition at the time of reception, as fed back by the UE. The feedback may specifically indicate a buffer of decoded bits from the initial decoded bit buffer of the transport block, or it may specifically indicate a buffer of decoded bits from the initial decoded bit buffer of the failed CB required to provide the desired instantaneous rate. In some examples, MIRS may be CB-based, where each CB has a feedback G2C metric, and MIRS may be transport block-based, where each transport block has a smaller feedback G2C metric. For CB-based MIRS, the transmitter (e.g., network entity 105-a) may send a retransmission with additional bits (e.g., a subsequent modified transmission 215) to reduce the effective rate per code block. The added bits in each retransmission (e.g., each subsequent modified transmission 215) reduce the effective rate of each CB by fine steps until all CBs are successfully decoded by UE 115-a and thus the entire transport block is successfully decoded by UE 115-a. The total number of bits transmitted on the first transmission 205 and subsequent modified transmissions 215 determines the actual rate used for each transport block.

[0087] Figure 3 An example of a transmission diagram 300 supporting a technique for reporting G2C metrics in MIRS, according to one or more aspects of this disclosure, is shown. In some examples, the transmission diagram may be implemented by wireless communication system 200 and wireless communication system 100. For example, network entity 105-a may transmit an initial transmission 205 and a subsequent modified transmission 215 in the manner shown in Figure 300.

[0088] Transmission diagram 300 may include an initial transmission 205-a, a first subsequent modified transmission 215-a, a second subsequent modified transmission 215-b, and a third subsequent modified transmission 215-c, illustrating MIRS. In one example, each of the transmissions may include a transport block 305. The initial transmission 205-a may correspond to a decoding rate equivalent to MCS27. The first subsequent modified transmission 215-a may add a small number of additional decoding bits 310 to the first transmission 205-a to provide an effective decoding rate equivalent to MCS26. The decoding bits may be parity bits, which can be used for Chase combination or incremental redundancy for decoding transport block 305. Similarly, the second subsequent modified transmission 215-b may add a small number of additional decoding bits 315 to the first subsequent modified transmission 215-a to provide an effective decoding rate equivalent to MCS25. Similarly, the third subsequent modified transmission 215-c can add a small number of additional decoding bits 320 to the second subsequent modified transmission 215-b to provide an effective decoding rate equivalent to MCS24. This operational scheme is possible by using ACK or NACK reports (where each NACK reduces the MCS) without reporting the G2C metric in the enhanced feedback message 210. However, using the G2C metric in the enhanced feedback message 210 allows the transmitter to skip multiple MCS levels to the desired MCS to provide the required rate. That is, the enhanced feedback message 210 with the G2C metric allows the transmitter to immediately cross the gap to the desired MCS, hence the name capacity gap.

[0089] MIRS closely tracks channel variations and achieves higher throughput at high signal-to-noise ratios compared to CSI-RS. Optional per-CB feedback can be used primarily in MIRS to provide gains superior to the best MCS. Utilizing per-TB feedback, MIRS performance can match the best MCS across all speeds. MIRS based on multiple IR-HARQ retransmissions provides gains superior to CSI-RS and achieves channel capacity regardless of UE mobility. MIRS can provide gains exceeding 6dB across a wide range of channel models and speeds in noise-constrained scenarios. MIRS offers resilience to interference and can achieve gains in interference-constrained scenarios. CB-based MIRS provides improved performance and significant gains superior to CSI-RS. Transport block-based MIRS without interleavers also provides improved performance and significant gains superior to CSI-RS. Similarly, applying transport block MIRS with interleavers further improves performance with minimal degradation compared to CB-based MIRS. MIRS is resilient to interference and provides throughput gains across a wide range of signal-to-interference ratios.

[0090] MIRS can increase overall latency and HARQ buffer size. To mitigate the number of retransmissions in MIRS, UE 115-a can report an enhanced feedback message 210 indicating a G2C metric to network entity 105-a. The G2C metric can indicate the size of the next retransmission (e.g., a subsequent modified transmission 215) based on mutual information (MI) calculated per information bit. In the download example, UE 115-a can calculate an MI-based metric, representing the MI per information bit. UE 115-a can convert the MI-based metric into a G2C metric reported to network entity 105-a. Network entity 105-a can use the G2C metric to select the size of the next retransmission (e.g., the number of additional decoded bits to add to the previously transmitted transmission). The G2C metric can be reported via HARQ feedback (e.g., enhanced feedback message 210) for the received Physical Downlink Shared Channel (PDSCH).

[0091] In some examples, UE 115-a may receive an initial transmission 205 from network entity 105-a in a time slot, and the initial transmission 205 may include multiple CBs having a first decoding rate. For each CB, UE 115-a may calculate the CB MI by averaging the MI of all single LLRs of all CBs (e.g., the average MI that an LLR can carry) by averaging the MI of all received log likelihood ratios (LLRs) in the time slot, and may calculate the MI of each CB by averaging the MI of all LLRs associated with the CB (e.g., including punched LLRs).

[0092] In some examples, the numerical MI calculation for an LLR set can be illustrated using the following equation:

[0093]

[0094] In some examples, UE 115-a may assess the number of resources sufficient for retransmission to achieve the target MI metric based on a calculated average. The G2C metric may be the determined number of resources sufficient for retransmission to achieve the target MI metric. UE 115-a may send an enhanced feedback message 210 indicating the G2C metric to network entity 105-a. The G2C metric may be limited to f of the initial transmission resources. MIRS The product of. Network entity 105-a can evaluate the next transmission size based on the G2C metric and transmit a subsequent modified transmission 215, including a certain number of additional decoded bits, based on the G2C metric.

[0095] In some examples, G2C metrics may be limited by thermal noise or interference, and the determination of the next retransmission size may be adversely affected by thermal noise or interference. Thermal noise G2C metrics can change smoothly at a rate proportional to the UE rate report, and G2C metrics can be considered a reliable estimate of the retransmission size. Interference-limited G2C metrics (such as interference from other cells) may be more difficult to track and may change abruptly. In some cases, network entity 105-a may have prior information about expected interference, and network entity 105-a may be able to account for expected interference in the retransmission size. In another case, network entity 105-a may implement different backoff and different retransmission strategies for interference-limited and thermally-limited G2C. In some examples, it may be advantageous to report whether the G2C metric is interference-limited or thermally-limited.

[0096] In some cases, UE 115-a may report an enhanced feedback message 210 to network entity 105-a containing data indicating thermal noise data, interference data, or both. Network entity 105-a may send subsequent modified transmissions 215 (e.g., retransmissions of the initial transmission with a certain number of decoded bits) based in part on the information (or data) indicating thermal noise, interference, or both. In some examples, network entity 105-a may send signaling 220 to UE 115-a indicating a configuration for reporting G2C metrics, noise data, interference data, or both noise data and interference data. UE 115-a may send the enhanced feedback message 210 indicating G2C metrics, noise data, interference data, or both noise data and interference data to network entity 105-a based on the configuration.

[0097] In some examples, in addition to reporting G2C metrics, UE 115-a can also report information based on estimated noise. For example, UE 115-a can estimate noise and report information to network entity 105-a based on the estimated noise. In some cases, UE 115-a can determine the noise covariance matrix and report the values ​​of the noise covariance matrix to network entity 105-a. For example, UE 115-a can report the eigenvalues ​​of the noise covariance matrix. The difference between the highest and lowest eigenvalues ​​of the noise covariance matrix can indicate the degree to which the interference is higher than thermal noise. In one example, UE 115-a can report all the eigenvalues ​​of the noise covariance matrix. In another example, UE 115-a can report the strongest eigenvalue, the weakest eigenvalue, or both the strongest and weakest eigenvalues ​​of the noise covariance matrix. In yet another example, UE 115-a can report selected eigenvalues ​​of the noise covariance matrix. In one example, UE 115-a may report the condition number of the noise covariance matrix. In another example, UE 115-a may report the full noise covariance matrix and the combined weights (e.g., least mean square estimate (MMSE)) used on the noise covariance matrix. Network entity 105-a may use the full noise covariance matrix and combined weights to understand the suppression achieved against interference and the true level of interference as observed at UE 115-a. Network entity 105-a may estimate the next retransmission size based on noise data. Additionally, network entity 105-a may have some understanding of the persistence of interference in future time slots, and network entity 105-a may perform additional backoff for G2C metrics that limit interference.

[0098] In some examples, UE 115-a can report G2C metrics and hypothetical G2C metrics as if no interference were present and only thermal noise existed. In some examples, network entity 105-a can send signaling 220 indicating the configuration for reporting G2C metrics, including reporting hypothetical G2C metrics. UE 115-a can determine thermal noise G2C metrics (e.g., G2C metrics where no interference is present) based on additive white Gaussian noise (AWGN) variance, noise covariance matrix, demodulation characteristics of UE 115-a, or a combination thereof. In some examples, UE 115-a can use demodulation reference signal (DMRS) symbols to compute thermal noise G2C metrics. For example, UE 115-a can evaluate the channel response of CB-related subcarriers and ODFM symbols per CB, and UE 115-a can estimate the AWGN variance. The channel response can be estimated in the same way as it would be in the presence of interference. In one example, the AWGN variance can be estimated using the noise variance estimated at the last transmission of zero-power CSI-RS. In another example, the AWGN variance can be estimated as the lowest eigenvalue of the noise covariance matrix. In yet another example, for time-selective or frequency-selective noise covariance matrices, the AWGN variance can be represented by the lowest eigenvalue among all eigenvalues ​​of all noise covariance matrices.

[0099] In some examples, the thermal noise G2C metric can be determined by UE 115-a by evaluating the channel response and the estimated noise variance relative to the UE demodulator characteristics. For linear minimum mean square error (LMMSE) equalization, UE 115-a can compute the post-equalization signal-to-noise ratio (SNR) and the corresponding MI per constellation point given the quadrature amplitude modulation (QAM) order. For maximum likelihood (ML) receivers, UE 115-a can compute the conditional channel capacity per resource element (RE) based on the QAM order. Network entity 105-a can estimate the next retransmission size (e.g., the number of additional decode bits) based on the reported hypothetical G2C metric. Additionally, network entity 105-a may have knowledge of the persistence of interference in future time slots and perform additional backoff for interference-limited G2C metrics.

[0100] In some examples, UE 115-a may report frequency-selective G2C metrics, time-selective G2C metrics, or frequency and time-selective G2C metrics. In some examples, network entity 105-a may send signaling 220 indicating a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics. The configuration may indicate frequency resources, time resources, or both frequency resources and time resources for the G2C metrics.

[0101] In some cases, network entity 105-a may ensure resources with reduced or no interference (e.g., resource blocks (RBs) in frequency and symbols in time), and network entity 105-a may instruct UE 115-a to report frequency-selective G2C metrics, time-selective G2C metrics, or both, on the indicated interference-reduced or interference-free REs, as well as G2C metrics on the remaining resources. Network entity 105-a may provide instructions to UE 115-a as part of a downlink control information (DCI) message, a MAC control element (MAC-CE) message, or an RRC message. The requested report may be periodic, aperiodic, or semi-periodic. Network entity 105-a may estimate the next retransmission size based on frequency-selective G2C metrics, time-selective G2C metrics, or both frequency- and time-selective G2C metrics.

[0102] In some examples, UE 115-a may report frequency-selective noise data, frequency-selective interference data, or both frequency-selective noise and interference data. In another example, UE 115-a may report time-selective noise data, time-selective interference data, or both time-selective noise and interference data. In yet another example, UE 115-a may report frequency and time-selective noise data, frequency and time-selective interference data, or frequency and time-selective noise and interference data. In some examples, network entity 105-a may send signaling 220 indicating a configuration for reporting G2C metrics and noise data, interference data, or both associated with G2C metrics. The configuration may indicate frequency resources, time resources, or both frequency resources and time resources for reporting noise data, interference data, or both. In another example, network entity 105-a may command UE 115-a to report noise data, interference data, or both on specified frequency resources, time resources, or both via configuration. Network entity 105-a may provide UE 115-a with a portion of a downlink control information (DCI) message, a MAC control element (MAC-CE) message, or an RRC message via configuration. The requested report may be periodic, aperiodic, or semi-periodic. In some examples, UE 115-a may send an enhanced feedback message 210 indicating noise data in a frequency-selective, time-selective, or frequency-and-time-selective manner, such as details of the noise covariance matrix discussed herein (e.g., information about one or more eigenvalues ​​of the noise covariance matrix). In some examples, UE 115-a may send an enhanced feedback message 210 indicating a hypothetical C2G metric in which observed interference is removed in a frequency-selective, time-selective, or frequency-and-time-selective manner. Network entity 105-a may estimate the next retransmission size in part based on both frequency-selective, time-selective, or frequency-and-time-selective noise data and / or interference data.

[0103] Figure 4 An example of a process flow 400 supporting techniques for reporting G2C metrics in MIRS, according to one or more aspects of this disclosure, is shown. In some examples, process flow 400 may be implemented as described in references respectively. Figure 1 and Figure 2 The described aspects of wireless communication systems 100 and 200, or those implemented therein, are used. For example, process flow 400 may be implemented by network entity 105-b and UE 115-b, which may be as described in reference to [references to other systems]. Figure 1 and Figure 2 Examples of network entity 105 and UE 115 described.

[0104] In some examples, the operations illustrated in process flow 400 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code (e.g., software executed by a processor), or any combination thereof. Alternative examples are possible, some of which may be performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or additional steps may be added.

[0105] At point 405, network entity 105-b may send signaling to UE 115-b instructing on the configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics. In one example, the configuration instructs on frequency resources, time resources, or a combination thereof for reporting G2C metrics associated with the frequency resources, time resources, or a combination thereof. In another example, the configuration instructs on the frequency resources, time resources, or a combination thereof associated with reporting noise data, interference data, or both.

[0106] At 410, network entity 105-b can send a transport block to UE 115-b.

[0107] At 415, network entity 105-b may receive from UE 115-b a feedback message indicating that reception of a portion of a transport block was unsuccessful, a G2C metric, and noise data, interference data, or both. In one example, the feedback message may include one or more values ​​of the noise covariance matrix. These values ​​may include one or more eigenvalues ​​of the noise covariance matrix. The eigenvalues ​​may include all eigenvalues ​​of the noise covariance matrix, a subset of the eigenvalues, the strongest eigenvalue, or the weakest eigenvalue. The values ​​may also include the condition number of the noise covariance matrix, one or more combined weights of the noise covariance matrix, or a combination thereof. In one example, the feedback message may include an indication of the noise covariance matrix and an indication of one or more combined weights of the noise covariance matrix.

[0108] In some examples, G2C metrics may be associated with frequency resources, time resources, or a combination thereof as indicated in the configuration. In some examples, noise data, interference data, or both may be associated with frequency resources, time resources, or a combination thereof as indicated in the configuration.

[0109] In some examples, the feedback message may indicate a second G2C metric. The second G2C metric can remove observed interference. In some examples, the UE 115-b may estimate the AWFN variance in part based on the zero-power channel state information reference signal transmission or the noise covariance matrix, and the second G2C metric may be based at least in part on one or more of the AWGN variance, the noise covariance matrix, and the UE's demodulator characteristics, or any combination thereof.

[0110] At 420, a network entity may transmit a transport block having a certain number of one or more decoded bits. The number of one or more decoded bits is based at least in part on a G2C metric and noise data, interference data, or both. In some examples, the number of one or more decoded bits may be based at least in part on a second G2C metric. The number of one or more decoded bits is based at least in part on a G2C metric and noise data, interference data, or both associated with frequency resources, time resources, or combinations thereof indicated in the configuration. In some examples, the number of one or more decoded bits may be based at least in part on a second G2C metric associated with frequency resources, time resources, or combinations thereof indicated in the configuration.

[0111] Figure 5A block diagram 500 illustrates a device 505 supporting techniques for reporting G2C metrics in MIRS, according to one or more aspects of this disclosure. Device 505 may be an example of aspects of network entity 105 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0114] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the techniques described herein for reporting G2C metrics in MIRS. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

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

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

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

[0118] 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 sending signaling to the UE indicating a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics. The communication manager 520 may be capable of, configured to, or operable to support components for sending transport blocks to the UE. The communication manager 520 may be capable of, configured to, or operable to support components for receiving from the UE a feedback message indicating unsuccessful reception of a portion of a transport block, a G2C metric, and noise data, interference data, or both. The communication manager 520 may be capable of, configured to, or operable to support components for sending transport blocks with a number of one or more decoded bits from a network entity, wherein the number of one or more decoded bits is based on G2C metrics and noise data, interference data, or both.

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

[0120] Figure 6 A block diagram 600 illustrates a device 605 supporting techniques for reporting G2C metrics in MIRS, according to one or more aspects of this disclosure. Device 605 may be an example of aspects of device 505 or network entity 105 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 can 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).

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

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

[0123] Device 605 or its various components may be examples of parts used to perform various aspects of techniques for reporting G2C metrics in MIRS as described herein. For example, communication manager 620 may include configuration manager 625, transport block manager 630, feedback manager 635, decode bit manager 640, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0124] Communication Manager 620 may support wireless communication according to examples disclosed herein. Configuration Manager 625 is capable of, configured to, or operable to support components for sending signaling to the UE indicative of a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics. Transport Block Manager 630 is capable of, configured to, or operable to support components for transmitting transport blocks to the UE. Feedback Manager 635 is capable of, configured to, or operable to support components for receiving from the UE a feedback message indicating that reception of a portion of a transport block was unsuccessful, a G2C metric, and noise data, interference data, or both. Decoding Bit Manager 640 is capable of, configured to, or operable to support components for transmitting transport blocks with a number of one or more decoding bits from a network entity, wherein the number of one or more decoding bits is based on G2C metrics and noise data, interference data, or both.

[0125] Figure 7 A block diagram 700 is shown of a communication manager 720 supporting techniques for reporting G2C metrics in MIRS, according to one or more aspects of this disclosure. The communication manager 720 may be an example of aspects of the communication manager 520, communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of techniques for reporting G2C metrics in multi-incremental redundancy schemes as described herein. For example, the communication manager 720 may include a configuration manager 725, a transport block manager 730, a feedback manager 735, a decoder bit manager 740, a noise covariance matrix manager 745, a second capacity gap manager 750, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0126] Communication Manager 720 may support wireless communication according to examples disclosed herein. Configuration Manager 725 is capable of, configured to, or operable to support components for sending signaling to the UE indicating a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics. Transport Block Manager 730 is capable of, configured to, or operable to support components for transmitting transport blocks to the UE. Feedback Manager 735 is capable of, configured to, or operable to support components for receiving from the UE a feedback message indicating that reception of a portion of a transport block was unsuccessful, a G2C metric, and noise data, interference data, or both. Decoding Bit Manager 740 is capable of, configured to, or operable to support components for transmitting transport blocks with a number of one or more decoding bits from a network entity, wherein the number of one or more decoding bits is based on G2C metrics and noise data, interference data, or both.

[0127] In some examples, the noise covariance matrix manager 745 is capable of, configured to, or able to operate to support components for receiving one or more values ​​of the noise covariance matrix from the UE.

[0128] In some examples, one or more values ​​of the noise covariance matrix include one or more eigenvalues ​​of the noise covariance matrix.

[0129] In some examples, one or more eigenvalues ​​include all the eigenvalues ​​of the noise covariance matrix, a subset of the eigenvalues ​​of the noise covariance matrix, the strongest eigenvalue of the noise covariance matrix, or the weakest eigenvalue of the noise covariance matrix.

[0130] In some examples, one or more values ​​of the noise covariance matrix include the condition number of the noise covariance matrix, one or more combined weights of the noise covariance matrix, or a combination thereof.

[0131] In some examples, the noise covariance matrix manager 745 is capable of, configured to, or able to operate to support components for receiving from the UE an indication of the noise covariance matrix and an indication of one or more combined weights of the noise covariance matrix.

[0132] In some examples, the second capacity gap manager 750 is capable of, configured to, or able to operate to support components for receiving feedback messages from the UE indicating a second G2C metric, wherein the second G2C metric removes observed interference.

[0133] In some examples, the number of one or more decoded bits is partly based on a second G2C metric.

[0134] In some examples, the configuration indicates frequency resources, time resources, or a combination thereof, and the G2C metric is associated with frequency resources, time resources, or a combination thereof.

[0135] In some examples, the configuration indicates frequency resources, time resources, or a combination thereof, and noise data, interference data, or both are associated with frequency resources, time resources, or a combination thereof.

[0136] Figure 8 A diagram of a system 800 including a device 805 supporting techniques for reporting G2C metrics in MIRS, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of device 505, device 605, or network entity 105 as described herein, or may include components thereof. Device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 805 may include components supporting output and obtaining communication, such as a communication manager 820, a transceiver 810, an antenna 815, at least one memory 825, code 830, and at least one processor 835. These components may communicate electronically or otherwise (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 840).

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

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

[0139] At least one processor 835 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 835 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 835. At least one processor 835 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 825) to cause device 805 to perform various functions (e.g., functions or tasks supporting techniques for reporting G2C metrics in multi-incremental redundancy schemes). For example, device 805 or components of device 805 may include at least one processor 835 and at least one memory 825 coupled to one or more processors in at least one processor 835, wherein at least one processor 835 and at least one memory 825 are configured to perform the various functions described herein. At least one processor 835 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 830) host functions for performing the functions of device 805. At least one processor 835 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 805 (such as within one or more memories of at least one memory 825). In some examples, at least one processor 835 may include multiple processors, and at least one memory 825 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 835 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 835) and memory circuitry (which may include at least one memory 825)) 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. Therefore, at least one processor 835 or a processing system including at least one processor 835 may be configured, configured to, or operated to cause the device 805 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 825 or otherwise.

[0140] In some examples, bus 840 may support communication at protocol layers of the protocol stack (e.g., within a protocol layer). In some examples, bus 840 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 805, or communication performed between different components of device 805 that are co-addressable or may be located in different locations (e.g., where device 805 may refer to a system in which one or more processors of communication manager 820, transceiver 810, at least one memory 825, code 830, and at least one processor 835 may be located in one of the different components or partitioned between the different components).

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

[0142] 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 sending signaling to the UE indicating a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics. The communication manager 820 may be capable of, configured to, or operable to support components for sending transport blocks to the UE. The communication manager 820 may be capable of, configured to, or operable to support components for receiving from the UE a feedback message indicating unsuccessful reception of a portion of a transport block, a G2C metric, and noise data, interference data, or both. The communication manager 820 may be capable of, configured to, or operable to support components for sending transport blocks from a network entity having a number of one or more decoded bits, wherein the number of one or more decoded bits is based on G2C metrics and noise data, interference data, or both.

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

[0144] In some examples, the communication manager 820 may be configured to use or otherwise coordinate with the transceiver 810, one or more antennas 815 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the transceiver 810, one or more processors in at least one processor 835, one or more memories in at least one memory 825, code 830, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 835, at least one memory 825, code 830, or any combination thereof). For example, code 830 may include instructions that can be executed by one or more processors in at least one processor 835 to cause the device 805 to perform various aspects of the techniques described herein for reporting G2C metrics in a multi-incremental redundancy scheme, or at least one processor 835 and at least one memory 825 may be otherwise configured to perform or support such operations individually or jointly.

[0145] Figure 9 A block diagram 900 illustrates a device 905 supporting techniques for reporting G2C metrics in MIRS, according to one or more aspects of this disclosure. Device 905 may be an example of aspects of UE 115 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0146] Receiver 910 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies used for reporting G2C metrics in multi-incremental redundancy schemes). The information may be passed to other components of device 905. Receiver 910 may utilize a single antenna or a collection of antennas.

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

[0148] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the techniques described herein for reporting G2C metrics in multi-incremental redundancy schemes. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0149] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of 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).

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

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

[0152] The communication manager 920 may support wireless communication according to examples disclosed herein. For example, the communication manager 920 may be capable of, configured to, or operable to support components for receiving signaling from a network entity indicating a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics. The communication manager 920 may be capable of, configured to, or operable to support components for receiving transport blocks from a network entity. The communication manager 920 may be capable of, configured to, or operable to support components for sending to a network entity a feedback message indicating that reception of a portion of a transport block was unsuccessful, along with G2C metrics and noise data, interference data, or both. The communication manager 920 may be capable of, configured to, or operable to support components for receiving transport blocks from a network entity having a number of one or more decoded bits, wherein the number of one or more decoded bits is based on G2C metrics and noise data, interference data, or both.

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

[0154] Figure 10 A block diagram 1000 of a device 1005 supporting techniques for reporting G2C metrics in MIRS, according to one or more aspects of this disclosure, is shown. Device 1005 may be an example of aspects of device 905 or UE 115 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005, or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020), may include at least one processor that can 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).

[0155] Receiver 1010 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies used for reporting G2C metrics in multi-incremental redundancy schemes). The information may be passed to other components of device 1005. Receiver 1010 may utilize a single antenna or a collection of antennas.

[0156] Transmitter 1015 may provide components for transmitting signals generated by other components of device 1005. For example, transmitter 1015 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques used for reporting G2C metrics in multi-incremental redundancy schemes). In some examples, transmitter 1015 may be co-located with receiver 1010 in a transceiver module. Transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0157] Device 1005 or its various components may be examples of various aspects of a technique for performing G2C metrics in a multi-incremental redundancy scheme as described herein. For example, communication manager 1020 may include configuration manager 1025, transport block manager 1030, feedback manager 1035, decode bit manager 1040, or any combination thereof. Communication manager 1020 may be examples of aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in combination with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0158] Communication Manager 1020 may support wireless communication according to examples disclosed herein. Configuration Manager 1025 is capable of, configured to, or operable to support components for receiving signaling from a network entity indicating a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics. Transport Block Manager 1030 is capable of, configured to, or operable to support components for receiving transport blocks from a network entity. Feedback Manager 1035 is capable of, configured to, or operable to support components for sending a feedback message to a network entity indicating that reception of a portion of a transport block was unsuccessful, along with G2C metrics and noise data, interference data, or both. Decoding Bit Manager 1040 is capable of, configured to, or operable to support components for receiving transport blocks from a network entity having a number of one or more decoding bits, wherein the number of one or more decoding bits is based on G2C metrics and noise data, interference data, or both.

[0159] Figure 11 A block diagram 1100 illustrates a communication manager 1120 supporting techniques for reporting G2C metrics in MIRS, according to one or more aspects of this disclosure. The communication manager 1120 may be an example of a communication manager 920, a communication manager 1020, or aspects thereof as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of techniques for reporting G2C metrics in multi-incremental redundancy schemes as described herein. For example, the communication manager 1120 may include a configuration manager 1125, a transport block manager 1130, a feedback manager 1135, a decode bit manager 1140, a noise covariance matrix manager 1145, a second capacity gap manager 1150, an AWGN variance manager 1155, 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).

[0160] Communication Manager 1120 may support wireless communication according to examples disclosed herein. Configuration Manager 1125 is capable of, configured to, or operable to support components for receiving signaling from a network entity indicating a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics. Transport Block Manager 1130 is capable of, configured to, or operable to support components for receiving transport blocks from a network entity. Feedback Manager 1135 is capable of, configured to, or operable to support components for sending a feedback message to a network entity indicating that reception of a portion of a transport block was unsuccessful, along with G2C metrics and noise data, interference data, or both. Decoding Bit Manager 1140 is capable of, configured to, or operable to support components for receiving transport blocks from a network entity having a number of one or more decoding bits, wherein the number of one or more decoding bits is based on G2C metrics and noise data, interference data, or both.

[0161] In some examples, the noise covariance matrix manager 1145 is capable of, configured to, or operable to support components for sending one or more values ​​of the noise covariance matrix to network entities.

[0162] In some examples, one or more values ​​of the noise covariance matrix include one or more eigenvalues ​​of the noise covariance matrix.

[0163] In some examples, one or more eigenvalues ​​include all the eigenvalues ​​of the noise covariance matrix, a subset of the eigenvalues ​​of the noise covariance matrix, the strongest eigenvalue of the noise covariance matrix, or the weakest eigenvalue of the noise covariance matrix.

[0164] In some examples, one or more values ​​of the noise covariance matrix include the condition number of the noise covariance matrix, one or more combined weights of the noise covariance matrix, or a combination thereof.

[0165] In some examples, the noise covariance matrix manager 1145 is capable of, configured to, or operable to support components for sending instructions to network entities regarding the noise covariance matrix and instructions regarding one or more combined weights of the noise covariance matrix.

[0166] In some examples, the second capacity gap manager 1150 is capable of, configured to, or able to operate to support components for sending feedback messages to network entities indicative of a second G2C metric, wherein the second G2C metric removes observed interference.

[0167] In some examples, the AWGN variance manager 1155 is capable of, configured to, or operable to support components for estimating the AWGN variance in part based on zero-power channel state information reference signal transmission or noise covariance matrix. In some examples, the second capacity gap manager 1150 is capable of, configured to, or operable to support components for which the second G2C is based on one or more of the AWGN variance, noise covariance matrix, UE demodulator characteristics, or any combination thereof.

[0168] In some examples, the number of one or more decoded bits is partly based on a second G2C metric.

[0169] In some examples, the configuration indicates frequency resources, time resources, or a combination thereof, and the G2C metric is associated with frequency resources, time resources, or a combination thereof.

[0170] In some examples, the configuration indicates frequency resources, time resources, or a combination thereof, and noise data, interference data, or both are associated with frequency resources, time resources, or a combination thereof.

[0171] Figure 12 A diagram of a system 1200 including a device 1205 supporting techniques for reporting G2C metrics in MIRS, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or UE 115 as described herein, or a component including such devices. Device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1205 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1220, an input / output (I / O) controller 1210, a transceiver 1215, an antenna 1225, at least one memory 1230, code 1235, and at least one processor 1240. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1245).

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

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

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

[0175] At least one processor 1240 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1240 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 1240. At least one processor 1240 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1230) to cause device 1205 to perform various functions (e.g., functions or tasks supporting techniques for reporting G2C metrics in multi-incremental redundancy schemes). For example, device 1205 or components of device 1205 may include at least one processor 1240 and at least one memory 1230 coupled to or coupled to at least one processor 1240, wherein at least one processor 1240 and at least one memory 1230 are configured to perform the various functions described herein. In some examples, at least one processor 1240 may include multiple processors, and at least one memory 1230 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1240 may be a component of a processing system, which may refer to a machine (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1240) and memory circuitry (which may include at least one memory 1230)) or system of components that receive or obtain 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. Thus, at least one processor 1240 or a processing system including at least one processor 1240 may be configured, capable of being configured, or operable to cause device 1205 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1230 or otherwise.

[0176] The communication manager 1220 may support wireless communication according to examples disclosed herein. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for receiving signaling from a network entity indicating a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics. The communication manager 1220 may be capable of, configured to, or operable to support components for receiving transport blocks from a network entity. The communication manager 1220 may be capable of, configured to, or operable to support components for sending to a network entity a feedback message indicating that reception of a portion of a transport block was unsuccessful, along with G2C metrics and noise data, interference data, or both. The communication manager 1220 may be capable of, configured to, or operable to support components for receiving transport blocks from a network entity having a number of one or more decoded bits, wherein the number of one or more decoded bits is based on G2C metrics and noise data, interference data, or both.

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

[0178] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using transceiver 1215, one or more antennas 1225, or any combination thereof, or otherwise cooperating with them. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported by or performed by at least one processor 1240, at least one memory 1230, code 1235, or any combination thereof. For example, code 1235 may include instructions that can be executed by at least one processor 1240 to cause device 1205 to perform various aspects of the techniques described herein for reporting G2C metrics in a multi-incremental redundancy scheme, or at least one processor 1240 and at least one memory 1230 may be otherwise configured to perform or support such operations individually or jointly.

[0179] Figure 13 A flowchart illustrating a method 1300 for reporting G2C metrics in MIRS, exemplifying various aspects of this disclosure, is shown. The operation of method 1300 can be implemented by a network entity or its components as described herein. For example, the operation of method 1300 can be implemented by, as referenced... Figures 1 to 8 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0180] At 1305, the method may include sending signaling to the UE instructing on a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics. Operation of block 1305 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1305 may be provided by reference to [reference needed]. Figure 7 The configuration manager 725 described is used to execute this.

[0181] At 1310, the method may include sending a transport block to the UE. The operation of block 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be derived from references... Figure 7 The described transport block manager 730 is used for execution.

[0182] At 1315, the method may include receiving from the UE a feedback message indicating that reception of a portion of the transport block was unsuccessful, a G2C metric, and noise data, interference data, or both. Operation of block 1315 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1315 may be derived from references... Figure 7 The feedback manager 735 described is used to execute this.

[0183] At 1320, the method may include sending a transport block from a network entity having a number of one or more decoded bits, wherein the number of one or more decoded bits is based on a G2C metric and noise data, interference data, or both. The operation of block 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1320 may be provided by reference to [reference needed]. Figure 7 The described decoder bit manager 740 is used to perform this.

[0184] Figure 14 A flowchart illustrating a method 1400 for reporting G2C metrics in MIRS, according to various aspects of this disclosure, is shown. Operation of method 1400 may be implemented by a UE or its components as described herein. For example, operation of method 1400 may be performed by, as referenced... Figures 1 to 4 and Figures 9 to 12 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.

[0185] At 1405, the method may include receiving signaling from a network entity indicative of a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics. Operation of box 1405 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1405 may be provided by reference to [reference needed]. Figure 11 The configuration manager 1125 described is used to execute this.

[0186] At 1410, the method may include receiving a transport block from a network entity. The operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be derived from references... Figure 11 The described transport block manager 1130 is used for execution.

[0187] At 1415, the method may include sending a feedback message to the network entity indicating that reception of a portion of a transport block was unsuccessful, a G2C metric, and noise data, interference data, or both. The operation of box 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1415 may be provided by reference to [reference needed]. Figure 11 The feedback manager 1135 described is used to execute this.

[0188] At 1420, the method may include receiving a transport block having a number of one or more decoded bits from a network entity, wherein the number of one or more decoded bits is based on a G2C metric and noise data, interference data, or both. The operation of block 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1420 may be provided by reference to [reference needed]. Figure 11 The described decoder bit manager 1140 is used to perform this.

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

[0190] Aspect 1: A method for wireless communication by a network entity, the method comprising: sending to a UE signaling for a configuration of reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics; sending a transport block to the UE; receiving from the UE a feedback message indicating that reception of a portion of the transport block was unsuccessful, the G2C metrics, and the noise data, the interference data, or both; and sending from the network entity the transport block having a number of one or more decoded bits, wherein the number of one or more decoded bits is at least partially based on the G2C metrics and the noise data, the interference data, or both.

[0191] Aspect 2: According to the method of aspect 1, receiving the feedback message further includes: receiving one or more values ​​of the noise covariance matrix from the UE.

[0192] Aspect 3: According to the method of aspect 2, wherein the one or more values ​​of the noise covariance matrix include one or more eigenvalues ​​of the noise covariance matrix.

[0193] Aspect 4: According to the method of aspect 3, wherein the one or more eigenvalues ​​include all of the eigenvalues ​​of the noise covariance matrix, a subset of the eigenvalues ​​of the noise covariance matrix, the strongest eigenvalue of the noise covariance matrix, or the weakest eigenvalue of the noise covariance matrix.

[0194] Aspect 5: According to the method of aspect 2, wherein the one or more values ​​of the noise covariance matrix include the condition number of the noise covariance matrix, one or more combined weights of the noise covariance matrix, or a combination thereof.

[0195] Aspect 6: The method according to any one of Aspects 1 to 5, wherein receiving the feedback message further includes: receiving from the UE an indication of the noise covariance matrix and an indication of one or more combined weights of the noise covariance matrix.

[0196] Aspect 7: The method according to any one of Aspects 1 to 6, wherein receiving the feedback message further includes: receiving from the UE the feedback message indicating a second G2C metric, wherein the second G2C metric removes the observed interference.

[0197] Aspect 8: According to the method of aspect 7, the number of said one or more decoded bits is partially based on the second G2C metric.

[0198] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the configuration indicates frequency resources, time resources, or a combination thereof, and the G2C metric is associated with the frequency resources, the time resources, or the combination thereof.

[0199] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the configuration indicates frequency resources, time resources or combinations thereof, and the noise data, the interference data or both are associated with the frequency resources, the time resources or combinations thereof.

[0200] Aspect 11: A method for wireless communication by a UE, the method comprising: receiving from a network entity signaling an indication of a configuration for reporting G2C metrics and noise data, interference data, or both associated with the G2C metrics; receiving a transport block from the network entity; sending to the network entity a feedback message indicating that reception of a portion of the transport block was unsuccessful, the G2C metrics, and the noise data, the interference data, or both; and receiving from the network entity the transport block having a number of one or more decoded bits, wherein the number of one or more decoded bits is at least partially based on the G2C metrics and the noise data, the interference data, or both.

[0201] Aspect 12: According to the method of aspect 11, sending the feedback message further includes sending one or more values ​​of the noise covariance matrix to the network entity.

[0202] Aspect 13: According to the method of aspect 12, wherein the one or more values ​​of the noise covariance matrix include one or more eigenvalues ​​of the noise covariance matrix.

[0203] Aspect 14: According to the method of aspect 13, wherein the one or more eigenvalues ​​include all of the eigenvalues ​​of the noise covariance matrix, a subset of the eigenvalues ​​of the noise covariance matrix, the strongest eigenvalue of the noise covariance matrix, or the weakest eigenvalue of the noise covariance matrix.

[0204] Aspect 15: The method according to any one of Aspects 13 to 14, wherein the one or more values ​​of the noise covariance matrix include the condition number of the noise covariance matrix, one or more combined weights of the noise covariance matrix, or a combination thereof.

[0205] Aspect 16: According to the method of aspect 11, receiving the feedback message further includes sending to the network entity an indication of the noise covariance matrix and an indication of one or more combined weights of the noise covariance matrix.

[0206] Aspect 17: The method according to any one of Aspects 11 to 16, wherein sending the feedback message further comprises: sending the feedback message to the network entity indicating a second G2C metric, wherein the second G2C metric removes the observed interference.

[0207] Aspect 18: The method according to aspect 17 further includes: estimating the variance of additive white Gaussian noise (AWGN) in part based on the zero-power channel state information reference signal transmission or noise covariance matrix; and wherein the second G2C is at least in part based on one or more of the AWGN variance, the noise covariance matrix, the demodulator characteristics of the UE, or any combination thereof.

[0208] Aspect 19: The method according to any one of aspects 17 to 18, wherein the number of said one or more decoded bits is partially based on the second G2C metric.

[0209] Aspect 20: The method according to any one of Aspects 11 to 19, wherein the configuration indicates frequency resources, time resources, or a combination thereof, and the G2C metric is associated with the frequency resources, the time resources, or the combination thereof.

[0210] Aspect 21: The method according to any one of Aspects 11 to 20, wherein the configuration indicates frequency resources, time resources or combinations thereof, and the noise data, the interference data or both are associated with the frequency resources, the time resources or combinations thereof.

[0211] Aspect 22: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of Aspects 1 to 10.

[0212] Aspect 23: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 1 to 10.

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

[0214] Aspect 25: 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 to cause the UE to perform a method according to any one of aspects 11 to 21.

[0215] Aspect 26: A UE for wireless communication, the UE comprising at least one component for performing a method according to any one of aspects 11 to 21.

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

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

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

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

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

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

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

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

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

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

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

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

[0228] 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 network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: Send signaling to the user equipment (UE) instructing the user to report capacity gap metrics and the configuration of noise data, interference data, or both associated with the capacity gap metrics; Send a transport block to the UE; The UE receives a feedback message indicating that reception of a portion of the transport block was unsuccessful, the capacity gap metric, and the noise data, the interference data, or both. as well as The network entity sends the transport block having a certain number of one or more decoded bits, wherein the number of one or more decoded bits is at least partially based on the capacity gap metric and the noise data, the interference data, or both.

2. The network entity of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: The UE receives one or more values ​​of the noise covariance matrix.

3. The network entity of claim 2, wherein the one or more values ​​of the noise covariance matrix include one or more eigenvalues ​​of the noise covariance matrix.

4. The network entity according to claim 3, wherein the one or more eigenvalues ​​include all of the eigenvalues ​​of the noise covariance matrix, a subset of the eigenvalues ​​of the noise covariance matrix, the strongest eigenvalue of the noise covariance matrix, or the weakest eigenvalue of the noise covariance matrix.

5. The network entity of claim 2, wherein the one or more values ​​of the noise covariance matrix include the condition number of the noise covariance matrix, one or more combined weights of the noise covariance matrix, or a combination thereof.

6. The network entity of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: The UE receives an indication of the noise covariance matrix and an indication of one or more combined weights of the noise covariance matrix.

7. The network entity of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: The UE receives a feedback message indicating a second capacity gap metric, wherein the second capacity gap metric removes observed interference.

8. The network entity of claim 7, wherein the number of said one or more decoded bits is in part based on the second capacity gap metric.

9. The network entity of claim 1, wherein the configuration indicates frequency resources, time resources, or a combination thereof, and the capacity gap metric is associated with the frequency resources, the time resources, or the combination thereof.

10. The network entity of claim 1, wherein the configuration indicates frequency resources, time resources, or a combination thereof, and the noise data, the interference data, or both are associated with the frequency resources, the time resources, or the combination thereof.

11. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Receive signaling from network entities instructing the configuration of reporting capacity gap metrics and associated noise data, interference data, or both; Receive transport blocks from the network entity; Send a feedback message to the network entity indicating that reception of a portion of the transport block was unsuccessful, the capacity gap metric, and the noise data, the interference data, or both; as well as The network entity receives the transport block having a certain number of one or more decoded bits, wherein the number of one or more decoded bits is at least partially based on the capacity gap metric and the noise data, the interference data, or both.

12. The UE of claim 11, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Send one or more values ​​of the noise covariance matrix to the network entity.

13. The UE of claim 12, wherein the one or more values ​​of the noise covariance matrix include one or more eigenvalues ​​of the noise covariance matrix.

14. The UE of claim 13, wherein the one or more eigenvalues ​​include all of the eigenvalues ​​of the noise covariance matrix, a subset of the eigenvalues ​​of the noise covariance matrix, the strongest eigenvalue of the noise covariance matrix, or the weakest eigenvalue of the noise covariance matrix.

15. The UE of claim 13, wherein the one or more values ​​of the noise covariance matrix include the condition number of the noise covariance matrix, one or more combined weights of the noise covariance matrix, or a combination thereof.

16. The UE of claim 11, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Send to the network entity an indication of the noise covariance matrix and an indication of one or more combined weights of the noise covariance matrix.

17. The UE of claim 11, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The feedback message indicating a second capacity gap metric is sent to the network entity, wherein the second capacity gap metric removes the observed interference.

18. The UE of claim 17, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The additive white Gaussian noise variance is estimated in part based on the zero-power channel state information reference signal transmission or noise covariance matrix; wherein the second capacity gap is at least partially based on one or more of the additive white Gaussian noise variance, the noise covariance matrix, the demodulator characteristics of the UE, or any combination thereof.

19. The UE of claim 17, wherein the number of said one or more decoded bits is in part based on the second capacity gap metric.

20. The UE of claim 11, wherein the configuration indicates frequency resources, time resources, or a combination thereof, and the capacity gap metric is associated with the frequency resources, the time resources, or the combination thereof.

21. The UE of claim 11, wherein the configuration indicates frequency resources, time resources, or a combination thereof, and the noise data, the interference data, or both are associated with the frequency resources, the time resources, or the combination thereof.

22. A method for wireless communication by a network entity, the method comprising: Send signaling to the user equipment (UE) instructing the user to report capacity gap metrics and the configuration of noise data, interference data, or both associated with the capacity gap metrics; Send a transport block to the UE; The UE receives a feedback message indicating that reception of a portion of the transport block was unsuccessful, the capacity gap metric, and the noise data, the interference data, or both. as well as The network entity sends the transport block having a certain number of one or more decoded bits, wherein the number of one or more decoded bits is at least partially based on the capacity gap metric and the noise data, the interference data, or both.

23. The method of claim 22, wherein receiving the feedback message further comprises: The UE receives one or more values ​​of the noise covariance matrix.

24. The method of claim 22, wherein receiving the feedback message further comprises: The UE receives a feedback message indicating a second capacity gap metric, wherein the second capacity gap metric removes observed interference.

25. The method of claim 22, wherein the configuration indicates frequency resources, time resources, or a combination thereof, and the capacity gap metric is associated with the frequency resources, the time resources, or the combination thereof.

26. The method of claim 22, wherein the configuration indicates frequency resources, time resources, or a combination thereof, and the noise data, the interference data, or both are associated with the frequency resources, the time resources, or the combination thereof.

27. A method for wireless communication by a user equipment (UE), the method comprising: Receive signaling from network entities instructing the configuration of reporting capacity gap metrics and associated noise data, interference data, or both; Receive transport blocks from the network entity; Send a feedback message to the network entity indicating that reception of a portion of the transport block was unsuccessful, the capacity gap metric, and the noise data, the interference data, or both; as well as The network entity receives the transport block having a certain number of one or more decoded bits, wherein the number of one or more decoded bits is at least partially based on the capacity gap metric and the noise data, the interference data, or both.

28. The method of claim 27, wherein sending the feedback message further comprises: Send one or more values ​​of the noise covariance matrix to the network entity.

29. The method of claim 27, wherein sending the feedback message further comprises: The feedback message indicating a second capacity gap metric is sent to the network entity, wherein the second capacity gap metric removes the observed interference.

30. The method of claim 27, wherein the configuration indicates frequency resources, time resources, or a combination thereof, the capacity gap metric is associated with the frequency resources, the time resources, or the combination thereof, and the noise data, the interference data, or both are associated with the frequency resources, the time resources, or the combination thereof.

Images