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) can communicate a transport block (TB) with a wireless communication device (WCD). The UE can communicate acknowledgement / negative-acknowledgement (ACK / NACK) feedback for the TB based at least in part on a switch from a first level of ACK / NACK feedback to a second level of ACK / NACK feedback based at least in part on a code block (CB) error pattern of the TB. Numerous other aspects are described.

Description

[0001] Cross-reference to related applications

[0002] 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 LEVELFEEDBACK SIGNALING”, assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0003] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus and methods for dynamically switching between block-level feedback signaling and block group-level feedback signaling. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). 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.

[0005] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution. Summary of the Invention

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

[0007] Some aspects described herein relate to a method of wireless communication performed by a network node. This method may include communicating a TB (Breakpoint Tolerance) with a UE. The method may include communicating ACK / NACK feedback for the TB based at least in part on a switch from a first-level ACK / NACK feedback to a second-level ACK / NACK feedback, switching at least in part on a CB (Breakpoint Tolerance) error mode based on the TB.

[0008] 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 ACK / NACK feedback to a second-level ACK / NACK feedback, switching a CB error mode at least in part based on the TB.

[0009] 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 (Terrain Response) with a UE. The one or more processors may be configured to communicate ACK / NACK feedback for the TB, at least in part based on a switch from a first-level ACK / NACK feedback to a second-level ACK / NACK feedback, switching a CB (Corrective Response) error mode at least in part based on the TB.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to communicate a TB with a WCD. When executed by one or more processors of the UE, the set of instructions enables the UE to communicate ACK / NACK feedback for the TB, at least in part, based on a switch from a first-level ACK / NACK feedback to a second-level ACK / NACK feedback, switching a CB error mode at least in part based on the TB.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions enables the network node to communicate a TB (Terrain Response) with the UE. When executed by one or more processors of the network node, the set of instructions enables the network node to communicate ACK / NACK feedback for the TB, at least in part, based on a switch from a first-level ACK / NACK feedback to a second-level ACK / NACK feedback, switching a CB (Corrective Response) error mode at least in part based on the TB.

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

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for communicating a TB (Terrain Response) to a UE. The apparatus may include components for communicating ACK / NACK feedback for the TB, at least in part based on switching from a first-level ACK / NACK feedback to a second-level ACK / NACK feedback, switching a CB (Corrective Response) error mode at least in part based on the TB.

[0014] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0015] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0016] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

[0017] Figure 1 This is a diagram illustrating an example of a wireless communication network according to the present disclosure.

[0018] Figure 2 This is a diagram illustrating communication between an example network node and an example user equipment (UE) in a wireless network according to the present disclosure.

[0019] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0020] Figure 4 This is a diagram illustrating an example of a hybrid automatic repeat request process according to this disclosure.

[0021] Figure 5 This is a diagram illustrating an example of a transport block divided into one or more code block groups (CBGs) and code blocks (CBs) according to the present disclosure.

[0022] Figure 6 This is a diagram illustrating an example algorithm that can be used to switch between CBG-level feedback signaling and CB-level feedback signaling according to this disclosure.

[0023] Figure 7A , Figure 7B , Figure 7C , Figure 7D , Figure 7E , Figure 7F and Figure 7GThese are illustrations of the first, second, third, fourth, fifth, sixth and seventh examples of CB error modes according to this disclosure.

[0024] Figure 8 This is a diagram illustrating an example of a wireless communication process between a transmitting device and a receiving device according to the present disclosure.

[0025] Figure 9 This is a diagram illustrating an example process performed, for example, at the UE or a device of the UE, according to this disclosure.

[0026] Figure 10 This is a diagram illustrating an example process performed, for example, at a network node or a device of a network node, according to the present disclosure.

[0027] Figure 11 This is a diagram of an example device for wireless communication according to the present disclosure.

[0028] Figure 12 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0029] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods practiced using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0030] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various boxes, modules, components, circuits, steps, processes, or algorithms (collectively, “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 on the specific application and the design constraints imposed on the system as a whole.

[0031] Feedback processes (such as Hybrid Automatic Request (HARQ) processes and / or HARQ protocols) enable receiving devices to correct errors in received data packets (such as transport blocks (TBs)). In some aspects, a TB can be divided into one or more code block groups (CBGs), and each CBG can be divided into one or more code blocks (CBs), and the HARQ process can manage acknowledgments (ACKs), negative acknowledgments (NACKs), and / or retransmissions at the CBG level rather than the TB level to mitigate retransmissions of the entire TB. For example, a receiving device can identify failed CBs within a specific CBG and send an indication of a NACK specific to that CBG. Based at least in part on the received NACK, the transmitting device can retransmit data within that specific CBG, rather than the entire TB.

[0032] However, in some scenarios, CBG-level retransmission may result in the retransmission of multiple CBs that were received without errors. For example, a CBG may include five (5) CBs, and the receiving device may receive a specific CBG with one (1) failed CB and four (4) CBs as passing CBs. Based at least in part on the use of the CBG-level retransmission mechanism, the receiving device may send a NACK for a specific CBG, and the transmitting device may retransmit all 5 CBs within the CBG instead of just the 1 failed CB. Retransmission of the 4 passing CBs within a specific CBG may result in unnecessary consumption of air interface resources. This unnecessary consumption of air interface resources may lead to reduced data throughput and / or increased data transfer latency within the wireless network.

[0033] Various aspects generally involve dynamic switching between CB-level feedback signaling and CBG-level feedback signaling. Some aspects more specifically involve the receiving equipment (such as User Equipment (UE) and / or network nodes) in the feedback process selecting the feedback signaling level that uses fewer air interface resources, at least in part, based on the error patterns in the received data packets. In some aspects, the UE can communicate TBs with the Wireless Communication Device (WCD). For example, the UE can send TBs to and / or receive TBs from the network node using uplink and / or downlink respectively. As another example, the UE can send TBs to and / or receive TBs from another UE using a sidelink. In some aspects, the UE can use feedback procedures (such as HARQ procedures) to manage and / or regulate TBs. The UE can communicate feedback signaling for TBs, such as ACK / NACK feedback signaling, at least in part, based on a switch from Level 1 feedback signaling to Level 2 feedback signaling. For illustration, the UE can analyze the CB error mode of the CB and switch between first-level feedback signaling (e.g., CBG-level feedback signaling) and second-level feedback signaling (e.g., CB-level feedback signaling) based at least in part on the CB error mode of the TB. For illustration, the UE can use the selected level of feedback signaling to send and / or receive feedback signaling.

[0034] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to reduce the amount of air interface resources used by retransmissions by dynamically switching between different levels of feedback signaling, such as dynamically switching between CB-level feedback signaling and CBG-level feedback signaling. For example, the receiving device in the feedback process can select a feedback signaling level that reduces the amount of air interface resources used for retransmissions. For example, the receiving device can analyze error patterns within a TB (e.g., CB error patterns) and select a feedback signaling level and / or reporting format that results in a more efficient retransmission using fewer air interface resources compared to other feedback signaling levels and / or reporting formats. Using fewer air interface resources for retransmissions can increase data throughput in a wireless network and / or reduce data transfer latency within the wireless network.

[0035] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of 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).

[0036] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted in or implemented for 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. These technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. Such technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, etc. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0037] Figure 1This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or elements of a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE120a, UE 120b, UE 120c, UE 120d, and UE 120e).

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

[0039] Various operating bands have been defined by frequency range designations: FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is distinct from the Extremely High Frequency (EHF) band (30 GHz to 300 GHz) designated as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are generally referred to as the midband frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into the midband frequency range. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in the midband frequency range. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in the midband frequency range, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 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 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

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

[0041] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses the complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0042] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographic locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations compliant with the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

[0043] 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). CUs 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, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as functional splits defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0044] 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, 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, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0045] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). A network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may be mobile based on the location of the associated mobile network node 110 (e.g., a train, satellite base station, unmanned aerial vehicle, or non-terrestrial network (NTN) network node).

[0046] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0047] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating 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. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0048] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and downlink BWP may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may 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 one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

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

[0050] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., 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." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0051] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), 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 device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an extended reality (XR) device, a vehicle 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 can communicate via a wireless medium, or may be coupled to them.

[0052] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more 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 (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A processor group that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire processor group that is configured or configured to perform the set of functions.

[0053] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, 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 are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0054] 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 collectively referred to as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0055] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or lower cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs capable of ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100. UEs 120 in the third category may possess intermediate-level complexity and / or capabilities (e.g., capabilities between UEs 120 in the first category and UEs 120 in the second category). UEs 120 in the third category may be referred to as reduced-capacity UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0056] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can use 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 to send and receive sidelink communication. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0057] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0058] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO technology typically utilizes multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some radio access technologies (RATs) can employ advanced MIMO techniques such as mTRP operation (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0059] In some aspects, the UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may communicate TB with the WCD; and switch ACK / NACK feedback for TB based at least in part on switching from a first-level ACK / NACK feedback to a second-level ACK / NACK feedback. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

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

[0061] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0062] Figure 2 This is a diagram illustrating an example network node 110 communicating with an example UE 120 in a wireless network according to the present disclosure.

[0063] like Figure 2As shown, 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 to 232t, where t≥1), a set of antennas 234 (shown as 234a to 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, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0064] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2 Any one or more processors described herein. For example, one or more processors of 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 UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0065] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The first set of processors and the second set of processors can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in combination. Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0066] For downlink communication from network node 110 to UE 120, transmit processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmit processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) according to the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmit processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0067] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., TA set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the set of downlink signals (e.g., [missing information]) together via a set of corresponding antennas 234. T (One downlink signal).

[0068] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

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

[0070] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use for transmitting and / or receiving communication with RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0071] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0072] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to execute network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0073] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 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, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0074] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may provide the decoded data for UE 120 to data sink 260 (which may include data pipelines, data queues, and / or applications executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0075] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from 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 receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). 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, etc. The control information may include indications of RSRP, RSSI, RSRQ, CQI, TPC, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0076] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by a set of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., ... U A set of output symbol streams is provided to modem 254. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0077] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or UUplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0078] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays 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 with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and 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.

[0079] In some examples, each antenna element of antenna 234 or 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, which can be used to independently transmit cross-polarized signals. 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. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0080] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0081] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0082] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0083] Figure 3 This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more decomposed control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link)). The CU 310 may communicate with one or more DU 330s via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340s via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120s via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s.

