CQI uncertainty reporting for latency reduction in MIRS

Abstract

An apparatus may be a UE configured to identify at least one performance metric associated with a channel estimation operation at the UE. The apparatus may be further configured to calculate at least one uncertainty value associated with the at least one performance metric. The apparatus may also be configured to send a first indication of the at least one uncertainty value associated with the at least one performance metric to the network node. For example, an apparatus may be a network node configured to receive, from a UE, a first indication and a second indication of at least one value of at least one performance metric associated with at least one uncertainty value, and selecting a set of parameters for subsequent communications based on the at least one value of the at least one performance metric and the at least one uncertainty value.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. nonprovisional patent application No. 18 / 333,458, filed on June 12, 2023, entitled “CQI UNCERTAINTY REPORT FORLATENCY REDUCTION IN MIRS”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates generally to communication systems, and more specifically to multiple incremental redundancy schemes (MIRS) for identifying optimized modulation and decoding schemes used for communication. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CEM) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt these technologies. Summary of the Invention

[0006] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. It is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0007] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus can be a wireless device or a component of a wireless device or user equipment (UE) configured to identify at least one performance metric associated with a channel estimation operation at the UE. The apparatus can be further configured to calculate at least one uncertainty value associated with the at least one performance metric. The apparatus can also be configured to transmit, to a network node, an indication of the at least one uncertainty value associated with the at least one performance metric.

[0008] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus can be a network node, a network device, or a component of a network node or network device configured to receive, from a UE, a first indication of at least one uncertainty value associated with at least one performance metric associated with a channel estimation operation at the UE. The apparatus can be further configured to receive, from the UE, a second indication of at least one value of the at least one performance metric associated with the at least one uncertainty value. The apparatus can also be configured to select a set of parameters for subsequent communications based on the at least one value of the at least one performance metric and the at least one uncertainty value.

[0009] To the accomplishment of the foregoing and related aspects, one or more aspects can include the features recited in the following description and illustrated in the accompanying drawings. The following description and accompanying drawings provide illustrative examples of the various aspects. However, various changes can be made and equivalents employed. BRIEF DESCRIPTION OF DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communications system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of a downlink (DL) channel within a subframe, in accordance with various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

[0014] Figure 2D FIG. 1 is a diagram illustrating an example of an uplink (UL) channel within a subframe, in accordance with various aspects of the present disclosure.

[0015] Figure 3 FIG. 2 is a diagram illustrating an example of a base station and a UE in an access network.

[0016] Figure 4 FIG. 3 is a diagram illustrating an example associated with MIRS, in accordance with one or more aspects of the present disclosure.

[0017] Figure 5 FIG. 4 is a call flow diagram illustrating use of a reported uncertainty value in association with MIRS, in accordance with some aspects of the present disclosure.

[0018] Figure 6 FIG. 5 is a flow diagram of a method of wireless communication.

[0019] Figure 7 FIG. 6 is a flow diagram of a method of wireless communication.

[0020] Figure 8 FIG. 7 is a flow diagram of a method of wireless communication.

[0021] Figure 9 FIG. 8 is a flow diagram of a method of wireless communication.

[0022] Figure 10 FIG. 9 is a diagram illustrating an example of a hardware implementation for an apparatus.

[0023] Figure 11 FIG. 10 is a diagram illustrating an example of a hardware implementation for a network entity. DETAILED DESCRIPTION

[0024] In some aspects of wireless communication, MIRS can be used to dynamically adjust one or more of rate, precoding, and / or rank based on incremental redundancy (IR) hybrid automatic repeat request (HARQ) (IR-HARQ). In some aspects, a first transmission associated with MIRS can use a higher modulation and coding scheme (MCS) (e.g., an MCS associated with a larger MCS index value or an MCS associated with a higher throughput) than indicated by channel state information (CSI) (e.g., based on a channel quality indicator (CQI) or rank indicator (RI) included in the CSI) and can rely on multiple retransmissions to pass a cyclic redundancy check (CRC) for a transport block (TB) or code block (CB). A transmitting device (e.g., a base station or network node) can determine a first higher MCS (e.g., an MCS associated with an MCS index value that is three greater than a reported MCS index value) for the first transmission according to a predefined (static) gap and / or a (static) lookup table (LUT). However, the above solution using a static offset from the reported MCS (e.g., a number of MCSs based on the reported MCS) can be associated with a larger latency per CB due to the multiple retransmissions expected based on using the first (significantly) higher MCS.

[0025] Various aspects of the present disclosure generally relate to improvements to MIRS (or outer loop link adaptation (OLLA)) involving transmitting, from a receiving device, an uncertainty report associated with a MCS (or related characteristic) indicated by the receiving device (e.g., based on MCS estimation capabilities of the receiving device, channel conditions, Doppler effects, interference, signal to interference and noise ratio (SINR), etc.). While MIRS and OLLA are discussed below, they should be understood only as examples of methods associated with determining a MCS for a particular communication that can be improved based on a received uncertainty report. For example, in some aspects of the present disclosure, a receiving device (e.g., a wireless device or UE) can report an indication of uncertainty (e.g., an uncertainty report) associated with a CQI (or RI) estimate (e.g., via CSI) to a transmitting device (e.g., a base station or network node), which can use the indication to determine a (dynamic) gap (or offset) between a second higher MCS for a first MIRS transmission and a MCS based on a value reported by the receiving device (e.g., a CQI and / or RI reported via CSI) to reduce latency associated with identifying or determining a MCS using MIRS. In some aspects, reducing latency can be based on the (dynamic) gap (from the reported uncertainty value and the reported CQI / RI estimate) being less than a (static) gap or offset (based on the reported CQI / RI estimate) such that a number of failed transmissions and associated time due to intentionally using a too high MCS for a first transmission is reduced for MIRS.

[0026] While both the (static) gap or offset and the (dynamic) gap or offset can be based on a maximum expected difference between an MCS value based on a set of measured values (e.g., values included in CSI) and an optimal (or highest) MCS, the (dynamic) gap or offset can be associated with a smaller maximum expected difference based on additional information provided by the receiving device. For example, a UE can report a (MCS) uncertainty value of "one MCS" such that a base station can determine to use an MCS that is one MCS or MCS index value higher than the reported MCS (e.g., an MCS associated with a reported value in CSI, such as a CQI or RI) for a first transmission of MIRS, rather than a larger number of MCSs (e.g., three MCSs or MCS index values, as described above). Thus, an optimal MCS or code rate can be identified with reduced latency when using MIRS with (MCS) uncertainty value reporting, while achieving the same optimized MCS or code rate, as compared to latency associated with using MIRS without (MCS) uncertainty value reporting.

[0027] When applied to OLLA, an uncertainty value can provide a transmitting device (e.g., a network node or base station) with additional information that can improve selection of an MCS for a subsequent transmission. For example, knowing that a reported value of a performance metric used to determine an MCS has an associated uncertainty of a first magnitude (e.g., greater or less than an assumed magnitude) can allow the transmitting device to increase the MCS (and associated throughput) for a subsequent transmission beyond what can have been selected based on the reported value of the performance metric without the additional information.

[0028] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by reporting at least one uncertainty value associated with at least one performance metric, the described techniques can be used to increase throughput associated with one of OLLA or MIRS. Additionally, for MIRS, reporting of uncertainty values can improve latency associated with identifying (or converging to) an optimized MCS (e.g., code rate and constellation) and throughput.

[0029] The detailed description set forth below, in connection with the appended drawings, is a description of various configurations and does not represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form, in order to avoid obscuring such concepts.

[0030] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented with electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0031] By way of example, an element, or any portion of an element, or any combination of elements can be implemented as a "processing system" that includes one or more processors. A processor can be a microprocessor, microcontroller, graphics processing unit (GPU), central processing unit (CPU), application processor, digital signal processor (DSP), reduced instruction set computing (RISC) processor, system on a chip (SoC), baseband processor, field programmable gate array (FPGA), programmable logic device (PLD), state machine, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system can execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination of them deemed useful by one of ordinary skill in the art, regardless of the particular computer-readable media on which the software can reside and / or be executed.

[0032] Thus, in one or more example aspects, implementations, and / or use cases, the described functions can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0033] While aspects, implementations and / or use cases described herein can be described in the context of 5G NR technology, aspects, implementations and / or use cases described herein can be applicable to any suitable wireless communication system. For example, the concepts described herein can be applicable to various other wireless communication systems, such as a 5G NR-U (unlicensed), 5G NR-Uu (un-terrestrial), 6G, and / or the like. Although aspects, implementations and / or use cases described herein can be described in the context of some examples, additional or different aspects, implementations and / or use cases can be generated in many different ways. The aspects, implementations and / or use cases described herein can be implemented across many different platforms, devices, systems, shapes, sizes and packaging arrangements. For example, aspects, implementations and / or use cases can be realized in integrated chip implementations 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 (AI)-enabled devices, and / or the like). Although some examples can or can not be specifically directed to use cases or applications, a wide range of applicability of the described examples can result. The aspects, implementations and / or use cases can range in scope across chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more technologies described herein. In some physical settings, devices incorporating aspects and features described can also include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals necessarily includes a variety of components, hardware, and software, for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, and / or the like). A variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, and / or the like of various sizes, shapes, and constitutions can practice the technologies described herein.

[0034] Deployment of communication systems, such as 5G NR systems, can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, network entity, mobility element of a network, radio access network (RAN) node, core network node, network element, or network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functionality, can be implemented in an aggregated or disaggregated architecture. For example, a BS, such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmission reception point (TRP), or a cell, and / or the like, can be implemented as an aggregated base station (also referred to as a standalone BS or a monolithic BS) or a disaggregated base station.

[0035] A disaggregated base station can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station can be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DUs can be implemented to be in communication with one or more RUs. Each of the CU, DU, and RU can be implemented as virtual units, a virtual central unit (VCU), virtual distributed unit (VDU), or virtual radio unit (VRU).

[0036] Base station operations or network designs can take into account the disaggregated nature of base station functionality. For example, a disaggregated base station can be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also referred to as a cloud radio access network (C-RAN)). Disaggregation can include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which can enable flexibility in network design. The various units of a disaggregated base station or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0037] Figure 1 is a diagram 100 illustrating examples of wireless communication systems and access networks. The illustrated wireless communication systems include a disaggregated base station architecture. The disaggregated base station architecture can include one or more CUs 110 that can communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CUs 110 can communicate with one or more DUs 130 via respective fronthaul links, such as Fl interfaces. The DUs 130 can communicate with one or more RUs 140 via respective front-haul links. The RUs 140 can communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 can be simultaneously served by multiple RUs 140.

[0038] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) can include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include wired interfaces configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Additionally, the units can include wireless interfaces that can include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive or transmit signals to one or more of the other units over a wireless transmission medium, or both.

[0039] In some aspects, CU 110 can host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by CU 110. CU 110 can be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can bi-directionally communicate with CU-CP units via an interface, such as an El interface. CU 110 can be implemented to communicate with DU 130 as needed for network control and signaling.

[0040] DU 130 can correspond to a logical unit that includes one or more base station functions for controlling operation of one or more RUs 140. In some aspects, DU 130 can host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) in accordance with a functional split, such as those defined by 3GPP. In some aspects, DU 130 can further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0041] Lower layer functionality can be implemented by one or more RUs 140. In some deployments, RUs 140 controlled by a DU 130 can correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among others) or both based at least in part on a functional split, such as a lower layer functional split. In such an architecture, RUs 140 can be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of communicating with the control and user planes of RUs 140 can be controlled by a corresponding DU 130. In some scenarios, this configuration can enable DUs 130 and CUs 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0042] The SMO framework 105 can be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 can be configured to support deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface, such as an Ol interface. For virtualized network elements, the SMO framework 105 can be configured to interact with a cloud computing platform, such as an Open Cloud (O-Cloud) 190 to perform network element lifecycle management, such as to instantiate a virtualized network element, via a cloud computing platform interface, such as an 02 interface. Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140, and near-RT RICs 125. In some implementations, the SMO framework 105 can communicate with hardware aspects of a 4G RAN, such as an Open eNB (O-eNB) 111, via an Ol interface. Additionally, in some implementations, the SMO framework 105 can communicate directly with one or more RUs 140 via an Ol interface. The SMO framework 105 can also include a non-RT RIC 115 configured to support functionality of the SMO framework 105.

[0043] The non-RT RIC 115 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based steering of applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to, or in communication with, the near-RT RIC 125, such as via an Al interface. The near-RT RIC 125 can be configured to include logical functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions via an interface, such as via an E2 interface, that connects one or more CUs 110, one or more DUs 130, or both, and an O-eNB with the near-RT RIC 125.

[0044] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 125, the non-RT RIC 115 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 125 and can be received at the SMO framework 105 or the non-RT RIC 115 from non-network data sources or from network functions. In some examples, the non-RT RIC 115 or the near-RT RIC 125 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 can monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions via the SMO framework 105, such as via reconfiguration of Ol, or via creation of RAN management policies, such as Al policies.

[0045] At least one of the CU 110, the DU 130, and the RU 140 can be referred to as a base station 102. Thus, the base station 102 can include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated with a dashed line to represent that each component can or can not be included in the base station 102). The base station 102 provides wireless access to the core network 120 for the UEs 104. A base station 102 can include a macro cell (high power cellular base station) and / or a small cell (low power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network can also include home evolved node Bs (eNBs) (HeNBs), which can provide service to a restricted group known as a closed subscriber group (CSG). The communication links between the RUs 140 and the UEs 104 can include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a RU 140 and / or downlink (DL) (also referred to as forward link) transmissions from a RU 140 to a UE 104. The communication links can use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links can be through one or more carriers, where a carrier can be a set of

[0046] Certain UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 can use the DL / UL WWAN spectrum. The D2D communication link 158 can use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication can be through a variety of wireless D2D communications systems, such as for example, Bluetooth ™ (Bluetooth is a trademark of Bluetooth Special Interest Group (SIG)), Wi-Fi ™ based on Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi is a trademark of Wi-Fi Alliance), LTE, or NR.

[0047] The wireless communications system can also include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs)) via communication links 154, e.g., in 5 GHz unlicensed spectrum, or the like. When communicating in unlicensed spectrum, the UEs 104 / AP 150 can perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

[0048] The electromagnetic spectrum is often subdivided based on frequency / wavelength into various classes, bands, channels, and so forth. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7. 125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Despite a portion of FR1 being greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar naming convention holds for FR2, which is often referred to (interchangeably) as a “millimeter wave” band, despite being different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) which is designated as such by the International Telecommunications Union (ITU).

