Dynamically switching between code block level feedback signaling and code block group level feedback signaling

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may communicate a transport block (TB) with a wireless communication device (WCD). The UE may communicate acknowledgement / negative acknowledgement (ACK / NACK) feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a code block (CB) error pattern of the TB. Numerous other aspects are described.

Description

DYNAMICALLY SWITCHING BETWEEN CODE BLOCK LEVEL FEEDBACK SIGNALING AND CODE BLOCK GROUP LEVEL FEEDBACK SIGNALING CROSS-REFERENCE TO RELATED APPLICATION

[0001] This Patent Application claims priority to Indian Patent Application No. 202321087964, filed on December 22, 2023, entitled “DYNAMICALLY SWITCHING BETWEEN CODE BLOCK LEVEL FEEDBACK SIGNALING AND CODE BLOCK GROUP LEVEL FEEDBACK SIGNALING,” and assigned to the assignee hereof. The disclosure of the prior Application is considered part of and is incorporated by reference into this Patent Application. FIELD OF THE DISCLOSURE

[0002] Aspects of the present disclosure generally relate to wireless communication and specifically relate to techniques, apparatuses, and methods for dynamically switching between code block level feedback signaling and code block group level feedback signaling. BACKGROUND

[0003] Wireless communication systems are widely deployed to provide various services that may include carrying voice, text, messaging, video, data, and / or other traffic. The services may include unicast, multicast, and / or broadcast services, among other examples. Typical wireless communication systems may employ multiple-access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (for example, time domain resources, frequency domain resources, spatial domain resources, and / or device transmit power, among other examples). Examples of such multiple-access RATs include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] The above multiple-access RATs have been adopted in various telecommunication standards to provide common protocols that enable different wireless communication devices to communicate on a municipal, national, regional, or global level. An example telecommunication standard is New Radio (NR). NR, which may also be referred to as 5G, is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) may be designed to better support Internet of things (IoT) and reduced capability device deployments, industrial connectivity, millimeter wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial 0097-5130PCT 1network (NTN) deployment, sidelink and other device-to-device direct communication technologies (for example, cellular vehicle-to-everything (CV2X) communication), massive multiple-input multiple-output (MIMO), disaggregated network architectures and network topology expansions, multiple-subscriber implementations, high-precision positioning, and / or radio frequency (RF) sensing, among other examples. As the demand for mobile broadband access continues to increase, further improvements in NR may be implemented, and other radio access technologies such as 6G may be introduced, to further advance mobile broadband evolution. SUMMARY

[0005] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include communicating a transport block (TB) with a wireless communication device (WCD). The method may include communicating acknowledgement / negative acknowledgement (ACK / NACK) feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a code block (CB) error pattern of the TB.

[0006] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include communicating a TB with a UE. The method may include communicating ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB.

[0007] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to communicate a TB with a WCD. The one or more processors may be configured to communicate ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB.

[0008] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to communicate a TB with a UE. The one or more processors may be configured to communicate ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB. 0097-5130PCT 2

[0009] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to communicate a TB with a WCD. The set of instructions, when executed by one or more processors of the UE, may cause the UE to communicate ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to communicate a TB with a UE. The set of instructions, when executed by one or more processors of the network node, may cause the network node to communicate ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for communicating a TB with a WCD. The apparatus may include means for communicating ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for communicating a TB with a UE. The apparatus may include means for communicating ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB.

[0013] Aspects of the present disclosure may generally be implemented by or as a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network node, network entity, wireless communication device, and / or processing system as substantially described with reference to, and as illustrated by, the specification and accompanying drawings.

[0014] The foregoing paragraphs of this section have broadly summarized some aspects of the present disclosure. These and additional aspects and associated advantages will be described hereinafter. The disclosed aspects may be used as a basis for modifying or designing other aspects for carrying out the same or similar purposes of the present disclosure. Such equivalent aspects do not depart from the scope of the appended claims. Characteristics of the aspects disclosed herein, both their organization and method of operation, together with associated 0097-5130PCT 3advantages, will be better understood from the following description when considered in connection with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The appended drawings illustrate some aspects of the present disclosure, but are not limiting of the scope of the present disclosure because the description may enable other aspects. Each of the drawings is provided for purposes of illustration and description, and not as a definition of the limits of the claims. The same or similar reference numbers in different drawings may identify the same or similar elements.

[0016] Fig.1 is a diagram illustrating an example of a wireless communication network in accordance with the present disclosure.

[0017] Fig.2 is a diagram illustrating an example network node in communication with an example user equipment (UE) in a wireless network in accordance with the present disclosure.

[0018] Fig.3 is a diagram illustrating an example disaggregated base station architecture in accordance with the present disclosure.

[0019] Fig.4 is a diagram illustrating an example of a hybrid automatic repeat request process, in accordance with the present disclosure.

[0020] Fig.5 is a diagram illustrating an example of a transport block that is partitioned into one or more code block groups (CBGs) and code blocks (CBs), in accordance with the present disclosure.

[0021] Fig.6 is a diagram illustrating an example of an example algorithm that may be used to switch between CBG-level feedback signaling and CB-level feedback signaling, in accordance with the present disclosure.

[0022] Figs.7A, 7B, 7C, 7D, 7E, 7F, and 7G are diagrams illustrating a first example, a second example, a third example, a fourth example, a fifth example, a sixth example, and a seventh example, respectively, of CB error patterns, in accordance with the present disclosure.

[0023] Fig.8 is a diagram illustrating an example of a wireless communication process between a transmitting device and a receiving device, in accordance with the present disclosure.

[0024] Fig.9 is a diagram illustrating an example process performed, for example, at UE, or an apparatus of a UE, in accordance with the present disclosure.

[0025] Fig.10 is a diagram illustrating an example process performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure.

[0026] Fig.11 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

[0027] Fig.12 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure. 0097-5130PCT 4DETAILED DESCRIPTION

[0028] Various aspects of the present disclosure are described hereinafter with reference to the accompanying drawings. However, aspects of the present disclosure may be embodied in many different forms and is not to be construed as limited to any specific aspect illustrated by or described with reference to an accompanying drawing or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art may appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using various combinations or quantities of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover an apparatus having, or a method that is practiced using, other structures and / or functionalities in addition to or other than the structures and / or functionalities with which various aspects of the disclosure set forth herein may be practiced. Any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0029] Several aspects of telecommunication systems will now be presented with reference to various methods, operations, apparatuses, and techniques. These methods, operations, apparatuses, and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0030] A feedback process, such as a hybrid automatic request (HARQ) process and / or HARQ protocol, may enable a receiving device to correct errors in a received data packet, such as a transport block (TB). In some aspects, a TB may be partitioned into one or more code block groups (CBGs), and each CBG may partitioned into one or more code blocks (CBs), and a HARQ process may manage acknowledgements (ACKs), negative acknowledgements (NACKs), and / or retransmissions at a CBG-level, rather than a TB-level, to mitigate retransmitting an entirety of the TB. To illustrate, the receiving device may identify a failing CB within a particular CBG, and transmit an indication of a NACK that is specific to the particular CBG. Based at least in part on receiving the NACK, the transmitting device may retransmit the data within the particular CBG, rather than the entirety of the TB.

[0031] In some scenarios, however, CBG-level retransmissions may result in the retransmission of multiple CBs that were received without error. For instance, a CBG may 0097-5130PCT 5include five (5) CBs, and the receiving device may receive a particular CBG with one (1) failing CB and four (4) CBs as passing CBs. Based at least in part on using a CBG-level retransmission mechanism, the receiving device may transmit a NACK for the particular CBG, and the transmitting device may retransmit all 5 of the CBs within the CBG, instead of just the 1 failing CB. The retransmission of the 4 passing CBs within the particular CBG may result in needless consumption of air interface resources. The needless consumption of these air interface resource may result in decreased data throughput and / or increased data transfer latencies within a wireless network.

[0032] Various aspects relate generally to dynamically dynamic switching between CB-level feedback signaling and CBG-level feedback signaling. Some aspects more specifically relate to a receiving device in a feedback process, such as a user equipment (UE) and / or a network node, selecting a feedback signaling level that uses fewer air interface resources based at least in part on an error pattern in a received data packet. In some aspects, a UE may communicate a TB with a wireless communication device (WCD). For example, the UE may transmit the TB to and / or receive the TB from a network node using an uplink and / or a downlink, respectively. As another example, the UE may transmit the TB to and / or receive the TB from another UE using a sidelink. In some aspects, the UE may use a feedback process, such as a HARQ process, to manage and / or regulate the TB. The UE may communicate feedback signaling, such as ACK / NACK feedback signaling, for the TB based at least in part on switching from a first level of feedback signaling to a second level of feedback signaling. To illustrate, the UE may analyze a CB error pattern of the CB and switch between the first level of feedback signaling (e.g., CBG-level feedback signaling) and the second level of feedback signaling (e.g., CB-level feedback signaling) based at least in part on the CB error pattern of the TB. To illustrate, the UE may transmit and / or receive the feedback signaling using the selected level of feedback signaling.

[0033] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by dynamically switching between different levels of feedback signaling, such as dynamically switching between CB-level feedback signaling and CBG-level feedback signaling, the described techniques can be used to reduce a number of air interface resources used by a retransmission. For example, a receiving device in a feedback process may select a feedback signaling level that reduces a number of air interface resources used for a retransmission. For instance, the receiving device may analyze an error pattern within a TB (e.g., a CB error pattern), and select the feedback signaling level and / or a reporting format that results in a more efficient retransmission that uses fewer air interface resources relative to other feedback signaling levels and / or reporting formats. Using fewer air interface resources for retransmissions may increase data throughput in a wireless network and / or decrease data transfer latencies within the wireless network. 0097-5130PCT 6

[0034] Multiple-access radio access technologies (RATs) have been adopted in various telecommunication standards to provide common protocols that enable wireless communication devices to communicate on a municipal, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP). 5G NR supports various technologies and use cases including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0035] As the demand for broadband access increases and as technologies supported by wireless communication networks evolve, further technological improvements may be adopted in or implemented for 5G NR or future RATs, such as 6G, to further advance the evolution of wireless communication for a wide variety of existing and new use cases and applications. Such technological improvements may be associated with new frequency band expansion, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, disaggregated network architectures and network topology expansion, device aggregation, advanced duplex communication, sidelink and other device-to- device direct communication, IoT (including passive or ambient IoT) networks, reduced capability (RedCap) UE functionality, industrial connectivity, multiple-subscriber implementations, high-precision positioning, radio frequency (RF) sensing, and / or artificial intelligence or machine learning (AI / ML), among other examples. These technological improvements may support use cases such as wireless backhauls, wireless data centers, extended reality (XR) and metaverse applications, meta services for supporting vehicle connectivity, holographic and mixed reality communication, autonomous and collaborative robots, vehicle platooning and cooperative maneuvering, sensing networks, gesture monitoring, human-brain interfacing, digital twin applications, asset management, and universal coverage applications using non-terrestrial and / or aerial platforms, among other examples. The methods, operations, apparatuses, and techniques described herein may enable one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0036] Fig.1 is a diagram illustrating an example of a wireless communication network 100 in accordance with the present disclosure. The wireless communication network 100 may be or may include elements of a 5G (or NR) network or a 6G network, among other examples. The wireless communication network 100 may include multiple network nodes 110, shown as a network node (NN) 110a, a network node 110b, a network node 110c, and a network node 110d. The network nodes 110 may support communications with multiple UEs 120, shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e. 0097-5130PCT 7

[0037] The network nodes 110 and the UEs 120 of the wireless communication network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, carriers, and / or channels. For example, devices of the wireless communication network 100 may communicate using one or more operating bands. In some aspects, multiple wireless networks 100 may be deployed in a given geographic area. Each wireless communication network 100 may support a particular radio access technology (RAT) (which may also be referred to as an air interface) and may operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include a 4G RAT, a 5G / NR RAT, and / or a 6G RAT, among other examples. In some examples, when multiple RATs are deployed in a given geographic area, each RAT in the geographic area may operate on different frequencies to avoid interference with one another.

[0038] Various operating bands have been defined as frequency range designations FR1 (410 MHz through 7.125 GHz), FR2 (24.25 GHz through 52.6 GHz), FR3 (7.125 GHz through 24.25 GHz), FR4a or FR4-1 (52.6 GHz through 71 GHz), FR4 (52.6 GHz through 114.25 GHz), and FR5 (114.25 GHz through 300 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in some documents and articles. Similarly, FR2 is often referred to (interchangeably) as a “millimeter wave” band in some documents and articles, despite being different than the extremely high frequency (EHF) band (30 GHz through 300 GHz), which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. The frequencies between FR1 and FR2 are often referred to as mid-band frequencies, which include FR3. Frequency bands falling within FR3 may inherit FR1 characteristics or FR2 characteristics, and thus may effectively extend features of FR1 or FR2 into mid-band frequencies. Thus, “sub-6 GHz,” if used herein, may broadly refer to frequencies that are less than 6 GHz, that are within FR1, and / or that are included in mid-band frequencies. Similarly, the term “millimeter wave,” if used herein, may broadly refer to frequencies that are included in mid-band frequencies, that are within FR2, FR4, FR4-a or FR4-1, or FR5, and / or that are within the EHF band. Higher frequency bands may extend 5G NR operation, 6G operation, and / or other RATs beyond 52.6 GHz. For example, each of FR4a, FR4- 1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 may implement dynamic spectrum sharing (DSS), in which multiple RATs (for example, 4G / LTE and 5G / NR) are implemented with dynamic bandwidth allocation (for example, based on user demand) in a single frequency band. It is contemplated that the frequencies included in these operating bands (for example, FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and techniques described herein may be applicable to those modified frequency ranges. 0097-5130PCT 8

[0039] A network node 110 may include one or more devices, components, or systems that enable communication between a UE 120 and one or more devices, components, or systems of the wireless communication network 100. A network node 110 may be, may include, or may also be referred to as an NR network node, a 5G network node, a 6G network node, a Node B, an eNB, a gNB, an access point (AP), a transmission reception point (TRP), a mobility element, a core, a network entity, a network element, a network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0040] A network node 110 may be implemented as a single physical node (for example, a single physical structure) or may be implemented as two or more physical nodes (for example, two or more distinct physical structures). For example, a network node 110 may be a device or system that implements part of a radio protocol stack, a device or system that implements a full radio protocol stack (such as a full gNB protocol stack), or a collection of devices or systems that collectively implement the full radio protocol stack. For example, and as shown, a network node 110 may be an aggregated network node (having an aggregated architecture), meaning that the network node 110 may implement a full radio protocol stack that is physically and logically integrated within a single node (for example, a single physical structure) in the wireless communication network 100. For example, an aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a full radio protocol stack to enable or facilitate communication between a UE 120 and a core network of the wireless communication network 100.

[0041] Alternatively, and as also shown, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 may implement a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same geographic location or in different geographic locations. For example, a disaggregated network node may have a disaggregated architecture. In some deployments, disaggregated network nodes 110 may be used in an integrated access and backhaul (IAB) network, in an open radio access network (O-RAN) (such as a network configuration in compliance with the O-RAN Alliance), or in a virtualized radio access network (vRAN), also known as a cloud radio access network (C-RAN), to facilitate scaling by separating base station functionality into multiple units that can be individually deployed.

[0042] The network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). A CU may host one or more higher layer control functions, such as radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, and / or service data adaptation protocol (SDAP) functions, among other examples. A DU may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and / or one or more higher 0097-5130PCT 9physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some examples, a DU also may host one or more lower PHY layer functions, such as a fast Fourier transform (FFT), an inverse FFT (iFFT), beamforming, physical random access channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, among other examples. An RU may host RF processing functions or lower PHY layer functions, such as an FFT, an iFFT, beamforming, or PRACH extraction and filtering, among other examples, according to a functional split, such as a lower layer functional split. In such an architecture, each RU can be operated to handle over the air (OTA) communication with one or more UEs 120.

[0043] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, a network node 110 may include one or more Near-Real Time (Near-RT) RAN Intelligent Controllers (RICs) and / or one or more Non-Real Time (Non-RT) RICs. In some examples, a CU, a DU, and / or an RU may be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples. A virtual unit may be implemented as a virtual network function, such as associated with a cloud deployment.

