Method for calculating signal-to-noise ratio estimation value of transport block

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may monitor a downlink transmission from a network device, the downlink transmission including a set of parity bits. The UE may determine, based at least in part on the monitoring, a number of parity in the set of parity bits that do not pass or satisfy the parity procedure. The UE may identify a feedback state indicator for the downlink transmission based at least in part on the monitoring and the number of parity. The UE may transmit a feedback message based at least in part on the number of parity, the feedback message including the feedback status indicator and additional information.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 840,378, entitled “METHODS TO COMPUTE A SIGNAL-TO-NOISE RATIO ESTIMATEFOR A TRANSPORT BLOCK,” filed by Elshafie et al. on June 14, 2022, which is assigned to the assignee of this application. Technical Field

[0003] The following relates to wireless communications, including methods for calculating a signal-to-noise ratio estimate for a transport block. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may use techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more network devices or one or more network access nodes, each of which simultaneously supports communication for multiple communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0005] The described technology relates to improved methods, systems, devices and apparatuses that support methods for calculating signal-to-noise ratio (SNR) estimates for transport blocks. In general, the described technology provides a solution for a user equipment (UE) to transmit parity information (or information derived from the parity information) to a network device. The network device then determines a modulation and coding scheme (MCS) based on the received information and then communicates with the UE using the determined MCS. The network device can use the parity information to determine an appropriate MCS or only use the MCS suggested by the UE in retransmissions.

[0006] The UE may monitor downlink transmissions from a network device. The downlink transmission may include systematic bits and parity bits. The UE uses the parity bits during the decoding attempt to confirm that the packet transmitted by the downlink is successfully received and decoded. For example, the UE may run a parity check (e.g., a parity check procedure iteration) on the received parity bits. Based on whether the parity bits fail or pass the parity check procedure, the UE may then send recovery information from the downlink. The UE may identify or otherwise determine a feedback status indicator for the downlink transmission, which is sent to the network device in a feedback message. In addition, the UE may include additional information associated with the parity check in the feedback message, such as how many parity checks are successful or unsuccessful, and the ratio of successful or unsuccessful parity checks to the total number of parity checks. Alternatively, the UE may use a table provided to the UE to map the parity check value to the SNR. In some examples, the UE may indicate the SNR of the channel and / or a preferred MCS derived from the SNR in the feedback message (e.g., the UE uses parity information to determine the SNR and / or a more appropriate MCS).

[0007] A method for wireless communication at a UE is described. The method may include: monitoring a downlink transmission from a network device, the downlink transmission including a set of parity check bits; determining, based on the monitoring, a number of parity checks in the set of parity check bits that fail a parity check procedure or satisfy the parity check procedure; identifying a feedback status indicator for the downlink transmission based on the monitoring and the number of parity checks; and sending a feedback message based on the number of parity checks, the feedback message including the feedback status indicator and additional information.

[0008] An apparatus for wireless communication at a UE is described. The apparatus may include at least one processor, a memory coupled to the at least one processor (e.g., operatively, communicatively, functionally, electronically, or electrically), and instructions stored in the memory. The instructions may be executable by at least one processor to cause the apparatus to: monitor a downlink transmission from a network device, the downlink transmission including a set of parity check bits; determine the number of parity checks in the set of parity check bits that do not pass a parity check procedure or satisfy the parity check procedure based on the monitoring; identify a feedback status indicator for the downlink transmission based on the monitoring and the number of parity checks; and send a feedback message based on the number of parity checks, the feedback message including the feedback status indicator and additional information.

[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for monitoring a downlink transmission from a network device, the downlink transmission including a set of parity check bits; a component for determining, based on the monitoring, the number of parity checks in the set of parity check bits that do not pass a parity check procedure or satisfy the parity check procedure; a component for identifying a feedback status indicator for the downlink transmission based on the monitoring and the number of parity checks; and a component for sending a feedback message based on the number of parity checks, the feedback message including the feedback status indicator and additional information.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by at least one processor to perform the following operations: monitoring a downlink transmission from a network device, the downlink transmission including a set of parity check bits; determining the number of parity checks in the set of parity check bits that do not pass a parity check procedure or meet the parity check procedure based on the monitoring; identifying a feedback status indicator for the downlink transmission based on the monitoring and the number of parity checks; and sending a feedback message based on the number of parity checks, the feedback message including the feedback status indicator and additional information.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: mapping the number of parity checks to an SNR associated with a channel used for the downlink transmission; and identifying an MCS based on the SNR, wherein the additional information in the feedback message may be the MCS.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, mapping the number of parity checks may include operations, features, components, or instructions for correlating the number of parity checks to an SNR reference based on one or more iterations of the parity check procedure.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying the MCS may include operations, features, means, or instructions for identifying a highest available MCS supported by the SNR.

[0014] In some examples of the methods, apparatus, and non-transitory computer readable media described herein, identifying the MCS may include operations, features, means, or instructions for identifying an estimated block error rate for the downlink transmission based on the number of parity checks.

[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for including the number of parity checks as the additional information in the feedback message.

[0016] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for performing one or more iterations of the parity check procedure on the set of parity check bits transmitted on the downlink.

[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for: after each iteration of the parity check procedure, identifying the number of parity checks.

[0018] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for: identifying the number of parity checks after a last iteration of the parity check procedure.

[0019] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for: identifying the number of parity checks at an intermediate iteration of the parity check procedure.

[0020] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for identifying the number of parity checks based on the parity checks satisfying the parity check procedure.

[0021] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for identifying a number of the parity checks based on the parity checks failing the parity check procedure.

[0022] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for identifying a number of parity checks based on a ratio of parity checks that satisfy the parity check procedure to parity checks that fail the parity check procedure.

[0023] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying the number of parity checks based on a ratio of the parity checks that satisfy the parity check procedure to a total number of parity checks used for the downlink transmission.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying the number of parity checks based on a ratio of parity checks that failed the parity check procedure to a total number of parity checks used for the downlink transmission.

[0025] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for identifying a set of indicator values ​​associated with the number of parity checks based on signaling exchanged with the network device.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of indicator values ​​includes an indicator value corresponding to a quantization of the number of parity checks.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of the indicator value set from the network device using at least one of radio resource control (RRC) signaling, a medium access control (MAC) control element (CE) message, a downlink control information (DCI) message, a UE assistance information message, or a combination thereof.

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying the number of parity checks based at least in part on a number of layers associated with the downlink transmission, a transport block size (TBS), a target block error rate (BLER), or any combination thereof.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the downlink transmission includes a cellular-based downlink transmission received from a network device or a sidelink-based downlink transmission received from a neighboring UE.

[0030] A method for wireless communication at a network device is described. The method may include: sending a downlink transmission including a set of parity bits to a UE; receiving a feedback message from the UE based on a number of parity checks associated with the set of parity bits, the feedback message including a feedback status indicator and additional information, the number of parity checks based on parity checks in the set of parity bits that fail a parity check procedure or satisfy the parity check procedure; and selecting an MCS for communicating with the UE based on the feedback message.

[0031] An apparatus for wireless communication at a network device is described. The apparatus may include at least one processor, a memory coupled to the at least one processor (e.g., operatively, communicatively, functionally, electronically, or electrically), and instructions stored in the memory. The instructions may be executable by the at least one processor to cause the apparatus to: send a downlink transmission including a set of parity bits to a UE; receive a feedback message from the UE based on the number of parity checks associated with the set of parity bits, the feedback message including a feedback status indicator and additional information, the number of parity checks being based on the parity checks in the set of parity bits that do not pass a parity check procedure or that satisfy the parity check procedure; and select an MCS for communicating with the UE based on the feedback message.

[0032] Another apparatus for wireless communication at a network device is described. The apparatus may include: means for sending a downlink transmission including a set of parity bits to a UE; means for receiving a feedback message from the UE based on a number of parity checks associated with the set of parity bits, the feedback message including a feedback status indicator and additional information, the number of parity checks based on parity checks in the set of parity bits that do not pass a parity check procedure or that satisfy the parity check procedure; and means for selecting an MCS for communicating with the UE based on the feedback message.

[0033] A non-transitory computer-readable medium storing code for wireless communication at a network device is described. The code may include instructions that can be executed by at least one processor to perform the following operations: sending a downlink transmission including a set of parity bits to a UE; receiving a feedback message from the UE based on a number of parity checks associated with the set of parity bits, the feedback message including a feedback status indicator and additional information, the number of parity checks based on parity checks in the set of parity bits that do not pass a parity check procedure or meet the parity check procedure; and selecting an MCS for communicating with the UE based on the feedback message.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying the MCS based on an SNR associated with a channel used for the downlink transmission, wherein the additional information in the feedback message may be the MCS.

[0035] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: identifying the number of parity checks based on the additional information in the feedback message; and identifying the MCS based on the number of parity checks.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the number of parity checks may be identified based on the parity checks satisfying the parity check procedure.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the number of parity checks may be identified based on the parity checks that failed the parity check procedure.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the number of parity checks may be identified based on a ratio of parity checks that satisfy the parity check procedure to parity checks that fail the parity check procedure.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the number of parity checks may be identified based on a ratio of parity checks that satisfy the parity check procedure to a total number of parity checks used for the downlink transmission.

[0040] In some examples of the methods, apparatus, and non-transitory computer readable media described herein, the number of parity checks may be identified based on a ratio of parity checks that failed the parity check procedure to a total number of parity checks used for the downlink transmission.

[0041] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for identifying a set of indicator values ​​associated with the number of parity checks based on signaling exchanged with the UE.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of indicator values ​​includes an indicator value corresponding to a quantization of the number of parity checks.

[0043] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication of the indicator value set to the UE using at least one of RRC signaling, MAC CE message, DCI message, UE assistance information message, or a combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 An example of a wireless communication system supporting a method for calculating a signal-to-noise ratio (SNR) estimate value of a transport block according to aspects of the present disclosure is illustrated.

[0045] Figure 2 An example of a wireless communication system supporting a method for calculating an SNR estimation value of a transport block according to aspects of the present disclosure is illustrated.

[0046] Figure 3 An example of a decoding configuration supporting a method for calculating an SNR estimation value of a transport block according to aspects of the present disclosure is illustrated.

[0047] Figure 4 An example of a process supporting a method for calculating an SNR estimation value of a transport block according to aspects of the present disclosure is illustrated.

[0048] Figure 5 and Figure 6 A block diagram of a device supporting a method for calculating an SNR estimate value of a transport block according to various aspects of the present disclosure is shown.

[0049] Figure 7 A block diagram of a communication manager supporting a method for calculating SNR estimates for transport blocks according to aspects of the present disclosure is shown.

[0050] Figure 8 A diagram of a system including a device supporting a method for calculating an SNR estimate value for a transport block according to aspects of the present disclosure is shown.

[0051] Fig. 9 and Fig.10 A block diagram of a device supporting a method for calculating an SNR estimate value of a transport block according to various aspects of the present disclosure is shown.

[0052] Fig.11 A block diagram of a communication manager supporting a method for calculating SNR estimates for transport blocks according to aspects of the present disclosure is shown.

[0053] Fig.12 A diagram of a system including a device supporting a method for calculating an SNR estimate value for a transport block according to aspects of the present disclosure is shown.

[0054] Figures 13 to 17 A flow chart illustrating a method supporting a method for calculating an SNR estimate value for a transport block according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0055] Some wireless communication systems may use turbo hybrid automatic repeat request (HARQ) procedures to improve latency and increase reliability. For example, a user equipment (UE) may be configured to indicate not only a negative acknowledgement (NACK), but also additional channel state information (CSI) using the NACK. The network device uses this information combination to select a more appropriate modulation and coding scheme (MCS) for communicating with the UE to avoid or minimize additional failed transmissions. For example, CSI information combined with a NACK indicating that the UE cannot successfully receive and decode a downlink transmission may provide an indication of the channel condition of a channel for communicating with the UE. Therefore, the network device may select an MCS for communicating with the UE that is more suitable for the channel condition. However, the CSI included with the NACK may be outdated. Additionally, conventional methods for providing other indicators of an appropriate MCS are challenging when the UE is to send a NACK because the UE typically lacks information about the signal that causes the NACK.

[0056] Various aspects of the present disclosure are initially described in the context of a wireless communication system. In general, the described technology provides a solution for a UE to transmit parity information to a network device, which derives an MCS from the parity information and then uses the derived MCS in communication with the UE. The network device can use the parity information to determine an appropriate MCS or only use the MCS suggested by the UE in retransmissions. The UE may monitor downlink transmissions from the network device. The downlink transmission may include systematic bits and parity bits. The UE uses the parity bits during decoding attempts to confirm that the packets transmitted by the downlink are successfully received and decoded. For example, the UE may run a parity check (e.g., a parity check procedure iteration) on the received parity bits. Based on whether the parity bits fail or pass the parity check procedure, the UE may then send recovery information from the downlink. The UE may identify or otherwise determine a feedback status indicator for the downlink transmission, which is sent to the network device in a feedback message. In addition, the UE may include additional information associated with the parity check in the feedback message, such as how many parity checks are successful or unsuccessful, the ratio of successful or unsuccessful parity checks to the total number of parity checks. Alternatively, the UE may use a table provided to the UE to map the parity check value to the SNR. In some examples, the UE may indicate the SNR of the channel and / or a preferred MCS derived from the SNR in the feedback message (e.g., the UE uses the parity check information to determine the SNR and / or a more appropriate MCS).

[0057] Various aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow charts related to methods for calculating SNR estimates for transport blocks.

[0058] Figure 1 An example of a wireless communication system 100 supporting a method for calculating an SNR estimate for a transport block according to various aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network devices 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, or a new radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low-latency communications, or communications with low-cost and low-complexity devices, or any combination thereof.

[0059] The network devices 105 may be dispersed across a geographic area to form the wireless communication system 100, and may be devices in different forms or with different capabilities. The network devices 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each network device 105 may provide a coverage area 110 over which the UEs 115 and the network devices 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the network devices 105 and the UEs 115 may support communication of signals according to one or more radio access technologies.

[0060] UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary, or mobile, or both at different times. UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. Figure 1 As shown, the UE 115 described herein may be able to communicate with various types of devices, such as other UEs 115, network devices 105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment).

[0061] The network devices 105 may communicate with the core network 130 or with each other, or both. For example, the network devices 105 may interact with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). The network devices 105 may communicate with each other directly (e.g., directly between the network devices 105) or indirectly (e.g., via the core network 130) or in both ways via the backhaul links 120 (e.g., via X2, Xn, or other interfaces). In some examples, the backhaul links 120 may be or include one or more wireless links.