[0084] Each component in the decomposed base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0085] In some respects, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, 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 may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0086] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0087] The non-RT RIC 350 may include or implement logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for 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 communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0088] 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 an external server. This information can be utilized by the near-RT RIC 370 and can be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may employ AI / ML models to perform corrective actions via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0089] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0090] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies or perform one or more operations associated with the dynamic switching between block-level feedback signaling and block group-level feedback signaling, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies or perform one or more operations associated with the dynamic switching between block-level feedback signaling and block group-level feedback signaling, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may execute or instruct, for example Figure 9 The process 900 Figure 10The operation of process 1000 or other processes as described herein (alone or in combination with one or more other processors). Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing instruction sets (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the instruction set may be made to be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 9 The process 900 Figure 10 The process 1000 or other processes as described herein. In some examples, the execution instructions may include run instructions, transformation instructions, compilation instructions, and / or interpretation instructions, etc.

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

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

[0093] Figure 4 This is a diagram illustrating Example 400 of the HARQ procedure according to this disclosure.

[0094] The MAC layer of the protocol stack can implement a HARQ protocol to provide a faster retransmission mechanism compared to other retransmission mechanisms, such as Radio Link Control (RLC) layer retransmission systems. In some aspects, the HARQ protocol may include a retransmission protocol, such as a transmit and wait (SAW) protocol, used in combination by the transmitting and receiving devices. This SAW protocol enables the receiving device to recover and / or correct data errors in the first HARQ process without hindering data transmission in the second HARQ process. Therefore, multiple HARQ processes can operate in parallel, and data errors identified in the first HARQ process may not hinder transmission in the second HARQ process. Some non-limiting examples of transmitting-receiving device pairs that can implement HARQ processes in combination may include network node 110 and UE 120 (e.g., downlink HARQ process), UE 120 and network node 110 (e.g., uplink HARQ process), and / or the first UE 120 and the second UE 120 (e.g., sidelink HARQ process). Therefore, the HARQ procedure can be used for downlink communication, uplink communication, and / or sidelink communication. In some aspects, and as part of the HARQ procedure, a network node may send information in a downlink control information (DCI) instructing a receiving device (e.g., UE 120) which downlink transmission and / or which uplink transmission should be processed using the HARQ protocol. Alternatively or additionally, and as part of the HARQ procedure, a first UE may send information in a sidelink control information (SCI) instructing a second UE which sidelink transmission should be processed using the HARQ protocol.

[0095] In some respects, HARQ procedures and / or HARQ protocols enable receiving devices to correct errors in received data packets, such as by correcting errors within a TB through soft assembly of packets at the physical (PHY) layer, at least in part, as described below. In some respects, a TB may be divided into one or more code block groups (CBGs), and each CBG may be divided into one or more code blocks (CBs), as per [the relevant description]. Figure 5 As described. To correct errors, the receiving device can buffer one or more data packets that have been identified as containing errors, combine the data packets, and process the combined data packets to reduce errors. In some aspects, "codeword (CW)" can refer to a TB including error protection, and transmission can include multiple CWs.

[0096] Example 400 includes transactions between a transmitting device and a receiving device. Transactions and / or data located above the dashed line 402 are performed by and / or reside at the transmitting device (e.g., network node 110 for downlink HARQ procedures, UE 120 for uplink HARQ procedures, and / or a first UE 120 for sidelink HARQ procedures). Transactions and / or data located below the dashed line 402 are performed by and / or reside at the receiving device (e.g., UE 120 for downlink HARQ procedures, network node 110 for uplink HARQ procedures, and / or a second UE 120 for sidelink HARQ procedures). As indicated by reference numeral 404, the transmitting device may transmit a first data packet 406, which is a new transmission of data included in the first data packet 406 (e.g., a first transmission of data shown in plain white). In some aspects, the transmitting device may buffer and / or store the first data packet 406 as part of a HARQ process until it receives an indication from the receiving device that the first data packet 406 has been received and / or recovered with minimal errors (e.g., no errors and / or a low number of errors meeting a low threshold). Based at least in part on receiving the first data packet 406 with minimal errors, the receiving device may send an acknowledgment (ACK) to the transmitting device, such as a HARQ acknowledgment as indicated by reference numeral 408. The receiving device may use any suitable error detection mechanism to verify the first data packet 406, such as a Cyclic Redundancy Check (CRC) process, which verifies the received data by calculating a CRC value using the received data and comparing the calculated CRC value with the CRC value included in the received data.

[0097] Based at least in part on the receipt of an ACK, the transmitting device may send a second data packet 410, as indicated by reference numeral 412, and the second data packet 410 may be a new transmission of data (e.g., data different from the data included in the first data packet 406). In a similar manner to the first data packet 406, the transmitting device may store the second data packet 410 in a buffer and / or remove the first data packet 406 from the buffer. In some aspects, the receiving device may not successfully receive the second data packet 410. Figure 4The second data packet 410-1 is shown as data packet 410-1. For example, the receiving device may identify that data packet 410-1 was received with a number of errors that failed to meet a low error threshold. Therefore, as shown by reference numeral 414, the receiving device may send a negative acknowledgment (NACK) to indicate that the second data packet 410 was received with errors and / or unsuccessfully. Alternatively or additionally, the receiving device may send a NACK to indicate a request for retransmission of the second data packet 410. In some aspects, and as shown by reference numeral 416, the receiving device may store data packet 410-1 in a buffer 418.

[0098] Based at least in part on the receipt of a NACK, and as indicated by reference numeral 420 in the accompanying drawings, the transmitting device may retransmit the second data packet 410 to the receiving device, wherein the retransmission is initiated by... Figure 4 This is illustrated using a dashed line pattern. The receiving device can receive a retransmission of the second data packet 410 (shown as data packet 410-2), and as shown by reference numeral 422, the receiving device can store data packet 410-2 in buffer 418 and / or can combine data packet 410-1 with data packet 410-2. As an example, the receiving device can combine data packet 410-1 and data packet 410-2 before channel decoding and / or error detection, and can process the combined data packets to mitigate errors, as shown by reference numeral 424. That is, by processing the combined data packets, the receiving device can recover data including minimal errors (e.g., no errors and / or including a number of errors that meet a low error threshold). In some aspects, the receiver can use soft combining to combine data packet 410-1 and data packet 410-2. “Soft combining” can mean combining multiple received signals at least in part based on the confidence and / or reliability of each received signal, such as combining received signals by using the log-likelihood ratio (LLR) to improve the signal quality of the combined data packets and reduce recovery errors.

[0099] In some respects, the receiving device may send an ACK to the sending device, such as in a scenario where the receiving device is able to recover a version of the second data packet 410 including minimal errors. In other respects, the receiving device may send a NACK to the sending device, such as in a scenario where the receiving device is unable to recover a version of the second data packet 410 with minimal errors.

[0100] The HARQ procedure can be used to regulate any combination of PDSCH transmission, PUSCH transmission, and / or Physical Side Link Shared Channel (PSSCH) transmission. Therefore, Figure 4The first data packet 406 and / or the second data packet 410 shown may be transmitted at least in part based on one or more PDSCHs, one or more PUSCHs, and / or one or more PSSCHs. For PDSCH transmission, the receiving device (e.g., UE 120) may send ACK / NACK feedback via PUCCH or PUSCH. For PUSCH transmission, the receiving device (e.g., network node 110) may send ACK / NACK feedback in uplink grant (e.g., via downlink control information (DCI) indication). For sidelink transmission, the receiving device (e.g., UE 120) may send ACK / ACK feedback via the Physical Sidelink Feedback Channel (PSFCH).

[0101] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0102] Figure 5 This is an illustration of example 500 of TB 502, which is divided into one or more CBGs and CBs according to this disclosure.

[0103] Wireless communication devices (WCDs) (such as network node 110 and / or UE 120) may include a corresponding protocol stack that enables a first WCD to communicate with a second WCD (and / or vice versa). The protocol stack may include multiple layers, and each layer may provide different functionality to the device. For illustrative purposes, and by way of example and not limitation, UE 120 and network node 110 may include corresponding PHY layers, Media Access Control (MAC) layers, Radio Link Control (RLC) layers, Packet Data Convergence Protocol (PDCP) layers, and Service Data Adaptation Protocol (SDAP) layers. The SDAP, PDCP, RLC, and MAC layers may be collectively referred to as Layer 2 (L2). Therefore, 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).

[0104] Various protocol layers can interact to enable wireless communication between WCDs. As an example, on the transmitting side (e.g., UE 120 transmitting uplink communication and / or network node 110 transmitting downlink communication), the SDAP layer can receive data streams and map data streams and / or control information to radio bearers. Alternatively or additionally, the SDAP layer can provide data streams to the PDCP layer via corresponding radio bearers. The PDCP layer can provide data in the form of Protocol Data Units (PDUs) to the RLC layer via an RLC channel. The RLC layer can handle the transfer of upper-layer PDUs to the MAC and / or PHY layers, and / or can provide data mapped to logical channels to the MAC layer. The MAC layer can encapsulate data from logical channels into TBs and can provide TBs to the PHY layer on one or more transport channels. The PHY layer can handle various operations related to the transmission of data signals, such as combining... Figure 2 More detailed description.

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

[0106] In some respects, the HARQ procedure can operate at the PHY layer and / or the MAC layer of the protocol stack. For example, the PHY layer can perform a soft combination of one or more transmissions as described with respect to reference numeral 424, and the MAC layer can manage retransmissions. TB 502 is an example TB that can be passed from the MAC layer to the PHY layer for transmission and / or from the PHY layer to the MAC layer after reception. Each TB can be configured to include a single MAC PDU, which can include a large number of bits (e.g., greater than 1 megabit). Thus, and as... Figure 5 As shown, TB can be divided into smaller data units, such as n CBG (by Figure 5 This is represented as CBG 504-1, CBG 504-2, CBG 504-3, and so on up to CBG 504- n ), and each CBG may include a set k One CB, of which n and k It is an integer. Therefore, TB 502 can include...m One CB, of which m It can be calculated as m = n k An integer. Each CB may have a corresponding CRC value generated by the transmitting device and / or checked by the receiving device to identify bit errors within the CB.

[0107] The HARQ process can be performed at the CBG level rather than the TB level to mitigate retransmissions that may exceed the entire TB of 1 Mbit and conserve air interface resources. For example, NACK can be specific to a particular CBG within the TB, such that the retransmission includes data within that specific CBG, rather than the entire TB. However, in some scenarios, CBG-level HARQ retransmissions can lead to inefficiencies, resulting in unnecessary consumption of air interface resources. For example, TB 502 includes CB error mode 506 spanning between CBG 504-2 (e.g., CB 5 and CB 7 shown in dashed patterns) and CBG 504-3 (e.g., CB 8 shown in dashed patterns). The receiving device can identify these errors using any suitable mechanism, such as CB CRC failure. In some aspects, CB error mode 506 can occur under good channel conditions (e.g., strong signal conditions) based at least in part on data preemption and / or data puncturing of TB 502. The punched data inserted into TB 502 can be data pointing to another UE and / or higher priority data. Alternatively or additionally, CB error mode 506 can occur at least in part based on time-frequency selective fading conditions.

[0108] In some respects, CB error mode 506 may be referred to as a sparse error mode and / or a sparse CB failure mode, at least in part, based on the number of failed CBs within the corresponding CBG. Using CBG-level feedback signaling, the receiving device may send a first NACK for CBG 504-2 and / or a second NACK for CBG 504-2, resulting in retransmission of CBG 504-2 and CBG 504-3, and thus retransmission of the entire CB included in CBG 504-2 and the entire CB included in CBG 504-3, even if some CBs are recovered without errors (e.g., CB 4, CB 6, CB 9, CB 10, and CB 11, shown in plain white). Therefore, 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 can retransmit CBG 504-2 and CBG 504-3, and retransmit eight (8) CBs when only three (3) CBs are faulty. Thus, the retransmission of CBG 504-2 and CBG 504-3 for CB error mode 506 results in nearly 70% of air interface resources being used unnecessarily to retransmit CBs that are received and / or recovered without errors. This unnecessary consumption of air interface resources can lead to reduced data throughput and / or increased data transfer latency within the wireless network.

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

