METHOD AND APPARATUS FOR IMPROVING HYBRID AUTOMATIC REPETITION REQUEST FOR SCHEDULING MULTIPLE TRANSPORT BLOCKS IN AN INTERNET OF THINGS SYSTEM

Description

1 / 26 METHOD AND APPARATUS FOR IMPROVING HYBRID AUTOMATIC REPETITION REQUEST FOR SCANNING MULTIPLE TRANSPORT BLOCKS IN AN INTERNET OF THINGS SYSTEM CROSS-REFERENCED TO RELATED PATENT APPLICATION(S)

[0001] This disclosure is part of a non-provisional application claiming the priority benefit of PCT Application No. PCT / CN2023 / 100152, filed on 14 June 2023, the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] This disclosure relates generally to mobile communications and, more particularly, to Hybrid Automatic Repeat Request (HARQ) enhancements for multi-transport block (multi-TB) scaling in an Internet of Things (IoT) system. BACKGROUND

[0003] Unless otherwise indicated in this document, the approaches described in this section are not prior techniques to the claims listed below and are not admitted as prior techniques by their inclusion in this section.

[0004] For current network implementations, a base station (BS) is operable to provide radio coverage to a specific geographic area using a plurality of cells forming a radio access network. The BS can support the operations of the cell plurality, and each cell can be operable to provide services to at least one user equipment (UE) within its radio coverage. Specifically, each cell can provide services to serve one or more UEs within its radio coverage based on at least one downlink control information (DCI), where the radio coverage of one cell can overlap with the radio coverage of another cell(s). In an Internet of Things (IoT) system, a cell can scale multiple link resources. Petition 870250101184, dated 05 / 11 / 2025, page 9 / 39 2 / 26 Uplink / Downlink (UL / DL) (e.g., TBs) to an UE within its radio coverage by a DCI to perform UL / DL transmissions, e.g., HARQ feedback transmissions from UL. HARQ is a mechanism to improve transmission reliability and robustness. With the HARQ mechanism, the UE needs to report HARQ feedback information to a corresponding DL transmission to the scheduling cell, so that the scheduling cell knows whether the DL transmission was successful and decides whether the next DL transmission will be a new transmission or a retransmission.

[0005] In the 3GPP (3G Partnership Project) Version 17, the concept of enabled / disabled HARQ feedback information is introduced, where disabled HARQ feedback information is designed to improve throughput in scenarios with high transmission delay, such as non-terrestrial networks (NTNs). However, when applying the enabled / disabled HARQ feedback information concept to IoT systems, the detailed HARQ operations have not yet been fully discussed, and some issues need to be resolved. For example, one issue relates to how or when to transmit HARQ feedback. Another issue relates to how to design the non-narrowband physical downlink control channel (NPDCCH) monitoring constraint in HARQ operations for multi-TB scaling.

[0006] Therefore, it is necessary to provide adequate schemes to address these issues. SUMMARY

[0007] The following summary is for illustrative purposes only and is not intended to be exhaustive in any way. That is, the following summary is provided to introduce concepts, highlights, benefits, and advantages of the new and non-obvious techniques described in this document. Selected implementations are described in more detail. Petition 870250101184, dated 05 / 11 / 2025, page 10 / 39 3 / 26 detailed below in the detailed description. Therefore, the following summary is not intended to identify essential characteristics of the claimed subject matter, nor is it intended to be used to determine the scope of the claimed subject matter.

[0008] One objective of this disclosure is to propose solutions or schemes that address the problems mentioned above relating to HARQ operations in the application of enabled / disabled HARQ feedback information for multi-TB scaling in IoT systems.

[0009] In one aspect, a method may involve an apparatus receiving a configuration from a network node of a wireless network, wherein the configuration indicates HARQ feedback information disabled or enabled for each or all of a plurality of HARQ processes. The method may involve the apparatus receiving a DCI from the network node, wherein the DCI indicates a scheduling of multiple TBs associated with the HARQ processes in an NPDSCH. The method may also involve the apparatus performing an NPDSCH reception for the TBs based on the DCI. The method may further involve the apparatus determining whether to report one or more HARQ feedbacks corresponding to the TBs based on the configuration.

[0010] In one aspect, an apparatus may comprise a transceiver that, during operation, communicates wirelessly with a network node of a wireless network. The apparatus may also comprise a processor communicatively coupled to the transceiver. The processor, during operation, may perform operations comprising receiving, via the transceiver, a configuration from the network node, wherein the configuration indicates HARQ feedback information disabled or enabled for each or all of a plurality of HARQ processes. The processor may perform operations comprising receiving, via the transceiver, a DCI from the network node, wherein the DCI indicates a multi-TB scheduling associated with the HARQ processes. Petition 870250101184, dated 05 / 11 / 2025, page 11 / 39 4 / 26 in an NPDSCH. The processor can also perform operations that include receiving NPDSCH data for the TBs via the transceiver based on the DCI. The processor can also perform operations that include determining whether to report one or more corresponding HARQ feedbacks to the TBs based on the configuration.

[0011] It is important to emphasize that, although the description provided in this document may be in the context of certain radio access technologies, networks, and network topologies, such as Long Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, 5th Generation (5G), New Radio (NR), Internet of Things (IoT) and Narrowband Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), in addition to 5G (B5G) and 6th Generation (6G), the concepts, schemes, and any proposed variations / derivatives may be implemented in, for, and by other types of radio access technologies, networks, and network topologies. Thus, the scope of this disclosure is not limited to the examples described in this document. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings are included to provide a better understanding of the disclosure and are incorporated into and constitute a part of this disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is important to note that the drawings are not necessarily to scale, as some components may appear disproportionate to size in the actual implementation, in order to clearly illustrate the concept of this disclosure.

