Systems and methods for disabling HARQ feedback through multiple transport block scheduling

Abstract

Systems and methods are provided for disabling hybrid automatic repeat request (HARQ) feedback through multiple transport block (TB) scheduling. A wireless communication device may receive, via at least one signaling, at least one configuration of a plurality of transport blocks (TBs) from a wireless communication node and hybrid automatic repeat request (HARQ) related information. The wireless communication device may generate at least one HARQ feedback for the plurality of TBs according to the at least one configuration. The at least one configuration may include an indication of whether bundling for the at least one HARQ feedback is configured.

Description

Technical Field

[0001] This disclosure relates generally to wireless communications, including but not limited to systems and methods for disabling hybrid automatic repeat request (HARQ) feedback through scheduling of multiple transport blocks (TBs). Background Technology

[0002] The Third Generation Partnership Project (3GPP), the standards organization, is currently working on developing a new radio interface called 5G New Radio (5G NR) and a next-generation packet core network (NG-CN or NGC). 5G NR will have three main components: the 5G Access Network (5G-AN), the 5G Core Network (5GC), and user equipment (UE). To facilitate the implementation of different data services and needs, the elements of the 5GC (also known as network functions) have been simplified: some are software-based, while others are hardware-based, allowing for adaptation as needed. Summary of the Invention

[0003] The exemplary embodiments disclosed herein are intended to address problems related to one or more of the problems presented in the prior art and provide additional features that will become apparent from the following detailed description taken in conjunction with the accompanying drawings. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example only and are not restrictive, and that various modifications can be made to the disclosed embodiments while remaining within the scope of this disclosure, as will be apparent to those skilled in the art who have read this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium that includes the following: A wireless communication device (e.g., a user equipment (UE)) can receive at least one configuration and Hybrid Automatic Repeat Request (HARQ) related information for multiple transport blocks (TBs) from a wireless communication node via at least one signaling. The wireless communication device can generate at least one HARQ feedback (e.g., HARQ-ACK information) for the multiple TBs according to at least one configuration. The at least one configuration may include an indication of whether bundling for at least one HARQ feedback is configured. In some embodiments, multiple configurations may exist (e.g., whether bundling is enabled or whether feedback is disabled). The multiple configurations may be configured via different signaling. Bundling for HARQ feedback may refer to aggregating feedback from multiple transport blocks or HARQ processes into a single transmission. The multiple TBs can be scheduled via a single downlink control information (DCI) or a single physical downlink control channel (PDCCH). The at least one signaling may include at least one of the following: downlink control information (DCI) signaling; higher layer signaling; medium access control element (MAC CE) signaling; or radio resource control (RRC) signaling. Multiple TBs may include at least one TB with HARQ feedback disabled.

[0005] In some embodiments, the at least one configuration may further include at least one of the following: an indication of whether one or more TBs in the same bundle are associated with the same HARQ process; an indication of whether feedback for at least one HARQ process is enabled or disabled; or an indication of whether HARQ feedback is enabled or disabled for at least one TB in the bundle.

[0006] In response to the absence of a bundle configured for at least one HARQ feedback, the wireless communication device can generate at least one HARQ feedback for one or more of a plurality of TBs with HARQ feedback enabled. For enhanced machine-type communication (eMTC), multiple bundles can be segmented. AND operations can be performed on a bundle-by-bundle basis.

[0007] In response to a bundle configured with at least one HARQ feedback, a wireless communication device can generate aggregated HARQ feedback for one or more TBs out of a plurality of TBs via a logical AND operation of a single HARQ feedback. The aggregated HARQ feedback can be the result of a logical AND operation of the single HARQ feedback within the bundle. In response to a bundle configured with at least one HARQ feedback and at least one TB out of a plurality of TBs with HARQ feedback enabled, the wireless communication device can generate aggregated HARQ feedback via a logical AND operation of the single HARQ feedback corresponding to at least one TB out of the plurality of TBs. The wireless communication device can generate aggregated HARQ feedback from the logical AND operation by excluding HARQ feedback from one or more TBs out of a plurality of TBs with HARQ feedback disabled. The wireless communication device can perform the logical AND operation by defining the corresponding HARQ feedback for each TB out of a plurality of TBs with HARQ feedback disabled as an acknowledgment (ACK) and including the corresponding HARQ feedback in the logical AND operation.

[0008] In response to the absence of a bundle configured for at least one HARQ feedback, the wireless communication device may generate at least one HARQ feedback for one or more of a plurality of TBs with HARQ-enabled feedback.

[0009] In some embodiments, the wireless communication device may generate aggregated HARQ feedback via a logical AND operation of individual HARQ feedbacks corresponding to each of the plurality of TBs. The wireless communication device may also generate aggregated HARQ feedback by bundling one or more of the plurality of TBs via a logical AND operation of individual HARQ feedbacks corresponding to the HARQ feedbacks of one or more of the plurality of TBs with HARQ enabled feedback.

[0010] Having at least one Transport Block (TB) with HARQ feedback enabled can instruct HARQ feedback to be enabled for at least one HARQ process associated with that TB. Having at least one TB with HARQ feedback disabled can instruct HARQ feedback to be disabled for at least one HARQ process associated with that TB. A Transport Block (TB) with HARQ feedback enabled can instruct HARQ feedback to be enabled for the associated HARQ process that has the TB. This can instruct feedback reception to be enabled for the corresponding HARQ process to assess the success or failure of the transmission. A Transport Block (TB) with HARQ feedback disabled can instruct HARQ feedback to be disabled for the associated HARQ process that has the TB. This can instruct feedback reception to be disabled, and the HARQ process continues without waiting for feedback to determine the result of the transmission.