[0044] Some network nodes 110 (for example, a base station, an RU, or a TRP) may provide communication coverage for a particular geographic area. In the 3GPP, the term “cell” can refer to a coverage area of a network node 110 or to a network node 110 itself, depending on the context in which the term is used. A network node 110 may support one or multiple (for example, three) cells. In some examples, a network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs 120 having association with the femto cell (for example, UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in- home network node. In some examples, a cell may not necessarily be stationary. For example, the geographic area of the cell may move according to the location of an associated mobile network node 110 (for example, a train, a satellite base station, an unmanned aerial vehicle, or a non-terrestrial network (NTN) network node).

[0045] The wireless communication network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, 0097-5130PCT 10femto network nodes, relay network nodes, aggregated network nodes, and / or disaggregated network nodes, among other examples. In the example shown in Fig.1, the network node 110a may be a macro network node for a macro cell 130a, the network node 110b may be a pico network node for a pico cell 130b, and the network node 110c may be a femto network node for a femto cell 130c.Various different types of network nodes 110 may generally transmit at different power levels, serve different coverage areas, and / or have different impacts on interference in the wireless communication network 100 than other types of network nodes 110. For example, macro network nodes may have a high transmit power level (for example, 5 to 40 watts), whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (for example, 0.1 to 2 watts).

[0046] In some examples, a network node 110 may be, may include, or may operate as an RU, a TRP, or a base station that communicates with one or more UEs 120 via a radio access link (which may be referred to as a “Uu” link). The radio access link may include a downlink and an uplink. “Downlink” (or “DL”) refers to a communication direction from a network node 110 to a UE 120, and “uplink” (or “UL”) refers to a communication direction from a UE 120 to a network node 110. Downlink channels may include one or more control channels and one or more data channels. A downlink control channel may be used to transmit downlink control information (DCI) (for example, scheduling information, reference signals, and / or configuration information) from a network node 110 to a UE 120. A downlink data channel may be used to transmit downlink data (for example, user data associated with a UE 120) from a network node 110 to a UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCHs), and downlink data channels may include one or more physical downlink shared channels (PDSCHs). Uplink channels may similarly include one or more control channels and one or more data channels. An uplink control channel may be used to transmit uplink control information (UCI) (for example, reference signals and / or feedback corresponding to one or more downlink transmissions) from a UE 120 to a network node 110. An uplink data channel may be used to transmit uplink data (for example, user data associated with a UE 120) from a UE 120 to a network node 110. Uplink control channels may include one or more physical uplink control channels (PUCCHs), and uplink data channels may include one or more physical uplink shared channels (PUSCHs). The downlink and the uplink may each include a set of resources on which the network node 110 and the UE 120 may communicate.

[0047] Downlink and uplink resources may include time domain resources (frames, subframes, slots, and / or symbols), frequency domain resources (frequency bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial domain resources (particular transmit directions and / or beam parameters). Frequency domain resources of some bands may be subdivided into bandwidth parts (BWPs). A BWP may be a continuous block of frequency domain resources (for example, a continuous block of resource blocks) that are 0097-5130PCT 11allocated for one or more UEs 120. A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and the downlink BWP may be the same BWP or different BWPs). A BWP may be dynamically configured (for example, by a network node 110 transmitting a DCI configuration to the one or more UEs 120) and / or reconfigured, which means that a BWP can be adjusted in real-time (or near-real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of the one or more UEs 120. This enables more efficient use of the available frequency domain resources in the wireless communication network 100 because fewer frequency domain resources may be allocated to a BWP for a UE 120 (which may reduce the quantity of frequency domain resources that a UE 120 is required to monitor), leaving more frequency domain resources to be spread across multiple UEs 120. Thus, BWPs may also assist in the implementation of lower-capability UEs 120 by facilitating the configuration of smaller bandwidths for communication by such UEs 120.

[0048] As described above, in some aspects, the wireless communication network 100 may be, may include, or may be included in, an IAB network. In an IAB network, at least one network node 110 is an anchor network node that communicates with a core network. An anchor network node 110 may also be referred to as an IAB donor (or “IAB-donor”). The anchor network node 110 may connect to the core network via a wired backhaul link. For example, an Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, an anchor network node 110 may connect to one or more devices of the core network that provide a core access and mobility management function (AMF). An IAB network also generally includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply as IAB nodes (or “IAB-nodes”). Each non-anchor network node 110 may communicate directly with the anchor network node 110 via a wireless backhaul link to access the core network, or may communicate indirectly with the anchor network node 110 via one or more other non-anchor network nodes 110 and associated wireless backhaul links that form a backhaul path to the core network. Some anchor network node 110 or other non-anchor network node 110 may also communicate directly with one or more UEs 120 via wireless access links that carry access traffic. In some examples, network resources for wireless communication (such as time resources, frequency resources, and / or spatial resources) may be shared between access links and backhaul links.

[0049] In some examples, any network node 110 that relays communications may be referred to as a relay network node, a relay station, or simply as a relay. A relay may receive a transmission of a communication from an upstream station (for example, another network node 110 or a UE 120) and transmit the communication to a downstream station (for example, a UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a “multi-hop network.” In the example shown in Fig.1, the network 0097-5130PCT 12node 110d (for example, a relay network node) may communicate with the network node 110a (for example, a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. Additionally or alternatively, a UE 120 may be or may operate as a relay station that can relay transmissions to or from other UEs 120. A UE 120 that relays communications may be referred to as a UE relay or a relay UE, among other examples.

[0050] The UEs 120 may be physically dispersed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. A UE 120 may be, may include, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. A UE 120 may be, include, or be coupled with a cellular phone (for example, a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (for example, a smart watch, smart clothing, smart glasses, a smart wristband, and / or smart jewelry, such as a smart ring or a smart bracelet), an entertainment device (for example, a music device, a video device, and / or a satellite radio), an extended reality (XR) device, a vehicular component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that may communicate via a wireless medium.

[0051] A UE 120 and / or a network node 110 may include one or more chips, system-on-chips (SoCs), chipsets, packages, or devices that individually or collectively constitute or comprise a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or multiple processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs) and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASIC), programmable logic devices (PLDs) (such as field programmable gate arrays (FPGAs)), or other discrete gate or transistor logic or circuitry (all of which may be generally referred to herein individually as “processors” or collectively as “the processor” or “the processor circuitry”). One or more of the processors may be individually or collectively configurable or configured to perform various functions or operations described herein. A group of processors collectively configurable or configured to perform a set of functions may include a first processor configurable or configured to perform a first function of the set and a second processor configurable or configured to perform a second function of the set, or may include the group of processors all being configured or configurable to perform the set of functions. 0097-5130PCT 13

[0052] The processing system may further include memory circuitry in the form of one or more memory devices, memory blocks, memory elements or other discrete gate or transistor logic or circuitry, each of which may include tangible storage media such as random-access memory (RAM) or read-only memory (ROM), or combinations thereof (all of which may be generally referred to herein individually as “memories” or collectively as “the memory” or “the memory circuitry”). One or more of the memories may be coupled (for example, operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) with one or more of the processors and may individually or collectively store processor-executable code (such as software) that, when executed by one or more of the processors, may configure one or more of the processors to perform various functions or operations described herein. Additionally or alternatively, in some examples, one or more of the processors may be preconfigured to perform various functions or operations described herein without requiring configuration by software. The processing system may further include or be coupled with one or more modems (such as a Wi-Fi (for example, IEEE compliant) modem or a cellular (for example, 3GPP 4G LTE, 5G, or 6G compliant) modem). In some implementations, one or more processors of the processing system include or implement one or more of the modems. The processing system may further include or be coupled with multiple radios (collectively “the radio”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled with one or more of multiple antennas. In some implementations, one or more processors of the processing system include or implement one or more of the radios, RF chains or transceivers. The UE 120 may include or may be included in a housing that houses components associated with the UE 120 including the processing system.

[0053] Some UEs 120 may be considered machine-type communication (MTC) UEs, evolved or enhanced machine-type communication (eMTC), UEs, further enhanced eMTC (feMTC) UEs, or enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be simply referred to as “MTC UEs”. An MTC UE may be, may include, or may be included in or coupled with a robot, an uncrewed aerial vehicle, a remote device, a sensor, a meter, a monitor, and / or a location tag. Some UEs 120 may be considered IoT devices and / or may be implemented as NB- IoT (narrowband IoT) devices. An IoT UE or NB-IoT device may be, may include, or may be included in or coupled with an industrial machine, an appliance, a refrigerator, a doorbell camera device, a home automation device, and / or a light fixture, among other examples. Some UEs 120 may be considered Customer Premises Equipment, which may include telecommunications devices that are installed at a customer location (such as a home or office) to enable access to a service provider's network (such as included in or in communication with the wireless communication network 100). 0097-5130PCT 14

[0054] Some UEs 120 may be classified according to different categories in association with different complexities and / or different capabilities. UEs 120 in a first category may facilitate massive IoT in the wireless communication network 100, and may offer low complexity and / or cost relative to UEs 120 in a second category. UEs 120 in a second category may include mission-critical IoT devices, legacy UEs, baseline UEs, high-tier UEs, advanced UEs, full- capability UEs, and / or premium UEs that are capable of ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB), and / or precise positioning in the wireless communication network 100, among other examples. A third category of UEs 120 may have mid-tier complexity and / or capability (for example, a capability between UEs 120 of the first category and UEs 120 of the second capability). A UE 120 of the third category may be referred to as a reduced capacity UE (“RedCap UE”), a mid-tier UE, an NR-Light UE, and / or an NR-Lite UE, among other examples. RedCap UEs may bridge a gap between the capability and complexity of NB-IoT devices and / or eMTC UEs, and mission-critical IoT devices and / or premium UEs. RedCap UEs may include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras that are associated with a limited bandwidth, power capacity, and / or transmission range, among other examples. RedCap UEs may support healthcare environments, building automation, electrical distribution, process automation, transport and logistics, and / or smart city deployments, among other examples.

[0055] In some examples, two or more UEs 120 (for example, shown as UE 120a and UE 120e) may communicate directly with one another using sidelink communications (for example, without communicating by way of a network node 110 as an intermediary). As an example, the UE 120a may directly transmit data, control information, or other signaling as a sidelink communication to the UE 120e. This is in contrast to, for example, the UE 120a first transmitting data in an UL communication to a network node 110, which then transmits the data to the UE 120e in a DL communication. In various examples, the UEs 120 may transmit and receive sidelink communications using peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols. In some deployments and configurations, a network node 110 may schedule and / or allocate resources for sidelink communications between UEs 120 in the wireless communication network 100. In some other deployments and configurations, a UE 120 (instead of a network node 110) may perform, or collaborate or negotiate with one or more other UEs to perform, scheduling operations, resource selection operations, and / or other operations for sidelink communications.

[0056] In various examples, some of the network nodes 110 and the UEs 120 of the wireless communication network 100 may be configured for full-duplex operation in addition to half- 0097-5130PCT 15duplex operation. A network node 110 or a UE 120 operating in a half-duplex mode may perform only one of transmission or reception during particular time resources, such as during particular slots, symbols, or other time periods. Half-duplex operation may involve time-division duplexing (TDD), in which DL transmissions of the network node 110 and UL transmissions of the UE 120 do not occur in the same time resources (that is, the transmissions do not overlap in time). In contrast, a network node 110 or a UE 120 operating in a full-duplex mode can transmit and receive communications concurrently (for example, in the same time resources). By operating in a full-duplex mode, network nodes 110 and / or UEs 120 may generally increase the capacity of the network and the radio access link. In some examples, full-duplex operation may involve frequency-division duplexing (FDD), in which DL transmissions of the network node 110 are performed in a first frequency band or on a first component carrier and transmissions of the UE 120 are performed in a second frequency band or on a second component carrier different than the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for a UE 120 but not for a network node 110. For example, a UE 120 may simultaneously transmit an UL transmission to a first network node 110 and receive a DL transmission from a second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for a network node 110 but not for a UE 120. For example, a network node 110 may simultaneously transmit a DL transmission to a first UE 120 and receive an UL transmission from a second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both a network node 110 and a UE 120.

[0057] In some examples, the UEs 120 and the network nodes 110 may perform MIMO communication. “MIMO” generally refers to transmitting or receiving multiple signals (such as multiple layers or multiple data streams) simultaneously over the same time and frequency resources. MIMO techniques generally exploit multipath propagation. MIMO may be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO may support simultaneous transmission to multiple receivers, referred to as multi-user MIMO (MU-MIMO). Some radio access technologies (RATs) may employ advanced MIMO techniques, such as mTRP operation (including redundant transmission or reception on multiple TRPs), reciprocity in the time domain or the frequency domain, single-frequency- network (SFN) transmission, or non-coherent joint transmission (NC-JT).

[0058] In some aspects, a UE (e.g., a UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may communicate a TB with a WCD; and communicate acknowledgement / negative acknowledgement (ACK / NACK) feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a code block (CB) error pattern of the TB. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein. 0097-5130PCT 16

[0059] In some aspects, a network node (e.g., a network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may communicate a TB with a UE; and communicate ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0060] As indicated above, Fig.1 is provided as an example. Other examples may differ from what is described with regard to Fig.1.

[0061] Fig.2 is a diagram illustrating an example network node 110 in communication with an example UE 120 in a wireless network in accordance with the present disclosure.

[0062] As shown in Fig.2, the network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a through 232t, where t 1), a set of antennas 234 (shown as 234a through 234v, where v 1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, among other examples. In some configurations, one or a combination of the antenna(s) 234, the modem(s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 214, and / or the TX MIMO processor 216 may be included in a transceiver of the network node 110. The transceiver may be under control of and used by one or more processors, such as the controller / processor 240, and in some aspects in conjunction with processor-readable code stored in the memory 242, to perform aspects of the methods, processes, and / or operations described herein. In some aspects, the network node 110 may include one or more interfaces, communication components, and / or other components that facilitate communication with the UE 120 or another network node.

[0063] The terms “processor,” “controller,” or “controller / processor” may refer to one or more controllers and / or one or more processors. For example, reference to “a / the processor,” “a / the controller / processor,” or the like (in the singular) should be understood to refer to any one or more of the processors described in connection with Fig.2, such as a single processor or a combination of multiple different processors. Reference to “one or more processors” should be understood to refer to any one or more of the processors described in connection with Fig.2. For example, one or more processors of the network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of the UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280. 0097-5130PCT 17

[0064] In some aspects, a single processor may perform all of the operations described as being performed by the one or more processors. In some aspects, a first set of (one or more) processors of the one or more processors may perform a first operation described as being performed by the one or more processors, and a second set of (one or more) processors of the one or more processors may perform a second operation described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. Reference to “one or more memories” should be understood to refer to any one or more memories of a corresponding device, such as the memory described in connection with Fig.2. For example, operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or different subsets of the one or more memories.

[0065] For downlink communication from the network node 110 to the UE 120, the transmit processor 214 may receive data (“downlink data”) intended for the UE 120 (or a set of UEs that includes the UE 120) from the data source 212 (such as a data pipeline or a data queue). In some examples, the transmit processor 214 may select one or more MCSs for the UE 120 in accordance with one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process the data (for example, including encoding the data) for transmission to the UE 120 on a downlink in accordance with the MCS(s) selected for the UE 120 to generate data symbols. The transmit processor 214 may process system information (for example, semi-static resource partitioning information (SRPI)) and / or control information (for example, CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and / or control symbols. The transmit processor 214 may generate reference symbols for reference signals (for example, a cell- specific reference signal (CRS), a demodulation reference signal (DMRS), or a channel state information (CSI) reference signal (CSI-RS)) and / or synchronization signals (for example, a primary synchronization signal (PSS) or a secondary synchronization signals (SSS)).

[0066] The TX MIMO processor 216 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, T output symbol streams) to the set of modems 232. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 232. Each modem 232 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for orthogonal frequency division multiplexing ((OFDM)) to obtain an output sample stream. Each modem 232 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time domain downlink signal. The modems 232a through 232t may together 0097-5130PCT 18transmit a set of downlink signals (for example, T downlink signals) via the corresponding set of antennas 234.

[0067] A downlink signal may include a DCI communication, a MAC control element (MAC- CE) communication, an RRC communication, a downlink reference signal, or another type of downlink communication. Downlink signals may be transmitted on a PDCCH, a PDSCH, and / or on another downlink channel. A downlink signal may carry one or more transport blocks (TBs) of data. A TB may be a unit of data that is transmitted over an air interface in the wireless communication network 100. A data stream (for example, from the data source 212) may be encoded into multiple TBs for transmission over the air interface. The quantity of TBs used to carry the data associated with a particular data stream may be associated with a TB size common to the multiple TBs. The TB size may be based on or otherwise associated with radio channel conditions of the air interface, the MCS used for encoding the data, the downlink resources allocated for transmitting the data, and / or another parameter. In general, the larger the TB size, the greater the amount of data that can be transmitted in a single transmission, which reduces signaling overhead. However, larger TB sizes may be more prone to transmission and / or reception errors than smaller TB sizes, but such errors may be mitigated by more robust error correction techniques.

[0068] For uplink communication from the UE 120 to the network node 110, uplink signals from the UE 120 may be received by an antenna 234, may be processed by a modem 232 (for example, a demodulator component, shown as DEMOD, of a modem 232), may be detected by the MIMO detector 236 (for example, a receive (Rx) MIMO processor) if applicable, and / or may be further processed by the receive processor 238 to obtain decoded data and / or control information. The receive processor 238 may provide the decoded data to a data sink 239 (which may be a data pipeline, a data queue, and / or another type of data sink) and provide the decoded control information to a processor, such as the controller / processor 240.

[0069] The network node 110 may use the scheduler 246 to schedule one or more UEs 120 for downlink or uplink communications. In some aspects, the scheduler 246 may use DCI to dynamically schedule DL transmissions to the UE 120 and / or UL transmissions from the UE 120. In some examples, the scheduler 246 may allocate recurring time domain resources and / or frequency domain resources that the UE 120 may use to transmit and / or receive communications using an RRC configuration (for example, a semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure a configured grant (CG) for the UE 120.

[0070] One or more of the transmit processor 214, the TX MIMO processor 216, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, and / or the controller / processor 240 may be included in an RF chain of the network node 110. An RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters 0097-5130PCT 19(ADCs), and / or other devices that convert between an analog signal (such as for transmission or reception via an air interface) and a digital signal (such as for processing by one or more processors of the network node 110). In some aspects, the RF chain may be or may be included in a transceiver of the network node 110.

[0071] In some examples, the network node 110 may use the communication unit 244 to communicate with a core network and / or with other network nodes. The communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, optical fiber, common public radio interface (CPRI), and / or a wired or wireless backhaul, among other examples. The network node 110 may use the communication unit 244 to transmit and / or receive data associated with the UE 120 or to perform network control signaling, among other examples. The communication unit 244 may include a transceiver and / or an interface, such as a network interface.

[0072] The UE 120 may include a set of antennas 252 (shown as antennas 252a through 252r, where r 1), a set of modems 254 (shown as modems 254a through 254u, where u 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, among other examples. One or more of the components of the UE 120 may be included in a housing 284. In some aspects, one or a combination of the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, or the TX MIMO processor 266 may be included in a transceiver that is included in the UE 120. The transceiver may be under control of and used by one or more processors, such as the controller / processor 280, and in some aspects in conjunction with processor-readable code stored in the memory 282, to perform aspects of the methods, processes, or operations described herein. In some aspects, the UE 120 may include another interface, another communication component, and / or another component that facilitates communication with the network node 110 and / or another UE 120.

[0073] For downlink communication from the network node 110 to the UE 120, the set of antennas 252 may receive the downlink communications or signals from the network node 110 and may provide a set of received downlink signals (for example, R received signals) to the set of modems 254. For example, each received signal may be provided to a respective demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use the respective demodulator component to condition (for example, filter, amplify, downconvert, and / or digitize) a received signal to obtain input samples. Each modem 254 may use the respective demodulator component to further demodulate or process the input samples (for example, for OFDM) to obtain received symbols. The MIMO detector 256 may obtain received symbols from the set of modems 254, may perform MIMO detection on the received symbols if applicable, and may provide 0097-5130PCT 20detected symbols. The receive processor 258 may process (for example, decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260 (which may include a data pipeline, a data queue, and / or an application executed on the UE 120), and may provide decoded control information and system information to the controller / processor 280.

[0074] For uplink communication from the UE 120 to the network node 110, the transmit processor 264 may receive and process data (“uplink data”) from a data source 262 (such as a data pipeline, a data queue, and / or an application executed on the UE 120) and control information from the controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receive processor 258 and / or the controller / processor 280 may determine, for a received signal (such as received from the network node 110 or another UE), one or more parameters relating to transmission of the uplink communication. The one or more parameters may include a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, a channel quality indicator (CQI) parameter, or a transmit power control (TPC) parameter, among other examples. The control information may include an indication of the RSRP parameter, the RSSI parameter, the RSRQ parameter, the CQI parameter, the TPC parameter, and / or another parameter. The control information may facilitate parameter selection and / or scheduling for the UE 120 by the network node 110.

[0075] The transmit processor 264 may generate reference symbols for one or more reference signals, such as an uplink DMRS, an uplink sounding reference signal (SRS), and / or another type of reference signal. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, and further processed by the set of modems 254 (for example, for DFT-s-OFDM or CP-OFDM). The TX MIMO processor 266 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, U output symbol streams) to the set of modems 254. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 254. Each modem 254 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for OFDM) to obtain an output sample stream. Each modem 254 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0076] The modems 254a through 254u may transmit a set of uplink signals (for example, R uplink signals or U uplink symbols) via the corresponding set of antennas 252. An uplink signal may include a UCI communication, a MAC-CE communication, an RRC communication, or 0097-5130PCT 21another type of uplink communication. Uplink signals may be transmitted on a PUSCH, a PUCCH, and / or another type of uplink channel. An uplink signal may carry one or more TBs of data. Sidelink data and control transmissions (that is, transmissions directly between two or more UEs 120) may generally use similar techniques as were described for uplink data and control transmission, and may use sidelink-specific channels such as a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0077] One or more antennas of the set of antennas 252 or the set of antennas 234 may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled with one or more transmission or reception components, such as one or more components of Fig.2. As used herein, “antenna” can refer to one or more antennas, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays. “Antenna panel” can refer to a group of antennas (such as antenna elements) arranged in an array or panel, which may facilitate beamforming by manipulating parameters of the group of antennas. “Antenna module” may refer to circuitry including one or more antennas, which may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0078] In some examples, each of the antenna elements of an antenna 234 or an antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit cross-polarized signals. The antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. A spacing between antenna elements may be such that signals with a desired wavelength transmitted separately by the antenna elements may interact or interfere constructively and destructively along various directions (such as to form a desired beam). For example, given an expected range of wavelengths or frequencies, the spacing may provide a quarter wavelength, a half wavelength, or another fraction of a wavelength of spacing between neighboring antenna elements to allow for the desired constructive and destructive interference patterns of signals transmitted by the separate antenna elements within that expected range.

[0079] The amplitudes and / or phases of signals transmitted via antenna elements and / or sub- elements may be modulated and shifted relative to each other (such as by manipulating phase 0097-5130PCT 22shift, phase offset, and / or amplitude) to generate one or more beams, which is referred to as beamforming. The term “beam” may refer to a directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. “Beam” may also generally refer to a direction associated with such a directional signal transmission, a set of directional resources associated with the signal transmission (for example, an angle of arrival, a horizontal direction, and / or a vertical direction), and / or a set of parameters that indicate one or more aspects of a directional signal, a direction associated with the signal, and / or a set of directional resources associated with the signal. In some implementations, antenna elements may be individually selected or deselected for directional transmission of a signal (or signals) by controlling amplitudes of one or more corresponding amplifiers and / or phases of the signal(s) to form one or more beams. The shape of a beam (such as the amplitude, width, and / or presence of side lobes) and / or the direction of a beam (such as an angle of the beam relative to a surface of an antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of the multiple signals relative to each other.

[0080] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, a UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or a different number of antenna elements. As another example, a network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or a different number of antenna elements. Generally, a larger number of antenna elements may provide increased control over parameters for beam generation relative to a smaller number of antenna elements, whereas a smaller number of antenna elements may be less complex to implement and may use less power than a larger number of antenna elements. Multiple antenna elements may support multiple-layer transmission, in which a first layer of a communication (which may include a first data stream) and a second layer of a communication (which may include a second data stream) are transmitted using the same time and frequency resources with spatial multiplexing.

[0081] While blocks in Fig.2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0082] Fig.3 is a diagram illustrating an example disaggregated base station architecture 300 in accordance with the present disclosure. One or more components of the example disaggregated base station architecture 300 may be, may include, or may be included in one or more network nodes (such one or more network nodes 110). The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, 0097-5130PCT 23or that can communicate indirectly with the core network 320 via one or more disaggregated control units, such as a Non-RT RIC 350 associated with a Service Management and Orchestration (SMO) Framework 360 and / or a Near-RT RIC 370 (for example, via an E2 link). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via F1 interfaces. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective RF access links. In some deployments, a UE 120 may be simultaneously served by multiple RUs 340.

[0083] Each of the components of the disaggregated base station architecture 300, including the CUs 310, the DUs 330, the RUs 340, the Near-RT RICs 370, the Non-RT RICs 350, and the SMO Framework 360, may include one or more interfaces or may be coupled with one or more interfaces for receiving or transmitting signals, such as data or information, via a wired or wireless transmission medium.

[0084] In some aspects, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit may communicate bidirectionally with a CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 310 may be deployed to communicate with one or more DUs 330, as necessary, for network control and signaling. Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. For example, a DU 330 may host various layers, such as an RLC layer, a MAC layer, or one or more PHY layers, such as one or more high PHY layers or one or more low PHY layers. Each layer (which also may be referred to as a module) may be implemented with an interface for communicating signals with other layers (and modules) hosted by the DU 330, or for communicating signals with the control functions hosted by the CU 310. Each RU 340 may implement lower layer functionality. In some aspects, real-time and non-real-time aspects of control and user plane communication with the RU(s) 340 may be controlled by the corresponding DU 330.

[0085] The SMO Framework 360 may support RAN deployment and provisioning of non- virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 360 may support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface, such as an O1 interface. For virtualized network elements, the SMO Framework 360 may interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface, such as an O2 interface. A virtualized network element may include, but is not limited to, a CU 310, a DU 330, an RU 340, a non-RT RIC 350, and / or a Near-RT RIC 370. In some aspects, the SMO Framework 360 may communicate with a hardware aspect of a 4G RAN, 0097-5130PCT 24a 5G NR RAN, and / or a 6G RAN, such as an open eNB (O-eNB) 380, via an O1 interface. Additionally or alternatively, the SMO Framework 360 may communicate directly with each of one or more RUs 340 via a respective O1 interface. In some deployments, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0086] The Non-RT RIC 350 may include or may implement a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence and / or machine learning (AI / ML) workflows including model training and updates, and / or policy- based guidance of applications and / or features in the Near-RT RIC 370. The Non-RT RIC 350 may be coupled to or may communicate with (such as via an A1 interface) the Near-RT RIC 370. The Near-RT RIC 370 may include or may implement a logical function that enables near-real- time control and optimization of RAN elements and resources via data collection and actions via an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, and / or an O-eNB with the Near-RT RIC 370.

[0087] In some aspects, to generate AI / ML models to be deployed in the Near-RT RIC 370, the Non-RT RIC 350 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 370 and may be received at the SMO Framework 360 or the Non-RT RIC 350 from non-network data sources or from network functions. In some examples, the Non-RT RIC 350 or the Near-RT RIC 370 may tune RAN behavior or performance. For example, the Non-RT RIC 350 may monitor long-term trends and patterns for performance and may employ AI / ML models to perform corrective actions via the SMO Framework 360 (such as reconfiguration via an O1 interface) or via creation of RAN management policies (such as A1 interface policies).

[0088] As indicated above, Fig.3 is provided as an example. Other examples may differ from what is described with regard to Fig.3.

[0089] The network node 110, the controller / processor 240 of the network node 110, the UE 120, the controller / processor 280 of the UE 120, the CU 310, the DU 330, the RU 340, or any other component(s) of Figs.1, 2, or 3 may implement one or more techniques or perform one or more operations associated with dynamically switching between code block level feedback signaling and code block group level feedback signaling, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, any other component(s) of Fig.2, the CU 310, the DU 330, or the RU 340 may perform or direct operations of, for example, process 900 of Fig.9, process 1000 of Fig.10, or other processes as described herein (alone or in conjunction with one or more other processors). The memory 242 may store data and program codes for the network node 110, the network node 110, the CU 310, the DU 330, or the RU 340. The memory 282 may 0097-5130PCT 25store data and program codes for the UE 120. In some examples, the memory 242 or the memory 282 may include a non-transitory computer-readable medium storing a set of instructions (for example, code or program code) for wireless communication. The memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same type or of different types). The memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same type or of different types). For example, the set of instructions, when executed (for example, directly, or after compiling, converting, or interpreting) by one or more processors of the network node 110, the UE 120, the CU 310, the DU 330, or the RU 340, may cause the one or more processors to perform process 900 of Fig.9, process 1000 of Fig.10, or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions, among other examples.