[0013] FIG. 1 is a diagram that describes an example scenario of a communication environment in which various solutions and schemes according to the present disclosure can be implemented.

[0014] FIG. 2 is a diagram that describes an example scenario of HARQ operations with HARQ feedback information. Petition 870250101184, dated 05 / 11 / 2025, p. 12 / 39 5 / 26 enabled / disabled according to an implementation of this disclosure.

[0015] FIG. 3 is a diagram that describes an example scenario of configuration indication for HARQ feedback information enabled / disabled for multiple TBs according to an implementation of the present disclosure.

[0016] FIG. 4 is a block diagram of an example communication system according to an implementation of the present disclosure.

[0017] FIG. 5 is a flowchart of an example process according to an implementation of the present disclosure. DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS

[0018] Detailed embodiments and implementations of the claimed subjects are disclosed in this document. However, it should be understood that the embodiments and implementations disclosed are merely illustrative of the claimed subjects, which may be embodied in various forms. This disclosure may, however, be embodied in many different forms and should not be interpreted as limited to the exemplary embodiments and implementations set forth in this document. Instead, these exemplary embodiments and implementations are provided so that the description of this disclosure is thorough and complete and fully conveys the scope of this disclosure to those skilled in the art. In the description below, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the embodiments and implementations presented. Overview

[0019] Implementations according to this disclosure refer to various techniques, methods, schemes, and / or solutions pertaining to HARQ enhancements for scaling multiple TB in an IoT system. According to this disclosure, several possible solutions can be implemented. Petition 870250101184, dated 05 / 11 / 2025, page 13 / 39 6 / 26 separately or together. That is, although these possible solutions can be described separately below, two or more of these possible solutions can be implemented in one combination or another.

[0020] The HARQ mechanism is primarily used for scheduling management, such as initial transmission and retransmission of information. In scenarios with relatively small transmission delay, such as the TN system, using HARQ feedback for DL ​​transmissions has many advantages, such as increasing transmission reliability. On the other hand, in scenarios with large transmission delay, such as the NTN system, disabling HARQ feedback for DL ​​transmissions can reduce UE power consumption and improve UL throughput. Consequently, considering IoT scenarios (e.g., IoT NTN), this disclosure proposes HARQ enhancement schemes for multi-TB scheduling in an IoT system to mitigate HARQ stalling and reduce UE power consumption.

[0021] FIG. 1 illustrates an example scenario 100 of a communication environment in which various solutions and schemes according to this disclosure can be implemented. Scenario 100 involves a UE 110 in wireless communication with a network 120 (e.g., a wireless network including an NTN and a TN) via a terrestrial network node 125 (e.g., an evolved-Node-B (eNB), a next-generation-Node-B (gNB), or a transmit / receive point (TRP)) and / or a non-terrestrial network node 128 (e.g., a satellite). For example, terrestrial network node 125 and / or non-terrestrial network node 128 can form an NTN service cell for wireless communication with UE 110. In some implementations, network 120 may be an IoT network (e.g., an NTN IoT network) and UE 110 may be an IoT device, such as an NB-IoT UE or an eMTC UE (e.g., a low-complexity reduced-bandwidth (BL) UE or a UE of Petition 870250101184, dated 05 / 11 / 2025, p. 14 / 39 7 / 26 coverage enhancement (CE)). In such a communication environment, UE 110, network 120, and terrestrial network node 125 and / or non-terrestrial network node 128 may implement various schemes pertaining to HARQ enhancements for multi-TB scaling in an IoT system according to this disclosure, as described below. It is worth noting that while the various proposed schemes may be described individually or separately below, in actual implementations, some or all of the proposed schemes may be used or implemented together. Of course, each of the proposed schemes may be used or implemented individually or separately.

[0022] In this disclosure, NTN refers to a network that uses radio frequency (RF) resources and information processing carried on high, medium, and low orbit satellites or other high-altitude communication platforms to provide communication services to UEs. Depending on the satellite's payload capacity, there are two typical scenarios, namely: transparent payload and regenerative payload. In transparent payload mode, the satellite does not process the signal and waveform in the communication service, but only acts as an RF amplifier to forward data. In regenerative payload mode, the satellite, in addition to RF amplification, also has modulation / demodulation, encoding / decoding, switching, routing, and other processing capabilities.

[0023] In general, an IoT system is primarily divided into NB-IoT and eMTC based on differences in system bandwidth and coverage. Typically, the bandwidth used in NB-IoT is around 200 kilohertz (kHz) and supports low-traffic data transmission at a rate below 100 kilobits per second (kbps). On the other hand, eMTC technology typically uses a bandwidth of 1.4 megahertz (MHz) and Petition 870250101184, dated 05 / 11 / 2025, p. 15 / 39 8 / 26 The maximum data transmission rate is 1 megabit per second (Mbps). For eMTC, different TBs corresponding to different HARQ process numbers can be scaled by a DCI. For NB-IoT, multiple TBs (i.e., two TBs) can be scaled together by a DCI without a HARQ process number field in the DCI, where the HARQ process ID of 0 should be assumed for the first TB and the HARQ process ID of 1 should be assumed for the second TB.