[0011] In some embodiments, a wireless communication device may associate at least one of a plurality of TBs in the same bundle with at least one identical HARQ process. TBs in the same bundle are associated with the same HARQ process. Thus, TBs with feedback enabled and TBs with feedback disabled are not mixed within the same bundle. At least one identical HARQ process associated with at least one of the multiple TBs can include at least one of the following: HARQ process 0; HARQ process 1; M HARQ processes, wherein the HARQ process ID is associated with a TB bundle index with or without an offset; M HARQ processes, wherein at least one identical HARQ process for each bundle is the HARQ process with the lowest HARQ process ID in the bundle; M HARQ processes, wherein at least one identical HARQ process for each bundle is the HARQ process with the highest HARQ process ID in the bundle; M HARQ processes, wherein at least one identical HARQ process for each bundle is a HARQ process associated with at least one TB in the bundle with the lowest TB index; M HARQ processes, wherein at least one identical HARQ process for each bundle is a HARQ process associated with at least one TB in the bundle with the highest TB index; or M HARQ processes with HARQ process IDs starting from at least one identical HARQ process associated with the first TB. M can be the number of bundles. In response to the fact that at least one identical HARQ process associated with at least one TB in the same bundle is HARQ feedback disabled, the wireless communication device may generate an acknowledgment (ACK). In response to the fact that at least one identical HARQ process associated with at least one TB in the same bundle is HARQ feedback disabled, no HARQ-ACK is generated for that at least one TB. In response to the fact that at least one identical HARQ process associated with at least one TB in the same bundle is HARQ feedback enabled, the wireless communication device may generate an aggregated HARQ feedback for at least one TB in the same bundle via a logical AND operation of a single HARQ feedback. The wireless communication device may generate at least one HARQ feedback for bundling according to at least one configuration.

[0012] In some embodiments, a wireless communication node may send at least one configuration and Hybrid Automatic Repeat Request (HARQ) related information for multiple transport blocks (TBs) to a wireless communication device (e.g., a UE) via at least one signaling. The wireless communication device may generate at least one HARQ feedback (e.g., HARQ-ACK information) for the multiple TBs based on at least one configuration. The at least one configuration may include an indication of whether a bundle for at least one HARQ feedback is configured. Attached Figure Description

[0013] Various exemplary embodiments of this solution are described in detail with reference to the following figures or drawings. The figures are provided for illustrative purposes only and depict only exemplary embodiments of the solution to aid the reader's understanding. Therefore, these figures should not be considered as limitations on the breadth, scope, or applicability of this solution. It should be noted that these figures are not necessarily drawn to scale for clarity and ease of explanation.

[0014] Figure 1 An example cellular communication network according to an embodiment of the present disclosure is shown, in which the techniques disclosed herein can be implemented; Figure 2 Block diagrams of example base stations and user equipment according to some embodiments of the present disclosure are shown; Figure 3 Example implementations of non-terrestrial networks (NTNs) according to some embodiments of the present disclosure are shown; Figure 4 Example representations of stopping and disabling HARQ feedback according to some embodiments of the present disclosure are shown; and Figure 5 A flowchart is shown as an example method for disabling Hybrid Automatic Repeat Request (HARQ) feedback through multiple transport block (TB) scheduling, according to embodiments of the present disclosure. Detailed Implementation

[0015] 1. Mobile communication technology and environment Figure 1 An example wireless communication network and / or system 100 that can implement the techniques disclosed herein is illustrated according to embodiments of this disclosure. In the following discussion, wireless communication network 100 can be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as "network 100". Such an example network 100 includes base stations 102 (hereinafter referred to as "BS 102", also called wireless communication nodes) and user equipment 104 (hereinafter referred to as "UE 104", also called wireless communication devices) that can communicate with each other via communication links 110 (e.g., wireless communication channels), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1In this context, BS 102 and UE 104 are contained within their respective geographical boundaries in cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating on its allocated bandwidth to provide sufficient radio coverage to the intended users of that cell.

[0016] For example, BS 102 can operate on the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can also be divided into subframes 120 / 127, which can include data symbols 122 / 128. In this disclosure, BS 102 and UE 104 are generally described herein as non-limiting examples of "communication nodes" that can practice the methods disclosed herein. According to various embodiments of this solution, such communication nodes may be capable of wireless and / or wired communication.

[0017] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM (orthogonal frequency division multiplexing) / OFDMA (orthogonal frequency division multiplexing access) signals) according to some embodiments of this solution is shown. System 200 may include components and elements configured to support known or conventional operating characteristics that do not need to be described in detail herein. In one illustrative embodiment, system 200 may be used in wireless communication environments (such as those described above) Figure 1 In a wireless communication environment 100, communication (e.g., sending and receiving) data symbols.

[0018] System 200 typically includes base station 202 (hereinafter referred to as "BS 202") and user equipment 204 (hereinafter referred to as "UE 204"). BS 202 includes BS (base station) transceiver module 210 (hereinafter also referred to as transceiver module 210, transceiver 210 or base station transceiver 210), BS antenna 212 (hereinafter also referred to as antenna 212, downlink antenna 212 or RF antenna arrangement 212), BS processor module 214 (hereinafter also referred to as processor module 214), BS memory module 216 (hereinafter also referred to as memory module 216) and network communication module 218, each module being coupled and interconnected with each other as needed via data communication bus 220. UE 204 includes a UE (User Equipment) transceiver module 230 (hereinafter also referred to as UE transceiver 230, transceiver module 230, or transceiver 230), a UE antenna 232 (hereinafter also referred to as antenna 232, uplink antenna 232, or RF antenna arrangement 232), a UE memory module 234 (hereinafter also referred to as memory module 234), and a UE processor module 236 (hereinafter also referred to as processor module 236). Each module is coupled to and interconnected with each other as needed via a data communication bus 240. BS 202 communicates with UE 204 via a communication channel 250 (hereinafter also referred to as: wireless transmission link 250, wireless data communication link 250), which may be any wireless channel or other medium suitable for the data transmission described herein.

[0019] As those skilled in the art will understand, system 200 may also include, in addition to Figure 2 Any number of modules other than those shown herein. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described in general terms of their functionality. Whether this functionality is implemented as hardware, firmware, or software may depend on the specific application and design constraints imposed on the system as a whole. Those skilled in the art can implement this functionality appropriately for each specific application; however, such implementation decisions should not be construed as limiting the scope of this disclosure.

[0020] According to some embodiments, UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 including a radio frequency (RF) transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 232. A duplex switch (not shown) may alternately couple the uplink transmitter or receiver to the uplink antenna in a time-duplex manner. Similarly, according to some embodiments, BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 including an RF transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to downlink antenna 212 in a time-division duplex manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that while the downlink transmitter is coupled to downlink antenna 212, the uplink receiver circuitry is coupled to uplink antenna 232 to receive transmissions via wireless transmission link 250. Conversely, the operation of the two transceivers 210 and 230 can be coordinated in time, such that while the uplink transmitter is coupled to the uplink antenna 232, the downlink receiver is coupled to the downlink antenna 212 to receive transmissions via the wireless transmission link 250. In some embodiments, there is tight time synchronization with a minimum guard time between changes in the duplex direction.

