Techniques for reporting a gap to capacity metric in a multiple incremental redundancy scheme

Abstract

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

Description

TECHNIQUES FOR REPORTING A GAP TO CAPACITY METRIC IN A MULTIPLE INCREMENTAL REDUNDANCY SCHEMECROSS REFERENCE

[0001] The present Application for Patent claims the benefit of Israel Patent Application No. 308189 by UZIEL et al., entitled ‘TECHNIQUES FOR REPORTING A GAP TO CAPACITY METRIC IN A MULTIPLE INCREMENTAL REDUNDANCY SCHEME.” filed November 01. 2023, assigned to the assignee hereof, and expressly incorporated by reference herein.FIELD OF TECHNOLOGY

[0002] The following relates to wireless communications, including techniques for reporting a gap to capacity metric in a multiple incremental redundancy scheme.BACKGROUND

[0003] Wireless communications systems are widely deployed to provide various ty pes of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transfomi spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE).SUMMARY

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support techniques for reporting a gap to capacity (G2C) metric in amultiple incremental redundancy scheme. For example, the described techniques provide for a receiver to transmit, to a transmitter, information indicative of thermal noise or interference associated with the G2C metric. The transmitter may transmit (and retransmit), to the receiver, a quantity of coded bits based on the G2C metric and the noise or the interference associated with the G2C metric. In some examples, the transmitter may transmit to the receiver signaling indicating a configuration for reporting the G2C metric, the noise data, the interference data or both, associated with the gap to capacity metric. To report information indicative of the thermal noise, the receiver may transmit values of a noise covariance matrix. In addition to the G2C metric, the receiver may report the G2C metric and a hypothetical G2C with only thermal noise present and no interference present.

[0005] A method for wireless communication by a network entity is described. The method may include transmitting, to a user equipment (UE), signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric, transmitting, to the UE, a transport block, receiving, from the UE, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both, and transmitting, from the network entity’, the transport block with a quantity of one or more coded bits, where the quantity of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0006] 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 with the one or more memories. The one or more processors may individually or collectively operable to execute the code to cause the network entity7to transmit, to a UE, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric, transmit, to the UE, a transport block, receive, from the UE. a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both, and transmit, from the network entity7, the transport block with a quantity7of one or more coded bits, where the quantity7of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0007] Another network entity for wireless communication is described. The network entity may include means for transmitting, to a UE, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric, means for transmitting, to the UE, a transport block, means for receiving, from the UE, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both, and means for transmitting, from the network entity, the transport block with a quantity of one or more coded bits, where the quantity of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to transmit, to a UE, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric, transmit, to the UE, a transport block, receive, from the UE, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both, and transmit, from the network entity, the transport block with a quantity of one or more coded bits, where the quantity of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0009] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from the UE. one or more values of a noise covariance matrix.

[0010] In some examples of the method, netw ork entities, and non-transitory computer-readable medium described herein, the one or more values of the noise covariance matrix include one or more eigenvalues of the noise covariance matrix.

[0011] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the one or more eigenvalues include all of the eigenvalues of the noise covariance matrix, a subset of the eigenvalues of the noisecovariance matrix, a strongest eigenvalue of the noise covariance matrix, or a weakest eigenvalue of the noise covariance matrix.

[0012] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the one or more values of the noise covariance matrix include a condition number of the noise covariance matrix, one or more combining weights of the noise covariance matrix, or a combination thereof.

[0013] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from the UE, an indication of a noise covariance matrix and an indication of one or more combining weights of the noise covariance matrix.

[0014] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from the UE, the feedback message indicating a second G2C metric, where the second G2C metric removes observed interference.

[0015] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the quantity of the one or more coded bits may be based in part on the second G2C metric.

[0016] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the configuration indicates a frequency resource, a time resource or a combination thereof, and the G2C metric may be associated with the frequency resource, the time resource or the combination thereof.

[0017] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the configuration indicates a frequencyresource, a time resource or a combination thereof, and the noise data, the interference data or both may be associated with the frequency resource, the time resource or the combination thereof.

[0018] A method for wireless communication by a UE is described. The method may include receiving, from a network entity, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with theG2C metric, receiving, from the network entity, a transport block, transmitting, to the network entity, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both, and receiving, from the network entity, the transport block with a quantity of one or more coded bits, where the quantity of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0019] 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 with the one or more memories. The one or more processors may individually or collectively operable to execute the code to cause the UE to receive, from a network entity7, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric, receive, from the network entity, a transport block, transmit, to the network entity, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both, and receive, from the network entity, the transport block with a quantity of one or more coded bits, where the quantity of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0020] Another UE for wireless communication is described. The UE may include means for receiving, from a network entity, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric, means for receiving, from the network entity, a transport block, means for transmitting, to the network entity, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both, and means for receiving, from the network entity, the transport block with a quantity of one or more coded bits, where the quantity of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0021] 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 indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric, receive, from the network entity, a transport block, transmit, to the networkentity, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both, and receive, from the network entity, the transport block with a quantity of one or more coded bits, where the quantity of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0022] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the network entity, one or more values of a noise covariance matrix.

[0023] In some examples of the method, user equipment (UEs). and non-transitory computer-readable medium described herein, the one or more values of the noise covariance matrix include one or more eigenvalues of the noise covariance matrix.

[0024] In some examples of the method, user equipment (UEs), and non-transitory7computer-readable medium described herein, 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, a strongest eigenvalue of the noise covariance matrix, or a weakest eigenvalue of the noise covariance matrix.

[0025] In some examples of the method, user equipment (UEs), and non-transitory7computer-readable medium described herein, the one or more values of the noise covariance matrix include a condition number of the noise covariance matrix, one or more combining weights of the noise covariance matrix, or a combination thereof.

[0026] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the network entity, an indication of a noise covariance matrix and an indication of one or more combining weights of the noise covariance matrix.

[0027] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the netw ork entity, the feedback messageindicating a second G2C metric, where the second G2C metric removes observed interference.

[0028] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for estimating an additive white gaussian noise (AWGN) variance based in part on a zero-power-channel-state-information-reference-signal transmission or a noise covariance matrix and where the second G2C may be based on one or more of the AWGN variance, the noise covariance matrix, a demodulator characteristic of the UE, or any combination thereof.

[0029] In some examples of the method, user equipment (UEs). and non-transitory computer-readable medium described herein, the quantity of the one or more coded bits may be based in part on the second G2C metric.

[0030] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the configuration indicates a frequency resource, a time resource or a combination thereof, and the G2C metric may be associated with the frequency resource, the time resource or the combination thereof.

[0031] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the configuration indicates a frequency resource, a time resource or a combination thereof, and the noise data, the interference data or both may be associated with the frequency resource, the time resource or the combination thereof.

[0032] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages will be better understood from the following description when considered in connection withthe accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.

[0033] While aspects and embodiments are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, packaging arrangements. For example, embodiments and / or uses may come about via integrated chip embodiments and other non-module-component based devices (e.g.. end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (Al)-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range in spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, radio frequency (RF)-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders / summers, etc.). It is intended that innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes, and constitution.BRIEF DESCRIPTION OF THE DRAWINGS

[0034] FIG. 1 shows an example of a wireless communications system that supports techniques for reporting a gap to capacity (G2C) metric in a multiple incremental redundancy scheme in accordance with one or more aspects of the present disclosure.

[0035] FIG. 2 shows an example of a wireless communications system that supports techniques for reporting a G2C metric in a multiple incremental redundancy scheme in accordance with one or more aspects of the present disclosure.

[0036] FIG. 3 shows an example of a transmission diagram that supports techniques for reporting a G2C metric in a multiple incremental redundancy scheme in accordance with one or more aspects of the present disclosure.

[0037] FIG. 4 shows an example of a process flow that supports techniques for reporting a G2C metric in a multiple incremental redundancy scheme in accordance with one or more aspects of the present disclosure.

[0038] FIGs. 5 and 6 show block diagrams of devices that support techniques for reporting a G2C metric in a multiple incremental redundancy scheme in accordance with one or more aspects of the present disclosure.

[0039] FIG. 7 shows a block diagram of a communications manager that supports techniques for reporting a G2C metric in a multiple incremental redundancy scheme in accordance with one or more aspects of the present disclosure.