[0062] One or more of the network devices 105 described herein may include or may be referred to by a person of ordinary skill in the art as a transceiver base station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next generation NodeB or a giga NodeB (any of which may be referred to as a gNB), a home NodeB, a home eNodeB, or other suitable terminology.

[0063] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where a "device" may also be referred to as a unit, a station, a terminal, a client, or the like. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a multimedia / entertainment device (e.g., a radio, an MP3 player, or a video device), a camera, a gaming device, a navigation / positioning device (e.g., a GNSS (Global Navigation Satellite System) device based on, for example, GPS (Global Positioning System), BeiDou system, GLONASS or Galileo system, ground-based equipment), a tablet computer, a laptop computer, a netbook, a smartbook, a personal computer, a smart device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, virtual reality goggles, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet)), a drone, a robot / robotic device, a vehicle, a vehicle's equipment, a meter (e.g., a parking meter, an electricity meter, a gas meter, a water meter), a monitor, a gas pump, an appliance (e.g., a kitchen appliance, a washing machine, a dryer), a location tag, a medical / health care device, an implant, a sensor / actuator, a display, or any other suitable device configured to communicate via a wireless or wired medium. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0064] The UE 115 described herein may be able to communicate with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network devices 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay network devices, etc. Figure 1 shown.

[0065] UE 115 and network device 105 may communicate wirelessly with each other via one or more communication links 125 on one or more carriers. The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels of a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0066] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be located according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

[0067] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the network device 105 or a downlink transmission from the network device 105 to the UE 115. A carrier may carry downlink communications or uplink communications (e.g., in an FDD mode) or may be configured to carry both downlink communications and uplink communications (e.g., in a TDD mode).

[0068] A carrier may be associated with a specific bandwidth of a radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a plurality of determined bandwidths of a carrier for a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network device 105, a UE 115, or both) may have a hardware configuration that supports communication over a specific carrier bandwidth, or may be capable of being configured to support communication over one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network device 105 or a UE 115 that supports simultaneous communication via carriers associated with a plurality of carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0069] The signal waveform transmitted through the carrier wave may be composed of multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM technology, a resource element may include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements received by UE 115 and the higher the order of the modulation scheme, the higher the data rate for UE 115 may be. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further improve the data rate or data integrity of communications with UE 115.

[0070] One or more parameter sets for a carrier may be supported, where the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0071] The time interval for the network device 105 or the UE 115 can be expressed as a multiple of a basic time unit, which can be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf maxIt can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

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

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

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

[0075] Each network device 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network device 105 (e.g., via a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of the network device 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping geographic coverage areas 110, and the like.

[0076] A macro cell generally covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. Small cells may be associated with lower-power network devices 105 than macro cells, and small cells may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with small cells (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). Network equipment 105 may support one or more cells, and may also use one or more component carriers to support communications on one or more cells.

[0077] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0078] In some examples, the network devices 105 may be mobile and thus provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same network device 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different network devices 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network devices 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.

[0079] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network devices 105 may have similar frame timing, and transmissions from different network devices 105 may be approximately aligned in time. For asynchronous operation, the network devices 105 may have different frame timing, and in some examples, transmissions from different network devices 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

[0080] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with network devices 105 without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging. In one aspect, the technology disclosed herein may be applicable to MTC or IoT UEs. MTC or IoT UE may include MTC / enhanced MTC (eMTC, also known as CAT-M, Cat M1) UE, NB-IoT (also known as CAT NB1) UE, and other types of UE. eMTC and NB-IoT may refer to future technologies that may evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (further enhanced eMTC), and mMTC (massive MTC), and NB-IoT may include eNB-IoT (enhanced NB-IoT) and FeNB-IoT (further enhanced NB-IoT).

[0081] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not support simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UEs 115 include entering a power saving deep sleep mode when not engaged in active communications, operating over a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

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

[0083] In some examples, UE 115 may also be able to communicate directly with other UE 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication may be located within a geographic coverage area 110 of a network device 105. Other UEs 115 in this group may be outside the geographic coverage area 110 of the network device 105, or otherwise unable to receive transmissions from the network device 105. In some examples, a group of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, wherein each UE 115 transmits to each other UE 115 in the group. In some examples, the network device 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between these UEs 115 without the involvement of the network device 105.

[0084] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, the vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network device 105) using vehicle-to-network (V2N) communication, or both.

[0085] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management for UE115 served by a network device 105 associated with the core network 130. User IP packets may be delivered through user plane entities, which may provide IP address allocation and other functions. The user plane entity may be connected to IP services 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or a packet-switched streaming service.

[0086] Some of the network devices 105, such as base stations, may include subcomponents, such as access network entities 140, which may be examples of access node controllers (ANCs). Each access network entity 140 may communicate with the UE 115 through one or more other access network transmission entities 145, which may be referred to as radio heads, smart radio heads, or transmission / reception points (TRPs). Each access network transmission entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or network device 105 may be distributed across various network devices 105 (e.g., radio heads and ANCs) or merged into a single network device 105.

[0087] The wireless communication system 100 may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, but these waves may be sufficient to penetrate structures so that macro cells provide service to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0088] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also referred to as a centimeter band) or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network device 105, and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater atmospheric attenuation and shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0089] The wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may use licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed radio frequency spectrum band, devices such as network devices 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands may be based on carrier aggregation configurations (e.g., LAA) in conjunction with component carriers operating in licensed bands. Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0090] The network device 105 or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network device 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more network device antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network device 105 may be located at different geographical locations. The network device 105 may have an antenna array having several rows and columns of antenna ports that the network device 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals sent via the antenna ports.

[0091] The network device 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0092] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., network device 105, UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0093] The network device 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network device 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communications with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network device 105 in different directions. For example, the network device 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions in different beam directions may be used to identify (e.g., by a transmitting device (such as the network device 105), or by a receiving device (such as the UE 115)) the beam direction for later transmission or reception by the network device 105.

[0094] Some signals, such as data signals associated with a particular receiving device, may be sent by network device 105 in a single beam direction, e.g., a direction associated with a receiving device, such as UE 115. In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals sent in one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network device 105 in different directions, and may report to network device 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0095] In some examples, transmission by a device (e.g., by network device 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from network device 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across a system bandwidth or one or more subbands. Network device 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or unprecoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent by network device 105 in one or more directions, UE 115 may employ similar techniques to send signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals in a single direction (e.g., to send data to a receiving device).

[0096] A receiving device (e.g., UE 115) may try multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from the network device 105. For example, the receiving device may try multiple reception directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when receiving a data signal). The single reception configuration may be aligned on a beam direction determined based on listening according to different reception configuration directions (e.g., a beam direction determined to have the highest signal strength, highest SNR, or other acceptable signal quality based on listening according to multiple beam directions).

[0097] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer or packet data convergence protocol (PDCP) layer may be IP-based. The radio link control (RLC) layer may perform packet segmentation and reassembly to communicate through logical channels. The medium access control (MAC) layer may perform priority handling and multiplexing of logical channels to transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer may provide the establishment, configuration, and maintenance of an RRC connection that supports radio bearers of user plane data between UE115 and network device 105 or core network 130. At the physical layer, transport channels may be mapped to physical channels.

[0098] UE 115 and network device 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data through communication link 125. HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In other cases, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0099] UE 115 may monitor a downlink transmission from network device 105, the downlink transmission including a set of parity bits. UE 115 may determine, based at least in part on the monitoring, the number of parity checks in the set of parity bits that fail a parity check procedure or satisfy the parity check procedure. UE 115 may identify a feedback status indicator for the downlink transmission based at least in part on the monitoring and the number of parity checks. UE 115 may send a feedback message based at least in part on the number of parity checks, the feedback message including the feedback status indicator and additional information.

[0100] Network device 105 may send a downlink transmission including a set of parity bits to UE 115. Network device 105 may receive a feedback message from UE 115 based at least in part on a number of parity checks associated with the set of parity bits, the feedback message including a feedback status indicator and additional information, the number of parity checks based at least in part on parity checks in the set of parity bits that failed a parity check procedure or satisfied the parity check procedure. Network device 105 may select an MCS for communicating with UE 115 based at least in part on the feedback message.

[0101] Figure 2 An example of a wireless communication system 200 supporting a method for calculating an SNR estimate value for a transport block according to aspects of the present disclosure is illustrated. The wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication system 200 may include a network device 205 and / or a UE 210, which may be examples of corresponding devices described herein.