[0024] In certain schemes proposed in accordance with this disclosure, a configuration indicating disabled or enabled HARQ feedback information for each or all HARQ processes in a plurality may be provided to the UE via radio resource control (RRC) signaling and / or a DCI field, before receiving a DCI indicating a multi-TB scheduling associated with the plurality of HARQ processes on the narrowband physical downlink shared channel (NPDSCH). For RRC-based indication, a bitmap may be used to indicate disabled / enabled HARQ feedback information for each HARQ process. For example, the RRC bitmap may include 2 bits (for NB-IoT cases) or 14 bits (for eMTC cases), each indicating disabled / enabled HARQ feedback information for a HARQ process (e.g., value 1 indicates disabled and value 0 indicates enabled).For DCI-based indication, a single bit can be used to indicate disabled / enabled HARQ feedback information for all HARQ processes (e.g., a value of 1 indicates disabled and a value of 0 indicates enabled). After performing an NPDSCH reception for the DCI-based scaled TBs, the UE can determine whether to report one or more HARQ feedbacks (e.g., HARQ acknowledgment (ACK) or non-acknowledgment (NACK)) corresponding to the TBs based on the configuration. More specifically, the UE can determine whether to report one or more HARQ feedbacks. Petition 870250101184, dated 05 / 11 / 2025, page 16 / 39 9 / 26 corresponding to the TBs associated with HARQ processes with HARQ feedback information enabled, as indicated by the configuration, and determine not to report any HARQ feedback corresponding to the TBs associated with HARQ processes with HARQ feedback information disabled, as indicated by the configuration.

[0025] In some implementations, if HARQ-ACK bundling is configured (for example, if the UE is configured with a top-layer parameter harq-AckBundling in npdschMultiTB-Config), the UE can report a single HARQ feedback that is generated by performing an AND logical operation on the HARQ feedbacks corresponding to the TBs associated with HARQ processes with HARQ feedback information enabled, or by performing an AND logical operation on the HARQ feedbacks corresponding to the TBs and assuming 1 in the AND logical operation for the TBs associated with HARQ processes with HARQ feedback information disabled.

[0026] In some implementations, if HARQ-ACK grouping is not configured, the UE may report one or multiple HARQ feedbacks, each corresponding to one of the TBs associated with the HARQ processes with HARQ feedback information enabled.

[0027] In some implementations, the TBs associated with HARQ processes with HARQ feedback information enabled can be configured in multiple TB packets Ab, where b = 1, ..., Mhabiutada. The reported HARQ feedbacks may include multiple HARQ feedbacks (e.g., Mhabiutadabits HARQACK, where Mhabiutada is the number of TB packets that have TBs configured with HARQ feedback information enabled) generated by performing a logical AND operation on all TBs in each of the TB packets.

[0028] In some implementations, TBs may be Petition 870250101184, dated 05 / 11 / 2025, page 17 / 39 10 / 26 configured in multiple TB packets Ab, where b = 1, ..., M. The reported HARQ feedback(s) may include multiple HARQ feedbacks (e.g., M bits HARQ-ACK, where M is the number of TB packets provided by the 3GPP Technical Specification (TS) 36.213, Table 7.3-1) generated by performing a logical AND operation on HARQ feedbacks on all TBs and assuming 1 in the logical AND operation for the TBs associated with the HARQ processes with HARQ feedback information disabled in each of the TB packets.

[0029] In some implementations, for no NPDCCH / PDCCH monitoring restriction, the UE may determine not to perform DCI monitoring on the NPDCCH or PDCCH in a first time period subsequent to the reporting of one or more HARQ feedbacks, in an event where at least one of the TBs is associated with HARQ processes with HARQ feedback information enabled. For example, the first time period T1 may include the UE-to-eNB / gNB round-trip time (RTT), for example, T1 = UE_eNB_RTT + 3 milliseconds (ms). Alternatively, the first time period T1 may include the Kmac offset to delay an application of a DL configuration indicated by a Medium Access Control (MAC) control element (CE) command on the PDSCH, for example, T1 = ^mac + 3 ms.

[0030] In some implementations, for no NPDCCH / PDCCH monitoring restriction, the UE may determine not to perform DCI monitoring in a second time period subsequent to receiving NPDSCH, if all TBs are associated with HARQ processes with HARQ feedback information disabled. For example, the second time period T2 may include a half-duplex guard period (e.g., T2 = Type B half-duplex guard period (1 ms)).

[0031] FIG. 2 illustrates an example scenario 200 of HARQ operations with HARQ feedback information. Petition 870250101184, dated 05 / 11 / 2025, page 18 / 39 11 / 26 enabled / disabled according to an implementation of this disclosure. Scenario 200 involves a UE (e.g., an NB-IoT UE or an eMTC UE) and a network node (e.g., an eNB / gNB / TRP) implementing proposed schemes relating to HARQ enhancements for multi-TB scaling in an IoT system according to this disclosure. Part (A) of FIG. 2 illustrates, from left to right, HARQ operations with HARQ feedback information enabled and HARQ operations with HARQ feedback information disabled. During HARQ operations with HARQ feedback information enabled, the UE receives a DCI (e.g., DCI N0 format) indicating a multi-TB scheduling on the NPDSCH and transmits HARQ DL feedbacks for the scheduled TBs to the network node (e.g., an eNB / gNB / TRP).Based on HARQ DL feedback, the network node can transmit a DCI to indicate the next transmission (e.g., a new transmission or a retransmission). For example, DCI format N0 is used for NPDSCH scheduling, DCI format N1 is used for narrowband physical uplink shared channel scheduling (NPUSCH), a DCI format 6-1a / b is used for NPDSCH scheduling for eMTC, and DCI format 6-0a / b is used for NPUSCH scheduling for eMTC, etc. During HARQ operations with HARQ feedback information disabled, the UE receives a DCI (e.g., DCI format N0) indicating a multi-TB scheduling in NPDSCH and does not transmit any HARQ DLs for the scheduled TBs to the network node, so the network node can initiate the next transmission without waiting for HARQ DL feedback. Part (B) of FIG.Figure 2 illustrates HARQ operations with HARQ feedback information enabled in the upper diagram and HARQ operations with HARQ feedback information disabled in the lower diagram. As shown in Part (B) of FIG. 2, the non-restriction of NPDCCH monitoring in the case of information. Petition 870250101184, dated 05 / 11 / 2025, page 19 / 39 12 / 26 HARQ feedback disabled is more relaxed than the non-restricted NPDCCH monitoring in the case of HARQ feedback information enabled, considering that the UE may need more time to prepare for the switching between the NPUSCH transmission carrying HARQ DL feedback and the next DCI reception when HARQ feedback information is enabled.