[0110] Dynamically switching between different levels of feedback signaling, such as between CB-level and CBG-level feedback signaling, allows the receiving device during the feedback process to select a feedback signaling level that reduces the amount of air interface resources used for retransmission. For example, the receiving device can analyze error patterns within a TB (e.g., CB error patterns) and select a feedback signaling level and / or reporting format that results in a more efficient retransmission using fewer air interface resources compared to other feedback signaling levels and / or reporting formats. Using fewer air interface resources for retransmission can increase data throughput in the wireless network and / or reduce data transfer latency within the wireless network.

[0111] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0112] Figure 6 This is a diagram illustrating Example 600 of an example algorithm that can be used to switch between CBG-level feedback signaling and CB-level feedback signaling according to this disclosure. "Feedback signaling" can refer to ACK / NACK feedback signaling and / or DCI feedback signaling, such as uplink control information (UCI) ACK / NACK feedback signaling for PDSCH and / or block group transmission information (CBGTI) signaling in DCI for PDSCH and / or PUSCH.

[0113] In some aspects, wireless computing devices (WCDs) (such as network node 110 and / or UE 120) can implement the flowcharts described in Example 600 to switch between CBG-level feedback signaling and CB-level feedback signaling to reduce retransmissions of CBs included in the CBG that are received and / or recovered with minimal errors (e.g., no errors and / or a low number of errors meeting a low threshold). As described above, reducing retransmissions of error-free and / or error-reducing CBs can conserve air interface resources, increase data throughput in the wireless network, and / or reduce data transfer latency within the wireless network. The flowcharts included in Example 600 are for discussion purposes, and other specific implementations may include alternative or additional steps for selecting between CBG-level feedback signaling and CB-level feedback signaling to improve retransmission efficiency (e.g., reducing the amount of air interface resources used by retransmissions).

[0114] As shown by reference numeral 602 in the attached figure, WCD can initialize one or more variables and / or counters. For example, WCD can initialize a counter. i Initialize to zero (0), where i It is an integer representing the index of CBG in TB. For example, as about Figure 5 The described TB 502 includes nA CBG, which is indexed as CBG(0) (e.g., for CBG 504-1, i =0), CBG(1) (for example, for CBG 504-2, i =1), until CBG ( n -1) (For example, for CBG 504- n , i = n -1). 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 respects, the CBG ACK counter may track the number of CBGs in the TB that include more CBs with the minimum error than the CBs with the failure error (e.g., the number of errors that failed to meet a low threshold), and the CBG NACK counter may track the number of CBGs in the TB that include more CBs with failure errors than the CBs with the minimum error. CBs with failure errors may alternatively be referred to as failed CBs, and CBs with the minimum error may be referred to as passed CBs.

[0115] As shown by reference numeral 604 in the attached figure, WCD can be analyzed by... i Each CB included in a CBG is analyzed to identify the failed CB. i The first CBG. In other words, WCD can analyze the first CBG. i Each CBG is used to identify whether a CBG includes one or more failed CBs. This is at least partially based on the first... i The CBG does not include failed CBs; the process can follow the "No" path indicated by reference numeral 606 in the attached figure, which includes WCDs. i The counter increments by 1, as shown by reference numeral 608, and the TB is analyzed to identify whether all CBGs within the TB have been analyzed, as shown by reference numeral 610. In some aspects, when some CBGs within the TB have not yet been analyzed, WCD can follow a "No" path as shown by reference numeral 612. Therefore, WCD can return to the decision box shown by reference numeral 604 to analyze the next CBG in the TB (e.g., using an incrementing counter). i The (th) of the counter i +1) CBGs). In other respects, WCD may determine whether to use CBG-level feedback signaling or CB-level feedback signaling by following the "yes" path indicated by reference numeral 614, at least in part, based on the completion of the analysis of all CBGs in the TB, as described below.

[0116] Return to the decision box indicated by reference numeral 604 and the first... iFor the analysis of the first CBG, WCD can follow the "yes" path as shown in Figure 616, and will... i The first number of CBs (and / or CB-level ACKs) within a CBG and the second number of CBs (and / or CB-level ACKs) within a CBG. i A second number of failed CBs (and / or CB-level NACKs) within a CBG is compared, as shown by reference numeral 618 in the attached figure. In some respects, the second number of failed CBs can be at least partially based on the first... i The scaling factor and / or percentage of the total number of failed CBs within a CBG (shown as 50%).

[0117] In some respects, scaling factors can be used for tuning. Figure 6The efficiency of the example algorithm is illustrated. For illustration, the first scaling factor can cause the decision point to be at least partially based on the number of successful CBs (and / or CB-level ACKs) being more than twice the number of failed CBs (and / or CB-level NACKs) in count (e.g., the number of successful CBs is at least two, three, and / or four times the number of failed CBs). Therefore, based at least partially on the fact that the number of successful CBs is higher in count than the number of failed CBs, the number of failed CBs can be described as highly sparse. In such a scenario, fewer air interface resources can be used to signal ACK / NACK feedback via DCI and / or UCI using second-level ACK / NACK feedback (e.g., CB-level ACK / NACK feedback), resulting in improved air interface resource efficiency compared to using first-level ACK / NACK feedback. For the second scaling factor, the number of successful CBs (and / or CB-level ACKs) can be lower in count than the number of failed CBs. In such a scenario, more air interface resources can be used to signal feedback via DCI and / or UCI using second-level ACK / NACK feedback. Therefore, for scenarios associated with a second scaling factor, using first-level ACK / NACK feedback signaling can be more efficient than using second-level ACK / NACK feedback signaling (e.g., using fewer air interface resources). In some aspects, the scaling factor can be tuned and / or selected based on the amount of available air interface resources for performing first-level ACK signaling and second-level ACK / NACK signaling. That is, the scaling factor can be selected, at least in part, based on optimally matching crossover points and / or decision points to achieve more efficient use of air interface resources when using first-level ACK / NACK feedback signaling and second-level ACK / NACK feedback signaling. Thus, the scaling factor can result in a decision point for switching between feedback signaling levels that balances the number of failed CBs within the CBG with the amount of air interface resources available for feedback signaling. For example, the scaling factor can be tuned (e.g., to a value >= 50%) to improve the efficiency of algorithms used for dynamically switching between CBG-level and CB-level feedback signaling. The scaling factor and / or percentage can be signaled to the WCD and / or hardcoded. The “sparse CB failure mode” can be defined as follows: for a set of CBs, the number of failed CBs in the set is less than the number of passed CBs in the set by a threshold.

[0118] Based at least in part on a first number of CBs passing that is greater than or equal to a second number of failed CBs, WCD may follow the "yes" path indicated by reference numeral 620 and may increment the CBG ACK counter as indicated by reference numeral 622. Alternatively or additionally, and based at least in part on a first number of CBs passing that is less than a second number of failed CBs, WCD may follow the "no" path indicated by reference numeral 624 and may increment the CBG NACK counter as indicated by reference numeral 626. In both the "yes" and "no" cases, WCD may be incremented as indicated by reference numeral 608. i The counter and the TB are analyzed as shown by reference numeral 610 to indicate whether all CBGs within the TB have been analyzed before proceeding. In some aspects, when some CBGs within the TB have not yet been analyzed, the WCD may follow a "No" path as shown by reference numeral 612. In other aspects, the WCD may, at least in part, follow a "Yes" path as shown by reference numeral 614 to determine whether to use CBG-level feedback signaling or CB-level feedback signaling based on the completion of analysis of all CBGs in the TB.

[0119] In some respects, to determine whether to use CBG-level feedback or CB-level feedback, the WCD can compare the CBG ACK counter with the CBG NACK counter, as shown in figure 628. As an example, the WCD can compare the CBG ACK counter with a weighted and / or scaled version of the CBG NACK counter, as indicated by reference numeral 628. Figure 6 It is shown as α CBG_highly_NACK, where α is the scaling factor (e.g., CBG_sparse_failure_factor In a manner similar to that described with respect to reference numeral 618, the scaling factor α can be selected, at least in part, based on optimally matching crossover points and / or decision points, to achieve more efficient use of air interface resources using both first-level and second-level ACK / NACK feedback signaling. Alternatively or additionally, the scaling factor α can be selected, at least in part, based on the CB failure modes (and / or the number of failed CBs) across all CBGs within the TB and the amount of air interface resources available for feedback signaling. Therefore, the scaling factor... The efficiency of the algorithm can be improved, at least in part, based on dynamically switching between CBG-level feedback signaling and CB-level feedback signaling (e.g., the amount of air interface resources used for feedback signaling). That is, the scaling factor. The switching point can be tuned to optimize air interface resource efficiency, based at least in part on the number of failed CBs in the TB. The scaling factor α can be signaled to the WCD and / or hardcoded.

[0120] Based at least in part on the calculation that the CBG ACK counter is equal to and / or greater than the CBG NACK counter (e.g., a scaled version of the CBGNACK counter), the WCD may follow the "Yes" path indicated by reference numeral 630 and select CB-level feedback signaling. By selecting CB-level feedback signaling, the WCD can mitigate retransmissions of one or more CBs received within the CBG with minimal errors and conserve air interface resources. Alternatively or additionally, based at least in part on the calculation that the CBG ACK counter is less than the CBGNACK counter, the WCD may follow the "No" path indicated by reference numeral 634 and select CBG-level feedback signaling as indicated by reference numeral 636. By selecting CBG-level feedback signaling, the WCD can reduce the overhead of signaling feedback signaling for retransmissions and conserve air interface resources. Therefore, the ability to switch between CB-level and CBG-level feedback signaling allows the WCD to select the level of feedback signaling that reduces air interface resources for specific error conditions, such as a first error condition that includes more CBs passing through relative to a failed CB and / or a second error condition that includes fewer CBs passing through relative to a failed CB. In other words, WCD can optimize the preservation of air interface resources, at least in part, based on the sparsity of checking CB CRC failures on different CBGs.

[0121] For clarity, Example 600 handles CBG within a single TB (and / or a single CW), but can alternatively or additionally be used for transmissions including multiple TBs and / or multiple CWs. For example, the WCD can perform a first pass (e.g., to completion) of the flowchart for a first TB and / or a first CW included in the transmission to select a first feedback signaling level for the first TB. Alternatively or additionally, the WCD can perform a second pass (e.g., to completion) of the flowchart for a second TB and / or a second CW included in the transmission to select a second feedback signaling level for the second TB. Therefore, feedback signaling for transmissions including multiple TBs and / or multiple CWs can use different feedback signaling types for different TBs.

[0122] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0123] Figure 7A , Figure 7B , Figure 7C , Figure 7D , Figure 7E , Figure 7F and Figure 7GThese are illustrations of the first example 700, the second example 710, the third example 720, the fourth example 730, the fifth example 740, the sixth example 750 and the seventh example 760, respectively, illustrating the CB error modes according to this disclosure.