[0102] The wireless communication system 200 may support turbo-HARQ. Broadly speaking, this may include UE 210 supporting HARQ-ACK and CSI feedback, thereby providing faster CQI feedback to achieve ultra-reliability for the first retransmission. For example, improved latency may be achieved by reducing the number of retransmissions to only one retransmission. For example, initially the network device 205 may map incoming packets available for transmission to an MCS based on a target block error rate (BLER), which is determined based on a current understanding of channel quality. The UE 210 may attempt to decode the initial transmission, but may fail. The UE 210 may attempt to determine the channel capacity based on a signal-to-interference-plus-noise ratio (SINR). When sending a NACK indication for a downlink transmission for a decoding failure, the UE 210 may include an indication of the CSI in a feedback message to the network device 205. The network device 205 may receive the NACK indication and the CSI indication in the feedback message and map the retransmission of the downlink information to an MCS determined based on an updated understanding of the CQI (e.g., based on the CSI indication received from the UE 210). For example, the coding length and resources used for the retransmission may be determined based on the CSI feedback received from the UE 210. Thus, the network device 205 may retransmit the downlink information to the UE 210 using the newly mapped MCS, which is more appropriate for the current channel conditions. This may enable the UE 210 to successfully decode the downlink transmission.

[0103] Therefore, turbo-HARQ can achieve residual BLER with at most two HARQ transmissions.The MCS for the first transmission may be based on the periodic CQI report received from the UE 210, and the MCS for the retransmission may be based on the asynchronous CSI report transmitted with the ACK / NACK feedback (eg, super ACK).

[0104] Therefore, the wireless communication system 200 may support various CSI enhancements. Such CSI enhancements may include new CSI reports based on other measurements that provide additional information (e.g., based on PDCCH / PDSCH decoding). This may support providing CSI feedback for PDCCH. This may include supporting downlink triggered CSI-RS reporting to reduce latency and increase reliability. For example, in a downlink DCI, a CSI trigger field (e.g., a Z bit) may be used to indicate a CSI trigger (which may include a CSI report setting and a CSI-RS resource setting). In some configurations, the UE 210 may send CSI plus ACK information in the same PUCCH resource. In another configuration, the UE 210 may send CSI and ACK in separate PUCCH resources.

[0105] Therefore, turbo-HARQ may be beneficial in many scenarios. Example scenarios may include deep fading situations (e.g., when the channel enters a deep fade, turbo HARQ helps the network device 205 to better understand the channel quickly and adjust accordingly). Another example scenario may include an interference situation where the interference is bursty. Another example scenario may include improved resource block / resource allocation when the inner loop CQI is driven by: SRS-based MCS (e.g., this is the case, especially when the network device 205 receiver experiences different noise / interference characteristics from the UE 210 side) and / or SRS / CSI-RS with high periodicity (e.g., having fast feedback based on PDSCH can simultaneously help the outer loop for the next transmission or quickly mitigate interference during bursty interference during retransmissions).

[0106] The wireless communication system 200 may support estimating the SNR based on the PDSCH. However, estimating the SNR of the channel using the DMRS portion of the PDSCH may not be an option. The log-likelihood ratio (LLR) technique for such SNR estimation may use an LLR-based metric that may be useful only when there is an ACK for a downlink transmission (e.g., when the UE is able to successfully receive and decode the downlink transmission) because once there is a BLER or NACK, the LLR metric becomes useless, and the input LLR and the output LLR are not representative.

[0107] Thus, aspects of the described technology provide a method for determining the SNR based on a NACKed transport block (TB) (e.g., a downlink transmission). In some aspects, this may include determining an estimate of the SNR using a parity check that has a low-density parity check (LDPC) number of checks that have a direct connection to the actual SNR of the signal. The SNR may then be mapped to the MCS using an average of unchecked parity bits versus an SNR curve for different MCS levels, or using a link curve for a given target BLER. This may enable the UE 210 to determine the best MCS to be used by the network device 205 in a retransmission to zero out channel errors.

[0108] That is, since the output LLR of the decoder of UE 210 is erroneous and useless when BLER exists, previous methods cannot be used because they rely on the assumption that the output LLR is error-free (e.g., with a high probability). Attempting to estimate the SNR using each LLR zero crossing and mapping the metric to the estimated SNR is inaccurate (e.g., showing a bell-shaped relationship with the SNR). Therefore, aspects of the described technology may count the number of parity bits checked for each downlink transmission. UE 210 may map the number of parity bits checked to the SNR curve to determine a more accurate SNR of the channel to be provided in the feedback message. Since the number of parity bits checked is directly related to the actual bit error rate of the downlink transmission, the more parity bits checked, the greater the confidence that the data is correctly decoded. When all parity bits have been checked (e.g., by parity check), this means that the downlink transmission is error-free and the mapping of MCS to the channel is correct for the channel. However, since there are several parity bits that are not checked (eg, fail parity check), this may be a better indicator of the actual channel quality (eg, SNR), which can be used to more appropriately map the highest MCS to the channel conditions for retransmissions.

[0109] Therefore, the network device 205 may send a downlink transmission (e.g., PDCCH and / or PDSCH) to the UE 210. The downlink transmission may include a parity bit set. The UE 210 and the network device 205 may each know the number of parity bits in the parity bit set of each rate-matched transport block. For example, some control / information bits may be backed up by multiple parity bits (e.g., in the F bit in the transport block, the G bit may carry data / control information, and the H bit may carry parity information). The UE 210 may identify or otherwise determine the number of parity checks that do not pass or meet the parity check procedure in the parity bit set. For example, the UE 210 may attempt to decode the downlink transmission (e.g., a TB carrying information including parity bits) using the parity bit set. The UE 210 may iteratively attempt to decode the downlink transmission using an encoder / decoder function / component, which uses the parity bit to confirm that the information / control bit has been successfully recovered from the downlink transmission.

[0110] Broadly speaking, the number of parity checks that fail to pass or meet the parity check procedure may be based on various metrics. For example, a first metric may include UE 210 identifying or otherwise determining the number of parity checks based on the number of parity checks that meet the parity check procedure (e.g., the number of parity checks that meet / check). Another example metric may include UE 210 identifying or otherwise determining the number of parity checks that fail to pass the parity check procedure (e.g., the number of parity checks that do not meet / check). Another example metric may include UE 210 identifying or otherwise determining the ratio of parity checks that meet the parity check procedure to parity checks that fail to pass the parity check procedure (e.g., the percentage / ratio of parity checks that do not meet / check relative to all parity checks sent on the downlink). Another example metric may include UE 210 identifying or otherwise determining the ratio of the total number of parity checks that meet / check the parity check procedure to the total number of parity checks sent for the downlink (e.g., the percentage / ratio of parity checks that meet / check relative to all parity checks sent on the downlink).

[0111] In some examples, UE 210 may iteratively attempt to decode the downlink transmission. For example, UE 210 may use the parity bits of the downlink transmission to perform iterations of the parity check procedure. UE 210 may identify or otherwise determine the number of parity checks after a particular iteration of the attempted decoding procedure. For example, UE 210 may identify the number of parity checks after each iteration of the parity check procedure, after the last iteration of the parity check procedure, and / or after a certain intermediate iteration of the parity check procedure. Therefore, a metric of the number of parity checks that do not pass or meet the parity check procedure may be calculated at each iteration of the decoder, after the last iteration of the decoder, and / or at a particular iteration of the decoder (e.g., after the first iteration, the 15th iteration, or other iterations).

[0112] UE 210 may also identify or otherwise determine (e.g., based on the results of the attempted decoding) a feedback status indicator (e.g., ACK / NACK) for the downlink transmission. For example, UE 210 may determine whether it is able to successfully receive and decode the downlink transmission (e.g., PDCCH and / or PDSCH), for example, based on a parity check and / or other decoding functions / steps. In the event that UE 210 is able to successfully receive and decode the downlink transmission, the feedback status indicator may include an ACK indicator. In the event that UE 210 is unable to successfully receive and decode the downlink transmission, the feedback status indicator may include a NACK indicator.

[0113] In some aspects, at which iteration of the parity check procedure the ACK and / or NACK code blocks and / or CBG are stopped and reported, the ACK and / or NACK code blocks and / or CBGs may vary. For example, the network device 205 may configure certain metric reporting options for a given set of iterations for the UE 210, which are based on whether an ACK feedback status indicator or a NACK feedback status indicator is reported. The network device 205 may configure the UE 210 to send metrics (e.g., such as the number and / or ratio of successful and / or unsuccessful parity checks relative to the total number of parity checks performed for downlink transmission) at iterations 1, 5, and 8, for example, or at iterations 16 and 18 for NACK, for example. The network device 205 may request the UE 210 to transmit additional information (e.g., CSI) for X iterations, which may use an X1 value for the ACK case and an X2 value for the NACK case). Such requests may be signaled from the network device 205 to the UE 210 using various configuration signaling (such as RRC signaling, MAC CE signaling, or DCI). Furthermore, the network device 205 may request the UE 210 to report in additional information (eg, metrics) for multiple iterations, such as iterations 1, 4, 18, or another other number of iterations.

[0114] Based on the feedback status indicator (e.g., NACK indicator), UE 210 may also identify or otherwise determine (e.g., in addition to the NACK indication) additional information to be included in the feedback message, the additional information being based on the number of parity checks (e.g., the number of parity checks that passed / failed the parity check procedure). In a broad sense, the additional information may directly and / or indirectly provide information associated with the channel condition. For example, UE 210 may identify or otherwise determine an estimated / empirical BER or an assumed BLER based on the number of parity checks (e.g., based on the ratio of unsatisfied checks, UE 210 may estimate a range of empirical BERs). Network device 205 may use the additional information to update its understanding of the current channel condition, and therefore map a more appropriate MCS to retransmissions to UE 210 (and / or other communications with UE 210) to reduce latency and increase reliability. Therefore, the additional information based on the number of parity checks may include the number of parity checks, the SNR based on the parity checks, and the preferred / requested MCS based on the number of parity checks / SNR.

[0115] In one example, UE 210 may include the number of parity checks (e.g., the number of parity checks that failed / passed or the ratio of parity checks that passed / failed) in the feedback message as additional information. That is, for greater flexibility, UE 210 may signal the number of LDPC bits that failed to be checked, and network device 205 may use the information appropriately.

[0116] In another example, UE 210 may signal an MCS as additional information, which may be identified, determined, or otherwise obtained by mapping the average number of unchecked LDPC parity checks to an SNR and then using a link curve to map the SNR to an MCS for a target BLER. For example, UE 210 may map the number of parity checks to an SNR associated with a channel for downlink transmission. UE 210 may identify or otherwise determine the MCS based on the SNR. In this example, UE 210 may include the MCS as additional information in the feedback message. In some examples, mapping the number of parity checks to the SNR may include UE 210 correlating the number of parity checks with an SNR reference based on iterations of a parity check procedure. UE 210 may identify or otherwise determine the highest MCS supported by the SNR, and signal the best MCS as additional information. In some examples, this may include UE 210 identifying or otherwise determining an estimated BLER for downlink transmission based on the number of parity checks. Based on the estimated BLER, UE 210 can identify or otherwise determine the highest MCS for the channel that achieves or otherwise supports a number of parity checks that meets a threshold (e.g., reduces the number of parity checks that fail the parity check procedure to a very low or zero number).