[0032] FIG. 3 illustrates an example scenario 300 of configuration indication for HARQ enabled / disabled feedback information for multiple TBs according to an implementation of this disclosure. Scenario 300 represents UE operations with RRC-based indication and / or DCI-based indication for provided HARQ enabled / disabled feedback information. To begin, in 301, the UE determines whether an RRC bitmap (e.g., 2 bits for NB-IoT or 14 bits for eMTC) for HARQ enabled / disabled feedback information is configured. After 301, if the RRC bitmap is not configured, the UE operations proceed to 302, where the UE determines whether a DCI field (e.g., 1 bit) for HARQ enabled / disabled feedback information is configured.Following step 302, if the DCI field is configured, UE operations proceed to step 303, where UE determines whether HARQ feedback information is enabled for all TBs (e.g., DCI field = 0 or enabled) or disabled for all TBs (e.g., DCI field = 1 or disabled). After step 302, if the DCI field is not configured, UE operations proceed to step 304, where UE follows the legacy design, determining whether HARQ feedback information is enabled for all TBs.

[0033] After 301, if the RRC bitmap is configured, the UE operations proceed to 305, where the UE determines whether a DCI field (e.g., 1 bit) for HARQ enabled / disabled feedback information is configured. Subsequently Petition 870250101184, dated 05 / 11 / 2025, page 20 / 39 From 13 / 26 to 305, if the DCI field is configured, UE operations proceed to 306, where UE determines whether HARQ feedback information is enabled for all TBs (e.g., DCI field = 0 or enabled) or HARQ feedback information is disabled for all TBs (e.g., DCI field = 1 or disabled). After 305, if the DCI field is not configured, UE operations proceed to 307, where UE determines whether the configured RRC bitmap indicates HARQ feedback information enabled / disabled for all TBs, or indicates HARQ feedback information enabled for some TBs and HARQ feedback information disabled for some other TBs. After step 307, if the configured RRC bitmap indicates HARQ feedback information enabled for all TBs, the UE operations proceed to step 308, where the UE determines HARQ feedback information enabled for all TBs.After 307, if the configured RRC bitmap indicates HARQ feedback information is disabled for all TBs, the UE operations proceed to 309, where the UE determines HARQ feedback information is disabled for all TBs.

[0034] After 307, if the configured RRC bitmap indicates HARQ feedback information enabled for some TBs and HARQ feedback information disabled for other TBs (i.e., mixed TB case), the UE operations proceed to 310, where the UE determines if HARQ-ACK grouping is configured. Subsequently to 310, if HARQ-ACK grouping is configured, the UE operations proceed to 311, where the UE determines to report ACK for the TBs with HARQ feedback information disabled, i.e., the UE performs an AND operation on the HARQ feedbacks for all TBs and assumes 1 in the AND operation for the TBs with HARQ feedback information disabled. In this way, no change will occur in the HARQ feedback schedule. After 310, if HARQ-ACK grouping is not configured, the operations Petition 870250101184, dated 05 / 11 / 2025, page 21 / 39 EU Regulation 14 / 26 continues to section 312, where the EU determines not to report HARQ feedback for TBs with HARQ feedback information disabled, i.e., to report only HARQ feedback for TBs with HARQ feedback information enabled. Consequently, HARQ timing for TBs with HARQ feedback information enabled does not include / account for the legacy HARQ-ACK feature / HARQ timing adopted for TBs with HARQ feedback information disabled. Illustrative Implementations

[0035] FIG. 4 illustrates an example 400 communication system having an example 410 communication device and an example 420 network device according to an implementation of the present disclosure. Each of the 410 communication and 420 network devices can perform various functions to implement schemes, techniques, processes, and methods described in this document regarding HARQ enhancements for multi-TB scaling in an IoT system, including scenarios / schemes described above as well as the 500 process described below.

[0036] The 410 communication device can be part of an electronic device, which can be an EU, such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the 410 communication device can be implemented in a smartphone, a smartwatch, a personal digital assistant, an electronic control unit (ECU) in a vehicle, a digital camera, or a computing device such as a tablet, laptop, or notebook. The 410 communication device can also be part of a machine-type device, which can be an IoT, NB-IoT, eMTC, IIoT EU, such as a stationary or fixed device, a household appliance, a roadside unit (RSU), a wired communication device, or a computing device. For example, the device of Petition 870250101184, dated 05 / 11 / 2025, page 22 / 39 15 / 26 410 communication can be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. Alternatively, the 410 communication device can be implemented in the form of one or more integrated circuit (IC) chips, such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more reduced instruction set computing (RISC) processors, or one or more complex instruction set computing (CISC) processors. The 410 communication device may include at least some of the components shown in FIG. 4, such as a 412 processor, for example.The communication apparatus 410 may also include one or more other components not relevant to the proposed scheme of this disclosure (for example, internal power supply, display device and / or user interface device) and, therefore, such components of the communication apparatus 410 are not shown in FIG. 4 nor described below in the interest of simplicity and brevity.