[0090] In some aspects, a UE (e.g., a UE 120) includes means for communicating a TB with a WCD; and / or means for communicating ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB. The means for the UE to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0091] In some aspects, a network node (e.g., a network node 110) includes means for communicating a TB with a UE; and / or means for communicating ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB. The means for the network node to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0092] Fig.4 is a diagram illustrating an example 400 of a HARQ process, in accordance with the present disclosure.

[0093] A MAC layer of a protocol stack may implement a HARQ protocol to provide a faster retransmission mechanism relative to other retransmission mechanisms, such as a radio link control (RLC) layer retransmission system. In some aspects, the HARQ protocol may include a transmitting device using a retransmission protocol in combination with a receiving device, such as a send and wait (SAW) protocol that enables the receiving device to recover and / or correct data errors in a first HARQ process without hindering data transmissions in a second HARQ process. Accordingly, multiple HARQ processes may operate in parallel, and data errors identified in the 0097-5130PCT 26first HARQ process may not hinder transmissions in the second HARQ process. Some non- limiting examples of transmitting device-receiving device pairs that may implement a HARQ process in combination may include a network node 110 and a UE 120 (e.g., a downlink HARQ process), a UE 120 and a network node 110 (e.g., an uplink HARQ process), and / or a first UE 120 and a second UE 120 (e.g., a sidelink HARQ process). Thus, a HARQ process may be used for downlink communications, uplink communications, and / or sidelink communications. In some aspects, and as part of a HARQ process, a network node may transmit information in downlink control information (DCI) that indicates to a receiving device (e.g., a UE 120) which downlink transmission(s) and / or which uplink transmissions to process using a HARQ protocol. Alternatively, or additionally, and as part of the HARQ process, a first UE may transmit information in sidelink control information (SCI) that indicates, to a second UE, which sidelink transmission(s) to process using the HARQ protocol.

[0094] In some aspects, a HARQ process and / or HARQ protocol may enable a receiving device to correct errors in a received data packet, such as by correcting errors within a TB based at least in part on soft combining packets in a physical (PHY) layer as described below. In some aspects, a TB may be partitioned into one or more code block groups (CBGs), and each CBG may partitioned into one or more code blocks (CBs) as described with regard to Fig.5. To correct for errors, the receiving device may buffer one or more data packets that have been identified as including an error, combine the data packets, and process the combined data packets to reduce errors. In some aspects, “codeword (CW)” may refer to a TB that includes error protection, and a transmission may include multiple CWs.

[0095] The example 400 includes transactions between a transmitting device and a receiving device. Transactions and / or data located above dashed line 402 are performed by, and / or reside at, a transmitting device (e.g., a network node 110 for a downlink HARQ process, a UE 120 for an uplink HARQ process, and / or a first UE 120 for a sidelink HARQ process). Transactions and / or data located below the dashed line 402 are performed by, and / or reside at, a receiving device (e.g., a UE 120 for a downlink HARQ process, a network node 110 for an uplink HARQ process, and / or a second UE 120 for a sidelink HARQ process). As shown by reference number 404, the transmitting device may transmit a first data packet 406 that is a new transmission of data that is included in the first data packet 406 (e.g., a first transmission of the data, shown through the use of solid white). In some aspects, the transmitting device may buffer and / or store the first data packet 406 as part of a HARQ process until receiving an indication from the receiving device that the first data packet 406 has been received and / or recovered with minimal errors (e.g., error- free and / or a number of errors that satisfy a low threshold). Based at least in part on receiving the first data packet 406 with minimal errors, the receiving device may transmit an acknowledgement (ACK) to the transmitting device as shown by reference number 408, such as a HARQ acknowledgement. The receiving device may validate the first data packet 406 using any suitable 0097-5130PCT 27error detection mechanism., such as a cyclic redundancy check (CRC) process that validates the received data by computing a CRC value using the received data and comparing the computed CRC value(s) to a CRC value included with the received data.

[0096] Based at least in part receiving the ACK, the transmitting device may transmit a second data packet 410 as shown by reference number 412, and the second data packet 410 may be a new transmission of data (e.g., different data than the data included in the first data packet 406). In a similar manner as the first data packet 406, the transmitting device may store the second data packet 410 in the buffer and / or remove the first data packet 406 from the buffer. In some aspects, the receiving device may not receive the second data packet 410 successfully, shown in Fig.4 as data packet 410-1. For example, the receiving device may identify that the data packet 410-1 was received with a number of errors that fail to satisfy the low error threshold. Accordingly, and as shown by reference number 414, the receiving device may transmit a negative acknowledgement (NACK) to indicate that the second data packet 410 was received with errors and / or unsuccessfully. Alternatively, or additionally, the receiving device may transmit the NACK to indicate a request for a retransmission of the second data packet 410. In some aspects, and as shown by reference number 416, the receiving device may store the data packet 410-1 in a buffer 418.