[0049] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as frequency range designation FR3 (7. 125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend features of FR1 and / or FR2 to mid-band frequencies. Moreover, even higher bands are currently under exploration to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher bands fall within the EHF band.

[0050] With the above in mind, unless specifically stated otherwise, if the term “Sub-6 GHz” or the like is used herein, this can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. Further, unless specifically stated otherwise, if the term “millimeter wave” or the like is used herein, this can broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR2-2, and / or FR5, or can be within the EHF band.

[0051] The base stations 102 and the UEs 104 can each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base stations 102 can transmit to UEs 104 in one or more transmit directions using beamforming. The UEs 104 can receive from the base stations 102 in one or more receive directions using beamforming. The UEs 104 can also transmit to the base stations 102 in one or more transmit directions using beamforming. The base stations 102 can receive from the UEs 104 in one or more receive directions using beamforming. The base station 102 / UE 104 can perform beam training to determine the best receive and transmit directions for each of the base station 102 / UE 104. The transmit and receive directions for the base station 102 can or can not be the same. The transmit and receive directions for the UE 104 can or can not be the same.

[0052] The base stations 102 can include and / or be referred to as gNBs, NodeBs, eNBs, access points, base transceiver stations, radio base stations, radio transceiver, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), TRPs, network nodes, network entities, network equipment, or some other suitable terminology. The base stations 102 can be implemented as integrated access and backhaul (IAB) nodes, relay nodes, sidelink nodes, aggregated (monolithic) base stations with baseband units (BBUs) including CUs and DUs and RUs, or as disaggregated base stations including one or more of CUs, DUs, and / or RUs. A collection of base stations that can include disaggregated and / or aggregated base stations can be referred to as a next generation (NG) RAN (NG-RAN).

[0053] The core network 120 can include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is a control node that handles signaling between the UEs 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 can include one or more location / determination servers, which can include one or more of a GMLC 165, an LMF 166, a positioning determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), and the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute a position of the UE 104. The NG-RAN can utilize one or more positioning methods to determine a position of the UE 104. Positioning the UE 104 can involve signal measurements, position estimation, and optional velocity calculations based on these measurements. The signal measurements can be made by the UE 104 and / or the base stations 102 serving the UE 104. The measured signals can be based on one or more of a satellite positioning system (SPS) 170 (e.g., Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN), or other satellite positioning / location system), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensors, motion sensors), NR Enhanced Cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or other systems / signals / sensors.

[0054] Examples of a UE 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similar functional device. Some of the UEs 104 can be referred to as IoT devices (e.g., a parking meter, gas pump, toaster, vehicle, heart monitor, etc.). The UE 104 can also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE can also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices can collectively or individually access a network.

[0055] Referring again to Figure 1 In certain aspects, the UE 104 can have a MCS uncertainty reporting component 198 that can be configured to identify at least one performance metric associated with channel estimation operations at the UE. The MCS uncertainty reporting component 198 can be further configured to calculate at least one uncertainty value associated with the at least one performance metric. The MCS uncertainty reporting component 198 can also be configured to transmit, to a network node, an indication of the at least one uncertainty value associated with the at least one performance metric. In certain aspects, the base station 102 can have a MCS uncertainty reporting component 199 that can be configured to receive, from a UE, a first indication of at least one uncertainty value associated with at least one performance metric, the at least one performance metric being associated with channel estimation operations at the UE. The MCS uncertainty reporting component 199 can be further configured to receive, from the UE, a second indication of at least one value of the at least one performance metric associated with the at least one uncertainty value. The MCS uncertainty reporting component 199 can also be configured to select a set of parameters for subsequent communications based on the at least one value of the at least one performance metric and the at least one uncertainty value. While the aspects described below can relate to 5G NR, aspects can be applicable to other aspects of wireless communication.

[0056] Figure 2A FIG. 200 is a diagram 200 illustrating an example of a first subframe, which is exemplified within a 5G NR frame structure. Figure 2B FIG. 230 is a diagram 230 illustrating an example of DL channels, which is exemplified within a 5G NR subframe. Figure 2Cis a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure can be frequency division duplexed (FDD) where particular subcarrier sets (carrier system bandwidths) are dedicated for DL or UL, or can be time division duplexed (TDD) where the same subcarrier set is used for DL and UL with scheduling. In the examples provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible to use between DL / UL, and subframe 3 is configured with slot format 1 (with all UL). While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with a slot format (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the following description also applies for 5G NR frame structures that are TDD. Figure 2A , Figure 2C In the examples provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible to use between DL / UL, and subframe 3 is configured with slot format 1 (with all UL). While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with a slot format (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the following description also applies for 5G NR frame structures that are TDD.

[0057] Figures 2A-2D A frame structure is illustrated, and aspects of the disclosure can be applicable to other wireless communication technologies that can have different frame structures and / or different channels. One frame (10 ms) can be divided into 10 equally sized subframes (1 ms). Each subframe can include one or more slots. A subframe can also include mini-slots, which can contain 7, 4, or 2 symbols. Each slot can include 14 or 12 symbols, depending on whether a cyclic prefix (CP) is normal or extended. For a normal CP, each slot can contain 14 symbols, and for an extended CP, each slot can contain 12 symbols. Symbols on the DL can be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power limited scenarios; limited to single stream transmission). The number of slots within a subframe is dependent on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can scale with 1 / SCS.

[0058]

[0059] Table 1: Parameter sets, SCS, and CP

[0060] For normal CP (14 symbols / slot), different numerologies µ 0 to 4 allow for 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, numerology 2 allows for 4 slots per subframe. Thus, for normal CP and numerology µ, there are 14 symbols / slot and 2 µ slots / subframe. The subcarrier spacing can equal , where is the numerology 0 to 4. Thus, the subcarrier spacing for numerology µ = 0 is 15 kHz, and the subcarrier spacing for numerology µ = 4 is 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D An example is provided for normal CP with 14 symbols per slot and numerology µ = 2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μβ. Within a frame collection, there can be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 2B ). Each BWP can have a particular numerology and CP (normal or extended).

[0061] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as a physical RB (PRB)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0062] As illustrated in Figure 2A , some of the REs carry reference (pilot) signals (RS) for the UE. The RS can include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0063] Figure 2BExamples of various DL channels are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP can be referred to as a control resource set (CORESET). A UE is configured to monitor PDCCH search space (e.g., common search space, UE-specific search space) for PDCCH candidates during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies of the channel bandwidth. A primary synchronization signal (PSS) can be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe / symbol timing and physical layer identity. A secondary synchronization signal (SSS) can be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as SS block (SSB)). The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information (such as system information blocks (SIBs)), and paging messages.

[0064] As Figure 2C illustrated, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for channel estimation at the base station. The UE can transmit DM-RS for the physical uplink control channel (PUCCH) and the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be transmitted in the first one or two symbols of a PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether short or long PUCCH is transmitted and depending on the particular PUCCH format used. The UE can transmit a sounding reference signal (SRS). The SRS can be transmitted in the last symbol(s) of a subframe. The SRS can have a comb-2 structure, and a UE can transmit SRS on one of the combs. The SRS can be used by a base station for channel quality estimation to enable frequency-dependent scheduling for the UL.

[0065] Figure 2DExamples of various UL channels within a subframe are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data, and can additionally be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0066] Figure 3 is a block diagram of the components of base station 310 and UE 350, which can be used in implementing the techniques described in this disclosure. At the base station 310, a transmit processor 320 can receive data from a data source 312 and control information from a controller / processor 340. The transmit processor 320 can process (e.g., encode and modulate) the data and control information to generate data symbols and control symbols, which can be precoded by a TX MIMO processor 322 if applicable, further processed by a modulator 324, and transmitted to the UE 350 via the antennas 326. At the UE 350, the antennas 354 can receive the transmitted signals, and the signals can be processed by a demodulator 356 to generate processed signals. A receive processor 358 can then process the processed signals to obtain data and control information, which can be provided to a data sink 360 and the controller / processor 359, respectively. The controller / processor 359 can include a processor 359 and memory 359, and can be used to implement the techniques described in this disclosure.

[0067] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, can include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams if multiple spatial streams are used. Channel estimates from a channel estimator 374 can be used to determine the beamforming

[0068] At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions can be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0069] The controller / processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 can be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the core network. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0070] Similar to the functionality described in connection with the DL transmission by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0071] The TX processor 368 can use channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 can be provided to different antenna 352 via separate transmitters 354. Each transmitter 354 can modulate an RF carrier with a respective spatial stream for transmission.

[0072] The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318 receives a signal through its respective antenna 320. Each receiver 318 recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0073] The controller / processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 can be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the core network. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0074] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 can be configured to perform aspects in connection with Figure 1 the MCS uncertainty reporting component 198.

[0075] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 can be configured to perform aspects in connection with Figure 1 the MCS uncertainty reporting component 199.

[0076] In some aspects of wireless communication (e.g., 5G NR), rate adaptation schemes are described that close (or narrow) the gap between optimal link adaptation and current CSI-RS based link adaptation. Current CSI-RS based channel capacity tracking schemes can fail to adapt to the instantaneous optimal MCS (e.g., the highest MCS that can be successfully decoded over a particular transmission time interval (TTI)). For example, current schemes can not utilize the full available channel capacity because, among other things, CSI-RS estimates are not perfect and generally do not accurately model the performance of a receiver, and channel conditions can change significantly between discrete times (e.g., slots that include CSI-RS, which can be referred to as CSI-RS slots), even at low speeds (e.g., for slowly moving wireless devices or UEs), the optimal MCS (and coding rate) can change significantly between these CSI-RS slots.

[0077] In a CSI-RS based channel capacity tracking scheme, the MCS (specifically, the coding rate) used can be set on a first transmission and can not be dynamically adapted. Thus, if the first transmission fails, approximately the same number of coded bits can be retransmitted without adjusting the number of coded bits based on the failure of the first transmission. Retransmission schemes associated with CSI-RS based channel capacity tracking schemes can use a small set of redundancy versions (RVs) to select bits for retransmission. These bits are either the same coded bits as the first transmission (e.g., for Chase combining), which results in the same code rate, or new coded bits (e.g., for incremental redundancy), which can result in a halving of the effective coding rate in the second retransmission.

[0078] Thus, when using a CSI-RS based channel capacity tracking scheme, the coding rate (or MCS) used for the first transmission should be carefully selected. For example, an overestimated rate can result in decoding errors and can result in a loss of throughput, and an underestimated rate can result in a loss of throughput compared to a larger payload that can have been transmitted over the same channel resources using an accurately estimated rate (or MCS).

[0079] In some aspects, link adaptation between CSI-RSs can be done using OLLA, but it can not accurately track optimal MCS changes. Thus, even with optimal CSI estimation where the MCS is optimally selected on the CSI slot, and regardless of whether OLLA is used, the throughput performance is far from the achievable performance of optimal per-slot MCS selection.

[0080] MIRS is a scheme that can close (or reduce) the gap to optimal MCS selection and achieve communication at (or close to) the capacity code rate regardless of mobility. In some aspects, MIRS can include using an overestimated MCS for a first transmission to ensure that throughput is not lost due to an underestimated rate. Fine-scale adaptation of the code rate can be based on small-size retransmissions using receiver-based ACK / NACK feedback (e.g., incremental redundancy (IR)-HARQ). For example, each time a receiver (e.g., a wireless device or UE that receives a transmission associated with MIRS) transmits a NACK (or alternatively, does not transmit an ACK), a small amount of additional redundancy bits can be transmitted. In some aspects, MIRS can use per-CB feedback to further maximize channel utilization.

[0081] Using per-CB feedback can include (e.g., at a transmitting device, such as a network node or base station) selecting an MCS for a first transmission that is expected to fail. This selection can determine the coding parameters (e.g., rate, TBS, etc.) for retransmissions of the failed transmission. For each decoding failure, the receiver transmits feedback with the per-CB decoding results. In some aspects, the receiver can convey additional information to allow the transmitter to converge to the optimized rate faster (e.g., with lower latency). Based on the reported failures (e.g., failures to decode a TB or CB), the transmitter can schedule and transmit a small number of additional bits (parity or redundancy bits) for the failed TB (or for the failed CB) compared to the initial coded bit buffer for the CB. The added bits in the retransmission set can then be used to reduce the effective code rate for each CB in fine steps until all CBs (and thus the entire TB) are successfully decoded. The total number of bits transmitted on the first transmission and subsequent transmissions is associated with (or can be used to calculate) the actual rate for each TB. Thus, using MIRS, the gap between the optimal MCS (instantaneous or per-slot, per-CB, or per-RB group) can be closed (or reduced) over a large SNR range by closely tracking channel variations to achieve higher throughput compared to a CSI-RS-based channel capacity tracking scheme.

[0082] In some aspects of wireless communications, MIRS can be used to dynamically adjust one or more of rate, precoding, and / or rank based on multiple IR-HARQs as described above. In some aspects, a first transmission associated with MIRS can use a higher MCS than the MCS reported (or indicated) in the CSI and can rely on multiple retransmissions to pass the CRC of the TB or CB as described above. A transmitting device (e.g., a base station or network node) can determine a first higher MCS for the first transmission according to a pre-defined (static) gap and / or (static) LUT (e.g., a MCS associated with a MCS index value that is three greater than the reported MCS index value). However, due to the multiple retransmissions expected based on using the first (significantly) higher MCS, the above-described solution using a static offset from the reported MCS can be associated with a larger latency per CB.

[0083] Various aspects of the present disclosure generally relate to improvements to MIRS (or OLLA) that involve transmitting an uncertainty report (e.g., based on MCS estimation capabilities of the receiving device, channel conditions, Doppler effects, interference, SINR, etc.) associated with the MCS indicated by the receiving device from the receiving device. For example, in some aspects of the present disclosure, a receiving device (e.g., a wireless device or UE) can report an indication of uncertainty associated with a CQI (or RI) estimate (e.g., an uncertainty report) to a transmitting device (e.g., a base station or network node), which the transmitting device can use to determine a (dynamic) gap (or offset) between a second higher MCS used for a first MIRS transmission and a MCS based on a value reported by the receiving device (e.g., a CQI and / or RI via a CSI report) to reduce latency associated with identifying or determining a MCS using MIRS. In some aspects, an uncertainty value can indicate an expected accuracy (or inaccuracy) of a corresponding value of a particular performance metric or channel characteristic (e.g., a value reported in a CSI or a value computed based on one or more values reported in a CSI). In some aspects, an uncertainty value can be indicated according to a corresponding value (e.g., for a reported CQI index, an uncertainty value can be reported according to the CQI index) and can indicate a maximum value and / or a minimum value, which can be an accurate value (e.g., an actual value or an optimal value) associated with a particular performance metric or channel characteristic. In some aspects, reducing latency can be based on the (dynamic) gap (based on the reported uncertainty value and the reported CQI / RI estimate) being less than the (static) gap or offset (based on the reported CQI / RI estimate) such that the number and associated time of failed transmissions due to intentionally using a too-high MCS for the first transmission is reduced for MIRS.