[0037] The 420 network device may be part of an electronic device, which may be a network node, such as a satellite, a BS, a small cell, a router, or an IoT network gateway. For example, the 420 network device may be implemented in a satellite or an eNB / gNB / TRP in a 4G / 5G, NR, IoT, NBioT, or IIoT network. Alternatively, the 420 network device may be implemented in the form of one or more IC chips, such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. The 420 network device may include at least some of the components shown in FIG. 4, such as a 422 processor, for example. The 420 network device may also include one or more other components not relevant to the proposed scheme of this disclosure (for example, a power supply of Petition 870250101184, dated 05 / 11 / 2025, page 23 / 39 16 / 26 internal power supply, display device and / or user interface device) and therefore such components of the network appliance 420 are not shown in FIG. 4 nor described below in the interest of simplicity and brevity.

[0038] In one aspect, each of the 412 processor and 422 processor can be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, although a singular term “a processor” is used in this document to refer to the 412 processor and the 422 processor, each of the 412 processor and 422 processor may include multiple processors in some implementations and a single processor in other implementations according to the present disclosure.In another aspect, each of the 412 and 422 processors may be implemented in hardware (and optionally firmware) form with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more varactors that are configured and arranged to achieve specific purposes in accordance with this disclosure. In other words, in at least some implementations, each of the 412 and 422 processors is a special-purpose machine specifically designed, organized, and configured to perform specific tasks, including HARQ enhancements for multi-TB scaling, in a device (for example, as represented by the 410 communication apparatus) and a network node (for example, as represented by the 420 network apparatus) in accordance with various implementations of this disclosure.

[0039] In some implementations, the communication device 410 may also include a transceiver 416 coupled to the processor 412 and capable of transmitting and receiving data wirelessly. Petition 870250101184, dated 05 / 11 / 2025, page 24 / 39 17 / 26 In some implementations, the 416 transceiver may be able to communicate wirelessly with different types of UEs and / or wireless networks of different radio access technologies (RATs), such as 4G / 5G / B5G / 6G. In some implementations, the 416 transceiver may be equipped with a plurality of antenna ports (not shown), such as four antenna ports. That is, the 416 transceiver may be equipped with multiple transmit antennas and multiple receive antennas for multi-input multiple-output (MIMO) wireless communications. In some implementations, the 420 network appliance may also include a 426 transceiver coupled to the 422 processor. The 426 transceiver may include a transceiver capable of transmitting and receiving data wirelessly. In some implementations, the 426 transceiver may be able to communicate wirelessly with different types of UEs from different RATs.In some implementations, the 426 transceiver can be equipped with a plurality of antenna ports (not shown), such as four antenna ports. That is, the 426 transceiver can be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communications.

[0040] In some implementations, the communication device 410 may also include a memory 414 coupled to processor 412 and capable of being accessed by processor 412 and storing data therein. In some implementations, the network device 420 may also include a memory 424 coupled to processor 422 and capable of being accessed by processor 422 and storing data therein. Each of the memories 414 and 424 may include a type of random access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM) and / or zero-capacitor RAM (Z-RAM). Alternatively, or additionally, each of the memories 414 and 424 may include a type of read-only memory (ROM), such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM) and / or programmable ROM. Petition 870250101184, dated 05 / 11 / 2025, p. 25 / 39 18 / 26 electrically erasable (EEPROM). Alternatively, or additionally, each of the 414 and 424 memories may include a type of non-volatile random access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0041] Each of the 410 communication devices and 420 network devices can be a communication entity capable of communicating with each other using various schemes proposed in accordance with this disclosure. For illustrative purposes and without limitation, a description of the capabilities of the 410 communication device, as an IoT UE (e.g., an NB-IoT UE or an eMTC UE) and of the 420 network device, as a network node (e.g., satellite or BS), is provided below.

[0042] According to some schematics of the present disclosure, processor 412 can receive, via transceiver 416, a configuration from network appliance 420, wherein the configuration indicates HARQ feedback information disabled or enabled for each or all of a plurality of HARQ processes. Furthermore, processor 412 can receive, via transceiver 416, a DCI from network appliance 420, wherein the DCI indicates a scheduling of multiple TBs associated with the HARQ processes in an NPDSCH. Then, processor 412 can perform, via transceiver 416, an NPDSCH reception for the TBs based on the DCI. After that, processor 412 can determine whether to report one or more HARQ feedbacks corresponding to the TBs based on the configuration.

[0043] In some implementations, the determination to report one or more HARQ feedbacks corresponding to the TBs based on the configuration may include: determining to report one or more HARQ feedbacks corresponding to the TBs associated with the HARQ processes with HARQ feedback information enabled, as indicated by the configuration; and determining not to report. Petition 870250101184, dated 05 / 11 / 2025, page 26 / 39 19 / 26 no HARQ feedback corresponding to the TBs associated with the HARQ processes with HARQ feedback information disabled, as indicated by the configuration.

[0044] In some implementations, in an event where a parameter indicating HARQ-ACK grouping is configured, one or more HARQ feedbacks may include a single HARQ feedback generated by performing a multiple HARQ feedback AND operation corresponding to the TBs associated with HARQ processes with HARQ feedback information enabled, or by performing a multiple HARQ feedback AND operation corresponding to the TBs and assuming 1 in the AND operation for the TBs associated with HARQ processes with HARQ feedback information disabled.

[0045] In some implementations, if a parameter indicating HARQ-ACK grouping is not configured, one or more HARQ feedbacks may include one or more HARQ feedbacks, each corresponding to a respective TB associated with the HARQ processes with HARQ feedback information enabled.

[0046] In some implementations, the TBs associated with HARQ processes with HARQ feedback information enabled can be configured in multiple TB packages, and one or more HARQ feedbacks can include multiple HARQ feedbacks generated by performing a logical AND operation on all TBs in each of the TB packages.