[0097] Based at least in part on receiving the NACK, and as shown by reference number 420, the transmitting device may retransmit the second data packet 410 to the receiving device, where the retransmission is shown by Fig.4 through the use of a dotted pattern. The receiving device may receive the retransmission of the second data packet 410 (shown as data packet 410-2), and, as shown by reference number 422, the receiving device may store the data packet 410-2 in the buffer 418 and / or may combine the data packet 410-1 with the data packet 410-2. As one example, the receiving device may combine the data packet 410-1 and the data packet 410-2 prior to channel decoding and / or error detection, and may process the combined data packet to mitigate errors as shown by reference number 424. That is, by processing the combined data packet, the receiving device may recover data that includes minimal errors (e.g., is error-free and / or includes a number of errors that satisfy the low error threshold). In some aspects, the receiving may combine the data packet 410-1 and the data packet 410-2 using soft combining. “Soft combining” may denote combining multiple received signals based at least in part on a confidence and / or reliability of each received signal, such as by combining received signals using a log likelihood ratio (LLR), to improve a signal quality of the combined data packet and reduce recovery errors.

[0098] In some aspects, the receiving device may transmit an ACK to the transmitting device, such as in scenarios that the receiving device is able to recover a version of the second data packet 410 that includes minimal errors. In other aspects, the receiving device may transmit a NACK to 0097-5130PCT 28the transmitting device, such as in scenarios that the receiving device is unable to recover a version of the second data packet 410 with minimal errors.

[0099] A HARQ process may be used to regulate any combination of PDSCH transmissions, PUSCH transmissions, and / or physical sidelink shared channel (PSSCH) transmissions. Accordingly, the first data packet 406 and / or the second data packet 410 shown by Fig.4 may be based at least in part on one or more PDSCH transmissions, one or more PUSCH transmissions, and / or one or more PSSCH transmissions. For PDSCH transmissions, the receiving device (e.g., a UE 120) may transmit ACK / NACK feedback via PUCCH or PUSCH. For PUSCH transmission, the receiving device (e.g., a network node 110) may transmit ACK / NACK feedback in an uplink grant (e.g., indicated via downlink control information (DCI)). For a sidelink transmission, the receiving device (e.g., a UE 120) may transmit ACK / ACK feedback via a physical sidelink feedback channel (PSFCH).

[0100] As indicated above, Fig.4 is provided as an example. Other examples may differ from what is described with regard to Fig.4.

[0101] Fig.5 is a diagram illustrating an example 500 of a TB 502 that is partitioned into one or more CBGs and CBs, in accordance with the present disclosure.

[0102] Wireless communication devices (WCDs), such as a network node 110 and / or a UE 120, may include respective protocol stacks that enable a first WCD to communicate with a second WCD (and / or vice versa). A protocol stack may include multiple layers, and each layer may provide different functionality to a device. To illustrate, a UE 120 and a network node 110 may include, by way of example and not of limitation, respective PHY layers, medium access control (MAC) layers, radio link control (RLC) layers, packet data convergence protocol (PDCP) layers, and service data adaptation protocol (SDAP) layers. The SDAP layer, PDCP layer, RLC layer, and MAC layer may be collectively referred to as Layer 2 (L2). Thus, in some cases, the SDAP, PDCP, RLC, and MAC layers are referred to as sublayers of Layer 2. The PHY layer may be referred to as Layer 1 (L1).

[0103] The various protocol layers may interact to enable wireless communication between the WCDs. As one example, and on a transmission side (e.g., a UE 120 transmitting an uplink communication and / or a network node 110 transmitting a downlink communication), the SDAP layer may receive a data flow and may map the data flow and / or or control information to radio bearers. Alternatively, or additionally, the SDAP layer may provide the data flows to the PDCP layer via the corresponding radio bearers. The PDCP layer may provide data, in the form of a protocol data unit (PDU), to the RLC layer via RLC channels. The RLC layer may handle transfer of upper layer PDUs to the MAC and / or PHY layers and / or may provide data, mapped to logical channels, to the MAC layer. The MAC layer may package data from logical channels into TBs, and may provide the TBs on one or more transport channels to the PHY layer. The PHY 0097-5130PCT 29layer may handle various operations relating to transmission of a data signal, as described in more detail in connection with Fig.2.

[0104] On the receiving side (e.g., a UE 120 receiving a downlink communication and / or a network node 110 receiving an uplink communication), the operations may be similar to those described for the transmitting side, but reversed. For example, the PHY layer may receive TBs and may provide the TBs on one or more transport channels to the MAC layer. The MAC layer may map the transport channels to logical channels and may provide data to the RLC layer via the logical channels. The RLC layer may map the logical channels to RLC channels and may provide data to the PDCP layer via the RLC channels. The PDCP layer may map the RLC channels to radio bearers and may provide data to the SDAP layer.

[0105] In some aspects, a HARQ process may operate at the PHY layer of a protocol stack and / or a MAC layer of the protocol stack. For example, the PHY layer may perform soft combining of one or more transmissions as described with regard to reference number 424, and the MAC layer may manage retransmissions. The TB 502 is an example TB that may be passed from the MAC layer to the PHY layer for transmission, and / or from the PHY later to the MAC layer after reception. Each TB may be configured to include a single MAC PDU that may include a large number of bits (e.g., greater than 1 megabit (Mbit)). Accordingly, and as shown by Fig.5, a TB may be partitioned into smaller data units, such as n CBGs (shown by Fig.5 as CBG 504-1, CBG 504-2, CBG 504-3, up to CBG 504-n), and each CBG may include a group of k CBs, where n and k are integers. Accordingly, the TB 502 may include m CBs, where m is an integer that may be calculated as m = n * k. Each CB may have a respective CRC value that is generated by a transmitting device and / or is checked by a receiving device to identify bit errors within the CB.

[0106] A HARQ process may perform ACK / NACKs and / or retransmissions at a CBG-level, rather than a TB-level, to mitigate retransmitting an entirety of a TB that may exceed 1 Mbits and to preserve air interface resources. To illustrate, a NACK may be specific to a particular CBG within the TB such that a retransmission includes data within the particular CBG, rather than the entirety of the TB. In some scenarios, however, CBG-level HARQ retransmissions may cause inefficiencies that result in needless consumption of air interface resources. To illustrate, the TB 502 includes a CB error pattern 506 that spans between CBG 504-2 (e.g., CB 5 and CB 7 shown with a dotted pattern) and CBG 504-3 (e.g., CB 8 shown with a dotted pattern). A receiving device may identify these errors using any suitable mechanism, such as via CB CRC failure. In some aspects, the CB error pattern 506 may occur in good channel conditions (e.g., strong signal conditions) based at least in part on data preemption and / or data puncturing of the TB 502. The punctured data inserted into the TB 502 may be data that is directed to another UE and / or higher priority data. Alternatively, or additionally, the CB error pattern 506 may occur based at least in part on a time frequency selective fading condition. 0097-5130PCT 30

[0107] In some aspects, the CB error patterns 506 may be referred to as a sparse error pattern and / or a sparse CB failure pattern based at least in part on a number of failure CBs within the respective CBGs. Using CBG-level feedback signaling, a receiving device may transmit a first NACK for the CBG 504-2 and / or a second NACK for the CBG 504-2, resulting the retransmission of the CBG 504-2 and the CBG 504-3 and, consequently, the retransmission of the entirety of CBs included in the CBG 504-2 and the entirety of the CBs included CBG 504-3, even though some CBs that were recovered without error (e.g., CB 4, CB 6, CB 9, CB 10, and CB 11, shown in solid white). Accordingly, and based at least in part on CBG-level feedback signaling (e.g., CBG-level HARQ feedback signaling) and CBG-level retransmission, the transmitting device may retransmit the CBG 504-2 and the CBG 504-3, and the retransmission of eight (8) CBs when only three (3) CBs where in error. Thus, the retransmission of CBG 504-2 and CBG 504-3 for the CB error pattern 506 results in nearly 70% of the air interface resources being used to needlessly retransmit CBs that were received and / or recovered without error. The needless consumption of these air interface resource may result in decreased data throughput and / or increased data transfer latencies within a wireless network.

[0108] Some techniques and apparatuses described herein provide dynamic switching between CB-level feedback signaling and CBG-level feedback signaling. In some aspects, a UE may communicate a TB with a WCD. For example, the UE may transmit the TB to and / or receive the TB from a network node using an uplink and / or a downlink, respectively. As another example, the UE may transmit the TB to and / or receive the TB from another UE using a sidelink. In some aspects, the UE may use a feedback process, such as a HARQ process, to manage and / or regulate the TB. The UE may communicate feedback signaling, such as ACK / NACK feedback signaling, for the TB based at least in part on switching from a first level of feedback signaling to a second level of feedback signaling. To illustrate, the UE may analyze a CB error pattern of the CB and switch between the first level of feedback signaling (e.g., CBG-level feedback signaling) and the second level of feedback signaling (e.g., CB-level feedback signaling) based at least in part on the CB error pattern of the TB. To illustrate, the UE may transmit and / or receive the feedback signaling using the selected level of feedback signaling.

[0109] Dynamically switching between different levels of feedback signaling, such as dynamically switching between CB-level feedback signaling and CBG-level feedback signaling, may enable a receiving device in a feedback process to select a feedback signaling level that reduces a number of air interface resources used for a retransmission. For instance, the receiving device may analyze an error pattern within a TB (e.g., a CB error pattern), and select the feedback signaling level and / or a reporting format that results in a more efficient retransmission that uses fewer air interface resources relative to other feedback signaling levels and / or reporting formats. 0097-5130PCT 31Using fewer air interface resources for retransmissions may increase data throughput in a wireless network and / or decrease data transfer latencies within the wireless network.

[0110] As indicated above, Fig.5 is provided as an example. Other examples may differ from what is described with regard to Fig.5.

[0111] Fig.6 is a diagram illustrating an example 600 of an example algorithm that may be used to switch between CBG-level feedback signaling and CB-level feedback signaling, in accordance with the present disclosure. “Feedback signaling” may denote ACK / NACK feedback signaling and / or DCI feedback signaling, such as uplink control information (UCI) ACK / NACK feedback signaling for PDSCH and / or code block group transmission information (CBGTI) signaling in DCI for PDSCH and / or PUSCH.

[0112] In some aspects, a wireless computing device (WCD), such as a network node 110 and / UE 120, may implement a flow diagram as described by the example 600 to switch between CBG-level feedback signaling and CB-level feedback signaling to reduce the retransmission of CBs included in a CBG that were received and / or recovered with minimal errors (e.g., error-free and / or a number of errors that satisfy a low threshold). As described above, reducing th the retransmission of error-free and / or reduced errors CBs may preserve air interface resources, increase data throughput in a wireless network, and / or reduce data transfer latencies within the wireless network. The flow diagram included in the example 600 is for discussion purposes, and other implementations may include alternate or additional steps to select between CBG-level feedback signaling and CB-level feedback signaling to improve retransmission efficiency (e.g., reduce a number of air interface resources used by a retransmission).

[0113] As shown by reference number 602, a WCD may initialize one or more variables and / or counters. For instance, the WCD may initialize a counter i to zero (0), where i is an integer that represents an index of a CBG in a TB. For instance, the TB 502 as describe with regard to Fig.5 includes n CBGs that are indexed as CBG(0) (e.g., i = 0 for CBG 504-1), CBG(1) (e.g., i = 1 for CBG 504-2), up to CBG (n-1) (e.g., i = n-1 for CBG 504-n). Alternatively, or additionally, the WCD may initialize a CBG ACK counter and / or a CBG NACK counter (shown as CBG_highly_ACK and CBG_highly_NACK). In some aspects, the CBG ACK counter may track CBGs in a TB that have more CBs with minimal errors than CBs with failing errors (e.g., a number of errors that fail to satisfy the low threshold), and the CBG NACK counter may track CBGs in the TB that have more CBs with failing errors than CBs with minimal errors. A CB with failing errors may alternatively be referred to as a failing CB, and a CB with minimal errors may be referred to as a passing CB.

[0114] As shown by reference number 604, the WCD may analyze the i-th CBG by analyzing each CB included in the i-th CBG to identify the failing CBs. That is, the WCD may analyze the i-th CBG to identify whether the CBG includes one or more failing CBs. Based at least in part on 0097-5130PCT 32the i-th CBG not including a failing CB, the process may follow the “NO” path shown by reference number 606 that includes the WCD incrementing the i counter by 1 as shown by reference number 608 and analyzing the TB to identify whether all CBGs within the TB have been analyzed as shown by reference number 610. In some aspects, the WCD may follow the “NO” path as shown by reference number 612 when some CBGs within the TB have not been analyzed. Accordingly, the WCD may return to the decision box shown by reference number 604 to analyze a next CBG (e.g., the (i+1)-th CBG using the incremented i counter) in the TB. In other aspects, the WCD may follow the “YES” path shown by reference number 614 based at least in part on completing an analysis of all CBGs in the TB to determine whether to use CBG level feedback signaling or CB-level feedback signaling as described below.

[0115] Returning to the decision box shown by reference number 604 and the analysis of the i- th CBG, the WCD may follow the “YES” path as shown by reference number 616 and compare a first number of passing CBs (and / or CB-level ACKs) within the i-th CBG to a second number of failing CBs (and / or CB-level NACKs) within the i-th CBGs as shown by reference number 618. In some aspects, the second number of failing CBs may be based at least in part on a scaling factor and / or percentage (shown as 50%) of the total number of failing CBs within the i-th CBG.

[0116] In some aspects, the scaling factor may be used to tune an efficiency of the example algorithm shown by Fig.6. To illustrate, a first scaling factor may result in a decision point being based at least in part on a number of passing CBs (and / or CB-level ACKs) being higher in count than a number of failing CBs (and / or CB-level NACKs) by a factor greater than one (e.g., the passing CBs are at least twice the amount of failing CBs, triple the amount, and / or quadruple the amount). Accordingly, the number of failing CBs may be referred to as being highly sparse based at least in part on the number of passing CBs being higher in count than the number of failing CBs. In such a scenario, fewer air interface resources may be used for signaling ACK / NACK feedback using the second level of ACK / NACK feedback (e.g., CB-level ACK / NACK feedback) via DCI and / or UCI, resulting in improved air interface resource efficiency relative to using the first level of ACK / NACK feedback. For a second scaling factor, a number of passing CBs (and / or CB-level ACKs) may be lower in count than a number of failing CBs. In such a scenario, more air interface resources may be used to signal feedback using the second level of ACK / NACK feedback via DCI and / or UCI. Accordingly, for the scenario associated with the second scaling factor, using the first level of ACK / NACK feedback signaling may be more efficient (e.g., use fewer air interface resources) relative to using the second level of ACK / NACK feedback signaling. In some aspects, the scaling factor may be tuned and / or selected based on a number of available air interface resources for performing the first level ACK signaling and the second level of ACK / NACK signaling. That is, the scaling factor may be selected based at least in part on optimally matching a cross-over point and / or decision point for using the first level of ACK / NACK feedback signaling and the second level of ACK / NACK feedback signaling to 0097-5130PCT 33obtain more efficient usage of the air interface resource(s). Accordingly, the scaling factor may result in a decision point for switching between feedback signaling levels that balances a number of failing CBs within a CBG and a number of air interface resources that are available for the feedback signaling. For example, the scaling factor may be tuned (e.g., to a value >=50%) to improve efficiency of the algorithm for dynamically switching between CBG-level and CB-level feedback signaling. The scaling factor and / or percentage may be signaled to the WCD and / or may be hardcoded. “Sparse CB failure pattern” may denote that, for a set of CBs, the number of failing CBs within the set of CBs are fewer than the number of passing CBs within the set of CBs by a threshold.

[0117] Based at least in part on the first number of passing CBs being greater or equal to the second number of failing CBs, the WCD may follow the “YES” path shown by reference number 620 and may increment the CBG ACK counter as shown by reference number 622. Alternatively, or additionally, and based at least in part on the first number of passing CBs being less than the second number of failing CBs, the WCD may follow the “NO” path shown by reference number 624 and may increment the CBG NACK counter as shown by reference number 626. In both the “YES” case and the “NO” case, the WCD may proceed by incrementing the i counter as shown by reference number 608 and analyzing the TB to identify whether all CBGs within the TB have been analyzed as shown by reference number 610. In some aspects, the WCD may follow the “NO” path as shown by reference number 612 when some CBGs within the TB have not been analyzed. In other aspects, the WCD may follow the “YES” path shown by reference number 614 based at least in part on completing an analysis of all CBGs in the TB to determine whether to use CBG level feedback signaling or CB-level feedback signaling.