[0124] The WCD (such as network node 110 and / or UE 120) can determine, for example, by using the flowchart described with respect to Example 600, 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). Alternatively or additionally, the WCD can determine the reporting format for the CB-level feedback signaling based at least in part on the CB error mode. For example, the WCD can support multiple reporting formats for the CB-level feedback signaling, and therefore, at least in part on the CB error mode observed by the WCD, select a specific reporting format that has increased transmission efficiency relative to other reporting formats from among the multiple reporting formats. That is, the WCD can select a specific reporting format that results in retransmissions using fewer air interface resources compared to other reporting formats.

[0125] Figure 7A A first example 700 is illustrated as a single CB error mode 702. Example scenarios that may lead to a single CB error mode may include data preemption (e.g., punching), high phase noise (PN), and / or remote interference management (RIM).

[0126] With regard to Figure 4 In a similar manner as described, TB 704 may include n Each CBG (shown as CBG 706-1, CBG 706-2, CBG 706-3, up to CBG 706-) n ), and each CBG can include k CB (in) Figure 7A The middle is shown as k =5). For the purposes of discussion, Example 700 is at least partially based on maxCodeBlockGroupsPerTransportBlock (For example, the configured parameters) are set to 8, so that the TB 704 can include up to 8 CBGs (e.g., n =8), and the total number of scheduling code blocks (Ncb) in TB 704 can be 38 (e.g., Ncb=38). At least in part based on maxCodeBlockGroupsPerTran sportBlock It is set to 8, meaning the total number of available bits for feedback signaling can be 8.

[0127] WCD can detect CB error mode 702 as a single CB error mode occurring in CB 15 of TB 704, and for an indexing system starting at zero (0), CB 15 can be absolutely indexed within TB 704 at index 14. In some aspects, WCD can choose a single CB report format as the report format, which includes WCD signaling the absolute index of the failed CB index in 8 bits available for feedback signaling. In some aspects, WCD can use fewer bits than 8 available bits. For example, based at least in part on Ncb=38, WCD can use the following formula to calculate the number of bits required to signal the absolute index: ceil(log2[Ncb]) units digit (1) Among them ceil( x The function returns a value greater than or equal to 1. x The smallest integer value, and log2[ y ]return y The base-2 logarithm. For Ncb=38, WCD can use six (6) of the eight feedback signaling bits to indicate the absolute index of the failed CB index (e.g., 0011102 for index 14). Therefore, a single CB report format can include WCD signaling the absolute index of a single failed CB (e.g., within TB).

[0128] Figure 7B The second example 710 shown includes a CB error mode 712 that can be classified as a first CB-based error mode. Example scenarios that could lead to CB error mode 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 failed CBs, and CB 10 is observed as a passed CB. Although CB 10 is observed as a passed CB, the WCD can report CB 10 as a failed CB at least in part based on the use of absolute CB and adjacent CB number reporting formats via CB-level feedback signaling. That is, the WCD can report that four (4) adjacent CBs have failed and / or can use CB-level feedback signaling to request retransmission of the four adjacent CBs. Compared to using CBG-level feedback signaling to request retransmission of CBG 704-2 and CBG 704-3, using CB-level signaling and absolute CB and adjacent CB number reporting formats can reduce the number of air interface resources used for retransmission. For example, retransmission via CB-level feedback signaling can reduce retransmissions by 60% as included in CBG 704-2 and CBG 704-3 as CB-to-CB.

[0129] In some respects, the absolute CB and adjacent CB number reporting format may include an absolute starting CB index that signals the first failed CB (e.g., CB 8) in the adjacent block. For example, using formula (1) above and Ncb=38 as the total number of CBs within TB 704: ceil(log2(38)) = 6 WCD can use 6 bits to signal the absolute start index within the TB of the first failed CB. Therefore, the absolute start index of CB 8 can be represented as 0001112, at least in part, based on an indexing scheme starting with 0. The remaining bits for the absolute CB and adjacent CB number reporting formats can be calculated as follows: Nrem = maxCodeBlockGroupsPerTransportBlock – ceil(log2[Ncb]) (2) In formula (2) use m axCodeBlockGroupsPerTransportBlock = The values ​​of 8 and ceil(log2[Ncb]) = 6: Nrem = 8 – 6 = 2 The absolute CB and adjacent CB number reporting format can use two (2) remaining bits to signal the number of adjacent CBs that are failure CBs after the starting CB index. For example, in Figure 7B In this format, the two remaining bits will be set to 112 to indicate that three (3) adjacent failure CBs (e.g., occurring after the first failure CB indicated by the absolute start index) are failure CBs. Therefore, the absolute CB and adjacent CB number reporting format includes the absolute start index that signals the first failure CB and the number of adjacent failure CBs that occurred after the first failure CB. In some aspects, the least significant bit (LSB) may be used to indicate the absolute start index, and the most significant bit (MSB) may include the number of adjacent failure CBs. For example, for Figure 7B In Example 710, the WCD can signal the absolute start index in the 6 LSBs and the number of adjacent failed CBs in the 2 MSBs as 110001112. However, in other examples, the LSBs can indicate the number of adjacent failed CBs, and the MSBs can indicate the start index of the first failed CB.

[0130] Figure 7CThe third example 720 shown includes a CB error mode 722 that can be classified as a second CB-based error mode. Example scenarios that could lead to CB error mode 722 may include data preemption, PN, RIM, and / or time- and frequency-selective fading. In the third example 720, the WCD observes CB 8, CB 9, CB 11, and CB 12 as failed CBs, and CB 10 as a passed CB. Although CB 10 is observed as a passed CB, the WCD can report CB 10 as a failed CB via CB-level feedback signaling, at least in part, using the absolute CB and relative CB number reporting format as the CB-level feedback signaling reporting format. That is, the WCD can report that five (5) adjacent CBs have failed and / or can use CB-level feedback signaling to request retransmission of the five adjacent CBs. Using CB-level signaling and the absolute CB and relative CB number reporting format can reduce the number of air interface resources used for retransmission compared to using CBG-level feedback signaling to request retransmission of CBG 704-2 and CBG 704-3. For example, retransmission via CB-level feedback signaling can mitigate 50% of the retransmissions included in CBG 704-2 and CBG 704-3 as CB via CB, which will otherwise use CBG-level feedback signaling for retransmission.

[0131] In both absolute and relative CB number reporting formats, the WCD can signal the absolute index of a failed CB located at the center and / or middle of CB error mode 722. In some respects, the WCD can use a number of bits at least partially based on formula (1) above. As an example, Ncb = 38 is used as the total number of CBs within TB 704: ceil(log2(38)) = 6 WCD can use 6 bits to indicate the absolute index of the center failure CB and / or intermediate failure CB. In Example 720, CB 10 is located at the center and / or middle of CB error mode 722, and WCD can use 6 bits to indicate the absolute index of 10 as 0010012, at least in part, based on an indexing scheme starting with 0. WCD can use the above formula (2) to calculate the remaining bits of the absolute CB and relative CB number reporting format. Follow maxCodeBlockGroupsPerTransportBlock = The previous example with 8 and ceil(log2[Ncb]) = 6 allows WCD to calculate the number of remaining bits in the feedback signaling field as follows: Nrem = 8 – 6 = 2 Therefore, and at least in part based on the absolute CB and relative CB reporting format, the WCD can use two remaining bits to signal the number of adjacent CBs, including the failed CB, in both directions of the center and / or intermediate CB index (e.g., CB 10). For example, the two adjacent CBs to the left of CB 10 (e.g., CB 8 and CB 9) are failed CBs, and the two adjacent CBs to the right of CB 10 (e.g., CB 11 and CB 12) are failed CBs. To indicate the number of adjacent failed CBs on each side of the center failed CB (e.g., CB 10), the WCD can set the two remaining bits of the feedback signaling field to 102. Thus, the absolute CB and relative CB number reporting format can include signaling the absolute index of the center failed CB and the number of adjacent failed CBs on each side of the center failed CB. In some aspects, the LSB can indicate the starting index, and the MSB can indicate the number of adjacent failed CBs. For example, for example 720, the WCD can signal: 100010012. However, in other examples, the LSB can indicate the number of adjacent failed CBs on each side of the central failed CB, and the MSB can indicate the absolute index of the central failed CB in the adjacent blocks of the CB.

[0132] Figure 7D The fourth example 730 shown includes a CB error mode 732 that can be classified as a third CB error mode based on adjacent CBs. Example scenarios that could lead to CB error mode 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 failed CBs, and CB 7 is observed as a passing CB. In the fourth example 730, TB 704 includes eight CBGs (shown as CBG 704-1, CBG 704-2, CBG 704-3, up to CBG 704-). n ,in n =8), and each CBG includes three (3) CBs. Therefore, in Example 730, TB 704 includes a total of 24 CBs (e.g., Ncb=24). In some respects, WCD can report failed CBs at least in part based on absolute CBs and bitmap reporting formats as CB-level feedback signaling reporting formats, via CB-level feedback signaling.

[0133] In both absolute CB and bitmap report formats, WCD can use the number of bits that can be calculated using formula (1) above to signal the CB index of the first failed CB (e.g., CB 6). For example 730, Ncb = 24 as the total number of CBs within TB 704: ceil(log2(24)) = 5 WCD can indicate the CB index as 001012 using 5 bits, at least partially based on an indexing scheme starting with 0. WCD can use formula (2) above to calculate the remaining bits for the absolute and relative CB number reporting formats. (Following...) maxCodeBl ockGroupsPerTransportBlock = Given the previous example of 8 and ceil(log2[Ncb]) = 5, WCD can calculate the following number of bits: Nrem = 8 – 5 = 3 Therefore, and at least in part based on the absolute CB and bitmap report format, the WCD can use three remaining bits to signal one or more failed CBs that occurred and / or aligned after the first failed CB (e.g., CB 6). That is, the WCD can use three bits, at least in part, to indicate up to three failed CBs based on each bit mapped to the corresponding CB. For example, the WCD can set the corresponding bit to a first value (e.g., "0") to indicate that the corresponding CB passed the CB, and / or it can set the corresponding bit to a second value (e.g., "1") to indicate that the corresponding CB was a failed CB. To further explain, 1002 can indicate that CB 7 is a failed CB (and CB 8 and CB 9 are passed CBs), 0102 can indicate that CB 8 is a failed CB (and CB 7 and CB 9 are passed CBs), and / or 0012 can indicate that CB 9 is a failed CB (and CB 7 and CB 8 are passed CBs). For CB error mode 732, only CB 8 is a failed CB, and the WCD can indicate 0102 in the remaining three bits, but other examples may include more than one failed CB. Therefore, the absolute CB and bitmap report format may include the absolute index of the first failed CB signaled by the WCD and a bitmap for subsequent CBs, where each bitmap maps to a corresponding CB that occurs after the first failed CB. In some aspects, the LSB may indicate the starting index, and the MSB may indicate the bitmap of the failed CB. For example, for example 730, the WCD may signal 010001012. However, in other examples, the LSB may indicate a bitmap, and the MSB may indicate the absolute index of the first failed CB.