[0117] In some aspects, a TB (e.g., a downlink transmission) may typically include multiple code block groups (CBGs), wherein each CBG includes multiple code blocks. The UE 210 may attempt to decode the downlink transmission using a decoder. The decoder may attempt to decode each code block of the downlink transmission. The number of parity checks that pass or fail the decoding attempt may be based on each code block (e.g., the number of parity checks is based on the attempt to decode each code block in the CBG of the downlink transmission). That is, each code block of the downlink transmission may be associated with its own number / ratio of parity checks that pass or fail the parity check procedure. The number / ratio of parity checks that pass or fail the parity check procedure may be based on the number of parity bits in the code block. If a CBG (which includes multiple code blocks) cannot be successfully received and decoded, the feedback status indicator may indicate NACK, and the CBG may be retransmitted by the network device 205. Therefore, in some aspects, the feedback status indicator may be based on each CBG. Thus, the additional information provided in the feedback message may include CSI information based on all code blocks on a per CBG basis (e.g., on a per code block and / or CBG basis) and / or may be based on all code blocks across all CBGs (e.g., on a per transport block basis, where the sum of all metrics across all code blocks is calculated for all parity checks across all code blocks). As discussed, the number of parity checks may generally indicate the number and / or ratio of successful and / or failed parity checks.

[0118] In some aspects, a TB (e.g., a downlink transmission) may typically include multiple layers (e.g., spatial layers, antenna ports, beamforming groups, etc.). The UE 210 may attempt to decode the downlink transmission using a decoder. The UE may calculate the number / ratio of parity checks that pass or fail the parity check procedure, which may depend on all received signals on all layers. Then (e.g., based on the number of downlink transmissions within a given number of layers or TBS or target BLER or a combination thereof), the UE 210 may compare the parity check ratio with the stored ratio with a table / curve of SINR for each MCS, which may be a function of the number of layers and one of the TBS and target BLER for the scheduled transmission, and used to obtain the current SINR for the scheduled MCS. After obtaining the SINR, the UE 210 may use a mapping function / table to convert the SINR to an MCS for a given desired one or more target BLERs for the target BLER.

[0119] Thus, UE 210 may measure the ratio of unsatisfactory parity to total parity. Based on the scheduled downlink transmission (e.g., CBG, TBS, layer, where TBS may be determined based on the current MCS, number of layers, etc.), the link curve may show the ratio of unsatisfactory parity to total parity for each MCS value (where multiple curves are functions of TBS and number of layers). Then, based on the scheduled MCS, the measured ratio of unsatisfactory parity to total parity, and the scheduled transmission target BLER, UE 210 may determine the current SINR. For example, taking the measured SINR and using a line curve showing BLER versus SINR for each MCS, UE 210 may select an MCS for the desired target BLER. As a non-limiting example, an SINR of 20 dB may correspond to using a BLER of 1e-3, resulting in a particular requested MCS. UE 210 may report the MCS for one or more of the target BLERs to the gNB.

[0120] Therefore, in some examples, the additional information carried or otherwise conveyed in the feedback message may be based on each code block. In some examples, UE 210 may report additional information on a per-code block basis for each code block in the downlink transmission. In some examples, UE 210 may report additional information on a worst code block basis. For example, UE 210 may calculate the number of parity checks that failed, the ratio of successful / failed parity checks, or the ratio of failed successful parity checks to the total number of parity checks on a per-code block basis, but then report the worst case metric as additional information (e.g., x worst code blocks, where x is a positive number). Since all code blocks in the downlink transmission will use the same MCS, if any code block retransmission fails (e.g., the retransmitted code block fails the parity check), the channel may not be suitable for communication.

[0121] In some examples, UE 210 may report additional information in the feedback message on a per CBG basis. For example, the decoder of UE 210 will perform a parity check on each code block and then may sum the number / ratio of successful / failed parity checks for code blocks across all code blocks of each CBG for all code blocks in the downlink transmission. The summation may be indicated as additional information carried or otherwise conveyed in the feedback message.

[0122] In some examples, there may be two methods for CBG reporting based on whether the feedback status indicator is ACK or NACK. For ACK CBG, UE 210 may report a worst-case scenario in additional information, such as a metric calculated based on the worst code block (e.g., among all code blocks in the code blocks in the CBG) (e.g., the number of unsatisfied parity checks, or the ratio of unsatisfied / satisfied parity checks relative to the total number of parity checks). For ACK CBG, UE 210 may send an average of all metrics in the additional information (e.g., the ratio of unsatisfied parity checks to satisfied parity checks relative to the total number of parity checks), an average of metrics using the sum of unsatisfied parity checks relative to the sum of the total number of parity checks performed, and / or a separate average for each metric. In some examples, UE 210 may send a worst-case scenario in additional information (e.g., as discussed above for NACK CBG using all code blocks in all ACK CBGs). In some examples, this may be reported in a single CSI report (e.g., in additional information carried in the feedback message). In some examples, UE 210 may report the worst metric for each CBG (e.g., using only code blocks of that CBG) in the additional information. In some aspects, the reporting size of the additional information may be based on which information (e.g., which metric) is reported by UE 210 in the feedback message.

[0123] As a non-limiting example, this may include UE 210 attempting to decode a first code block (or CBG), which results in x unsuccessful parity checks, and then attempting to decode a second code block (or CBG), which results in y unsuccessful parity checks (where x is a number greater than y). In this case, UE 210 may include x as additional information in the feedback message. As another non-limiting example, this may include UE 210 attempting to decode a first code block (or CBG), which results in a ratio of x unsuccessful parity checks to successful parity checks, and then attempting to decode a second code block (or CBG), which results in a ratio of y unsuccessful parity checks to successful parity checks (where x is a number greater than y). In this case, UE 210 may again include x as additional information in the feedback message.

[0124] Therefore, UE 210 may identify or otherwise include additional information in the feedback message, which is based at least in some aspects on the number of parity checks that pass / fail the parity check procedure. In a broad sense, network device 205 and UE 210 may exchange various signaling (e.g., RRC signaling, MAC CE signaling, DCI signaling, or UE auxiliary information signaling) to agree to include the quantization of the number of parity checks as additional information in the feedback message. For example, an indicator value set that may be identified or otherwise agreed to carry or otherwise convey additional information may be included. This may include network device 205 and UE 210 negotiating or otherwise signaling a table that associates the number of LDPC bits sent with certain quantization levels and / or mechanisms that network device 205 and UE 210 will use to quantize the number of LDPC bit parity checks that are not checked. The indicator value may correspond to or otherwise provide information associated with quantizing the number of parity checks that fail / pass the parity check procedure sent for the downlink.

[0125] As a non-limiting example, the indicator value set may include two bits that are included in a feedback message that carries additional information associated with the number of parity checks. In this example, two bits are set to "00" to indicate 1 to 10 as the number of parity checks, are set to "01" to indicate 11 to 20 as the number of parity checks, are set to "10" to indicate 21 to 30 as the number of parity checks, and are set to "11" to cover other cases (e.g., the number of parity checks>30). As another non-limiting example of including four parity bits in a parity bit set, two bits are set to "00" to indicate one as the number of parity checks, are set to "01" to indicate two as the number of parity checks, are set to "10" to indicate three as the number of parity checks, and are set to "11" to indicate four as the number of parity checks. Other examples of indicator value sets may also be used to signal the number / ratio of parity checks that pass / fail a parity check. Thus, the set of indicator values ​​may provide an association between the quantization level and the number of parity bits sent.

[0126] As discussed above, the additional information may signal a preferred MCS and / or estimated SNR / BLER. In this example, the set of indicator values ​​may correspond to different MCS values, SNR values, or BLER values. Since the network device 205 and the UE 210 have negotiated the quantization level / value of the additional information, the network device 205 will know how to appropriately interpret the additional information carried in the feedback message or otherwise conveyed.

[0127] Thus, the network device 205 may receive a feedback message based on the number / ratio of parity checks for parity bits that failed / passed the parity check procedure, which feedback message carries or otherwise conveys, in addition to additional information, a feedback status (e.g., ACK / NACK) for a downlink transmission (e.g., PDCCH and / or PDSCH). The network device 205 may identify or otherwise determine an MCS for communications with the UE 210 (e.g., retransmissions of downlink transmissions and / or for other downlink transmissions) based on the feedback message.

[0128] For example, the network device 205 may recover the number (e.g., actual number and / or ratio) of parity checks that failed / passed the parity check procedure. Based on the number of parity checks carried in the additional information, the network device 205 may identify the highest MCS that can be used to communicate with the UE 210 (e.g., achieving a very low or zero count as the number of parity checks that failed the parity check procedure). As another example, the network device 205 may recover the BLER from the additional information carried in the feedback message. The network device 205 may correlate the BLER indication with an MCS table to identify or otherwise determine the highest MCS to be used for the channel. As another example, the network device 205 may recover the MCS from the additional information carried in the feedback message. The network device 205 may use the indicated MCS as the MCS for communicating with the UE 210.

[0129] Thus, the network device 205 and the UE 210 may use the feedback status indicator (e.g., ACK / NACK indication) carried in the feedback message and the additional information associated with the number of parity checks (e.g., the number / ratio of parity checks that passed or failed the parity check procedure) to improve the MCS selection for communication between the network device 205 and the UE 210. Although these techniques are generally described in the context of a cellular communication link (e.g., a Uu interface), it should be understood that these techniques may also be applied in the context of sidelink communications (e.g., a PC5 interface) performed via a physical sidelink channel. In the context of a sidelink interface, references to the network device 205 and / or the UE 210 may include a sidelink UE. The techniques described herein may also be equally applicable in the context of a relay network (e.g., such as an integrated access and backhaul (IAB) network). In the context of a relay network, references to the network device 205 and / or the UE 210 may include a relay node, an IAB node, a customer premises equipment (CPE), or any network node within the wireless communication system 200.

[0130] Figure 3 An example of a decoding configuration 300 supporting a method for calculating an SNR estimate for a transport block according to aspects of the present disclosure is illustrated. The decoding configuration 300 may implement aspects of the wireless communication system 100 and / or 200. Aspects of the decoding configuration 300 may be implemented at or by a decoder 305, which may be a function / component of a UE as described herein.

[0131] As discussed above, aspects of the described technology may include a network device performing a downlink transmission (e.g., a PDCCH and / or PDSCH transmission) to a UE. In addition to information bits (e.g., control bits and / or data bits), a downlink transmission (e.g., a transport block) may also include a set of parity bits. When attempting to receive and decode a downlink transmission, the UE may use the parity bits (e.g., using a decoder 305). For example, the UE may iteratively feed the bits of the downlink transmission (including the set of parity bits) into a decoder 305, which includes a component / logic that uses the parity bits to perform a parity check to confirm that the information bits are successfully decoded. If the parity check procedure passes, the information bits may be considered to be successfully received and decoded. If the parity check procedure fails, the information bits may be considered to be unsuccessfully received and decoded.

[0132] Based on the result of the parity check procedure, the UE may identify or otherwise determine the number of parity checks in the set of parity check bits that passed or failed the parity check procedure. For example, the number of parity checks may correspond to the number of parity checks that failed the parity check procedure, the number of parity checks that passed the parity check procedure, the ratio of parity checks that passed the parity check procedure to parity checks that failed the parity check procedure, the ratio of parity checks that passed or failed the parity check procedure to the total number of parity check bits in the downlink transmission.

[0133] The UE may also identify or otherwise determine a feedback status indicator for the downlink transmission. Broadly speaking, the feedback status indicator may include ACK or NACK information based on whether the UE was able to successfully receive and decode the downlink transmission. Typically, the feedback status indicator may be based on the number of parity checks (e.g., a failed parity check may indicate that the UE was unable to successfully receive and decode the downlink transmission). The UE may send a feedback message to the network device that carries or otherwise conveys an indication of the feedback status indicator.