[0118] In some aspects, to determine whether to use CBG-level feedback or CB-level feedback, the WCD may compare the CBG ACK counter to the CBG NACK counter as shown by reference number 628. As one example, the WCD may compare the CBG ACK counter to a weighted and / or scaled version of the CBG NACK counter, shown by Fig.6 as *CBG_highly_NACK, where is a scaling factor (e.g., CBG_sparse_failure_factor). In a similar manner as described with regard to reference number 618, the scaling factor may be selected based at least in part on optimally matching a cross-over point and / or decision point for using the first level of ACK / NACK feedback signaling and the second level of ACK / NACK feedback signaling to obtain more efficient usage of the air interface resource(s). Alternatively, or additionally, the scaling factor may be selected based at least in part on the CB failure pattern (and / or a number of failing CBs) across all CBG within a TB and a number of air interface resources that are available for the feedback signaling. Accordingly, the scaling factor may be tuned to improve efficiency of the algorithm (e.g., a number of air interface resources used for feedback signaling) based at least in part on dynamically switching between CBG-level feedback 0097-5130PCT 34signaling and CB-level feedback signaling. That is, the scaling factor may be tuned to select a switching point that optimizes air interface resource efficiency based at least in part on a number of failing CBs in a TB. The scaling factor may be signaled to the WCD and / or may be hardcoded.

[0119] Based at least in part on computing that the CBG ACK counter is equal to and / or larger than the CBG NACK counter (e.g., the scaled version of the CBG NACK counter), the WCD may follow the “YES” path shown by reference number 630 and select CB-level feedback signaling. By selecting CB-level feedback signaling, the WCD may mitigate the retransmission of one or more CBs within a CBG that were received with minimal errors and preserve air interface resources. Alternatively, or additionally, based at least in part on computing that the CBG ACK counter is less than the CBG NACK counter, the WCD may follow the “NO” path shown by reference number 634 and select CBG-level feedback signaling as shown by reference number 636. By selecting CBG-level feedback signaling, the WCD may reduce an overhead that is used to signal the feedback signaling for a retransmission and preserve air interface resources. Accordingly, the ability to switch between CB-level feedback signaling and CBG-level feedback signaling may enable a WCD to select a level of feedback signaling that reduces air interface resources for a particular error case, such as a first error case that includes more passing CBs relative to failing CBs and / or a second error case that includes fewer passing CBs relative to failing CBs. That is, the WCD may optimize the preservation of air interface resources based at least in part on checking the sparse nature of CB CRC failure across different CBGs.

[0120] For clarity, the example 600 processes the CBGs within a single TB (and / or a single CW), but may alternatively, or additionally be used for a transmission that includes multiple TBs and / or multiple CWs. For instance, a WCD may perform a first pass of the flow diagram (e.g., to completion) for a first TB and / or a first CW included in a transmission to select a first feedback signaling level for the first TB. Alternatively, or additionally, the WCD may perform a second pass of the flow diagram (e.g., to completion) for a second TB and / or a second CW included in the transmission to select a second feedback signaling level for the second TB. Thus, feedback signaling for a transmission that includes multiple TBs and / or multiple CW may use different feedback signaling types for the different TBs.

[0121] As indicated above, Fig.6 is provided as an example. Other examples may differ from what is described with regard to Fig.6.

[0122] Figs.7A, 7B, 7C, 7D, 7E, 7F, and 7G are diagrams illustrating a first example 700, a second example 710, a third example 720, a fourth example 730, a fifth example 740, a sixth example 750, and a seventh example 760, respectively, of CB error patterns, in accordance with the present disclosure. 0097-5130PCT 35

[0123] A WCD, such as a network node 110 and / or a UE 120, may make a determination to dynamically switch between CBG-level feedback signaling (e.g., CBG-level ACK / NACK feedback signaling) and CB-level feedback signaling (e.g., CB-level ACK / NACK feedback signaling), such as by using the flow diagram described with regard to the example 600. Alternatively, or additionally, the WCD may determine a reporting format for CB-level feedback signal based at least in part on a CB error pattern. For instance, the WCD may support multiple reporting formats for CB-level feedback signaling and, consequently, select a particular reporting format from the multiple reporting formats that has increased transmission efficiency relative to the other reporting formats based at least in part on a CB error pattern observed by the WCD. That is, the WCD may select a particular reporting format that results in a retransmission using fewer air interface resources relative to other reporting formats.

[0124] Fig.7A illustrate a first example 700 of a CB error pattern 702 that is a single CB error pattern. Example scenarios that may result a single CB error pattern may include data preemption (e.g., puncturing), high Phase Noise (PN), and / or Remote Interference Management (RIM).

[0125] In a similar manner as described with regard to Fig.4, a TB 704 may include n CBGs (shown as CBG 706-1, CBG 706-2, CBG 706-3, up to CBG 706-n), and each CBG may include k CBs (shown in Fig.7A as k = 5). For discussion purposes, the example 700 is based at least in part on maxCodeBlockGroupsPerTransportBlock (e.g., a configured parameter) being set to 8 such that the TB 704 may include up to 8 CBGs (e.g., n = 8), and a total number of scheduled code blocks (Ncb) in the TB 704 may be 38 (e.g., Ncb = 38). Based at least in part on the maxCodeBlockGroupsPerTransportBlock being set to 8, a total number of available bits for feedback signaling may be 8.

[0126] The WCD may detect the CB error pattern 702 as a single CB error pattern that occurs in CB 15 of the TB 704, and the CB 15 may be absolutely indexed within the TB 704 at index 14 for an indexing system that starts at zero (0). In some aspects, the WCD may select, as the reporting format, a single CB reporting format that includes the WCD signaling the absolute index of the failing CB index in the 8 bits that are available for feedback signaling. In some aspects, the WCD may use fewer bits than the 8 available bits. For example, based at least in part on Ncb = 38, the WCD may calculate a number of bits that are needed to signal the absolute index using the formula: ceil(log2[Ncb]) bits (1) where the ceil(x) function returns the smallest integer value that is greater or equal to x, and log2[y] returns a base 2 logarithm of y. For Ncb=38, the WCD may use six (6) bits of the 8 feedback signaling bits to indicate the absolute index of the failing CB index (e.g., 0011102for an 0097-5130PCT 36index of 14). Accordingly, the single CB reporting format may include the WCD signaling an absolute index (e.g., within the TB) of the single failing CB.

[0127] The second example 710 shown by Fig.7B includes a CB error pattern 712 that may be classified as a first contiguous-CB-based error pattern. Example scenarios that may result in the CB error pattern 712 may include data preemption, PN, RIM, and / or time and frequency selective fading. In the second example 710, CB 8, CB 9, and CB 11 are observed as failing CBs, and CB 10 is observed as a passing CB. Although CB 10 is observed as a passing CB, the WCD may report that the CB 10 is a failing CB via CB-level feedback signaling based at least in part on using an absolute-CB-and-contiguous-CB-number reporting format. That is, the WCD may report that four (4) contiguous CBs have failed and / or may request retransmission of the 4 contiguous CBs using CB-level feedback signaling. Using CB-level signaling and the absolute- CB-and-contiguous-CB-number reporting format may reduce a number of air interface resources used for a retransmission relative to requesting a retransmission of CBG 704-2 and CBG 704-3 using CBG-level feedback signaling. For instance, the retransmissions via the CB-level feedback signaling may mitigate the retransmission of 60% of the CBs included in CBG 704-2 and CBG 704-3 that are passing CBs.

[0128] In some aspects, the absolute-CB-and-contiguous-CB-number reporting format may include signaling an absolute start CB index of a first failing CB in the contiguous block (e.g., CB 8). For instance, using formula (1) above and Ncb = 38 as the total number of CBs within the TB 704: ceil(log2(38)) = 6 the WCD may use 6 bits may be used to signal the absolute start index within the TB of the first failing CB. Accordingly, the absolute start index of CB 8 may be represented as 0001112based at least in part on an indexing scheme that starts at 0. The remaining bits for the absolute-CB-and- contiguous-CB-number reporting format may calculated as: Nrem = maxCodeBlockGroupsPerTransportBlock – ceil(log2[Ncb]) (2) Using the values of maxCodeBlockGroupsPerTransportBlock = 8, and ceil(log2[Ncb]) = 6 in the formula (2): Nrem = 8 – 6 = 2 The absolute-CB-and-contiguous-CB-number reporting format may use two (2) remaining bits to signal a number of contiguous CBs after the starting CB index that are failing CBs. For instance, in Fig.7B, the two remaining bits would be set to 112to indicate that three (3) contiguous CBs 0097-5130PCT 37(e.g., that occur after the first failing CB indicated by the absolute start index) are failing CB. Accordingly, the absolute-CB-and-contiguous-CB-number reporting format includes signaling an absolute start index of a first failing CB and a number of contiguous failing CBs that occur after the first failing CB. In some aspects, the least significant bits (LSB) may be used to indicate the absolute start index and the most significant bits (MSB) may include the number of contiguous failing CBs. To illustrate, for the example 710 shown by Fig 7B, the WCD may signal the absolute start index in the 6 LSBs and the number of contiguous failing CBs in the 2 MSBs as 110001112. However, in other examples, the LSBs may indicate the number of contiguous failing CBs and the MSBs may indicate the start index of the first failing CB.

[0129] The third example 720 shown by Fig.7C includes a CB error pattern 722 that may be classified as a second contiguous-CB-based error pattern. Example scenarios that may result in the CB error pattern 722 may include data preemption, PN, RIM, and / or time and frequency selective fading. In the third example 720, the WCD observes that CB 8, CB 9, CB 11, and CB 12 are failing CBs, and CB 10 is a passing CB. Although CB 10 is observed as a passing CB, the WCD may report that the CB 10 is a failing CB via CB-level feedback signaling based at least in part on using an absolute-CB-and-relative-CB-number reporting format that is CB-level feedback signaling reporting format. That is, the WCD may report that five (5) contiguous CBs have failed and / or may request retransmission of the 5 contiguous CBs using CB-level feedback signaling. Using CB-level signaling and the absolute-CB-and-relative-CB-number reporting format may reduce a number of air interface resources used for the retransmissions relative to requesting a retransmission of CBG 704-2 and CBG 704-3 using CBG-level feedback signaling. For instance, the retransmissions via the CB-level feedback signaling may mitigate the retransmission of 50% of the CBs included in CBG 704-2 and CBG 704-3 that are passing CBs that would otherwise be retransmitting using CBG-level feedback signaling.

[0130] In an absolute-CB-and-relative-CB-number reporting format, the WCD may signal an absolute index of a failing CB that is located in a center and / or middle of the CB error pattern 722. In some aspects, the WCD may use a number of bits that are based at least in part on formula (1) above. As one example, using Ncb = 38 as the total number of CBs within the TB 704: ceil(log2(38)) = 6 the WCD may indicate the absolute index of the center failing CB and / or middle failing CB using 6 bits. In the example 720, CB 10 is located in the center and / or middle of the CB error pattern 722, and the WCD may indicate the absolute index of 10 using 6 bits as: 0010012based at least in part on an indexing scheme that starts at 0. The remaining bits for the absolute-CB-and-relative- CB-number reporting format may calculated by the WCD using formula (2) above. Following the 0097-5130PCT 38previous examples of maxCodeBlockGroupsPerTransportBlock = 8, and ceil(log2[Ncb]) = 6, the WCD may calculate the following number of remaining bits in a feedback signaling field as: Nrem = 8 – 6 = 2 Accordingly, and based at least in part on the absolute-CB-and-relative-CB reporting format, the WCD may use the 2 remaining bits to signal a number of contiguous CB’s in both directions of the center and / or middle CB index (e.g., CB 10) that include failing CBs. For instance, 2 contiguous CBs to the left of CB 10 (e.g., CB 8 and CB 9) are failing CBs, and 2 contiguous CBs to the right of CB 10 (e.g., CB 11 and CB 12) failing CBs. To indicate the number of contiguous failing CBs on each side of the center failing CB (e.g., CB 10), the WCD may set the two remaining bits of the feedback signaling field to 102. Accordingly, the absolute-CB-and-relative- CB-number reporting format may include signaling an absolute index of a center failing CB and a number of contiguous failing CBs on each side of the center failing CB. In some aspects, the LSBs may indicate the starting index and the MSBs may indicate the number of contiguous failing CB. To illustrate, for the example 720, the WCD may signal: 100010012. However, in other examples, the LSBs may indicate the number of contiguous failing CBs on each side of a center failing CB and the MSBs may indicate the absolute index of the center failing CB in the contiguous block of CBs.

[0131] The fourth example 730 shown by Fig.7D includes a CB error pattern 732 that may be classified as a third contiguous-CB-based CB error pattern. Example scenarios that may result in the CB error pattern 732 may include data preemption, PN, RIM, and / or time and frequency selective fading. In the fourth example 730, CB 6 and CB 8 are observed as failing CBs, and CB 7 is observed as a passing CB. In the fourth example 730, the TB 704 includes 8 CBGs (shown as CBG 704-1, CBG 704-2, CBG 704-3, up to CBG 704-n, where n = 8), and each CBG includes three (3) CBs. Accordingly, in the example 730, the TB 704 includes a total of 24 CBs (e.g., Ncb = 24). In some aspects, the WCD may report the failing CBs via CB-level feedback signaling based at least in part on using an absolute-CB-and-bitmap reporting format that is CB-level feedback signaling reporting format.

[0132] In the absolute-CB-and-bitmap reporting format, the WCD may signal a CB index of a first failing CB (e.g., CB 6) using a number of bits that may be calculated using formula (1) above. For the example 730, Ncb = 24 as the total number of CBs within the TB 704: ceil(log2(24)) = 5 the WCD may indicate the CB index using 5 bits: 001012 based at least in part on an indexing scheme that starts at 0. The remaining bits for the absolute-CB-and-relative-CB-number reporting 0097-5130PCT 39format may calculated by the WCD using formula (2) above. Following the previous examples of maxCodeBlockGroupsPerTransportBlock = 8, and ceil(log2[Ncb]) = 5, the WCD may calculate the following number of bits: Nrem = 8 – 5 = 3 Accordingly, and based at least in part on the absolute-CB-and-bitmap reporting format, the WCD may use the 3 remaining bits to signal one or more failure CBs that occur and / or are aligned after the first failing CB (e.g., CB 6). That is, the WCD may indicate up to 3 failing CBs using the 3 bits based at least in part on each bit mapping to a respective CB. For instance, the WCD may set a respective bit to a first value (e.g., “0”) to indicate the respective CB is a passing CB and / or may set the respective bit to a second value (e.g., “1”) to indicate that the respective CB is a failing CB. To further explain, 1002may indicate that CB 7 is a failing CB (and that CB 8 and CB 9 are passing CBs), 0102may indicate that CB 8 is a failing CB (and that CB 7 and CB 9 are passing CBs), and / or 0012may indicate that CB 9 is a failing CB (and that CB 7 and CB 8 are passing CBs). For the CB error pattern 732, only CB 8 is a failing CB, and the WCD may indicate 0102in the remaining 3 bits, but other examples may include more than one failing CB. Accordingly, the absolute-CB-and-bitmap reporting format may include a WCD signaling an absolute index of a first failing CB and bitmap for subsequent CBs, where each bit maps to a respective CB that occurs after the first failing CB. In some aspects, the LSBs may indicate the starting index and the MSBs may indicate the bitmap of failing CBs. To illustrate, for the example 730, the WCD may signal 010001012. However, in other examples, the LSBs may indicate the bitmap and the MSBs may indicate an absolute index of the first failing CB.

[0133] The fifth example 740 shown by Fig.7E includes a CB error pattern 742 that may be classified as a first periodic CB error pattern. Example scenarios that may result in the CB error pattern 742 may include data preemption, PN, RIM, and / or time and frequency selective fading. In the fifth example 740, the periodic CB error pattern may be characterized based at least in part on an offset 744 from a start of the TB to a first failing CB (e.g., shown as a 2 CB offset to CB 3) and a periodicity 746 (e.g., shown as six (6) CBs). Alternatively, or additionally, the periodic CB error pattern may be characterized based at least in part on a TB coverage of the periodic failures, such as 100% coverage that indicates the periodic CB error pattern spans 100% of the CBs in the TB 704, 75% coverage that indicates the periodic CB error pattern spans 75% of the CBs in the TB 704, 50% coverage that indicates the periodic CB error pattern spans 50% of the CBs in the TB 704, and / or 25% coverage that indicates the periodic CB error pattern spans 25% of the CBs in the TB 704. In some aspects, the coverage may be based at least in part on the starting failure CB (e.g., CB 3). For instance, a 25% coverage may indicate that the periodic CB error pattern spans 25% of the CBs in the TB 704 starting at CB 3. 0097-5130PCT 40