[0021] UE transceiver 230 and base transceiver 210 are configured to communicate via wireless data communication link 250 and cooperate with RF antenna arrangements 212 / 232 appropriately configured to support specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 210 and base transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited to application to specific standards and associated protocols. Rather, UE transceiver 230 and base transceiver 210 may be configured to support alternative or additional wireless data communication protocols (including future standards or variations thereof).

[0022] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, UE 204 may be implemented in various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 may be implemented or realized using a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of multiple computing devices, such as a combination of a digital signal processor and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors incorporating a digital signal processor core, or any other combination of such configurations.

[0023] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be directly implemented in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any practical combination thereof. Memory modules 216 and 234 can be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 can be coupled to processor modules 210 and 230 respectively, such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234 respectively. Memory modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include cache memory for storing temporary variables or other intermediate information during the execution of instructions to be executed by processor modules 210 and 230 respectively. Memory modules 216 and 234 may each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0024] Network communication module 218 broadly represents the hardware, software, firmware, processing logic, and / or other components of base station 202 that enable bidirectional communication between base station transceiver 210 and other network components and communication nodes configured to communicate with base station 202. For example, network communication module 218 may be configured to support Internet or WiMAX (World Interoperability for Microwave Access) services. In a typical but non-limiting deployment, network communication module 218 provides an 802.3 Ethernet interface, allowing base station transceiver 210 to communicate with traditional Ethernet-based computer networks. In this way, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms “configured for,” “configured to,” and their various variations used in this document in relation to a specified operation or function refer to devices, components, circuits, structures, machines, signals, etc., that are physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0025] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) for interconnecting and communicating with other systems. The model is divided into seven sub-components or layers, each representing a conceptual set of services provided to its upper and lower layers. The OSI model also defines logical networks and efficiently describes computer packet transmission using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or the seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the Media Access Control (MAC) layer. In some embodiments, the third layer may be the Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be the Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be the Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be a Non-Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer is other layers.

[0026] Various exemplary embodiments of this solution are described below with reference to the accompanying drawings to enable those skilled in the art to create and use this solution. As will be apparent to those skilled in the art, various changes or modifications can be made to the examples described herein without departing from the scope of this solution after reading this disclosure. Therefore, this solution is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein is merely exemplary. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, this solution is not limited to the specific order or hierarchy presented.

[0027] 2. Systems and methods for disabling Hybrid Automatic Repeat Request (HARQ) feedback through multi-transmission block (TB) scheduling. In Hybrid Automatic Repeat Request (HARQ) mechanisms, HARQ processes can perform new retransmissions after receiving feedback. However, in scenarios with long propagation delays (such as non-terrestrial networks (NTNs)), HARQ processes may face significant waiting times for feedback before proceeding with the next transmission. This delay can lead to HARQ stalls, where all HARQ processes have completed their transmissions but have not received feedback due to a large round-trip delay (RTT). To avoid HARQ stalls and increase throughput in NTN environments, disabling HARQ feedback can be considered. Disabling HARQ feedback allows for temporary deactivation of feedback reception, enabling the transmitter to continue transmitting without waiting for feedback.

[0028] However, current methods for disabling HARQ feedback mechanisms primarily focus on single-TB scheduling scenarios. When multiple TBs are scheduled by a single DCI, whether / how feedback is transmitted remains unresolved, especially in scenarios where HARQ processes with and without feedback enabled are scheduled by the same DCI. Therefore, this disclosure investigates disabling HARQ feedback mechanisms for multi-TB scheduling scenarios.

[0029] Currently, disabling HARQ feedback mechanisms primarily focuses on single transport block (TB) scheduling. However, when multiple TBs are scheduled using a single downlink control information (DCI), feedback transmission becomes a concern. Specifically, when a hybrid HARQ process with both enabled and disabled feedback is scheduled using the same DCI, uncertainty may arise regarding how to handle feedback transmission. Therefore, this disclosure specifically addresses the scenario of multi-TB scheduling and investigates disabling HARQ feedback mechanisms. This disclosure mitigates the impact of long latency and enhances system performance in NTN deployments for various communication applications.

[0030] Figure 3 An example structure of a transparent NTN according to some embodiments of this disclosure is shown. The link between the UE (e.g., user equipment, UE 104, UE 204, mobile device, wireless communication device, terminal, etc.) and the satellite can be a serving link. The link between the BS (e.g., base station, BS 102, BS 202, gNB, eNB, wireless communication node, etc.) and the satellite can be a feeder link and can be common to all UEs within the same cell. Due to the high altitude of the satellite, the propagation delay can be significant. For NTNs, especially for airborne entities in geosynchronous equatorial orbit (GEO), the RTT between the UE and the BS can be as long as hundreds of milliseconds due to the long (signal transmission / propagation) distance (one or more). In low Earth orbit (LEO), the RTT between the UE and the BS can be from a few milliseconds to tens of milliseconds.

[0031] Figure 4 Representations of HARQ pauses and disabling HARQ feedback according to some embodiments of this disclosure are shown. New Radio (NR)-NTN can support disabling HARQ feedback. By disabling HARQ feedback for a specific HARQ process, continuous transmission of new transport blocks (TBs) becomes possible without stopping the waiting process. This capability is... Figure 2 The second scenario is illustrated. Therefore, HARQ pauses caused by large round-trip times (RTTs) can be avoided, thereby improving throughput. In terms of configuration, per-HARQ process enable / disable configuration based on Radio Resource Control (RRC) is supported, providing the necessary flexibility and control for the HARQ feedback mechanism.

[0032] In Internet of Things (IoT)-NTN, disabling HARQ feedback can be supported. Enable / disable configuration per HARQ process based on RRC can be supported. Furthermore, enable / disable configuration based on Downlink Control Information (DCI) can disable feedback for scheduling Transport Blocks (TBs). Compared to New Radio (NR), Narrowband IoT (NB-IoT) and enhanced Machine Type Communication (eMTC) support scheduling multiple Transport Blocks (TBs) using a single Downlink Control Information (DCI). Therefore, the same DCI can be used to schedule HARQ processes with and without feedback enabled. However, determining how to handle this scenario remains an ongoing topic of discussion and research. In the context of NB-IoT and eMTC, the best methods for managing the transmission and reception of feedback in such situations are being actively explored.

[0033] Example 1 of implementation: HARQ feedback bundling for mixed enabling and disabling of feedback For NB-IoT and eMTC, when multiple transport blocks (TBs) are scheduled by a single downlink control information (DCI) and hybrid automatic repeat request (HARQ) bundles are applicable to HARQ feedback, how to handle such situations when HARQ feedback is disabled in a portion of the TBs may present challenges that require further research.