[0040] FIG. 8 shows a diagram of a system including a device that supports techniques for reporting a G2C metric in a multiple incremental redundancy scheme in accordance with one or more aspects of the present disclosure.

[0041] FIGs. 9 and 10 show block diagrams of devices that support techniques for reporting a G2C metric in a multiple incremental redundancy scheme in accordance with one or more aspects of the present disclosure.

[0042] FIG. 11 shows a block diagram of a communications manager that supports techniques for reporting a G2C metric in a multiple incremental redundancy scheme in accordance with one or more aspects of the present disclosure.

[0043] FIG. 12 shows a diagram of a system including a device that supports techniques for reporting a G2C metric in a multiple incremental redundancy scheme in accordance with one or more aspects of the present disclosure.

[0044] FIGs. 13 through 14 show flowcharts illustrating methods that support techniques for reporting a G2C metric in a multiple incremental redundancy scheme in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION

[0045] In some wireless communications systems, wireless devices may operate in accordance with a multiple incremental redundancy scheme (MIRS). MIRS may be used to determine a modulation coding scheme (MCS) for communication between a network entity and a user equipment (UE) at or near a channel capacity. For example, the network entity may transmit a transport block to the UE. The UE may transmit feedback indicating reception of a portion of the transport block was unsuccessful (which is hybrid automatic repeat request (HARQ) feedback) and may transmit feedback indicating a quantity of parity bits or a fraction of the transport block for successful reception of the transport block. The network entity may utilize multiple small sized re-transmissions (e.g., an incremental retransmission hybrid automatic repeat request (IR-HARQ)) for fine, dynamic adaptation of the coding rate, based on feedback from a receiving wireless device (e.g., acknowledgment (ACK) or non- ACK (NACK) messages). When the UE sends feedback (NACK), the network entity may adjust the next transmission of the transport block by including a quantity of additional coded bits. However, the multiple re-transmissions increase overall latency and a hybrid automatic repeat request (HARQ) buffer size.

[0046] To mitigate the quantity of re-transmissions in MIRS, the UE may report a gap to capacity (G2C) metric to the network entity. The G2C metric may indicate a size of the next-retransmission based on calculated mutual information per information bit. The network entity may evaluate the next transmission size based on the G2C metric and may retransmit the transport block including a quantity of additional coded bits based on the G2C metric. That is, the next transmission may include the transport block in a code rate, reflected in a quantity of coded bits, based on the G2C metric. In some examples, the G2C metric may be limited by thermal noise or by interference, and the determination of the next-retransmission size may be adversely impacted by thermal noise or by interference.

[0047] The techniques described herein provide procedures for reporting the G2C metric in MIRS. The techniques reduce the quantity of re-transmissions in MIRS. The UE may report information indicative of the thermal noise and the interference in the feedback, and the network entity may determine the next transmission sized based on the G2C metric and the information indicative of the thermal noise and the interference.

[0048] In some examples, the network entity may transmit, to the UE, signaling indicating a configuration for reporting the G2C metric and the information indicative of the noise, the interference, or both. Additionally, network entity' may transmit, to the UE, signaling requesting a frequency selective, time selective or combination frequency and time selective G2C metric. The network entity may transmit, to the UE, a transport block. The UE may transmit, to the network entity’, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric, the noise data associated with the G2C metric, the interference data associated with the G2C metric, or both the noise data and the interference data associated with the G2C metric. In some examples, the feedback message may include HARQ related feedback (e.g., a regular HARQ feedback) indicating that the transport block was not received successfully for transport block based MIRS or indicating that part of the code blocks were not received successfully for code block group based MIRS. To report information indicative of the noise, the UE may transmit values of a noise covariance matrix in the feedback. For example, the UE may transmit eigen values of the noise covariance matrix. In another example, the UE may transmit a condition number of the noise covariance matrix or combining weights of the noise covariance matrix. The network entity may transmit, to the UE, the transport block and a quantity of additional coded bits based on the G2C metric and based on the noise data, the interference data or both the noise data and the interference data. In some examples, in addition to the G2C metric, the UE may report a hypothetical G2C with only noise present and no interference present, and the network entity may transmit the transport block and the quantity of additional coded bits based on the hypothetical G2C metric.

[0049] Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are also described in context of a transmission diagram and a process flow. Aspects of the disclosure are furtherillustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to techniques for reporting a G2C metric in MIRS.

[0050] FIG. 1 shows an example of a wireless communications system 100 that supports techniques for reporting a G2C metric in a multiple incremental redundancy scheme in accordance with one or more aspects of the present disclosure. The wireless communications 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 communications system 100 may be a Long Term Evolution (LTE) network, an LTE- Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

[0053] As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a networkentity 105 (e.g., any network entity described herein), a UE 1 15 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity7105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity7105 also discloses that a first node is configured to receive information from a second node.

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

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

[0056] In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities 105, such as an integrated access backhaul (I AB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a netw ork entity 105 may include one or more of 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 (Near-RT RIC), aNon-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU). or a transmission reception point (TRP). One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g.. a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0057] The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof) are performed at a CU 160, a DU 165. or an RU 170. Forexample, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g.. Radio Resource Control (RRC), service data adaption protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (LI) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or more RUs 170). In some cases, a functional split between a CU 160 and a DU 165, or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170. while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170). A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to one or more DUs 165 via a midhaul communication link 162 (e.g., Fl, Fl-c. Fl-u), and a DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that are in communication via such communication links.

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

[0059] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support techniques for reporting a G2C metric in a multiple incremental redundancy scheme as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 180).

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

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

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

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

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

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

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

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

[0068] In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area 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, the overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 providecoverage for various coverage areas 1 10 using the same or different radio access technologies.

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

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

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

[0072] The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

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

[0074] A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A netw ork entity' 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 1 15. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

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