[0134] The feedback message may also include additional information based at least in part on the number of parity checks. For example, the additional information carried or otherwise conveyed in the feedback message may include an indication of the number / ratio of parity checks that passed / failed the parity check procedure or information associated with the number / ratio (such as an indicator value). Other examples of additional information may include an estimated SNR / BLER, a maximum MCS.

[0135] Decoding configuration 300 illustrates an example of how the number of parity checks can be related to SNR, but similar techniques can be applied to estimated BLER or highest MCS. In other examples, multiple tables can be used, where the first table relates the number of parity checks to SNR and the second table relates SNR (or BLER) to the highest MCS.

[0136] For example, the UE and / or network equipment may use Figure 3 , such as the number of parity checks that failed a parity check procedure) is related to the SNR of the channel. This may enable the UE and / or network device to determine a CSI that better understands the channel based on the parity check procedure used to attempt to decode and recover information from the downlink transmission. For example, the UE and / or network device may identify on the graph the curve that most closely corresponds to the highest MCS (e.g., using fewer resource blocks) that results in an acceptable error rate (where only three curves are shown by way of example). Based on the highest MCS corresponding to the number of parity checks, the network device may select an MCS for retransmitting downlink transmissions to the UE and / or for other downlink transmissions to the UE.

[0137] Figure 4 An example of a process 400 supporting a method for calculating an SNR estimate for a transport block according to aspects of the present disclosure is illustrated. The process 400 may implement aspects of the wireless communication system 100 and / or 200 and / or the decoding configuration 300. Aspects of the process 400 may be implemented by and / or at a network device 405 and / or a UE 410, which may be examples of corresponding devices described herein.

[0138] At 415, network device 405 may transmit or otherwise provide (and UE 410 may monitor, receive, or otherwise obtain) a downlink transmission including a set of parity bits. The downlink transmission may correspond to a PDCCH transmission and / or a PDSCH transmission.

[0139] At 420, UE 410 may identify or otherwise determine, for example based on monitoring, the number of parity checks in the set of parity bits that passed or failed the parity check procedure. For example, UE 410 may perform one or more iterations of the parity check procedure on the set of parity check bits sent on the downlink. UE 410 may identify or otherwise determine the number of parity checks after each iteration of the parity check procedure, after the last iteration of the parity check procedure, and / or after some intermediate iteration of the parity check procedure.

[0140] In a broad sense, the number of parity checks may include the number of parity checks that meet the parity check procedures, the number of parity checks that fail the parity check procedures, the ratio of parity checks that meet the parity check procedures to the parity checks that fail the parity check procedures, and the ratio of parity checks that fail the parity check procedures to the total number of parity checks used for downlink transmission.

[0141] At 425, UE 410 may identify or otherwise determine a feedback status indicator for the downlink transmission. Broadly speaking, the feedback status indicator may be based on the number of parity checks and may indicate whether UE 410 is able to successfully receive and decode the downlink transmission. For example, if UE 410 is able to successfully receive and decode the downlink transmission (e.g., at least a threshold number of parity checks pass the parity check procedure), the feedback status indicator may indicate ACK information. If UE 410 is unable to successfully receive and decode the downlink transmission (e.g., a threshold number of successful parity checks are not reached), the feedback status indicator may indicate NACK information. UE 410 may successfully or unsuccessfully receive and decode the downlink transmission based on the parity check procedure performed on the downlink transmission using the parity check bits in the parity check bit set. Therefore, the feedback status indicator may be based on the number of parity checks determined at 420.

[0142] At 430, the UE 410 may send or otherwise provide (and the network device 405 may receive or otherwise obtain) a feedback message that includes a feedback status indicator and additional information based on the number of parity checks. For example, the additional information carried or otherwise conveyed in the feedback message may include an indication of a parity check that satisfies a parity check procedure, an indication of a parity check that fails a parity check procedure, a ratio of a parity check that fails a parity check procedure to a parity check that passes a parity check procedure, a ratio of a parity check that fails a parity check procedure to a total number of parity check procedures performed, and / or a ratio of a parity check that passes a parity check procedure to a total number of parity check procedures performed.

[0143] In some examples, the additional information carried in the feedback message may include only the number of parity checks. In another example, UE 410 may map the number of parity checks to an SNR associated with a channel used for downlink transmission. Based on the SNR, UE 410 may identify an MCS, where the MCS is indicated as additional information in the feedback message. For example, UE 410 may align the number of parity checks with an SNR reference (e.g., such as Figure 3 For example, UE 410 may identify the highest MCS supported by the SNR and indicate the highest MCS as additional information in the feedback message.

[0144] At 435, the network device 405 may identify or otherwise select an MCS for communicating with the UE 410 based on the feedback message. For example, if the feedback status indicator indicates ACK information, the network device 405 may continue to use the current MCS to communicate with the UE 410. However, if the feedback status indicator indicates NACK information, the network device 405 may identify a different MCS to use for communicating with the UE 410. In the case where the additional information includes the number of parity checks, this may include the network device 405 correlating the number of parity checks with the SNR / BLER and then selecting the MCS based on the correlated SNR / BLER. In the case where the additional information includes the SNR / BLER, the network device 405 may select the MCS based on the correlation between the SNR and the MCS. In the case where the additional information includes the MCS, the network device 405 may use the indicated MCS as an updated MCS for communicating with the UE 410. Communications with UE 410 in this context may include retransmissions of original downlink transmissions and / or may include subsequent downlink transmissions to UE 410 .

[0145] Therefore, the network device 405 and the UE 410 can use the feedback status indicator in combination with additional information based on the number of parity checks to improve MCS / resource selection / allocation decisions. This can reduce latency and increase reliability for communications between the network device 405 and the UE 410.

[0146] Figure 5 A block diagram 500 of a device 505 supporting a method for calculating an SNR estimate for a transport block according to aspects of the present disclosure is shown. The device 505 may be an example of aspects of a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0147] The receiver 510 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to methods for calculating SNR estimates for transport blocks, data channels, information channels). The information may be communicated to other components of the device 505. The receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0148] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to methods for calculating SNR estimates for transport blocks, data channels, information channels). In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0149] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the method for calculating an SNR estimate for a transport block as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or components thereof, may support a method for performing one or more of the functions described herein.

[0150] In some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0151] Additionally or alternatively, in some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software). If implemented in code executed by a processor, the functionality of the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), a graphics processing unit (GPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured to or otherwise support means for performing the functions described in the present disclosure).

[0152] In some examples, communication manager 520 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with receiver 510, transmitter 515, or both. For example, communication manager 520 can receive information from receiver 510, transmit information to transmitter 515, or be integrated in conjunction with receiver 510, transmitter 515, or both to receive information, transmit information, or perform various other operations as described herein.

[0153] According to the examples disclosed herein, the communication manager 520 may support wireless communication at the UE. For example, the communication manager 520 may be configured to or otherwise support a component for monitoring a downlink transmission from a network device, the downlink transmission including a parity bit set. The communication manager 520 may be configured to or otherwise support a component for determining the number of parity checks in the parity bit set that do not pass the parity check procedure or satisfy the parity check procedure based on the monitoring. The communication manager 520 may be configured to or otherwise support a component for identifying a feedback status indicator for the downlink transmission based on the monitoring and the number of parity checks. The communication manager 520 may be configured to or otherwise support a component for sending a feedback message based on the number of parity checks, the feedback message including the feedback status indicator and additional information.

[0154] By including or configuring a communication manager 520 according to examples as described herein, a device 505 (e.g., a processor controlling or otherwise coupled to a receiver 510, a transmitter 515, a communication manager 520, or a combination thereof) may support techniques for improving MCS / resource selection / allocation by utilizing the results of a parity check procedure in a decoder as additional information signaled to a network device.

[0155] Figure 6 A block diagram 600 of a device 605 supporting a method for calculating an SNR estimate for a transport block according to aspects of the present disclosure is shown. The device 605 may be an example of aspects of the device 505 or UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0156] The receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to methods for calculating SNR estimates for transport blocks, data channels, information channels). The information may be passed to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0157] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to methods for calculating SNR estimates for transport blocks, data channels, information channels). In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0158] The device 605 or its various components may be examples of components for performing various aspects of the method for calculating the SNR estimate of the transport block as described herein. For example, the communication manager 620 may include a downlink transmission manager 625, a parity check manager 630, a feedback manager 635, or any combination thereof. The communication manager 620 may be an example of various aspects of the communication manager 520 as described herein. In some examples, the communication manager 620 or its various components may be configured to perform various operations (e.g., receive, monitor, transmit) using the receiver 610, the transmitter 615, or both or otherwise in cooperation with the receiver, the transmitter, or both. For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to receive information, transmit information, or perform various other operations as described herein.

[0159] According to the examples disclosed herein, the communication manager 620 may support wireless communication at the UE. The downlink transmission manager 625 may be configured to or otherwise support a component for monitoring a downlink transmission from a network device, the downlink transmission including a parity bit set. The parity check manager 630 may be configured to or otherwise support a component for determining the number of parity checks in the parity check bit set that do not pass the parity check procedure or meet the parity check procedure based on the monitoring. The feedback manager 635 may be configured to or otherwise support a component for identifying a feedback status indicator for the downlink transmission based on the monitoring and the number of the parity checks. The feedback manager 635 may be configured to or otherwise support a component for sending a feedback message based on the number of the parity checks, the feedback message including the feedback status indicator and additional information.

[0160] Figure 7A block diagram 700 of a communication manager 720 supporting a method for calculating an SNR estimate for a transport block according to aspects of the present disclosure is shown. The communication manager 720 may be an example of aspects of the communication manager 520, the communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of the method for calculating an SNR estimate for a transport block as described herein. For example, the communication manager 720 may include a downlink transmission manager 725, a parity manager 730, a feedback manager 735, a mapping manager 740, a parity indication manager 745, a parity iteration manager 750, a parity result manager 755, a signaling manager 760, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0161] According to the examples disclosed herein, the communication manager 720 may support wireless communication at the UE. The downlink transmission manager 725 may be configured to or otherwise support a component for monitoring a downlink transmission from a network device, the downlink transmission including a parity bit set. The parity check manager 730 may be configured to or otherwise support a component for determining the number of parity checks in the parity check bit set that do not pass the parity check procedure or meet the parity check procedure based on the monitoring. The feedback manager 735 may be configured to or otherwise support a component for identifying a feedback status indicator for the downlink transmission based on the monitoring and the number of the parity checks. In some examples, the feedback manager 735 may be configured to or otherwise support a component for sending a feedback message based on the number of the parity checks, the feedback message including the feedback status indicator and additional information.

[0162] In some examples, the mapping manager 740 may be configured to or otherwise support means for mapping the number of parity checks to an SNR associated with a channel for the downlink transmission. In some examples, the mapping manager 740 may be configured to or otherwise support means for identifying a modulation and coding scheme based on the SNR, wherein the additional information in the feedback message is the modulation and coding scheme.

[0163] In some examples, to support mapping the number of parity checks, the mapping manager 740 may be configured to or otherwise support means for correlating the number of parity checks to an SNR reference based on one or more iterations of the parity check procedure. In some examples, to support identifying a modulation and coding scheme, the mapping manager 740 may be configured to or otherwise support means for identifying a highest modulation and coding scheme supported by the SNR. In some examples, to support identifying a modulation and coding scheme, the mapping manager 740 may be configured to or otherwise support means for identifying an estimated block error rate for the downlink transmission based on the number of parity checks.

[0164] In some examples, parity indication manager 745 may be configured or otherwise support means for including the parity number as the additional information in the feedback message.