[0034] In the following disclosure, HARQ feedback can refer to HARQ-ACK information. A Transport Block (TB) with HARQ feedback enabled can refer to enabling HARQ feedback for the associated HARQ process that has the TB. This can instruct feedback reception to be enabled for the corresponding HARQ process to assess the success or failure of the transmission. A Transport Block (TB) with HARQ feedback disabled can refer to disabling HARQ feedback for the associated HARQ process that has the TB. This can instruct feedback reception to be disabled, and the HARQ process continues without waiting for feedback to determine the result of the transmission.

[0035] - For NB-IoT, when multiple TBs are scheduled by a single DCI, the HARQ-ACK binding process can be as follows: -against , -If UE is npdsch-MultiTB-Config High-level parameters are configured in the middle. harq-AckBundlingFurthermore, the narrowband physical downlink shared channel (NPDSCH) corresponds to the narrowband physical downlink control channel (NPDCCH) with DCI cyclic redundancy check (CRC) scrambled by the cell radionetwork temporary identifier (C-RNTI). -ACK / NACK (Negative Acknowledgement) responses can be achieved by executing a TB... r+1 It is generated by the logical AND operation of the corresponding HARQ-ACK, where .

[0036] The UE can perform a logical AND operation on all ACK / NACK operations for all TBs. That is, if at least one NACK exists, the final response for the bundled TB can be a NACK.

[0037] When a subset of TBs scheduled by a single DCI have HARQ feedback disabled, at least one TB with disabled HARQ feedback can be excluded from the bundle (e.g., not considered when performing a logical AND operation). Therefore, when multiple TBs are scheduled by a single DCI, at least one of the following processes can be supported: When HARQ-ACK binding is not configured, HARQ feedback may not be generated / reported for at least one TB with HARQ feedback disabled.

[0038] When HARQ-ACK bundling is configured and / or at least one TB is HARQ feedback enabled, the ACK / NACK response can be generated by performing a logical AND operation with the HARQ-ACK corresponding to the scheduled TB, excluding at least one TB with HARQ feedback disabled. For example, the ACK / NACK response can be generated by performing a AND operation with the scheduled TB. The corresponding HARQ-ACK logical AND operation is used to generate it, where r+1 refers to the index of at least one TB that enables HARQ feedback. The ACK / NACK response can be generated by performing a logical AND operation with the HARQ feedback enabled. It is generated by the logical AND operation of the corresponding HARQ-ACK. .

[0039] When HARQ-ACK binding is configured and / or at least one TB is HARQ feedback enabled, an acknowledgment (ACK) can be assumed / generated / reported for at least one TB with HARQ feedback disabled (e.g., when generating an ACK / NACK response / performing a logical AND operation). For example, an ACK / NACK response can be achieved by performing an AND operation. It is generated by the logical AND operation of the corresponding HARQ-ACK, where, HARQ-ACK corresponding to at least one TB with HARQ feedback disabled is assumed to be ACK.

[0040] When HARQ feedback is disabled for all scheduled TBs, HARQ feedback may not be generated / transmitted. This procedure can be applied regardless of whether HARQ-ACK binding is configured.

[0041] When HARQ-ACK binding is configured, at least one TB with HARQ feedback disabled can be disregarded when generating / transmitting ACK / NACK responses. For example, if the UE is in npdsch-MultiTB-Config High-level parameters are configured in the middle. harq- AckBundling Furthermore, if the Narrowband Physical Downlink Shared Channel (NPDSCH) corresponds to the Narrowband Physical Downlink Control Channel (NPDCCH) with DCI Cyclic Redundancy Check (CRC) scrambled by the Cell Radio Network Temporary Identifier (C-RNTI), then only at least one TB with HARQ feedback enabled will be considered.

[0042] For eMTC, when multiple TBs are scheduled by a single DCI, the process for HARQ-ACK bundling can be as follows: For low-complexity / enhanced coverage (BL / CE) UEs with reduced bandwidth, if the UE is configured with CEModeA (CE Mode A), and if the UE is in ce-PDSCH-MultiTB-Config (ce-PDSCH-MultiTB-Configuration) High-level parameters are configured in the middle. harq-AckBundling Furthermore, multiple TBs are scheduled in the corresponding DCI format 6-1A with CRC scrambled by C-RNTI. - For HARQ-ACK transmissions associated with the corresponding DCI, the UE can bind A in TB. b Perform a logical AND operation of HARQ-ACK on all TBs to generate M HARQ-ACK bits, where b=1, …, M; - Belongs to TB bundle A b The collection of TBs and the number of TB bundles M This can be given in Table 1; - The value can be the number of scheduling TBs determined in the corresponding DCI.

[0043] Table 1: Different values ​​for the DCI field "Multi-TB HARQ-ACK Bundle Size" and the number of scheduled transport blocks N TB Different values ​​of A b and the value of M

[0044] Based on different configurations of multi-TB HARQ-ACK bundle size and the number of scheduled TBs, TBs can be divided into different bundles, and a logical AND operation of HARQ-ACK can be performed on each bundle.

[0045] When a portion of the TBs scheduled by a single DCI have HARQ feedback disabled, enhancements may be needed because all scheduled TBs are considered in the bundle partitioning. N TB The value can be the number of scheduled TBs determined in the corresponding DCI. When multiple TBs are scheduled by a single DCI, at least one of the following enhancements can be considered: 1. Bundle partitioning can be the same as the current specification. When generating HARQ-ACK, at least one TB with HARQ feedback disabled in each bundle can be disregarded. For example, for HARQ-ACK transmissions associated with the corresponding DCI, the UE can bundle each TB... In the process of enabling HARQ feedback, a logical AND operation is performed on all TBs to generate M HARQ-ACK bits, where b = 1, …, M. More specifically, assume that… And the DCI field "Multi-TB HARQ-ACK Bundle Size" equals "10", if , , If HARQ feedback is disabled, then TB bundling It could be: , , .

[0046] When performing the logical AND operation of HARQ-ACK, the deleted TB is not considered.

[0047] If all TBs in the bundle have feedback disabled, then: The ACK is generated for this bundle. For example, suppose... And the DCI field “Multi-TB HARQ-ACK Bundle Size” equals “10”, if , , and If HARQ feedback is disabled, then the three bundles can be generated as follows: , , .