[0076] The UEs 1 15 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. HARQ feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., a communication link 125, a D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in poor radio conditions (e g., low signal-to-noise conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.

[0077] In some wireless communications systems, wireless devices may operate in accordance with MIRS. MIRS may be used to determine a MCS for communication between the network entity 105 and the UE 115 at or near a channel capacity. For example, the network entity 105 may transmit a transport block to the UE 115. The UE 115 may transmit feedback indicating reception of a portion of the transport block was unsuccessful (which is hybrid automatic repeat request (HARQ) feedback) and may transmit feedback indicating a quantity of parity bits or a fraction of the transport block for successful reception of the transport block. The network entity 105 may utilize multiple small sized re-transmissions (e.g., IR-HARQ) for fine, dynamic adaptation of the coding rate, based on feedback from a receiving wireless device (e.g.. ACK or NACK messages). When the UE 1 15 sends feedback (NACK), the network entity 105 may adjust the next transmission of the transport block by including a quantity of additional coded bits. However, the multiple re-transmissions increase overall latency and a HARQ buffer size.

[0078] To mitigate the quantity of re-transmissions in MIRS, the UE 115 may report a G2C metric to the network entity 105. The G2C metric may indicate a size of the nextretransmission based on calculated mutual information per information bit. The network entity 105 may evaluate the next transmission size based on the G2C metric and may retransmit the transport block including a quantity of additional coded bits based on the G2C metric. That is, the next transmission may include the transport block in a coderate, reflected in a quantity of coded bits, based on the G2C metric. In some examples, the G2C metric may be limited by thermal noise or by interference, and the determination of the next-retransmission size may be adversely impacted by thermal noise or by interference.

[0079] The techniques described herein provide procedures for reporting the G2C metric in MIRS. The techniques reduce the quantity of re-transmissions in MIRS. The UE 115 may report information indicative of the thermal noise and the interference in the feedback, and the network entity 105 may determine the next transmission sized based on the G2C metric and the information indicative of the thermal noise and the interference.

[0080] In some examples, the network entity 105 may transmit, to the UE 1 15, signaling indicating a configuration for reporting the G2C metric and the information indicative of the noise, the interference, or both. Additionally, network entity 105 may transmit, to the UE 115, signaling indicating the configuration that request a frequency selective, time selective or combination frequency and time selective G2C metric. The network entity 105 may transmit, to the UE 115, a transport block. The UE 115 may transmit, to the network entity7105 and in accordance with the configuration, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric, the noise data associated with the G2C metric, the interference data associated with the G2C metric, or both the noise data and the interference data associated with the G2C metric. In some examples, the feedback message may include HARQ related feedback (e.g., a regular HARQ feedback) indicating that the transport block was not received successfully for transport block based MIRS or indicating that part of the code blocks were not received successfully for code block group based MIRS. To report information indicative of the noise, the UE 115 may transmit or otherwise indicate values of a noise covariance matrix in the feedback in accordance with the configuration (e.g., the configuration indicates for the UE 115 to provide feedback indicating one or more eigenvalues). For example, the UE 1 15 may transmit one or more eigen values of the noise covariance matrix. In another example, the UE 115 may transmit a condition number of the noise covariance matrix or combining weights of the noise covariance matrix. The network entity 105 may transmit, to the UE 115, the transport block and a quantity of additional coded bits based on the G2C metricand based on the noise data, the interference data or both the noise data and the interference data. In some examples, in addition to the G2C metric, the UE 115 may report a hypothetical G2C with only noise present and no interference present, and the network entity 105 may transmit the transport block and the quantity of additional coded bits based on the hypothetical G2C metric.

[0081] FIG. 2 shows an example of a wireless communications system 200 that supports techniques for reporting the G2C metric in MIRS in accordance with one or more aspects of the present disclosure. In some examples, the wireless communications system 200 may implement aspects of the wireless communications system 100. For example, the wireless communications system 200 may include a network entity 105-a and a UE 115-a, which may be examples of a network entity 105 and a UE 115 respectively, as described herein with reference to FIG. 1.

[0082] The network entity 105-a and the UE 115-a may be in wireless communication and may implement a rate adaptation scheme for a NR based system. In some examples, the rate adaptation scheme of MIRS may improve the gap between a defined (e.g., optimal) link adaptation as compared to a channel state information reference signal (CSI-RS) based link adaptation. The CSI-RS based channel capacity tracking scheme may not adapt to the instantaneous optimal MCS as the CSI-RS based link adaptation does not utilize the full available channel capacity. The instantaneous optimal MCS may be the highest MCS that may be successfully decoded by the UE 115-a on a specific TTI. One reason for CSI-RS based link adaptation not achieving instantaneous optimal MCS is the CSI-RS estimation may not model the receiver’s performance accurately. Additionally, since the channel state is sampled at discrete times (e.g., CSI-RS slots) and the channel is varying, the optimal MCS and coding rate may significantly vary between the sampled slots. The channel may vary when the UE 115-a is stationary, and the channel may vary7due to movement of the UE 115-a with the channel varying more at high velocities. The optimal MCS between CSI slots is not achievable by the CSI-RS based link adaptation scheme as the optimal MCS between CSI slots may vary7due to the velocity of the UE 115-a.

[0083] In the CSI-RS based link adaptation scheme, the implemented MCS, and specifically the coding rate, is set on a first transmission and may not be dynamically adapted. If the first transmission fails, approximately a same quantity of coded bits isretransmitted. In the regular HARQ IR retransmission, the MCS is kept the same, meaning the same size of bits per allocation are retransmitted, and the same size of bits per allocation are added to the previous transmissions reducing the rate. The retransmission scheme provides a small set of redundancy versions used to select the bits for retransmission. These bits are either the same coded bits as the first transmission (e.g., Chase combining) which provides same code rate or new coded bits (e.g., incremental redundancy) which halves the effective coding rate in the second retransmission. Thus, the selection of the coding rate on first transmission may greatly affects the results. Overestimated the coding rate may result in decoding errors and may lead to throughput loss. Underestimated coding rates may result in a loss of throughput as larger payload may have been transmitted over the same channel resource. An outer loop link adaptation (OLLA) between CSI-RS slots may be implemented, but the OLLA may not track the optimal MCS changes accurately. Even with optimal CSI estimation with the MCS optimally selected on CSI slots with or without implementing OLLA, the throughput performance may be less than an achievable performance of per slot MCS selection.

[0084] MIRS may improve the gap to optimal MCS selection, and MIRS may achieve communication at a capacity’ code rate regardless of mobility and velocity of the UE 1 15 -a. Referring to FIG. 2, the network entity 105-a and the UE 115 -a may be in wireless communication and operate in accordance with MIRS. For example, the network entity 105-a may use MIRS to determine an efficient MCS and achieve communication with the UE 115-a at or near a capacity code rate. For example, the network entity 105-a may select an overestimated MCS to ensure throughput is not lost due to an underestimated rate. The network entity 105-a may rely on extensive usage of small sized re-transmission (e.g., IR-HARQ) for fine, dynamic adaptation of the coding rate, based on the UE 115-a feedback (e.g., NACK) for the transmission. That is, each time the UE 115-a transmits, to the network entity 105-a, a NACK (or alternatively, does not send an ACK), the network entity' 105-a may add a small quantity of additional redundancy bits to the transmission. In some examples, the network entity' 105-a may use per code block (CB) feedback to further improve channel utilization.

[0085] In some examples, to implement MIRS, the transmitter, such as the network entity 105-a (e.g., gNobeB), may select an MCS on the first transmission that isexpected to fail or overestimate the MCS. For example, the network entity 105-a may transmit an initial transmission 205 to the UE 115-a. The selection of the first transmission MCS may determine the coding parameters (e.g., rate and transport block size) for all of the following retransmissions. For each decoding failure, the receiver, such as the UE 1 15-a, may transmit an enhanced feedback message 210 with per CB or transport block decoding results. In some examples, the receiver, such as the UE 115-a, may convey additional information to enable the transmitter (e.g., network entity 105-a) a faster convergence to the actual acceptable rate. For each failure indicated by the enhanced feedback message 210 from the receiver (UE 115-a), the transmitter (e.g., network entity 105-a) may schedule a retransmission at the required rate such that the combined rate after HARQ IR combination will provide the same rate that is feedbacked by the UE corresponding to the instantaneous conditions at the time of reception. The feedback may specifically indicate the buffer of coded bits from the initial coded bits buffer of the transport block or may specifically indicate the buffer of coded bits from the initial coded bits buffer of the failing CBs required to provide the required instantaneous rate. In some examples, MIRS may be CB based with the feedback G2C metric per CB, and MIRS may be transport block based with smaller feedback G2C metric per transport block. For the CB base MIRS, the transmitter (e.g., network entity 105-a) may transmit the retransmission (e.g., subsequent modified transmission 215) with the additional bits to reduce the effective rate of each code block. The added bits in each retransmission (e.g.. each subsequent modified transmission 215) reduce the effective rate of each CB in fine steps until all CBs are decoded successfully by the UE 115-a and consequently the whole transport block is decoded successfully by the UE 115-a. The total quantity of bits, sent over the first transmission 205 and subsequent modified transmissions 215 determine the actual used rate for each transport block.

[0086] FIG. 3 shows an example of a transmission diagram 300 that supports techniques for reporting the G2C metric in MIRS in accordance with one or more aspects of the present disclosure. In some examples, the transmission diagram may be implemented by the wireless communications system 200 and the wireless communications system 100. For example, the network entity 105-a may transmit theinitial transmission 205 and subsequent modified transmissions 21 in a manner demonstrated by the transmission diagram 300.

[0087] The 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 coding rate equivalent to MCS27. The first subsequent modified transmission 215-a may add a small quantity of additional coding bits 310 to the first transmission 205-a to provide an effective coding rate equivalent to MCS26. The coded bits may be parity bits that may be used for Chase combining or incremental redundancy for decoding of the transport block 305.Similarly, the second subsequent modified transmission 215-b may add a small quantity of additional coding bits 315 to the first subsequent modified transmission 215-a to provide an effective coding rate equivalent to MCS25. Likewise, the third subsequent modified transmission 215-c may add a small quantity' of additional coding bits 320 to the second subsequent modified transmission 215-b to provide an effective coding rate equivalent to MCS24. This scheme of operation is possible without reporting the G2C metric in the enhanced feedback message 210 by using the ACK or NACK report with each NACK reducing the MCS. However, using the G2C metric in the enhanced feedback message 210 allows the transmitter to jump multiple MCS levels to the required MCS as to provide the required rate. That is, the enhanced feedback message 210 with the G2C metric allows the transmitter to cross the gap immediately to the required MCS hence the name gap to capacity.

[0088] MIRS may closely track channel variation and achieve higher throughput over a large signal to noise ratio than the CSI-RS scheme. The gain over optimal MCS may be mainly provided using per CB feedback which is optional in MIRS. With per TB feedback, performance of MIRS may align to the optimal MCS for all speeds. MIRS based on multiple IR-HARQ retransmissions may provide gains over the CSI-RS scheme and may achieve channel capacity regardless of UE mobility. MIRS may provide above 6 dB gains in a wide range of channel models and velocities in noise limited scenarios. MIRS may provide resiliency to interference and may achieve gains in interference limited scenarios. The CB based MIRS may provide improvedperformance and significant gains over the CSI-RS scheme. The transport block based MIRS without an interleaver may also provide improved performance and significant gains over the CSI-RS scheme. Similarly, applying a transport block MIRS with interleaver may further improve performance with a small degradation as compared to the CB based MIRS. MIRS may be resilient to interference and may provide throughput gains for a wide range of signal and interference ratios.

[0089] MIRS may increase the overall latency and the HARQ buffer size. To mitigate the quantity of re-transmissions in MIRS, the UE 115-a may report, to the network entity 105-a, the enhanced feedback message 210 indicating a G2C metric. The G2C metric may indicate a size of the next-retransmission (e.g., subsequent modified transmission 215) based on calculated mutual information (MI) per information bit. In the dow nload example, the UE 115-a may calculate a Mi-based metric, representing the MI per information bit. The UE 115-a may translate the MI -based metric to the G2C metric which is reported to the network entity 105-a. The network entity 105-a may use the G2C metric for selection of the size of the next retransmission (e.g., quantity of additional coding bits to add to the previous transmission). The G2C metric may be reported via the HARQ feedback (e.g., enhanced feedback message 210) for the received physical downlink shared channel (PDSCH).

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

[0091] In some examples, the numerical MI calculation for a set of LLRs may be illustrated with the following equations:

[0098] In some examples, the UE 115-a may evaluate a quantity of resources sufficient for a retransmission to achieve a target MI metric based on the calculated averages. The G2C metric may be the determined quantity7of resources sufficient for a retransmission to achieve a target MI metric. The UE 115-a may transmit, to the network entity 105-a, the enhanced feedback message 210 indicating the G2C metric. The G2C metric may be restricted to a multiplication of MIRS of the initial transmission resources. The network entity7105-a may evaluate the next transmission size based on the G2C metric and transmit the subsequent modified transmission 215 including a quantity of additional coded bits based on the G2C metric.

[0099] In some examples, the G2C metric may be limited by thermal noise or by interference, and the determination of the next retransmission size may be adversely impacted by thermal noise or by interference. The thermal noise G2C metric may change smoothly in a rate proportional to the UE velocity reports, and the G2C metric may be considered a reliable estimate of the re-transmission size. The interference limited G2C metric, such as interference from other cells, may be more difficult to track and may change abruptly. In some cases, the network entity 105-a may have a-pnory information about expected interference, and the network entity 105-a may be able to account for the expected interference in the re-transmission size. In another case, the network entity 105-a may perform different backoff and different re-transmission policy for interference limited and thermal limited G2Cs. In some examples, reporting whether the G2C metric is interference limited or thermal noise limited may be advantageous.

[0100] In some cases, the UE 115-a may report, to the network entity 105-a, the enhanced feedback message 210 with data indicative of thermal noise data, interference data or both. The network entity 105-a may transmit the subsequent modifiedtransmission 215 (e g., re-transmission of the initial transmission with a quantity of coded bits) based in part on the information (or data) indicating the thermal noise, the interference or both. In some examples, the network entity 105 -a may transmit, to the UE 115-a, signaling 220 indicating a configuration for reporting the G2C metric, the noise data, the interference data or both the noise data and the interference data. The UE 115-a may transmit, to the network entity 105-a, the enhanced feedback message 210, based on the configuration, indicating the G2C metric, the noise data, the interference data or the noise data and the interference data.

[0101] In some examples, in addition to reporting the G2C metric, the UE 115-a may report information based on the estimated noise. For example, the UE 115-a may estimate the noise and report, to the network entity 105-a, information based on estimated noise. In some cases, the UE 115-a may determine a noise covariance matrix and may report, to the network entity 105-a, values of the noise covariance matrix. For example, the UE 115-a may report eigenvalues of the noise covariance matrix. The difference between the highest eigenvalue of the noise covariance matrix and the lowest eigenvalue of the noise covariance matrix may represent how much the interference is above the thermal noise. In one example, the UE 115-a may report all of the eigenvalues of the noise covariance matrix. In another example, the UE 115-a may report a strongest eigenvalue of the noise covariance matrix, a weakest eigenvalue of the noise covariance matrix or both the strongest and the weakest eigenvalue of the noise covariance matrix. In a further example, the UE 115-a may report selected eigenvalues of noise covariance matrix. In one example, the UE 115-a may report the noise covariance matrix condition number. In another example, the UE 1 15-a may report the full noise covariance matrix as well as the combining weights (e.g., minimum mean-square estimation (MMSE)) employed by the noise covariance matrix. The network entity 105-a may use the full noise covariance matrix and the combining weights to understand the suppression achieved for the interference and the real interference level as observed at the UE 115-a. The network entity 105-a may estimate the next re-transmission size based on the noise data. Additionally, the network entity 105-a may have some knowledge of the interference persistence in future slots, and the network entity 105-a may perform additional backoff for the G2C metric that is interference limited.

[0102] In some examples, the UE 1 15-a may report the G2C metric and a hypothetical G2C metric as if no interference is present and only thermal noise is present. In some examples, the network entity 105-a may transmit the signaling 220 indicating the configuration for reporting the G2C metric including reporting the hypothetical G2C metric. The UE 115-a may determine the thermal noise G2C metric (e.g., G2C metric with no interference present) based on an additive white gaussian noise (AWGN) variance, the noise covariance matrix, demodulation characteristics of the UE 115-a or a combination of thereof. In some examples, the UE 115-a may calculate the thermal noise G2C metric using the demodulation reference signal (DMRS) symbols. For example, the UE 115-a may evaluate, per CB, the channel response of the CB relevant subcarriers and ODFM symbols, and the UE 115-a may estimate the AWGN variance. The channel response may be estimated in the same manner as estimated in the presence of interferences. In one example, the AWGN variance may be estimated using a noise variance estimated at the last transmission of zero-power-CSI-RS. In another example, the AWGN variance may be estimated as the lowest eigen value of the noise covariance matrix. In a further example, for a time selective or frequency selective noise covariance matrix, the AWGN variance may be represented by the lowest of all eigenvalues of all noise covariance matrixes.

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

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

[0105] In some cases, the network entity’ 105-a may secure interference reduced or interference free resources (e.g., resource blocks (RBs) in frequency and symbols in time), and the network entity 105-a may instruct the UE 115-a to report the frequency selective G2C metric, the time selective G2C metric or both on the indicated interference reduced or interference free REs as well as G2C metric on the rest of the resources. The network entity 105-a may provide instructions to the UE 115-a as part of a downlink control information (DCI) message, a MAC control element (MAC-CE) message or a RRC message. The requested reports may be periodic, a-periodic or semiperiodic. The network entity 105-a may estimate the next re-transmission size based on the frequency selective G2C metric, time selective G2C metric or both frequency and time selective G2C metric.

[0106] In some examples, the UE 115-a may report frequency selective noise data, frequency selective interference data or both frequency selective noise and interference data. In another example, the UE 115-a may report time selective noise data, time selective interference data or both time selective noise and interference data. In a further example, the 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, the network entity 105-a may transmit the signaling 220 indicating the configuration for reporting the G2C metric and the noise data, the interference data or both associated with the G2C metric. The configuration may indicate a frequency resource, a time resource or both the frequency resource and the time resource for reporting the noise data, the interference data or both. In another example, the network entity 105-a may instruct the UE 115-a to report, via the configuration, the noise data, interference data or both on specified frequency resource, time resource or both. The network entity 105-a may provide via the configuration to the UE 115-a as part of a dow nl ink control information (DCI) message, a MAC control element (MAC-CE) message or a RRC message. The requested reports may be periodic.a-periodic or semi-periodic. In some examples, the UE 115-a may transmit the enhanced feedback message 210 indicating the noise data, such as the noise covariance matrix details discussed herein (e.g., information about one or more eigenvalues of the noise covariance matrix) in the frequency selective, time selective or frequency and time selective manner. In some examples, the UE 1 15-a may transmit the enhanced feedback message 210 indicating the hypothetical C2G metric with observed interference removed in the frequency selective, time selective or frequency and time selective manner. The network entity 105-a may estimate the next re-transmission size based in part on the frequency selective, time selective or both frequency and time selective noise data and / or interference data.

[0107] FIG. 4 shows an example of a process flow 400 that supports techniques for reporting the G2C metric in MIRs in accordance with one or more aspects of the present disclosure. In some examples, the process flow 400 may implement or be implemented by aspects of the wireless communications systems 100 and 200 as described with reference to FIGs. 1 and 2, respectively. For example, the process flow 400 may be implemented by a network entity 105-b and a UE 115-b, which may be respective examples of network entities 105 and UEs 115 as described with reference to FIGs. 1 and 2, respectively.

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

[0109] At 405, the network entity 105-b may transmit, to the UE 115-b, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric. In one example, the configuration indicates a frequency resource, a time resource or a combination thereof for reporting the G2C metric associated with the frequency resource, the time resource or the combination thereof. In another example, the configuration indicates a frequency resource, a time resource or a combination thereof for reporting the noise data, the interference data orboth is associated with the frequency resource, the time resource or the combination thereof.

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

[0112] In some examples, the G2C metric may be associated with the frequency resource, the time resource or the combination thereof indicated in the configuration. In some examples, the noise data, the interference data or both may be associated may be associated with the frequency resource, the time resource or the combination thereof indicated in the configuration

[0113] In some examples, the feedback message may indicate a second G2C metric. The second G2C metric may remove observed interference. In some examples, the UE 115-b may estimate an AWFN variance based in part on a zero-power-channel-state- information-reference-signal transmission or a 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 a demodulator characteristic of the UE, or any combination thereof.

[0114] At 420, the network entity may transmit the transport block with a quantity of one or more coded bits. The quantity of the one or more coded bits is based at least in part on the G2C metric and the noise data, the interference data or both. In some examples, the quantity of the one or more coded bits may be based at least in part on the second G2C metric. The quantity of the one or more coded bits is based at least in part on the G2C metric and the noise data, the interference data or both associated with the frequency resource, the time resource or the combination thereof indicated in the configuration. In some examples, the quantity of the one or more coded bits may be based at least in part on the second G2C metric associated with the frequency resource, the time resource or the combination thereof indicated in the configuration

[0115] FIG. 5 shows a block diagram 500 of a device 505 that supports techniques for reporting the G2C metric in MIRS in accordance w ith one or more aspects of the present disclosure. The device 505 may be an example of aspects of a network entity 105 as described herein. The device 505 may include a receiver 510, a transmitter 515. and a communications manager 520. The device 505, or one or more components of the device 505 (e.g., the receiver 510, the transmitter 515, and the communications manager 520), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0116] The receiver 510 may provide a means for obtaining (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). Information may be passed on to other components of the device 505. In some examples, the receiver 510 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 510 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0117] The transmitter 515 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of thedevice 505. For example, the transmitter 515 may output 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). In some examples, the transmitter 515 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the 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, the transmitter 515 and the receiver 510 may be co-located in a transceiver, which may include or be coupled with a modem.