[0134] In some aspects, the WCD may use a CB-offset-and-periodicity reporting format (e.g., a CB-level feedback signaling reporting format) to indicate the failing CBs of the first periodic CB error pattern, and the CB-offset-and-periodicity reporting format may partition a feedback signaling field into three sub-fields: an offset sub-field, a periodicity sub-field, and a coverage sub-field. To illustrate, and using the example in which maxCodeBlockGroupsPerTransportBlock = 8, the WCD may have 8 bits available in a feedback signaling field. Based at least in part on this example, that CB-offset-and-periodicity reporting format may assign three (3) bits the offset sub-field, 3 bits to the periodicity sub-field, and 2 bits to the coverage sub-field. A WCD may signal a number of offset CBs to the first failing CB in the offset sub-field (e.g., 0102to indicate 2 as shown by the offset 744), a number of CBs in the periodic CB error pattern in the periodicity sub-field (e.g., 1102to indicate 6 as shown by the periodicity 746), and / or a mapping that indicates the coverage in the coverage sub-field. For instance, based at least in part on using 2 bits in the coverage sub-field, the WCD may use a mapping in which 002indicates100% coverage, 012indicates75% coverage, 102indicates 50% coverage, and / or 112indicates 25% coverage. The partitioning of the feedback signaling field can place the offset sub-field, the periodicity sub-field, and / or the coverage sub-field in any order of LSB to MSB (or vice versa). As one non-limiting example, the WCD may signal 001100102 that positions the coverage sub-field in the 2 MSB, the offset sub-field in the 3 LSB, and the periodicity sub-field in between the coverage sub-field and the offset sub-field. Other examples may use a different ordering than shown above. Alternatively, or additionally, the CB-offset-and-periodicity reporting format may omit the coverage sub-field. For instance, selecting the CB-offset-and-periodicity reporting format may implicitly indicate that the periodic CB error pattern spans 100% coverage, and the 2-bit sub-field may instead indicate a respective failure CB around a center failure CB in a similar manner as described with regard to the third example 720 and / or a number of consecutive failure CBs as described with regard to the sixth example 750.

[0135] To illustrate, the sixth example 750 shown by Fig.7F includes a CB error pattern 752 that may be classified as a second periodic CB error pattern. Example scenarios that may result in the CB error pattern 732 may include data preemption, PN, RIM, and / or time and frequency selective fading. In the sixth example 750, and in a similar manner as described with regard to the fifth example 740, the periodic CB error pattern may be characterized based at least in part on an offset 754 to a first failing CB (e.g., shown as a 2 CB offset to CB 3) and a periodicity 756 (e.g., shown as 6 CBs). In some aspects, the WCD may use a CB-offset-periodicity-and-consecutive- CB reporting format (e.g., a CB-level feedback signaling reporting format). For example, based at least in part on maxCodeBlockGroupsPerTransportBlock = 8, the WCD may have 8 bits available in a feedback signaling field, and the CB-offset-periodicity-and-consecutive-CB reporting format may partition the 8 available bits into sub-fields. As one example, and in a similar manner as described above, the CB-offset-periodicity-and-consecutive-CB reporting 0097-5130PCT 41format may assign 3 bits to an offset sub-field and 3 bits to a periodicity sub-field. In some aspects, the use of the CB-offset-periodicity-and-consecutive-CB reporting format may implicitly indicate 100% coverage of the periodic CB error pattern. For discussion purposes, the size of each sub-field in the fifth example and the sixth example described above are based at least in part on an 8-bit feedback signaling field, and signaling fields with more or fewer bits may partition the sub-fields into different sizes than described above and below.

[0136] In some aspects, the remaining bits of the feedback signaling field may be used to indicate a number of consecutive and / or contiguous failing CBs that are relative to a base periodic CB. To illustrate, CB 3, CB 9, CB 15, up to CB 33 may be considered base periodic CBs based at least in part on the periodicity 756 restarting at each of these CBs. The CB-offset-periodicity- and-consecutive-CB reporting format may include a consecutive failure CBs sub-field to indicate a number of CBs following the base periodic CB that are failure CBs. For instance, and with regard to an 8-bit feedback signaling field, the CB-offset-periodicity-and-consecutive-CB reporting format may assign the remaining 2-bits to the consecutive failure CBs sub-field that may be used to indicate a number of consecutive failing CBs. The WCD may set the consecutive failure CBs sub-field to a first value (e.g., 002) to indicate that none of the consecutive CBs are failure CBs, a second value (e.g., 012) to indicate that a first CB of the consecutive CBs is a failure CB, a third value (e.g., 102) to indicate that the first consecutive CB and the second consecutive CB are failure CBs, and / or a fourth value (e.g., 112) to indicate that all three of the consecutive CBs are failure CBs. Indicating a failure CB may implicitly indicate a retransmission request for the failing CB (and / or vice versa). Alternatively, or additionally, indicating a failure CB may implicitly indicate a NACK for the failing CB (and / or vice versa).

[0137] Based at least in part on the CB error pattern 752 shown by Fig.7F, the WCD may indicate the fourth value (e.g., 112) to indicate that all three of the consecutive CBs shown by reference number 758-1, reference number 758-2, and reference number 758-n are failure CBs. To further explain, within a first set of three consecutive CBs that are shown by reference number 758-1, CB 4 in a zero CB offset position is a passing CB, CB 5 in a first CB offset position is a failure CB, and CB 6 in a second CB offset position is a passing CB. Within an n-th set of three consecutive CBs that are shown by reference number 758-n, CB 34 in a zero CB offset position is a failing CB, CB 35 in a first CB offset position is a passing CB, and CB 36 in a second CB offset position is a failing CB. In combination, the first set of three consecutive CBs and the n-th set of three consecutive CBs include a failing CB in the zero CB offset position, the first CB offset position, and the second CB offset position. Accordingly, the WCD may indicate the fourth value of 112to ensure a retransmission request for each failing CB, which may result in the additional retransmission of one or more passing CBs (e.g., CB 4, CB 6, CB 12, and CB 35). However, the additional retransmission of the one or more passing CBs may use fewer air interface resources relative to using CBG-level feedback signaling. 0097-5130PCT 42

[0138] The seventh example 760 shown by Fig.7G includes a CB error pattern 762 that may be classified as a contiguous-CB-based error pattern. Example scenarios that may result in the CB error pattern 762 may include data preemption, PN, RIM, and / or time and frequency selective fading. In some aspects, a WCD may indicate the failing CBs in the CB error pattern 762 using CB-level feedback signaling reporting format that is an absolute-CBG-and-CB-failure-bitmap reporting format.

[0139] In the seventh example 760, the TB 704 includes 8 CBGs (shown as CBG 704-1, CBG 704-2, CBG 704-3, up to CBG 704-n, where n = 8), and each CBG includes three (3) CBs. Accordingly, in the seventh example 760, the TB 704 includes a total of 24 CBs (e.g., Ncb = 24). In some aspects, the absolute-CBG-and-CB-failure-bitmap reporting format may partition a feedback signaling field into three sub-fields: a CBG index sub-field, a CBG bitmap sub-field, and a consecutive CBG sub-field. The CBG index sub-field may be used to indicate an absolute index of a first CBG that includes a first failure CB. Each bit included in the CBG bitmap sub- field may map to a respective CB within a CBG, and may be used to indicate a CB error pattern within a CBG. The consecutive CBG sub-field may be used to indicate a number of consecutive CBGs, relative to the first CBG, that include the CB error pattern indicated by the CBG bitmap subfield.

[0140] As one example, and based at least in part on maxCodeBlockGroupsPerTransportBlock = 8, the WCD may have 8 bits available in a feedback signaling field. In some aspects, the absolute-CBG-and-CB-failure-bitmap may assign 3 bits to the CBG index sub-field, may assign 3 bits to the CBG bitmap sub-field based at least in part on each CBG including 3 CBs (e.g., Nb = 3, where Nb represents a number of CBs included in a CBG), and may assign any remaining bits of the feedback signaling field (e.g., 2) to the consecutive CBG sub-field. In the seventh example 760, the first failing CB is CB 2, and CB 2 is included in the CBG 704-1. Using an indexing scheme that starts at 0, the CBG 704-1 may be assigned an absolute index of 0, and, consequently, a WCD may set the CBG index to sub-field to the index value of 0002. Within the CBG 704-1, CB 2 and CB 3 are observed as failing CBs, and the WCD may configure the bits in CBG bitmap sub-field to a bit error pattern that indicates CB 2 and CB 3 are failing CBs and that CB 1 is a passing CB. For example, and in a similar manner as described with regard to Fig.7D, the WCD may set the respective bits of the CBG bitmap sub-field that map to CB 2 and CB 3 to a respective value that indicates a failing CB (e.g., “1”) and the respective bit of the CBG bitmap sub-field that maps to CB 1 to a value that indicates a passing CB (e.g., “0”), resulting in the WCD setting the CBG bitmap subfield to 0112. In analyzing the consecutive CBG 704-2 and the consecutive CBG 704-3, the WCD may derive that the bit error pattern indicated in the CBG bitmap sub-field may adequately describe the failure CBs included in the consecutive CBG 704-2 and the consecutive CBG 704-3. That is, the bit error pattern in the CBG bitfield sub-field indicates the failure CBs of 0097-5130PCT 43the consecutive CBG 704-2 and the consecutive CBG 704-3, in addition to some passing CBs (e.g., CB 5 and CB 9). Accordingly, the WCD may set the consecutive CBG sub-field to a value of 2 (e.g., 102) to extend the application of the bit error pattern that is indicated by the CBG bitmap sub-field to the consecutive CBGs and, subsequently, indicate a request for retransmission of the indicated CBs in two consecutive CBGs that occur after the first CBG. Although using the absolute-CBG-and-CB-failure-bitmap reporting format may result in the needless retransmission of passing CB 5 and passing CB 9, the air interface resource used for these retransmissions are fewer than indicated the same failure CBs using CBG-level feedback signaling, resulting in reduced air resource consumption relative to CBG-level feedback signaling.

[0141] In some aspects, the feedback signaling may indicate a feedback signaling level type (e.g., a CB-level feedback type or a CBG-level feedback type) that is used for the feedback signaling. For instance, and as described with regard to Fig.6, a WCD may determine to dynamically switch between the CB-level feedback signaling and / or CBG-level feedback signaling based at least in part on selecting a feedback signaling level type that results in a retransmission using fewer air interface resources. Alternatively, or additionally, the WCD may determine to dynamically switch between different CB-level feedback signaling reporting formats based at least in part on selecting a reporting format that reduces a number of needless CB retransmissions (e.g., for passing CBs) and / or results in a retransmission that uses fewer air interface resources. Accordingly, in some aspects, the WCD may indicate a feedback signaling level type, such as by setting a single overhead bit to a first value (e.g., “0”) that indicates a first feedback signaling level type (e.g., CB-level feedback signaling or CBG-level feedback signaling) and a second value (e.g., “1”) that indicates the other feedback-level type (e.g., CBG-level feedback signaling or CB-level feedback signaling, respectively). As one example, the WCD may first evaluate CB-level feedback signaling and / or reporting formats. Based at least in part on identifying a CB error pattern and / or a reporting format as described above that may use CB-level signaling to reduce air interface resource consumption, the WCD may configure the feedback signaling field and set the single overhead bit to the value that indicates CB-level feedback signaling. Based at least in part on being unable to find a CB error pattern and / or a reporting format that benefits from CB-level feedback signaling, the WCD may switch to CBG-level feedback signaling and set the single overhead to a value that indicates CBG-level feedback signaling. That is, if the WCD is unable to find a suitable CB-level feedback signaling and / or reporting format that reduces air interface consumption, the WCD may use CBG-level feedback signaling. The single overhead bit may be a separate bit than the example 8-bit feedback signaling field described above and / or may be included in the 8-bit feedback signaling field.

[0142] Alternatively, or additionally, the WCD may indicate a reporting format that is used for CB-level feedback signaling. For instance, each of the seven examples of CB-level feedback signaling reporting formats described above may be uniquely indicated from one another using 3 0097-5130PCT 44reporting format overhead bits (e.g., 0002, 0012, up to 1112). The reporting format overhead bits may be separate from the example 8-bit feedback signaling field described above and / or may be included in the 8-bit feedback signaling field. Accordingly, the reporting format may include a number of bits that is equivalent to a total number of possible CBGs included in a TB (e.g., maxCodeBlockGroupsPerTransportBlock). Alternatively, or additionally, the reporting format may use more bits than a number of bits that is equal to the total possible CBGs in the TB.

[0143] Dynamically switching between different levels of feedback signaling, such as dynamically switching between CB-level feedback signaling and CBG-level feedback signaling, may enable a receiving device in a feedback process to select a feedback signaling level that reduces a number of air interface resources used for a retransmission. For instance, the receiving device may analyze an error pattern within a TB (e.g., a CB error pattern), and select the feedback signaling level and / or a reporting format that results in a more efficient retransmission that uses fewer air interface resources relative to other feedback signaling levels and / or reporting formats. Using fewer air interface resources for retransmissions may increase data throughput in a wireless network and / or decrease data transfer latencies within the wireless network.

[0144] As indicated above, Figs.7A, 7B, 7C, 7D, 7E, 7F, and 7G are provided as examples. Other examples may differ from what is described with regard to Figs.7A, 7B, 7C, 7D, 7E, 7F, and 7G.

[0145] Fig.8 is a diagram illustrating an example 800 of a wireless communication process between a transmitting device 802 and a receiving device 804, in accordance with the present disclosure. The transmitting device 802 and the receiving device 804 may be varying combinations of WCDs, such as a network node 110 and a UE 120, a UE 120 and a network node 110, and / or a first UE 120 and a second UE 120, respectively. The notations “transmitting device” and “receiving device” are used in reference to a transmitting side and a receiving side of a feedback process and / or a retransmission process, such as a HARQ process as described above. Accordingly, and as shown by Fig.8, the transmitting device 802 may transmit communications to and / or receive communications from the receiving device 804 (and / or vice versa).

[0146] As shown by reference number 810, a transmitting device 802 and a receiving device 804 may establish a connection with one another, and the connection may include any combination of a downlink, an uplink, and / or a sidelink. To illustrate, the transmitting device 802 and the receiving device 804 may be a network node 110 and a UE 120 (or vice versa) and the UE 120 may power up in a cell coverage area provided by the network node 110, and the UE 120 and the network node 110 may perform one or more procedures (e.g., a random access channel (RACH) procedure and / or an RRC procedure) to establish a wireless connection. As another example, the UE 120 may move into the cell coverage area provided by the network node 110 and may perform a handover from a source network node (e.g., another network node 110) to the 0097-5130PCT 45network node 110. In some aspects, the transmitting device 802 and the receiving device 804 may be a first UE 120 and a second UE 120, and the first UE 120 and the second UE 120 may establish a sidelink with one another.

[0147] The transmitting device 802 and the receiving device 804 may communicate via the connection based at least in part on any combination of Layer 1 signaling (e.g., DCI, UCI, and / or SCI), Layer 2 signaling (e.g., a MAC control element (CE)), and / or Layer 3 signaling (e.g., RRC signaling). To illustrate, the transmitting device 802 may request, via RRC signaling, capability information and / or the receiving device 804 may transmit, via RRC signaling, the capability information (and / or vice versa). Alternatively, or additionally, the transmitting device 802 and / or receiving device 804 may autonomously transmit capability device to the other WCD. In some aspects, the capability information indicates that the WCD supports dynamically switching between a first level of feedback signaling (e.g., a CBG-level feedback signaling type) and a second level (e.g., a CB-level feedback signaling type). Alternatively, or additionally, the capability information indicates one or more reporting formats that are supported for a feedback signaling level type (e.g., the CB-level feedback signaling). In some aspects, the transmitting device 802 may indicate to initiate a feedback process (e.g., a HARQ process) and / or indicate one or more air interface resources that are associated with the feedback process.

[0148] As part of communicating via the connection, the transmitting device 802 may transmit configuration information via Layer 3 signaling (e.g., RRC signaling), and activate and / or deactivate a particular configuration via Layer 2 signaling (e.g., a MAC CE) and / or Layer 1 signaling (e.g., DCI and / or SCI). To illustrate, a network node 110 may transmit configuration information via Layer 3 signaling at a first point in time associated with a UE 120 being tolerant of communication delays, and the network node 110 may transmit an activation of the configuration via Layer 2 signaling and / or Layer 1 signaling at a second point in time associated with the UE 120 being intolerant to communication delays.

[0149] As shown by reference number 820, the transmitting device 802 may transmit, and the receiving device 804 may receive, a communication. In some aspects, the communication includes a TB that is directed to the receiving device 804. The TB may be partitioned into one or more CBGs, and each CBG may be partitioned into one or more CBs as described with regard to Fig.5.