[0048] For example, the UE can generate 3 HARQ-ACK bits. (For...) A A 1 in the HARQ-ACK bit can be set to ACK. For A The 2 HARQ-ACK bits can be used to... TB 3 and TB 4. Generate it by performing a logical AND operation on HARQ-ACK. (For...) A The 3 HARQ-ACK bits can be used to... TB 6 and TB 7. Generate by performing a logical AND operation on HARQ-ACK.

[0049] No HARQ-ACK was generated for the bundle. The number of HARQ-ACK bits M can be reduced accordingly. For example, suppose... N TB =8 and the DCI field "Multi-TB HARQ-ACK Bundle Size" equals "10", if , , and If HARQ feedback is disabled, then the three bundles can be generated as follows: , , .

[0050] UE can be targeted separately and Generate 2 HARQ-ACK bits. (Targeting...) The HARQ-ACK bits can be used to... and Generate it by performing a logical AND operation on HARQ-ACK. (For...) The HARQ-ACK bits can be used to... and Generate it by performing a logical AND operation on HARQ-ACK.

[0051] 2. Bundle partitioning can be the same as the current specification. When generating a HARQ-ACK, at least one TB (Bundle) with HARQ disable feedback in each bundle can be assumed / generated / reported as an ACK. For example, for a HARQ-ACK transmission associated with the corresponding DCI, the UE can perform this by bundling the TBs... Perform a logical AND operation of HARQ-ACK on all TBs to generate M 1 HARQ-ACK bit, of which, b =1, …, M HARQ-ACK corresponding to TB with HARQ feedback disabled is assumed to be ACK.

[0052] More specifically, assuming And the DCI field "Multi-TB HARQ-ACK Bundle Size" equals "10", if 、 、 If HARQ feedback is disabled, then TB bundling... It could be: , , .

[0053] When performing a logical AND operation on HARQ-ACK, the HARQ-ACK corresponding to the bolded TB can be assumed to be ACK. If all TBs in the bundle have feedback disabled, a similar approach to the first enhancement can be considered.

[0054] 3. In and The definition can exclude at least one TB with HARQ feedback disabled. Then the current process can be reused. For example: Belongs to TB bundle The set of TBs and the number M of TB bundles can be given in Table 1; where only at least one TB with HARQ feedback enabled is considered. N TB The value can be the number of scheduling TBs with HARQ feedback enabled, as determined in the corresponding DCI.

[0055] More specifically, when 8 TBs are scheduled by DCI, but only 4 TBs have HARQ feedback enabled, then By assuming the DCI field "Multi-TB HARQ-ACK Bundle Size" equals "10", the three bundles can be generated as follows: , , .

[0056] , , and This can refer to a TB with HARQ feedback enabled, scheduled by DCI. TBs with HARQ feedback disabled may not be considered during the HARQ-ACK generation process.

[0057] If HARQ feedback is enabled, the number of TBs Compared with the candidates in Table 1 If any of the values ​​do not match, enhancement may be required. For example, a minimum number of candidates greater than or equal to the number of TBs with HARQ feedback enabled could be applied. Value. For TB bundles, TBs with HARQ feedback enabled can be assigned to TB bundles sequentially. Regarding the bundling of TB For available space, at least one of the following should be considered: When generating HARQ-ACK, free space may not be considered.

[0058] When generating a HARQ-ACK, an ACK for free space can be assumed / generated.

[0059] For TB bundles that do not contain TBs with HARQ feedback enabled, HARQ-ACK bits cannot be generated.

[0060] More specifically, when 8 TBs are scheduled by DCI, but only 3 TBs have HARQ feedback enabled, then the application... =4 is used for TB bundling. By assuming the DCI field "Multi-TB HARQ-ACK Bundle Size" is equal to "10", 3 bundles can be generated as follows: , , .

[0061] , and This can refer to a TB with HARQ feedback enabled, scheduled by DCI. The UE can: Specifically for and Generate 2 HARQ-ACK bits. (Targeting...) HARQ-ACK information is not generated or transmitted.

[0062] Specifically for , and Generate 3 HARQ-ACK bits. (Targeting...) Generate an ACK.

[0063] Furthermore, if all TBs have feedback disabled, HARQ-ACK will not be generated / transmitted.

[0064] Example 2 of implementation: When configuring HARQ feedback binding, Association with HARQ process In Implementation Example 1, each TB is associated with an independent HARQ process. Therefore, TBs with feedback enabled and TBs with feedback disabled can be bundled. If the association between TBs and HARQ processes is strengthened, the bundling of TBs with and without HARQ feedback can be avoided. For example, when multiple TBs are scheduled by a single DCI and HARQ-ACK bundling is configured, TBs in the same bundle can be associated with the same HARQ process or carried by the same (N)PDSCH.

[0065] For NB-IoT, when multiple TBs are scheduled by a single DCI and configured with HARQ-ACK binding, the scheduled TBs may be associated with the same HARQ process or carried by the same NPDSCH. If the associated HARQ process has HARQ-ACK enabled, the ACK / NACK response can be generated by performing a logical AND operation with the HARQ-ACK corresponding to the scheduled TB. If the associated HARQ process has HARQ-ACK disabled, at least one of the following can be considered: HARQ feedback was not generated / transmitted; or ACK is generated / transmitted.

[0066] For eMTC, when multiple TBs are scheduled by a single DCI and configured with HARQ-ACK bundling, the TBs within the same bundle are associated with the same HARQ process or carried by the same PDSCH. The TB bundling process shown in Example 1 of the implementation can be reused. For a TB bundle associated with a HARQ process that enables HARQ feedback, a logical AND operation can be performed on all TBs within the bundle. For a TB bundle associated with a HARQ process that disables HARQ feedback, at least one of the following can be considered: No HARQ feedback was generated / transmitted for TB bundling; or Generate / transmit ACKs for TB bundles.

[0067] More specifically, when 8 TB are scheduled by DCI and the DCI field "Multi-TB HARQ-ACK Bundle Size" is equal to "10", 3 bundles can be generated as follows: , , .

[0068] TB Bundling , and It can be associated with 3 different HARQ processes. (Assuming...) Associated with HARQ processes disabled by HARQ-ACK, and and Associated with the HARQ process enabled by HARQ-ACK.

[0069] UE can be targeted separately and Generate 2 HARQ-ACK bits. (Targeting...) The HARQ-ACK bits can be used to... , and Generate it by performing a logical AND operation on HARQ-ACK. (For...) The HARQ-ACK bits can be used to... and Generate by performing a logical AND operation on HARQ-ACK; or UE can be targeted separately , and Generate 3 HARQ-ACK bits. (Targeting...) The HARQ-ACK bit can be set to ACK. For The HARQ-ACK bits can be used to... , and Generate it by performing a logical AND operation on HARQ-ACK. (For...) The HARQ-ACK bits can be used to... and Generate it by performing a logical AND operation on HARQ-ACK.