[0118] The communications manager 520, the receiver 510, the transmitter 515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of techniques for reporting the G2C metric in MIRS as described herein. For example, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

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

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

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

[0122] The communications manager 520 may support wireless communication in accordance with examples as disclosed herein. For example, the communications manager 520 is capable of, configured to, or operable to support a means for transmitting, to a UE, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric. The communications manager 520 is capable of, configured to, or operable to support a means for transmitting, to the UE. a transport block. The communications manager 520 is capable of, configured to, or operable to support a means for receiving, from the UE, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both. The communications manager 520 is capable of. configured to, or operable to support a means for transmitting, from the network entity, the transport block with a quantify of one or more coded bits, where the quantify of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0123] By including or configuring the communications manager 520 in accordance with examples as described herein, the device 505 (e.g.. at least one processor controlling or otherwise coupled with the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof) may support techniques for more efficient utilization of communication resources).

[0124] FIG. 6 shows a block diagram 600 of a device 605 that supports techniques for reporting the G2C metric in MIRS in accordance with one or more aspects of the present disclosure. The device 605 may be an example of aspects of a device 505 or a network entity 105 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605, or one or more components of the device 605 (e.g., the receiver 610, the transmitter 615, and the communications manager 620), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g.. via one or more buses).

[0125] The receiver 610 may provide a means for obtaining (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). Information may be passed on to other components of the device 605. In some examples, the receiver 610 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 610 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0126] The transmitter 615 may provide a means for outputting (e g., transmitting, providing, conveying, sending) information generated by other components of the device 605. For example, the transmitter 615 may output 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). In some examples, the transmitter 615 may support outputting information bytransmitting signals via one or more antennas. Additionally, or alternatively, the 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, the transmitter 615 and the receiver 610 may be co-located in a transceiver, which may include or be coupled with a modem.