[0084] While both the (static) gap or offset and the (dynamic) gap or offset can be based on a maximum expected difference between an MCS value based on a set of measured values (e.g., values included in CSI) and an optimal (or highest) MCS, the (dynamic) gap or offset can be associated with a smaller maximum expected difference based on additional information provided by the receiving device. For example, a UE can report an MCS uncertainty value of "one MCS" such that a base station can determine to use an MCS that is one MCS or MCS index value higher than the reported MCS (e.g., an MCS associated with a value reported in or associated with CSI, such as a CQI, an RI, a SINR, a reference signal received power (RSRP), a received signal strength indicator (RSSI), etc.) for a first transmission of MIRS, rather than a larger number of MCSs (e.g., three MCSs or MCS index values, as described above). Thus, an optimal MCS can be identified with reduced latency when using MIRS with an MCS uncertainty value, as compared to latency associated with using MIRS without an MCS uncertainty value, without impacting performance (e.g., reaching the same optimal MCS or code rate).

[0085] When applied to OLLA, an uncertainty value can provide a transmitting device (e.g., a network node or base station) with additional information that can improve selection of an MCS for a subsequent transmission. For example, knowing that a reported value of a performance metric (e.g., a measured channel characteristic that can be associated with a throughput or other characteristic associated with communication between a transmitting device and a receiving device) used to determine an MCS has an associated uncertainty of a first magnitude (e.g., greater than or less than an assumed magnitude) can allow the transmitting device to increase an MCS (and associated throughput) for a subsequent transmission beyond what can have been selected based on the reported value of the performance metric without the additional information.