[0070] The UE can receive an indication from the network regarding whether a TB in the same bundle can be associated with the same HARQ process or carried by the same (N)PDSCH. This indication may be explicit or implicit. For an explicit indication, the network may send signaling to the UE via at least one of Radio Resource Control (RRC) signaling, Media Access Control Unit (MAC CE) signaling, Downlink Control Information (DCI) signaling, or System Information Block (SIB) broadcasting regarding whether a TB in the same bundle can be associated with the same HARQ process or carried by the same (N)PDSCH. For an implicit indication, the UE can associate a TB in the same bundle with the same HARQ process when at least one HARQ process is configured to disable feedback.

[0071] When a TB (Task Block) in the same bundle is associated with the same HARQ process, it's possible to consider which HARQ process is associated with that bundle. For NB-IoT, if HARQ-ACK bundling can be configured, all TBs are in the same bundle. A UE with HARQ-ACK bundling can have at most two HARQ processes. Therefore, when multiple TBs are scheduled by a single DCI and HARQ-ACK bundling is configured, the HARQ process associated with the scheduled TBs can include at least one of the following: HARQ process 0; or HARQ process 1.

[0072] For eMTC, TB can be divided into multiple bundles. Therefore, when multiple TBs are scheduled by a single DCI and HARQ-ACK bundles are configured, the HARQ processes associated with the TB bundles can be: M HARQ processes, where the HARQ process ID is associated with the TB bundle index with or without an offset; M HARQ processes, where the HARQ process for each bundle is the HARQ process with the lowest HARQ process ID in the bundle; M HARQ processes, where the HARQ process for each bundle is the HARQ process with the highest HARQ process ID in the bundle; M HARQ processes with HARQ process IDs starting from the HARQ process associated with the first TB, where the HARQ process for each bundle is associated with the TB with the lowest TB index in the bundle; M HARQ processes, where the HARQ process for each bundle is associated with the TB with the highest TB index in the bundle; M HARQ processes with HARQ process IDs starting from the HARQ process associated with the first TB; where M can be the number of TB bundles.

[0073] For the HARQ process ID associated with the TB bundled index, at least one of the following examples can be considered: M HARQ processes are sequentially associated with TB bundles, where the HARQ process ID equals the TB bundle index. For example, HARQ process 1 is bundled with TB. Relatedly, HARQ process 2 is bundled with TB. Related, etc.

[0074] Starting with the process with the lowest HARQ process ID (e.g., HARQ process 0), M HARQ processes are sequentially associated with TB bundles based on the TB bundle index. For example, HARQ process 0 is associated with TB bundle. Relatedly, HARQ process 1 is bundled with TB. Related, etc.

[0075] M HARQ processes, starting from the HARQ process with the highest HARQ process ID (e.g., ending with HARQ process 7), are sequentially associated with TB bundles based on the TB bundle index. For example, HARQ process 7 is associated with TB bundle. Relatedly, HARQ process 6 is bundled with TB. Related, etc.

[0076] M HARQ processes are sequentially associated with a TB (Task Block), with an offset between the HARQ process ID and the TB bundle index. For example, suppose the offset is X. Then, HARQ process 1+X is bundled with the TB. Relatedly, HARQ process 2+X is bundled with TB. Related, etc. X can be zero, positive, or negative. If the TB binding index plus the offset exceeds the range of HARQ process ID values, a modulo operation can be performed based on the HARQ process ID.

[0077] For the associations in the above example, only available HARQ processes may be considered. When a HARQ process is already in use, it can be skipped in the association between a HARQ process and a TB. The following HARQ processes are associated with TB in sequence. For example, suppose HARQ processes 1 through M are initially associated with TB. To TB bundle Related. However, HARQ process Y has already been used. Then, HARQ processes 1 to HARQ process Y-1 can be bound to TB. To TB bundle Related, and HARQ processes Y+1 to M+1 can be bound to TB. To TB bundle Related.

[0078] For M HARQ processes, the HARQ process for each bundle is the HARQ process in the bundle with the lowest HARQ process ID. More specifically, the lowest HARQ process ID may refer to the lowest HARQ process ID among the HARQ processes initially associated with the TB in the TB bundle. For example, suppose 8 TBs are scheduled and divided into 3 bundles, as shown below. , , .

[0079] Each TB can be associated with a unique HARQ process. Without loss of generality, assume that HARQ processes 0-7 are initially associated with... to Related. So, regarding TB bundling... HARQ processes can be HARQ process 0 through HARQ process 2. (Bundling) The lowest HARQ process ID is HARQ process 0. Similarly, for TB bundling... Bundled with TB The lowest HARQ process IDs can be HARQ process 3 and HARQ process 6, respectively. For M HARQ processes, where each bundled HARQ process is the HARQ process with the highest HARQ process ID in the bundle, similar to the above.

[0080] It should be understood that one or more features in the above implementation examples are not unique to a particular implementation example, but can be combined in any way (e.g., in any priority and / or order, simultaneously or otherwise).

[0081] Figure 5 A flowchart of a method 500 for disabling Hybrid Automatic Repeat Request (HARQ) feedback via multiple transport block (TB) scheduling is shown. Method 500 can be used in conjunction with this document. Figures 1 to 4 This method is implemented by any one or more of the components and devices described in the detailed description. In summary, in some embodiments, method 500 may be performed by a wireless communication device (e.g., a UE). Depending on the embodiment, additional, fewer, or different operations may be performed in method 500. At least one aspect of these operations relates to a system, method, apparatus, or computer-readable medium.

[0082] A wireless communication device (e.g., a user equipment (UE)) can receive at least one configuration and Hybrid Automatic Repeat Request (HARQ) related information for multiple transport blocks (TBs) from a wireless communication node via at least one signaling. The wireless communication device can generate at least one HARQ feedback (e.g., HARQ-ACK information) for the multiple TBs based on at least one configuration. The at least one configuration may include an indication of whether bundling for at least one HARQ feedback is configured. In some embodiments, multiple configurations may exist (e.g., whether bundling is enabled or feedback is disabled). Multiple configurations can be configured via different signaling. Multiple TBs can be scheduled via a single downlink control information (DCI) or a single physical downlink control channel (PDCCH). The at least one signaling may include at least one of the following: downlink control information (DCI) signaling; higher-layer signaling; media access control element (MAC CE) signaling; or radio resource control (RRC) signaling. Multiple TBs may include at least one TB with HARQ feedback disabled.