[0165] In some examples, parity iteration manager 750 may be configured or otherwise support means for performing one or more iterations of the parity check procedure on the set of parity check bits transmitted on the downlink. In some examples, parity iteration manager 750 may be configured or otherwise support means for identifying the number of parity checks after each iteration of the parity check procedure.

[0166] In some examples, parity check iteration manager 750 may be configured or otherwise support means for identifying the number of parity checks after the last iteration of the parity check procedure. In some examples, parity check iteration manager 750 may be configured or otherwise support means for identifying the number of parity checks at an intermediate iteration of the parity check procedure.

[0167] In some examples, parity check result manager 755 may be configured or otherwise support means for identifying the number of parity checks based on the parity checks that satisfy the parity check procedure. In some examples, parity check result manager 755 may be configured or otherwise support means for identifying the number of parity checks based on the parity checks that do not pass the parity check procedure.

[0168] In some examples, the parity check result manager 755 may be configured to or otherwise support a component for identifying the number of parity checks based on a ratio of parity checks that satisfy the parity check procedure to parity checks that fail the parity check procedure. In some examples, the parity check result manager 755 may be configured to or otherwise support a component for identifying the number of parity checks based on a ratio of parity checks that satisfy the parity check procedure to the total number of parity checks sent for the downlink. In some examples, the parity check result manager 755 may be configured to or otherwise support a component for identifying the number of parity checks based on a ratio of parity checks that fail the parity check procedure to the total number of parity checks sent for the downlink.

[0169] In some examples, the parity check result manager 755 may be configured to or otherwise support a component for identifying the number of parity checks based at least in part on a number of layers, a TBS, a target BLER, or any combination thereof associated with the downlink transmission. In some examples, the downlink transmission includes a cellular-based downlink transmission received from a network device (e.g., a Uu interface-based transmission) or a sidelink-based downlink transmission (e.g., a PC5 interface-based transmission) received from a neighboring UE (e.g., a sidelink UE within a threshold range).

[0170] In some examples, the signaling manager 760 may be configured to or otherwise support components for identifying a set of indicator values ​​associated with the number of parity checks based on signaling exchanged with the network device. In some examples, the set of indicator values ​​includes an indicator value corresponding to a quantization of the number of parity checks.

[0171] In some examples, the signaling manager 760 may be configured to or otherwise support means for receiving an indication of the indicator value set from the network device using at least one of RRC signaling, a MAC CE message, a DCI message, a UE assistance information message, or a combination thereof.

[0172] Figure 8A diagram of a system 800 including a device 805 supporting a method for calculating an SNR estimate for a transport block according to various aspects of the present disclosure is shown. The device 805 may be an example of a device 505, a device 605, or a UE 115 as described herein, or include components thereof. The device 805 may communicate wirelessly with one or more network devices 105, UE 115, or any combination thereof. The device 805 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, and a processor 840. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845).

[0173] I / O controller 810 can manage input signals and output signals of device 805. I / O controller 810 can also manage peripheral devices that are not integrated into device 805. In some cases, I / O controller 810 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 810 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 810 may be implemented as part of a processor, such as processor 840. In some cases, a user may interact with device 805 via I / O controller 810 or via hardware components controlled by I / O controller 810.

[0174] In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bidirectionally via one or more antennas 825, wired or wireless links as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. The transceiver 815 or the transceiver 815 and one or more antennas 825 may be examples of transmitters 515, transmitters 615, receivers 510, receivers 610, or any combination thereof or components thereof as described herein.

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

[0176] The processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a GPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting a method for calculating an SNR estimate value for a transport block). For example, the device 805 or a component of the device 805 may include a processor 840 and a memory 830 coupled to the processor 840, and the processor 840 and the memory 830 are configured to perform the various functions described herein.

[0177] According to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. For example, the communication manager 820 may be configured to or otherwise support a component for monitoring a downlink transmission from a network device, the downlink transmission including a parity bit set. The communication manager 820 may be configured to or otherwise support a component for determining the number of parity checks that do not pass a parity check procedure or satisfy the parity check procedure in the parity check bit set based on the monitoring. The communication manager 820 may be configured to or otherwise support a component for identifying a feedback status indicator for the downlink transmission based on the monitoring and the number of parity checks. The communication manager 820 may be configured to or otherwise support a component for sending a feedback message based on the number of parity checks, the feedback message including the feedback status indicator and additional information.

[0178] By including or configuring the communication manager 820 according to examples as described herein, the device 805 may support techniques for improving MCS / resource selection / allocation using the results of the parity check procedure in the decoder as additional information signaled to the network device.

[0179] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions that are executable by the processor 840 to cause the device 805 to perform various aspects of the method for calculating SNR estimates for transport blocks as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.

[0180] Fig. 9 A block diagram 900 of a device 905 supporting a method for calculating an SNR estimate for a transport block according to aspects of the present disclosure is shown. The device 905 may be an example of aspects of a network device 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0181] The receiver 910 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to methods for calculating SNR estimates for transport blocks, data channels, information channels). The information may be passed to other components of the device 905. The receiver 910 may utilize a single antenna or a collection of multiple antennas.

[0182] The transmitter 915 may provide means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to methods for calculating SNR estimates for transport blocks, data channels, information channels). In some examples, the transmitter 915 may be co-located with the receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0183] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the method for calculating an SNR estimate for a transport block as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or components thereof may support a method for performing one or more of the functions described herein.

[0184] In some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0185] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software). If implemented in code executed by a processor, the functionality of the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, a GPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured to or otherwise support means for performing the functionality described in the present disclosure).

[0186] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated in conjunction with the receiver 910, the transmitter 915, or both to receive information, transmit information, or perform various other operations as described herein.

[0187] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a network device. For example, the communication manager 920 may be configured to or otherwise support a component for sending a downlink transmission including a set of parity bits to a UE. The communication manager 920 may be configured to or otherwise support a component for receiving a feedback message from the UE based on the number of parity checks associated with the set of parity bits, the feedback message including a feedback status indicator and additional information, the number of parity checks being based on the parity checks in the set of parity bits that do not pass a parity check procedure or that satisfy the parity check procedure. The communication manager 920 may be configured to or otherwise support a component for selecting a modulation and coding scheme for communicating with the UE based on the feedback message.

[0188] By including or configuring a communication manager 920 according to examples as described herein, a device 905 (e.g., a processor controlling or otherwise coupled to a receiver 910, a transmitter 915, a communication manager 920, or a combination thereof) may support techniques for improving MCS / resource selection / allocation by utilizing the results of a parity check procedure in a decoder as additional information signaled to a network device.

[0189] Fig.10 A block diagram 1000 of a device 1005 supporting a method for calculating an SNR estimate for a transport block according to aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or the network device 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0190] The receiver 1010 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to methods for calculating SNR estimates for transport blocks, data channels, information channels). The information may be communicated to other components of the device 1005. The receiver 1010 may utilize a single antenna or a collection of multiple antennas.

[0191] The transmitter 1015 may provide means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to methods for calculating SNR estimates for transport blocks, data channels, information channels). In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0192] The device 1005 or its various components may be examples of components for performing various aspects of the method for calculating the SNR estimate of the transport block as described herein. For example, the communication manager 1020 may include a downlink transmission manager 1025, a feedback manager 1030, an MCS manager 1035, or any combination thereof. The communication manager 1020 may be an example of various aspects of the communication manager 920 as described herein. In some examples, the communication manager 1020 or its various components may be configured to use the receiver 1010, the transmitter 1015, or both or otherwise cooperate with the receiver, the transmitter, or both to perform various operations (e.g., receive, monitor, send). For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or be integrated with the receiver 1010, the transmitter 1015, or both to receive information, send information, or perform various other operations as described herein.

[0193] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network device. The downlink transmission manager 1025 may be configured to or otherwise support a component for sending a downlink transmission including a set of parity bits to a UE. The feedback manager 1030 may be configured to or otherwise support a component for receiving a feedback message from the UE based on the number of parity checks associated with the set of parity bits, the feedback message including a feedback status indicator and additional information, the number of parity checks being based on the parity checks in the set of parity bits that do not pass a parity check procedure or that satisfy the parity check procedure. The MCS manager 1035 may be configured to or otherwise support a component for selecting a modulation and coding scheme for communicating with the UE based on the feedback message.

[0194] Fig.11 A block diagram 1100 of a communication manager 1120 supporting a method for calculating an SNR estimate for a transport block according to aspects of the present disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of means for performing various aspects of the method for calculating an SNR estimate for a transport block as described herein. For example, the communication manager 1120 may include a downlink transmission manager 1125, a feedback manager 1130, an MCS manager 1135, an SNR manager 1140, a parity check result manager 1145, a signaling manager 1150, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0195] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network device. The downlink transmission manager 1125 may be configured to or otherwise support a component for sending a downlink transmission including a parity bit set to a UE. The feedback manager 1130 may be configured to or otherwise support a component for receiving a feedback message from the UE based on the number of parity checks associated with the parity bit set, the feedback message including a feedback status indicator and additional information, the number of parity checks being based on the parity checks in the parity bit set that do not pass a parity check procedure or satisfy the parity check procedure. The MCS manager 1135 may be configured to or otherwise support a component for selecting a modulation and coding scheme for communicating with the UE based on the feedback message.

[0196] In some examples, SNR manager 1140 may be configured or otherwise support means for identifying the modulation and coding scheme based on the SNR associated with the channel used for the downlink transmission, wherein the additional information in the feedback message is the modulation and coding scheme.

[0197] In some examples, parity check result manager 1145 may be configured to or otherwise support means for identifying the number of parity checks based on the additional information in the feedback message. In some examples, parity check result manager 1145 may be configured to or otherwise support means for identifying the modulation and coding scheme based on the number of parity checks.

[0198] In some examples, the number of parity checks is identified based on the parity checks that satisfy the parity check procedure. In some examples, the number of parity checks is identified based on the parity checks that fail the parity check procedure. In some examples, the number of parity checks is identified based on the ratio of the parity checks that satisfy the parity check procedure to the parity checks that fail the parity check procedure. In some examples, the number of parity checks is identified based on the ratio of the parity checks that satisfy the parity check procedure to the total number of parity checks sent for the downlink. In some examples, the number of parity checks is identified based on the ratio of the parity checks that fail the parity check procedure to the total number of parity checks sent for the downlink.

[0199] In some examples, the signaling manager 1150 may be configured to or otherwise support a means for identifying a set of indicator values ​​associated with the number of parity checks based on signaling exchanged with the UE. In some examples, the set of indicator values ​​includes an indicator value corresponding to a quantization of the number of parity checks. In some examples, the signaling manager 1150 may be configured to or otherwise support a means for sending an indication of the set of indicator values ​​to the UE using at least one of RRC signaling, a medium access control (MAC) control element (CE) message, a DCI message, a UE assistance information message, or a combination thereof.

[0200] Fig.12 A diagram of a system 1200 including a device 1205 supporting a method for calculating an SNR estimate for a transport block according to aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a network device 105 as described herein, or include components thereof. The device 1205 may communicate wirelessly with one or more network devices 105, UEs 115, or any combination thereof. The device 1205 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1220, a network communication manager 1210, a transceiver 1215, an antenna 1225, a memory 1230, a code 1235, a processor 1240, and an inter-station communication manager 1245. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1250).

[0201] The network communications manager 1210 may manage communications with the core network 130 (eg, via one or more wired backhaul links). For example, the network communications manager 1210 may manage the delivery of data communications for client devices, such as one or more UEs 115.

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