[0127] The device 605, or various components thereof, may be an example of means for performing various aspects of techniques for reporting the G2C metric in MIRS as described herein. For example, the communications manager 620 may include a configuration manager 625, a transport block manager 630, a feedback manager 635. a coded bits manager 640, or any combination thereof. The communications manager 620 may be an example of aspects of a communications manager 520 as described herein. In some examples, the communications manager 620, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610. the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0128] The communications manager 620 may support wireless communication in accordance with examples as disclosed herein. The configuration manager 625 is capable of, configured to, or operable to support a means for transmitting, to a UE, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric. The transport block manager 630 is capable of, configured to, or operable to support a means for transmitting, to the UE, a transport block. The feedback manager 635 is capable of, configured to, or operable to support a means for receiving, from the UE. a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both. The coded bits manager 640 is capable of, configured to, or operable to support a means for transmitting, from the network entity7, the transport block with a quantity of one or more coded bits, where the quantity of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0129] FIG. 7 shows a block diagram 700 of a communications manager 720 that supports techniques for reporting the G2C metric in MIRS in accordance with one or more aspects of the present disclosure. The communications manager 720 may be an example of aspects of a communications manager 520, a communications manager 620,or both, as described herein. The communications manager 720, or various components thereof, may be an example of means for performing various aspects of techniques for reporting a G2C metric in a multiple incremental redundancy scheme as described herein. For example, the communications manager 720 may include a configuration manager 725, a transport block manager 730, a feedback manager 735, a coded bits manager 740, a noise covariance matrix manager 745, a second gap to capacity manager 750, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses) which may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity' 105), or any combination thereof.

[0130] The communications manager 720 may support wireless communication in accordance with examples as disclosed herein. The configuration manager 725 is capable of, configured to, or operable to support a means for transmitting, to a UE. signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric. The transport block manager 730 is capable of, configured to, or operable to support a means for transmitting, to the UE, a transport block. The feedback manager 735 is capable of. configured to, or operable to support a means for receiving, from the UE, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both. The coded bits manager 740 is capable of, configured to, or operable to support a means for transmitting, from the network entity, the transport block with a quantity of one or more coded bits, where the quantity of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0131] In some examples, the noise covariance matrix manager 745 is capable of, configured to, or operable to support a means for receiving, from the UE, one or more values of a noise covariance matrix.

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

[0133] In some examples, 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, a strongest eigenvalue of the noise covariance matrix, or a weakest eigenvalue of the noise covariance matrix.

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

[0135] In some examples, the noise covariance matrix manager 745 is capable of, configured to, or operable to support a means for receiving, from the UE. an indication of a noise covariance matrix and an indication of one or more combining weights of the noise covariance matrix.

[0136] In some examples, the second gap to capacity manager 750 is capable of, configured to, or operable to support a means for receiving, from the UE. the feedback message indicating a second G2C metric, where the second G2C metric removes observed interference.

[0137] In some examples, the quantity of the one or more coded bits is based in part on the second G2C metric.

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