[0047] In some implementations, TBs can be configured in multiple TB packages, and one or more HARQ feedbacks can include one or multiple HARQ feedbacks generated by performing a logical AND operation on HARQ feedbacks across all TBs and assuming 1 in the logical AND operation for TBs associated with HARQ processes with HARQ feedback information disabled in each of the TB packages. Petition 870250101184, dated 05 / 11 / 2025, page 27 / 39 20 / 26

[0048] In some implementations, processor 412 may also choose not to perform DCI monitoring in the first time period following the reporting of one or more HARQ feedbacks, in an event where at least one of the TBs is associated with HARQ processes with HARQ feedback information enabled.

[0049] In some implementations, the first time period may include an RTT (e.g., UE_eNB_RTT) between communication device 410 and network device 420, or an offset (e.g., Kmac) to delay the application of a DL configuration indicated by a CE MAC command on a PDSCH.

[0050] In some implementations, processor 412 may also choose not to perform DCI monitoring in a second time period subsequent to receiving NPDSCH, if all TBs are associated with HARQ processes with HARQ feedback information disabled.

[0051] In some implementations, the second time period may include a half-duplex guard period (e.g., Type B half-duplex guard period (1 ms)). Illustrative Processes

[0052] FIG. 5 illustrates an example process 500 according to an implementation of the present disclosure. Process 500 may be an example of implementing the above scenarios / schemes, partially or completely, with respect to HARQ enhancements for multi-TB scaling in an IoT system. Process 500 may represent an aspect of implementing communication device features 410. Process 500 may include one or more operations, actions, or functions, as illustrated by one or more of blocks 510 to 540. Although illustrated as discrete blocks, multiple process 500 blocks may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Furthermore, process 500 blocks may be executed in the order shown in Petition 870250101184, dated 05 / 11 / 2025, pp. 28 / 39 21 / 26 FIG. 5 or, alternatively, in a different order. Process 500 can be implemented by communication device 410 or any suitable UE or machine-type devices. For illustrative purposes only and without limitation, process 500 is described below in the context of communication device 410. Process 500 can start in block 510.

[0053] In 510, process 500 may involve processor 412 of communication device 410 receiving, via transceiver 416, a configuration from a network node (e.g., network device 420) of a wireless network (e.g., an IoT network (NTN)), wherein the configuration indicates HARQ feedback information disabled or enabled for each or all of a plurality of HARQ processes. Process 500 may proceed from 510 to 520.

[0054] In 520, process 500 may involve processor 412 receiving, via transceiver 416, a DCI from the network node, where the DCI indicates a multi-TB scheduling associated with HARQ processes in an NPDSCH. Process 500 may proceed from 520 to 530.

[0055] In 530, process 500 may involve processor 412 performing, via transceiver 416, an NPDSCH reception for the TBs based on DCI. Process 500 may proceed from 530 to 540.

[0056] In 540, process 500 may involve processor 412 determining whether to report one or more HARQ feedbacks corresponding to the TBs based on the configuration.

[0057] In some implementations, the determination to report one or more HARQ feedbacks corresponding to the TBs based on the configuration may include: determining to report one or more HARQ feedbacks corresponding to the TBs associated with the HARQ processes with HARQ feedback information enabled, as indicated by the configuration; and determining not to report any HARQ feedbacks corresponding to the TBs associated with the Petition 870250101184, dated 05 / 11 / 2025, pp. 29 / 39 22 / 26 HARQ processes with HARQ feedback information disabled, as indicated by the configuration.

[0058] In some implementations, in an event where a parameter indicating HARQ-ACK grouping is configured, one or more HARQ feedbacks may include a single HARQ feedback generated by performing a multiple HARQ feedback AND operation corresponding to the TBs associated with HARQ processes with HARQ feedback information enabled, or by performing a multiple HARQ feedback AND operation corresponding to the TBs and assuming 1 in the AND operation for the TBs associated with HARQ processes with HARQ feedback information disabled.

[0059] In some implementations, if a parameter indicating HARQ-ACK grouping is not configured, one or more HARQ feedbacks may include one or more HARQ feedbacks, each corresponding to a respective TB associated with the HARQ processes with HARQ feedback information enabled.

[0060] In some implementations, the TBs associated with HARQ processes with HARQ feedback information enabled can be configured in multiple TB packages, and one or more HARQ feedbacks can include multiple HARQ feedbacks generated by performing a logical AND operation on all TBs in each of the TB packages.

[0061] In some implementations, TBs can be configured in multiple TB packages, and one or more HARQ feedbacks can include one or multiple HARQ feedbacks generated by performing a logical AND operation on HARQ feedbacks across all TBs and assuming 1 in the logical AND operation for TBs associated with HARQ processes with HARQ feedback information disabled in each of the TB packages.

[0062] In some implementations, process 500 may Petition 870250101184, dated 05 / 11 / 2025, pages 30 / 39 23 / 26 also involves processor 412 determining not to perform DCI monitoring in the first time period subsequent to the reporting of one or more HARQ feedbacks, in an event where at least one of the TBs is associated with HARQ processes with HARQ feedback information enabled.

[0063] In some implementations, the first time period may include an RTT (e.g., UE_eNB_RTT) between the communication device 410 and the network device 420, or an offset (e.g., Kmac) to delay the application of a DL configuration indicated by a CE MAC command on a PDSCH.

[0064] In some implementations, process 500 may involve processor 412 determining not to perform DCI monitoring in a second time period subsequent to receiving NPDSCH, if all TBs are associated with HARQ processes with HARQ feedback information disabled.

[0065] In some implementations, the second time period may include a half-duplex guard period (e.g., Type B half-duplex guard period (1 ms)). Additional Notes