[0134] Figure 7EThe fifth example 740 shown includes a CB error mode 742 that can be classified as a first periodic CB error mode. Example scenarios that may lead to CB error mode 742 may include data preemption, PN, RIM, and / or time- and frequency-selective fading. In the fifth example 740, the periodic CB error mode may be characterized at least in part based on an offset 744 from the start of TB to the first failed 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 mode may be characterized at least in part based on the TB coverage of the periodic failure, such as indicating that the periodic CB error mode spans 100% coverage of the CBs in TB 704, indicating that the periodic CB error mode spans 75% coverage of the CBs in TB 704, indicating that the periodic CB error mode spans 50% coverage of the CBs in TB 704, and / or indicating that the periodic CB error mode spans 25% coverage of the CBs in TB 704. In some aspects, the coverage may be at least in part based on the initial failure CB (e.g., CB 3). For example, 25% coverage may indicate that the periodic CB error mode starts from CB 3 and spans 25% of the CBs in TB 704.

[0135] In some aspects, WCD can use CB offset and periodic reporting formats (e.g., CB-level feedback signaling report format) to indicate the failure of the first periodic CB error mode, and the CB offset and periodic reporting format can divide the feedback signaling field into three subfields: an offset subfield, a periodicity subfield, and a coverage subfield. For illustration, and using one of them... maxCodeBlockGroupsPerTransportBlock =In example 8, WCD may have 8 bits available in the feedback signaling field. Based at least in part on this example, the CB offset and periodic report format may assign three (3) bits to the offset subfield, three bits to the periodic subfield, and two bits to the coverage subfield. WCD may signal the number of offset CBs in the offset subfield for the first failed CB (e.g., 0102 indicates 2, as shown in offset 744), the number of CBs in the periodic CB error mode in the periodic subfield (e.g., 1102 indicates 6, as shown in periodic 746), and / or indicate the coverage mapping in the coverage subfield. For example, based at least in part on using two bits in the coverage subfield, WCD may use mappings where 002 indicates 100% coverage, 012 indicates 75% coverage, 102 indicates 50% coverage, and / or 112 indicates 25% coverage. The feedback signaling field can be divided into offset subfields, periodicity subfields, and / or coverage subfields in any LSB to MSB order (or vice versa). As a non-limiting example, the WCD can signal 001100102, which positions the coverage subfield within 2 MSBs, the offset subfield within 3 LSBs, and the periodicity subfield between the coverage and offset subfields. Other examples may use different orderings than those shown above. Alternatively or additionally, the CB offset and periodicity reporting format may omit the coverage subfield. For example, selecting the CB offset and periodicity reporting format may implicitly indicate that the periodic CB error pattern spans 100% coverage, and the 2-bit subfield may instead indicate the corresponding failed CBs around the center failed CB and / or the number of consecutive failed CBs as described with respect to the sixth example 750, in a manner similar to that described with respect to the third example 720.

[0136] For example, Figure 7F The sixth example 750 shown includes a CB error mode 752 that can be classified as a second periodic CB error mode. Example scenarios that could lead to CB error mode 732 may include data preemption, PN, RIM, and / or time- and frequency-selective fading. In the sixth example 750, and in a similar manner to that described with respect to the fifth example 740, the periodic CB error mode can be characterized at least in part based on an offset 754 to the first failed CB (e.g., shown as a 2 CB offset to CB 3) and periodicity 756 (e.g., shown as 6 CBs). In some aspects, WCD can use CB offset periodicity and a continuous CB reporting format (e.g., a CB-level feedback signaling reporting format). For example, at least in part based on maxCodeBlockGroupsP erTransportBlock =8. The WCD can have 8 bits available in the feedback signaling field, and the CB offset periodicity and continuous CB report formats can divide these 8 available bits into subfields. As an example, and in a manner similar to that described above, the CB offset periodicity and continuous CB report formats can assign 3 bits to the offset subfield and 3 bits to the periodicity subfield. In some respects, using the CB offset periodicity and continuous CB report formats can implicitly indicate 100% coverage of periodic CB error modes. For discussion purposes, the size of each subfield in the fifth and sixth examples described above is at least partially based on the 8-bit feedback signaling field, and signaling fields with more or fewer bits can divide the subfields into sizes different from those described above and below.

[0137] In some respects, the remaining bits of the feedback signaling field can be used to indicate the number of consecutive and / or adjacent failed CBs relative to the base periodicity CB. For example, CB 3, CB 9, CB 15, up to CB 33 can be considered the base periodicity CB based at least in part on the periodicity 756 that restarts at each of these CBs. The CB offset periodicity and consecutive CB reporting format can include a consecutive failed CB subfield to indicate the number of CBs that are failed CBs after the base periodicity CB. For example, and with respect to the 8-bit feedback signaling field, the CB offset periodicity and consecutive CB reporting format can assign the remaining 2 bits to the consecutive failed CB subfield, which can be used to indicate the number of consecutive failed CBs. WCD can set the consecutive failed CB subfield to a first value (e.g., 002) to indicate that none of the CBs in the consecutive CBs are failed CBs, to a second value (e.g., 012) to indicate that the first CB in the consecutive CBs is a failed CB, to a third value (e.g., 102) to indicate that the first consecutive CB and the second consecutive CB are failed CBs, and / or to a fourth value (e.g., 112) to indicate that all three CBs in the consecutive CBs are failed CBs. Indicating a failed CB can implicitly indicate a retransmission request for a failed CB (and / or vice versa). Alternatively or additionally, indicating a failed CB can implicitly indicate a NACK for a failed CB (and / or vice versa).

[0138] At least in part based on Figure 7F As shown in CB error mode 752, WCD can indicate a fourth value (e.g., 112) to indicate the error pattern specified by reference numerals 758-1, 758-2, and 758-1. nAll three consecutive CBs shown are failed CBs. To further explain, within the first set of three consecutive CBs shown by reference numeral 758-1, CB 4 in the zero CB offset position is a passing CB, CB 5 in the first CB offset position is a failed CB, and CB 6 in the second CB offset position is a passing CB. In the set of three consecutive CBs shown by reference numeral 758-1, CB 4 in the zero CB offset position is a passing CB, CB 5 in the first CB offset position is a failed CB, and CB 6 in the second CB offset position is a passing CB. n The three consecutive CB shown are the first n Within the set, CB 34 in the zero CB offset location is a failed CB, CB 35 in the first CB offset location is a passing CB, and CB 36 in the second CB offset location is a failed CB. Combined, the first set of three consecutive CBs and the nth set of three consecutive CBs include failed CBs in the zero CB offset location, the first CB offset location, and the second CB offset location. Therefore, WCD can instruct a fourth value 112 to ensure a retransmission request for each failed CB, which may result in additional retransmissions for one or more passing CBs (e.g., CB 4, CB 6, CB 12, and CB 35). However, additional retransmissions for one or more passing CBs can utilize fewer air interface resources compared to using CBG-level feedback signaling.

[0139] Figure 7G The seventh example 760 shown includes a CB error mode 762 that can be classified as an error mode based on adjacent CBs. Example scenarios that could lead to CB error mode 762 may include data preemption, PN, RIM, and / or time- and frequency-selective fading. In some aspects, WCD may use a CB-level feedback signaling report format to indicate failed CBs in CB error mode 762, which is an absolute CBG and a CB failure bitmap report format.

[0140] In the seventh example 760, TB 704 includes eight CBGs (shown as CBG 704-1, CBG 704-2, CBG 704-3, up to CBG 704- n ,in n=8), and each CBG includes three (3) CBs. Therefore, in the seventh example 760, TB 704 includes a total of 24 CBs (e.g., Ncb=24). In some respects, the absolute CBG and CB failure bitmap report format can divide the feedback signaling field into three subfields: CBG index subfield, CBG bitmap subfield, and consecutive CBG subfield. The CBG index subfield can be used to indicate the absolute index of the first CBG that includes the first failed CB. Each bit included in the CBG bitmap subfield can be mapped to the corresponding CB within the CBG and can be used to indicate the CB error mode within the CBG. The consecutive CBG subfield can be used to indicate the number of consecutive CBGs relative to the first CBG that include the CB error mode indicated by the CBG bitmap subfield.

[0141] As an example, and at least in part based on maxCodeBlockGroupsPerTransportBlock = 8. WCD can have 8 bits available in the feedback signaling field. In some respects, the absolute CBG and CB failure bitmap can assign 3 bits to the CBG index subfield, at least in part based on the fact that each CBG includes 3 CBs (e.g., Nb=3, where Nb represents the number of CBs included in the CBG), and any remaining bits (e.g., 2) of the feedback signaling field can be assigned to the consecutive CBG subfields. In the seventh example 760, the first failed CB is CB 2, and CB 2 is included in CBG 704-1. Using an indexing scheme starting with 0, CBG 704-1 can be assigned an absolute index 0, and therefore WCD can set the CBG index to the subfield to the index value 0002. Within CBG 704-1, CB2 and CB3 are observed as failed CBs, and WCD can configure a bit in the CBG bitmap subfield to a bit error mode that indicates CB2 and CB3 are failed CBs and CB1 is a successful CB. For example, and with respect to... Figure 7DIn a similar manner, WCD can set the corresponding bits in the CBG bitmap subfield that map to CB 2 and CB 3 to the corresponding values ​​indicating failed CBs (e.g., "1"), and set the corresponding bits in the CBG bitmap subfield that map to CB 1 to the values ​​indicating passed CBs (e.g., "0"), thus causing WCD to set the CBG bitmap subfield to 0112. When analyzing consecutive CBG 704-2 and consecutive CBG 704-3, WCD can deduce that the bit error patterns indicated in the CBG bitmap subfields sufficiently describe the failed CBs included in consecutive CBG 704-2 and consecutive CBG 704-3. That is, except for some passed CBs (e.g., CB 5 and CB 9), the bit error patterns in the CBG bitmap subfields indicate the failed CBs in consecutive CBG 704-2 and consecutive CBG 704-3. Therefore, WCD can set the consecutive CBG subfield to a value of 2 (e.g., 102) to extend the application of the bit error pattern indicated by the CBG bitmap subfield to consecutive CBGs, and subsequently indicate a request to retransmit the indicated CB in two consecutive CBGs occurring after the first CBG. Although using the absolute CBG and CB failure bitmap reporting format may result in unnecessary retransmissions via CB 5 and via CB 9, the air interface resources used for these retransmissions are less than for the same failed CB indicated using CBG-level feedback signaling, resulting in reduced air resource consumption relative to CBG-level feedback signaling.