[0083] In some embodiments, the at least one configuration may further include at least one of the following: an indication of whether one or more TBs in the same bundle are associated with the same HARQ process; an indication of whether feedback for at least one HARQ process is enabled or disabled; or an indication of whether HARQ feedback is enabled or disabled for at least one TB in the bundle.

[0084] In response to the absence of a bundle configured for at least one HARQ feedback, the wireless communication device can generate at least one HARQ feedback for one or more of a plurality of bundles where HARQ feedback is enabled. For enhanced machine-type communication (eMTC), multiple bundles can be divided. AND operations can be performed on a bundle-by-bundle basis.

[0085] In response to a bundle configured with at least one HARQ feedback, a wireless communication device can generate aggregated HARQ feedback for one or more TBs out of a plurality of TBs via a logical AND operation of a single HARQ feedback. In response to a bundle configured with at least one HARQ feedback and at least one TB out of a plurality of TBs with HARQ feedback enabled, the wireless communication device can generate aggregated HARQ feedback via a logical AND operation of a single HARQ feedback corresponding to at least one TB out of the plurality of TBs. The wireless communication device can generate aggregated HARQ feedback from the logical AND operation by excluding HARQ feedback from one or more TBs out of a plurality of TBs with HARQ feedback disabled. The wireless communication device can perform the logical AND operation by defining the corresponding HARQ feedback for each TB out of a plurality of TBs with HARQ feedback disabled as an acknowledgment (ACK) and including the corresponding HARQ feedback in the logical AND operation.

[0086] In response to the lack of a bundle configured for at least one HARQ feedback, the wireless communication device may generate at least one HARQ feedback for one or more of a plurality of TBs with HARQ feedback enabled.

[0087] In some embodiments, the wireless communication device may generate aggregated HARQ feedback via a logical AND operation of individual HARQ feedbacks corresponding to each of the plurality of TBs. The wireless communication device may also generate aggregated HARQ feedback by bundling one or more of the plurality of TBs via a logical AND operation of individual HARQ feedbacks corresponding to the HARQ feedbacks of one or more of the plurality of TBs with HARQ enabled feedback.

[0088] Having HARQ feedback enabled in at least one of a plurality of TBs can instruct that HARQ feedback be enabled for at least one HARQ process associated with that at least one TB. Conversely, disabling HARQ feedback in at least one of a plurality of TBs can instruct that HARQ feedback be disabled for at least one HARQ process associated with that at least one TB.

[0089] In some embodiments, a wireless communication device may associate at least one of a plurality of TBs in the same bundle with at least one identical HARQ process (e.g., map, associate, correspond, pair). TBs in the same bundle are associated with the same HARQ process. Thus, TBs with feedback enabled and TBs with feedback disabled are not mixed in the same bundle. At least one identical HARQ process associated with at least one of the multiple TBs can include at least one of the following: HARQ process 0; HARQ process 1; M HARQ processes, wherein the HARQ process ID is associated with a TB bundle index with or without an offset; M HARQ processes, wherein at least one identical HARQ process for each bundle is the HARQ process with the lowest HARQ process ID in the bundle; M HARQ processes, wherein at least one identical HARQ process for each bundle is the HARQ process with the highest HARQ process ID in the bundle; M HARQ processes, wherein at least one identical HARQ process for each bundle is a HARQ process associated with at least one TB in the bundle with the lowest TB index; M HARQ processes, wherein at least one identical HARQ process for each bundle is a HARQ process associated with at least one TB in the bundle with the highest TB index; or M HARQ processes with HARQ process IDs starting from at least one identical HARQ process associated with the first TB. M can be the number of bundles. In response to the fact that at least one identical HARQ process associated with at least one TB in the same bundle is HARQ feedback disabled, the wireless communication device may generate an acknowledgment (ACK). In response to the fact that at least one identical HARQ process associated with at least one TB in the same bundle is HARQ feedback disabled, no HARQ-ACK is generated for that at least one TB. In response to the fact that at least one identical HARQ process associated with at least one TB in the same bundle is HARQ feedback enabled, the wireless communication device may generate an aggregated HARQ feedback for at least one TB in the same bundle via a logical AND operation of a single HARQ feedback. The wireless communication device may generate at least one HARQ feedback for bundling according to at least one configuration.

[0090] In some embodiments, a wireless communication node may send at least one configuration and Hybrid Automatic Repeat Request (HARQ) related information for multiple transport blocks (TBs) to a wireless communication device (e.g., a UE) via at least one signaling. The wireless communication device may generate at least one HARQ feedback (e.g., HARQ-ACK information) for the multiple TBs based on at least one configuration. The at least one configuration may include an indication of whether a bundle for at least one HARQ feedback is configured.

[0091] While various embodiments of the solution have been described above, it should be understood that these embodiments are presented by way of example only and not by way of limitation. Similarly, various schematic diagrams may depict exemplary architectures or configurations, which are provided to enable those skilled in the art to understand exemplary features and functionality of the solution. However, those skilled in the art will understand that the solution is not limited to the exemplary architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment herein may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above.

[0092] It should also be understood that any references to elements in this document using names such as "first," "second," etc., generally do not restrict the number or order of these elements. Rather, these names may be used in this document as a convenient means of distinguishing two or more elements, or multiple instances of a single element. Therefore, references to the first and second elements do not imply that only two elements can be used, or that the first element must precede the second element in some way.

[0093] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols that may be mentioned in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0094] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code in conjunction with instructions (which may be referred to herein as "software" or "software module"), or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware, and software, various exemplary components, blocks, modules, circuits, and steps have generally been described above in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these techniques, depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation will not depart from the scope of this disclosure.

[0095] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein can be implemented within or executed by an integrated circuit (IC). An integrated circuit (IC) can include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, a processor may be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of computing devices, such as a DSP and microprocessors, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration performing the functions described herein.

[0096] If these functions are implemented in software, they can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any medium capable of transferring a computer program or code from one location to another. Storage media can be any available medium accessible to a computer. For example, but not limited to, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electronically erasable programmable read-only memory (EEPROM), compact optical disc read-only memory (CD-ROM), or other optical disc storage, disk storage, or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and is accessible to a computer.