[0066] The subject described in this document sometimes illustrates different components contained within or connected to other different components. It should be understood that such represented architectures are merely examples, and that, in fact, many other architectures can be implemented to achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively associated so that the desired functionality is achieved. Therefore, any two components combined in this document to obtain a specific functionality can be seen as associated with each other, so that the desired functionality is achieved, regardless of architectures or intermediate components. Similarly, Petition 870250101184, dated 05 / 11 / 2025, pages 31 / 39 24 / 26 Any two components thus associated can also be seen as being operationally connected or operationally coupled to each other to achieve the desired functionality, and any two components capable of being associated can also be seen as being operationally coupleable to each other to achieve the desired functionality. Specific examples of operationally coupleable components include, but are not limited to, physically coupleable components and / or components that physically interact and / or components that can interact wirelessly and / or components that interact wirelessly and / or components that interact logically and / or components that can interact logically.

[0067] Additionally, with regard to the use of substantially any plural and / or singular term in this document, those skilled in the art may translate from plural to singular and / or from singular to plural, as appropriate to the context and / or application. The various singular / plural permutations may be expressly presented in this document for the sake of clarity.

[0068] Furthermore, it will be understood by those skilled in the art that, in general, the terms used in this document, and especially in the appended claims, for example, bodies of the appended claims, are generally conceived as open terms, for example, the term including should be interpreted as including, but not limited to, the term possessing should be interpreted as possessing at least, the term includes should be interpreted as includes, but not limited to, etc. It will further be understood by those within the art that, if a specific number of an introduced claim citation is intended, such intention will be explicitly cited in the claim and, in the absence of such citation, such intention will not be present. For example, as an aid to understanding, the following appended claims Petition 870250101184, dated 05 / 11 / 2025, pp. 32 / 39 Paragraphs 25 / 26 may contain the use of the introductory phrases "at least one" and "one or more" to introduce claims. However, the use of such phrases should not be interpreted as implying that the introduction of a claim by the indefinite articles "a" or "an" limits any specific claim containing such introduced claim to implementations containing only one of these statements, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an," for example, "a" and / or "an" should be interpreted as "at least one" or "one or more"; the same applies to the use of definite articles used to introduce claims.Furthermore, even if a specific number of an introduced claim statement is explicitly stated, those skilled in the art will recognize that such a statement should be interpreted as meaning at least the stated number, for example, the simple statement of two claims, without other modifiers, means at least two claims, or two or more claims. Additionally, in cases where a convention analogous to “at least one of A, B, and C, etc.” is used, in general, such a construction is intended in the sense that someone skilled in the art would understand the convention, for example, “a system possessing at least one of A, B, and C” would include, but not be limited to, systems possessing A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. In cases where a convention analogous to “at least one of A, B, or C, etc.” is used...The term "a system possessing at least one of A, B, or C" is generally used, and this construction is intended to be understood by someone skilled in the technique. For example, "a system possessing at least one of A, B, or C" would include, but not be limited to, systems possessing A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. It will also be understood by those within the field. Petition 870250101184, dated 05 / 11 / 2025, pp. 33 / 39 26 / 26 technique that virtually any disjunctive word and / or phrase that presents two or more alternative terms, whether in the description, claims or drawings, should be understood as encompassing the possibilities of including one of the terms, any of the terms or both terms. For example, the sentence A or B will be understood as including the possibilities of A or B or A and B.

[0069] From the foregoing, it will be appreciated that various implementations of the present disclosure have been described in this document for illustrative purposes, and that various modifications may be made without departing from the scope and spirit of the present disclosure. Consequently, the various implementations disclosed in this document are not intended to be limiting, with the true scope and spirit being indicated by the following claims. Petition 870250101184, dated 05 / 11 / 2025, pp. 34 / 39

Claims

1 / 6 CLAIMS 1. A method, CHARACTERIZED in that it comprises: receiving, by a device processor, a network node configuration of a wireless network, wherein the configuration indicates Hybrid Automatic Repeat Request (HARQ) feedback information disabled or enabled for each or all of a plurality of HARQ processes; receiving, by the processor, a Downlink Control Information (DCI) from the network node, wherein the DCI indicates a scheduling of multiple transport blocks (TBs) associated with the HARQ processes on a shared narrowband physical downlink channel (NPDSCH); performing, by the processor, an NPDSCH reception for the TBs based on the DCI; and determining, by the processor, whether to report one or more HARQ feedbacks corresponding to the TBs based on the configuration.

2. Method, according to claim 1, CHARACTERIZED in that the determination of whether to report one or more HARQ feedbacks corresponding to the TBs based on the configuration comprises: determining whether to report the one or more HARQ feedbacks corresponding to the TBs associated with the HARQ processes with HARQ feedback information enabled, as indicated by the configuration; and determining whether not to report any HARQ feedbacks corresponding to the TBs associated with the HARQ processes with HARQ feedback information disabled, as indicated by the configuration.

3. Method, according to claim 1, CHARACTERIZED by the fact that, in an event where a parameter indicating HARQ confirmation grouping (ACK) is configured, the one or more HARQ feedbacks comprise a single HARQ feedback generated by performing a logical AND operation of multiple HARQ feedbacks corresponding to the TBs associated with the HARQ processes with HARQ feedback information enabled, or by performing a logical AND operation of multiple HARQ feedbacks corresponding to the TBs and assuming 1 in the logical AND operation for the TBs associated with the HARQ processes with HARQ feedback information disabled.

4. Method, according to claim 1, CHARACTERIZED in that, in an event where a parameter indicating HARQ-ACK grouping is not configured, the one or more HARQ feedbacks comprise one or multiple HARQ feedbacks, each corresponding to a respective TB associated with the HARQ processes with HARQ feedback information enabled.