[0142] In some aspects, feedback signaling can indicate the type of feedback signaling level used for feedback signaling (e.g., CB-level feedback type or CBG-level feedback type). For example, and as regarding Figure 6As described, the WCD can determine the dynamic switching between CB-level feedback signaling and / or CBG-level feedback signaling based at least in part on the selection of feedback signaling level types that result in retransmissions using fewer air interface resources. Alternatively or additionally, the WCD can determine the dynamic switching between different CB-level feedback signaling reporting formats based at least in part on the selection of reporting formats that reduce the number of unnecessary CB retransmissions (e.g., for CB) and / or retransmissions resulting in fewer air interface resources. Thus, in some aspects, the WCD can indicate the feedback signaling level type, such as by setting a single overhead bit to a first value (e.g., "0") indicating a first feedback signaling level type (e.g., CB-level feedback signaling or CBG-level feedback signaling) and a second value (e.g., "1") indicating another feedback level type (e.g., CBG-level feedback signaling or CB-level feedback signaling, respectively). As an example, the WCD can first evaluate the CB-level feedback signaling and / or reporting format. Based at least in part on CB error modes and / or reporting formats that identify CB-level signaling as described above as potentially reducing air interface resource consumption, the WCD can configure the feedback signaling field and set a single overhead bit to a value indicating CB-level feedback signaling. Based at least in part on the inability to find a CB error mode and / or reporting format that benefits from CB-level feedback signaling, the WCD can switch to CBG-level feedback signaling and set a single overhead bit to a value indicating CBG-level feedback signaling. That is, if the WCD cannot find suitable CB-level feedback signaling and / or reporting formats that reduce air interface consumption, the WCD can use CBG-level feedback signaling. The single overhead bit can be a bit separate from the example 8-bit feedback signaling field described above and / or can be included in the 8-bit feedback signaling field.

[0143] Alternatively or additionally, the WCD may indicate the reporting format used for CB-level feedback signaling. For example, each of the seven examples of CB-level feedback signaling reporting formats described above may be uniquely indicated by three reporting format overhead bits (e.g., 0002, 0012, up to 1112). The reporting format overhead bits may be separate from and / or included in the 8-bit feedback signaling field of the examples described above. Thus, the reporting format may include a number of bits equal to the total number of possible CBGs included in the TB (e.g., ...). maxCodeBlockGroupsPerTransportBlock Alternatively or additionally, the report format may use more bits than the total possible CBG bits in TB.

[0144] Dynamically switching between different levels of feedback signaling, such as between CB-level and CBG-level feedback signaling, allows the receiving device during the feedback process to select a feedback signaling level that reduces the amount of air interface resources used for retransmission. For example, the receiving device can analyze error patterns within a TB (e.g., CB error patterns) and select a feedback signaling level and / or reporting format that results in a more efficient retransmission using fewer air interface resources compared to other feedback signaling levels and / or reporting formats. Using fewer air interface resources for retransmission can increase data throughput in the wireless network and / or reduce data transfer latency within the wireless network.

[0145] As indicated above, Figure 7A , Figure 7B , Figure 7C , Figure 7D , Figure 7E , Figure 7F and Figure 7G This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7A , Figure 7B , Figure 7C , Figure 7D , Figure 7E , Figure 7F and Figure 7G The examples described are different.

[0146] Figure 8 This is a diagram illustrating an example 800 of a wireless communication process between a transmitting device 802 and a receiving device 804 according to this disclosure. The transmitting device 802 and the receiving device 804 can be different combinations of WCDs, such as network node 110 and UE 120, UE 120 and network node 110, and / or a first UE 120 and a second UE 120, respectively. The notes "transmitting device" and "receiving device" are used with reference to the transmitting and receiving sides of a feedback process and / or retransmission process (such as the HARQ process described above). Therefore, and as... Figure 8 As shown, the transmitting device 802 can send communications to the receiving device 804 and / or receive communications from the receiving device (and / or vice versa).

[0147] As indicated by reference numeral 810 in the accompanying drawings, transmitting device 802 and receiving device 804 can establish a connection with each other, and this connection can include any combination of downlink, uplink, and / or sidelink. For illustration, transmitting device 802 and receiving device 804 can be network node 110 and UE 120 (or vice versa), and UE 120 can be powered on in a cell coverage area provided by network node 110, and UE 120 and network node 110 can perform one or more procedures (e.g., a Random Access Channel (RACH) procedure and / or an RRC procedure) to establish a radio connection. As another example, UE 120 can move to a cell coverage area provided by network node 110 and can perform a handover from a source network node (e.g., another network node 110) to network node 110. In some aspects, transmitting device 802 and receiving device 804 can be a first UE 120 and a second UE 120, and the first UE 120 and the second UE 120 can establish a sidelink with each other.

[0148] Transmitting device 802 and 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., MAC control element (CE)), and / or Layer 3 signaling (e.g., RRC signaling). For example, transmitting device 802 may request capability information via RRC signaling, and / or receiving device 804 may transmit the capability information via RRC signaling (and / or vice versa). Alternatively or additionally, transmitting device 802 and / or receiving device 804 may autonomously transmit capability information to another WCD. In some aspects, the capability information indicates that the WCD supports dynamic switching between first-level feedback signaling (e.g., CBG-level feedback signaling type) and second-level feedback signaling (e.g., CB-level feedback signaling type). Alternatively or additionally, the capability information indicates one or more reporting formats supported for the feedback signaling level type (e.g., CB-level feedback signaling). In some respects, transmitting device 802 may instruct the initiation of a feedback procedure (e.g., a HARQ procedure) and / or instruct one or more air interface resources associated with the feedback procedure.

[0149] As part of communication via this connection, transmitting device 802 may send configuration information via Layer 3 signaling (e.g., RRC signaling) and activate and / or deactivate specific configurations via Layer 2 signaling (e.g., MAC CE) and / or Layer 1 signaling (e.g., DCI and / or SCI). For illustration, network node 110 may send configuration information via Layer 3 signaling at a first time point associated with UE 120 tolerating communication delays, and network node 110 may send activation of the configuration via Layer 2 signaling and / or Layer 1 signaling at a second time point associated with UE 120 not tolerating communication delays.

[0150] As indicated by reference numeral 820 in the attached drawing, transmitting device 802 can transmit communication, and receiving device 804 can receive communication. In some aspects, the communication includes a TB directed to receiving device 804. A TB can be divided into one or more CBGs, and each CBG can be divided into one or more CBs, as per [reference to...]. Figure 5 As described.

[0151] As shown by reference numeral 830 in the attached figure, receiving device 804 can select a feedback signaling level type (e.g., CB level and / or CBG level) for sending feedback (e.g., ACK / NACK feedback) to transmitting device 802. As an example, receiving device 804 can, as per [reference to...] Figure 6 The described method analyzes each CBG included in a TB to select between CBG-level feedback signaling and CB-level feedback signaling. In some aspects, receiving device 804 can analyze multiple TBs and / or multiple CWs within a communication, as described above. Alternatively or additionally, and at least in part based on the selection of CB-level feedback signaling, receiving device 804 can select the reporting format for CB-level feedback signaling (e.g., ACK / NACK feedback signaling) at least in part based on the CB error mode identified by receiving device 804 within the TB. For illustration, and as per [reference to...] Figure 7A As described, the receiving device 804 can identify whether the CB error mode is a single CB error mode and select the single CB report format for CB-level feedback signaling. (See also: Regarding...) Figure 7B , Figure 7C , Figure 7D and / or Figure 7G As described, the receiving device 804 can identify CB error modes based on adjacent CB error modes, and can select the use of absolute CB and adjacent CB number reporting formats, absolute CB and relative CB number reporting formats, absolute CB and bitmap reporting formats, and / or absolute CBG and CB failure bitmap reporting formats for CB-level feedback signaling. In some aspects, and as per [reference to...] Figure 7E and Figure 7F As described, the receiving device 804 can identify the CB error mode as a periodic CB error mode and can select a CB offset and periodic report format or a CB offset periodic and continuous CB report format as the report format for CB-level feedback signaling. Therefore, in some aspects, the receiving device 804 can select a report format from multiple report formats supported by the receiving device 804 based at least in part on the transmission efficiency of the CB error mode and / or the report format (e.g., a report format that reduces the number of air interface resources in retransmissions).

[0152] In some respects, and as about Figure 7A , Figure 7B , Figure 7C , Figure 7D , Figure 7E , Figure 7F and Figure 7G As described, the number of bits used in the report format can be at least partially based on configured parameters, such as... maxCodeBlockGroupsPerTran sportBlock In other words, the feedback signaling field and / or report format may include the number of bits indicated by the configured parameters. However, in other respects, the report format may be based at least in part on more bits than indicated by the configured parameters. For example, for maxCodeBlockGroupsPerTransportBlock =8 example, the report format can use more than 8 bits. For example, the report format may include a first overhead field (e.g., a unit field) indicating the feedback signaling level type and / or a second overhead field (e.g., a 3-bit field) indicating the report format type.

[0153] As indicated by reference numeral 840 in the accompanying drawings, receiving device 804 can send feedback at least partially based on the selected feedback signaling level type, and sending device 802 can receive this feedback. For example, receiving device 804 can send feedback signaling in DCI carried by the downlink, UCI carried by the uplink, and / or SCI carried by the sidelink. In scenarios where receiving device 804 dynamically selects CB-level feedback signaling, the feedback signaling can be at least partially based on CB-level feedback signaling. In some aspects, receiving device 804 can use a selected report format to send feedback, as described above. Alternatively or additionally, in scenarios where receiving device 804 dynamically selects CBG-level feedback signaling, the feedback signaling can be at least partially based on CBG-level feedback signaling. Feedback signaling can include and / or any combination of indicating ACK / NACK feedback (e.g., HARQ ACK / NACK feedback), feedback signaling level type, and / or report format.

[0154] As indicated by reference numeral 850 in the accompanying drawings, transmitting device 802 can transmit retransmissions, and receiving device 804 can receive retransmissions. Retransmissions can be based at least in part on a selected feedback signaling level type used by the receiving device. As an example, transmitting device 802 can retransmit one or more CBGs. As another example, transmitting device 802 can transmit a portion of one or more CBGs by transmitting one or more CBGs (e.g., but not the entire CBG).

[0155] As indicated above, Figure 8 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 8 The examples described are different.

[0156] Figure 9This is a diagram illustrating an example process 900 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 900 is an example in which a device or UE (e.g., UE 120) performs operations associated with dynamically switching between CB-level feedback signaling and CBG-level feedback signaling.

[0157] like Figure 9 As shown, in some aspects, process 900 may include communication with WCD via TB (box 910). For example, UE (e.g., using...) Figure 11 The receiving component 1102, transmitting component 1104 and / or communication manager 1106 described herein can communicate TB with WCD as described above.

[0158] like Figure 9 Further shown, in some aspects, process 900 may include conveying ACK / NACK feedback for TB based at least in part on switching from a first-level ACK / NACK feedback to a second-level ACK / NACK feedback, switching at least in part on the CB error mode based on TB (box 920). For example, the UE (e.g., using...) Figure 11 The receiving component 1102, transmitting component 1104 and / or communication manager 1106 described herein may communicate ACK / NACK feedback for TB based at least in part on switching from first-level ACK / NACK feedback to second-level ACK / NACK feedback, switching at least in part on CB error mode based on TB, as described above.

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

[0160] In the first aspect, communicating the TB and communicating the ACK / NACK feedback includes sending the TB and receiving the ACK / NACK feedback, or receiving the TB and sending the ACK / NACK feedback.