[0139] In some examples, the configuration indicates a frequency resource, a time resource or a combination thereof, and the noise data, the interference data or both is associated with the frequency resource, the time resource or the combination thereof.

[0140] FIG. 8 shows a diagram of a system 800 including a device 805 that supports techniques for reporting the G2C metric in MIRS in accordance with one or more aspects of the present disclosure. The device 805 may be an example of or include the components of a device 505, a device 605, or a network entity 105 as described herein. The device 805 may communicate with one or more network entities 105, one ormore UEs 1 15, or any combination thereof, which may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device 805 may include components that support outputting and obtaining communications, such as a communications manager 820, a transceiver 810, an antenna 815, at least one memory 825, code 830, and at least one processor 835. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g.. a bus 840).

[0141] The transceiver 810 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 810 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 810 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver. In some examples, the device 805 may include one or more antennas 815, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 810 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 815, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas 815, from a wired receiver), and to demodulate signals. In some implementations, the transceiver 810 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 815 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 815 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 810 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 810, or the transceiver 810 and the one or more antennas 815, or the transceiver 810 and the one or more antennas 815 and one or more processors or one or more memory components (e.g., the at least one processor 835, the at least one memory 825, or both), may be included in a chip or chip assembly that isinstalled in the device 805. Tn some examples, the transceiver 810 may be operable to support communications via one or more communications links (e.g., a communication link 125, a backhaul communication link 120, a midhaul communication link 162, a fronthaul communication link 168).

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

[0143] The at least one processor 835 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the at least one processor 835 may be configured to operate a memory array using a memoiy controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 835. The at least one processor 835 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 825) to cause the device 805 to perform various functions (e.g., functions or tasks supporting techniques for reporting a G2C metric in a multiple incremental redundancy scheme). For example, the device 805 or a component of the device 805 may include at least one processor 835 and at least one memory 825 coupled with one or more of the at least one processor 835, the at least one processor 835 andthe at least one memory 825 configured to perform various functions described herein. The 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 operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 830) to perform the functions of the device 805. The 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 the device 805 (such as within one or more of the at least one memory 825). In some examples, the at least one processor 835 may include multiple processors and the at least one memory 825 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 835 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 835) and memory circuitry (which may include the at least one memory 825)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. As such, the at least one processor 835 or a processing system including the at least one processor 835 may be configured to, configurable to, or operable to cause the device 805 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to.” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 825 or otherwise, to perform one or more of the functions described herein.

[0144] In some examples, a bus 840 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 840 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of the device 805, or between different components of the device 805 that may be co-located or located in different locations (e.g., where the device 805 may refer to a system in which one or more of the communications manager 820, thetransceiver 810, the at least one memon 825, the code 830, and the at least one processor 835 may be located in one of the different components or divided between different components).

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

[0146] The communications manager 820 may support wireless communication in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for transmitting, to a UE, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric. The communications manager 820 is capable of. configured to, or operable to support a means for transmitting, to the UE, a transport block. The communications manager 820 is capable of, configured to, or operable to support a means for receiving, from the UE, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both. The communications manager 820 is capable of, configured to, or operable to support a means for transmitting, from the network entity, the transport block with a quantity of one or more coded bits, where the quantity of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0147] By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 may support techniques for improved communication reliability, reduced latency, more efficient utilization of communication resources, and improved coordination between devices.

[0148] In some examples, the communications manager 820 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 810, the one or more antennas 815 (e.g., where applicable), or any combination thereof. Although the communications manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 820 may be supported by or performed by the transceiver 810, one or more of the at least one processor 835, one or more of the at least one memory 825. the code 830, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 835, the at least one memory 825, the code 830, or any combination thereof). For example, the code 830 may include instructions executable by one or more of the at least one processor 835 to cause the device 805 to perform various aspects of techniques for reporting a G2C metric in a multiple incremental redundancy scheme as described herein, or the at least one processor 835 and the at least one memory 825 may be otherwise configured to, individually or collectively, perform or support such operations.

[0149] FIG. 9 shows a block diagram 900 of a device 905 that supports techniques for reporting the G2C metric in MIRS in accordance with one or more aspects of the present disclosure. The device 905 may be an example of aspects of a UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905, or one or more components of the device 905 (e.g., the receiver 910, the transmitter 915. and the communications manager 920), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0150] The receiver 910 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for reporting a G2C metric in a multiple incremental redundancy scheme). Information may be passed on to other components of the device 905. The receiver 910 may utilize a single antenna or a set of multiple antennas.

[0151] The transmitter 915 may provide a means for transmitting signals generated by other components of the device 905. For example, the 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 for reporting a G2C metric in a multiple incremental redundancy scheme). In some examples, the transmitter 915 may be colocated with a receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a set of multiple antennas.

[0152] The communications manager 920, the receiver 910, the transmitter 915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of techniques for reporting a G2C metric in a multiple incremental redundancy scheme as described herein. For example, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

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

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

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

[0156] The communications manager 920 may support wireless communication in accordance with examples as disclosed herein. For example, the communications manager 920 is capable of, configured to, or operable to support a means for receiving, from a network entity, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric. The communications manager 920 is capable of, configured to, or operable to support a means for receiving, from the network entity, a transport block. The communications manager 920 is capable of, configured to, or operable to support a means for transmitting, to the network entity, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both. The communications manager 920 is capable of, configured to, or operable to support a means for receiving, from the network entity, the transport block with a quantity of one or more coded bits, where the quantity of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0157] By including or configuring the communications manager 920 in accordance with examples as described herein, the device 905 (e.g.. at least one processor controlling or otherwise coupled with the receiver 910, the transmitter 915, the communications manager 920, or a combination thereof) may support techniques for more efficient utilization of communication resources.

[0158] FIG. 10 shows a block diagram 1000 of a device 1005 that supports techniques for reporting the G2C metric in MIRS in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of aspects of a device 905 or a UE 115 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020. The device 1005, or one or more components of the device 1005 (e.g., the receiver 1010, the transmitter 1015, and the communications manager 1020), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g.. via one or more buses).

[0159] The receiver 1010 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for reporting a G2C metric in a multiple incremental redundancy scheme). Information may be passed on to other components of the device 1005. The receiver 1010 may utilize a single antenna or a set of multiple antennas.

[0160] The transmitter 1015 may provide a means for transmitting signals generated by other components of the device 1005. For example, the 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 for reporting a G2C metric in a multiple incremental redundancy scheme). In some examples, the transmitter 1015 may be co-located with a receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a set of multiple antennas.

[0161] The device 1005. or various components thereof, may be an example of means for performing various aspects of techniques for reporting a G2C metric in a multiple incremental redundancy scheme as described herein. For example, the communications manager 1020 may include a configuration manager 1025, a transport block manager 1030. a feedback manager 1035. a coded bits manager 1040, or any combination thereof. The communications manager 1020 may be an example of aspects of a communications manager 920 as described herein. In some examples, the communications manager 1020, or various components thereof, may be configured to perform various operations (e.g.. receiving, obtaining, monitoring, outputting,transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0162] The communications manager 1020 may support wireless communication in accordance with examples as disclosed herein. The configuration manager 1025 is capable of, configured to, or operable to support a means for receiving, from a network entity, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric. The transport block manager 1030 is capable of, configured to, or operable to support a means for receiving, from the network entity, a transport block. The feedback manager 1035 is capable of, configured to, or operable to support a means for transmitting, to the network entity, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both. The coded bits manager 1040 is capable of, configured to, or operable to support a means for receiving, from the network entity, the transport block with a quantity of one or more coded bits, where the quantity of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0163] FIG. 11 shows a block diagram 1100 of a communications manager 1120 that supports techniques for reporting the G2C metric in MIRS in accordance with one or more aspects of the present disclosure. The communications manager 1120 may be an example of aspects of a communications manager 920, a communications manager 1020, or both, as described herein. The communications manager 1120, or various components thereof, may be an example of means for performing various aspects of techniques for reporting a G2C metric in a multiple incremental redundancy scheme as described herein. For example, the communications manager 1120 may include a configuration manager 1125, a transport block manager 1130, a feedback manager 1135, a coded bits manager 1140, a noise covariance matrix manager 1145, a second gap to capacity manager 1150, an AWGN variance manager 1155, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g.. oneor more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0164] The communications manager 1120 may support wireless communication in accordance with examples as disclosed herein. The configuration manager 1125 is capable of, configured to, or operable to support a means for receiving, from a network entity, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric. The transport block manager 1130 is capable of, configured to, or operable to support a means for receiving, from the network entity, a transport block. The feedback manager 1135 is capable of, configured to, or operable to support a means for transmitting, to the network entity, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both. The coded bits manager 1140 is capable of, configured to, or operable to support a means for receiving, from the network entity, the transport block with a quantity of one or more coded bits, where the quantity of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0165] In some examples, the noise covariance matrix manager 1145 is capable of, configured to, or operable to support a means for transmitting, to the network entity’, one or more values of a noise covariance matrix.

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