[0203] Memory 1230 may include RAM and ROM. Memory 1230 may store computer-readable, computer-executable code 1235 including instructions that, when executed by processor 1240, cause device 1205 to perform various functions described herein. Code 1235 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1235 may not be directly executable by processor 1240, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1230 may include a BIOS, etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0204] Processor 1240 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a GPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1240 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1240. Processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1230) to enable device 1205 to perform various functions (e.g., functions or tasks supporting a method for calculating an SNR estimate value for a transport block). For example, device 1205 or a component of device 1205 may include processor 1240 and memory 1230 coupled to processor 1240, and processor 1240 and memory 1230 are configured to perform various functions described herein.

[0205] The inter-site communication manager 1245 may manage communications with other network devices 105 and may include a controller or scheduler for controlling communications with UE 115 in cooperation with other network devices 105. For example, the inter-site communication manager 1245 may coordinate scheduling of transmissions to UE 115 for various interference mitigation techniques, such as beamforming or joint transmission. In some examples, the inter-site communication manager 1245 may provide an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network devices 105.

[0206] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network device. For example, the communication manager 1220 may be configured to or otherwise support a component for sending a downlink transmission including a set of parity bits to a UE. The communication manager 1220 may be configured to or otherwise support a component for receiving a feedback message from the UE based on the number of parity checks associated with the set of parity bits, the feedback message including a feedback status indicator and additional information, the number of parity checks being based on the parity checks in the set of parity bits that do not pass a parity check procedure or that satisfy the parity check procedure. The communication manager 1220 may be configured to or otherwise support a component for selecting a modulation and coding scheme for communicating with the UE based on the feedback message.

[0207] By including or configuring the communication manager 1220 according to examples as described herein, the device 1205 may support techniques for improving MCS / resource selection / allocation using the results of the parity check procedure in the decoder as additional information signaled to the network device.

[0208] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1215, one or more antennas 1225, or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the processor 1240, the memory 1230, the code 1235, or any combination thereof. For example, the code 1235 may include instructions that are executable by the processor 1240 to cause the device 1205 to perform various aspects of the method for calculating SNR estimates for transport blocks as described herein, or the processor 1240 and the memory 1230 may be otherwise configured to perform or support such operations.

[0209] Fig.13A flow chart illustrating a method 1300 for supporting a method for calculating an SNR estimate for a transport block according to aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0210] At 1305, the method may include: monitoring a downlink transmission from a network device, the downlink transmission including a set of parity bits. The operations of 1305 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 7 The described downlink transmission manager 725 is performed.

[0211] At 1310, the method may include: determining, based on the monitoring, the number of parity checks in the parity bit set that failed the parity check procedure or satisfied the parity check procedure. The operations of 1310 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Figure 7 The parity manager 730 described herein is performed.

[0212] At 1315, the method may include: identifying a feedback status indicator for the downlink transmission based on the monitoring and the number of parity checks. The operations of 1315 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Figure 7 The described feedback manager 735 is executed.

[0213] At 1320, the method may include: sending a feedback message based on the number of parity checks, the feedback message including the feedback status indicator and additional information. The operations of 1320 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1320 may be performed as described in reference to Figure 7 The described feedback manager 735 is executed.

[0214] Fig.14 A flow chart illustrating a method 1400 for supporting a method for calculating an SNR estimate for a transport block according to aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0215] At 1405, the method may include: monitoring a downlink transmission from a network device, the downlink transmission including a set of parity bits. The operations of 1405 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 7 The described downlink transmission manager 725 is performed.

[0216] At 1410, the method may include: determining, based on the monitoring, the number of parity checks in the parity bit set that failed the parity check procedure or satisfied the parity check procedure. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 7 The parity manager 730 described herein is performed.

[0217] At 1415, the method may include mapping the number of parity checks to an SNR associated with a channel used for the downlink transmission. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 7 The described mapping manager 740 is used to perform.

[0218] At 1420, the method may include: identifying a modulation and coding scheme based on the SNR, wherein the additional information in the feedback message is the modulation and coding scheme. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described in reference Figure 7 The described mapping manager 740 is used to perform.

[0219] At 1425, the method may include: identifying a feedback status indicator for the downlink transmission based on the monitoring and the number of parity checks. The operations of 1425 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1425 may be performed as described in reference to Figure 7 The described feedback manager 735 is executed.

[0220] At 1430, the method may include: sending a feedback message based on the number of parity checks, the feedback message including the feedback status indicator and additional information. The operations of 1430 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1430 may be performed as described in reference to Figure 7The described feedback manager 735 is executed.

[0221] Fig.15 A flow chart illustrating a method 1500 for supporting a method for calculating an SNR estimate for a transport block according to aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0222] At 1505, the method may include: monitoring a downlink transmission from a network device, the downlink transmission including a set of parity bits. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 7 The described downlink transmission manager 725 is performed.

[0223] At 1510, the method may include: determining, based on the monitoring, the number of parity checks in the parity bit set that failed the parity check procedure or satisfied the parity check procedure. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 7 The parity manager 730 described herein is performed.

[0224] At 1515, the method may include: identifying a feedback status indicator for the downlink transmission based on the monitoring and the number of parity checks. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Figure 7 The described feedback manager 735 is executed.

[0225] At 1520, the method may include: sending a feedback message based on the number of parity checks, the feedback message including the feedback status indicator and additional information. The operations of 1520 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Figure 7 The described feedback manager 735 is executed.

[0226] At 1525, the method may include: including the number of parity checks as the additional information in the feedback message. The operation of 1525 may be performed according to the examples disclosed herein. In some examples, various aspects of the operation of 1525 may be performed as described in reference Figure 7 The parity check instructions manager 745 described are performed.

[0227] Fig.16 A flow chart illustrating a method 1600 for supporting a method for calculating an SNR estimate for a transport block according to aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a network device or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network device or a component thereof as described in reference to Figures 1 to 4 and Figures 9 to 12 The described network device 105 may be performed. In some examples, the network device may execute an instruction set to control the functional elements of the network device to perform the described functions. Additionally or alternatively, the network device may use dedicated hardware to perform various aspects of the described functions.

[0228] At 1605, the method may include: sending a downlink transmission including a set of parity bits to the UE. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.11 The described downlink transmission manager 1125 is performed.

[0229] At 1610, the method may include: receiving a feedback message from the UE based on the number of parity checks associated with the parity check bit set, the feedback message including a feedback status indicator and additional information, the number of parity checks based on the parity checks in the parity check bit set that do not pass the parity check procedure or satisfy the parity check procedure. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.11 The described feedback manager 1130 is implemented.

[0230] At 1615, the method may include: selecting a modulation and coding scheme for communicating with the UE based on the feedback message. The operations of 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference Fig.11 The described MCS manager 1135 is executed.

[0231] Fig.17 A flow chart illustrating a method 1700 for supporting a method for calculating an SNR estimate for a transport block according to aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a network device or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network device or a component thereof as described in reference to Figures 1 to 4 and Figures 9 to 12 The described network device 105 may be performed. In some examples, the network device may execute an instruction set to control the functional elements of the network device to perform the described functions. Additionally or alternatively, the network device may use dedicated hardware to perform various aspects of the described functions.

[0232] At 1705, the method may include: sending a downlink transmission including a set of parity bits to the UE. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.11 The described downlink transmission manager 1125 is performed.

[0233] At 1710, the method may include: receiving a feedback message from the UE based on the number of parity checks associated with the parity check bit set, the feedback message including a feedback status indicator and additional information, the number of parity checks based on the parity checks in the parity check bit set that do not pass the parity check procedure or satisfy the parity check procedure. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.11 The described feedback manager 1130 is implemented.

[0234] At 1715, the method may include: selecting a modulation and coding scheme for communicating with the UE based on the feedback message. The operations of 1715 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference Fig.11 The described MCS manager 1135 is executed.

[0235] At 1720, the method may include: identifying a set of indicator values ​​associated with the number of parity checks based on signaling exchanged with the UE. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Fig.11 The described signaling manager 1150 is executed.

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

[0237] Aspect 1: A method for wireless communication at a UE, the method comprising: monitoring a downlink transmission from a network device, the downlink transmission comprising a set of parity bits; determining, based at least in part on the monitoring, the number of parity checks in the set of parity bits that fail a parity check procedure or satisfy the parity check procedure; identifying a feedback status indicator for the downlink transmission based at least in part on the monitoring and the number of parity checks; and sending a feedback message based at least in part on the number of parity checks, the feedback message comprising the feedback status indicator and additional information.

[0238] Aspect 2: According to the method of Aspect 1, the method also includes: mapping the number of parity checks to an SNR associated with a channel used for the downlink transmission; and identifying an MCS scheme based at least in part on the SNR, wherein the additional information in the feedback message is the MCS scheme.

[0239] Aspect 3: The method according to aspect 2, wherein mapping the number of parity checks comprises: correlating the number of parity checks with an SNR reference based at least in part on one or more iterations of the parity check procedure.

[0240] Aspect 4: The method according to any one of aspects 2 to 3, wherein identifying the MCS scheme comprises: identifying the highest available MCS scheme supported by the SNR.

[0241] Aspect 5: The method according to any one of aspects 2 to 4, wherein identifying the MCS scheme includes: identifying an estimated block error rate for the downlink transmission based at least in part on the number of parity checks.

[0242] Aspect 6: According to the method according to any one of Aspects 1 to 5, the method further comprises: including the number of parity checks as the additional information in the feedback message.

[0243] Aspect 7: According to the method according to any one of aspects 1 to 6, the method further comprises: performing one or more iterations of the parity check procedure on the set of parity check bits sent in the downlink.

[0244] Aspect 8: The method according to aspect 7, further comprising: identifying the number of parity checks after each iteration of the parity check procedure.

[0245] Aspect 9: The method according to any one of aspects 7 to 8, further comprising: after the last iteration of the parity check procedure, identifying the number of parity checks.

[0246] Aspect 10: The method according to any one of aspects 7 to 9, further comprising: identifying the number of parity checks at an intermediate iteration of the parity check procedure.

[0247] Aspect 11: The method according to any one of aspects 1 to 10, further comprising: identifying the number of parity checks based at least in part on the parity checks satisfying the parity check procedure.

[0248] Aspect 12: The method according to any one of aspects 1 to 11, further comprising: identifying the number of parity checks based at least in part on the parity checks that failed the parity check procedure.

[0249] Aspect 13: The method according to any one of aspects 1 to 12, further comprising: identifying the number of parity checks based at least in part on a ratio of parity checks that satisfy the parity check procedure to parity checks that fail the parity check procedure.

[0250] Aspect 14: According to the method according to any one of aspects 1 to 13, the method also includes: identifying the number of parity checks based at least in part on the ratio of the parity checks that satisfy the parity check procedure to the total number of parity checks used for the downlink transmission.

[0251] Aspect 15: According to the method of any one of Aspects 1 to 14, the method also includes: identifying the number of parity checks based at least in part on the ratio of parity checks that fail the parity check procedure to the total number of parity checks used for the downlink transmission.

[0252] Aspect 16: The method according to any one of aspects 1 to 15, the method further comprising: identifying a set of indicator values ​​associated with the number of parity checks based at least in part on signaling exchanged with the network device.

[0253] Aspect 17: The method according to aspect 16, wherein the set of indicator values ​​includes an indicator value corresponding to a quantization of the number of parity checks.

[0254] Aspect 18: According to the method according to any one of Aspects 16 to 17, the method also includes: receiving an indication of the indicator value set from the network device using at least one of RRC signaling, MAC CE message, DCI message, UE assistance information message, or a combination thereof.