[0161] Secondly, ACK / NACK feedback includes ACK / NACK message signaling.

[0162] Thirdly, ACK / NACK feedback includes DCI feedback signaling.

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

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

[0165] In the sixth aspect, the CB error mode is a single CB error mode, and the reporting format is a single CB report format.

[0166] In the seventh aspect, the CB error mode is based on the error mode of adjacent CBs, and the reporting format is the absolute CB and adjacent CB number reporting format.

[0167] In the eighth aspect, the CB error mode is based on the error mode of adjacent CBs, and the reporting format is an absolute CB and a relative CB number reporting format.

[0168] In the ninth aspect, the CB error mode is based on the adjacent CB error mode, and the reporting format is absolute CB and bitmap reporting format.

[0169] In the tenth aspect, the CB error mode is a periodic CB error mode, and the reporting format is a CB offset and periodic reporting format.

[0170] In the eleventh aspect, the CB error mode is a periodic CB error mode, and the reporting format is a CB offset periodic and continuous CB reporting format.

[0171] In the twelfth aspect, the CB error mode is based on the error mode of adjacent CB, and the reporting format is the absolute CBG and CB failure bitmap reporting format.

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

[0173] In the fourteenth aspect, process 900 includes sending instructions on the report format.

[0174] In the fifteenth aspect, the report format uses a first number of bits that is larger than the second number of possible CBGs in TB.

[0175] In the sixteenth aspect, process 900 includes receiving an instruction on a report format to be used for ACK / NACK feedback at the second level, and communicating ACK / NACK feedback includes using the report format to communicate ACK / NACK feedback.

[0176] In the seventeenth aspect, process 900 includes sending information indicating the ability to dynamically switch between a first level and a second level.

[0177] In the eighteenth aspect, process 900 includes sending capability information indicating support for one or more reporting formats for the second level.

[0178] In the nineteenth aspect, ACK / NACK feedback is based at least in part on the enabling of multiple codewords.

[0179] In the twentieth aspect, communicating ACK / NACK feedback includes using side links to communicate ACK / NACK feedback.

[0180] In aspect twenty-one, the overhead associated with ACK / NACK feedback indicates level two.

[0181] In aspect twenty-two, the overhead associated with ACK / NACK feedback indicates the reporting format for level two.

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

[0183] although Figure 9 An example box of process 900 is shown, but in some respects, process 900 may include... Figure 9 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 900 may be executed in parallel.

[0184] Figure 10 This is a diagram illustrating an example process 1000 performed, for example, at a network node or a device of a network node, according to the present disclosure. Example process 1000 is an example in which a device or network node (e.g., network node 110) performs operations associated with dynamically switching between CB-level feedback signaling and CBG-level feedback signaling.

[0185] like Figure 10 As shown, in some aspects, process 1000 may include communicating TB (box 1010) with the UE. For example, a network node (e.g., using...) Figure 12 The receiving component 1202, transmitting component 1204 and / or communication manager 1206 described herein can communicate TB with the UE as described above.

[0186] like Figure 10 Further shown, in some aspects, process 1000 may include communicating ACK / NACK feedback for TB based at least in part on switching from a first-level ACK / NACK feedback to a second-level ACK / NACK feedback, switching at least in part on the CB error mode based on TB (box 1020). For example, network nodes (e.g., using...) Figure 12The receiving component 1202, transmitting component 1204 and / or communication manager 1206 described herein may communicate ACK / NACK feedback for TB based at least in part on switching from first-level ACK / NACK feedback to second-level ACK / NACK feedback, switching at least in part on CB error mode based on TB, as described above.

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

[0188] In the first aspect, communicating the TB and communicating the ACK / NACK feedback includes sending the TB and receiving the ACK / NACK feedback, or receiving the TB and sending the ACK / NACK feedback.

[0189] Secondly, ACK / NACK feedback includes ACK / NACK message signaling.

[0190] Thirdly, ACK / NACK feedback includes DCI feedback signaling.

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

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

[0193] In the sixth aspect, the CB error mode is a single CB error mode, and the reporting format is a single CB report format.

[0194] In the seventh aspect, the CB error mode is based on the error mode of adjacent CBs, and the reporting format is the absolute CB and adjacent CB number reporting format.

[0195] In the eighth aspect, the CB error mode is based on the error mode of adjacent CBs, and the reporting format is an absolute CB and a relative CB number reporting format.

[0196] In the ninth aspect, the CB error mode is based on the adjacent CB error mode, and the reporting format is absolute CB and bitmap reporting format.

[0197] In the tenth aspect, the CB error mode is a periodic CB error mode, and the reporting format is a CB offset and periodic reporting format.

[0198] In the eleventh aspect, the CB error mode is a periodic CB error mode, and the reporting format is a CB offset periodic and continuous CB reporting format.

[0199] In the twelfth aspect, the CB error mode is based on the error mode of adjacent CB, and the reporting format is the absolute CBG and CB failure bitmap reporting format.

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

[0201] In the fourteenth aspect, process 1000 includes sending instructions on the report format.

[0202] In the fifteenth aspect, the report format uses a first number of bits that is larger than the second number of possible CBGs in TB.

[0203] In the sixteenth aspect, process 1000 includes receiving an instruction on a report format to be used for ACK / NACK feedback at the second level, and communicating ACK / NACK feedback includes using the report format to communicate ACK / NACK feedback.

[0204] In the seventeenth aspect, process 1000 includes receiving capability information of the UE, which indicates support for dynamic switching between a first level and a second level.

[0205] In the eighteenth aspect, process 1000 includes receiving capability information of the UE, which indicates one or more reporting formats supported for the second level.

[0206] In the nineteenth aspect, ACK / NACK feedback is based at least in part on the enabling of multiple codewords.

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

[0208] In aspect twenty-one, the overhead associated with ACK / NACK feedback indicates the reporting format for level two.

[0209] although Figure 10 An example box of process 1000 is shown, but in some respects, process 1000 may include... Figure 10 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1000 may be executed in parallel.

[0210] Figure 11This is a diagram of an example device 1100 for wireless communication according to the present disclosure. Device 1100 may be a UE, or a UE may include device 1100. In some aspects, device 1100 includes a receiving component 1102, a transmitting component 1104, and / or a communication manager 1106 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1106 is combined with... Figure 1 The described communication manager 140. As shown, device 1100 can communicate with another device 1108 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1102 and transmitting component 1104.

[0211] In some respects, device 1100 can be configured to perform the functions described herein. Figures 5 to 8 One or more operations as described herein. Additionally or alternatively, device 1100 may be configured to perform one or more processes described herein (such as...). Figure 9 The process 900) or a combination thereof. In some respects, Figure 11 The illustrated device 1100 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 11 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) 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 function or operation of the component.

[0212] Receiver 1102 may receive communications from device 1108, such as reference signals, control information, data communications, or combinations thereof. Receiver 1102 may provide the received communications to one or more other components of device 1100. In some aspects, receiver 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications, and may provide the processed signals to one or more other components of device 1100. In some aspects, receiver 1102 may include combinations of... Figure 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0213] Transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1108. In some aspects, one or more other components of device 1100 may generate communications and provide the generated communications to transmitting component 1104 for transmission to device 1108. In some aspects, transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and may transmit the processed signals to device 1108. In some aspects, transmitting component 1104 may include combinations of... Figure 2 The described UE 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 combinations thereof. In some aspects, the transmit component 1104 may co-located with the receive component 1102 in one or more transceivers.

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

[0215] The receiving component 1102 and / or the transmitting component 1104 can communicate the TB with the WCD. The receiving component 1102 and / or the transmitting component 1104 can communicate ACK / NACK feedback for the TB based at least in part on switching from a first-level ACK / NACK feedback to a second-level ACK / NACK feedback, switching at least in part on the CB error mode of the TB.

[0216] The communication manager 1106 can select the report format for CB-level ACK / NACK feedback based at least in part on the CB error mode. Alternatively or additionally, the transmitting component 1104 can transmit an indication of the report format. In some aspects, the receiving component 1102 can receive an indication of the report format to be used for second-level ACK / NACK feedback.

[0217] The transmitting component 1104 can transmit capability information indicating support for dynamic switching between a first level and a second level. Alternatively or additionally, the transmitting component 1104 can transmit capability information indicating support for one or more reporting formats for the second level.

[0218] Figure 11The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 11 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 11 The two or more components shown can be implemented within a single component, or Figure 11 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 11 The collection of (one or more) components shown is executable and described as being composed of Figure 11 The other set of components shown performs one or more functions.

[0219] Figure 12 This is a diagram of an example device 1200 for wireless communication according to the present disclosure. Device 1200 may be a network node, or a network node may include device 1200. In some aspects, device 1200 includes a receiving component 1202, a transmitting component 1204, and / or a communication manager 1206 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1206 is combined with... Figure 1 The described communication manager 150. As shown, device 1200 can communicate with another device 1208 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1202 and transmitting component 1204.

[0220] In some respects, device 1200 can be configured to perform the functions described herein. Figures 5 to 8 One or more operations as described herein. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein (such as...). Figure 10 The process 1000) or a combination thereof. In some respects, Figure 12 The illustrated device 1200 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 12 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) 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 function or operation of the component.

[0221] The receiving component 1202 can receive communications from the device 1208, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1202 can provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and can provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combinations of... Figure 2 The described network node may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, receiver component 1202 and / or transmitter component 1204 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 1200 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0222] Transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1208. In some aspects, one or more other components of device 1200 may generate communications and provide the generated communications to transmitting component 1204 for transmission to device 1208. In some aspects, transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and may transmit the processed signals to device 1208. In some aspects, transmitting component 1204 may include combinations of... Figure 2 The described network node includes 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 combinations thereof. In some aspects, the transmit component 1204 may co-located with the receive component 1202 in one or more transceivers.

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

[0224] The receiving component 1202 and / or the transmitting component 1204 may communicate the TB to the UE. The receiving component 1202 and / or the transmitting component 1204 may communicate ACK / NACK feedback for the TB based at least in part on switching from a first-level ACK / NACK feedback to a second-level ACK / NACK feedback, with the switching based at least in part on the CB error mode of the TB.

[0225] The communication manager 1206 can select the report format for CB-level ACK / NACK feedback based at least in part on the CB error mode. In some aspects, the transmitting component 1204 can transmit an indication of the report format. Alternatively or additionally, the receiving component 1202 can receive an indication of the report format to be used for second-level ACK / NACK feedback.

[0226] The receiving component 1202 may receive capability information of the UE, which indicates support for dynamic switching between a first level and a second level. Alternatively or additionally, the receiving component 1202 may receive capability information of the UE, which indicates one or more reporting formats supported for the second level.

[0227] Figure 12 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 12 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 12 The two or more components shown can be implemented within a single component, or Figure 12 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 12 The collection of (one or more) components shown is executable and described as being composed of Figure 12 The other set of components shown performs one or more functions.