[0150] As shown by reference number 830, the receiving device 804 may select a feedback signaling level type (e.g., a CB-level and / or a CBG-level) to use for transmitting feedback (e.g., ACK / NACK feedback) to the transmitting device 802. As one example, the receiving device 804 may analyze each CBG included in the TB as described with regard to Fig.6 to select between CBG-level feedback signaling and CB-level feedback signaling. In some aspects, the receiving device 804 may analyze multiple TBs and / or multiple CW within the communication as described 0097-5130PCT 46above. Alternatively, or additionally, and based at least in part on selecting CB-level feedback signaling, the receiving device 804 may select a reporting format for the CB-level feedback signaling (e.g., ACK / NACK feedback signaling) based at least in part on a CB error pattern that the receiving device 804 identifies within the TB. To illustrate, and as described with regard to Fig.7A, the receiving device 804 may identify that the CB error pattern is a single CB error pattern, and select a single CB reporting format for CB-level feedback signaling. As described with regard to Fig.7B, Fig.7C, Fig 7D, and / or 7G, the receiving device 804 may identify that the CB error pattern is a contiguous-CB-based error pattern, and may select to use an absolute-CB- and-contiguous-CB-number reporting format, an absolute-CB-and-relative-CB-number reporting format, an absolute-CB-and-bitmap reporting format, and / or an absolute-CBG-and-CB-failure- bitmap reporting format for CB-level feedback signaling. In some aspects, and as described with regard to Fig.7E and Fig.7F, the receiving device 804 may identify that the CB error pattern is a periodic CB error pattern, and may select, as the reporting format, a CB-offset-and-periodicity reporting format or a CB-offset-periodicity-and-consecutive-CB reporting format for CB-level feedback signaling. Accordingly, in some aspects, the receiving device 804 may selecting the reporting format from multiple reporting formats that are supported by the receiving device 804 based at least in part on the CB error pattern and / or a transmission efficiency of the reporting format (e.g., a reporting format that reduces a number of air interface resources in a retransmission).

[0151] In some aspects, and as described with regard to Fig.7A, 7B, 7C, 7D, 7E, 7F, and 7G, a number of bits used in the reporting format may be based at least in part on a configured parameter, such as maxCodeBlockGroupsPerTransportBlock. That is, a feedback signaling field and / or the reporting format may include a number of bits that is indicated by the configured parameter. However, in other aspects, the reporting format may be based at least in part on more bits than indicated by the configured parameter. To illustrate, for a maxCodeBlockGroupsPerTransportBlock =8 example, the reporting format may use more than 8 bits. For instance, the reporting format may include a first overhead field that indicates a feedback signaling level type (e.g., a single bit field) and / or a second overhead field that indicates the reporting format type (e.g., a 3-bit field)

[0152] As shown by reference number 840, the receiving device 804 may transmit, and the transmitting device 802 may receive, feedback based at least in part on the selected feedback signaling level type. For instance, the receiving device 804 may transmit the feedback signaling in DCI carried by a downlink, UCI carried by an uplink, and / or SCI carried by a sidelink. The feedback signaling may be based at least in part on CB-level feedback signaling in scenarios that the receiving device 804 dynamically selects CB-level feedback signaling. In some aspects, the receiving device 804 may transmit the feedback using the selected reporting format as described above. Alternatively, or additionally, the feedback signaling may be based at least in part on 0097-5130PCT 47CBG-level feedback signaling in scenarios that the receiving device 804 dynamically selects CBG-level feedback signaling. The feedback signaling may include and / or indicate any combination of ACK / NACK feedback (e.g., HARQ ACK / NACK feedback), a feedback signaling level type, and / or a reporting format.

[0153] As shown by reference number 850, the transmitting device 802 may transmit, and the receiving device 804 may receive, a retransmission. The retransmission may be based at least in part on the selected feedback signaling level type used by the receiving device. As one example, the transmitting device 802 may retransmit one or more CBGs. As another example, the transmitting device 802 may transmit a portion of one or more CBGs by transmitting one or more CBs (e.g., but not an entirety of the CBG).

[0154] As indicated above, Fig.8 is provided as an example. Other examples may differ from what is described with regard to Fig.8.

[0155] Fig.9 is a diagram illustrating an example process 900 performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure. Example process 900 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with dynamically switching between CB-level feedback signaling and CBG-level feedback signaling.

[0156] As shown in Fig.9, in some aspects, process 900 may include communicating a TB with a WCD (block 910). For example, the UE (e.g., using reception component 1102, transmission component 1104, and / or communication manager 1106, depicted in Fig.11) may communicate a TB with a WCD, as described above.

[0157] As further shown in Fig.9, in some aspects, process 900 may include communicating ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB (block 920). For example, the UE (e.g., using reception component 1102, transmission component 1104, and / or communication manager 1106, depicted in Fig.11) may communicate ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB, as described above.

[0158] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0159] In a first aspect, communicating the TB and communicating the ACK / NACK feedback includes transmitting the TB and receiving the ACK / NACK feedback, or receiving the TB and transmitting the ACK / NACK feedback.

[0160] In a second aspect, the ACK / NACK feedback included ACK / NACK message signaling. 0097-5130PCT 48

[0161] In a third aspect, the ACK / NACK feedback includes DCI feedback signaling.

[0162] In a fourth aspect, the first level comprises CBG-level ACK / NACK feedback, and the second level includes CB-level ACK / NACK feedback.

[0163] In a fifth aspect, process 900 includes selecting a reporting format for the CB-level ACK / NACK feedback based at least in part on the CB error pattern, and communicating the ACK / NACK feedback includes communicating the ACK / NACK feedback using the reporting format.

[0164] In a sixth aspect, the CB error pattern is a single CB error pattern, and the reporting format is a single CB reporting format.

[0165] In a seventh aspect, the CB error pattern is a contiguous-CB-based error pattern, and the reporting format is an absolute-CB-and-contiguous-CB-number reporting format.

[0166] In an eighth aspect, the CB error pattern is a contiguous-CB-based error pattern, and the reporting format is an absolute-CB-and-relative-CB-number reporting format.

[0167] In a ninth aspect, the CB error pattern is a contiguous-CB-based error pattern, and the reporting format is an absolute-CB-and-bitmap reporting format.

[0168] In a tenth aspect, the CB error pattern is a periodic CB error pattern, and the reporting format is a CB-offset-and-periodicity reporting format.

[0169] In an eleventh aspect, the CB error pattern is a periodic CB error pattern, and the reporting format is a CB-offset-periodicity-and-consecutive-CB reporting format.

[0170] In a twelfth aspect, the CB error pattern is a contiguous-CB-based error pattern, and the reporting format is an absolute-CBG-and-CB-failure-bitmap reporting format.

[0171] In a thirteenth aspect, selecting the reporting format for the CB-level ACK / NACK feedback includes selecting the reporting format from multiple reporting formats based at least in part on a transmission efficiency of the reporting format for the CB error pattern.

[0172] In a fourteenth aspect, process 900 includes transmitting an indication of the reporting format.

[0173] In a fifteenth aspect, the reporting format uses a first number of bits that is greater than a second number of total possible CBGs in the TB.

[0174] In a sixteenth aspect, process 900 includes receiving an indication of a reporting format to use for the second level of ACK / NACK feedback, and communicating the ACK / NACK feedback includes communicating the ACK / NACK feedback using the reporting format.

[0175] In a seventeenth aspect, process 900 includes transmitting capability information that indicates support for dynamically switching between the first level and the second level.

[0176] In an eighteenth aspect, process 900 includes transmitting capability information that indicates one or more reporting formats that are supported for the second level. 0097-5130PCT 49

[0177] In a nineteenth aspect, the ACK / NACK feedback is based at least in part on multiple codewords being enabled.

[0178] In a twentieth aspect, communicating the ACK / NACK feedback includes communicating the ACK / NACK feedback using a sidelink.

[0179] In a twenty-first aspect, overhead associated with the ACK / NACK feedback indicates the second level.

[0180] In a twenty-second aspect, overhead associated with the ACK / NACK feedback indicates a reporting format of the second level.

[0181] In a twenty-third aspect, the UE is a first UE, and the WCD is at least one of a network node, or a second UE.

[0182] Although Fig.9 shows example blocks of process 900, in some aspects, process 900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig.9. Additionally, or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0183] Fig.10 is a diagram illustrating an example process 1000 performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure. Example process 1000 is an example where the apparatus or the network node (e.g., network node 110) performs operations associated with dynamically switching between CB-level feedback signaling and CBG-level feedback signaling.

[0184] As shown in Fig.10, in some aspects, process 1000 may include communicating a TB with a UE (block 1010). For example, the network node (e.g., using reception component 1202, transmission component 1204, and / or communication manager 1206, depicted in Fig.12) may communicate a TB with a UE, as described above.

[0185] As further shown in Fig.10, in some aspects, process 1000 may include communicating ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB (block 1020). For example, the network node (e.g., using reception component 1202, transmission component 1204, and / or communication manager 1206, depicted in Fig.12) may communicate ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB, as described above.

[0186] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein. 0097-5130PCT 50

[0187] In a first aspect, communicating the TB and communicating the ACK / NACK feedback includes transmitting the TB and receiving the ACK / NACK feedback, or receiving the TB and transmitting the ACK / NACK feedback.

[0188] In a second aspect, the ACK / NACK feedback includes ACK / NACK message signaling.

[0189] In a third aspect, the ACK / NACK feedback includes DCI feedback signaling.

[0190] In a fourth aspect, the first level includes CBG-level ACK / NACK feedback, and the second level comprises CB-level ACK / NACK feedback.

[0191] In a fifth aspect, process 1000 includes selecting a reporting format for the CB-level ACK / NACK feedback based at least in part on the CB error pattern, and communicating the ACK / NACK feedback includes communicating the ACK / NACK feedback using the reporting format.

[0192] In a sixth aspect, the CB error pattern is a single CB error pattern, and the reporting format is a single CB reporting format.

[0193] In a seventh aspect, the CB error pattern is a contiguous-CB-based error pattern, and the reporting format is an absolute-CB-and-contiguous-CB-number reporting format.

[0194] In an eighth aspect, the CB error pattern is a contiguous-CB-based error pattern, and the reporting format is an absolute-CB-and-relative-CB-number reporting format.

[0195] In a ninth aspect, the CB error pattern is a contiguous-CB-based error pattern, and the reporting format is an absolute-CB-and-bitmap reporting format.

[0196] In a tenth aspect, the CB error pattern is a periodic CB error pattern, and the reporting format is a CB-offset-and-periodicity reporting format.

[0197] In an eleventh aspect, the CB error pattern is a periodic CB error pattern, and the reporting format is a CB-offset-periodicity-and-consecutive-CB reporting format.

[0198] In a twelfth aspect, the CB error pattern is a contiguous-CB-based error pattern, and the reporting format is an absolute-CBG-and-CB-failure-bitmap reporting format.

[0199] In a thirteenth aspect, selecting the reporting format for the CB-level ACK / NACK feedback includes selecting the reporting format from multiple reporting formats based at least in part on a transmission efficiency of the reporting format for the CB error pattern.

[0200] In a fourteenth aspect, process 1000 includes transmitting an indication of the reporting format.

[0201] In a fifteenth aspect, the reporting format uses a first number of bits that is greater than a second number of total possible CBGs in the TB.

[0202] In a sixteenth aspect, process 1000 includes receiving an indication of a reporting format to use for the second level of ACK / NACK feedback, and communicating the ACK / NACK feedback includes communicating the ACK / NACK feedback using the reporting format. 0097-5130PCT 51

[0203] In a seventeenth aspect, process 1000 includes receiving capability information for the UE, the capability information indicating support for dynamically switching between the first level and the second level.

[0204] In an eighteenth aspect, process 1000 includes receiving capability information for the UE, the capability information indicating one or more reporting formats that are supported for the second level.

[0205] In a nineteenth aspect, the ACK / NACK feedback is based at least in part on multiple codewords being enabled.

[0206] In a twentieth aspect, overhead associated with the ACK / NACK feedback indicates the second level.

[0207] In a twenty-first aspect, overhead associated with the ACK / NACK feedback indicates a reporting format of the second level.

[0208] Although Fig.10 shows example blocks of process 1000, in some aspects, process 1000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig.10. Additionally, or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0209] Fig.11 is a diagram of an example apparatus 1100 for wireless communication, in accordance with the present disclosure. The apparatus 1100 may be a UE, or a UE may include the apparatus 1100. In some aspects, the apparatus 1100 includes a reception component 1102, a transmission component 1104, and / or a communication manager 1106, which may be in communication with one another (for example, via one or more buses and / or one or more other components). In some aspects, the communication manager 1106 is the communication manager 140 described in connection with Fig.1. As shown, the apparatus 1100 may communicate with another apparatus 1108, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 1102 and the transmission component 1104.

[0210] In some aspects, the apparatus 1100 may be configured to perform one or more operations described herein in connection with Figs.5-8. Additionally, or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as process 900 of Fig.9, or a combination thereof. In some aspects, the apparatus 1100 and / or one or more components shown in Fig.11 may include one or more components of the UE described in connection with Fig.2. Additionally, or alternatively, one or more components shown in Fig. 11 may be implemented within one or more components described in connection with Fig.2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a 0097-5130PCT 52non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

[0211] The reception component 1102 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1108. The reception component 1102 may provide received communications to one or more other components of the apparatus 1100. In some aspects, the reception component 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 1100. In some aspects, the reception component 1102 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers / processors, one or more memories, or a combination thereof, of the UE described in connection with Fig.2.

[0212] The transmission component 1104 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1108. In some aspects, one or more other components of the apparatus 1100 may generate communications and may provide the generated communications to the transmission component 1104 for transmission to the apparatus 1108. In some aspects, the transmission component 1104 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1108. In some aspects, the transmission component 1104 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or a combination thereof, of the UE described in connection with Fig.2. In some aspects, the transmission component 1104 may be co-located with the reception component 1102 in one or more transceivers.

[0213] The communication manager 1106 may support operations of the reception component 1102 and / or the transmission component 1104. For example, the communication manager 1106 may receive information associated with configuring reception of communications by the reception component 1102 and / or transmission of communications by the transmission component 1104. Additionally, or alternatively, the communication manager 1106 may generate and / or provide control information to the reception component 1102 and / or the transmission component 1104 to control reception and / or transmission of communications.

[0214] The reception component 1102 and / or the transmission component 1104 may communicate a TB with a WCD. The reception component 1102 and / or the transmission 0097-5130PCT 53component 1104 may communicate ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB.

[0215] The communication manager 1106 may select a reporting format for the CB-level ACK / NACK feedback based at least in part on the CB error pattern. Alternatively, or additionally, the transmission component 1104 may transmit an indication of the reporting format. In some aspects, the reception component 1102 may receive an indication of a reporting format to use for the second level of ACK / NACK feedback.

[0216] The transmission component 1104 may transmit capability information that indicates support for dynamically switching between the first level and the second level. Alternatively, or additionally, the transmission component 1104 may transmit capability information that indicates one or more reporting formats that are supported for the second level.

[0217] The number and arrangement of components shown in Fig.11 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig.11. Furthermore, two or more components shown in Fig.11 may be implemented within a single component, or a single component shown in Fig.11 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig.11 may perform one or more functions described as being performed by another set of components shown in Fig. 11.

[0218] Fig.12 is a diagram of an example apparatus 1200 for wireless communication, in accordance with the present disclosure. The apparatus 1200 may be a network node, or a network node may include the apparatus 1200. In some aspects, the apparatus 1200 includes a reception component 1202, a transmission component 1204, and / or a communication manager 1206, which may be in communication with one another (for example, via one or more buses and / or one or more other components). In some aspects, the communication manager 1206 is the communication manager 150 described in connection with Fig.1. As shown, the apparatus 1200 may communicate with another apparatus 1208, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 1202 and the transmission component 1204.

[0219] In some aspects, the apparatus 1200 may be configured to perform one or more operations described herein in connection with Figs.5-8. Additionally, or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as process 1000 of Fig.10, or a combination thereof. In some aspects, the apparatus 1200 and / or one or more components shown in Fig.12 may include one or more components of the network node described in connection with Fig.2. Additionally, or alternatively, one or more components 0097-5130PCT 54shown in Fig.12 may be implemented within one or more components described in connection with Fig.2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

[0220] The reception component 1202 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1208. The reception component 1202 may provide received communications to one or more other components of the apparatus 1200. In some aspects, the reception component 1202 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 1200. In some aspects, the reception component 1202 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers / processors, one or more memories, or a combination thereof, of the network node described in connection with Fig.2. In some aspects, the reception component 1202 and / or the transmission component 1204 may include or may be included in a network interface. The network interface may be configured to obtain and / or output signals for the apparatus 1200 via one or more communications links, such as a backhaul link, a midhaul link, and / or a fronthaul link.

[0221] The transmission component 1204 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1208. In some aspects, one or more other components of the apparatus 1200 may generate communications and may provide the generated communications to the transmission component 1204 for transmission to the apparatus 1208. In some aspects, the transmission component 1204 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1208. In some aspects, the transmission component 1204 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or a combination thereof, of the network node described in connection with Fig.2. In some aspects, the transmission component 1204 may be co-located with the reception component 1202 in one or more transceivers. 0097-5130PCT 55

[0222] The communication manager 1206 may support operations of the reception component 1202 and / or the transmission component 1204. For example, the communication manager 1206 may receive information associated with configuring reception of communications by the reception component 1202 and / or transmission of communications by the transmission component 1204. Additionally, or alternatively, the communication manager 1206 may generate and / or provide control information to the reception component 1202 and / or the transmission component 1204 to control reception and / or transmission of communications.