[0255] Aspect 19: According to any one of aspects 16 to 17, the method also includes: identifying the number of parity checks based at least in part on a number of layers, a TBS, a target BLER, or any combination thereof associated with the downlink transmission.

[0256] Aspect 20: The method according to any one of aspects 16 to 17, wherein the downlink transmission comprises a cellular-based downlink transmission received from a network device or a sidelink-based downlink transmission received from a neighboring UE.

[0257] Aspect 21: A method for performing wireless communications at a network device, the method comprising: sending a downlink transmission including a parity bit set to a UE; receiving a feedback message from the UE based at least in part on the number of parity checks associated with the parity bit set, the feedback message comprising a feedback status indicator and additional information, the number of parity checks being based at least in part on the parity checks in the parity bit set that do not pass a parity check procedure or satisfy the parity check procedure; and selecting an MCS scheme for communicating with the UE based at least in part on the feedback message.

[0258] Aspect 22: The method according to Aspect 21 further comprises: identifying the MCS scheme based at least in part on an SNR associated with a channel used for the downlink transmission, wherein the additional information in the feedback message is the MCS scheme.

[0259] Aspect 23: According to the method described in any one of Aspects 21 to 22, the method further includes: identifying the number of parity checks based at least in part on the additional information in the feedback message; and identifying the MCS scheme based at least in part on the number of parity checks.

[0260] Aspect 24: The method according to any one of aspects 21 to 23, wherein the number of parity checks is identified based at least in part on the parity checks satisfying the parity check procedure.

[0261] Aspect 25: The method according to any one of aspects 21 to 24, wherein the number of parity checks is identified based at least in part on the parity checks that failed the parity check procedure.

[0262] Aspect 26: The method according to any one of aspects 21 to 25, wherein the number of parity checks is identified based at least in part on a ratio of parity checks that satisfy the parity check procedure to parity checks that fail the parity check procedure.

[0263] Aspect 27: A method according to any one of aspects 21 to 26, wherein the number of parity checks is identified based at least in part on a ratio of parity checks that satisfy the parity check procedure to a total number of parity checks used for the downlink transmission.

[0264] Aspect 28: The method according to any one of aspects 21 to 27, wherein the number of parity checks is identified based at least in part on a ratio of parity checks that fail the parity check procedure to a total number of parity checks used for the downlink transmission.

[0265] Aspect 29: The method according to any one of aspects 21 to 28, the method further comprising: identifying a set of indicator values ​​associated with the number of parity checks based at least in part on signaling exchanged with the UE.

[0266] Aspect 30: The method according to aspect 29, wherein the set of indicator values ​​includes an indicator value corresponding to a quantization of the number of parity checks.

[0267] Aspect 31: According to the method according to any one of Aspects 29 to 30, the method also includes: using at least one of RRC signaling, MAC CE message, DCI message, UE assistance information message or a combination thereof to send an indication of the indicator value set to the UE.

[0268] Aspect 32: An apparatus for performing wireless communications at a UE, the apparatus comprising: at least one processor; a memory coupled to the at least one processor; and instructions stored in the memory and executable by the at least one processor to cause the apparatus to perform a method according to any one of Aspects 1 to 20.

[0269] Aspect 33: An apparatus for wireless communication at a UE, the apparatus comprising at least one means for performing a method according to any one of aspects 1 to 20.

[0270] Aspect 34: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by at least one processor to perform the method according to any one of aspects 1 to 20.

[0271] Aspect 35: An apparatus for performing wireless communications at a network device, the apparatus comprising: at least one processor; a memory coupled to the at least one processor; and instructions stored in the memory and executable by the at least one processor to cause the apparatus to perform a method according to any one of Aspects 21 to 31.

[0272] Aspect 36: An apparatus for wireless communication at a network device, the apparatus comprising at least one means for performing the method according to any one of aspects 21 to 31.

[0273] Aspect 37: A non-transitory computer-readable medium storing code for wireless communication at a network device, the code comprising instructions executable by at least one processor to perform the method according to any one of aspects 21 to 31.

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

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

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

[0277] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, CPU, GPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0278] The functions described herein can be implemented in the form of hardware, software executed by a processor, or any combination thereof. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, whether it is described in software, firmware, middleware, microcode, hardware description language, or other terms. When implemented in software executed by a processor, the function can be stored on a computer-readable medium as one or more instructions or codes, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software, firmware, hard wiring, or any combination thereof executed by a processor. The features of the implementation function can also be physically located at different locations, including being distributed so that the various parts of the function are implemented at different physical locations.

[0279] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transmitted from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code components and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

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

[0281] The term "determining" encompasses a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), or ascertaining. Additionally, "determining" may include receiving (such as receiving information) or accessing (such as accessing data in a memory). Additionally, "determining" may include resolving, selecting, choosing, establishing, and other such similar actions.

[0282] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0283] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: at least one processor; a memory coupled to the at least one processor; and instructions stored in the memory and executable by the at least one processor to cause the apparatus to: monitoring a downlink transmission from a network device, the downlink transmission comprising a set of parity bits; determining, based at least in part on the monitoring, a number of parity checks in the set of parity bits that failed a parity check procedure or satisfied the parity check procedure; identifying a feedback status indicator for the downlink transmission based at least in part on the monitoring and the number of parity checks; as well as A feedback message is sent based at least in part on the number of parity checks, the feedback message comprising the feedback status indicator and additional information.

2. The apparatus of claim 1 , wherein the instructions are further executable by the at least one processor to cause the apparatus to: mapping the number of parity checks to a signal-to-noise ratio associated with a channel used for the downlink transmission; and A modulation and coding scheme is identified based at least in part on the signal-to-noise ratio, wherein the additional information in the feedback message is the modulation and coding scheme.

3. The apparatus of claim 2, wherein the instructions for mapping the number of parity checks are executable by the at least one processor to cause the apparatus to: The number of parity checks is correlated to a signal-to-noise ratio reference based at least in part on one or more iterations of the parity check procedure.

4. The apparatus of claim 2, wherein the instructions for identifying the modulation and coding scheme are executable by the at least one processor to cause the apparatus to: The highest modulation and coding scheme supported by the signal-to-noise ratio is identified.

5. The apparatus of claim 2, wherein the instructions for identifying the modulation and coding scheme are executable by the at least one processor to cause the apparatus to: An estimated block error rate for the downlink transmission is identified based at least in part on the number of parity checks.

6. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the apparatus to: The number of parity checks is included in the feedback message as the additional information.

7. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the apparatus to: One or more iterations of the parity checking procedure are performed on the set of parity checking bits for the downlink transmission.

8. The apparatus of claim 7, wherein the instructions are further executable by the at least one processor to cause the apparatus to: After each iteration of the parity check procedure, the number of parity checks is identified.

9. The apparatus of claim 7, wherein the instructions are further executable by the at least one processor to cause the apparatus to: After the last iteration of the parity check procedure, the number of parity checks is identified.

10. The apparatus of claim 7, wherein the instructions are further executable by the at least one processor to cause the apparatus to: At an intermediate iteration of the parity check procedure, the number of parity checks is identified.

11. The apparatus of claim 1 , wherein the instructions are further executable by the at least one processor to cause the apparatus to: The number of parity checks is identified based at least in part on the parity checks satisfying the parity check procedure.

12. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the apparatus to: The number of parity checks is identified based at least in part on parity checks that failed the parity check procedure.

13. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the apparatus to: The number of parity checks is identified based at least in part on a ratio of parity checks that satisfy the parity check procedure to parity checks that fail the parity check procedure.

14. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the apparatus to: The number of parity checks is identified based at least in part on a ratio of parity checks that satisfy the parity check procedure to a total number of parity checks used for the downlink transmission.

15. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the apparatus to: The number of parity checks is identified based at least in part on a ratio of parity checks that failed the parity check procedure to a total number of parity checks used for the downlink transmission.

16. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the apparatus to: A set of indicator values ​​associated with the number of parity checks is identified based at least in part on signaling exchanged with the network device.

17. The apparatus of claim 16, wherein the set of indicator values ​​comprises an indicator value corresponding to a quantization of the number of parity checks.

18. The apparatus of claim 16, wherein the instructions are further executable by the at least one processor to cause the apparatus to: An indication of the set of indicator values ​​is received from the network device using at least one of radio resource control (RRC) signaling, a medium access control (MAC) control element (CE) message, a downlink control information (DCI) message, a UE assistance information message, or a combination thereof.

19. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the apparatus to: The number of parity checks is identified based at least in part on a number of layers associated with the downlink transmission, a transport block size (TBS), a target block error rate (BLER), or any combination thereof.

20. The apparatus of claim 1, wherein the downlink transmission comprises a cellular-based downlink transmission received from a network device or a sidelink-based downlink transmission received from a neighboring UE.

21. An apparatus for wireless communication at a network device, the apparatus comprising: at least one processor; a memory coupled to the at least one processor; and instructions stored in the memory and executable by the at least one processor to cause the apparatus to: sending a downlink transmission including a set of parity bits to a user equipment (UE); receiving a feedback message from the UE based at least in part on a number of parity checks associated with the set of parity check bits, the feedback message comprising a feedback status indicator and additional information, the number of parity checks based at least in part on parity checks in the set of parity check bits that fail a parity check procedure or that satisfy the parity check procedure; and A modulation and coding scheme for communicating with the UE is selected based at least in part on the feedback message.

22. The apparatus of claim 21, wherein the instructions are further executable by the at least one processor to cause the apparatus to: The modulation and coding scheme is identified based at least in part on a signal-to-noise ratio associated with a channel used for the downlink transmission, wherein the additional information in the feedback message is the modulation and coding scheme.

23. The apparatus of claim 21, wherein the instructions are further executable by the at least one processor to cause the apparatus to: identifying the number of parity checks based at least in part on the additional information in the feedback message; and The modulation and coding scheme is identified based at least in part on the number of parity checks.

24. The apparatus of claim 21, wherein the number of parity checks is identified based at least in part on parity checks that satisfy the parity check procedure.

25. The apparatus of claim 21, wherein the number of parity checks is identified based at least in part on the parity checks that failed the parity check procedure.

26. The apparatus of claim 21, wherein the number of parity checks is identified based at least in part on a ratio of parity checks that satisfy the parity check procedure to parity checks that fail the parity check procedure.

27. The apparatus of claim 21, wherein the number of parity checks is identified based at least in part on a ratio of parity checks that satisfy the parity check procedure to a total number of parity checks used for the downlink transmission.

28. The apparatus of claim 21, wherein the number of parity checks is identified based at least in part on a ratio of parity checks that failed the parity check procedure to a total number of parity checks used for the downlink transmission.

29. A method for wireless communication at a user equipment (UE), the method comprising: monitoring a downlink transmission from a network device, the downlink transmission comprising a set of parity bits; determining, based at least in part on the monitoring, a number of parity checks in the set of parity bits that failed a parity check procedure or satisfied the parity check procedure; identifying a feedback status indicator for the downlink transmission based at least in part on the monitoring and the number of parity checks; as well as A feedback message is sent based at least in part on the number of parity checks, the feedback message comprising the feedback status indicator and additional information.

30. A method for wireless communication at a network device, the method comprising: sending a downlink transmission including a set of parity bits to a user equipment (UE); receiving a feedback message from the UE based at least in part on a number of parity checks associated with the set of parity check bits, the feedback message comprising a feedback status indicator and additional information, the number of parity checks based at least in part on parity checks in the set of parity check bits that fail a parity check procedure or that satisfy the parity check procedure; and A modulation and coding scheme for communicating with the UE is selected based at least in part on the feedback message.

Images