[0228] The following provides an overview of some aspects of this disclosure: Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: communicating a transport block (TB) with a wireless communication device (WCD); and communicating ACK / NACK feedback for the TB based at least in part on switching from a first-level ACK / NACK feedback to a second-level ACK / NACK feedback, the switching being based at least in part on a code block (CB) error mode of the TB.

[0229] Aspect 2: According to the method of aspect 1, the communication of the TB and the communication of the ACK / NACK feedback include: sending the TB and receiving the ACK / NACK feedback, or receiving the TB and sending the ACK / NACK feedback.

[0230] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the ACK / NACK feedback includes ACK / NACK message signaling.

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

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

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

[0234] Aspect 7: According to the method of aspect 6, the CB error mode is a single CB error mode, and the report format is a single CB report format.

[0235] Aspect 8: According to the method of aspect 6, wherein the CB error mode is based on the error mode of adjacent CBs, and wherein the report format is an absolute CB and adjacent CB number report format.

[0236] Aspect 9: According to the method of aspect 6, wherein the CB error mode is based on the error mode of adjacent CBs, and wherein the reporting format is an absolute CB and relative CB number reporting format.

[0237] Aspect 10: According to the method of aspect 6, wherein the CB error mode is based on the error mode of adjacent CB, and wherein the report format is an absolute CB and a bitmap report format.

[0238] Aspect 11: According to the method of aspect 6, wherein the CB error mode is a periodic CB error mode, and wherein the reporting format is a CB offset and periodic reporting format.

[0239] Aspect 12: According to the method of aspect 6, the CB error mode is a periodic CB error mode, and the reporting format is a CB offset periodic and continuous CB reporting format.

[0240] Aspect 13: According to the method of aspect 6, wherein the CB error mode is based on the error mode of adjacent CB, and wherein the report format is an absolute CBG and CB failure bitmap report format.

[0241] Aspect 14: According to the method of aspect 6, wherein selecting the report format for the CB-level ACK / NACK feedback includes: selecting the report format from a plurality of report formats based at least in part on the transmission efficiency of the report format for the CB error mode.

[0242] Aspect 15: The method according to aspect 6 further includes: sending an instruction on the report format.

[0243] Aspect 16: According to the method of aspect 6, wherein the report format uses a first number of bits that is larger than the second number of possible CBGs in the TB.

[0244] Aspect 17: The method according to any one of Aspects 1 to 16, the method further comprising: receiving an instruction on a report format to be used for ACK / NACK feedback at the second level, wherein conveying the ACK / NACK feedback comprises: using the report format to convey the ACK / NACK feedback.

[0245] Aspect 18: The method according to any one of aspects 1 to 17, the method further comprising: sending capability information indicating support for dynamic switching between the first level and the second level.

[0246] Aspect 19: The method according to any one of aspects 1 to 18, the method further comprising: sending capability information indicating one or more reporting formats supported for the second level.

[0247] Aspect 20: The method according to any one of Aspects 1 to 19, wherein the ACK / NACK feedback is at least partially based on the enabling of a plurality of codewords.

[0248] Aspect 21: The method according to any one of Aspects 1 to 20, wherein conveying the ACK / NACK feedback comprises: using a side link to convey the ACK / NACK feedback.

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

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

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

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

[0253] Aspect 26: According to the method of aspect 25, communicating the TB and communicating the ACK / NACK feedback includes: sending the TB and receiving the ACK / NACK feedback, or receiving the TB and sending the ACK / NACK feedback.

[0254] Aspect 27: The method according to any one of Aspects 25 to 26, wherein the ACK / NACK feedback includes ACK / NACK message signaling.

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

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

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

[0258] Aspect 31: According to the method of aspect 30, the CB error mode is a single CB error mode, and the report format is a single CB report format.

[0259] Aspect 32: According to the method of aspect 30, the CB error mode is based on the error mode of adjacent CBs, and the report format is an absolute CB and adjacent CB number report format.

[0260] Aspect 33: According to the method of aspect 30, the CB error mode is based on the error mode of adjacent CBs, and the reporting format is an absolute CB and relative CB number reporting format.

[0261] Aspect 34: According to the method of aspect 30, the CB error mode is based on the adjacent CB error mode, and the report format is an absolute CB and a bitmap report format.

[0262] Aspect 35: According to the method of aspect 30, the CB error mode is a periodic CB error mode, and the reporting format is a CB offset and periodic reporting format.

[0263] Aspect 36: According to the method of aspect 30, the CB error mode is a periodic CB error mode, and the reporting format is a CB offset periodic and continuous CB reporting format.

[0264] Aspect 37: According to the method of aspect 30, the CB error mode is based on the error mode of adjacent CBs, and the report format is an absolute CBG and CB failure bitmap report format.

[0265] Aspect 38: According to the method of aspect 30, selecting the report format for the CB-level ACK / NACK feedback includes: selecting the report format from a plurality of report formats based at least in part on the transmission efficiency of the report format for the CB error mode.

[0266] Aspect 39: The method according to aspect 38 further includes: sending an instruction on the report format.

[0267] Aspect 40: According to the method of aspect 30, wherein the report format uses a first number of bits that is larger than the second number of possible CBGs in the TB.

[0268] Aspect 41: The method according to any one of Aspects 25 to 40, the method further comprising: receiving an instruction for a report format to be used for ACK / NACK feedback at the second level, wherein conveying the ACK / NACK feedback comprises: using the report format to convey the ACK / NACK feedback.

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

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

[0271] Aspect 44: The method according to any one of Aspects 25 to 43, wherein the ACK / NACK feedback is at least partially based on a plurality of codewords being enabled.

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

[0273] Aspect 46: The method according to any one of Aspects 25 to 45, wherein the overhead associated with the ACK / NACK feedback indicates the 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 to 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 according to one or more of aspects 1 to 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 being configured to cause the device to perform the method according to one or more of aspects 1 to 46.

[0276] Aspect 49: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 46.

[0277] Aspect 50: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in one or more of aspects 1 to 46.

[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 according to one or more of aspects 1 to 46.

[0279] Aspect 52: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 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 being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 46.

[0281] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various forms of practice.

[0282] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0283] As used in this article, depending on the context, "meeting the threshold" can mean a value 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, not equal to the threshold, etc.

[0284] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: 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 multiple of the same element (e.g., 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, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Similarly, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0286] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors coupled to the one or more memories, the one or more processors being configured to cause the UE to: Transmitting transport blocks (TB) with wireless communication devices (WCD); and The ACK / NACK feedback for the TB is communicated at least in part based on a switch from a first-level ACK / NACK feedback to a second-level ACK / NACK feedback, the switch being at least in part based on the code block (CB) error mode of the TB.

2. The apparatus of claim 1, wherein the first level includes block group level (CBG level) ACK / NACK feedback, and The second level includes 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: The report format for the CB-level ACK / NACK feedback is selected based at least in part on the CB error mode, and In order for the UE to convey the ACK / NACK feedback, the one or more processors are configured to cause the UE to: Use the aforementioned report format to communicate the ACK / NACK feedback.

4. The apparatus of claim 3, wherein the CB error mode is a single CB error mode, and The report format mentioned is the single CB report format.

5. The apparatus of claim 3, wherein the CB error mode is based on the error mode of the adjacent CB, and The report format mentioned above is the absolute CB and adjacent CB number report format.

6. The apparatus of claim 3, wherein the CB error mode is based on the error mode of the adjacent CB, and The report format mentioned above refers to both absolute CB and relative CB number report formats.

7. The apparatus of claim 3, wherein the CB error mode is based on the error mode of the adjacent CB, and The report formats mentioned are absolute CB and bitmap report formats.

8. The apparatus of claim 3, wherein the CB error mode is a periodic CB error mode, and The report format mentioned above is the CB offset and periodic report format.

9. The apparatus of claim 3, wherein the CB error mode is a periodic CB error mode, and The report format mentioned therein is the CB offset periodic and continuous CB report format.

10. The apparatus of claim 3, wherein the CB error mode is based on the error mode of adjacent CBs, and The report format mentioned above is the absolute CBG and CB failure bitmap report format.

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

12. The apparatus of claim 3, wherein the one or more processors are further configured to cause the UE to: Send instructions on the report format.

13. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: Receive instructions on the report format to be used for the second level of ACK / NACK feedback, and In order for the UE to convey the ACK / NACK feedback, the one or more processors are configured to cause the UE to: Use the aforementioned report format to communicate the ACK / NACK feedback.

14. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: Send information indicating the ability to dynamically switch between the first level and the second level.

15. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: Send information indicating the capability to support one or more report formats for the second level.

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

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

18. An apparatus for wireless communication at a network node, the apparatus comprising: One or more memory units; and One or more processors coupled to the one or more memories, the one or more processors being configured to cause the network node to: Communicating transport blocks (TB) with user equipment (UE); and The ACK / NACK feedback for the TB is communicated at least in part based on a switch from a first-level ACK / NACK feedback to a second-level ACK / NACK feedback, the switch being at least in part based on the code block (CB) error mode of the TB.

19. The apparatus of claim 18, wherein, in order for the network node to convey the TB and the ACK / NACK feedback, the one or more processors are configured to cause the network node to: Sending the TB and receiving the ACK / NACK feedback, or Receive the TB and send the ACK / NACK feedback.

20. The apparatus of claim 18, wherein the ACK / NACK feedback includes 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 send downlink control information (DCI) feedback signaling.

22. The apparatus of claim 18, wherein the one or more processors are further configured to provide ACK / NACK feedback at the network node code block group (CBG) level, and The second level includes CB-level ACK / NACK feedback.

23. The apparatus of claim 22, wherein the one or more processors are further configured to cause the network node to: The report format for the CB-level ACK / NACK feedback is selected based at least in part on the CB error mode. In order for the network node to convey the ACK / NACK feedback, the one or more processors are configured to cause the network node to: Use the aforementioned report format to communicate the ACK / NACK feedback.

24. The apparatus of claim 23, wherein the one or more processors are further configured to cause the network node to: Send instructions on the report format.

25. The apparatus of claim 18, wherein the one or more processors are further configured to cause the network node to: Receive instructions on the report format to be used for the second level of ACK / NACK feedback. In order for the network node to convey the ACK / NACK feedback, the one or more processors are configured to cause the network node to: Use the aforementioned report format to communicate the ACK / NACK feedback.

26. The apparatus of claim 18, wherein the one or more processors are further configured to cause the network node to: The system receives information from the UE regarding its ability to dynamically switch 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: The UE receives an indication of its capability information for one or more reporting formats supported by the second level.

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

29. A method for wireless communication performed by a user equipment (UE), the method comprising: Transmitting Transport Blocks (TBs) with Wireless Communication Devices (WCDs); as well as The ACK / NACK feedback for the TB is communicated at least in part based on a switch from a first-level ACK / NACK feedback to a second-level ACK / NACK feedback, the switch being at least in part based on the code block (CB) error mode of the TB.

30. A method for wireless communication performed by a network node, the method comprising: Communicate transport blocks (TB) with user equipment (UE); as well as The ACK / NACK feedback for the TB is communicated at least in part based on a switch from a first-level ACK / NACK feedback to a second-level ACK / NACK feedback, the switch being at least in part based on the code block (CB) error mode of the TB.

Images