[0097] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of such elements for performing the relevant functions described herein. Furthermore, for the purposes of discussion, various modules are described as discrete modules; however, as will be apparent to those skilled in the art, two or more modules can be combined into a single module that performs the relevant functions according to embodiments of this solution.

[0098] Furthermore, memory or other storage devices, as well as communication components, may be used in embodiments of this solution. It should be understood that, for clarity, the above description refers to embodiments of this solution described with reference to different functional units and processors. However, it will be apparent that any suitable functional distribution among different functional units, processing logic elements, or domains can be used without impairing this solution. For example, functions shown to be performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing the described functions and do not indicate a strict logical or physical structure or organization.

[0099] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is given the broadest scope consistent with the novel features and principles disclosed herein as set forth in the following claims.

Claims

1. A method comprising: The wireless communication device receives at least one configuration and Hybrid Automatic Repeat Request (HARQ) related information for multiple transport blocks (TBs) from the wireless communication node via at least one signaling. as well as The wireless communication device generates at least one HARQ feedback for the plurality of TBs according to the at least one configuration; The at least one configuration includes an indication of whether a bundle for the at least one HARQ feedback is configured.

2. The method according to claim 1, wherein, The multiple TBs are scheduled by a single downlink control information (DCI) or a single physical downlink control channel (PDCCH).

3. The method according to claim 1, wherein, The at least one signaling includes at least one of the following: Downlink Control Information (DCI) signaling; High-level signaling; Media Access Control Element (MAC CE) signaling, or Radio Resource Control (RRC) signaling.

4. The method according to claim 1, wherein, The plurality of TBs includes at least one TB with HARQ feedback disabled.

5. The method according to claim 1, wherein, The at least one configuration also includes at least one of the following: An indication of whether one or more TBs in the same bundle are associated with the same HARQ process; Feedback or indication that at least one HARQ process is disabled; or An indication of whether at least one of the plurality of TBs is enabled or disabled for HARQ feedback.

6. The method according to claim 1, comprising: In response to the lack of a bundle configured for the at least one HARQ feedback, the wireless communication device generates the at least one HARQ feedback for one or more of the plurality of TBs with HARQ feedback enabled.

7. The method according to claim 1, comprising: In response to the configuration of bundling for the at least one HARQ feedback, the wireless communication device generates an aggregated HARQ feedback for one or more of the plurality of TBs via a logical AND operation of a single HARQ feedback.

8. The method according to claim 1, comprising: In response to the configuration of bundling for the at least one HARQ feedback and the HARQ feedback being enabled for at least one of the plurality of TBs, the wireless communication device generates aggregated HARQ feedback by performing a logical AND operation on the individual HARQ feedback corresponding to at least one of the plurality of TBs.

9. The method according to claim 7 or 8, comprising: The aggregated HARQ feedback is generated by the wireless communication device by excluding HARQ feedback from one or more of the plurality of TBs that have HARQ feedback disabled from the logical AND operation.

10. The method according to claim 7 or 8, comprising: The logical AND operation is performed by the wireless communication device by defining the corresponding HARQ feedback of each of the plurality of TBs with HARQ feedback disabled as an acknowledgment (ACK) and including the corresponding HARQ feedback in the logical AND operation.

11. The method according to claim 1, comprising: In response to the configuration of a bundle for the at least one HARQ feedback, the wireless communication device generates the at least one HARQ feedback for one or more of the plurality of TBs that have HARQ feedback enabled.

12. The method according to claim 1, comprising: The wireless communication device generates aggregated HARQ feedback by performing a logical AND operation on individual HARQ feedbacks corresponding to each of the plurality of TBs.

13. The method according to claim 1, comprising: The wireless communication device generates aggregated HARQ feedback by performing a logical AND operation on individual HARQ feedback corresponding to the HARQ feedback of one or more of the plurality of TBs with HARQ feedback enabled, for the bundling of one or more TBs of the plurality of TBs.

14. The method according to claim 5, wherein, At least one of the plurality of TBs has HARQ feedback enabled for at least one HARQ process associated with the at least one TB, and HARQ feedback is enabled.

15. The method according to claim 5, wherein, At least one of the plurality of TBs has HARQ feedback instructions disabled for at least one HARQ process associated with the at least one TB, and HARQ feedback is disabled.

16. The method of claim 1, comprising: The wireless communication device associates at least one of the plurality of TBs in the same bundle with at least one identical HARQ process.

17. The method according to claim 16, wherein, At least one identical HARQ process associated with at least one of the plurality of TBs includes at least one of the following: HARQ process 0; HARQ process 1; M HARQ processes, where the HARQ process ID is associated with a TB bundle index with or without an offset; M HARQ processes, wherein at least one identical HARQ process in each bundle is the HARQ process in the bundle with the lowest HARQ process ID; M HARQ processes, wherein at least one identical HARQ process in each bundle is the HARQ process with the highest HARQ process ID in the bundle; M HARQ processes, wherein at least one identical HARQ process for each bundle is a HARQ process associated with at least one TB in the bundle that has the lowest TB index; M HARQ processes, wherein at least one identical HARQ process for each bundle is a HARQ process associated with at least one TB in the bundle that has the highest TB index; or M HARQ processes, each having a HARQ process ID starting from at least one of the same HARQ processes associated with the first TB; Where M is the number of bundles.

18. The method of claim 16, comprising: In response to the at least one identical HARQ process associated with at least one of the plurality of TBs in the same bundle having HARQ feedback disabled, an acknowledgment (ACK) is generated by the wireless communication device.

19. The method of claim 16, comprising: In response to the at least one identical HARQ process associated with at least one of the plurality of TBs in the same bundle having HARQ feedback disabled, no HARQ-ACK is generated for the at least one TB.

20. The method of claim 16, comprising: In response to the activation of HARQ feedback for at least one of the at least one TBs in the same bundle, HARQ feedback is generated by the wireless communication device via a logical AND operation of a single HARQ feedback for at least one TB in the same bundle.

21. The method of claim 16, comprising: The wireless communication device generates the at least one HARQ feedback for bundling according to the at least one configuration.

22. A method comprising: A wireless communication node sends at least one configuration and Hybrid Automatic Repeat Request (HARQ) related information for a plurality of transport blocks (TBs) to a wireless communication device via at least one signaling, wherein the wireless communication device generates at least one HARQ feedback for the plurality of TBs according to the at least one configuration, and wherein the at least one configuration includes an indication of whether a bundling for the at least one HARQ feedback is configured.

23. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 22.

24. An apparatus comprising: At least one processor is configured to perform the method according to any one of claims 1 to 22.

Images