5. Method, according to claim 1, CHARACTERIZED in that the TBs associated with the HARQ processes with HARQ feedback information enabled are configured in multiple TB packages, and one or more HARQ feedbacks comprise multiple HARQ feedbacks generated by performing a logical AND operation on all TBs in each of the TB packages.

6. Method, according to claim 1, CHARACTERIZED in that the TBs are configured in multiple TB packages, and one or more HARQ feedbacks comprise one or multiple HARQ feedbacks generated by performing a logical AND operation of HARQ feedbacks on all TBs and assuming 1 in the logical AND operation for the TBs associated with the HARQ processes with HARQ feedback information disabled in each of the TB packages.

7. Method, according to claim 1, CHARACTERIZED in that it further comprises: determining not to perform DCI monitoring in a first time period subsequent to the reporting of one or more HARQ feedbacks, in an event where at least one of the TBs Petition 870250090266, dated 03 / 10 / 2025, page 17 / 22 3 / 6 is associated with HARQ processes with enabled HARQ feedback information.

8. Method according to claim 7, CHARACTERIZED in that the first time period comprises a round-trip time (RTT) between the device and the network node, or an offset to delay an application of a downlink (DL) configuration indicated by a medium access control (MAC) control element (CE) command on a PDSCH.

9. Method, according to claim 2, CHARACTERIZED in that it further comprises: determining not to perform DCI monitoring in a second time period subsequent to the receipt of NPDSCH, in an event that all TBs are associated with HARQ processes with HARQ feedback information disabled.

10. Method according to claim 9, CHARACTERIZED in that the second time period comprises a half-duplex guard period.

11. Apparatus, CHARACTERIZED by the fact that it comprises: a transceiver that, during operation, communicates wirelessly with a network node of a wireless network; and a processor communicatively coupled to the transceiver such that, during operation, the processor performs operations comprising: receiving, through the transceiver, a network node configuration, wherein the configuration indicates Hybrid Automatic Repeat Request (HARQ) feedback information disabled or enabled for each or all of a plurality of HARQ processes; receiving, through the transceiver, a Downlink Control Information (DCI) from the network node, wherein the DCI indicates a scheduling of multiple transport blocks (TBs) associated with HARQ processes on a shared narrowband physical downlink channel (NPDSCH); Petition 870250090266, dated 03 / 10 / 2025, p.18 / 22 4 / 6 perform, via the transceiver, an NPDSCH reception for the TBs based on the DCI; and determine whether to report one or more HARQ feedbacks corresponding to the TBs based on the configuration.

12. Apparatus, according to claim 11, CHARACTERIZED in that the determination of whether to report one or more HARQ feedbacks corresponding to the TBs based on the configuration comprises: determining whether to report the one or more HARQ feedbacks corresponding to the TBs associated with the HARQ processes with HARQ feedback information enabled, as indicated by the configuration; and determining whether not to report any HARQ feedbacks corresponding to the TBs associated with the HARQ processes with HARQ feedback information disabled, as indicated by the configuration.

13. Device according to claim 11, CHARACTERIZED in that, in an event where a parameter indicating HARQ confirmation grouping (ACK) is configured, the one or more HARQ feedbacks comprise a single HARQ feedback generated by performing a multiple HARQ feedback AND operation corresponding to the TBs associated with the HARQ processes with HARQ feedback information enabled, or by performing a multiple HARQ feedback AND operation corresponding to the TBs and assuming 1 in the AND operation for the TBs associated with the HARQ processes with HARQ feedback information disabled.

14. Device according to claim 11, CHARACTERIZED in that, in an event where a parameter indicating HARQ-ACK grouping is not configured, the one or more HARQ feedbacks comprise one or multiple HARQ feedbacks, each corresponding to a respective TB associated with the HARQ processes with HARQ feedback information enabled. Petition 870250090266, dated 03 / 10 / 2025, p. 19 / 22 5 / 6 15. Apparatus, according to claim 11, CHARACTERIZED in that the TBs associated with the HARQ processes with HARQ feedback information enabled are configured in multiple TB packages, and one or more HARQ feedbacks comprise multiple HARQ feedbacks generated by performing a logical AND operation on all TBs in each of the TB packages.

16. Apparatus, according to claim 11, CHARACTERIZED in that the TBs are configured in multiple TB packages, and one or more HARQ feedbacks comprise one or multiple HARQ feedbacks generated by performing a logical AND operation of HARQ feedbacks on all TBs and assuming 1 in the logical AND operation for the TBs associated with the HARQ processes with HARQ feedback information disabled in each of the TB packages.

17. Device according to claim 11, CHARACTERIZED in that, during operation, the processor also performs operations comprising: determining not to perform DCI monitoring in a first time period subsequent to the reporting of one or more HARQ feedbacks, in an event where at least one of the TBs is associated with HARQ processes with HARQ feedback information enabled.

18. Device according to claim 17, CHARACTERIZED in that the first time period comprises a round-trip time (RTT) between the device and the network node, or an offset to delay an application of a downlink (DL) configuration indicated by a medium access control (MAC) control element (CE) command on a PDSCH.

19. Device, according to claim 11, CHARACTERIZED in that, during operation, the processor also performs operations comprising: determining not to perform DCI monitoring in a second period of time subsequent to receiving NPDSCH, in an event that all TBs are associated with HARQ processes with HARQ feedback information disabled.

20. Device, according to claim 19, CHARACTERIZED in that the second time period comprises a half-duplex storage period. Petition 870250090266, dated 03 / 10 / 2025, pp. 21 / 22

Images