[0167] In some examples, 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, a strongest eigenvalue of the noise covariance matrix, or a weakest eigenvalue of the noise covariance matrix.

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

[0169] In some examples, the noise covariance matrix manager 1145 is capable of, configured to, or operable to support a means for transmitting, to the network entity, anindication of a noise covariance matrix and an indication of one or more combining weights of the noise covariance matrix.

[0170] In some examples, the second gap to capacity manager 1150 is capable of, configured to, or operable to support a means for transmitting, to the network entity, the feedback message indicating a second G2C metric, where the second G2C metric removes observed interference.

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

[0172] In some examples, the quantity of the one or more coded bits is based in part on the second G2C metric.

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

[0174] In some examples, the configuration indicates a frequency resource, a time resource or a combination thereof, and the noise data, the interference data or both is associated with the frequency resource, the time resource or the combination thereof.

[0175] FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports techniques for reporting the G2C metric in MIRS in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of or include the components of a device 905. a device 1005, or a UE 115 as described herein. The device 1205 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1205 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1220. an input / output (I / O) controller 1210, a transceiver 1215, an antenna1225, at least one memory 1230, code 1235, and at least one processor 1240. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g.. a bus 1245).

[0176] The I / O controller 1210 may manage input and output signals for the device 1205. The I / O controller 1210 may also manage peripherals not integrated into the device 1205. In some cases, the I / O controller 1210 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 1210 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®. OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally, or alternatively, the I / O controller 1210 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I / O controller 1210 may be implemented as part of one or more processors, such as the 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.

[0177] In some cases, the device 1205 may include a single antenna 1225. However, in some other cases, the device 1205 may have more than one antenna 1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1215 may communicate bi-directionally, via the one or more antennas 1225, wired, or wireless links as described herein. For example, the transceiver 1215 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1215 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1225 for transmission, and to demodulate packets received from the one or more antennas 1225. The transceiver 1215, or the transceiver 1215 and one or more antennas 1225, may be an example of a transmitter 915, a transmitter 1015, a receiver 910, a receiver 1010. or any combination thereof or component thereof, as described herein.

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

[0179] The at least one processor 1240 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof)- In some cases, the at least one processor 1240 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 1240. The at least one processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 1230) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting techniques for reporting a G2C metric in a multiple incremental redundancy scheme). For example, the device 1205 or a component of the device 1205 may include at least one processor 1240 and at least one memory 1230 coupled with or to the at least one processor 1240, the at least one processor 1240 and at least one memory 1230 configured to perform various functions described herein. In some examples, the at least one processor 1240 may include multiple processors and the at least one memory 1230 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1240 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1240) and memory circuitry (which may include the at least one memory 1230)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. As such, the at least one processor 1240 or a processing system including the at least one processor 1240 may be configured to, configurable to,or operable to cause the device 1205 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability’, when executing code stored in the at least one memory’ 1230 or otherwise, to perform one or more of the functions described herein.

[0180] The communications manager 1220 may support wireless communication in accordance with examples as disclosed herein. For example, the communications manager 1220 is capable of, configured to, or operable to support a means for receiving, from a network entity, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric. The communications manager 1220 is capable of, configured to, or operable to support a means for receiving, from the network entity’, a transport block. The communications manager 1220 is capable of, configured to, or operable to support a means for transmitting, to the network entity, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both. The communications manager 1220 is capable of, configured to, or operable to support a means for receiving, from the network entity, the transport block with a quantity of one or more coded bits, where the quantity of the one or more coded bits is based on the G2C metric and the noise data, the interference data or both.

[0181] By including or configuring the communications manager 1220 in accordance with examples as described herein, the device 1205 may support techniques for improved communication reliability, reduced latency, more efficient utilization of communication resources, and improved coordination between devices.