[0086] Figure 4 is a diagram illustrating an example 400 associated with MIRS in accordance with one or more aspects of the present disclosure. Figure 4 Initial messages 405 and retransmissions 410, 415, and 420 of a communication are depicted. For example, the communication can be transmitted by a transmitter device, such as a network node (e.g., a base station 502 in Figure 5 may be received by a receiver device, such as a UE (e.g., a UE 504 in Figure 5 may be received by a receiver device, such as a UE (e.g., a UE 504 in

[0087] For example, as Figure 4As shown, the initial message 405 can include a TB including a payload (e.g., information bits or systematic bits) and one or more redundancy (parity) bits. The initial transmission can use a first code rate and / or a first MCS. The first code rate and / or the first MCS can be overestimated (e.g., for the channel) and / or can be a highest available or configured code rate and / or MCS. Alternatively or additionally, the first code rate and / or the first MCS can be based on a known gap / offset (e.g., one of a preconfigured / predefined gap / offset or a LUT-based gap / offset) from MCS values reported by the receiver device (e.g., via CSI). In some aspects that implement uncertainty value reporting from the receiver device, the first code rate and / or the first MCS can be further based on an uncertainty value reported by the receiver device, as further described below.

[0088] The first retransmission 410 can include a plurality of additional (redundancy / parity) coding bits (e.g., from a set of bits associated with the TB). For example, the receiver device can be unable to successfully decode the TB using the initial message 405. Accordingly, the transmitter device can schedule and / or transmit the first retransmission 410 to incrementally and efficiently reduce the code rate and / or MCS used for the communication. The plurality of additional coding bits included in the first retransmission 410 can reduce the effective code rate and / or MCS used for the communication to a second code rate and / or a second MCS.

[0089] The second retransmission 415 can include a plurality of additional (redundancy / parity) coding bits (e.g., from a set of bits associated with the TB). For example, the receiver device can be unable to successfully decode the TB using the initial message 405 and the first retransmission 410. Accordingly, the transmitter device can schedule and / or transmit the second retransmission 415 to incrementally and efficiently reduce the code rate and / or MCS used for the communication. The plurality of additional coding bits included in the second retransmission 415 can reduce the effective code rate and / or MCS used for the communication to a third code rate and / or a third MCS.

[0090] The third retransmission 420 can include a plurality of additional (redundancy / parity) coding bits (e.g., from a set of bits associated with the TB). For example, the receiver device can be unable to successfully decode the TB using the initial message 405, the first retransmission 410, and the second retransmission 415. Accordingly, the transmitter device can schedule and / or transmit the third retransmission 420 to incrementally and efficiently reduce the code rate and / or MCS used for the communication. The plurality of additional coding bits included in the third retransmission 420 can reduce the effective code rate and / or MCS used for the communication to a third code rate and / or a third MCS.

[0091] Accordingly, the transmitter device can be enabled to incrementally decrease the effective code rate used for the communication using the retransmissions 410, 415, and 420. For example, if the receiver device is enabled to successfully decode the communication (e.g., the entire TB) after the third retransmission is transmitted, the effective code rate used for the communication (e.g., for the TB) can be based at least in part on the number of coded bits transmitted in the initial message 405, the first retransmission 410, the second retransmission 415, and the third retransmission 420. It will be appreciated that Figure 4 The number of retransmissions illustrated in FIG. 5 is exemplary and does not limit the present disclosure. The transmitter device can transmit fewer or more than three retransmissions in order for the receiver device to successfully decode the entire communication. The transmitter device can continue to provide retransmissions until the receiver device has successfully decoded the entire communication (e.g., when the CRC passes). Accordingly, the transmitter device can stop further retransmissions when ACK feedback is received from the receiver device, where the ACK feedback can indicate that the receiver device has successfully decoded the communication.

[0092] The initial message 405, the first retransmission 410, the second retransmission 415, and the third retransmission 420 can be transmitted in different time windows (e.g., in different slots). For example, the transmitter device can transmit the initial message 405 in a first slot. The transmitter device can transmit the first retransmission 410 in a second slot (e.g., can transmit the additional bits for the first retransmission 410 indicated in Figure 4 The transmitter device can transmit the second retransmission 415 in a third slot (e.g., can transmit the additional bits for the second retransmission 415 indicated in Figure 4 The transmitter device can transmit the third retransmission 420 in a fourth slot (e.g., can transmit the additional bits for the third retransmission 420 indicated in Figure 4 The transmitter device can transmit the third retransmission 420 in a fourth slot (e.g., can transmit the additional bits for the third retransmission 420 indicated in Figure 4 not shown in FIG. 5).

[0093] Figure 5 is a call flow diagram 500 illustrating the use of a reported MCS uncertainty value in association with MIRS in accordance with some aspects of the present disclosure. In some aspects, the MIRS can be associated with a communication between a base station 502 and a UE 504. In some aspects, the functions attributed to the base station 502 can be performed by a network node or network device, such as described above with respect to FIG. 1. Figure 1one or more components of the wireless device that support communication with the network devices / nodes and MIRS. Accordingly, references in the following description to “sending” can be understood to refer to a first component of the base station 502 or UE 504 outputting (or providing) an indication of the contents of the transmission to be sent by a different component of the base station 502 or UE 504. Similarly, references in the following description to “receiving” can be understood to refer to a first component of the base station 502 or UE 504 receiving a transmitted signal and outputting (or providing) the received signal (or information based on the received signal) to a different component of the base station 502 or UE 504.

[0094] As part of establishing a connection between the base station 502 and UE 504 at 506, in some aspects, the base station 502 can transmit an uncertainty reporting configuration 508 and the UE 504 can receive the uncertainty reporting configuration. In some aspects, the uncertainty reporting configuration 508 can be transmitted via a RRC message or a MAC-CE (or other similar layer 3 or layer 2 messaging, as appropriate). For example, the uncertainty reporting configuration 508 can be transmitted / received as part of establishing a connection between the base station 502 and UE 504 to configure reporting of uncertainty values. Additionally, or alternatively, in some aspects, the uncertainty reporting configuration 508 or an updated uncertainty reporting configuration 532 can be transmitted if there are certain changes at one of the base station 502 or UE 504 after a connection has been established (e.g., based on a trigger or triggering event). In some aspects, the uncertainty reporting configuration 508 can include a set of parameters associated with transmitting, from the UE 504, an indication of at least one uncertainty value associated with a MIRS (or OLLA), as described below.

[0095] In some aspects, the set of parameters can indicate a first subset of parameters associated with capabilities of the network node and a second subset of parameters associated with a format for an indication of an uncertainty value. For example, the base station 502 can indicate, via the uncertainty reporting configuration 508 (and set of parameters), a maximum number of retransmissions supported by the base station 502, a retransmission granularity (e.g., a retransmission unit, such as one of a CB, multiple CBs, a RB, multiple RBs, a TB, etc.), and a retransmission applicable size (e.g., a size associated with a retransmission, which in some aspects can be based on a MCS LUT). The uncertainty reporting configuration 508 (and set of parameters) can additionally or alternatively indicate a support for uncertainty value reporting, a set of performance metrics for which to provide an indication of associated uncertainty, a granularity of frequency resources associated with uncertainty value reporting (e.g., a frequency unit for which the base station 502 supports a change in code rate, such as a subcarrier, a RB including 12 subcarriers, or a subband including multiple RBs within a wideband transmission), and a duration associated with MIRS (e.g., a threshold time for a refresh or for a timeout associated with MIRS). In some aspects, the uncertainty reporting configuration 508 (and set of parameters) can additionally or alternatively indicate other configuration parameters related to a rank, a PDSCH occupancy value (e.g., how many frequency resources a PDSCH communication overlaps with a CSI-RS, where a larger occupancy value can reduce resources at the UE 504 for channel quality estimation and an associated accuracy of channel quality estimation), a frequency band, a carrier, a beam direction, an SSB, a constellation associated with uncertainty reporting (e.g., QPSK, 16QAM, etc.) (e.g., the uncertainty reporting configuration 508 can indicate to transmit an uncertainty value for each of a plurality of ranks, PDSCH occupancy values, frequency bands, and constellations). In some aspects, the uncertainty reporting configuration 508 can also include one or more lists of indices, LUTs, or other indicated or preconfigured information for indicating uncertainty values from the UE 504 to the base station 502, or associated therewith.

[0096] In some aspects that do not support MIRS, the uncertainty reporting configuration 508 can represent a configuration for uncertainty reporting related to OLLA, and can omit some of the parameters discussed above as they can not be relevant to OLLA. For example, in addition to MIRS-specific configuration parameters omitted due to not supporting MIRS, when OLLA is used to determine a single MCS applied to a frequency across a wideband (e.g., a complete set of frequencies used for a particular connection or communication), the uncertainty reporting configuration 508 can not indicate a granularity of frequency resources associated with uncertainty value reporting, as a single uncertainty value can be applied to determine a single MCS.

[0097] At 510, the UE 504 can identify (or determine) at least one performance metric associated with the channel estimation operations at the UE 504. In some aspects, the at least one performance metric can be one or more of a CQI, a RI, or other performance metric associated with the determination of an optimal MCS. In some aspects, the at least one performance metric can be identified (or determined) based on the uncertainty reporting configuration 508.

[0098] In some aspects, the UE 504 can determine (or compute) at least one uncertainty value at 512 that is not based on measured channel conditions. The at least one uncertainty value can include an uncertainty value associated with a computed MCS for each supported rank at the UE 504. In some aspects, the at least one uncertainty value can include a plurality of uncertainty values including an uncertainty value for each MCS for each supported rank, such that when provided to the base station 502, the base station 502 can store the plurality of uncertainty values for later use to reduce overhead and / or as a baseline uncertainty for a given MCS / rank combination. While discussed with respect to MCS uncertainty values, in some aspects, the uncertainty values discussed below can include uncertainty values associated with CQI, RI, or other components of CSI. In some aspects, the uncertainty values are associated with components of CSI used to determine an MCS for MIRS and / or OLLA based on which of MIRS and / or OLLA is implemented by the base station 502 and / or the UE 504.

[0099] Based on the uncertainty reporting configuration 508 or other message from the base station 502, the units associated with the at least one uncertainty value determined (or computed) at 512 can be known (or preconfigured) units or can be associated with a requested (e.g., configured) attribute or parameter. For example, the at least one uncertainty value can be a requested unit associated with a MCS related unit (e.g., a MCS index value), a code rate, or another known or requested parameter associated or related. In some aspects, the at least one uncertainty value determined (or computed) at 512 can be an index value into a known or configured list of indices, a codebook, or a LUT (e.g., stored information that can be referenced to reduce overhead associated with uncertainty value reporting or indication).

[0100] In some aspects, the at least one uncertainty value can include a plurality of uncertainty values, each corresponding to one of the plurality of carrier frequencies, frequency bands, beam directions, and / or detected SSBs. For example, in some aspects, an uncertainty value can be determined (or computed) at 512 per carrier frequency, per frequency band, per beam direction, per detected SSB, and / or for each of the one or more parameters associated with the CSI (e.g., for each CQI value reported in the CSI). In some aspects, per carrier frequency, per frequency band, per beam direction, and / or per detected SSB can be based on a predicted uncertainty value associated with each carrier frequency, frequency band, beam direction, and / or detected SSB, where the prediction can be based on previous measurements made by the UE 504 and / or based on a (statistical) model / simulation of uncertainty values for carrier frequencies, frequency bands, beam directions, and / or detected SSBs.

[0101] In some aspects, the at least one uncertainty value can be determined (or computed) at 512 based on available hardware resources at the UE 504. As described above, a plurality of uncertainty values can be determined (or computed) at 512 for a plurality of corresponding amounts of available resources. The amount of available resources can be indicated based on (modem) occupancy of the related PDSCH transmissions, or related to (modem) occupancy of the related PDSCH transmissions. For example, each of the plurality of uncertainty values can be associated with one or more threshold numbers of RBs associated with PDSCH transmissions transmitted via a same, overlapping, or adjacent set of time resources, where the allocation of CSI-RS resources can be increased or decreased based on the allocation of PDSCH resources. For example, a first uncertainty value can be associated with related PDSCH transmissions occupying 0 to N-1 RBs, and a second uncertainty value can be associated with related PDSCH transmissions occupying N to 2N-1 RBs (e.g., where the value of N and the total number of uncertainty values can be based on a total number of hardware resources available for decoding at the UE 504). For a CSI-RS transmitted at a same / overlapping / adjacent time as a PDSCH occupying ‘M’ RBs, the base station 502 can use the at least one uncertainty value associated with the related PDSCH transmissions occupying M RBs in determining the MCS for a subsequent transmission in addition to the reported value of the performance metric of the transmitted CSI-RS (e.g., the CQI or RI reported in the CSI).

[0102] In some aspects, at least one uncertainty value can be determined (or computed) at 512 for a plurality of modulation constellations, schemes, or orders (e.g., QPSK, 16QAM, 64QAM, etc.). In some aspects, a plurality of values can be determined for a plurality of modulation constellations / schemes / orders, as uncertainty can change across modulation boundaries. For example, a first number of MCS indexes can be determined for an uncertainty value associated with a first modulation constellation / scheme / order, while a second number of MCS indexes can be determined for an uncertainty value associated with a second modulation constellation / scheme / order, such that for a MCS determined based on a reported performance metric (e.g., a CQI, RI, SINR, RSRP, RSSI in or associated with a CSI) that is close to a transition from an MCS index associated with a first modulation order to an MCS index associated with a second modulation order, the base station can use a second uncertainty value to determine a MCS offset to use (and a MCS to use for a first transmission of a MIRS).

[0103] Based on the at least one uncertainty value determined at 512, the UE 504 can transmit a first indication of one or more MCS uncertainty values 514, and the base station 502 can receive the first indication. In some aspects, the first indication of one or more MCS uncertainty values 514 can include an indication of at least one uncertainty value associated with the at least one performance metric computed at 512. Thus, the first indication of one or more MCS uncertainty values 514 can include any of the uncertainty values discussed with respect to the computation of the at least one uncertainty value at 512 (e.g., any of the one or more uncertainty values associated with different parameter values or resources). In some aspects, the first indication of one or more MCS uncertainty values 514 can be transmitted for use in association with a MIRS or for use in association with an OLLA in the absence of support for a MIRS. In some aspects, the first indication of one or more MCS uncertainty values 514 can be transmitted via a RRC message or a MAC-CE (or other similar layer 3 or layer 2 messaging, as appropriate). In some aspects, the first indication of one or more MCS uncertainty values 514 can be sufficient to provide a benefit without reporting additional uncertainty values based on channel conditions or channel measurements (e.g., a second indication of one or more MCS uncertainty values 524 as described below).

[0104] In some aspects, after establishing the connection at 506, the base station 502 can transmit one or more CSI-RSs 516, and the UE 504 can receive and measure the one or more CSI-RSs at 518 as part of a channel estimation operation. In some aspects, the one or more CSI-RSs 516 can include or be associated with an indication of an uncertainty report or a request for an uncertainty report (e.g., an indication of one or more uncertainty values). The indication / request included in or associated with the one or more CSI-RSs 516 can indicate that the UE 504 is to transmit an updated uncertainty report (e.g., an updated indication of one or more previously reported uncertainty values). In some aspects, the one or more CSI-RSs 516 can include or be associated with an indication of PDSCH occupation associated with at least one of the one or more CSI-RSs 516. For example, if a PDSCH transmission occasion with little or no associated data is to overlap with a set of time resources associated with the at least one CSI-RS, the base station 502 can indicate to the UE 504 to dedicate additional resources to decoding the at least one CSI-RS to reduce an uncertainty value associated with channel estimation based on the at least one CSI-RS.

[0105] Based on measuring the one or more CSI-RSs 516 at 518, the UE 504 can calculate (or determine) one or more uncertainty values associated with the at least one performance metric identified at 510 at 520. The one or more uncertainty values can be associated with an MCS, a CQI, or an RI. In some aspects, calculating the one or more uncertainty values at 520 can be based on one or more of available resources (e.g., hardware resources) at the UE 504 and / or a configuration / request from the base station 502, as discussed above with respect to the uncertainty report configuration 508 and / or the CSI-RSs 516. In some aspects, as part of measuring the one or more CSI-RSs 516 at 518, or as part of calculating the one or more uncertainty values at 520, the UE 504 can identify (or determine / calculate) values associated with the identified performance metrics (e.g., a recommended MCS, a CQI to include in CSI, and / or an RI to include in CSI).

[0106] In some aspects, the calculation at 520 can be based on a (pre-trained) LUT or other stored data or information based on a number of channel models, Doppler velocities, interference scenarios, etc. In some aspects, the calculation of the one or more uncertainty values at 520 can be based on running a full modem with data self-generation and adding noise based on the estimated SINR. In some aspects, the calculation of the one or more uncertainty values at 520 can be based on a rank associated with the identified (or determined / calculated) RI or a last layer number according to a PDSCH received.

[0107] After calculating the one or more uncertainty values at 520 (and / or identifying values associated with the identified performance metrics at 518 or 520), the UE 504 can transmit, and the base station 502 can receive, a CSI 522 including one or more of a CQI or an RI based on the one or more CSI-RSs 516. In some aspects, the CSI 522 can be transmitted using a format that can also be used without additional reporting of the one or more uncertainty values. In some aspects, the CSI 522 can be transmitted using a format that can include additional information related to uncertainty value reporting, such as a 1-bit indicator indicating that the uncertainty values have not changed and the UE will not transmit an uncertainty value report or that the uncertainty values have changed and the UE will transmit an uncertainty value report. In some aspects, the uncertainty value report associated with the CSI 522 can include an indication of one or more differences from one of an original (or baseline) uncertainty value report (e.g., the uncertainty values reported during connection setup, such as the first indication of one or more MCS uncertainty values 514) or an immediately preceding reported uncertainty value (e.g., an increment or offset for each of the one or more uncertainty values indicated in the one of). For example, if the CSI 522 includes an indication that the calculated one or more uncertainty values have changed from a last-reported (or baseline) set of one or more uncertainty values, the base station 502 can receive an uncertainty value report that can include a set of one or more associated (e.g., subsequently reported) uncertainty values that are interpreted as a change to the set of one or more previously reported uncertainty values. Alternatively, if the CSI 522 includes an indication that the calculated one or more uncertainty values have not changed from a last-reported (or baseline) set of one or more uncertainty values, the UE 504 can not transmit the second indication of one or more MCS uncertainty values 524, and the base station 502 can not receive (and / or monitor for) the second indication, and the base station 502 can use the previously reported (or baseline) uncertainty values.

[0108] The UE 504 can additionally transmit a second indication 524 of one or more MCS uncertainty values, e.g., in association with the MIRS, and the base station 502 can receive the second indication. In some aspects, the UE 504 can transmit the second indication 524 of one or more MCS uncertainty values based on one or more of a trigger or request from the base station 502, e.g., a request included in or associated with the one or more CSI-RSs 516. In some aspects, the trigger can be associated with one or more of a change of serving beam (e.g., during a handover) or a change in the calculated MCS uncertainty values from previously reported MCS uncertainty values. As described above, the second indication 524 of one or more MCS uncertainty values can include uncertainty values per TB, CB, rank, frequency unit, or other characteristic / parameter (e.g., as indicated in the uncertainty reporting configuration 508) for MCS, CQI, and / or RI.

[0109] In some aspects, the base station 502 can determine, at 526, a MCS (and / or rank) for a PDSCH transmission (e.g., a first transmission associated with the MIRS) based on the CSI 522, the first indication 514 of one or more MCS uncertainty values, and / or the second indication 524 of one or more MCS uncertainty values. In some aspects, the determination at 526 can be further based on a time offset (e.g., a time distance) from a CSI-RS used to determine the MCS for the PDSCH transmission. For example, as more time elapses from the channel estimation, the uncertainty of the channel estimation can increase based on greater channel variations that are more likely between times separated by a greater time difference.

[0110] Accordingly, the reported uncertainty value can be reported multiple times in accordance with CSI-RS transmissions / measurement. Alternatively or additionally, the reported uncertainty value can be modified based on a known elapsed time (e.g., number of symbols or slots) from the CSI-RS associated with the reported uncertainty value (e.g., based on a linear function or some other function) and possibly known or indicated (e.g., in one of the uncertainty reporting configuration 508, the first indication of one or more MCS uncertainty values 514, and / or the second indication of one or more MCS uncertainty values 524) set of parameters (e.g., set of coefficients associated with the linear function). For example, the increase in uncertainty value over time can be based on parameters determined by long-term channel conditions (e.g., power delay profile (PDP), Doppler spread, Doppler shift, etc.). Accordingly, the uncertainty can be specified as a linear function a*t + b, where t is associated with time (e.g., measured in number of symbols or slots) relative to the CSI-RS, and a and b are parameters / coefficients. In some aspects, a (and b) can be determined by the base station 502 or the UE 504 independently or based on a negotiation between the base station 502 and the UE 504. For example, in some aspects, a can be determined internally by the base station 502 and b can be reported by the UE 504. In some aspects, the function can be a non-linear function based on a selectable option.

[0111] In some aspects, the base station 502 can determine, at 526, the MCS (and / or rank) for PDSCH transmissions (whether associated with MIRS or OLLA) based on the MCS (and / or rank) associated with one or more values included in the CSI 522 (e.g., CQI and / or RI used to determine the MCS and / or rank) and the uncertainty value (for MCS, CQI, and / or RI) included in the first indication of one or more MCS uncertainty values 514 and / or the second indication of one or more MCS uncertainty values 524. In some aspects, the MCS determined at 526 can be the MCS associated with one or more values included in the CSI 522 plus the most recently reported uncertainty value associated with the MCS. In some aspects, the MCS determined at 526 can be based on adding the MCS associated with one or more values included in the CSI 522 to the most recently reported uncertainty value associated with the MCS, then adding an additional offset.

[0112] The base station 502 can then transmit a PDSCH transmission 528 based on the determined MCS (e.g., the MCS determined based on the CSI 522 and at least one of the first indication of one or more MCS uncertainty values 514 and / or the second indication of one or more MCS uncertainty values 524), and the UE 504 can receive the PDSCH transmission. The transmission can be a first transmission associated with using a MIRS with a MCS that is greater than an expected optimal MCS (e.g., associated with a higher index value and / or greater throughput), or can be an OLLA-based PDSCH transmission. Based on the PDSCH transmission 528, the UE 504 can transmit feedback 529 including one of an ACK or a NACK associated with a HARQ for OLLA or an IR-HARQ for MIRS, and the base station 502 can receive the feedback. The communications between the base station 502 and the UE 504 can continue with additional transmissions (e.g., retransmissions) from the base station 502 to the UE 504 and feedback from the UE 504 to the base station 502 (e.g., at least until an ACK is received).

[0113] In some aspects, the base station 502 can determine to update the configuration of uncertainty value reporting at 530 based on the feedback received from the UE 504 (e.g., the feedback 529 and / or additional feedback). For example, if the use of uncertainty value reporting (e.g., the first indication of one or more MCS uncertainty values 514 and / or the second indication of one or more MCS uncertainty values 524) results in a latency that is higher than an expected latency or a threshold latency value (e.g., a time from the initial transmission of the PDSCH transmission 528 to an indication of successful decoding), the base station 502 can determine to update the configuration of uncertainty value reporting at 530 in some aspects. In some aspects, the base station 502 can determine to request (or indicate) additional resources (e.g., processing resources) at the UE 504 for determining uncertainty values with a higher accuracy at 530. Alternatively, or additionally, the base station 502 can determine to request (or indicate) that the UE 504 discontinue (or omit transmitting) uncertainty value reporting at 530.

[0114] Based on the determination at 530, the base station 502 can transmit an updated uncertainty reporting configuration 532, and the UE 504 can receive the updated uncertainty reporting configuration. In some aspects, the updated uncertainty reporting configuration 532 can be smaller (e.g., include fewer bits and / or fields) than the uncertainty reporting configuration 508, as it can not include values for many of the parameters configured in the uncertainty reporting configuration 508. For example, the updated uncertainty reporting configuration 532 can indicate whether dedicated additional resources (e.g., in the form of a minimum number of resources, a maximum uncertainty useful for reporting, or other related parameters) and / or whether to interrupt transmission of uncertainty value reports, without indicating, for example, parameters associated with MIRS or (expected / requested) granularity of uncertainty value reports.

[0115] Figure 6 is a flow diagram of a method of wireless communication. The method can be performed by a UE (e.g., the UE 104, 504; the apparatus 1004). In some aspects, as part of establishing a connection with the UE, the UE can receive, from a network node (e.g., a base station or base station component), a (second) indication of a set of parameters associated with transmitting an indication of at least one uncertainty value. In some aspects, the set of parameters indicates a first subset of parameters associated with a capability of the network node and a second subset of parameters associated with a format for a first indication of at least one uncertainty value associated with at least one performance metric. In some aspects, the first subset of parameters can include a maximum number of retransmissions supported by the network node, a retransmission granularity (e.g., a retransmission unit, such as one of a CB, a plurality of CBs, a RB, a plurality of RBs, a TB, etc.), and a retransmission applicable size (e.g., a size associated with retransmission, which in some aspects can be based on a MCS LUT). In some aspects, the second subset of parameters can indicate that the UE transmit a plurality of MCS uncertainty values corresponding to at least one of: a plurality of subcarriers, a plurality of RBs including 12 subcarriers, a plurality of subbands including a plurality of RBs within a full bandwidth (e.g., associated with a wideband transmission). In some aspects, the second subset of parameters can indicate that the UE transmit a MCS uncertainty value corresponding to a full bandwidth (e.g., a set of frequency resources associated with a wideband transmission). For example, with reference to Figure 5 , the UE 504 can receive the uncertainty reporting configuration 508.

[0116] At 604, the UE can identify at least one performance metric associated with a channel estimation operation at the UE. For example, 604 can be performed by the UE 504, the apparatus 1004, the processor 1202, the processor 1402, or another processor in the UE 504 or apparatus 1004. Figure 10The application processor 1006, cellular baseband processor 1024, and / or MCS uncertainty reporting component 198 are used to perform this. In some aspects, at least one performance metric is one or more of CQI or RI. In some aspects, at least one performance metric may be based on an indication of a set of parameters associated with the transmission of at least one uncertainty value. For example, refer to Figure 5 UE 504 can identify at least one performance metric associated with the channel estimation operation at UE 504 based on uncertainty report configuration 508 at 510.

[0117] At point 606, the UE can calculate at least one uncertainty value associated with at least one performance metric. For example, 606 can be derived from... Figure 10 The application processor 1006, cellular baseband processor 1024, and / or MCS uncertainty reporting component 198 are used to perform this operation. In some aspects, at least one uncertainty value may be associated with one or more of CQI or RI. In some aspects, at least one uncertainty value may include a first uncertainty value for at least one of a first MCS value or a rank indicator value. In some aspects, at least one uncertainty value may be at least one hardware-dependent (e.g., channel condition-independent) uncertainty value calculated independently of a particular channel estimation operation. In some aspects, at least one hardware-dependent uncertainty value may include a hardware-dependent uncertainty value for each MCS for each supported rank. In some aspects, a hardware-dependent uncertainty value for each MCS for each supported rank may be associated with one of an MCS index or a code rate. In some aspects, at least one hardware-dependent uncertainty value may be further associated with one of the following: each of a plurality of frequency bands, each of a plurality of beam directions, or each of a plurality of SSBs. In some aspects, calculating the hardware-dependent uncertainty value at 606 may be associated with establishing a connection to a network node for channel estimation operations. For example, refer to... Figure 5 UE504 can calculate at 512 at at least one uncertainty value that is not based on the measured channel conditions.

[0118] In some aspects, the UE can perform channel estimation operations and can transmit a Channel Indicator Sequence (CSI) to the network node based on the channel estimation. In some aspects, the CSI may include information about channel quality (e.g., CQI) and rank (e.g., RI), which in some aspects can be used to determine the Multi-Channel Sequence (MCS) for subsequent data transmissions from the network node. The channel estimation and the transmitted CSI may be based on an indication of a set of parameters associated with an indication of at least one uncertainty value for the transmission pair. Therefore, the calculation at 606 may alternatively or additionally include calculating multiple uncertainty values ​​(e.g., MCS uncertainty values) corresponding to at least one of the following based on the channel estimation and / or CSI-RS: multiple subcarriers, multiple Restricted Blocks (RBs) including 12 subcarriers, and multiple subbands including multiple RBs within a wideband transmission. In some aspects, the uncertainty values ​​calculated at 606 may include MCS uncertainty values ​​corresponding to the full bandwidth of the wideband transmission. For example, refer to... Figure 5 At 520, UE 504 can calculate at least one uncertainty value based on channel conditions estimated by receiving one or more CSI-RS 516 and measuring CSI-RS at 518 as part of a channel estimation operation based on uncertainty reporting configuration 508.

[0119] In some aspects, the UE may send an indication to the network node whether at least one uncertainty value (e.g., an uncertainty value calculated at 606) differs from a previously reported uncertainty value (e.g., an indication that the at least one uncertainty value differs from the value of the previously reported uncertainty value). In some aspects, the indication of whether the at least one uncertainty value is different may be sent in the CSI or as a separate indication. For example, refer to Figure 5 UE 504 may send CSI 522 to base station 502, which includes an indication that at least one uncertainty value calculated at 520 is different from a previously reported uncertainty value.

[0120] At point 610, the UE can send an indication to the network node of at least one uncertainty value associated with at least one performance metric. For example, 610 can be... Figure 10 The application processor 1006, cellular baseband processor 1024, transceiver 1022, antenna 1080, and / or MCS uncertainty reporting component 198 are used to perform this operation. In some aspects, at least one uncertainty value may include at least one hardware-related uncertainty value. For example, refer to... Figure 5 UE 504 may send a first indication 514 to base station 502 for one or more MCS uncertainty values ​​based on calculating at least one uncertainty value at 512.

[0121] In some aspects, the at least one uncertainty value includes a first uncertainty value for a first MCS value. In some aspects, the first uncertainty value for the first MCS value can be associated with a first modulation scheme (e.g., a first constellation from QPSK, 16QAM, 64QAM, etc.). In some aspects, the at least one uncertainty value can also include a second uncertainty value for a second MCS value associated with a second modulation scheme (e.g., a second constellation from QPSK, 16QAM, 64QAM, etc.). In some aspects, the at least one uncertainty value includes a plurality of MCS uncertainty values indicated in a second subset of parameters associated with the format used for the first indication and computed at 606. For example, with reference to Figure 5 The UE 504 can transmit a second indication 524 of one or more MCS uncertainty values based on the uncertainty values computed at 520.

[0122] After transmitting the indication of the at least one uncertainty value associated with the at least one performance metric, in some aspects, the UE can receive a data transmission associated with at least one of a MCS or a rank based on the indication of the at least one uncertainty value. In some aspects using uncertainty value reporting for OLLA, the hardware-related uncertainty values can be sufficient to provide improved performance, and without additional uncertainty values based on channel estimation, the MCS or rank can be determined based on the indication of the at least one hardware-related uncertainty value (e.g., the UE can omit transmitting uncertainty values based on channel estimation). For example, with reference to Figure 5 The UE 504 can receive a PDSCH transmission 528 based on the MCS and / or rank determined at 526, which can be determined based on the first indication 514 of one or more MCS uncertainty values, based on the second indication 524 of one or more MCS uncertainty values, or based on both the first indication 514 of one or more MCS uncertainty values and the second indication 524 of one or more MCS uncertainty values.

[0123] In some aspects, the UE can transmit feedback (e.g., HARQ or IR-HARQ) in response to the received data transmission. At least one of the MCS or the rank can be based on the reported values in the CSI (e.g., associated with the identified performance metric) and the at least one uncertainty value. For example, with reference to Figure 5 The UE 504 can receive a PDSCH transmission 528 based on the MCS and / or rank determined at 526.

[0124] Based on the feedback, the UE can receive, from the network node, an indication of an update to the set of parameters associated with transmitting the indication of the at least one uncertainty value. In some aspects, the indication of the update can indicate whether dedicated additional resources (e.g., in the form of a minimum number of resources, a maximum uncertainty useful for reporting, or other relevant parameters) and / or whether to interrupt transmission of the uncertainty value reporting. In some aspects, the indication of the update can include an update to a parameter associated with MIRS or a (desired / requested) granularity of the uncertainty value reporting, as discussed with respect to the indication of the set of parameters associated with transmitting the indication of the at least one uncertainty value. For example, with reference to Figure 5 The UE 504 can receive an updated uncertainty reporting configuration 532 based on the feedback 529.

[0125] Figure 7 is a flow diagram of a method of wireless communication. The method can be performed by a UE (e.g., the UE 104, 504; the apparatus 1004). At 702, as part of establishing a connection with the UE, the UE can receive, from a network node (e.g., a base station or base station component), a (second) indication of a set of parameters associated with transmitting an indication of at least one uncertainty value. For example, 702 can be performed by Figure 10 by the application processor 1006, the cellular baseband processor 1024, the transceiver 1022, the antenna 1080, and / or the MCS uncertainty reporting component 198. In some aspects, the set of parameters indicates a first subset of parameters associated with a capability of the network node and a second subset of parameters associated with a format for a first indication of at least one uncertainty value associated with at least one performance metric. In some aspects, the first subset of parameters can include a maximum number of retransmissions supported by the network node, a retransmission granularity (e.g., a retransmission unit such as one of a CB, a plurality of CBs, a RB, a plurality of RBs, a TB, etc.), and a retransmission applicable size (e.g., a size associated with a retransmission, which in some aspects can be based on a MCS LUT). In some aspects, the second subset of parameters can indicate that the UE is to transmit a plurality of MCS uncertainty values corresponding to at least one of: a plurality of subcarriers, a plurality of RBs including 12 subcarriers, a plurality of subbands within a wideband transmission including a plurality of RBs. In some aspects, the second subset of parameters can indicate that the UE is to transmit an MCS uncertainty value corresponding to a full bandwidth (e.g., a set of frequency resources associated with a wideband transmission). For example, with reference to Figure 5 The UE 504 can receive an uncertainty reporting configuration 508.

[0126] At 704, the UE can identify at least one performance metric associated with a channel estimation operation at the UE. For example, 704 can be performed by Figure 10The application processor 1006, cellular baseband processor 1024, and / or MCS uncertainty reporting component 198 are used to perform this. In some aspects, at least one performance metric is one or more of CQI or RI. In some aspects, at least one performance metric may be based on an indication of a set of parameters associated with the transmission of at least one uncertainty value. For example, refer to Figure 5 UE 504 may identify at 510 at at least one performance metric associated with the channel estimation operation at UE 504.

[0127] At point 706, the UE can calculate at least one uncertainty value associated with at least one performance metric. For example, 706 can be derived from... Figure 10 The application processor 1006, cellular baseband processor 1024, and / or MCS uncertainty reporting component 198 are used to perform this operation. In some aspects, at least one uncertainty value may be associated with one or more of CQI or RI. In some aspects, at least one uncertainty value may include a first uncertainty value for at least one of a first MCS value or a rank indicator value. In some aspects, at least one uncertainty value may be at least one hardware-dependent (e.g., channel condition-independent) uncertainty value calculated independently of a particular channel estimation operation. In some aspects, at least one hardware-dependent uncertainty value may include a hardware-dependent uncertainty value for each MCS for each supported rank. In some aspects, a hardware-dependent uncertainty value for each MCS for each supported rank may be associated with one of an MCS index or a code rate. In some aspects, at least one hardware-dependent uncertainty value may further be associated with one of the following: each of a plurality of frequency bands, each of a plurality of beam directions, or each of a plurality of SSBs. In some aspects, at least one uncertainty value may include a first uncertainty value associated with a first set of conditions (e.g., a first resource amount associated with PDSCH transmissions overlapping or adjacent to instances of CSI-RS) and a second uncertainty value associated with a second set of conditions (e.g., a second resource amount associated with PDSCH transmissions overlapping or adjacent to instances of CSI-RS). In some aspects, calculating the hardware-related uncertainty value at 706 may be associated with establishing a connection with a network node for channel estimation operations. For example, refer to... Figure 5 UE 504 can calculate at 512 at at least one uncertainty value that is not based on the measured channel conditions.

[0128] In some aspects, the UE can perform a channel estimation operation and can transmit CSI to the network node based on the channel estimation. In some aspects, the CSI can include information about channel quality (e.g., CQI) and rank (e.g., RI), which can be used in some aspects to determine an MCS for a subsequent data transmission from the network node. The channel estimation and the transmitted CSI can be based on an indication of a set of parameters associated with transmitting the indication of at least one uncertainty value. Thus, the computation at 706 can alternatively or additionally include computing a plurality of uncertainty values (e.g., MCS uncertainty values) corresponding to at least one of: a plurality of subcarriers, a plurality of RBs including 12 subcarriers, a plurality of subbands including a plurality of RBs within a wideband transmission, based on the channel estimation and / or the CSI-RS. In some aspects, the uncertainty value computed at 706 can include an MCS uncertainty value corresponding to a full bandwidth of the wideband transmission. For example, with reference to Figure 5 At 520, the UE 504 can compute at least one uncertainty value based on channel conditions estimated based on receiving one or more CSI-RSs 516 at 518 and measuring the CSI-RSs as part of a channel estimation operation.

[0129] At 708, the UE can transmit, to the network node, an indication of whether the at least one uncertainty value (e.g., the uncertainty value computed at 706) is different from a previously reported uncertainty value (e.g., a value indicating whether the at least one uncertainty value is different from a previously reported uncertainty value). For example, 708 can be performed by application processor 1006, cellular baseband processor 1024, transceiver 1022, antenna 1080, and / or MCS uncertainty reporting component 198 of FIG. 13. Figure 10 At 520, the UE 504 can compute at least one uncertainty value based on channel conditions estimated based on receiving one or more CSI-RSs 516 at 518 and measuring the CSI-RSs as part of a channel estimation operation. Figure 5 At 520, the UE 504 can compute at least one uncertainty value based on channel conditions estimated based on receiving one or more CSI-RSs 516 at 518 and measuring the CSI-RSs as part of a channel estimation operation.

[0130] At 710, the UE can transmit, to the network node, an indication of at least one uncertainty value associated with at least one performance metric. For example, 710 can be performed by application processor 1006, cellular baseband processor 1024, transceiver 1022, antenna 1080, and / or MCS uncertainty reporting component 198 of FIG. 13. Figure 10 At 520, the UE 504 can compute at least one uncertainty value based on channel conditions estimated based on receiving one or more CSI-RSs 516 at 518 and measuring the CSI-RSs as part of a channel estimation operation. Figure 5UE 504 may send a first indication 514 to base station 502 for one or more MCS uncertainty values ​​based on calculating at least one uncertainty value at 512.

[0131] In some aspects, at least one uncertainty value includes a first uncertainty value for a first MCS value. In some aspects, the first uncertainty value for the first MCS value may be associated with a first modulation scheme (e.g., a first constellation from QPSK, 16QAM, 64QAM, etc.). In some aspects, at least one uncertainty value may also include a second uncertainty value for a second MCS value associated with a second modulation scheme (e.g., a second constellation from QPSK, 16QAM, 64QAM, etc.). In some aspects, at least one uncertainty value includes multiple MCS uncertainty values ​​indicated and calculated at 706 in a second subset of parameters associated with the format used for the first indication. For example, refer to... Figure 5 UE 504 may send a second indication 524 for one or more MCS uncertainty values ​​based on the uncertainty value calculated at 520.

[0132] At 712, the UE can receive data transmissions associated with at least one of the MCS or rank based on an indication of at least one uncertainty value. For example, 712 can be... Figure 10 The application processor 1006, cellular baseband processor 1024, transceiver 1022, antenna 1080, and / or MCS uncertainty reporting component 198 are used to perform this. In some aspects of using uncertainty value reporting for OLLA, hardware-dependent uncertainty values ​​may be sufficient to provide improved performance, and in the absence of additional uncertainty values ​​based on channel estimation, the MCS or rank can be based on an indication of at least one hardware-dependent uncertainty value (e.g., the UE may omit transmitting uncertainty values ​​based on channel estimation). For example, refer to... Figure 5 UE 504 may receive PDSCH transmission 528 based on the MCS and / or rank determined at 526, which may be determined based on a first indication 514 of one or more MCS uncertainty values, a second indication 524 of one or more MCS uncertainty values, or a first indication 514 of one or more MCS uncertainty values ​​and a second indication 524 of one or more MCS uncertainty values.

[0133] In some respects, the UE may send feedback (e.g., HARQ or IR-HARQ) in response to received data transmission. At least one of the MCS or rank may be based on a reported value in the CSI (e.g., associated with an identified performance metric) and at least one uncertainty value. For example, referencing Figure 5At 526, the UE 504 can receive a PDSCH transmission 528 based on the determined MCS and / or rank.

[0134] At 714, the UE can receive, from the network node, an indication of an update to the set of parameters associated with transmitting the indication of the at least one uncertainty value. For example, 714 can be performed by the application processor 1006, the cellular baseband processor 1024, the transceiver 1022, the antenna 1080, and / or the MCS uncertainty reporting component 198. In some aspects, the indication of the update can indicate whether dedicated additional resources (e.g., in the form of a minimum number of resources, a maximum uncertainty useful for reporting, or other relevant parameters) and / or whether to interrupt transmission of the uncertainty value reporting. In some aspects, the indication of the update can include an update to the parameters associated with the MIRS or the (expected / requested) granularity of the uncertainty value reporting, as discussed with respect to the indication of the set of parameters received at 702. For example, with reference to Figure 10 At 526, the UE 504 can receive a PDSCH transmission 528 based on the determined MCS and / or rank. Figure 5 At 526, the UE 504 can receive a PDSCH transmission 528 based on the determined MCS and / or rank.

[0135] Figure 8 is a flow diagram of a method of wireless communication. The method can be performed by a base station (e.g., the base station 102, 502; the network entity 1002, 1102). As part of establishing a connection with a UE (e.g., a wireless device), the base station can transmit, for the UE, a (third) indication of a set of parameters associated with transmitting an indication of at least one uncertainty value. In some aspects, the set of parameters indicates a first subset of parameters associated with a capability of the network node and a second subset of parameters associated with a format for a first indication of at least one uncertainty value associated with at least one performance metric. In some aspects, the first subset of parameters can include a maximum number of retransmissions supported by the network node, a retransmission granularity (e.g., a retransmission unit, such as one of a CB, a plurality of CBs, a RB, a plurality of RBs, a TB, etc.), and a retransmission applicable size (e.g., a size associated with a retransmission, which in some aspects can be based on a MCS LUT). In some aspects, the second subset of parameters can indicate that the UE is to transmit a plurality of MCS uncertainty values corresponding to at least one of: a plurality of subcarriers, a plurality of RBs including 12 subcarriers, or a plurality of subbands including a plurality of RBs within a wideband transmission. In some aspects, the second subset of parameters can indicate that the UE is to transmit an MCS uncertainty value corresponding to a full bandwidth. For example, with reference to Figure 5 At 526, the UE 504 can receive a PDSCH transmission 528 based on the determined MCS and / or rank.

[0136] At 804, the base station can receive from the UE a first indication of at least one uncertainty value associated with at least one performance metric, which is related to channel estimation operations at the UE. For example, 804 may be... Figure 11 The CU processor 1112, DU processor 1132, RU processor 1142, transceiver 1146, antenna 1180, and / or MCS uncertainty reporting component 199 perform the operation. In some aspects, at least one uncertainty value may be associated with one or more of CQI or RI. In some aspects, at least one uncertainty value includes a first uncertainty value for at least one of a first MCS value or a rank indicator value. In some aspects, at least one uncertainty value may be at least one hardware-dependent (e.g., channel condition-independent) uncertainty value calculated independently of a particular channel estimation operation. In some aspects, at least one hardware-dependent uncertainty value may include a hardware-dependent uncertainty value for each MCS for each supported rank (e.g., the rank supported by the UE). In some aspects, the hardware-dependent uncertainty value for each MCS for each supported rank may be associated with one of an MCS index or a code rate. In some aspects, at least one hardware-dependent uncertainty value may further be associated with one of: each of a plurality of frequency bands, each of a plurality of beam directions, or each of a plurality of SSBs. In some respects, receiving hardware-dependent uncertainty values ​​at 806 can be associated with establishing a connection with the UE for channel estimation operations. For example, refer to Figure 5 Base station 502 may receive a first indication 514 for one or more MCS uncertainty values ​​(which are hardware-related uncertainty values ​​not based on channel measurements).

[0137] In some aspects, the base station may participate in channel estimation operations (e.g., transmitting CSI-RS for channel estimation operations) and may receive CSI from the UE based on the channel estimation. In some aspects, the CSI may include information about channel quality (e.g., CQI) and rank (e.g., RI), which in some aspects can be used to determine the MCS for subsequent data transmissions from the base station. The channel estimation and the received CSI may be based on an indication of a set of parameters associated with an indication of at least one uncertainty value for transmission. Thus, the indication received at 806 may alternatively or additionally include receiving multiple uncertainty values ​​(e.g., MCS uncertainty values) corresponding to at least one of the following: multiple subcarriers, multiple RBs including 12 subcarriers, multiple subbands including multiple RBs within a wideband transmission. In some aspects, the indication received at 806 may include an MCS uncertainty value corresponding to the full bandwidth (e.g., the set of frequency resources associated with wideband transmission). For example, refer to Figure 5The base station 502 may receive a first indication 514 for one or more MCS uncertainty values ​​based on hardware-related parameters / characteristics and / or a second indication 524 for one or more MCS uncertainty values ​​based on channel conditions estimated by transmitting one or more CSI-RS 516 as part of a channel estimation operation.

[0138] In some respects, at least one uncertainty value may include at least one hardware-related uncertainty value. For example, refer to Figure 5 Base station 502 can receive a first indication 514 for one or more MCS uncertainty values ​​from UE 504. In some aspects, at least one uncertainty value includes a first uncertainty value for a first MCS value. In some aspects, the first uncertainty value for the first MCS value may be associated with a first modulation scheme (e.g., a first constellation from QPSK, 16QAM, 64QAM, etc.). In some aspects, at least one uncertainty value may also include a second uncertainty value for a second MCS value associated with a second modulation scheme (e.g., a second constellation from QPSK, 16QAM, 64QAM, etc.). In some aspects, at least one uncertainty value includes multiple MCS uncertainty values ​​indicated by a second subset of parameters associated with the format used for the first indication. For example, referencing... Figure 5 Base station 502 can receive a second indication 524 for one or more MCS uncertainty values.

[0139] At point 806, the base station can receive from the UE a second indication of at least one value of at least one performance metric associated with at least one uncertainty value. For example, point 806 may be derived from... Figure 11 The CU processor 1112, DU processor 1132, RU processor 1142, transceiver 1146, antenna 1180, and / or MCS uncertainty reporting component 199 are used to perform this function. In some aspects, at least one performance metric is one or more of CQI or RI. In some aspects, at least one performance metric may be based on an indication of a set of parameters associated with an indication of at least one uncertainty value transmitted. For example, refer to... Figure 5 Base station 502 can receive CSI 522 by transmitting one or more CSI-RS 516 signals. For example... Figure 5 As indicated in the document, a second instruction may be received at 806 before the first instruction is received at 804.

[0140] In some aspects, the base station can receive from the UE an indication of whether at least one uncertainty value (e.g., an uncertainty value received at 804) differs from a previously reported uncertainty value (e.g., a value indicating whether the at least one uncertainty value differs from a previously reported uncertainty value). In some aspects, the indication of whether the at least one uncertainty value is different can be sent in the CSI (a CSI received at 806 that includes at least one value of at least one performance metric) or as a separate indication. For example, refer to... Figure 5 Base station 502 can receive CSI 522 from UE 504, which includes an indication that at least one uncertainty value is different from a previously reported uncertainty value.

[0141] At point 808, the base station can select a set of parameters for subsequent communication based on at least one value of at least one performance metric and at least one uncertainty value. For example, point 808 can be determined by... Figure 11 The CU processor 1112, DU processor 1132, RU processor 1142, and / or MCS uncertainty reporting component 199 perform this operation. In some aspects, the parameter set may include determining the MCS (or rank) associated with subsequent communication. The MCS (and / or rank) used for PDSCH transmission (e.g., a first transmission associated with MIRS or a PDSCH transmission associated with OLLA) is based on a first indication of at least one uncertainty value received at 804 and a second indication received at 806. In some aspects, the parameter set selected at 808 may be further based on a time offset (e.g., time distance) from the CSI-RS used to determine the parameter set for subsequent communication. In some aspects of using uncertainty value reporting for OLLA, hardware-dependent uncertainty values ​​may be sufficient to provide improved performance, and in the absence of additional uncertainty values ​​based on channel estimation, the MCS or rank may be based on an indication of at least one hardware-dependent uncertainty value (e.g., the base station may omit receiving uncertainty values ​​based on channel estimation). For example, refer to... Figure 5 Base station 502 may determine the MCS and / or rank at 526 based on a first indication 514 of one or more MCS uncertainty values, a second indication 524 of one or more MCS uncertainty values, or both the first indication 514 and the second indication 524 of one or more MCS uncertainty values.

[0142] The base station can transmit data associated with a selected set of parameters. In some aspects, data transmission can be a PDSCH transmission associated with MIRS. For example, refer to Figure 5 Base station 502 can transmit PDSCH based on the MCS and / or rank determined at 526 at 528.

[0143] In some aspects, the base station can receive feedback (e.g., HARQ or IR-HARQ) in response to the transmitted data. At least one of the MCS or the rank can be based on a reported value (e.g., associated with the identified performance metric) and an uncertainty value in the CSI. For example, referring to Figure 5 The base station 502 can receive a PDSCH transmission 528 based on the MCS and / or rank determined at 526.

[0144] In some aspects, the base station can transmit, for the UE, an indication of an update to a set of parameters associated with transmitting an indication of at least one uncertainty value. In some aspects, the indication of the update can indicate whether dedicated additional resources (e.g., in the form of a minimum number of resources, a maximum uncertainty useful for reporting, or other relevant parameters) and / or whether to interrupt transmission of the uncertainty value reporting. In some aspects, the indication of the update can include an update to a parameter or a (desired / requested) granularity of uncertainty value reporting associated with MIRS, as discussed for the indication of the set of parameters transmitted by the base station. For example, referring to Figure 5 The base station 502 can transmit an updated uncertainty reporting configuration 532 based on the feedback 529.

[0145] Figure 9 is a flow diagram of a method of wireless communication. The method can be performed by a base station (e.g., the base station 102, 502; the network entity 1002, 1102). At 902, as part of establishing a connection with a UE (e.g., a wireless device), the base station can transmit, for the UE, a (third) indication of a set of parameters associated with transmitting an indication of at least one uncertainty value. For example, 902 can be performed by a base station 502 by determining 504 the set of parameters, transmitting 506 the indication of the set of parameters, and / or the like. Figure 11the CU processor 1112, the DU processor 1132, the RU processor 1142, the transceiver 1146, the antenna 1180, and / or the MCS uncertainty reporting component 199 to perform. In some aspects, the set of parameters indicates a first subset of parameters associated with capabilities of the network node and a second subset of parameters associated with a format for a first indication of at least one uncertainty value associated with at least one performance metric. In some aspects, the first subset of parameters can include a maximum number of retransmissions supported by the network node, a retransmission granularity (e.g., a retransmission unit, such as one of a CB, a plurality of CBs, a RB, a plurality of RBs, a TB, etc.), and a retransmission applicable size (e.g., a size associated with a retransmission, which in some aspects can be based on a MCS LUT). In some aspects, the second subset of parameters can indicate that the UE is to transmit a plurality of MCS uncertainty values corresponding to at least one of: a plurality of subcarriers, a plurality of RBs including 12 subcarriers, a plurality of subbands including a plurality of RBs within a wideband transmission. In some aspects, the second subset of parameters can indicate that the UE is to transmit an MCS uncertainty value corresponding to a full bandwidth (e.g., a set of frequency resources associated with a wideband transmission). For example, with reference to Figure 5 The base station 502 can transmit an uncertainty reporting configuration 508, for example.

[0146] At 904, the base station can receive, from the UE, a first indication of at least one uncertainty value associated with at least one performance metric associated with channel estimation operations at the UE. For example, 904 can be performed by the uncertainty reporting component 1902. Figure 11by the CU processor 1112, the DU processor 1132, the RU processor 1142, the transceiver 1146, the antenna 1180, and / or the MCS uncertainty reporting component 199. In some aspects, the at least one uncertainty value can be associated with one or more of a CQI or a RI. In some aspects, the at least one uncertainty value includes a first uncertainty value for at least one of a first MCS value or a rank indicator value. In some aspects, the at least one uncertainty value can be at least one hardware-related (e.g., channel condition independent) uncertainty value that is computed independent of a particular channel estimation operation. In some aspects, the at least one hardware-related uncertainty value can include a hardware-related uncertainty value for each MCS for each supported rank. In some aspects, the hardware-related uncertainty value for each MCS for each supported rank can be associated with one of a MCS index or a code rate. In some aspects, the at least one hardware-related uncertainty value can be further associated with one of: each frequency band of a plurality of frequency bands, each beam direction of a plurality of beam directions, or each SSB of a plurality of SSBs. In some aspects, the at least one uncertainty value can include a first uncertainty value associated with a first set of conditions (e.g., associated with PDSCH transmissions that overlap or are adjacent to an instance of a CSI-RS or a first amount of resources for a first time from a last CSI-RS or reported uncertainty value) and a second uncertainty value associated with a second set of conditions (e.g., associated with PDSCH transmissions that overlap or are adjacent to an instance of a CSI-RS or a second amount of resources for a second time from a last CSI-RS or reported uncertainty value). In some aspects, receiving the hardware-related uncertainty value at 906 can be associated with establishing a connection with the UE for channel estimation operations. For example, with reference to Figure 5 , the base station 502 can receive a first indication 514 of one or more MCS uncertainty values (which are hardware-related uncertainty values that are not based on channel measurements).

[0147] In some aspects, the base station can participate in a channel estimation operation (e.g., transmit a CSI-RS for the channel estimation operation) and can receive CSI from the UE based on the channel estimation. In some aspects, the CSI can include information about channel quality (e.g., CQI) and rank (e.g., RI), which in some aspects can be used to determine an MCS for a subsequent data transmission from the base station. The channel estimation and the received CSI can be based on the indication of the set of parameters associated with transmitting the indication of the at least one uncertainty value. Thus, the indication received at 906 can alternatively or additionally include receiving a plurality of uncertainty values (e.g., MCS uncertainty values) corresponding to at least one of: a plurality of subcarriers as indicated by a second subset of the parameters, a plurality of RBs including 12 subcarriers, a plurality of subbands including a plurality of RBs within a wideband transmission. In some aspects, the indication received at 906 can include an MCS uncertainty value corresponding to a full bandwidth (e.g., a set of frequency resources associated with the wideband transmission). For example, with reference to Figure 5 The base station 502 can receive a first indication 514 of one or more MCS uncertainty values based on hardware-related parameters / characteristics and / or a second indication 524 of one or more MCS uncertainty values based on channel conditions estimated based on transmitting one or more CSI-RSs 516 as part of a channel estimation operation.

[0148] In some aspects, the at least one uncertainty value can include at least one hardware-related uncertainty value. For example, with reference to Figure 5 The base station 502 can receive, from the UE 504, a first indication 514 of one or more MCS uncertainty values. In some aspects, the at least one uncertainty value includes a first uncertainty value for a first MCS value. In some aspects, the first uncertainty value for the first MCS value can be associated with a first modulation scheme (e.g., a first constellation from QPSK, 16QAM, 64QAM, etc.). In some aspects, the at least one uncertainty value can further include a second uncertainty value for a second MCS value associated with a second modulation scheme (e.g., a second constellation from QPSK, 16QAM, 64QAM, etc.). In some aspects, the at least one uncertainty value includes a plurality of MCS uncertainty values indicated in a second subset of parameters associated with a format for the first indication. For example, with reference to Figure 5 The base station 502 can receive a second indication 524 of one or more MCS uncertainty values.

[0149] At 906, the base station can receive, from the UE, a second indication of at least one value of at least one performance metric associated with the at least one uncertainty value. For example, 906 can be performed by a processor 338 of the base station 502, under the control of the operating system 342 or a channel estimation component 346 in the software 340. Figure 11by the CU processor 1112, the DU processor 1132, the RU processor 1142, the transceiver 1146, the antenna 1180, and / or the MCS uncertainty reporting component 199 of the apparatus 1100. In some aspects, the at least one performance metric is one or more of a CQI or an RI. In some aspects, the at least one performance metric can be based on an indication of a set of parameters associated with transmitting the indication of the at least one uncertainty value. For example, with reference to Figure 5 The base station 502 can receive the CSI 522 based on transmitting the one or more CSI-RSs 516. As indicated in Figure 5 the second indication can be received at 906 prior to receiving the first indication at 904.

[0150] In some aspects, the base station can receive, from the UE, an indication of whether the at least one uncertainty value (e.g., the uncertainty value received at 904) is different from a previously reported uncertainty value (e.g., a value indicating whether the at least one uncertainty value is different from a previously reported uncertainty value). In some aspects, the indication of whether the at least one uncertainty value is different can be transmitted in the CSI (the CSI including the at least one value of the at least one performance metric received at 906) or as a separate indication. For example, with reference to Figure 5 The base station 502 can receive, from the UE 504, the CSI 522 including an indication that the at least one uncertainty value is different from a previously reported uncertainty value.

[0151] At 908, the base station can select a set of parameters for a subsequent communication based on the at least one value of the at least one performance metric and the at least one uncertainty value. For example, 908 can be performed by Figure 11 the CU processor 1112, the DU processor 1132, the RU processor 1142, and / or the MCS uncertainty reporting component 199 of the apparatus 1100. In some aspects, the set of parameters can include determining an MCS (or rank) associated with the subsequent communication. The MCS (and / or rank) for a PDSCH transmission (e.g., a first transmission associated with a MIRS or a PDSCH transmission associated with an OLLA) is based on the first indication of the at least one uncertainty value received at 904 and the second indication received at 906. In some aspects, selecting the set of parameters at 908 can be further based on a time offset (e.g., a time distance) from a CSI-RS used to determine the set of parameters for the subsequent communication. In some aspects using uncertainty value reporting for OLLA, a hardware-related uncertainty value can be sufficient to provide improved performance, and without an additional uncertainty value based on a channel estimate, the MCS or rank can be based on the indication of the at least one hardware-related uncertainty value (e.g., the base station can omit receiving an uncertainty value based on a channel estimate). For example, with reference to Figure 5Base station 502 may determine the MCS and / or rank at 526 based on a first indication 514 of one or more MCS uncertainty values, a second indication 524 of one or more MCS uncertainty values, or both the first indication 514 and the second indication 524 of one or more MCS uncertainty values.

[0152] At point 910, the base station can transmit data associated with a selected set of parameters. For example, point 910 can be... Figure 11 The CU processor 1112, DU processor 1132, RU processor 1142, transceiver 1146, antenna 1180, and / or MCS uncertainty reporting component 199 are used to perform this. In some aspects, data transmission can be a PDSCH transmission associated with MIRS. For example, refer to Figure 5 Base station 502 can transmit PDSCH based on the MCS and / or rank determined at 526 at 528.

[0153] In some aspects, the base station can receive feedback (e.g., HARQ or IR-HARQ) in response to data transmitted at 910. At least one of the MCS or rank can be based on reported values ​​in the CSI (e.g., associated with the identified performance metric) and uncertainty values. For example, referencing Figure 5 Base station 502 can receive PDSCH transmission 528 based on the MCS and / or rank determined at 526.

[0154] At point 912, the base station can send an indication to the UE of an update to the set of parameters associated with an indication of transmitting at least one uncertainty value. For example, 912 can be... Figure 11 The CU processor 1112, DU processor 1132, RU processor 1142, transceiver 1146, antenna 1180, and / or MCS uncertainty reporting component 199 are used to perform this. In some aspects, the updated indication may indicate whether additional resources are dedicated (e.g., in the form of a minimum number of resources, the maximum uncertainty useful for reporting, or other relevant parameters) and / or whether the transmission of uncertainty value reports is interrupted. In some aspects, the updated indication may include updates to the (expected / requested) granularity of parameters or uncertainty value reports associated with MIRS, as discussed for the indication of the parameter set transmitted at 902. For example, refer to... Figure 5 Base station 502 can send updated uncertainty report configuration 532 based on feedback 529.

[0155] Figure 10is a diagram 1000 illustrating an example of a hardware implementation for an apparatus 1004. The apparatus 1004 can be a UE, a component of a UE, or can implement UE functionality. In some aspects, the apparatus 1004 can include at least one cellular baseband processor 1024 (also referred to as a modem) coupled with one or more transceivers 1022 (e.g., a cellular RF transceiver). The cellular baseband processor 1024 can include at least one on-chip memory 1024'. In some aspects, the apparatus 1004 can further include one or more Subscriber Identity Modules (SIM) cards 1020, and at least one application processor 1006 coupled with a secure digital (SD) card 1008 and a screen 1010. The application processor 1006 can include on-chip memory 1006'. In some aspects, the apparatus 1004 can further include a Bluetooth module 1012, a WLAN module 1014, a SPS module 1016 (e.g., a GNSS module), one or more sensor modules 1018 (e.g., a barometric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; a light detection and ranging (LIDAR), a radio detection and ranging (RADAR), a sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technology for positioning), an additional memory module 1026, a power supply 1030, and / or a camera 1032. The Bluetooth module 1012, the WLAN module 1014, and the SPS module 1016 can include on-chip transceivers (TRXs) (or in some cases, only receivers (RXs)). The Bluetooth module 1012, the WLAN module 1014, and the SPS module 1016 can include their own dedicated antennas, and / or utilize one or more antennas 1080 for communications. The cellular baseband processor 1024 communicates with the UE 104 and / or with a RU associated with the network entity 1002 via the one or more antennas 1080 through the transceiver 1022. The cellular baseband processor 1024 and the application processor 1006 can each include computer-readable media / memory 1024', 1006', respectively. The additional memory module 1026 can also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1024', 1006', 1026 can be non-transitory. The cellular baseband processor 1024 and the application processor 1006 each are responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1024 / application processor 1006, causes the cellular baseband processor 1024 / application processor 1006 to perform the various functions described supra. The computer-readable medium / memory can also be used for storing data manipulated by the cellular baseband processor 1024 / application processor 1006 when executing software.The cellular baseband processor 1024 / application processor 1006 can be a component of the UE 350 and can include at least one memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the apparatus 1004 can be at least one processor chip (modem and / or application) and include only the cellular baseband processor 1024 and / or the application processor 1006, and in another configuration, the apparatus 1004 can be the entire UE (e.g., see FIG. 3. Figure 3 and include additional modules of the apparatus 1004.

[0156] As discussed above, the MCS uncertainty reporting component 198 can be configured to identify at least one performance metric associated with channel estimation operations at the UE. The MCS uncertainty reporting component 198 can be further configured to calculate at least one uncertainty value associated with the at least one performance metric. The MCS uncertainty reporting component 198 can also be configured to transmit, to a network node, an indication of the at least one uncertainty value associated with the at least one performance metric. The MCS uncertainty reporting component 198 can be within the cellular baseband processor 1024, the application processor 1006, or both the cellular baseband processor 1024 and the application processor 1006. The MCS uncertainty reporting component 198 can be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When implementing with multiple processors, the multiple processors can carry out the stated processes / algorithm individually or in combination. As illustrated, the apparatus 1004 can include a variety of components configured for various functions. In one configuration, the apparatus 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) can include means for identifying at least one performance metric associated with channel estimation operations at the UE. The apparatus 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) can also include means for calculating at least one uncertainty value associated with the at least one performance metric. The apparatus 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) can also include means for transmitting, to a network node, an indication of the at least one uncertainty value associated with the at least one performance metric. The apparatus 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) can also include means for receiving, from the network node as part of establishing a connection with the UE, a second indication of a set of parameters associated with transmitting the indication of the at least one uncertainty value. The apparatus 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) can also include means for transmitting a value indicating whether the at least one uncertainty value is different from a previously reported uncertainty value. The apparatus 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) can also include means for receiving a data transmission associated with at least one of a MCS or a rank based on the indication of the at least one uncertainty value. The means can be the MCS uncertainty reporting component 198 of the apparatus 1004 configured to perform the functions recited by the means. As described above, the apparatus 1004 can include the TX processor 368, the RX processor 356, and the controller / processor 359.Thus, in one configuration, the means can be a TX processor 368, an RX processor 356, and / or a controller / processor 359 that are configured to perform the functions recited by the means or as otherwise described herein. Figure 6 and Figure 7 the TX processor 368, the RX processor 356, and / or the controller / processor 359.

[0157] Figure 11 is a diagram 1100 illustrating examples of hardware implementation for a network entity 1102. The network entity 1102 can be a BS, a component of a BS, or can implement BS functionality. The network entity 1102 can include at least one of a CU 1110, a DU 1130, or a RU 1140. For example, depending on the layer functionality handled by the component 199, the network entity 1102 can include the CU 1110; both the CU 1110 and the DU 1130; each of the CU 1110, the DU 1130, and the RU 1140; the DU 1130; both the DU 1130 and the RU 1140; or the RU 1140. The CU 1110 can include at least one CU processor 1112. The CU processor 1112 can include on-chip memory 1112'. In some aspects, the CU 1110 can also include an additional memory module 1114 and a communication interface 1118. The CU 1110 communicates with the DU 1130 over a backhaul link, such as an Fl interface. The DU 1130 can include at least one DU processor 1132. The DU processor 1132 can include on-chip memory 1132'. In some aspects, the DU 1130 can also include an additional memory module 1134 and a communication interface 1138. The DU 1130 communicates with the RU 1140 over a front-haul link. The RU 1140 can include at least one RU processor 1142. The RU processor 1142 can include on-chip memory 1142'. In some aspects, the RU 1140 can also include an additional memory module 1144, one or more transceivers 1146, one or more antennas 1180, and a communication interface 1148. The RU 1140 communicates with the UE 104. The on-chip memories 1112', 1132', 1142' and the additional memory modules 1114, 1134, 1144 can each be considered a computer- readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of the processors 1112, 1132, 1142 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described supra. The computer-readable medium / memory can also be used for storing data that is manipulated by the processor when executing software.

[0158] As discussed above, the MCS uncertainty reporting component 199 can be configured to receive, from a UE, a first indication of at least one uncertainty value associated with at least one performance metric associated with channel estimation operations at the UE. The MCS uncertainty reporting component 199 can be further configured to receive, from the UE, a second indication of at least one value of the at least one performance metric associated with the at least one uncertainty value. The MCS uncertainty reporting component 199 can also be configured to select a set of parameters for subsequent communications based on the at least one value of the at least one performance metric and the at least one uncertainty value. The MCS uncertainty reporting component 199 can be within one or more processors of one or more of the CU 1110, the DU 1130, and the RU 1140. The MCS uncertainty reporting component 199 can be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are present, the stated processes / algorithm can be executed separately or combined to be executed by one or more processors. The network entity 1102 can include multiple components that are configured for various functions. In one configuration, the network entity 1102 can include means for receiving, from a UE, a first indication of at least one uncertainty value associated with at least one performance metric associated with channel estimation operations at the UE. In one configuration, the network entity 1102 can include means for receiving, from the UE, a second indication of at least one value of the at least one performance metric associated with the at least one uncertainty value. In one configuration, the network entity 1102 can include means for selecting a set of parameters for subsequent communications based on the at least one value of the at least one performance metric and the at least one uncertainty value. In one configuration, the network entity 1102 can include means for transmitting, to the UE, a third indication of a set of reporting parameters associated with receiving the first indication of the at least one uncertainty value as part of establishing a connection with the UE. In one configuration, the network entity 1102 can include means for transmitting, to the UE, a subsequent communication based on the selected set of parameters. The means can be the MCS uncertainty reporting component 199 of the network entity 1102 configured to perform the functions recited by the means. As described above, the network entity 1102 can include the TX processor 316, the RX processor 370, and the controller / processor 375. Accordingly, in one configuration, the means can be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means or described with respect to Figure 8 and Figure 9 the MCS uncertainty reporting component 199.

[0159] Various aspects of the present disclosure generally relate to improvements to MIRS (or OLLA) that involve transmitting, from a receiving device, an uncertainty report associated with an MCS indicated by the receiving device (e.g., based on MCS estimation capabilities of the receiving device, channel conditions, Doppler effects, interference, SINR, etc.). For example, in some aspects of the present disclosure, a receiving device (e.g., a wireless device or UE) can report an indication (e.g., an uncertainty report) of uncertainty associated with a CQI (or RI) estimate (e.g., via CSI) to a transmitting device (e.g., a base station or network node), which the transmitting device can use to determine a (dynamic) gap (or offset) between a second, higher MCS used for a first MIRS transmission and an MCS based on values reported by the receiving device (e.g., CQI and / or RI reported via CSI) to reduce latency associated with identifying or determining an MCS using MIRS. In some aspects, reducing latency can be based on the (dynamic) gap (based on the reported uncertainty value and the reported CQI / RI estimate) being less than a (static) gap or offset (based on the reported CQI / RI estimate), such that the number and associated time of failed transmissions due to intentionally using a too-high MCS for a first transmission for MIRS is reduced.

[0160] While both the (static) gap or offset and the (dynamic) gap or offset can be based on a maximum expected difference between a MCS value based on a set of measured values (e.g., values included in CSI) and an optimal (or highest) MCS, the (dynamic) gap or offset can be associated with a smaller maximum expected difference based on additional information provided by the receiving device. For example, a UE can report a MCS uncertainty value of “one MCS” such that a base station can determine to use a MCS that is one MCS or MCS index value higher than the reported MCS (e.g., a MCS associated with values reported in or associated with CSI, such as CQI, RI, SINR, RSRP, RSSI, etc.) for a first transmission of MIRS, rather than a larger number of MCSs (e.g., three MCSs or MCS index values, as described above). Thus, when using MIRS with a MCS uncertainty value, an optimal MCS can be identified with reduced latency compared to latency associated with using MIRS without a MCS uncertainty value, without impacting performance (e.g., reaching the same optimal MCS or code rate).

[0161] When applied to OLLA used between CSI-RSs, the uncertainty value can provide a transmitting device (e.g., a network node or base station) with additional information that can improve selection of an MCS for a subsequent transmission. For example, knowing that a reported value of a performance metric used to determine the MCS has an associated uncertainty of a first magnitude (e.g., greater than an assumed magnitude) can allow the transmitting device to increase the MCS (and associated throughput) for a subsequent transmission beyond what might have been selected based on the reported value of the performance metric without the additional information.

[0162] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by reporting at least one uncertainty value associated with at least one performance metric, the described techniques can be used to increase throughput associated with one of OLLA, MIRS, or other methods of determining an MCS for a particular communication. Additionally, for MIRS, reporting of uncertainty values can improve latency associated with identifying (or converging to) an optimized MCS (e.g., code rate and constellation) and throughput.

[0163] Generally, MIRS is a proposed method for improving channel state feedback (CSF) reporting that more rigorously utilizes instantaneous capacity. MIRS relies on attempting to transmit a higher capacity MCS than what is recommended in CQI. The above disclosure proposes that the UE will also recommend to the base station (e.g., gNB) how much the MCS should be raised in the first transmission attempt.

[0164] It should be appreciated that a specific ordering or hierarchy of the blocks in the disclosed processes / flowcharts is merely illustrative. It should be appreciated that the specific ordering or hierarchy of the blocks in the processes / flowcharts can be rearranged based on design preference. Additionally, some blocks can be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not necessarily limited to the specific order or hierarchy presented.

[0165] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other aspects. Thus, the claims are not to be limited to the aspects described herein, but are to be given the full scope defined by the language of the claims. Unless otherwise defined, a reference to a singular element includes “one or more” thereof. Terms such as “if,” “when,” and “while” do not imply direct temporal relationships or reaction sequences. That is, a phrase referring to “when” does not mean “immediately upon” or “in response to” an action, but simply means that an action will occur if a condition is met, without requiring a specific or immediate temporal relationship to the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of the group consisting of A, B, and C,” “one or more of the group consisting of A, B, and C,” and “A, B, and / or C” include the entire group of A, B, and / or C and can include combinations of one or more A, one or more B, or one or more C. Specifically, the combinations “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of the group consisting of A, B, and C,” “one or more of the group consisting of A, B, and C,” and “A, B, and / or C” can include A alone, B alone, C alone, A and B, A and C, B and C, or A and B and C, where any such combination can contain one or more members of A, B, or C. A set should be interpreted as a collection of elements that can be one or more. Accordingly, a set of X includes one or more X. When a set of one or more processors is configured to perform a set of functions, the set of one or more processors is configured to perform the set of functions individually or in any combination. Thus, each processor in the set of one or more processors can be configured to perform a particular subset of the set of functions, where the subset is a proper subset of the complete set, an appropriate subset of the set, or an empty subset of the set. If a first device receives data from a second device or sends data to the second device, the data can be received or sent directly from or to the first device and the second device, or indirectly through a set of devices between the first device and the second device. A device configured to “output” data, such as a signal or message, may, for example, send the data with a transceiver, or can transfer the data to a device that sends the data.A device configured to "obtain" data (such as transmit, signal, or message) can, for example, receive the data with a transceiver, or can obtain the data from a device that receives the data. Information stored in memory includes instructions and / or data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, any combination of the

[0166] As used herein, the phrase "based on" shall not be construed as a signification of an exclusive set of items, conditions, factors, etc. on which information is to be based unless there is explicit language to that effect. In other words, the phrase "based on A" (where A can be information, conditions, factors, etc.) should be interpreted as "based at least in part on A," unless otherwise specifically recited.

[0167] The following aspects are merely exemplary and can be combined with other aspects or teachings described herein without limitation.

[0168] Aspect 1 is a method of wireless communication at a user equipment (UE), comprising: identifying at least one performance metric associated with a channel estimation operation at the UE; calculating at least one uncertainty value associated with the at least one performance metric; and transmitting, to a network node, an indication of the at least one uncertainty value associated with the at least one performance metric.

[0169] Aspect 2 is the method of aspect 1, wherein the at least one performance metric is one or more of a channel quality indicator (CQI) or a rank indicator (RI), and wherein the at least one uncertainty value is associated with one or more of the CQI or the RI.

[0170] Aspect 3 is the method of any one of aspects 1 and 2, wherein the at least one uncertainty value comprises a first uncertainty value for at least one of a first modulation and coding scheme (MCS) value or a rank indicator value.

[0171] Aspect 4 is the method of aspect 3, wherein the first uncertainty value for the first MCS value is associated with a first modulation scheme, and wherein the at least one uncertainty value further comprises a second uncertainty value for a second MCS value associated with a second modulation scheme.

[0172] Aspect 5 is the method of any of aspects 3 and 4, wherein the indication is a first indication, the method further comprising: receiving, from the network node as part of establishing a connection with the UE, a second indication of a set of parameters associated with transmitting the indication of the at least one uncertainty value, wherein the set of parameters indicates a first subset of parameters associated with a capability of the network node and a second subset of parameters associated with a format for the first indication.

[0173] Aspect 6 is the method of aspect 5, wherein the second subset of parameters associated with the format for the first indication indicates that the UE transmits a plurality of MCS uncertainty values corresponding to at least one of: a plurality of subcarriers, a plurality of resource blocks (RBs) including 12 subcarriers, or a plurality of subbands including a plurality of RBs within a wideband transmission.

[0174] Aspect 7 is the method of aspect 6, wherein the at least one uncertainty value comprises the plurality of MCS uncertainty values.

[0175] Aspect 8 is the method of any of aspects 1-7, wherein the at least one uncertainty value comprises at least one hardware-related uncertainty value that is computed independently of a particular channel estimation operation.

[0176] Aspect 9 is the method of aspect 8, wherein the at least one hardware-related uncertainty value comprises a hardware-related uncertainty value for each modulation and coding scheme (MCS) of each supported rank, wherein the hardware-related uncertainty value for each MCS of each supported rank is associated with one of: an MCS index or a code rate, wherein the at least one hardware-related uncertainty value is further associated with one of: each of a plurality of frequency bands, each of a plurality of beam directions, or each of a plurality of synchronization signal blocks (SSBs).

[0177] Aspect 10 is the method of any of aspects 8 and 9, wherein computing the hardware- related uncertainty value and transmitting the indication of the hardware-related uncertainty value are associated with establishing a connection with the network node for the channel estimation operation.

[0178] Aspect 11 is the method of any of aspects 1-10, wherein the at least one uncertainty value comprises a first uncertainty value associated with a first set of conditions and a second uncertainty value associated with a second set of conditions.

[0179] Aspect 12 is the method of any of aspects 1-11, the method further comprising: transmitting a value indicating whether the at least one uncertainty value is different from a previously reported uncertainty value.

[0180] Aspect 13 is a method of any of aspects 1 through 12, further comprising receiving, based on the indication of the at least one uncertainty value, data transmissions associated with at least one of a modulation and coding scheme (MCS) or a rank.

[0181] Aspect 14 is a method of wireless communication of a network node, the method comprising: receiving, from a user equipment (UE), a first indication of at least one uncertainty value associated with at least one performance metric associated with channel estimation operations at the UE; receiving, from the UE, a second indication of at least one value of the at least one performance metric associated with the at least one uncertainty value; and selecting a set of parameters for subsequent communications based on the at least one value of the at least one performance metric and the at least one uncertainty value.

[0182] Aspect 15 is the method of aspect 14, wherein the at least one performance metric is one or more of a channel quality indicator (CQI) or a rank indicator (RI), and wherein the at least one uncertainty value is associated with one or more of the CQI or the RI.

[0183] Aspect 16 is the method of any of aspects 14 and 15, wherein the at least one uncertainty value comprises a first uncertainty value for at least one first modulation and coding scheme (MCS) value or rank indicator value.

[0184] Aspect 17 is the method of aspect 16, wherein the first uncertainty value for the first MCS value is associated with a first modulation scheme, and wherein the at least one uncertainty value further comprises a second uncertainty value for a second MCS value associated with a second modulation scheme.

[0185] Aspect 18 is the method of any of aspects 16 and 17, further comprising: transmitting, as part of establishing a connection with the UE, a third indication of a set of reporting parameters associated with receiving the first indication of the at least one uncertainty value for the UE, wherein the set of reporting parameters indicates a first subset of parameters associated with capabilities of the network node and a second subset of parameters associated with a format for the first indication.

[0186] Aspect 19 is the method of aspect 18, wherein the second subset of parameters associated with the format for the first indication indicates that the UE is to transmit a number of MCS uncertainty values corresponding to at least one of: a number of subcarriers, a number of resource blocks (RBs) including 12 subcarriers, or a number of subbands including a number of RBs within a wideband transmission.

[0187] Aspect 20 is the method of aspect 19, wherein the at least one value of the at least one performance metric associated with the at least one uncertainty value comprises the plurality of MCS uncertainty values.

[0188] Aspect 21 is the method of any one of aspects 14-20, wherein the at least one uncertainty value comprises at least one hardware-related uncertainty value that is computed independently of a particular channel estimation operation.

[0189] Aspect 22 is the method of aspect 21, wherein the at least one hardware-related uncertainty value comprises a hardware-related uncertainty value for each modulation and coding scheme (MCS) for each supported rank, wherein the hardware-related uncertainty value for each MCS for each supported rank is associated with one of an MCS index or a code rate, wherein the at least one hardware-related uncertainty value is further associated with one of: each band of a plurality of bands, each beam direction of a plurality of beam directions, or each synchronization signal block (SSB) of a plurality of SSBs.

[0190] Aspect 23 is the method of any one of aspects 14-22, wherein the at least one uncertainty value comprises a first uncertainty value associated with a first set of conditions and a second uncertainty value associated with a second set of conditions.

[0191] Aspect 24 is the method of any one of aspects 14-23, wherein the subsequent communication is associated with at least one feedback-related parameter optimization operation.

[0192] Aspect 25 is an apparatus for wireless communication at a device, the apparatus comprising a memory and at least one processor coupled to the memory and configured to individually or in any combination, based on information stored in the memory, implement any of aspects 1-24.

[0193] Aspect 26 is the apparatus of aspect 25, further comprising a transceiver or antenna coupled to the at least one processor.

[0194] Aspect 27 is an apparatus for wireless communication at a device, the apparatus comprising means for implementing any of aspects 1-24.

[0195] Aspect 28 is a computer-readable medium (for example, a non-transitory computer- readable medium) storing computer executable code, where the code when executed by at least one processor causes the processor to individually or in any combination implement any of aspects 1-24.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and configured, based at least in part on information stored in the at least one memory, to: identify at least one performance metric associated with a channel estimation operation at the UE; calculate at least one uncertainty value associated with the at least one performance metric; and send, to a network node, an indication of the at least one uncertainty value associated with the at least one performance metric.

2. The apparatus of claim 1, wherein the at least one performance metric is one or more of a channel quality indicator (CQI) or a rank indicator (RI), and wherein the at least one uncertainty value is associated with one or more of the CQI or the RI.

3. The apparatus of claim 1, wherein the at least one uncertainty value includes a first uncertainty value for at least one of a first modulation and coding scheme (MCS) value or a rank indicator value.

4. The apparatus of claim 3, wherein the first uncertainty value for the first MCS value is associated with a first modulation scheme, and wherein the at least one uncertainty value further includes a second uncertainty value for a second MCS value associated with a second modulation scheme.

5. The apparatus of claim 3, wherein the indication is a first indication, the at least one processor being further configured, individually or in any combination, to: receive, from the network node as part of establishing a connection with the UE, a second indication of a set of parameters associated with sending the indication of the at least one uncertainty value, wherein the set of parameters indicates a first subset of parameters associated with a capability of the network node and a second subset of parameters associated with a format for the first indication.

6. The apparatus of claim 5, wherein the second subset of parameters associated with the format for the first indication indicates that the UE sends a plurality of MCS uncertainty values corresponding to at least one of a plurality of subcarriers, a plurality of resource blocks (RBs) including 12 subcarriers, or a plurality of subbands including a plurality of RBs within a wideband transmission.

7. The apparatus of claim 6, wherein the at least one uncertainty value includes the plurality of MCS uncertainty values.

8. The apparatus of claim 1, wherein the at least one uncertainty value includes at least one hardware-related uncertainty value calculated independently of a particular channel estimation operation. ​ 9. The apparatus of claim 8, wherein the at least one hardware-related uncertainty value comprises a hardware-related uncertainty value for each modulation and coding scheme (MCS) for each supported rank, wherein the hardware-related uncertainty value for each MCS for each supported rank is associated with one of a MCS index or a code rate, wherein the at least one hardware-related uncertainty value is further associated with one of each of a plurality of frequency bands, each of a plurality of beam directions, or each of a plurality of synchronization signal blocks (SSBs).

10. The apparatus of claim 8, wherein the at least one processor, individually or in any combination, is further configured to calculate the at least one hardware-related uncertainty value and transmit the indication of the at least one hardware-related uncertainty value in association with establishing a connection with the network node for the channel estimation operation.

11. The apparatus of claim 1, wherein the at least one uncertainty value comprises a first uncertainty value associated with a first set of conditions and a second uncertainty value associated with a second set of conditions.

12. The apparatus of claim 1, the at least one processor, individually or in any combination, is further configured to: transmit a value indicating whether the at least one uncertainty value is different from a previously reported uncertainty value.

13. The apparatus of claim 1, the at least one processor, individually or in any combination, is further configured to: receive a data transmission associated with at least one of a modulation and coding scheme (MCS) or a rank based on the indication of the at least one uncertainty value.

14. The apparatus of claim 1, the apparatus further comprising a transceiver coupled to the at least one processor, wherein to transmit the indication, the at least one processor, individually or in any combination, is configured to transmit, via the transceiver, the indication of the at least one uncertainty value associated with the at least one performance metric to the network node.

15. An apparatus for communication of a network node, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to, individually or in any combination, based at least in part on information stored in the at least one memory: receive, from a user equipment (UE), a first indication of at least one uncertainty value associated with at least one performance metric, the at least one performance metric associated with a channel estimation operation at the UE; receive, from the UE, a second indication of at least one value of the at least one performance metric associated with the at least one uncertainty value; and select a set of parameters for subsequent communication based on the at least one value of the at least one performance metric and the at least one uncertainty value. ​ 16. The apparatus of claim 15, wherein the at least one performance metric is one or more of a channel quality indicator (CQI) or a rank indicator (RI), and wherein the at least one uncertainty value is associated with one or more of the CQI or the RI.

17. The apparatus of claim 15, wherein the at least one uncertainty value includes a first uncertainty value for at least one first modulation and coding scheme (MCS) value or rank indicator value.

18. The apparatus of claim 17, wherein the first uncertainty value for the first MCS value is associated with a first modulation scheme, and wherein the at least one uncertainty value further includes a second uncertainty value for a second MCS value associated with a second modulation scheme.

19. The apparatus of claim 17, wherein the at least one processor, individually or in any combination, is further configured to: transmit, as part of establishing a connection with the UE, a third indication to the UE of a set of reporting parameters associated with receiving the first indication of the at least one uncertainty value, wherein the set of reporting parameters indicates a first subset of parameters associated with a capability of the network node and a second subset of parameters associated with a format for the first indication.

20. The apparatus of claim 19, wherein the second subset of parameters associated with the format for the first indication indicates that the UE is to transmit a plurality of MCS uncertainty values corresponding to at least one of: a plurality of subcarriers, a plurality of resource blocks (RBs) including 12 subcarriers, or a plurality of subbands including a plurality of RBs within a wideband transmission.

21. The apparatus of claim 20, wherein the at least one value of the at least one performance metric associated with the at least one uncertainty value includes the plurality of MCS uncertainty values.

22. The apparatus of claim 15, wherein the at least one uncertainty value includes at least one hardware-related uncertainty value that is computed independent of a particular channel estimation operation.

23. The apparatus of claim 22, wherein the at least one hardware-related uncertainty value includes a hardware-related uncertainty value for each modulation and coding scheme (MCS) per supported rank, wherein the hardware-related uncertainty value for each MCS per supported rank is associated with one of a MCS index or a code rate, wherein the at least one hardware-related uncertainty value is further associated with one of: each of a plurality of frequency bands, each of a plurality of beam directions, or each of a plurality of synchronization signal blocks (SSBs).

24. The apparatus of claim 15, wherein the at least one uncertainty value includes a first uncertainty value associated with a first set of conditions and a second uncertainty value associated with a second set of conditions.

25. The apparatus of claim 15, wherein the subsequent communication is associated with at least one feedback-related parameter optimization operation.

26. The apparatus of claim 15, the apparatus further comprising a transceiver coupled to the at least one processor, wherein to receive the first indication and the second indication, the at least one processor is configured, individually or in any combination: to receive the first indication via the transceiver; and to receive the second indication via the transceiver.

27. A method for communication of a user equipment (UE), the method comprising: identifying at least one performance metric associated with channel estimation operations at the UE; calculating at least one uncertainty value associated with the at least one performance metric; and sending, to a network node, an indication of the at least one uncertainty value associated with the at least one performance metric.

28. The method of claim 27, wherein the at least one performance metric is one or more of a channel quality indicator (CQI) or a rank indicator (RI), and wherein the at least one uncertainty value is associated with one or more of the CQI or the RI.

29. A method for communication of a network node, the method comprising: receiving, from a user equipment (UE), a first indication of at least one uncertainty value associated with at least one performance metric, the at least one performance metric being associated with channel estimation operations at the UE; receiving, from the UE, a second indication of at least one value of the at least one performance metric associated with the at least one uncertainty value; and selecting a set of parameters for subsequent communication based on the at least one value of the at least one performance metric and the at least one uncertainty value.

30. The method of claim 29, wherein the at least one performance metric is one or more of a channel quality indicator (CQI) or a rank indicator (RI), and wherein the at least one uncertainty value is associated with one or more of the CQI or the RI. ​

Images