[0223] The reception component 1202 and / or the transmission component 1204 may communicate a TB with a UE. The reception component 1202 and / or the transmission component 1204 may communicate ACK / NACK feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a CB error pattern of the TB.

[0224] The communication manager 1206 may select a reporting format for the CB-level ACK / NACK feedback based at least in part on the CB error pattern. In some aspects, the transmission component 1204 may transmit an indication of the reporting format. Alternatively, or additionally, the reception component 1202 may receive an indication of a reporting format to use for the second level of ACK / NACK feedback.

[0225] The reception component 1202 may receive capability information for the UE, the capability information indicating support for dynamically switching between the first level and the second level. Alternatively, or additionally, the reception component 1202 may receive capability information for the UE, the capability information indicating one or more reporting formats that are supported for the second level.

[0226] The number and arrangement of components shown in Fig.12 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig.12. Furthermore, two or more components shown in Fig.12 may be implemented within a single component, or a single component shown in Fig.12 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig.12 may perform one or more functions described as being performed by another set of components shown in Fig. 12.

[0227] The following provides an overview of some Aspects of the present disclosure:

[0228] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: communicating a transport block (TB) with a wireless communication device (WCD); and communicating acknowledgement / negative acknowledgement (ACK / NACK) feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback 0097-5130PCT 56to a second level of ACK / NACK feedback, the switching being based at least in part on a code block (CB) error pattern of the TB.

[0229] Aspect 2: The method of Aspect 1, wherein communicating the TB and communicating the ACK / NACK feedback comprises: transmitting the TB and receiving the ACK / NACK feedback, or receiving the TB and transmitting the ACK / NACK feedback.

[0230] Aspect 3: The method of any of Aspects 1-2, wherein the ACK / NACK feedback comprises ACK / NACK message signaling.

[0231] Aspect 4: The method of any of Aspects 1-3, wherein the ACK / NACK feedback comprises downlink control information (DCI) feedback signaling.

[0232] Aspect 5: The method of any of Aspects 1-4, wherein the first level comprises code block group-level (CBG-level) ACK / NACK feedback, and wherein the second level comprises CB-level ACK / NACK feedback.

[0233] Aspect 6: The method of Aspect 5, further comprising: selecting a reporting format for the CB-level ACK / NACK feedback based at least in part on the CB error pattern, wherein communicating the ACK / NACK feedback comprises: communicating the ACK / NACK feedback using the reporting format.

[0234] Aspect 7: The method of Aspect 6, wherein the CB error pattern is a single CB error pattern, and wherein the reporting format is a single CB reporting format.

[0235] Aspect 8: The method of Aspect 6, wherein the CB error pattern is a contiguous-CB- based error pattern, and wherein the reporting format is an absolute-CB-and-contiguous-CB- number reporting format.

[0236] Aspect 9: The method of Aspect 6, wherein the CB error pattern is a contiguous-CB- based error pattern, and wherein the reporting format is an absolute-CB-and-relative-CB-number reporting format.

[0237] Aspect 10: The method of Aspect 6, wherein the CB error pattern is a contiguous-CB- based error pattern, and wherein the reporting format is an absolute-CB-and-bitmap reporting format.

[0238] Aspect 11: The method of Aspect 6, wherein the CB error pattern is a periodic CB error pattern, and wherein the reporting format is a CB-offset-and-periodicity reporting format.

[0239] Aspect 12: The method of Aspect 6, wherein the CB error pattern is a periodic CB error pattern, and wherein the reporting format is a CB-offset-periodicity-and-consecutive-CB reporting format.

[0240] Aspect 13: The method of Aspect 6, wherein the CB error pattern is a contiguous-CB- based error pattern, and wherein the reporting format is an absolute-CBG-and-CB-failure-bitmap reporting format. 0097-5130PCT 57

[0241] Aspect 14: The method of Aspect 6, wherein selecting the reporting format for the CB- level ACK / NACK feedback comprises: selecting the reporting format from multiple reporting formats based at least in part on a transmission efficiency of the reporting format for the CB error pattern.

[0242] Aspect 15: The method of Aspect 6, further comprising: transmitting an indication of the reporting format.

[0243] Aspect 16: The method of Aspect 6, wherein the reporting format uses a first number of bits that is greater than a second number of total possible CBGs in the TB.

[0244] Aspect 17: The method of any of Aspects 1-16, further comprising: receiving an indication of a reporting format to use for the second level of ACK / NACK feedback, wherein communicating the ACK / NACK feedback comprises: communicating the ACK / NACK feedback using the reporting format.

[0245] Aspect 18: The method of any of Aspects 1-17, further comprising: transmitting capability information that indicates support for dynamically switching between the first level and the second level.

[0246] Aspect 19: The method of any of Aspects 1-18, further comprising: transmitting capability information that indicates one or more reporting formats that are supported for the second level.

[0247] Aspect 20: The method of any of Aspects 1-19, wherein the ACK / NACK feedback is based at least in part on multiple codewords being enabled.

[0248] Aspect 21: The method of any of Aspects 1-20, wherein communicating the ACK / NACK feedback comprises: communicating the ACK / NACK feedback using a sidelink.

[0249] Aspect 22: The method of any of Aspects 1-21, wherein overhead associated with the ACK / NACK feedback indicates the second level.

[0250] Aspect 23: The method of any of Aspects 1-22, wherein overhead associated with the ACK / NACK feedback indicates a reporting format of the second level.

[0251] Aspect 24: The method of any of Aspects 1-23, wherein the UE is a first UE, and wherein the WCD is at least one of: a network node, or a second UE.

[0252] Aspect 25: A method of wireless communication performed by a network node, comprising: communicating a transport block (TB) with a user equipment (UE); and communicating acknowledgement / negative acknowledgement (ACK / NACK) feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a code block (CB) error pattern of the TB. 0097-5130PCT 58

[0253] Aspect 26: The method of Aspect 25, wherein communicating the TB and communicating the ACK / NACK feedback comprises: transmitting the TB and receiving the ACK / NACK feedback, or receiving the TB and transmitting the ACK / NACK feedback.

[0254] Aspect 27: The method of any of Aspects 25-26, wherein the ACK / NACK feedback comprises ACK / NACK message signaling.

[0255] Aspect 28: The method of any of Aspects 25-27, wherein the ACK / NACK feedback comprises downlink control information (DCI) feedback signaling.

[0256] Aspect 29: The method of any of Aspects 25-28, wherein the first level comprises code block group (CBG) level ACK / NACK feedback, and wherein the second level comprises CB- level ACK / NACK feedback.

[0257] Aspect 30: The method of Aspect 29, further comprising: selecting a reporting format for the CB-level ACK / NACK feedback based at least in part on the CB error pattern, wherein communicating the ACK / NACK feedback comprises: communicating the ACK / NACK feedback using the reporting format.

[0258] Aspect 31: The method of Aspect 30, wherein the CB error pattern is a single CB error pattern, and wherein the reporting format is a single CB reporting format.

[0259] Aspect 32: The method of Aspect 30, wherein the CB error pattern is a contiguous-CB- based error pattern, and wherein the reporting format is an absolute-CB-and-contiguous-CB- number reporting format.

[0260] Aspect 33: The method of Aspect 30, wherein the CB error pattern is a contiguous-CB- based error pattern, and wherein the reporting format is an absolute-CB-and-relative-CB-number reporting format.

[0261] Aspect 34: The method of Aspect 30, wherein the CB error pattern is a contiguous-CB- based error pattern, and wherein the reporting format is an absolute-CB-and-bitmap reporting format.

[0262] Aspect 35: The method of Aspect 30, wherein the CB error pattern is a periodic CB error pattern, and wherein the reporting format is a CB-offset-and-periodicity reporting format.

[0263] Aspect 36: The method of Aspect 30, wherein the CB error pattern is a periodic CB error pattern, and wherein the reporting format is a CB-offset-periodicity-and-consecutive-CB reporting format.

[0264] Aspect 37: The method of Aspect 30, wherein the CB error pattern is a contiguous-CB- based error pattern, and wherein the reporting format is an absolute-CBG-and-CB-failure-bitmap reporting format.

[0265] Aspect 38: The method of Aspect 30, wherein selecting the reporting format for the CB-level ACK / NACK feedback comprises: selecting the reporting format from multiple reporting 0097-5130PCT 59formats based at least in part on a transmission efficiency of the reporting format for the CB error pattern.

[0266] Aspect 39: The method of Aspect 38, further comprising: transmitting an indication of the reporting format.

[0267] Aspect 40: The method of Aspect 30, wherein the reporting format uses a first number of bits that is greater than a second number of total possible CBGs in the TB.

[0268] Aspect 41: The method of any of Aspects 25-40, further comprising: receiving an indication of a reporting format to use for the second level of ACK / NACK feedback, wherein communicating the ACK / NACK feedback comprises: communicating the ACK / NACK feedback using the reporting format.

[0269] Aspect 42: The method of any of Aspects 25-41, further comprising: receiving capability information for the UE, the capability information indicating support for dynamically switching between the first level and the second level.

[0270] Aspect 43: The method of any of Aspects 25-42, further comprising: receiving capability information for the UE, the capability information indicating one or more reporting formats that are supported for the second level.

[0271] Aspect 44: The method of any of Aspects 25-43, wherein the ACK / NACK feedback is based at least in part on multiple codewords being enabled.

[0272] Aspect 45: The method of any of Aspects 25-44, wherein overhead associated with the ACK / NACK feedback indicates the second level.

[0273] Aspect 46: The method of any of Aspects 25-45, wherein overhead associated with the ACK / NACK feedback indicates a reporting format of the second level.

[0274] Aspect 47: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 1-46.

[0275] Aspect 48: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform the method of one or more of Aspects 1-46.

[0276] Aspect 49: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-46.

[0277] Aspect 50: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method of one or more of Aspects 1-46. 0097-5130PCT 60

[0278] Aspect 51: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-46.

[0279] Aspect 52: A device for wireless communication, the device comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-46.

[0280] Aspect 53: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the device to perform the method of one or more of Aspects 1-46.

[0281] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.

[0282] As used herein, the term “component” is intended to be broadly construed as hardware or a combination of hardware and at least one of software or firmware. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware or a combination of hardware and software. It will be apparent that systems or methods described herein may be implemented in different forms of hardware or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems or methods is not limiting of the aspects. Thus, the operation and behavior of the systems or methods are described herein without reference to specific software code, because those skilled in the art will understand that software and hardware can be designed to implement the systems or methods based, at least in part, on the description herein. A component being configured to perform a function means that the component has a capability to perform the function, and does not require the function to be actually performed by the component, unless noted otherwise.

[0283] As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples. 0097-5130PCT 61

[0284] As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (for example, a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).

[0285] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” and similar terms are intended to be open-ended terms that do not limit an element that they modify (for example, an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based on or otherwise in association with” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or,” unless explicitly stated otherwise (for example, if used in combination with “either” or “only one of”). It should be understood that “one or more” is equivalent to “at least one.”

[0286] Even though particular combinations of features are recited in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. 0097-5130PCT 62

Claims

WHAT IS CLAIMED IS:

1. An apparatus for wireless communication at a user equipment (UE), comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to cause the UE to: communicate a transport block (TB) with a wireless communication device (WCD); and communicate acknowledgement / negative acknowledgement (ACK / NACK) feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a code block (CB) error pattern of the TB.

2. The apparatus of claim 1, wherein the first level comprises code block group-level (CBG- level) ACK / NACK feedback, and wherein the second level comprises CB-level ACK / NACK feedback.

3. The apparatus of claim 2, wherein the one or more processors are further configured to cause the UE to: select a reporting format for the CB-level ACK / NACK feedback based at least in part on the CB error pattern, and wherein the one or more processors, to cause the UE to communicate the ACK / NACK feedback, are configured to cause the UE to: communicate the ACK / NACK feedback using the reporting format.

4. The apparatus of claim 3, wherein the CB error pattern is a single CB error pattern, and wherein the reporting format is a single CB reporting format.

5. The apparatus of claim 3, wherein the CB error pattern is a contiguous-CB-based error pattern, and wherein the reporting format is an absolute-CB-and-contiguous-CB-number reporting format.

6. The apparatus of claim 3, wherein the CB error pattern is a contiguous-CB-based error pattern, and wherein the reporting format is an absolute-CB-and-relative-CB-number reporting format. 0097-5130PCT 637. The apparatus of claim 3, wherein the CB error pattern is a contiguous-CB-based error pattern, and wherein the reporting format is an absolute-CB-and-bitmap reporting format.

8. The apparatus of claim 3, wherein the CB error pattern is a periodic CB error pattern, and wherein the reporting format is a CB-offset-and-periodicity reporting format.

9. The apparatus of claim 3, wherein the CB error pattern is a periodic CB error pattern, and wherein the reporting format is a CB-offset-periodicity-and-consecutive-CB reporting format.

10. The apparatus of claim 3, wherein the CB error pattern is a contiguous-CB-based error pattern, and wherein the reporting format is an absolute-CBG-and-CB-failure-bitmap reporting format.

11. The apparatus of claim 3, wherein the one or more processors, to cause the UE to select the reporting format for the CB-level ACK / NACK feedback, are configured to cause the UE to: select the reporting format from multiple reporting formats based at least in part on a transmission efficiency of the reporting format for the CB error pattern.

12. The apparatus of claim 3, wherein the one or more processors are further configured to cause the UE to: transmit an indication of the reporting format.

13. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: receive an indication of a reporting format to use for the second level of ACK / NACK feedback, and wherein the one or more processors, to cause the UE to communicate the ACK / NACK feedback, are configured to cause the UE to: communicate the ACK / NACK feedback using the reporting format.

14. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: transmit capability information that indicates support for dynamically switching between the first level and the second level. 0097-5130PCT 6415. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: transmit capability information that indicates one or more reporting formats that are supported for the second level.

16. The apparatus of claim 1, wherein overhead associated with the ACK / NACK feedback indicates the second level.

17. The apparatus of claim 1, wherein overhead associated with the ACK / NACK feedback indicates a reporting format of the second level.

18. An apparatus for wireless communication at a network node, comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to cause the network node to: communicate a transport block (TB) with a user equipment (UE); and communicate acknowledgement / negative acknowledgement (ACK / NACK) feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a code block (CB) error pattern of the TB.

19. The apparatus of claim 18, wherein the one or more processors, to cause the network node to communicate the TB and communicating the ACK / NACK feedback, are configured to cause the network node to: transmit the TB and receiving the ACK / NACK feedback, or receive the TB and transmitting the ACK / NACK feedback.

20. The apparatus of claim 18, wherein the ACK / NACK feedback comprises ACK / NACK message signaling.

21. The apparatus of claim 18, wherein the one or more processors are further configured to cause the network node to downlink control information (DCI) feedback signaling.

22. The apparatus of claim 18, wherein the one or more processors are further configured to cause the network node to code block group (CBG) level ACK / NACK feedback, and wherein the second level comprises CB-level ACK / NACK feedback. 0097-5130PCT 6523. The apparatus of claim 22, wherein the one or more processors are further configured to cause the network node to: select a reporting format for the CB-level ACK / NACK feedback based at least in part on the CB error pattern, wherein the one or more processors, to cause the network node to communicate the ACK / NACK feedback, are configured to cause the network node to: communicate the ACK / NACK feedback using the reporting format.

24. The apparatus of claim 23, wherein the one or more processors are further configured to cause the network node to: transmit an indication of the reporting format.

25. The apparatus of claim 18, wherein the one or more processors are further configured to cause the network node to: receive an indication of a reporting format to use for the second level of ACK / NACK feedback, wherein the one or more processors, to cause the network node to communicate the ACK / NACK feedback, are configured to cause the network node to: communicate the ACK / NACK feedback using the reporting format.

26. The apparatus of claim 18, wherein the one or more processors are further configured to cause the network node to: receive capability information for the UE that indicates support for dynamically switching between the first level and the second level.

27. The apparatus of claim 18, wherein the one or more processors are further configured to cause the network node to: receive capability information for the UE that indicates one or more reporting formats that are supported for the second level.

28. The apparatus of claim 18, wherein overhead associated with the ACK / NACK feedback indicates at least one of: the second level, or a reporting format of the second level.

29. A method of wireless communication performed by a user equipment (UE), comprising: 0097-5130PCT 66communicating a transport block (TB) with a wireless communication device (WCD); and communicating acknowledgement / negative acknowledgement (ACK / NACK) feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a code block (CB) error pattern of the TB.

30. A method of wireless communication performed by a network node, comprising: communicating a transport block (TB) with a user equipment (UE); and communicating acknowledgement / negative acknowledgement (ACK / NACK) feedback for the TB based at least in part on switching from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback, the switching being based at least in part on a code block (CB) error pattern of the TB. 0097-5130PCT 67

Images