[0182] In some examples, the communications manager 1220 may be configured to perform various operations (e g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1215, the one or more antennas 1225, or any combination thereof. Although the communications manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1220 may be supported by or performed by the at least one processor 1240, the at least one memory’ 1230, the code 1235, or any combination thereof. For example, the code 1235 may include instructions executable by the at least one processor 1240 to cause the device 1205 to perform various aspects of techniquesfor reporting a G2C metric in a multiple incremental redundancy scheme as described herein, or the at least one processor 1240 and the at least one memon 1230 may be otherwise configured to, individually or collectively, perform or support such operations.

[0183] FIG. 13 shows a flowchart illustrating a method 1300 that supports techniques for reporting the G2C metric in MIRS in accordance with aspects of the present disclosure. The operations of the method 1300 may be implemented by a network entity or its components as described herein. For example, the operations of the method 1300 may be performed by a network entity as described with reference to FIGs. 1 through 8. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

[0184] At 1305, the method may include transmitting, to a UE, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric. The operations of block 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by a configuration manager 725 as described with reference to FIG. 7.

[0185] At 1310, the method may include transmitting, to the UE, a transport block. The operations of block 1310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by a transport block manager 730 as described with reference to FIG. 7.

[0186] At 1315, the method may include receiving, from the UE, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both. The operations of block 1315 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed by a feedback manager 735 as described with reference to FIG. 7.

[0187] At 1320, the method may include transmitting, from the network entity, the transport block with a quantity of one or more coded bits, where the quantity of the oneor more coded bits is based on the G2C metric and the noise data, the interference data or both. The operations of block 1320 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed by a coded bits manager 740 as described with reference to FIG. 7.

[0188] FIG. 14 shows a flowchart illustrating a method 1400 that supports techniques for reporting the G2C metric in MIRS in accordance with aspects of the present disclosure. The operations of the method 1400 may be implemented by a UE or its components as described herein. For example, the operations of the method 1400 may be performed by a UE 115 as described with reference to FIGs. 1 through 4 and 9 through 12. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using specialpurpose hardware.

[0189] At 1405, the method may include receiving, from a network entity, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric. The operations of block 1405 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by a configuration manager 1125 as described with reference to FIG. 11.

[0190] At 1410, the method may include receiving, from the network entity, a transport block. The operations of block 1410 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by a transport block manager 1130 as described with reference to FIG. 11.

[0191] At 1415, the method may include transmitting, to the network entity, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both. The operations of block 1415 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by a feedback manager 1135 as described with reference to FIG. 11.

[0192] At 1420, the method may include receiving, from the network entity, the transport block with a quantity of one or more coded bits, where the quantity of the oneor more coded bits is based on the G2C metric and the noise data, the interference data or both. The operations of block 1420 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed by a coded bits manager 1140 as described with reference to FIG. 11.

[0193] The following provides an overview of aspects of the present disclosure:

[0194] Aspect 1 : A method for wireless communication by a network entity, comprising: transmitting, to a UE, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric; transmitting, to the UE, a transport block; receiving, from the UE, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both; and transmitting, from the network entity, the transport block with a quantity of one or more coded bits, wherein the quantity of the one or more coded bits is based at least in part on the G2C metric and the noise data, the interference data or both.

[0195] Aspect 2: The method of aspect 1, wherein receiving the feedback message further comprising: receiving, from the UE, one or more values of a noise covariance matrix.

[0196] Aspect 3: The method of aspect 2, wherein the one or more values of the noise covariance matrix comprise one or more eigenvalues of the noise covariance matrix.

[0197] Aspect 4: The method of aspect 3, wherein the one or more eigenvalues comprise all of the eigenvalues of the noise covariance matrix, a subset of the eigenvalues of the noise covariance matrix, a strongest eigenvalue of the noise covariance matrix, or a weakest eigenvalue of the noise covariance matrix.

[0198] Aspect 5: The method of aspect 2, wherein the one or more values of the noise covariance matrix comprise a condition number of the noise covariance matrix, one or more combining weights of the noise covariance matrix, or a combination thereof.

[0199] Aspect 6: The method of any of aspects 1 through 5, wherein receiving the feedback message further comprising: receiving, from the UE, an indication of a noisecovariance matrix and an indication of one or more combining weights of the noise covariance matrix.

[0200] Aspect 7 : The method of any of aspects 1 through 6, wherein receiving the feedback message further comprising: receiving, from the UE, the feedback message indicating a second G2C metric, wherein the second G2C metric removes observed interference.

[0201] Aspect 8: The method of aspect 7, wherein the quantity of the one or more coded bits is based in part on the second G2C metric.

[0202] Aspect 9: The method of any of aspects 1 through 8, wherein the configuration indicates a frequency resource, a time resource or a combination thereof, and the G2C metric is associated with the frequency resource, the time resource or the combination thereof.

[0203] Aspect 10: The method of any of aspects 1 through 9, wherein the configuration indicates a frequency resource, a time resource or a combination thereof, and the noise data, the interference data or both is associated with the frequency resource, the time resource or the combination thereof.

[0204] Aspect 11: A method for wireless communication by a UE, comprising: receiving, from a network entity, signaling indicating a configuration for reporting a G2C metric and noise data, interference data or both associated with the G2C metric; receiving, from the network entity, a transport block; transmitting, to the network entity, a feedback message indicating reception of a portion of the transport block was unsuccessful, the G2C metric and the noise data, the interference data or both; and receiving, from the network entity, the transport block with a quantity of one or more coded bits, wherein the quantity of the one or more coded bits is based at least in part on the G2C metric and the noise data, the interference data or both.

[0205] Aspect 12: The method of aspect 11. wherein transmitting the feedback message further comprising: transmitting, to the network entity, one or more values of a noise covariance matrix.

[0206] Aspect 13: The method of aspect 12, wherein the one or more values of the noise covariance matrix comprise one or more eigenvalues of the noise covariance matrix.

[0207] Aspect 14: The method of aspect 13, wherein the one or more eigenvalues comprise all of the eigenvalues of the noise covariance matrix, a subset of the eigenvalues of the noise covariance matrix, a strongest eigenvalue of the noise covariance matrix, or a weakest eigenvalue of the noise covariance matrix.

[0208] Aspect 15: The method of any of aspects 13 through 14, wherein the one or more values of the noise covariance matrix comprise a condition number of the noise covariance matrix, one or more combining weights of the noise covariance matrix, or a combination thereof.

[0209] Aspect 16: The method of aspect 11, wherein receiving the feedback message further comprising: transmitting, to the network entity, an indication of a noise covariance matrix and an indication of one or more combining weights of the noise covariance matrix.

[0210] Aspect 17: The method of any of aspects 11 through 16. wherein transmitting the feedback message further comprising: transmitting, to the network entity7, the feedback message indicating a second G2C metric, wherein the second G2C metric removes observed interference.

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

[0212] Aspect 19: The method of any of aspects 17 through 18. wherein the quantity of the one or more coded bits is based in part on the second G2C metric.

[0213] Aspect 20: The method of any of aspects 11 through 19, wherein the configuration indicates a frequency resource, a time resource or a combination thereof,and the G2C metric is associated with the frequency resource, the time resource or the combination thereof.

[0214] Aspect 21 : The method of any of aspects 11 through 20, wherein the configuration indicates a frequency resource, a time resource or a combination thereof, and the noise data, the interference data or both is associated with the frequency resource, the time resource or the combination thereof.

[0215] Aspect 22: A network entity for wireless communication, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 1 through 10.

[0216] Aspect 23: A network entity for wireless communication, comprising at least one means for performing a method of any of aspects 1 through 10.

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

[0218] Aspect 25: A UE for wireless communication, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 11 through 21.

[0219] Aspect 26: A UE for wireless communication, comprising at least one means for performing a method of any of aspects 11 through 21.

[0220] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform a method of any of aspects 11 through 21.

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

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

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

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

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

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

[0227] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e.. A and B and C). Also, as used herein, the phrase“based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

[0228] As used herein, including in the claims, the article “a” before a noun is open- ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a,” “at least one,” “one or more,” “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components.” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.”

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

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

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

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

Claims

CLAIMSWhat is claimed is:1 . A network entity, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to: transmit, to a user equipment (UE), signaling indicating a configuration for reporting a gap to capacity metric and noise data, interference data or both associated with the gap to capacity metric; transmit, to the UE, a transport block; receive, from the UE. a feedback message indicating reception of a portion of the transport block was unsuccessful, the gap to capacity metric and the noise data, the interference data or both; and transmit, from the network entity, the transport block with a quantity of one or more coded bits, wherein the quantity of the one or more coded bits is based at least in part on the gap to capacity metric and the noise data, the interference data or both.

2. The network entity of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to: receive, from the UE, one or more values of a noise covariance matrix.

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

4. The network entity of claim 3, wherein the one or more eigenvalues comprise all of the eigenvalues of the noise covariance matrix, a subset of the eigenvalues of the noise covariance matrix, a strongest eigenvalue of the noise covariance matrix, or a 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 comprise a condition number of the noise covariancematrix, one or more combining weights of the noise covariance matrix, or a combination thereof.

6. The network entity of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to: receive, from the UE, an indication of a noise covariance matrix and an indication of one or more combining weights of the noise covariance matrix.

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

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

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

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

11. A user equipment (UE), comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to:receive, from a network entity, signaling indicating a configuration for reporting a gap to capacity metric and noise data, interference data or both associated with the gap to capacity metric; receive, from the network entity, a transport block; transmit, to the network entity, a feedback message indicating reception of a portion of the transport block was unsuccessful, the gap to capacity metric and the noise data, the interference data or both; and receive, from the network entity, the transport block with a quantity of one or more coded bits, wherein the quantity of the one or more coded bits is based at least in part on the gap to capacity metric and the noise data, the interference data or both.

12. The UE of claim 11, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: transmit, to the network entity, one or more values of a noise covariance matrix.

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

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

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

16. The UE of claim 11 , wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: transmit, to the network entity, an indication of a noise covariance matrix and an indication of one or more combining weights of the noise covariance matrix.

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

18. The UE of claim 17, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: estimate an additive white gaussian noise variance based in part on a zero-power-channel-state-information-reference-signal transmission or a noise covariance matrix; wherein the second gap to capacity' be based at least in part on one or more of the additive white gaussian noise variance, the noise covariance matrix, a demodulator characteristic of the UE, or any combination thereof.

19. The UE of claim 17, wherein the quantity of the one or more coded bits is based in part on the second gap to capacity metric.

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

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

22. A method for wireless communication by a network entity, comprising: transmitting, to a user equipment (UE), signaling indicating a configuration for reporting a gap to capacity metric and noise data, interference data or both associated with the gap to capacity metric; transmitting, to the UE. a transport block;receiving, from the UE, a feedback message indicating reception of a portion of the transport block was unsuccessful, the gap to capacity metric and the noise data, the interference data or both; and transmitting, from the network entity, the transport block with a quantity of one or more coded bits, wherein the quantity of the one or more coded bits is based at least in part on the gap to capacity metric and the noise data, the interference data or both.

23. The method of claim 22, wherein receiving the feedback message further comprising: receiving, from the UE, one or more values of a noise covariance matrix.

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

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

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

27. A method for wireless communication by a user equipment (UE), comprising: receiving, from a network entity, signaling indicating a configuration for reporting a gap to capacity metric and noise data, interference data or both associated with the gap to capacity metric; receiving, from the network entity, a transport block;transmiting, to the network entity, a feedback message indicating reception of a portion of the transport block was unsuccessful, the gap to capacity metric and the noise data, the interference data or both; and receiving, from the network entity, the transport block with a quantity of one or more coded bits, wherein the quantity' of the one or more coded bits is based at least in part on the gap to capacity metric and the noise data, the interference data or both.

28. The method of claim 27, wherein transmiting the feedback message further comprising: transmiting, to the network entity, one or more values of a noise covariance matrix.

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

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

Images