System and technique for scheduling feedbackless hybrid automatic repeat request resources

Abstract

Systems and techniques for wireless communications are provided. For example, an apparatus (e.g., a user equipment (UE)) may receive a plurality of downlink communications, each downlink communication associated with a hybrid automatic repeat request (HARQ) process. The apparatus may determine one or more uplink communications, each uplink communication including feedback associated with at least one downlink communication of the plurality of downlink communications. The apparatus may transmit the one or more uplink communications based on an uplink communication transmission configuration, the uplink communication transmission configuration determined based on a type of each downlink communication of the plurality of downlink communications.

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE

[0001] Aspects of the present disclosure generally relate to wireless communications. In some implementations, examples are described for implementing multi-Transport Block (multi-TB) scheduling using Hybrid Automatic Repeat Request (HARQ) enabled and HARQ disabled processes. [Background technology]

[0002]

[0002] Wireless communication systems are deployed to provide various telecommunication services, including telephone, video, data, messaging, and broadcast, among others. Wireless communication systems have evolved through various generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including interim 2.5G networks), third generation (3G) high-speed data, Internet-enabled wireless service, fourth generation (4G) service (e.g., Long-Term Evolution (LTE), or WiMax), and fifth generation (5G) service (e.g., New Radio (NR)). Currently, many different types of wireless communication systems are in use, including cellular systems and personal communications service (PCS) systems. Examples of known cellular systems include the Cellular Analog Advanced Mobile Phone System (AMPS) and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile communication (GSM), etc. Summary of the Invention

[0003]

[0003] The following provides a simplified summary of one or more aspects disclosed herein. Therefore, the following summary should not be considered as an extensive overview of all contemplated aspects, nor should it be considered as identifying key or critical elements of all contemplated aspects or defining the scope related to any particular aspect. Thus, the sole purpose of the following summary is to present certain concepts of one or more aspects of the mechanisms disclosed herein in a simplified form prior to the detailed description presented below.

[0004]

[0004] A system, method, apparatus, and computer-readable medium for implementing wireless communication are disclosed. Both NB-IoT and eMTC are low-power wide-area network (LPWAN) wireless communication standards developed by 3GPP. For example, eMTC is a type of LTE-M network that can be used to support IoT devices (e.g., among others) through lower device complexity and extended coverage based on existing LTE base stations. eMTC can be implemented as a subtype of LTE-M network that operates within an existing LTE deployment and / or in a standalone deployment. NB-IoT is another low-power wide-area network (LPWAN) wireless communication standard developed by 3GPP. NB-IoT networks can be designed to provide improved indoor coverage, low cost, long battery life, and high connection density. NB-IoT networks can be implemented using a subset of LTE limited to a single narrow band with a bandwidth of 200 kilohertz (kHz).

[0005]

[0005] In eMTC and NB-IoT, a UE may receive one or more downlink communications from a base station. The downlink communications may include one or more Transport Blocks (TBs) (e.g., payloads passed between the MAC layer and the PHY layer for a shared data channel, such as a Physical Downlink Shared Channel (PDSCH) and / or a Physical Uplink Shared Channel (PUSCH)). The UE may generate feedback for some or all of the TBs received or otherwise decoded by the UE. The feedback may include an acknowledgement (ACK) or a negative acknowledgement (NACK) for one or more TBs received or decoded by the UE. In some examples, the UE may generate and send hybrid automatic repeat request (HARQ) feedback to the base station from which the UE received one or more TBs.

[0006]

[0006] A TB may be scheduled using one or more HARQ processes. A HARQ process may include a series of wireless communications between a UE and a base station, where the base station does not transmit a next TB on a HARQ process until the base station receives (e.g., from the UE) a HARQ ACK for the most recent TB on the HARQ process. When multiple HARQ processes are utilized, the HARQ processes may be performed in parallel. In some examples, in eMTC, up to eight TBs (e.g., HARQ processes) may be scheduled by a single Downlink Control Information (DCI) in what may be referred to as "multi-TB scheduling". In NB-IoT, a UE may use up to two HARQ processes for wireless communications with a base station. In some cases, some eMTC and NB-IoT implementations may treat all HARQ processes associated with a UE as feedback-enabled HARQ processes. A feedback-enabled HARQ process may be an HARQ process in which a subsequent TB is not transmitted to the UE until the base station receives HARQ feedback for the most recent TB (eg, as described above).

[0007] In some examples, feedback-enabled HARQ processes may contribute to "HARQ stalls" in eMTC and / or NB-IoT implementations with relatively long Round Trip Times (RTTs) between the UE and the base station. HARQ stalls may occur when a base station goes idle (e.g., does not transmit) on a given feedback-enabled HARQ process while waiting (e.g., for an RTT) to receive a HARQ ACK / NACK for the most recent TB transmitted on the feedback-enabled HARQ process. eMTC and / or NB-IoT may be implemented using one or more terrestrial networks, one or more non-terrestrial networks (Non-Terrestrial Networks (NTNs)), or a combination of the two. When eMTC and / or NB-IoT are implemented using NTNs, wireless communications may be exchanged between the UE and NTN nodes or entities, which may include a gateway, a base station or a portion thereof, and / or one or more satellites or other high altitude platforms. Based on the relatively large distance between the UE and the NTN node, the wireless communication between the UE and the NTN node may experience relatively large propagation time delay or round trip times (RTTs). HARQ stalls may increase when the RTT between the UE and the base station is relatively high. For example, in eMTC over NTN and / or NB-IoT over NTN, the RTT between the UE and the base station may be tens or hundreds of milliseconds (ms), and HARQ stalls may be more likely to occur for the feedback-enabled HARQ process implemented in eMTC over NTN or NB-IoT over NTN.

[0008]

[0008] In some examples, eMTC and / or NB-IoT may include one or more feedback-disabled HARQ processes that may be used to reduce HARQ stalls. In a feedback-disabled HARQ process, the UE may not generate or transmit feedback for a TB received on the feedback-disabled HARQ process, and the base station may transmit or schedule a subsequent TB to the UE on the feedback-disabled HARQ process without waiting to receive a HARQ ACK / NACK from the UE. In some examples of eMTC over NTN and / or NB-IoT over NTN, the UE may communicate with the base station using a combination of feedback-enabled and feedback-disabled HARQ processes. For example, the UE and the base station may use multi-TB scheduling, where one or more feedback-enabled HARQ processes and one or more feedback-disabled HARQ processes are scheduling using a single DCI. What is needed are systems and techniques that can be used to implement multi-TB scheduling for coexisting feedback-enabled and feedback-disabled HARQ processes. For example, there is a need for systems and techniques that can be used to implement multi-TB scheduling for coexisting feedback-enabled and feedback-disabled HARQ processes in eMTC over NTN and NB-IoT over NTN.

[0009]

[0009] Systems and techniques for multi-TB scheduling of feedback-enabled HARQ processes and feedback-disabled HARQ processes are described herein. For example, the systems and techniques may be used to implement multi-TB scheduling of feedback-enabled HARQ processes and feedback-disabled HARQ processes in eMTC, eMTC over NTN, NB-IoT, NB-IoT over NTN, etc. In some examples, the systems and techniques may be used to implement multi-TB scheduling of feedback-enabled HARQ processes and feedback-disabled HARQ processes in NB-IoT and / or NB-IoT over NTN. In some aspects, a UE may receive multiple TBs using a combination of feedback-disabled and feedback-enabled HARQ processes that may be scheduled (e.g., multi-TB scheduled) by a single downlink control information (DCI). A HARQ ACK bit (e.g., 0 or 1 for ACK or NACK, respectively) may be determined for a TB received via a feedback-enabled HARQ process included in a multi-TB scheduled block. In some cases, one or more "dummy" (e.g., placeholder) bits may be determined for TBs received via feedback-disabled HARQ processes included in a multi-TB scheduled block. In some aspects, dummy bits, other feedback, and / or uplink communication may be omitted for some or all of the TBs received via feedback-disabled HARQ processes included in a multi-TB scheduled block.

[0010] In some aspects, systems and techniques may be used to implement multi-TB scheduling for one or more combinations (e.g., heterogeneous sets) of feedback-enabled and feedback-disabled HARQ processes. For example, each TB of a multi-TB scheduled block may be received in a different downlink time slot or subframe at the UE. The UE may generate or schedule a multi-HARQ scheduled block in response to receiving a TB of the multi-TB scheduled block. In some aspects, a multi-HARQ scheduled block may include a HARQ-ACK bit (e.g., a HARQ ACK / NACK) determined for each TB received via a feedback-enabled HARQ process, where a relative position of the HARQ-ACK bit in the multi-HARQ scheduled block is the same as or is otherwise based on a relative position of a corresponding TB in the multi-TB scheduled block. In some aspects, a multi-HARQ scheduled block may include a "hole" or empty uplink slot / subframe for each TB received via a feedback-disabled HARQ process. The location of the empty uplink slots or subframes in the multi-HARQ scheduled block may be the same as or may be otherwise based on the corresponding location(s) of the feedback disabled TB in the multi-TB scheduled block. In some cases, the multi-HARQ scheduled block may be generated to omit any empty uplink slots or subframes associated with the feedback disabled TBs of the multi-TB scheduled block.In some aspects, systems and techniques may be used to implement multi-TB scheduling for one or more combinations (e.g., heterogeneous sets) of feedback-enabled and feedback-disabled HARQ processes by continuously scheduling feedback-enabled HARQ processes (e.g., in multi-TB scheduled blocks received by the UE and in multi-HARQ-ACK scheduled blocks generated by the UE as feedback based on the multi-TB scheduled blocks). In some cases, feedback-disabled HARQ processes may be additionally continuously scheduled either before or after continuously scheduled feedback-enabled HARQ processes.

[0011] In some aspects, a multi-TB scheduled block may include one or more feedback-enabled HARQ processes and one or more feedback-disabled HARQ processes, where the multi-TB scheduled block is divided into multiple TB bundles. Each TB bundle may include a unique subset of the HARQ processes and TBs included in or otherwise associated with the multi-TB scheduled block. In some examples, the systems and techniques may implement multi-TB scheduling by generating a "dummy" (e.g., placeholder) HARQ-ACK bit or value for any feedback-disabled TBs in one or more TB bundles. In some cases, a dummy or placeholder HARQ-ACK is not generated for feedback-disabled TBs included in a bundle that includes only feedback-disabled TBs (e.g., if a bundle does not include at least one feedback-enabled TB, a dummy HARQ-ACK is not generated for any of the TBs in the bundle). In some aspects, if a bundle includes at least one feedback-enabled TB, a dummy HARQ-ACK bit may be generated for each feedback-disabled TB included in the bundle, and a HARQ-ACK bit may be generated for each feedback-enabled TB included in the bundle.

[0012] According to at least one example, a method for wireless communication in a user equipment (UE) is provided. The method may include receiving a plurality of downlink communications, where each downlink communication of the plurality of downlink communications is associated with a hybrid automatic repeat request (HARQ) process, determining one or more uplink communications, where each uplink communication of the one or more uplink communications includes feedback associated with at least one downlink communication of the plurality of downlink communications, and transmitting the one or more uplink communications based on an uplink communication transmission configuration, where the uplink communication transmission configuration is determined based on a type of each downlink communication of the plurality of downlink communications.

[0013] In another example, a method for wireless communication in a user equipment (UE) is provided, which may include receiving a first Physical Downlink Shared Channel (PDSCH) communication including at least a first downlink communication of a plurality of downlink communications, the first downlink communication including a transport block (TB) associated with a first feedback disabled Hybrid Automatic Repeat Request (HARQ) process, and receiving a second PDSCH communication including at least an additional downlink communication, the additional downlink communication including an additional TB associated with the first feedback disabled HARQ process, where the first PDSCH communication and the second PDSCH communication are separated by a predefined time interval.

[0014] In another example, a method for wireless communication in a Narrowband-Internet of Things (NB-IoT) UE is provided. The method may include receiving, in the NB-IoT UE, a plurality of downlink communications associated with up to four HARQ processes, the up to four HARQ processes including a subset of up to two feedback-enabled HARQ processes, and one or more HARQ processes of the up to four HARQ processes not included in the subset are feedback-disabled HARQ processes.

[0015]

[0015] In another example, an apparatus for wireless communication is provided that includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor may be configured to receive a plurality of downlink communications, where each downlink communication of the plurality of downlink communications is associated with a Hybrid Automatic Repeat Request (HARQ) process, determine one or more uplink communications, where each uplink communication of the one or more uplink communications includes feedback associated with at least one downlink communication of the plurality of downlink communications, and transmit the one or more uplink communications based on an uplink communication transmission configuration, where the uplink communication transmission configuration is determined based on a type of each downlink communication of the plurality of downlink communications.

[0016] In another example, an apparatus for wireless communication is provided, including at least one memory and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to receive a first Physical Downlink Shared Channel (PDSCH) communication including at least a first downlink communication of a plurality of downlink communications, the first downlink communication including a transport block (TB) associated with a first feedback disabled Hybrid Automatic Repeat Request (HARQ) process, and receive a second PDSCH communication including at least an additional downlink communication, the additional downlink communication including an additional TB associated with the first feedback disabled HARQ process, wherein the first PDSCH communication and the second PDSCH communication are separated by a predefined time interval.

[0017] In another example, an apparatus (e.g., a Narrowband Internet of Things (NB-IoT) UE or component thereof) for wireless communication is provided that includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor can be configured to receive a plurality of downlink communications associated with up to four HARQ processes, the up to four HARQ processes including a subset of up to two feedback-enabled HARQ processes, and one or more HARQ processes of the up to four HARQ processes that are not included in the subset are feedback-disabled HARQ processes.

[0018]

[0018] In another example, a non-transitory computer-readable medium of an apparatus having stored thereon instructions which, when executed by one or more processors, cause the one or more processors to receive a plurality of downlink communications, where each downlink communication of the plurality of downlink communications is associated with a hybrid automatic repeat request (HARQ) process, determine one or more uplink communications, where each uplink communication of the one or more uplink communications includes feedback associated with at least one downlink communication of the plurality of downlink communications, and transmit the one or more uplink communications based on an uplink communication transmission configuration, where the uplink communication transmission configuration is determined based on a type of each downlink communication of the plurality of downlink communications.

[0019]

[0019] In another example, a non-transitory computer-readable medium of an apparatus having stored thereon instructions that, when executed by one or more processors, cause the one or more processors to receive a first physical downlink shared channel (PDSCH) communication including at least a first downlink communication of a plurality of downlink communications, the first downlink communication including a transport block (TB) associated with a first feedback disabled hybrid automatic repeat request (HARQ) process, and receive a second PDSCH communication including at least an additional downlink communication, the additional downlink communication including an additional TB associated with the first feedback disabled HARQ process, wherein the first PDSCH communication and the second PDSCH communication are separated by a predefined time interval.

[0020]

[0020] In another example, a non-transitory computer-readable medium for a Narrowband Internet of Things (NB-IoT) user equipment (UE) is provided having instructions stored thereon which, when executed by one or more processors, cause the one or more processors to receive a plurality of downlink communications associated with up to four HARQ processes, the maximum four HARQ processes including a subset of up to two feedback-enabled HARQ processes, and one or more HARQ processes of the maximum four HARQ processes that are not included in the subset are feedback-disabled HARQ processes.

[0021] In another example, an apparatus for wireless communication is provided, the apparatus including: means for receiving a plurality of downlink communications, where each downlink communication of the plurality of downlink communications is associated with a hybrid automatic repeat request (HARQ) process; means for determining one or more uplink communications, where each uplink communication of the one or more uplink communications includes feedback associated with at least one downlink communication of the plurality of downlink communications; and means for transmitting the one or more uplink communications based on an uplink communication transmission configuration, where the uplink communication transmission configuration is determined based on a type of each downlink communication of the plurality of downlink communications.

[0022] In another example, an apparatus for wireless communication is provided, the apparatus including: means for receiving a first Physical Downlink Shared Channel (PDSCH) communication including at least a first downlink communication of a plurality of downlink communications, the first downlink communication including a transport block (TB) associated with a first feedback disabled Hybrid Automatic Repeat Request (HARQ) process; and means for receiving a second PDSCH communication including at least an additional downlink communication, the additional downlink communication including an additional TB associated with the first feedback disabled HARQ process, where the first PDSCH communication and the second PDSCH communication are separated by a predefined time interval.

[0023] In another example, an apparatus (e.g., a Narrowband Internet of Things (NB-IoT) UE) for wireless communication is provided that includes means for receiving a plurality of downlink communications associated with up to four HARQ processes, the plurality of downlink communications including a subset of up to two feedback-enabled HARQ processes, and one or more HARQ processes of the maximum four HARQ processes not included in the subset are feedback-disabled HARQ processes.

[0024]

[0024] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as substantially described in this specification with reference to the drawings and the specification.

[0025]

[0025] The foregoing has outlined rather broadly the features and technical advantages of the examples according to the present disclosure so that the following "Description of the Preferred Embodiments" may be better understood. Additional features and advantages are described below. The concepts and examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The properties of the concepts disclosed herein, both their mechanisms and methods of operation, together with associated advantages, will be better understood from the following description when considered in conjunction with the accompanying figures. Each of the figures is provided for illustration and explanation, and not as a definition of the limits of the claims.

[0026]

[0026] Although aspects are described in this disclosure by illustrating some examples, those skilled in the art will understand that such aspects can be implemented in many different configurations and scenarios. The techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some aspects may be implemented via integrated chip implementations or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital applications (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). It is contemplated that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed configurations, and / or end-user devices of various sizes, shapes, and configurations.

[0027]

[0027] Other objects and advantages associated with the embodiments disclosed herein will become apparent to those skilled in the art based on the accompanying drawings and detailed description. [Brief description of the drawings]

[0028]

[0028] The accompanying drawings are presented to aid in the explanation of various aspects of the present disclosure and are provided only to illustrate the aspects and not to limit the aspects. [Figure 1]

[0029] FIG. 1 is a block diagram illustrating an example of a wireless communication network, in accordance with some examples. [Diagram 2]

[0030] FIG. 2 illustrates a design of a base station and a user equipment (UE) device that enables transmission and processing of signals exchanged between the UE and the base station in accordance with some examples. [Diagram 3]

[0031] FIG. 2 illustrates an example of a disaggregated base station, in accordance with some examples. [Figure 4]

[0032] FIG. 2 is a block diagram illustrating components of user equipment, according to some examples. [Figure 5A]

[0033] FIG. 1 illustrates an example network architecture supporting communication via non-terrestrial network (NTN) devices, according to some examples. [Figure 5B] FIG. 1 illustrates an example network architecture supporting communication via non-terrestrial network (NTN) devices, according to some examples. [Figure 5C] FIG. 1 illustrates an example network architecture supporting communication via non-terrestrial network (NTN) devices, according to some examples. [Figure 6]

[0034] FIG. 1 illustrates an example of an NTN configuration, according to some examples. [Figure 7A]

[0035] FIG. 1 illustrates an example of multi-transport block (multi-TB) scheduling, according to some examples. [Figure 7B] FIG. 1 illustrates an example of multi-transport block (multi-TB) scheduling, according to some examples. [Figure 8]

[0036] FIG. 1 illustrates an example of multi-TB scheduling with feedback-enabled and feedback-disabled Hybrid Automatic Repeat Request (HARQ) processes included in the same multi-TB block, according to some examples. [Figure 9]

[0037] FIG. 1 illustrates an example of multi-TB scheduling with feedback-enabled and feedback-disabled HARQ processes included in the same multi-TB block, according to some examples. [Figure 10A]

[0038] FIG. 1 illustrates an example of multi-TB scheduling of a multi-TB block using TB bundling, according to some examples. [Figure 10B]

[0039] FIG. 2 illustrates an example of a TB bundling configuration, according to some examples. [Figure 11]

[0040] FIG. 13 illustrates another example of multi-TB scheduling of a multi-TB block using TB bundling, according to some examples. [Figure 12]

[0041] FIG. 1 illustrates an example of modified HARQ round trip time (RTT) timer start for multi-TB scheduling, according to some examples. [Figure 13]

[0042] 1 is a flow diagram illustrating an example of a process implemented by an aircraft UE to perform a mobile handover, according to some examples. [Figure 14]

[0043] FIG. 1 is a block diagram illustrating an example of a computing system, in accordance with some examples. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0029]

[0044] Certain aspects of the present disclosure are provided below for illustrative purposes. Alternative aspects may be devised without departing from the scope of the present disclosure. In addition, well-known elements of the present disclosure are not described in detail or are omitted so as not to obscure the relevant details of the present disclosure. As will be apparent to one skilled in the art, some of the aspects described herein may be applied independently, and some of them may be applied in combination. In the following description, for purposes of explanation, specific details are set forth to provide a thorough understanding of the aspects of the present application. However, it will be apparent that the various aspects may be practiced without these specific details. The figures and descriptions are not intended to be limiting.

[0030]

[0045] The following description provides only exemplary embodiments and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the following description of exemplary embodiments provides those skilled in the art with an enabling description for implementing the exemplary embodiments. It should be understood that various changes may be made in the function and arrangement of elements without departing from the scope of the present application as set forth in the appended claims.

[0031]

[0046] Wireless communication networks are deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, any combination thereof, or other communication services. Wireless communication networks may support both access links and sidelinks for communication between wireless devices. An access link may refer to any communication link between a client device (e.g., a user equipment (UE), a station (STA), or other client device) and a base station (e.g., a 3GPP gNB for 5G / NR, a 3GPP eNB for 4G / LTE, a Wi-Fi access point (AP), or other base station). For example, an access link may support uplink signaling, downlink signaling, connection procedures, etc. An example of an access link is a Uu link or interface (e.g., also referred to as NR-Uu) between a 3GPP gNB and a UE.

[0032]

[0047] The 3rd Generation Partnership Project (3GPP) has defined specifications that provide support for machine-type communication (MTC). MTC may be used to provide wireless communication between Internet-of-Things (IoT) devices. A large-scale deployment of IoT devices may involve tens of thousands, hundreds of thousands, or more IoT devices. MTC wireless communication may be used to provide improved coverage, latency, power consumption, and / or connection density, etc., for large-scale deployment of IoT devices (e.g., among other devices). A large-scale deployment of devices that communicate via MTC may also be referred to as large-scale machine-type communication (mMTC). In some cases, mMTC may be implemented using enhanced machine-type communication (eMTC) and / or narrowband IoT (NB-IoT).

[0033]

[0048] Both NB-IoT and eMTC are low power wide area network (LPWAN) wireless communication standards developed by 3GPP. For example, eMTC is a type of LTE-M network that may be used to support IoT devices (e.g., among others) through lower device complexity and extended coverage based on existing LTE base stations. In some cases, eMTC may be used to provide relatively high data rates to connected devices. eMTC may be implemented as a subtype of an LTE-M network. For example, an eMTC Cat-M1 network may have a channel width (e.g., bandwidth) of 1.08 MHz operating within an existing LTE deployment and a channel width of 1.4 MHz operating in a standalone deployment. In some cases, an eMTC network may include a power saving mode (PSM) and / or other optimizations that may be used to provide improved battery life for devices connected to or communicating through the eMTC network.

[0034]

[0049] NB-IoT is another low-power wide area network (LPWAN) wireless communication standard developed by 3GPP. NB-IoT is a radio access type (RAT) supported by the evolved UMTS Terrestrial Radio Access Network (E-UTRAN) that was added by 3GPP in the 3GPP Release 13 specification to provide 180 kHz UL / DL (uplink / downlink) bandwidth. NB-IoT networks can be designed to provide improved indoor coverage, low cost, long battery life, and high connection density. NB-IoT networks can be implemented using a subset of LTE limited to a single narrow band with a bandwidth of 200 kilohertz (kHz). Orthogonal frequency-division multiplexing (OFDM) modulation is used for downlink (DL) communications, and single-carrier frequency-division multiple access (SC-FDMA) is used for uplink (UL) communications.

[0035]

[0050] In eMTC and NB-IoT, a UE may receive one or more downlink communications from a base station. The downlink communications may include one or more transport blocks (TBs), medium access control (MAC) packet data units (PDUs), etc. For example, a TB may be a payload passed between a MAC layer and a PHY layer for a shared data channel, such as a physical downlink shared channel (PDSCH) and / or a physical uplink shared channel (PUSCH). In some cases, the UE may generate feedback for some or all of the TBs received or otherwise decoded by the UE. For example, the feedback may include an acknowledgement (ACK) or a negative acknowledgement (NACK) for one or more TBs received or decoded by the UE. The UE may transmit the generated feedback (e.g., ACK / NACK) back to the base station where the UE received the TB corresponding to each generated ACK or NACK. In some examples, the UE may generate and transmit hybrid automatic repeat request (HARQ) feedback to the base station according to an output of a decoding procedure applied at the UE for the received TB. For example, the UE may generate and transmit a HARQ ACK to indicate to the base station that the UE successfully received and decoded a given TB, and the UE may generate and transmit a HARQ NACK to indicate to the base station that the UE did not successfully decode a given TB.

[0036]

[0051] TBs may be scheduled using one or more HARQ processes associated with the UE and / or the base station. Each HARQ process may include a series of wireless communications between the UE and the base station, where the base station does not transmit the next TB for a given HARQ process until the base station receives (e.g., from the UE) a HARQ ACK for the current or most recently scheduled TB on the given HARQ process. When multiple HARQ processes are utilized, the HARQ processes may be performed in parallel. For example, if a total of four HARQ processes are used to schedule TBs from the base station to the UE, a HARQ NACK or other transmission error on HARQ process #2 will not prevent the UE from continuing to receive new TBs on HARQ processes #1, #3, and #4 (e.g., as long as the UE continues to transmit HARQ ACKs for TBs scheduled on HARQ processes #1, #3, and #4). In some examples, in eMTC, the UE may use up to eight HARQ processes for wireless communications with the base station. For example, in eMTC, up to eight TBs (e.g., HARQ processes) can be scheduled by a single downlink control information (DCI) in what is sometimes referred to as "multi-TB scheduling." In NB-IoT, a UE may use up to two HARQ processes for wireless communication with a base station.

[0037]

[0052] In some cases, some eMTC and NB-IoT implementations may operate under the assumption that all HARQ processes associated with a UE (e.g., used by the UE to receive TBs from a base station) are feedback-enabled HARQ processes. For example, a feedback-enabled HARQ process may be an HARQ process in which a subsequent TB is not scheduled or transmitted to the UE until the base station receives HARQ feedback (e.g., ACK / NACK) for the previous TB (e.g., as described above).

[0038]

[0053] In some examples, feedback-enabled HARQ processes may contribute to "HARQ stalls" in eMTC and / or NB-IoT implementations with relatively long RTTs or RTDs between the UE and the base station. HARQ stalls may occur when a base station is forced to idle (e.g., not transmit) on a given feedback-enabled HARQ process while waiting to receive a HARQ ACK / NACK for the most recent TB it transmitted on the given feedback-enabled HARQ process. For example, when a base station transmits a TB on a feedback-enabled HARQ process, the base station then spends at least one full RTT waiting (e.g., stalling or idle) to receive a HARQ ACK / NACK that will be used to determine the base station's next transmission (e.g., transmit the next TB in response to the ACK and retransmit the current TB in response to the NACK).

[0039]

[0054] In some cases, the impact of HARQ stalls may be negligible or relatively small, such as in terrestrial networks with relatively low RTT. For example, HARQ stalls may be unlikely to occur in terrestrial eMTC or NB-IoT networks with RTT<10 ms. However, eMTC and / or NB-IoT may be implemented using one or more terrestrial networks, one or more non-terrestrial networks (NTNs), or a combination of the two. When eMTC and / or NB-IoT are implemented using an NTN, wireless communications may be exchanged between a UE and an NTN node or entity. For example, the NTN entity may include a gateway, a base station or a portion thereof (e.g., a central unit (CU), a distributed unit (DU), a radio unit (RU), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, or other NTN nodes / entities), or one or more satellites or other high altitude platforms. Based on a relatively large distance between the UE and the NTN node (e.g., a satellite or high altitude platform, or a base station or gateway that communicates with the UE via the satellite or high altitude platform), the wireless communication between the UE and the NTN node may experience a relatively large propagation time delay. The propagation time delay may also be referred to as round trip delay (RTD) and / or round trip time (RTT). The RTD and / or RTT may be determined based on the physical distance that the wireless communication signal travels (e.g., propagates) between the UE and the NTN node. For example, when the UE communicates with a satellite or a gateway and / or base station via a satellite, the wireless communication between the UE and the satellite, gateway, or base station may travel a distance of hundreds or thousands of kilometers.

[0040]

[0055] As mentioned above, HARQ stalls may increase when the RTT between the UE and the base station is relatively high. For example, in eMTC over NTN and / or NB-IoT over NTN, the RTT between the UE and the base station may be tens or hundreds of milliseconds (ms), and HARQ stalls may be more likely to occur for feedback-enabled HARQ processes implemented in eMTC over NTN or NB-IoT over NTN.

[0041]

[0056] In some examples, eMTC and / or NB-IoT may include one or more feedback-disabled HARQ processes. In some cases, feedback-disabled HARQ processes may be used to reduce the impact and / or likelihood of HARQ stalls occurring in networks with relatively high RTTs between UEs and base stations. For example, TBs may be scheduled on feedback-disabled HARQ processes in the same or similar manner as described above with respect to feedback-enabled HARQ processes. However, in feedback-disabled HARQ processes, the UE may not generate or transmit feedback for TBs received on the feedback-disabled HARQ process. Additionally or alternatively, the base station may transmit or schedule a subsequent TB to the UE on a feedback-disabled HARQ process without waiting to receive a HARQ ACK / NACK from the UE (e.g., for a previously scheduled TB).

[0042]

[0057] Feedback-disabled HARQ processes may be used to reduce or prevent HARQ stalls, but in some cases may not be used to completely replace feedback-enabled HARQ processes (e.g., since some TBs and / or HARQ processes may still rely on the exchange of HARQ ACK / NACKs between the UE and the base station). For example, a UE communicating with a base station using eMTC / NB-IoT over NTN may be associated with one or more HARQ processes used to transmit TBs with important or sensitive data, where HARQ ACK / NACKs should be used to handle missing or erroneous TBs.

[0043]

[0058] In some examples of eMTC over NTN and / or NB-IoT over NTN, a UE may communicate with a base station using a combination of feedback-enabled and feedback-disabled HARQ processes. For example, the UE and base station may use multi-TB scheduling with one or more feedback-enabled HARQ processes and one or more feedback-disabled HARQ processes scheduling using a single DCI. As previously mentioned, existing approaches for eMTC and NB-IoT may assume that all of the TBs scheduled by a single DCI have HARQ feedback enabled. In some cases, existing specifications for multi-TB scheduling in eMTC and / or NB-IoT may assume that each TB included in multi-TB scheduling has HARQ feedback enabled. What is needed is a system and technique that can be used to implement multi-TB scheduling for coexisting feedback-enabled and feedback-disabled HARQ processes. What is needed is a system and technique that can be used to implement multi-TB scheduling for coexisting feedback-enabled and feedback-disabled HARQ processes in eMTC over NTN and NB-IoT over NTN, for example.

[0044]

[0059] Systems, apparatuses, processes (also referred to as methods), and computer-readable media (collectively "systems and techniques") for multi-TB scheduling of feedback-enabled and feedback-disabled HARQ processes are described herein. For example, the systems and techniques may be used to implement multi-TB scheduling of feedback-enabled and feedback-disabled HARQ processes in eMTC and / or eMTC over NTN. In some examples, the systems and techniques may be used to implement multi-TB scheduling of feedback-enabled and feedback-disabled HARQ processes in NB-IoT and / or NB-IoT over NTN. For example, in eMTC or NB-IoT, a UE may receive multiple downlink communications (e.g., TBs) from a base station via multiple HARQ processes. One or more of the HARQ processes may have HARQ feedback disabled (e.g., feedback-disabled HARQ processes). For example, the HARQ processes may have HARQ feedback disabled to prevent or reduce HARQ stalls and / or throughput losses associated with RTT between the UE and the base station. Additionally, one or more of the HARQ processes may have HARQ feedback enabled (eg, a feedback-enabled HARQ process).

[0045]

[0060] In some aspects, a UE may receive multiple TBs using a combination of feedback-disabled and feedback-enabled HARQ processes that may be scheduled (e.g., multi-TB scheduled) by a single downlink control information (DCI). In some examples, the systems and techniques may be used to determine one or more uplink communications in response to some or all of the multi-scheduled TBs associated with a single DCI. For example, a HARQ ACK bit (e.g., 0 or 1 for ACK or NACK, respectively) may be determined for TBs received via feedback-enabled HARQ processes included in a multi-TB scheduled block. In some cases, one or more dummy bits may be determined for TBs received via feedback-disabled HARQ processes included in a multi-TB scheduled block. In some examples, dummy bits, other feedback, and / or uplink communications may be omitted for some or all of the TBs received via feedback-disabled HARQ processes included in a multi-TB scheduled block.

[0046]

[0061] In some examples, multi-TB scheduling may be performed for HARQ processes that have HARQ feedback enabled (e.g., feedback-enabled HARQ processes). Feedback-disabled HARQ processes may be transmitted without multi-TB scheduling. In some examples, multi-TB scheduling may be performed only for feedback-disabled HARQ processes, and feedback-enabled HARQ processes may be transmitted without multi-TB scheduling. In some aspects, multi-TB scheduling may be performed separately for a set of feedback-enabled HARQ processes and for a set of feedback-disabled HARQ processes, without performing multi-TB scheduling for the heterogeneous sets of feedback-enabled and feedback-disabled HARQ processes.

[0047]

[0062] In some examples, the systems and techniques may be used to implement multi-TB scheduling for one or more combinations (e.g., heterogeneous sets) of feedback-enabled and feedback-disabled HARQ processes. For example, the systems and techniques may determine a HARQ-ACK transmission timeline (also referred to herein as a "transmission schedule" or "transmission configuration") for an uplink transmission of a determined uplink communication (e.g., a determined HARQ-ACK bit). For example, each TB of a multi-TB scheduled block may be received in a different downlink time slot or subframe at the UE. The UE may generate or schedule a multi-HARQ scheduled block in response to receiving a TB of the multi-TB scheduled block. In some aspects, the multi-HARQ scheduled block may include a HARQ-ACK bit (e.g., a HARQ ACK / NACK) determined for each TB received via a feedback-enabled HARQ process, where a relative position of the HARQ-ACK bit in the multi-HARQ scheduled block is the same as or is otherwise based on a relative position of a corresponding TB in the multi-TB scheduled block. In some examples, a multi-HARQ scheduled block may include a "hole" or empty uplink slot / subframe for each TB received via a feedback-disabled HARQ process. The location of the empty uplink slot or subframe in the multi-HARQ scheduled block may be the same as or may be otherwise based on the corresponding location(s) of the feedback-disabled TB in the multi-TB scheduled block. In some cases, a multi-HARQ scheduled block may be generated to omit any empty uplink slot or subframe associated with a feedback-disabled TB of the multi-TB scheduled block.For example, a multi-HARQ scheduled block may only include HARQ-ACK bits generated for feedback valid TBs of the multi-TB scheduled block in the same relative order as the feedback valid TBs were received in the multi-TB scheduled block.

[0048]

[0063] In some examples, systems and techniques may be used to implement multi-TB scheduling for one or more combinations (e.g., heterogeneous sets) of feedback-enabled and feedback-disabled HARQ processes by continuously scheduling feedback-enabled HARQ processes (e.g., in multi-TB scheduled blocks received by the UE and in multi-HARQ-ACK scheduled blocks generated by the UE as feedback based on the multi-TB scheduled blocks). In some cases, the feedback-disabled HARQ processes may be additionally continuously scheduled either before or after the continuously scheduled feedback-enabled HARQ processes.

[0049]

[0064] In some aspects, a multi-TB scheduled block may include one or more feedback-enabled HARQ processes and one or more feedback-disabled HARQ processes, where the multi-TB scheduled block is divided into multiple TB bundles. Each TB bundle may include a unique subset of the HARQ processes and TBs included in or otherwise associated with the multi-TB scheduled block. In some examples, systems and techniques may implement multi-TB scheduling by generating a "dummy" (e.g., placeholder) HARQ-ACK bit or value for any feedback-disabled TBs in one or more TB bundles. In some cases, a dummy or placeholder HARQ-ACK is not generated for feedback-disabled TBs included in a bundle that includes only feedback-disabled TBs (e.g., if a bundle does not include at least one feedback-enabled TB, then no dummy HARQ-ACK is generated for any of the TBs in the bundle). In some aspects, if a bundle includes at least one feedback-enabled TB, then a dummy HARQ-ACK bit may be generated for each feedback-disabled TB included in the bundle, and a HARQ-ACK bit may be generated for each feedback-enabled TB included in the bundle.

[0050]

[0065] Various aspects of the disclosure are described below with reference to the figures.

[0051]

[0066] The terms "user equipment" (UE) and "network entity" as used herein are not intended to be specific or limited to any particular radio access technology (RAT) unless otherwise specified. In general, a UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, and / or a tracking device, etc.), a wearable device (e.g., a smart watch, a smart glass, a wearable ring, and / or an extended reality (XR) device, such as a virtual reality (VR) headset, an augmented reality (AR) headset or glasses, or a mixed reality (MR) headset), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an aircraft (e.g., a plane, a jet, an unmanned aerial vehicle (UAE) or drone, a helicopter, an airship, a glider, etc.), and / or an Internet of Things (IoT) device, etc., used by a user to communicate over a wireless communication network. A UE may be mobile or stationary (e.g., at a given time) and may communicate with a radio access network (RAN). As used herein, the term "UE" may be referred to interchangeably as an "access terminal" or "AT", "client device", "wireless device", "subscriber device", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station", or variations thereof. In general, a UE may communicate with a core network via the RAN, through which the UE may be connected to external networks, such as the Internet, and to other UEs.Of course, other mechanisms for connecting to the core network and / or the Internet are possible for the UE, such as via a wired access network, a wireless local area network (WLAN) network (e.g., based on the IEEE 802.11 communications standard, etc.).

[0052]

[0067] The network entity may be implemented with an aggregated or monolithic base station architecture, or alternatively with a disaggregated base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near-real-time (Near-RT) RAN Intelligent Controller (RIC), or a non-real-time (Non-RT) RIC. A base station (e.g., having an aggregated / monolithic base station architecture or a disaggregated base station architecture) may operate according to one of several RATs in communication with UEs depending on the network in which it is deployed, and may alternatively be referred to as an access point (AP), a network node, a Node B (Node B, NB), an evolved Node B (eNB), a next generation eNB (ng-eNB), a New Radio (NR) Node B (e.g., also referred to as a gNB or g Node B), etc. A base station may be primarily used to support wireless access by UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, the base station may provide edge node signaling functionality, while in other systems, it may provide additional control and / or network management functionality. A communication link through which a UE can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which a base station can send signals to a UE is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, or a forward traffic channel, etc.). The term traffic channel (TCH), as used herein, may refer to either an uplink, a reverse or downlink, and / or a forward traffic channel.

[0053]

[0068] The term "network entity" or "base station" (e.g., with aggregated / monolithic or non-aggregated base station architecture) may refer to a single physical transmit receive point (TRP) or multiple physical TRPs that may or may not be collocated. For example, when the term "network entity" or "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station, corresponding to a cell (e.g., or several cell sectors) of the base station. When the term "network entity" or "base station" refers to multiple collocated physical TRPs, the physical TRP may be an array of antennas of the base station (e.g., as in the case of a multiple-input multiple-output (MIMO) system or when the base station employs beamforming). When the term "base station" refers to multiple non-colocated physical TRPs, the physical TRPs may be a distributed antenna system (DAS) (e.g., a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (e.g., a remote base station connected to a serving base station). Alternatively, a non-colocated physical TRP may be a serving base station that receives measurement reports from a UE and a neighboring base station whose reference radio frequency (RF) signal (e.g., or simply "reference signal") the UE is measuring. Since a TRP is a point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station should be understood as referring to a particular TRP of the base station.

[0054]

[0069] In some implementations that support positioning of UEs, a network entity or base station may not support wireless access by the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but instead may transmit reference signals to the UE to be measured by the UE and / or may receive and measure signals transmitted by the UE. Such base stations may be referred to as positioning beacons (e.g., when they transmit signals to the UE) and / or location measurement units (e.g., when they receive and measure signals from the UE).

[0055]

[0070] An RF signal includes electromagnetic waves of a given frequency that carry information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, the receiver may receive multiple "RF signals" corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same RF signal transmitted over different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" when it is clear from the context that the term "signal" refers to a wireless signal or an RF signal.

[0056]

[0071] Various aspects of the systems and techniques described herein are discussed below with reference to the figures. According to various aspects, FIG. 1 illustrates an example of a wireless communication system 100. The wireless communication system 100 (e.g., may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 and various UEs 104. In some aspects, the base stations 102 may also be referred to as "network entities" or "network nodes." One or more of the base stations 102 may be implemented in an aggregated or monolithic base station architecture. Additionally or alternatively, one or more of the base stations 102 may be implemented in a non-aggregated base station architecture and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near-real-time (Near-RT) RAN intelligent controller (RIC), or a non-real-time (Non-RT) RIC. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macro cell base station may include eNBs and / or ng-eNBs where the wireless communication system 100 corresponds to a Long Term Evolution (LTE) network, or gNBs where the wireless communication system 100 corresponds to an NR network, or a combination of both, and the small cell base station may include femtocells, picocells, microcells, etc.

[0057]

[0072] The base stations 102 collectively form a RAN and may interface with a core network 170 (e.g., evolved packet core (EPC) or 5G core (5GC)) through the backhaul links 122 and to one or more location servers 172 through the core network 170 (which may be part of the core network 170 or external to the core network 170). In addition to other functions, the base stations 102 may perform functions related to one or more of forwarding user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, non-access stratum (NAS) message delivery, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracing, RAN information management (RIM), paging, positioning, and alert message delivery. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC or 5GC) via backhaul links 134, which may be wired and / or wireless.

[0058]

[0073] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more cells may be supported by the base stations 102 in each coverage area 110. A "cell" is a logical communication entity used to communicate with the base stations (e.g., over some frequency resources, referred to as a carrier frequency, component carrier, carrier, band, etc.) and may be associated with an identifier (e.g., a physical cell identifier (PCI), a virtual cell identifier (VCI), a cell global identifier (CGI)) to distinguish cells operating over the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access to different types of UEs. Because a cell is supported by a particular base station, the term "cell" may refer to either or both of the logical communication entity and the base station that supports it, depending on the context. In addition, because a TRP is typically the physical transmission point of a cell, the terms "cell" and "TRP" may be used interchangeably. In some cases, the term "cell" may also refer to the geographic coverage area (e.g., sector) of a base station, as long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.

[0059]

[0074] The geographic coverage areas 110 of neighboring macrocell base stations 102 may overlap partially (e.g., in handover regions), and some of the geographic coverage areas 110 may be significantly overlapped by larger geographic coverage areas 110. For example, a small cell base station 102' may have a coverage area 110' that significantly overlaps with the coverage area 110 of one or more macrocell base stations 102. A network including both small cell base stations and macrocell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may serve closed groups known as closed subscriber groups (CSGs).

[0060]

[0075] The communication link 120 between the base station 102 and the UE 104 may include uplink (e.g., also referred to as reverse link) transmissions from the UE 104 to the base station 102, and / or downlink (e.g., also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated for the downlink than for the uplink).

[0061]

[0076] The wireless communication system 100 may further include a WLAN AP 150 communicating with WLAN stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum (e.g., 5 gigahertz (GHz)). When communicating in the unlicensed frequency spectrum, the WLAN STAs 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure before communicating to determine if a channel is available. In some examples, the wireless communication system 100 may include devices (e.g., UEs, etc.) that communicate with one or more UEs 104, base stations 102, APs 150, etc. utilizing an ultra-wideband (UWB) spectrum. The UWB spectrum may range from 3.1 GHz to 10.5 GHz.

[0062]

[0077] The small cell base station 102' may operate in a licensed and / or unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum used by the WLAN AP 150. A small cell base station 102' employing LTE and / or 5G in an unlicensed frequency spectrum may extend coverage to and / or increase capacity of an access network. NR in an unlicensed spectrum may be referred to as NR-U. LTE in an unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MulteFire.

[0063]

[0078] The wireless communication system 100 may further include a mmW base station 180 that may operate at millimeter wave (mmW) and / or sub-mmW frequencies in communication with the UE 182. The mmW base station 180 may be implemented in an aggregated or monolithic base station architecture, or alternatively in a non-aggregated base station architecture (e.g., including one or more of a CU, DU, RU, Near-RT RIC, or Non-RT RIC). Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength of 1 millimeter to 10 millimeters. Radio waves in this band may be referred to as millimeter waves. Sub-mmW may go down to frequencies of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band ranges from 3 GHz to 30 GHz and is also referred to as centimeter wave. Communications using the mmW and / or sub-mmW radio frequency bands have high path loss and relatively short distances. The mmW base station 180 and the UE 182 may utilize (e.g., transmit and / or receive) beamforming over the mmW communication link 184 to compensate for the large path loss and short distance. Additionally, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or quasi-mmW and beamforming. Accordingly, it will be appreciated that the above illustrations are merely examples and should not be construed as limiting various aspects disclosed herein.

[0064]

[0079] In some aspects related to 5G, the frequency spectrum in which a wireless network node or entity (e.g., base station 102 / 180, UE 104 / 182) operates is divided into multiple frequency ranges: FR1 (e.g., 450-6000 Megahertz (MHz)), FR2 (e.g., 24250-52600 MHz), FR3 (e.g., above 52600 MHz), and FR4 (e.g., between FR1 and FR2). In a multi-carrier system such as 5G, one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells." In carrier aggregation, the anchor carrier is a carrier operating on a primary frequency (e.g., FR1) utilized by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carriers all carry common and UE-specific control channels and may (but are not always) be carriers among licensed frequencies. The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once an RRC connection is established between the UE 104 and the anchor carrier and may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier among unlicensed frequencies. Since both the primary uplink carrier and the primary downlink carrier are typically UE-specific, the secondary carrier may include only the necessary signaling information and signals, e.g., signaling information and signals that are UE-specific may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time.This may be done, for example, to balance the load on different carriers. Since a "serving cell" corresponds to a carrier frequency and / or component carrier over which several base stations are communicating (whether a PCell or an SCell, for example), the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. may be used interchangeably.

[0065]

[0080] For example, still referring to FIG. 1, one of the frequencies utilized by the macrocell base station 102 may be an anchor carrier (or “PCell”), and the other frequencies utilized by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers (“SCells”). In carrier aggregation, the base station 102 and / or the UE 104 may use spectrum with a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100 MHz) per carrier for a total of Yx MHz (e.g., x component carriers) for transmission in each direction. The component carriers may or may not be adjacent to each other in the frequency spectrum. The allocation of carriers may be asymmetric for the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink rather than the uplink). The simultaneous transmission and / or reception of multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, two 20 MHz carriers aggregated in a multi-carrier system would theoretically provide a two-fold increase in data rate (e.g., 40 MHz) compared to the data rate achieved by a single 20 MHz carrier.

[0066]

[0081] To operate on multiple carrier frequencies, the base station 102 and / or the UE 104 may include multiple receivers and / or transmitters. For example, the UE 104 may have two receivers, "receiver 1" and "receiver 2", where "receiver 1" is a multi-band receiver that can be tuned to band (e.g., carrier frequency) "X" or band "Y", and "receiver 2" is a one-band receiver that can only be tuned to band "Z". In this example, if the UE 104 is served in band "X", band "X" would be referred to as a PCell or active carrier frequency, and "receiver 1" would need to tune from band "X" to band "Y" (e.g., SCell) (and vice versa) to measure band "Y". In contrast, regardless of whether the UE 104 is served in band "X" or band "Y", the UE 104 can measure band "Z" without interrupting service on band "X" or band "Y" because there is a separate "receiver 2".

[0067]

[0082] The wireless communications system 100 may further include a UE 164, which may communicate with the macrocell base station 102 via communications link 120 and / or with the mmW base station 180 via an mmW communications link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0068]

[0083] The wireless communication system 100 may further include one or more UEs, such as a UE 190, that indirectly connect to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (e.g., sometimes referred to as "sidelinks"). In the example of FIG. 1, the UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which the UE 190 may indirectly obtain cellular connectivity), and a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (e.g., through which the UE 190 may indirectly obtain WLAN-based Internet connectivity). In one example, the D2D P2P links 192 and 194 may be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), Wi-Fi Direct (Wi-Fi-D), Bluetooth®, etc.

[0069]

[0084] 2 shows a block diagram of a design of a base station 102 and a UE 104 that enables transmission and processing of signals exchanged between the UE and the base station in accordance with some aspects of the disclosure. The design 200 includes components of a base station 102, which may be one of the base stations 102 in FIG. 1, and a UE 104, which may be one of the UEs 104 in FIG. 1. The base station 102 may be equipped with T antennas 234a through 234t, and the UE 104 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0070]

[0085] At the base station 102, a transmit processor 220 may receive data for one or more UEs from a data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., code and modulate) the data for each UE based at least in part on the selected MCS(es) for the UE, and provide data symbols to all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, higher layer signaling, etc.) and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for a reference signal (e.g., a cell-specific reference signal (CRS)) and a synchronization signal (e.g., a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. The modulators 232a through 232t are shown as combined modulator-demodulators (MOD-DEMOD). In some cases, the modulators and demodulators may be separate components. Each modulator of the modulators 232a through 232t may process a respective output symbol stream, such as for an orthogonal frequency division multiplexing (OFDM) scheme, to obtain an output sample stream.Each modulator 232a-t may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals may be transmitted from modulators 232a-t via T antennas 234a-t, respectively. According to some aspects described in more detail below, synchronization signals may be generated using location coding to convey additional information.

[0071]

[0086] At the UE 104, the antennas 252a-252r may receive downlink signals from the base station 102 and / or other base stations and may provide received signals to the demodulators (DEMODs) 254a-254r, respectively. The demodulators 254a-254r are shown as combined modulator-demodulators (MOD-DEMOD). In some cases, the modulator and demodulator may be separate components. Each demodulator of the demodulators 254a-254r may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator of the demodulators 254a-254r may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a-254r, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 260, and provide decoded control and system information to the controller / processor 280. The channel processor may determine the reference signal received power (RSRP), a received signal strength indicator (RSSI), a reference signal received quality (RSRQ), a channel quality indicator (CQI), etc.

[0072]

[0087] On the uplink, at the UE 104, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 may also generate reference symbols for one or more reference signals (e.g., based at least in part on a beta value or set of beta values ​​associated with the one or more reference signals). The symbols from the transmit processor 264 may be precoded by a TX-MIMO processor 266, further processed by modulators 254a-254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 102, if applicable. At the base station 102, uplink signals from the UE 104 and other UEs may be received by antennas 234a-t, processed by demodulators 232a-t, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 104. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller (e.g., processor) 240. The base station 102 may include a communication unit 244 and communicate to the network controller 231 via the communication unit 244. The network controller 231 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0073]

[0088] In some aspects, one or more components of the UE 104 may be included within a housing. The controller 240 of the base station 102, the controller / processor 280 of the UE 104, and / or any other component(s) of FIG. 2 may implement one or more techniques associated with determining an implicit UCI beta value for NR.

[0074]

[0089] The memories 242 and 282 may store data and program codes for the base station 102 and the UE 104, respectively. The scheduler 246 may schedule UEs for data transmission on the downlink, uplink, and / or sidelink.

[0075]

[0090] In some aspects, the deployment of a communication system such as a 5G New Radio (NR) system may be configured in multiple ways with various components or parts. In a 5G NR system, or network, a network node, network entity, mobility element of the network, Radio Access Network (RAN) node, core network node, network element, or network equipment such as a base station (BS), or one or more units (or one or more components) performing a base station function may be implemented in an aggregated or non-aggregated architecture. For example, a BS (e.g., a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) may be implemented as an aggregated base station (also known as a standalone BS or monolithic BS) or a non-aggregated base station.

[0076]

[0091] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A non-aggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (e.g., one or more centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU or alternatively distributed geographically or virtually across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0077]

[0092] The operation of a base station type or network design may take into account the aggregation characteristics of the base station functions. For example, a disaggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (e.g., a network configuration supported by the O-RAN alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functions across two or more units in various physical locations, as well as distributing functions virtually for at least one unit, which may allow flexibility in network design. Various units of a disaggregated base station, or a disaggregated RAN architecture, may be configured for wired or wireless communication with at least one other unit.

[0078]

[0093] 3 shows a diagram illustrating an example disaggregated base station 300 architecture. The disaggregated base station 300 architecture may include one or more central units (CUs) 310 that may communicate directly with the core network 320 via a backhaul link or indirectly with the core network 320 through one or more disaggregated base station units (e.g., a Near-RT RAN Intelligent Controller (RIC) 325 via an E2 link, or a Non-RT RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more distributed units (DUs) 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more radio units (RUs) 340 via respective fronthaul links. The RU 340 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be served by multiple RUs 340 simultaneously.

[0079]

[0094] Each of the units, e.g., CU310, DU330, RU340, and Near-RT RIC325, Non-RT RIC315, and SMO framework 305, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units over a transmission medium. For example, the units may include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Furthermore, the units may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., a radio frequency (RF) transceiver, etc.) configured to receive or transmit or transmit signals over a wireless transmission medium to one or more of the other units.

[0080]

[0095] In some aspects, the CU 310 may host one or more upper layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functions (e.g., Central Unit - User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP unit, when implemented in an O-RAN configuration, may communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface. The CU 310 may be implemented to communicate with the DU 330, as necessary, for network control and signaling.

[0081]

[0096] The DU 330 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (e.g., modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.), at least in part according to a functional division such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 330 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with a control function hosted by the CU 310.

[0082]

[0097] The lower layer functions may be implemented by one or more RUs 340. In some deployments, the RUs 340 controlled by the DUs 330 may correspond to logical nodes hosting RF processing functions, or lower PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional division such as a lower layer functional division. In such an architecture, the RU(s) 340 may be implemented to handle over the air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU(s) 340 may be controlled by the corresponding DUs 330. In some scenarios, this configuration may enable the DU(s) 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0083]

[0098] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support deployment of dedicated physical resources for RAN coverage requirements that can be managed via an operation and maintenance interface (e.g., an O1 interface, etc.). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (e.g., an open cloud (O-Cloud) 390, etc.) to perform network element lifecycle management (e.g., instantiate virtualized network elements, etc.) via a cloud computing platform interface (e.g., an O2 interface, etc.). Such virtualized network elements may include, but are not limited to, the CU 310, the DU 330, the RU 340, and the Near-RT RIC 325. In some implementations, the SMO framework 305 may communicate with hardware aspects of a 4G RAN, such as the open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via an O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0084]

[0099] The Non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 325. The Non-RT RIC 315 may be coupled to the Near-RT RIC 325 or may communicate with the Near-RT RIC 325 (e.g., via an A1 interface). The Near-RT RIC 325 may be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources by data collection and action over interfaces (e.g., via an E2 interface) that connect one or more CUs 310, one or more DUs 330, or both, and O-eNBs to the Near-RT RIC 325.

[0085]

[0100] In some implementations, the Non-RT RIC 315 may receive parameters or external enrichment information from an external server to generate the AI / ML models to be deployed to the Near-RT RIC 325. Such information may be utilized by the Near-RT RIC 325 and may be received from non-network data sources or from network functions in the SMO framework 305 or the Non-RT RIC 315. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to adjust RAN behavior or performance. For example, the Non-RT RIC 315 may employ the AI / ML models to monitor long-term trends and patterns in performance and implement corrective actions through the SMO framework 305 (e.g., reconfiguration via O1, etc.) or through the creation of RAN management policies (e.g., A1 policies, etc.).

[0086]

[0101] 4 illustrates an example of a computing system 470 of a wireless device 407. The wireless device 407 may include a client device such as a UE (e.g., UE 104, UE 152, UE 190) or other type of device (e.g., a station (STA) configured to communicate using a Wi-Fi interface) that may be used by an end user. For example, the wireless device 407 may include a mobile phone, a router, a tablet computer, a laptop computer, a tracking device, a wearable device (e.g., an extended reality (XR) device such as a smart watch, glasses, a virtual reality (VR), an augmented reality (AR), or a mixed reality (MR) device), an Internet of Things (IoT) device, a vehicle, an aircraft, and / or another device configured to communicate over a wireless communication network. The computing system 470 includes software and hardware components that may be electrically or communicatively coupled (or may be otherwise in communication, as appropriate) via a bus 489. For example, the computing system 470 includes one or more processors 484. The one or more processors 484 may include one or more CPUs, ASICs, FPGAs, APs, GPUs, VPUs, NSPs, microcontrollers, special purpose hardware, any combination thereof, and / or other processing devices or systems. A bus 489 may be used by the one or more processors 484 to communicate between cores and / or with one or more memory devices 486.

[0087]

[0102] The computing system 470 may also include one or more memory devices 486, one or more digital signal processors (DSPs) 482, one or more SIMs 474, one or more modems 476, one or more wireless transceivers 478, an antenna 487, one or more input devices 472 (e.g., a camera, a mouse, a keyboard, a touch-sensitive screen, a touchpad, a keypad, a microphone, etc.), and one or more output devices 480 (e.g., a display, a speaker, a printer, etc.).

[0088]

[0103] In some aspects, the computing system 470 may include one or more radio frequency (RF) interfaces configured to transmit and / or receive RF signals. In some examples, the RF interface may include components such as modem(s) 476, wireless transceiver(s) 478, and / or antenna 487. The one or more wireless transceivers 478 may transmit and receive wireless signals (e.g., signals 488) via antenna 487 from one or more other devices, such as other wireless devices, network devices (e.g., base stations such as eNBs and / or gNBs, Wi-Fi access points (APs) such as routers, range extenders, etc.), cloud networks, etc. In some examples, the computing system 470 may include multiple antennas or antenna arrays that may facilitate simultaneous transmit and receive capabilities. The antenna 487 may be an omni-directional antenna such that radio frequency (RF) signals may be received from and transmitted in all directions. The wireless signals 488 may be transmitted over a wireless network. The wireless network may be any wireless network, such as a cellular or telecommunications network (e.g., 3G, 4G, 5G, etc.), a wireless local area network (e.g., a Wi-Fi network), a Bluetooth™ network, and / or other network.

[0089]

[0104] In some examples, the wireless signals 488 may be transmitted directly to other wireless devices using sidelink communication (e.g., using a PC5 interface, using a DSRC interface, etc.). The wireless transceiver 478 may be configured to transmit RF signals for conducting sidelink communication via the antenna 487 in accordance with one or more transmit power parameters that may be associated with one or more coordination modes. The wireless transceiver 478 may also be configured to receive sidelink communication signals having different signal parameters from other wireless devices.

[0090]

[0105] In some examples, the one or more wireless transceivers 478 may include an RF front end that includes one or more components such as an amplifier, a mixer (also called a signal multiplier) for signal downconversion, a frequency synthesizer (also called an oscillator) that provides a signal to the mixer, a baseband filter, an analog-to-digital converter (ADC), one or more power amplifiers, among other components. The RF front end may generally handle the selection of the wireless signal 488 and its conversion to a baseband or intermediate frequency, and may convert the RF signal to the digital domain.

[0091]

[0106] In some cases, computing system 470 may include a coding-decoding device (or CODEC) configured to encode and / or decode data transmitted and / or received using one or more wireless transceivers 478. In some cases, computing system 470 may include an encryption-decryption device or component configured to encrypt and / or decrypt data transmitted and / or received by one or more wireless transceivers 478 (e.g., according to the AES and / or DES standards).

[0092]

[0107] Each of the one or more SIMs 474 may securely store an international mobile subscriber identity (IMSI) number and associated keys assigned to a user of the wireless device 407. The IMSI and keys may be used to identify and authenticate a subscriber when accessing a network provided by a network service provider or operator associated with the one or more SIMs 474. The one or more modems 476 may modulate one or more signals to encode information for transmission using the one or more wireless transceivers 478. The one or more modems 476 may also demodulate signals received by the one or more wireless transceivers 478 to decode the transmitted information. In some examples, the one or more modems 476 may include a Wi-Fi modem, a 4G (or LTE) modem, a 5G (or NR) modem, and / or other types of modems. The one or more modems 476 and the one or more wireless transceivers 478 may be used to communicate data for the one or more SIMs 474.

[0093]

[0108] The computing system 470 may also include (and / or be in communication with) one or more non-transitory machine-readable storage media or storage devices (e.g., one or more memory devices 486), which may include, but are not limited to, local and / or network-accessible storage, disk drives, drive arrays, optical storage devices, solid-state storage devices such as RAM and / or ROM, which may be programmable, flash-updateable, etc. Such storage devices may be configured to implement any suitable data storage system, including, but not limited to, various file systems, database structures, etc.

[0094]

[0109] In various aspects, functions may be stored as one or more computer program products (e.g., instructions or code) in memory device(s) 486 and executed by one or more processor(s) 484 and / or one or more DSPs 482. Computing system 470 may also include software elements (e.g., in one or more memory devices 486) including, for example, an operating system, device drivers, executable libraries, and / or other code, such as one or more application programs, which may include computer programs that implement functions provided by various aspects and / or may be designed to implement methods and / or configure systems described herein.

[0095]

[0110] In some aspects, the wireless device 407 (e.g., a UE) may include means for performing the operations described herein. The means may include one or more of the components of the computing system 470. For example, the means for performing the operations described herein may include one or more of the input device(s) 472, the SIM(s) 474, the modem(s) 476, the wireless transceiver(s) 478, the output device(s) (480), the DSP(s) 482, the processor (484), the memory device(s) 486, and / or the antenna(s) 487.

[0096]

[0111] In some aspects, the UE 407 may include means for receiving a downlink transmission in a first downlink timeslot and a scheduling offset (e.g., K offset For example, the update may include means for receiving an update to an updated scheduling offset (e.g., an updated K offset) In some aspects, the UE 407 may further include means for transmitting an uplink transmission associated with the downlink transmission using a second uplink timeslot, where the second uplink timeslot is determined based on the first uplink timeslot and the selected scheduling offset. In some aspects, the UE 407 may further include means for determining the selected scheduling offset as one of the scheduling offset or the updated scheduling offset.

[0097]

[0112] In some examples, the receiving means may include one or more wireless transceivers 478, one or more modems 476, one or more SIMs 474, one or more processors 484, one or more DSPs 482, one or more memory devices 486, any combination thereof, or other component(s) of the client device. In some examples, the determining means may include one or more processors 484, one or more DSPs 482, one or more memory devices 486, any combination thereof, or other component(s) of the client device. In some examples, the transmitting means may include one or more wireless transceivers 478, one or more modems 476, one or more SIMs 474, one or more processors 484, one or more DSPs 482, one or more memory devices 486, any combination thereof, or other component(s) of the client device.

[0098]

[0113] FIG. 5A provides a generalized illustration of various components, any or all of which may be utilized as appropriate, and each of which may be duplicated or omitted as necessary. While the example of FIG. 5A includes one UE 505, it should be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the network architecture 500. Similarly, the network architecture 500 may include a greater (or lesser) number of non-terrestrial network (NTN) devices, NTN gateways, base stations, RANs, core networks, and / or other components. The connections shown connecting the various components in the network architecture 500 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Additionally, the components may be rearranged, combined, separated, substituted, and / or omitted depending on the desired functionality.

[0099]

[0114] The UE 505 may be configured to communicate with the core network 510 via the NTN device 502, the NTN gateway 504, and the base station 506. As indicated by the RAN 512, one or more RANs associated with the core network 510 may include one or more base stations. Access to the network may be provided to the UE 505 via wireless communication between the UE 505 and the base station 506 (e.g., a serving base station) via the NTN device 502 and the NTN gateway 504. The base station 506 may provide wireless communication access to the core network 510 on behalf of the UE 505, for example, using 5G NR.

[0100]

[0115] The base station 506 may be referred to by other names such as network entity, gNB, base station, network node, "satellite node", satellite NodeB (sNB), "satellite access node", etc. The base station 506 may not be the same as a terrestrial network gNB, but may be based on a terrestrial network gNB with additional capabilities. For example, the base station 506 may terminate the air interface and associated air interface protocols to the UE 505 via the NTN device 502 and the NTN gateway 504, and may transmit DL signals to the UE 505 and receive UL signals from the UE 505. The base station 506 may also support signaling connections and voice and data bearers to the UE 505, and may support handover of the UE 505 between different radio cells for the NTN device 502, between different NTN devices, and / or between different base stations. The base station 506 may be configured to manage mobile radio beams (e.g., for aircraft and / or non-stationary (non-GEO) devices) and associated mobility of the UE 505. The base station 506 may assist in handover (or transfer) of the NTN device 502 between different NTN gateways or different base stations. In some examples, the base station 506 may be separate from the NTN gateway 504, for example, as shown in the example of FIG. 5A. In other examples, the base station 506 may include one or more NTN gateways or may be combined with one or more NTN gateways, for example, using a split architecture. For example, in a split architecture, the base station 506 may include a central unit (CU) and the NTN gateway 504 may include or act as a distributed unit (DU). The base station 506 may be fixed to the ground with a transparent payload operation. In one implementation, the base station 506 may be physically combined with or physically connected to the NTN gateway 504 to reduce complexity and cost.

[0101]

[0116] The NTN gateway 504 may be shared by two or more base stations and may communicate with the UE 505 via the NTN device 502. The NTN gateway 504 may be dedicated to one associated constellation of the NTN device. The NTN gateway 504 may be included within the base station 506, for example as a base station DU within the base station 506. The NTN gateway 504 may communicate with the NTN device 502 using control and user plane protocols. The control and user plane protocols between the NTN gateway 504 and the NTN device 502 may (i) establish and release communication links from the NTN gateway 504 to the NTN device 502, including authentication and encryption, (ii) update the NTN device software and firmware, (iii) perform operations and maintenance (O&M) of the NTN device, (iv) control radio beams (e.g., direction, power, on / off status) and mapping between radio beams and the NTN gateway UL and DL payloads, and / or (v) support handoff of the NTN device 502 or radio cell to another NTN gateway.

[0102]

[0117] Support of transparent payloads by the network architecture 500 shown in FIG. 5A may impact the communication system as follows: The core network 510 may treat the satellite RAT as a new type of RAT with longer delay, reduced bandwidth, and / or higher error rate. As a result, there may be some impact on PDU session establishment and mobility management (MM) and connection management (CM) procedures. The NTN device 502 may be shared with other services (e.g., satellite TV, fixed Internet access) with 5G NR mobile access for transparently added UEs. This may allow legacy NTN devices to be used and may avoid the need to deploy new types of NTN devices. The base station 506 may assist in the allocation and transfer of the NTN device 502 and radio cells between the base station 506 and the NTN gateway 504, and may support handover of the UE 505 between radio cells, between NTN devices, and between other base stations. Thus, the base station 506 may be different from the terrestrial network gNB. Additionally, the coverage area of ​​the base station 506 may be much larger than the coverage area of ​​a terrestrial network base station.

[0103]

[0118] In the illustrated example of FIG. 5A, the service link 520 may facilitate communication between the UE 505 and the NTN device 502, the feeder link 522 may facilitate communication between the NTN device 502 and the NTN gateway 504, and the interface 524 may facilitate communication between the base station 506 and the core network 510. The service link 520 and the feeder link 522 may be implemented by the same radio interface (e.g., the NR-Uu interface). The interface 524 may be implemented by an NG interface.

[0104]

[0119] FIG. 5B illustrates a diagram of a network architecture 525 capable of supporting NTN access (e.g., using 5G NR). The network architecture 525 illustrated in FIG. 5B is similar to that illustrated in FIG. 5A, and similarly designated elements are similar or identical. However, FIG. 5B illustrates a network architecture with a regenerated payload, as opposed to the transparent payload illustrated in FIG. 5A. Unlike the transparent payload, the regenerated payload includes an on-board base station (e.g., includes the functional capabilities of a base station) and is referred to herein as an NTN device 502 / base station. The RAN 512 is illustrated as including an NTN device 502 / base station. Reference to an NTN device 502 / base station may refer to functions related to communication with the UE 505 and the core network 510, and / or functions related to communication with the NTN gateway 504 and the UE 505 at the physical radio frequency level.

[0105]

[0120] The on-board base station may perform many of the same functions as the base station 506 described above. For example, the NTN device 502 / base station may terminate the air interface and associated air interface protocols to the UE 505, transmit DL signals to the UE 505, and receive UL signals from the UE 505, which may include encoding and modulating transmitted signals and demodulating and decoding received signals. The NTN device 502 / base station may also support signaling connections and voice and data bearers to the UE 505, and may support handover of the UE 505 between different radio cells for the NTN device 502 / base station, and between or among different NTN devices / base stations. The NTN device 502 / base station may assist in handover (or transfer) of the UE 505 between different NTN gateways and different control networks. The NTN device 502 / base station may hide or mask certain aspects of the NTN device 502 / base station from the core network 510 (e.g., by interfacing to the core network 510 in the same or similar manner as a terrestrial network base station). The NTN device 502 / base station may further support sharing of the NTN device 502 / base station. The NTN device 502 / base station may communicate with one or more NTN gateways and one or more core networks via the NTN gateway 504. In some aspects, the NTN device 502 / base station may communicate directly with other NTN devices / base stations using Inter-Satellite Links (ISLs), which may support an Xn interface between any pair of NTN devices / base stations.

[0106]

[0121] With low Earth orbit (LEO) devices, the NTN device 502 / base station may manage mobile radio cells with coverage at different times. The NTN gateway 504 may be directly connected to the core network 510 as shown. The NTN gateway 504 may be shared by multiple core networks, for example, if the NTN gateway is limited. In some examples, the core network 510 may need to know the coverage area(s) of the NTN device 502 / base station to page the UE 505 and manage handovers. Thus, as can be seen, the network architecture 525 with regenerative payloads may have more impact and complexity with respect to both the NTN device 502 / base station and the core network 510 than the network architecture 500 including transparent payloads as shown in FIG. 5A.

[0107]

[0122] Support of regenerative payloads by the network architecture 525 shown in FIG. 5B may impact the network architecture 525 as follows: If fixed tracking areas and fixed cells are not supported, the core network 510 may be impacted, since the core components of the fixed cell and fixed tracking area based mobility management and restriction services for terrestrial PLMNs may be replaced by new systems (e.g., based on the location of the UE 505). If fixed tracking areas and fixed cells are supported, the core network 510 may map any fixed tracking area to one or more NTN devices / base stations that have current radio coverage of the fixed tracking area when performing paging of the UE 505 located within this fixed tracking area. This may include configuration in the core network 510 of long-term orbit data for the NTN device 502 / base station (e.g., obtained from the operator of the NTN device 502 / base station) and may add significant new impacts to the core network 510.

[0108]

[0123] In the illustrated example of FIG. 5B, the service link 520 may facilitate communication between the UE 505 and the NTN device 502 / base station, the feeder link 522 may facilitate communication between the NTN device 502 / base station and the NTN gateway 504, and the interface 524 may facilitate communication between the NTN gateway 504 and the core network 510. The service link 520 may be implemented by an NR-Uu interface. The feeder link 522 may be implemented by an NG interface over the SRI. The interface 524 may be implemented by an NG interface.

[0109]

[0124] FIG. 5C is a diagram of a network architecture 550 capable of supporting NTN access (e.g., using 5G NR). The network architecture shown in FIG. 5C is similar to that shown in FIG. 5A and FIG. 5B, and similarly designated elements are similar or identical. However, FIG. 5C illustrates a network architecture with a regenerative payload and a split architecture for base stations, as opposed to a transparent payload as shown in FIG. 5A. For example, a base station may be split between a central unit (CU) and a distributed unit (DU). In the illustrated example of FIG. 5C, the network architecture 550 includes an NTN-CU 516, which may be a ground-based base station or a terrestrial base station. The regenerative payload includes an on-board base station DU, referred to herein as an NTN-DU 514. The NTN-CU 516 and the NTN-DU 514, collectively or individually, may correspond to a network node associated with the base station 310 of FIG. 3.

[0110]

[0125] The NTN-DU 514 communicates with the NTN-CU 516 via the NTN gateway 504. The NTN-CU 516 together with the NTN-DU 514 may perform functions and use internal communication protocols similar or identical to those of a gNB with a split architecture. In this example, the NTN-DU 514 may correspond to and perform similar or identical functions as a gNB distributed unit (gNB-DU), while the NTN-CU 516 may correspond to and perform similar or identical functions as a gNB central unit (gNB-CU). However, the NTN-CU 516 and NTN-DU 514 may each include additional capabilities to support UE 505 access using NTN devices.

[0111]

[0126] The NTN-DU 514 and NTN-CU 516 may communicate with each other using the F1 Application Protocol (F1AP) and may together perform some or all of the same functions as the base station 506 or the NTN device 502 / base station as described in connection with FIG. 5B and FIG. 5C, respectively. The NTN-DU 514 may terminate the air interface to the UE 505 and associated lower level air interface protocols, and may transmit DL signals to the UE 505 and receive UL signals from the UE 505, which may include encoding and modulation of transmitted signals and demodulation and decoding of received signals. The operation of the NTN-DU 514 may be partially controlled by the NTN-CU 516. The NTN-DU 514 may support one or more NR radio cells for the UE 505. The NTN-CU 516 may also be divided into separate control plane (CP) (NTN-CU-CP) and user plane (UP) (NTN-CU-UP) parts. The NTN-DU 514 and NTN-CU 516 may communicate over the F1 interface to support (a) control plane signaling for the UE 505 using IP, Stream Control Transmission Protocol (SCTP), and F1 Application Protocol (F1AP) protocols, and (b) user plane data transfer for the UE using IP, User Datagram Protocol (UDP), PDCP, SDAP, GTP-U, and NR User Plane Protocol (NRUPP) protocols.

[0112]

[0127] The NTN-CU 516 may communicate with one or more other NTN-CUs and / or one or more other terrestrial base stations using terrestrial links to support the Xn interface between any pair of NTN-CUs and / or between the NTN-CU 516 and any terrestrial base station. The NTN-DU 514, together with the NTN-CU 516, may (i) support signaling connections and voice and data bearers to the UE 505, (ii) support handover of the UE 505 between different radio cells for the NTN-DU 514 and between different NTN-DUs, and (iii) assist handover (or transfer) of NTN devices between different NTN gateways or different core networks. The NTN-CU 516 may hide or mask certain aspects of the NTN devices from the core network 510 (e.g., by interfacing to the core network 510 in the same or similar manner as a terrestrial network base station).

[0113]

[0128] In the network architecture 550 of FIG. 5C, the NTN-DU 514 that communicates with and is accessible from the NTN-CU may change over time with the LEO device. With a split base station architecture, the core network 510 may connect to a fixed, time-invariant NTN-CU, which may reduce difficulties with paging the UE 505. For example, the core network 510 may not need to know the NTN-DU required to page the UE 505. A network architecture with regenerative payloads with a split base station architecture may thereby reduce the impact of the core network 510 at the expense of additional impact on the NTN-CU 516.

[0114]

[0129] As shown in FIG. 5C, the support of regenerated payloads with a split base station architecture may affect the network architecture 550 as follows: The impact on the core network 510 may be limited with respect to the transparent payloads (e.g., NTN device 502) discussed above. For example, the core network 510 may treat the satellite RAT in the network architecture 550 as a new type of RAT with longer delay, reduced bandwidth, and / or higher error rate. The impact on the NTN-DU 514 may be less than the impact on the NTN device / base station (e.g., NTN device 502 / base station with a non-split architecture) as discussed above with reference to FIG. 5B. The NTN-DU 514 may manage the change of association with different (fixed) NTN-CUs. Furthermore, the NTN-DU 514 may manage radio beams and radio cells. The impact of the NTN-CU 516 may be similar to that of the base station 506 for a network architecture with transparent payloads, as discussed above, except for the extra impact to manage association changes with different NTN-DUs and reduced impact to support radio cells and radio beams that may be forwarded to the NTN-DU 514. In some aspects, the NTN device may correspond to a high altitude platform system (HAPS) that serves one or more UEs on the ground.

[0115]

[0130] One or more satellites may be integrated with the terrestrial infrastructure of the wireless communications system. A satellite may refer to a Low Earth Orbit (LEO), Medium Earth Orbit (MEO), Geostationary Earth Orbit (GEO), and / or Highly Elliptical Orbit (HEO) device. A Non-Terrestrial Network (NTN) may refer to a network or a segment of a network that uses aircraft or spacecraft for transmission. An aircraft may refer to High Altitude Platforms (HAPs), including Unmanned Aircraft Systems (UAS).

[0116]

[0131] NTNs may be configured to help provide wireless communications in unserved or underserved areas to upgrade the performance of terrestrial networks. For example, communication satellites may provide coverage to a larger geographic area than TN base stations. NTNs may also enhance service reliability by providing service continuity to UEs or mobile platforms (e.g., passenger vehicles - passenger aircraft, ships, high-speed trains, buses). NTNs may also improve service availability, including critical communications. NTNs may also enable network scalability through the provision of efficient multicast / broadcast resources for data delivery towards the network edge or even directly to user equipment.

[0117]

[0132] FIG. 6 illustrates an example of an NTN 600 configuration. An NTN may refer to a network or a segment of a network that uses RF resources onboard an NTN platform. An NTN platform may refer to a spacecraft or an aircraft. A spacecraft includes a communication satellite, which may be classified based on its orbit. For example, a communication satellite may include a GEO device that appears geostationary relative to the Earth. Thus, a single GEO device may provide coverage to a geographic coverage area. In other examples, a communication satellite may include a non-GEO device, such as a LEO device, a MEO device, or a HEO device. A non-GEO device does not appear geostationary relative to the Earth. Thus, a satellite constellation (e.g., one or more satellites) may be configured to provide coverage to a geographic coverage area. Aircraft may refer to systems including Tethered UAS (TUA), Lighter Than Air UAS (LTA), and Heavier Than Air UAS (HTA) (e.g., at altitudes typically between 8-50 km, including High Altitude Platforms (HAPs)).

[0118]

[0133] In some aspects, the NTN 600 may include an NR-NTN. The example of FIG. 6 provides that the NTN 600 may include a first NTN device 602, a second NTN device 604, a third NTN device 606, an NTN gateway 608, a data network 610, and a UE 630 within cell coverage of the first NTN device 602. In some aspects, the UE 630 may include an IoT device, and the UE may be connected to the NTN 600 for wireless communication.

[0119]

[0134] The NTN gateway 608 may be one of one or more NTN gateways that may connect the NTN 600 to a public data network. In some examples, the NTN gateway 608 may support functionality for forwarding signals from the NTN device to a Uu interface, such as an NR-Uu interface. In other examples, the NTN gateway 608 may provide a transport network layer node and support a transport protocol, such as operating as an IP router. A satellite radio interface (SRI) may provide an IP trunk connection between the NTN gateway 608 and the NTN device, carrying an NG interface or an F1 interface, respectively. One or more geosynchronous equatorial orbit (GEO) devices (e.g., which may be referred to herein as a first NTN device 602, a second NTN device 604, or a third NTN device 606) may be fed by the NTN gateway 608, and one or more NTN devices may be deployed across a satellite target coverage that may correspond to regional or even continental coverage. A non-GEO device may be served sequentially by one or more NTN gateways at a time, and the NTN 600 may be configured to provide service and feeder link continuity between successive serving NTN gateways with duration to perform mobility anchoring and handover.

[0120]

[0135] A first NTN device 602, including a spacecraft or aircraft, may communicate with a data network 610 through a feeder link 612 established between the first NTN device 602 and an NTN gateway 608 to provide services to a UE 630 within the cell coverage or field of view of the NTN cell 620 of the first NTN device 602 via a service link 614. The feeder link 612 may include a wireless link between the NTN gateway and the NTN device. The service link 614 may refer to a radio link between an NTN device (e.g., the first NTN device 602) and the UE 630. In some examples, the first NTN device 602 may use one or more directional beams (e.g., beamforming) to exchange communications with the UE 630. A beam may refer to a wireless communication beam generated by an antenna mounted on the NTN device.

[0121]

[0136] In some examples, the UE 630 may communicate with the first NTN device 602 via a service link 614. The second NTN device 604 may relay communications for the first NTN device 602 through an inter-satellite link (ISL) 616, and the second NTN device 604 may communicate with the data network 610 through a feeder link 612 established between the second NTN device 604 and an NTN gateway 608. The ISL link may be provided between a constellation of satellites and may include the use of a transparent payload onboard the NTN device. The ISL may operate in RF frequencies or optical bands.

[0122]

[0137] In the illustrated example of FIG. 6, the first NTN device 602 may provide a first physical cell ID (PCI) ("PCI1") to the NTN cell 620. In some examples, a constellation of satellites may provide coverage to the NTN cell 620. For example, the first NTN device 602 may include a non-GEO device that does not appear to be stationary relative to the Earth. Therefore, the satellite constellation (e.g., one or more satellites) may be configured to provide coverage to the NTN cell 620. For example, the first NTN device 602 and the third NTN device 606 may be part of a satellite constellation that provides coverage to the NTN cell 620.

[0123]

[0138] In some examples, NTN deployments may provide different services based on the type of payload carried by the NTN device. The type of payload may determine whether the NTN device operates as a relay node or a base station. For example, a transport payload may implement frequency conversion and radio frequency (RF) amplifiers in both the uplink (UL) and downlink (DL) directions and may correspond to an analog RF repeater. A transparent payload may, for example, receive UL signals from all served UEs and redirect the combined signal DL to an earth station without demodulating or decoding the signal. Similarly, a transparent payload may receive UL signals from an earth station and redirect the signal DL to a served UE without demodulating or decoding the signal. However, a transparent payload may frequency convert the received signal and amplify and / or filter the received signal before transmitting the signal.

[0124]

[0139] As mentioned above, in some examples, one or more of eMTC and / or NB-IoT may be implemented using an NTN network (e.g., also referred to as "eMTC over NTN" and "NB-IoT over NTN", respectively). In some cases, when an eMTC or NB-IoT over NTN implementation includes one or more feedback-enabled HARQ processes, HARQ stalls may occur (e.g., based on a relatively long RTT between a UE and a base station associated with eMTC over NTN and / or NB-IoT over NTN network). The systems and techniques described herein may be used to implement multi-TB scheduling of feedback-enabled HARQ processes and feedback-disabled HARQ processes. For example, the systems and techniques may be used to implement multi-TB scheduling of feedback-enabled HARQ processes and feedback-disabled HARQ processes in eMTC over NTN and / or NB-IoT over NTN, as described in more detail below.

[0125]

[0140] 7A and 7B are diagrams illustrating an example of multi-TB scheduling. For example, FIG. 7A illustrates an example multi-TB scheduled block 710 including only feedback-enabled HARQ processes 1-8 (e.g., shown as unshaded squares). FIG. 7B illustrates an example multi-TB scheduled block 720 including only feedback-disabled HARQ processes 1-8 (e.g., shown as shaded squares). As illustrated, the multi-TB scheduled blocks 710 and 720 each include a total of eight HARQ processes. Each HARQ process may be used to transmit (e.g., from a base station or NTN node to a UE) and / or receive (e.g., by a UE) a transport block (TB). In some cases, the example multi-TB scheduled blocks 710 and 720 may include a greater or lesser number of HARQ processes (and may be associated with a greater or lesser number of TBs, e.g., carried on or associated with a HARQ process). For example, in an NB-IoT over NTN network, the multi-TB scheduled blocks 710 and 720 may include up to two HARQ processes, up to four HARQ processes, etc. In one illustrative example, the multi-TB scheduled blocks 710 and 720 may be associated with an eMTC on an NTN network, where up to eight TBs (e.g., up to eight HARQ processes) may be scheduled in the multi-TB scheduled blocks. In one illustrative example, the multi-TB scheduled blocks may be scheduled or otherwise based on downlink control information (DCI). In some cases, the multi-TB scheduled blocks may be scheduled based on or using a single DCI.In some aspects, a multi-TB scheduled block may be scheduled by a DCI transmitted using a PDCCH, and the TBs associated with the multi-TB scheduled block may be transmitted using a PDSCH (e.g., the eight TBs 1-8 included in the example multi-TB scheduled blocks 710 and 720 may be transmitted using a PDSCH).

[0126]

[0141] In some aspects, the exemplary multi-TB scheduled blocks (e.g., 710, 720) may be received using a downlink interface associated with the UE. For example, the multi-TB scheduled blocks 710 and 720 may be transmitted from a base station or NTN node and received using a downlink interface associated with the UE. In some cases, each individual TB included in the multi-TB scheduled block may be received in a different downlink time slot or downlink subframe at the UE. For example, TBs 1-8 included in the multi-TB scheduled block 710 may be received in eight different downlink time slots or subframes at the UE. The downlink time slots may be back-to-back or otherwise consecutive (e.g., no additional wireless communication data is received between TBs). In some cases, one or more downlink time slots may be used to receive additional wireless communication data interleaved with the TBs of the multi-TB scheduled block (e.g., the last TB 8 is received eight or more time slots after the first TB 1 was received).

[0127]

[0142] As previously described, the UE may generate HARQ feedback based on or otherwise in response to receiving one or more TBs. For example, the UE may generate HARQ feedback (e.g., ACKs or NACKs, also collectively referred to herein as "HARQ-ACK", "HARQ bits", or "HARQ-ACK bits") for one or more TBs included in a multi-TB scheduled block. Also as previously described, in some cases, the UE generates HARQ-ACK feedback for feedback-enabled TBs (e.g., TBs received on or associated with feedback-enabled HARQ processes, such as TBs 1-8 of the feedback-enabled multi-TB block 710). The UE may not generate HARQ-ACK feedback for feedback-disabled TBs (e.g., TBs received on or associated with feedback-disabled HARQ processes, such as TBs 1-8 of the feedback-disabled multi-TB block 710).

[0128]

[0143] In an illustrative example, the HARQ-ACK generated for the feedback enabled multi-TB scheduled block 710 may be included in the combined uplink communication block 715. The combined uplink communication block 715 may also be referred to as the multi-HARQ scheduled block 715. For example, the UE may receive multiple TBs in one TB scheduled block 710, determine a HARQ-ACK bit (e.g., 0 or 1) for each TB 1-8, and schedule or transmit eight HARQ-ACKs 1'-8' in one multi-HARQ scheduled block 715. In some examples, the multi-HARQ scheduled block 715 may correspond to the multi-TB scheduled block 710. For example, the eight HARQ-ACKs 1'-8' may be included in the multi-HARQ scheduled block 715 using the same relative order as the eight TBs (e.g., for which the eight HARQ-ACKs were determined) are included in the multi-TB scheduled block 710.

[0129]

[0144] In some aspects, the multi-TB block 710 (e.g., received by the UE on a downlink (DL) interface) is completely received before transmission of the multi-HARQ block 715 begins. For example, the UE may receive the last TB8 of the multi-TB block 710 before transmitting the first HARQ-ACK1′ of the multi-HARQ block 715. In some examples, the UE may implement half-duplex wireless communication (e.g., the downlink and uplink are not performed simultaneously). In some examples, the first HARQ-ACK1′ of the multi-HARQ block 715 may be transmitted in an uplink timeslot or subframe immediately following the downlink timeslot or subframe in which the last TB8 of the multi-TB block 710 was received. In some cases, as described in more detail below, one or more time slots or subframes may separate the end of the multi-TB block 710 and the beginning of the multi-HARQ block 715 (e.g., one or more time slots or subframes may be located between TB8 of the multi-TB block 710 and HARQ-ACK1' of the multi-HARQ block 715).

[0130]

[0145] As shown in FIG. 7B, the determination of the HARQ-ACK bit and / or the multi-HARQ scheduled block may be omitted when the UE receives a multi-TB scheduled block that includes only feedback disabled HARQ processes (e.g., the HARQ-ACK bit and the multi-HARQ scheduled block may not be generated for the feedback disabled multi-TB scheduled block 720).

[0131]

[0146] In some aspects, the systems and techniques may implement multi-TB scheduling by including only feedback-enabled TBs or only feedback-invalid TBs in a given multi-TB scheduled block. For example, the systems and techniques may implement multi-TB scheduling such that a given multi-TB scheduled block includes only feedback-enabled TBs (e.g., in the feedback-enabled multi-TB block 710) or only feedback-invalid TBs (e.g., in the feedback-invalid multi-TB block 720). In some aspects, the systems and techniques may implement multi-TB scheduling using only feedback-enabled multi-TB blocks (e.g., in the multi-TB block 710) and transmit feedback-invalid TBs without using multi-TB scheduling. In some cases, the systems and techniques may implement multi-TB scheduling using only feedback-invalid multi-TB blocks (e.g., in the multi-TB block 720) and transmit feedback-enabled TBs without using multi-TB scheduling.

[0132]

[0147] In some aspects, the systems and techniques may perform multi-TB scheduling across homogeneous groups of feedback-enabled HARQ processes and homogeneous groups of feedback-disabled HARQ processes, where a heterogeneous group including both feedback-enabled and feedback-disabled HARQ processes is transmitted without using multi-TB scheduling.

[0133]

[0148] In one exemplary example, the systems and techniques may be used to perform multi-TB scheduling for one or more combinations (e.g., heterogeneous sets) of feedback-enabled and feedback-disabled HARQ processes. For example, a single DCI may be used to schedule a single multi-TB block that includes both feedback-enabled and feedback-disabled HARQ processes (e.g., a single multi-TB block that includes feedback-enabled and feedback-disabled TBs).

[0134]

[0149] FIG. 8 is a diagram 800 illustrating an example of multi-TB scheduling with feedback-enabled HARQ processes and feedback-disabled HARQ processes (e.g., feedback-enabled TB and feedback-disabled TB) included in the same multi-TB block. As shown, the multi-TB scheduled block 810 may include multiple feedback-enabled HARQ processes (e.g., five feedback-enabled HARQ processes 1, 2, 4, 7, and 8) and multiple feedback-disabled HARQ processes (e.g., three feedback-disabled HARQ processes 3, 5, and 6). The multi-TB scheduled block 810 may be received by a UE, for example, using a downlink (DL) interface associated with the UE. In some cases, the multi-TB scheduled block 810 may be received from a base station or NTN node that may be included in eMTC over NTN and / or NB-IoT over NTN network. As shown, the feedback-enabled HARQ processes are shown as unshaded squares and the feedback-disabled HARQ processes (e.g., 3, 5, and 6) are shown as shaded squares. In some examples, the multi-TB block 810 may include more or less than the five (e.g., 1, 2, 4, 7, and 8) feedback-enabled HARQ processes shown in Figure 8. Additionally or alternatively, the multi-TB block 810 may include more or less than the three (e.g., 3, 5, and 6) feedback-disabled HARQ processes shown in Figure 8.

[0135]

[0150] In one illustrative example, the UE may generate and transmit a multi-HARQ scheduled feedback block in response to receiving one or more of TBs 1-8 included in the multi-TB block 810. For example, the multi-HARQ block may include one or more HARQ-ACK bits generated or determined for a corresponding one or more of TBs 1-8 included in the multi-TB block 810 (e.g., as described above with respect to FIGS. 7A and 7B).

[0136]

[0151] In some aspects, the UE may generate a multi-HARQ feedback block including a determined HARQ-ACK bit (e.g., ACK or NACK, 0 or 1, etc.) for each feedback valid TB and a determined placeholder feedback bit (e.g., "dummy" ACK, NACK, 0, 1, etc.) for each feedback invalid TB. For example, the multi-HARQ feedback block 815a may include HARQ-ACK bits 1', 2', 4', 7', and 8', which may be determined for feedback valid TBs 1, 2, 4, 7, and 8, respectively. The multi-HARQ feedback block 815a may further include placeholder feedback bits for feedback invalid TBs 3, 5, and 6 (e.g., shown as three empty slots in the multi-HARQ feedback block 815a). The multi-HARQ feedback block 815a may be generated based on an uplink transmission configuration or an uplink transmission schedule such that each HARQ-ACK bit (e.g., 1', 2', 4', 7', 8') has the same relative position in the multi-HARQ feedback block 815a as its corresponding feedback enabled TB in the multi-TB block 810 (e.g., the same relative position as one of feedback enabled TBs 1, 2, 4, 7, 8). The uplink transmission configuration may further be used to schedule the placeholder feedback bits such that each placeholder feedback bit has the same relative position in the multi-HARQ feedback block 815a as one of the feedback disabled TBs in the multi-TB block 810 (e.g., the same relative position as one of feedback disabled TBs 3, 5, 6). In some examples, a multi-HARQ feedback block (e.g., multi-HARQ feedback block 815a) including a HARQ-ACK bit for each feedback valid TB and a placeholder feedback bit for each feedback invalid TB may be generated without any changes to the HARQ-ACK transmission timeline (e.g., without any changes to the HARQ-ACK transmission timeline associated with the multi-TB block 810).

[0137]

[0152] In some aspects, the UE may generate and transmit a multi-HARQ feedback block without generating or transmitting “dummy” (e.g., placeholder) feedback bits for feedback-disabled TBs 3, 4, and 5. For example, the UE may generate and transmit HARQ-ACK bits for feedback-enabled TBs 1, 2, 4, 7, and 8 of the multi-TB block 810 and transmit nothing for feedback-disabled TBs 3, 5, and 6 of the multi-TB block 810.

[0138]

[0153] In one illustrative example, the HARQ-ACK transmission timeline may remain unchanged, and the UE creates a "hole" (e.g., an empty uplink time slot or subframe where the UE does not transmit anything) for each feedback-disabled TB. For example, the multi-HARQ feedback block 815b shown in FIG. 8 may be generated to include HARQ-ACK bits 1', 2', 4', 7', 8' corresponding to feedback-enabled TBs 1, 2, 4, 7, 8, respectively, and "holes" or empty slots corresponding to feedback-disabled TBs 3, 5, 6. In the example multi-HARQ block 815b, each HARQ-ACK bit (e.g., 1', 2', 4', 7', 8') is located in the same relative position within the multi-HARQ block 815b as the feedback-enabled TBs (e.g., 1, 2, 4, 7, 8) are located within the multi-TB block 810.

[0139]

[0154] Furthermore, each HARQ-ACK bit may be located in the same relative position in the example of multi-HARQ block 815a (e.g., HARQ-ACK bits are transmitted for feedback enabled TBs and "dummy" feedback bits are transmitted for feedback disabled TBs) and in the example of 815b (e.g., HARQ-ACK bits are transmitted for feedback enabled TBs and "hole" / nothing is transmitted for feedback disabled TBs). As previously mentioned, when a UE generates a multi-HARQ block with either "dummy" bits for feedback disabled TBs (e.g., multi-HARQ block 815a) or "hole" / empty slots for feedback disabled TBs (e.g., multi-HARQ block 815b), the multi-HARQ block may be transmitted using an unmodified HARQ-ACK transmission timeline. The unmodified HARQ-ACK transmission timeline may be determined as the order or time slots / subframes in which TBs 1-8 are received in the multi-TB block 810.

[0140]

[0155] In another illustrative example, the HARQ-ACK transmission timeline may be modified to transmit only HARQ-ACK bits 1', 2', 4', 7', 8' consecutively or back-to-back. For example, as shown in multi-HARQ block 815c, the UE may generate a multi-HARQ feedback block to include only HARQ-ACK bits for feedback enabled TBs. In this case, the multi-HARQ feedback block, such as multi-HARQ block 815c, does not include any dummy feedback bits for feedback disabled TBs (e.g., as in multi-HARQ block 815a) and does not include any "holes" / empty slots for feedback disabled TBs (e.g., as in multi-HARQ block 815b).

[0141]

[0156] For example, the HARQ-ACK transmission timeline (e.g., uplink transmission configuration for transmitting multi-HARQ block 815c) may be modified by shifting one or more of the HARQ-ACK bits generated for feedback enabled TBs to earlier uplink time slots / subframes that would otherwise be associated with feedback disabled TBs. For example, multi-HARQ block 815c may be generated by shifting one or more of HARQ-ACK bits 1', 2', 4', 7', 8' to earlier time slots / subframes that would otherwise be used to transmit either a "dummy" placeholder feedback bit for feedback disabled TBs (e.g., as in multi-HARQ block 815a) or a "hole" / empty slot for feedback disabled TBs (e.g., as in multi-HARQ block 815b). As shown in FIG. 8, multi-HARQ block 815c may be generated by shifting HARQ-ACK bit 4' one slot left and HARQ-ACK bits 7' and 8' three slots left.

[0142]

[0157] As shown, the multi-HARQ block 815c may include a total of five uplink timeslots (e.g., one uplink timeslot for each of the five HARQ-ACK bits 1', 2', 4', 7', 8'). In some cases, since the multi-HARQ feedback block 815c does not include uplink timeslots associated with feedback null TBs 3, 5, 6, the multi-HARQ feedback block 815c may be transmitted in a smaller amount of total timeslots than either of the multi-HARQ blocks 815a or 815b. Furthermore, the multi-HARQ feedback block 815c may finish transmitting earlier than either of the multi-HARQ blocks 815a or 815b (e.g., all else being equal, the multi-HARQ feedback block 815c may finish transmitting a number of timeslots before the multi-HARQ feedback block 815a or 815b equal to the number of feedback null TBs included in the multi-TB block 810).

[0143]

[0158] In another illustrative example, the UE may generate a multi-HARQ block based on a multi-TB block by scheduling all feedback-enabled HARQ processes together and scheduling all feedback-disabled HARQ processes together. For example, if a "dummy" or placeholder feedback bit is generated for each feedback-disabled TB (e.g., as shown in multi-HARQ block 815a), the UE may generate a multi-HARQ feedback block that schedules HARQ-ACK bits consecutively (e.g., back-to-back) and schedules "dummy" placeholder bits consecutively (e.g., back-to-back). In some examples, the multi-HARQ feedback block may be generated based on an uplink communication configuration in which the HARQ-ACK bits determined for the feedback-enabled TBs are scheduled earlier than the "dummy" placeholder bits determined for the feedback-disabled TBs. In some cases, the multi-HARQ feedback block may be generated based on an uplink communication configuration in which the HARQ-ACK bits determined for the feedback-enabled TBs are scheduled later than the "dummy" placeholder bits determined for the feedback-disabled TBs.

[0144]

[0159] In some cases, when a "dummy" placeholder bit is not generated for a feedback disabled TB (e.g., only HARQ-ACK bits are determined for a feedback disabled TB), the UE may receive a multi-TB block (e.g., such as multi-TB block 810) and immediately begin transmitting HARQ-ACK bits after the end of the multi-TB block (e.g., using an uplink interface to a base station or NTN node). For example, after the PDSCH associated with multi-TB block 810 ends, the UE may immediately begin transmitting HARQ-ACK bits 1', 2', 4', 7', 8'. If the multi-HARQ block includes a "hole" or empty uplink slot for a feedback disabled TB, the "hole" or empty uplink slot may be transmitted after the last HARQ-ACK bit (e.g., 8') is transmitted.

[0145]

[0160] In some examples, multi-TB scheduling may be implemented based on scheduling all feedback-enabled HARQ processes together and scheduling all feedback-disabled HARQ processes together for both the multi-TB block and the corresponding multi-HARQ feedback block generated based on the multi-TB block. For example, FIG. 9 is a diagram 900 illustrating an example of multi-TB scheduling where a single multi-TB block 910 includes feedback-enabled TBs and feedback-disabled TBs (e.g., TBs 1-4 and 5-8, respectively) grouped consecutively and separately. In this example, a UE may receive a multi-TB block (e.g., multi-TB block 910) with a HARQ-ACK transmission timeline already sorted to group feedback-enabled TBs 1-4 and feedback-disabled TBs 5-8 separately. Based on the multi-TB block 910 that already includes HARQ-ACK transmission timelines sorted based on feedback-enabled / feedback-disabled status of TBs 1-8, the UE may then generate a multi-HARQ feedback block that uses the same HARQ-ACK timeline as the multi-TB block 910. For example, if "dummy" placeholder bits are generated for feedback disable TBs 5-8, then multi-HARQ feedback block 915a may include the placeholder bits in the same relative order as feedback disable TBs 5-8 in multi-TB block 910. Similarly, if "holes" or empty uplink transmission slots / subframes are utilized for feedback disable TBs 5-8, then multi-HARQ feedback block 915b may only include HARQ-ACK bits 1'-4' in a first group of uplink transmission slots / subframes followed by a second group of uplink transmission slots / subframes for feedback disable TBs, the "holes."

[0146]

[0161] In the examples described above with respect to Figures 7A-9, reference was made to a UE receiving a multi-TB block (e.g., multi-TB blocks 710, 810, 910) without HARQ-ACK bundling being enabled. When HARQ-ACK bundling is not enabled, each multi-TB block includes TBs 1-8 in a single set or group. In some aspects, HARQ-ACK bundling may be enabled and the multi-TB block may include one or more subsets or subgroups, each including a unique portion of the TBs associated with the entire multi-TB block.

[0147]

[0162] For example, FIG. 10A is a diagram 1000 illustrating an example of multi-TB scheduling for a multi-TB block 1010 including feedback enabled TBs (e.g., TBs 1, 2, 5, 6) and feedback disabled TBs (e.g., 3, 4, 7, 8), where TBs 1-8 of the multi-TB block 1010 are split into bundles B1, B2, and B3. In some examples, a greater or lesser number of bundles may be included in the multi-TB block 1010. In some cases, each bundle may include an equal number of TBs (e.g., for a multi-TB block including 8 TBs, HARQ-ACK bundling may be applied to create two bundles with 4 TBs each, four bundles with 2 TBs each, etc.). In some examples, the number of bundles and the number of TBs may be equal (e.g., the multi-TB block 1010 may be bundled using 8 bundles, with each bundle including a single TB of TBs 1-8). In some examples, multi-TB block 1010 may be bundled using a first bundle including TBs 1-3, a second bundle including TBs 4-6, and a third bundle including TBs 7-8.

[0148]

[0163] In some aspects, the multi-TB blocks may be bundled based on a TB bundling configuration. For example, the TB bundling configuration may include one or more predefined bundling schemes. In some cases, the TB bundling configuration may include different predefined bundling schemes based on the multi-TB block size (e.g., the number of TBs included in the multi-TB block). An example TB bundling configuration 1000b may include a multi-TB block size N TB 10B for TB=1, 2, 4, 6, and 8. In some aspects, multiple different TB bundling configurations may be utilized. For example, a multi-TB block may be bundled based on a TB bundling configuration selected from multiple TB bundling configurations. In one illustrative example, the use of multiple TB bundling configurations may provide a base station or NTN node with increased flexibility in bundling feedback-enabled HARQ processes and feedback-disabled HARQ processes together (e.g., bundling feedback-enabled TBs and feedback-disabled TBs together). In some aspects, a radio resource control (RRC) and / or medium access control (MAC) control element (MAC-CE) transmission may be used to indicate a selected TB bundling configuration or a selected TB bundling configuration table to be used.

[0149]

[0164] 10A illustrates an exemplary multi-TB block 1010 to which TB bundling has been applied. For example, the multi-TB block 1010 includes eight TBs 1-8 and three bundles B1, B2, and B3. As illustrated, bundle B1 includes feedback-enabled TBs 1 and 2. Bundle B2 includes feedback-disabled TBs 3 and 4, and bundle B3 includes feedback-enabled TBs 5 and 6 and feedback-disabled TBs 7 and 8.

[0150]

[0165] In one illustrative example, bundling may be performed to reduce the total number of feedback bits included in a multi-HARQ feedback block generated by a UE based on receiving a bundled multi-TB block (e.g., bundled multi-TB block 1010, etc.). For example, a bundled multi-HARQ feedback block may be generated to include a single feedback bit per bundle (e.g., rather than a feedback bit per TB or per feedback enabled TB, both of which are described above). For example, a feedback bit may be generated for each bundle by computing a logical AND over the feedback bits determined for each TB included in the bundle.

[0151]

[0166] For example, a "dummy" placeholder bit may be generated for each feedback-invalid TB (e.g., TBs 3, 4, 7, 8) included in the multi-TB block 1010. A HARQ-ACK bit may be generated for each feedback-valid TB (e.g., TBs 1, 2, 5, 6) as described above. The resulting set of feedback bits 1013 is shown in FIG. 10A. In an illustrative example, the set of feedback bits 1013 may be associated with the same bundle or bundling scheme as the multi-TB block 1010. For example, HARQ-ACK bits 1' and 2' may be included in a first bundle (e.g., corresponding to bundle B1 in the multi-TB block 1010), two "dummy" placeholder bits may be included in a second bundle (e.g., corresponding to bundle B2 in the multi-TB block 1010), and HARQ-ACK bits 5', 6' and two "dummy" placeholder bits may be included in a third bundle (e.g., corresponding to bundle B3 in the multi-TB block 1010).

[0152]

[0167] The multi-HARQ feedback block 1015 may be generated based on the multi-TB block 1010 and / or the set of feedback bits 1013 by determining a logical AND between the feedback bits 1013 associated with each of the bundles B1, B2, and B3. In some cases, when a logical AND is used to calculate the feedback bits for the bundles, a default value of 1 (e.g., dummy ACK) may be used as a placeholder feedback bit for each feedback-disabled TB. As shown, the multi-HARQ feedback block 1015 may include feedback bit B1' and HARQ-ACK bits 1' and 2' determined for bundle B1, feedback bit B2' and placeholder feedback bits associated with feedback-disabled TBs 3 and 4 determined for bundle B2, and HARQ-ACK bits 5', 6' and placeholder feedback bits associated with feedback-disabled TBs 7 and 8 determined for bundle B3. In some examples, the HARQ-ACK transmission timeline may remain unchanged between the bundled multi-TB block 1010 and the bundled multi-HARQ block 1015.

[0153]

[0168] FIG. 11 is a diagram 1100 illustrating another example multi-TB block 1110 to which TB bundling is applied, where example multi-HARQ feedback blocks 1115a and 1115b may be generated without determining "dummy" placeholder feedback bits for feedback-disabled TBSs (e.g., TBs 2, 4, 7, 8). As shown, the multi-TB block 1110 includes eight TBs 1-8, where TBs 1, 2, 5, 6 are feedback-enabled TBs, and TBs 3, 4, 7, 8 are feedback-disabled TBs. A TB bundling configuration is applied to the multi-TB block 1110. A first bundle B1 includes feedback-enabled TBs 1 and 2, a second bundle B2 includes feedback-disabled TBs 3 and 4, and a third bundle B3 includes feedback-enabled TBs 5, 6 and feedback-disabled TBs 7, 8. In an example example, the multi-TB block 1110 and the multi-TB block 1010 illustrated in FIG. 10A may be the same.

[0154]

[0169] In one illustrative example, bundling may be performed to generate a bundled multi-HARQ feedback block (e.g., bundled multi-HARQ feedback block 1115a and / or 1115b, described in more detail below, etc.) based on the bundled multi-TB block 1110. For example, a HARQ-ACK bit may be generated for each feedback valid TB (e.g., TBs 1, 2, 5, 6). HARQ-ACK bits 1', 2', 5', 6' may be included in the set of feedback bits 1113 as shown in FIG.

[0155]

[0170] The set of feedback bits 1113 (which may be used later, e.g., to generate bundled multi-HARQ feedback blocks 1115a and / or 1115b) may further include one or more "dummy" placeholder bits generated for one or more of the feedback disabled TBs (e.g., TBs 3, 4, 7, 8). In the example described above with respect to FIG. 10A, a dummy placeholder bit was generated for each feedback disabled TB.

[0156]

[0171] In the example of FIG. 11, dummy placeholder bits may be generated only for feedback disable TBs included in a bundle (e.g., one of the bundles B1, B2, B3 associated with the bundled multi-TB block 1110) that includes at least one feedback enable TB. For example, as shown in FIG. 11, the set of feedback bits 1113 may include a dummy placeholder bit generated for feedback disable TB7 and a dummy placeholder bit generated for feedback disable TB8, but does not include dummy placeholder bits for feedback disable TBs 3 or 4. Feedback disable TBs 7 and 8 are included in bundle B3 that includes at least one feedback enable TB (e.g., B3 includes two feedback enable TBs 5 and 6), and thus dummy placeholder bits may be generated for feedback disable TBs 7 and 8. Feedback disable TBs 3 and 4 are included in bundle B2 that includes only feedback disable TBs. Thus, in some examples, dummy placeholder bits are not generated for feedback disable TBs 3 and 4.

[0157]

[0172] In one illustrative example, a set of feedback bits (e.g., 1113) used to subsequently generate a bundled multi-HARQ block (e.g., 1115a and / or 1115b) may include a HARQ-ACK bit generated for each feedback enabled TB and a dummy placeholder feedback bit generated for any feedback disabled TB included in a bundle with at least one feedback enabled TB. The set of feedback bits (e.g., 1113) may omit generating any placeholder feedback bits for feedback disabled TBs included in a bundle with only feedback disabled TBs (e.g., if each TB in a bundle is feedback disabled, then no dummy placeholder feedback bits are generated for the TBs of that bundle).

[0158]

[0173] In some aspects, the bundled multi-HARQ feedback block 1115a may be generated based on the set of feedback bits 1113 by calculating a combined (e.g., single) feedback bit for each bundle. For example, the combined feedback bit B1' may be calculated as a logical AND between HARQ-ACK bits 1' and 2' (e.g., determined for TBs 1 and 2 of bundle B1). The combined feedback bit B3' may be calculated as a logical AND between HARQ-ACK bits 5', 6' (e.g., determined for TBs 5 and 6 of bundle B3) and two dummy placeholders included in the set of feedback bits 1113 (e.g., determined for feedback disable TBs 7 and 8 of bundle B3, as described above).

[0159]

[0174] In some aspects, when the set of feedback bits 1113 does not include a HARQ-ACK bit or a dummy placeholder bit for a given bundle, a bundled multi-HARQ feedback block 1115a may be generated to include a "hole" or empty uplink timeslot / subframe for that bundle. For example, bundle B2 includes only feedback disable TBs 3 and 4, and the set of feedback bits 1113 is empty for bundle B2. As shown, the bundled multi-HARQ feedback block 1115a includes a "hole" or empty uplink timeslot / subframe between combined feedback bits B1' and B2' (e.g., combined feedback bit B1' is transmitted in the first uplink timeslot, nothing is transmitted in the second uplink timeslot (e.g., a "hole" is transmitted), and combined feedback bit B2' is transmitted in the third uplink timeslot).

[0160]

[0175] In some examples, the bundled multi-HARQ feedback block 1115b may be generated without a "hole" or empty uplink timeslot / subframe for feedback disabled bundles in the received multi-TB block 1110. For example, the combined feedback bits B1' and B3' may be transmitted back-to-back or in consecutive timeslots without reserving or transmitting a "hole" or empty timeslot for bundle B2 (e.g., the combined feedback bit B1' may be transmitted in a first uplink timeslot and the combined feedback bit B3' may be transmitted in a second uplink timeslot upon completion of transmission of the bundled multi-HARQ feedback block 1115b).

[0161]

[0176] In some aspects, a base station may transmit multiple TBs via the same feedback-disabled HARQ process without a time gap between successive TB transmissions. For example, when transmitting via a feedback-disabled HARQ process, the base station does not need to wait to transmit the next TB until a HARQ feedback bit is received for the most recently transmitted TB. In some cases, a UE receiving a TB from a base station (e.g., via one or more HARQ processes, as described above) may process the received TB using a HARQ process-like processing in which a fixed amount of time or a minimum amount of time is associated with processing a given TB on a given HARQ process. In some cases, a base station may transmit multiple TBs via a feedback-disabled HARQ process with a time gap (e.g., between successive transmitted TBs) that is shorter than the minimum HARQ process-like processing time for each TB at the UE. In one illustrative example, the systems and techniques may include a predetermined minimum time gap (e.g., delay) between successive instances of PDSCH on the same HARQ process when feedback is disabled for the HARQ process. For example, in eMTC over an NTN network, the predetermined minimum time gap may be 4 milliseconds (ms). In some cases, shorter or longer predetermined minimum time gaps (e.g., shorter or longer than 4 ms) may be used.

[0162]

[0177] In some aspects, NB-IoT may support up to two HARQ processes. For example, NB-IoT may support up to two HARQ processes when implementing multi-TB scheduling (e.g., up to two HARQ processes may be scheduled per PDSCH and / or using a single DCI). In some examples, HARQ stalls (e.g., as described above) may occur in NB-IoT over NTN networks or other networks with relatively large RTTs between UEs and base stations (e.g., NTN nodes). For example, with only two HARQ processes per DCI / PDSCH, the base station may be idle for multiple downlink time slots while waiting to receive HARQ-ACK bits for TBs sent via two HARQ processes.

[0163]

[0178] In some cases, the base station may transmit more than the supported maximum of two HARQ processes. The NB-IoT UE may be a low-complexity device that does not include sufficient buffer space to store more than two HARQ processes. For example, the NB-IoT UE may include a soft buffer that cannot store more than two HARQ processes simultaneously. In the case of feedback-enabled HARQ processes, the UE may use the soft buffer to store log-likelihood ratios (LLRs) of an initial transmission (e.g., a TB) received via one or more (or all) of the feedback-enabled HARQ processes in a multi-TB scheduled block. For example, the UE may store the LLRs in the soft buffer if the TB needs to be retransmitted (e.g., if the UE does not successfully receive or decode a given TB, the UE will transmit a HARQ-NACK that causes the base station to retransmit the given TB). The retransmitted TB may then be combined with the corresponding LLRs stored in the UE's soft buffer.

[0164]

[0179] In some aspects, the UE may not need to store LLRs for TBs received via feedback-disabled HARQ processes (e.g., except for possible transmission schemes such as blind retransmission). In one illustrative example, the systems and techniques can increase the number of HARQ processes supported by NB-IoT to more than two without increasing the soft buffer storage size associated with the UE receiving the HARQ process via NB-IoT. For example, the maximum number of HARQ processes may be increased from two to four, while the storage size of the soft buffer remains at two HARQ processes. In some aspects, up to four total HARQ processes may be transmitted, with up to two feedback-enabled HARQ processes included in the four (e.g., because two feedback-enabled HARQ processes fill the storage of the UE's soft buffer).

[0165]

[0180] In one illustrative example, a dedicated bit in a DCI scheduling an NPDSCH may be used to indicate whether soft buffer storage is required or not required for a given HARQ process scheduled by the DCI. In some examples, the dedicated bit may be used to indicate whether a given HARQ process is feedback enabled or feedback disabled, and the UE may infer whether soft buffer storage is required or not required based on the feedback type of each HARQ process. For example, the dedicated bit may be set to a first value for feedback enabled HARQ processes (e.g., indicating that soft buffer storage is required for feedback enabled HARQ processes) and set to a second value for feedback disabled HARQ processes (e.g., indicating that soft buffer storage is not required for feedback disabled HARQ processes).

[0166]

[0181] In some aspects, a dedicated bit may be used to signal (e.g., implicitly signal) a HARQ process ID number for one or more of the HARQ processes scheduled by a DCI. For example, the existing "HARQ Process ID" field may currently be provided and occupies one bit. By combining the existing "HARQ Process ID" field with the dedicated bit described above, the number of HARQ processes that may be scheduled by a single DCI may be increased from two to four.

[0167]

[0182] The above description may apply to eMTC over NTN, NB-IoT over NTN, or both. In some aspects, in NB-IoT over NTN networks, the UE may wait k ms from the end of a multi-TB block transmission before starting a multi-HARQ feedback block transmission (e.g., in response to a TB of the multi-TB block). 0 For example, the HARQ-ACK transmission may be delayed at least k subframes after the last TB of the multi-TB block is received. o ' subframes after the UE receives a multi-TB block including feedback enabled TB1 and feedback disabled TB2. 0 ' delay can still be counted from the end of TB2.

[0168]

[0183] Since TB2 is a feedback nulling process, in one illustrative example, k 0 The delay of ' may instead be counted from the end of the last TB (e.g., in a multi-TB block received by the UE) for which HARQ feedback is enabled. In the above example, the UE may count the k ' delay from the end of TB1 instead of TB2 (e.g., because TB1 is the last feedback-enabled TB in the multi-TB block). 0 In some examples, the UE may need to start HARQ-ACK transmission at a time that is greater than or equal to the end of the multi-TB PDSCH +2 ms.

[0169]

[0184] FIG. 12 illustrates an example of a modified HARQ RTT timer start for multi-TB scheduling according to an aspect of the disclosure. For example, diagram 1200a illustrates an example where PDCCH 1202 is used to schedule PDSCH_1, PDSCH_2, PDSCH_3, and PDSCH_4 for which corresponding ACKs ACK1, ACK2, ACK3, and ACK4 are generated. For example, ACK1 may correspond to PDSCH_1, ACK2 may correspond to PDSCH_2, ACK3 may correspond to PDSCH_3, and ACK4 may correspond to PDSCH_4. FIG. 1200b illustrates an example where PDCCH 1202 is used to schedule PDSCH_1, PDSCH_2, PDSCH_3, and PDSCH_4 for which corresponding NACKs NACK1, NACK2, NACK3, and NACK4 are generated. For example, NACK1 may correspond to PDSCH_1, NACK2 may correspond to PDSCH_2, NACK3 may correspond to PDSCH_3, and NACK4 may correspond to PDSCH_4. In some examples, the PDCCH 1202 and / or one or more of PDSCH_1-PDSCH_4 may be the same in FIG. 1200a and FIG. 1200b. In some aspects, one or more (or all) of the PDSCHs PDSCH_1-PDSCH_4 may include downlink communications, such as TBs, that are associated with a HARQ process (e.g., as previously described above).

[0170]

[0185] In some cases, the HARQ RTT timer 1250 may be started at the end of the last scheduled TB. For example, the HARQ RTT timer 1250 may be started from the end of PDSCH_4 based on PDSCH_4 that includes the last scheduled TB associated with the PDCCH 1202 (e.g., as shown in FIG. 1200b).

[0171]

[0186] In an illustrative example, a HARQ RTT timer (e.g., HARQ RTT timer 1250) may be started from the last scheduled TB for which HARQ feedback is enabled. For example, referring again to FIG. 1200b, if the HARQ process associated with PDSCH_4 is a HARQ feedback disabled process (and, e.g., the HARQ process associated with PDSCH_3 is a HARQ feedback enabled process), then the HARQ RTT timer 1250 may be started from the end of PDSCH_3. In some aspects, the HARQ RTT timer 1250 may be started before the end of the last scheduled TB associated with PDCCH 1202 based on determining that the UE is in full-duplex mode (e.g., before the end of PDSCH_4).

[0172]

[0187] In some aspects, the HARQ RTT length (e.g., the duration of a HARQ RTT timer, such as the duration of HARQ RTT timer 1250) may be modified for multi-TB scheduling, in accordance with one or more aspects of the present disclosure. The formula for the HARQ RTT timer (e.g., the duration of the HARQ RTT) may be given for an NB-IoT UE (e.g., in subframes) as follows: HARQ_RTT_Timer NB-IoT =k+2(N+1)+RTT offset +delta PDCCH Formula (1)

[0173]

[0188] Here, k is the interval (e.g., in subframes) between the last subframe of the downlink transmission and the first subframe of the first HARQ feedback transmission. N is the transmission duration (e.g., number of subframes) of the associated HARQ feedback. For example, k may represent the number of subframes of the interval between the last scheduled TB for which HARQ feedback is enabled and the first subframe of the first HARQ feedback transmission (e.g., the number of subframes between PDSCH_3 and NACK1 in the above example). In other examples, k may represent the number of subframes of the interval between the last scheduled TB and the first subframe of the first HARQ feedback transmission (e.g., the number of subframes between PDSCH_4 and NACK1).

[0174]

[0189] In one illustrative example, the duration of the HARQ RTT timer (e.g., the duration of the HARQ RTT timer 1250) is modified to k+(2-X) * (N+1)+RTT offset +delta PDCCH where X is the number of TBs associated with the feedback-disabled HARQ process. For example, as the number of TBs associated with the feedback-disabled HARQ process increases, the number of subframes used for the HARQ RTT timer duration may decrease (e.g., based on starting the HARQ RTT timer 1250 from the last scheduled TB where HARQ feedback is enabled, the length of the corresponding HARQ RTT timer 1250 may decrease relative to the duration of the HARQ RTT timer starting from the end of the last scheduled TB).

[0175]

[0190] In another aspect, an equation for the HARQ RTT timer (e.g., the duration of the HARQ RTT, such as the duration of the HARQ RTT timer 1250) may be given as follows (e.g., in units of subframes) for an eMTC UE using HARQ-ACK bundling: HARQ RTT timereMTC_Bundling =7+kN+RTT offset Formula (2)

[0176]

[0191] where N is the PUCCH repetition factor used for uplink transmission(s) from the eMTC UE and k is the number of HARQ feedback bundles transmitted by the eMTC UE. In some aspects, k is expressed as k=ceiling(N TB / M), where N TB is the number of scheduled TBs as indicated in the PDCCH (e.g., PDCCH 1202, etc.), and M is the multi-TB HARQ-ACK bundling size.

[0177]

[0192] In one illustrative example, the duration of the HARQ RTT timer is modified for eMTC UEs with HARQ-ACK bundling to be 7+(kX) * N+RTT offset where X is the number of bundles for which HARQ feedback is disabled (e.g., X is the number of feedback disabled TB bundles). In some cases, as the number of HARQ feedback disabled bundles increases, the number of subframes used for the duration of the HARQ RTT timer may decrease (e.g., the duration of the HARQ RTT timer 1250 may be smaller).

[0178]

[0193] In another aspect, an equation for the HARQ RTT timer (e.g., the duration of the HARQ RTT, such as the duration of the HARQ RTT timer 1250) may be given as follows (e.g., in subframe units) for an eMTC UE not using HARQ bundling: HARQ RTT timer eMTC_No_Bundling =7+mN+RTT offset Formula (3)

[0179]

[0194] where N is the repetition factor of the PUCCH used for the uplink transmission(s), again as shown in equation (2) above, and m is the number of scheduled TBs as shown in the PDCCH (e.g., PDCCH 1202). In some examples, m in equation (3) is N in equation (2) TB may be the same as or similar to

[0180]

[0195] In one illustrative example, the duration of the HARQ RTT timer is modified for eMTC UEs without HARQ bundling to be 7+(mX) * N+RTT offset where X is the number of TBs for which HARQ feedback is disabled. In some cases, as the number of HARQ feedback disabled TBs increases, the number of subframes used for the duration of the HARQ RTT timer may decrease (e.g., the duration of the HARQ RTT timer 1250 may become smaller).

[0181]

[0196] In some aspects, systems and techniques may include DCI override of RRC configured feedback-enabled and / or feedback-disabled HARQ processes. For example, in some cases, the designation of an HARQ process as feedback-enabled or feedback-disabled may be expected to be provided by RRC signaling (e.g., following NR-NTN).

[0182]

[0197] In one illustrative example, the DCI bit may be used to override a feedback enabled (or feedback disabled) configuration that would otherwise be indicated by an RRC signal. For example, the DCI bit may be included in a DCI used to schedule a transmission on a given HARQ process (e.g., as described above). In some cases, the DCI override bit may be used to change or modify the RRC indication behavior for a given TB on the HARQ process with which the DCI override bit is associated (e.g., a HARQ process scheduled by a DCI that includes a DIC override bit). In some aspects, the DCI override bit may be utilized for single TB scheduling.

[0183]

[0198] In some examples, the DCI override bit may be implemented using a newly designated bit in the DCI. In some cases, the DCI override bit may be implemented using an existing bit in the DCI (e.g., by reusing an existing bit as the override bit). For example, in the context of HARQ-ACK bundling with single-TB scheduling, a feedback-disabled TB may be overridden to a feedback-enabled TB by setting the "HARQ ACK bundling flag" on (or "1") for the TB, whereas if feedback is disabled, the flag is set to off.

[0184]

[0199] FIG. 13 is a flow chart illustrating an example of a process 1300 for wireless communication in a user equipment (UE). For example, the process 1300 may be implemented using one or more techniques described herein (e.g., for scheduling feedback-less hybrid automatic repeat resource request (HARQ) feedback). The process 1300 may be implemented by a computing device or apparatus, such as a wireless communication device (e.g., UE), or a component or system of a wireless communication device (e.g., a chipset). Operations of the process 1300 may be implemented as software components executing and operating on one or more processors (e.g., processor(s) 484 of FIG. 4, processor 1410 of FIG. 14, or other processor(s)). Furthermore, transmission and reception of signals by the wireless communication device in the process 1300 may be enabled by, for example, one or more antennas (e.g., antenna 487 of FIG. 4) and / or one or more transceivers (e.g., wireless transceiver(s) 478 of FIG. 4).

[0185]

[0200] At block 1302, the process 1300 includes receiving a plurality of wireless downlink communications, where each downlink communication of the plurality of downlink communications is associated with a hybrid automatic repeat request (HARQ) process. For example, the plurality of wireless downlink communications may be received by a wireless communication device (or a component thereof). In some examples, the plurality of downlink communications includes one or more feedback enabled transport blocks (TBs). Each feedback enabled TB may be associated with a HARQ feedback enabled process. In some cases, the one or more feedback enabled TBs are received according to multi-TB scheduling based on downlink control information (DCI) associated with the multi-TB scheduling. For example, the feedback enabled TBs associated with the HARQ feedback enabled process may be the same as or similar to the exemplary feedback enabled TBs 1-8 included in the feedback enabled multi-TB block 710 shown in FIG. 7A.

[0186]

[0201] In some examples, the downlink communications may include one or more feedback nulling TBs, where each feedback nulling TB is associated with a HARQ feedback nulling process and is received without using multi-TB scheduling.

[0187]

[0202] In some examples, the downlink communications may include one or more feedback disabled transport blocks (TBs), where each feedback disabled TB is associated with a HARQ feedback disabled process. In some cases, the one or more feedback disabled TBs are received using multi-TB scheduling based on downlink control information (DCI) associated with the multi-TB scheduling. For example, the feedback disabled TBs associated with the HARQ feedback disabled process may be the same as or similar to the exemplary feedback disabled TBs 1-8 included in the feedback disabled multi-TB block 720 shown in FIG. 7B.

[0188]

[0203] In some examples, the downlink communications include one or more feedback enabled TBs (e.g., associated with a HARQ feedback enabled process) and further include one or more feedback disabled TBs (e.g., associated with a HARQ feedback disabled process). The one or more feedback enabled TBs and the one or more feedback disabled TBs may be received according to multi-TB scheduling based on downlink control information (DCI) associated with the multi-TB scheduling. For example, the downlink communications may be received in a multi-TB scheduled block, such as the multi-TB scheduled block 810 shown in FIG. 8 or the multi-TB scheduled block 910 shown in FIG. 9.

[0189]

[0204] In some aspects, one or more feedback-enabled TBs and one or more feedback-disabled TBs may be received as one or more TB bundles. Each feedback-enabled TB and each feedback-disabled TB may be included in only one TB bundle of the one or more TB bundles. For example, the feedback-enabled TBs and the feedback-disabled TBs may be included in one or more of the TB bundles B1, B2, and B3 shown in FIG. 10 and FIG. 11. In some examples, the one or more TB bundles may include at least one of a feedback-enabled TB bundle (e.g., each feedback-enabled TB bundle includes at least one feedback-enabled TB) and / or a feedback-disabled TB bundle (e.g., each feedback-disabled TB bundle does not include a feedback-enabled TB). For example, the feedback-enabled TB bundle may be the same as or similar to the feedback-enabled TB bundles B1 and / or B3 shown in FIG. 10A. The feedback-disabled TB bundle may be the same as or similar to the feedback-disabled TB bundle B2 shown in FIG. 10A.

[0190]

[0205] At block 1304, process 1300 includes determining one or more uplink communications, where each uplink communication of the one or more uplink communications includes feedback associated with at least one downlink communication of the plurality of downlink communications. For example, the one or more uplink communications may be determined by a wireless communication device (or a component thereof).

[0191]

[0206] In some examples, the one or more uplink communications include HARQ feedback that has been determined for each feedback enabled TB of the one or more feedback enabled TBs. For example, the one or more uplink communications may include HARQ-ACK bits 1'-8' shown in FIG. 7A as being determined for feedback enabled TBs 1-8. In some cases, the first uplink slot of the uplink communication transmission configuration is later than the last downlink slot associated with receiving one or more feedback enabled TBs using multi-TB scheduling. For example, the uplink time slot associated with transmitted HARQ-ACK 1' may be later than the downlink time slot associated with receiving TB 8, in the context of the example of FIG. 7A.

[0192]

[0207] In some examples, one or more uplink communications do not include feedback associated with one or more feedback disable TBs (e.g., no uplink communications are generated for feedback disable TBs 1-8 included in feedback disable TB 720 shown in FIG. 7B).

[0193]

[0208] In some examples, when the multiple downlink communications include a single multi-TB block with both feedback enabled TBs and feedback disabled TBs (e.g., multi-TB scheduled block 810 shown in FIG. 8, multi-TB scheduled block 910 shown in FIG. 9, etc.), the one or more uplink communications may include a respective HARQ feedback determined for each feedback enabled TB of the one or more feedback enabled TBs and a respective placeholder feedback determined for each feedback disabled TB of the one or more feedback disabled TBs. For example, the one or more uplink communications may be provided as a multi-HARQ feedback block, such as the multi-HARQ feedback block 815a shown in FIG. 8.

[0194]

[0209] In some examples, the one or more uplink communications include HARQ feedback determined for each feedback-enabled TB and do not include feedback associated with one or more feedback-disabled TBs. For example, the one or more uplink communications may be provided as a multi-HARQ feedback block, such as the multi-HARQ feedback block 815b illustrated in FIG. 8. In some cases, in block 1304, the process 1300 may further include determining an uplink communication transmission configuration based on a relative order associated with receiving the one or more feedback-enabled TBs and the one or more feedback-disabled TBs. For example, the uplink communication transmission configuration may be determined by generating, for each feedback-enabled TB included in the relative order, a HARQ feedback transmission time interval associated with the HARQ feedback determined for the feedback-enabled TB and generating, for each feedback-disabled TB included in the relative order, an empty uplink transmission time interval associated with the feedback-disabled TB.

[0195]

[0210] In some cases, the HARQ feedback that has been determined for each feedback valid TB of the one or more feedback valid TBs may be transmitted without transmitting anything for the feedback invalid TBs. For example, the HARQ feedback may be provided as a multi-HARQ feedback block, such as the multi-HARQ feedback block 815c shown in FIG. 8. The HARQ feedback may be transmitted in the same relative order associated with receiving the one or more feedback valid TBs, where the relative order does not include the one or more feedback invalid TBs. In some cases, the HARQ feedback may be transmitted without reserving one or more uplink transmission time intervals for the one or more feedback invalid TBs.

[0196]

[0211] In some aspects, when multiple downlink communications are received as feedback-enabled and / or feedback-disabled TBs included in one or more TB bundles (e.g., TB bundles B1, B2, and B3 shown in FIG. 10A), a respective HARQ feedback may be generated for each feedback-enabled TB included in the feedback-enabled TB bundle. In some cases, a respective placeholder feedback may be generated for each feedback-disabled TB included in the feedback-enabled TB bundle. In some aspects, a bundled HARQ feedback may be determined based on the respective HARQ feedback and the respective placeholder feedback, where one or more uplink communications include the bundled HARQ feedback. For example, the bundled HARQ feedback may include bundled HARQ feedback bits B1′, B2′, and / or B3′ shown in FIG. 10A as included in the bundled HARQ feedback block 1015.

[0197]

[0212] In some examples, the bundled HARQ feedback bits (e.g., B1', B2', B3' shown in FIG. 10A) may be determined by computing a logical AND between each HARQ feedback and each placeholder feedback. In some cases, the placeholder feedback may include an acknowledgement (ACK) or a logical value "1".

[0198]

[0213] At block 1306, process 1300 includes transmitting one or more uplink communications based on an uplink communication transmission configuration, the uplink communication transmission configuration being determined based on a type of each downlink communication of the plurality of downlink communications. For example, the one or more uplink communications may be transmitted by a wireless communication device (or a component thereof).

[0199]

[0214] In some examples, when multiple downlink communications include a single multi-TB block with both feedback enabled TBs and feedback disabled TBs (e.g., multi-TB scheduled block 810 shown in FIG. 8, multi-TB scheduled block 910 shown in FIG. 9, etc.), the uplink communication transmission configuration may be determined based on a relative order associated with receiving one or more feedback enabled TBs and one or more feedback disabled TBs. In some examples, the HARQ feedback and the placeholder feedback are transmitted using the same relative order associated with receiving one or more feedback enabled TBs and one or more feedback disabled TBs.

[0200]

[0215] In some examples, when TB bundling is enabled or implemented (e.g., a multi-TB scheduled block is received using one or more TB bundles, such as bundles B1, B2, and B3 shown in FIG. 10A as being associated with multi-TB block 1010), an uplink communication transmission configuration may be determined based on a relative order associated with receiving the one or more TB bundles. For example, the uplink communication transmission configuration may be determined by generating, for each given feedback-enabled TB bundle included in the relative order, a HARQ feedback transmission time interval associated with the bundled HARQ feedback determined for the given feedback-enabled TB bundle, and generating, for each given feedback-disabled TB bundle included in the relative order, an empty uplink transmission time interval associated with the given feedback-disabled TB bundle.

[0201]

[0216] In some cases, the bundled HARQ feedback may be transmitted in the same relative order associated with receiving one or more TB bundles, where the relative order does not include one or more feedback null TB bundles. For example, the bundled HARQ feedback may be transmitted without reserving one or more uplink transmission time intervals for one or more feedback null TB bundles (e.g., in the multi-HARQ feedback block 1115b shown in FIG. 11).

[0202]

[0217] In some examples, the processes described herein (e.g., process 1300 and / or other processes described herein) may be performed by a computing device or apparatus (e.g., a UE, a network entity, etc.). In one example, process 1300 may be performed by a wireless communication device such as a UE (e.g., wireless device 407 of FIG. 4, UE 505 of FIGS. 5A-5C, UE 630 of FIG. 6, a mobile device, and / or other UE or device). In another example, process 1300 may be performed by a computing device having a computing system 1400 shown in FIG. 14. For example, a wireless communication device having a computing architecture shown in FIG. 14 (e.g., wireless device 407 of FIG. 4, UE 505 of FIGS. 5A-5C, UE 630 of FIG. 6, a mobile device, and / or other UE or device) may include components of a UE and may implement the operations of FIG. 13.

[0203]

[0218] In some cases, a computing device or apparatus may include various components, such as one or more input devices, one or more output devices, one or more processors, one or more microprocessors, one or more microcomputers, one or more cameras, one or more sensors, and / or other component(s) configured to perform steps of processes described herein. In some examples, a computing device may include a display, one or more network interfaces configured to communicate and / or receive data, any combination thereof, and / or other component(s). The one or more network interfaces may be configured to communicate and / or receive wired and / or wireless data, including data according to 3G, 4G, 5G, and / or other cellular standards, data according to the WiFi (802.11x) standard, data according to the Bluetooth™ standard, data according to the Internet Protocol (IP) standard, and / or other types of data.

[0204]

[0219] Components of a computing device may be implemented with circuitry, for example, components may include and / or be implemented using electronic circuitry or other electronic hardware, which may include one or more programmable electronic circuitry (e.g., microprocessors, graphics processing units (GPUs), digital signal processors (DSPs), central processing units (CPUs), and / or other suitable electronic circuitry), and / or may include and / or be implemented using computer software, firmware, or any combination thereof to perform various operations described herein.

[0205]

[0220] Process 1300 is illustrated as a logical flow diagram, whose operations represent sequences of operations that may be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, the operations represent computer-executable instructions stored on one or more computer-readable storage media that, when executed by one or more processors, perform the described operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, etc. that perform particular functions or implement particular data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations may be combined in any order and / or in parallel to implement a process.

[0206]

[0221] Additionally, process 1300 and / or other processes described herein may be performed under the control of one or more computer systems configured with executable instructions and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) that collectively execute on one or more processors, by hardware, or a combination thereof. As mentioned above, the code may be stored on a computer-readable or machine-readable storage medium, for example, in the form of a computer program comprising instructions executable by one or more processors. The computer-readable or machine-readable storage medium may be non-transitory.

[0207]

[0222] Fig. 14 illustrates an example of a system for implementing certain aspects of the present technology. In particular, Fig. 14 illustrates an example of a computing system 1400, which may be, for example, any computing device constituting an internal computing system, a remote computing system, a camera, or any component of the system that communicates with each other using a connection 1405. The connection 1405 may be a physical connection using a bus, or may be a direct connection to a processor 1410, such as in a chipset architecture. The connection 1405 may also be a virtual connection, a network connection, or a logical connection.

[0208]

[0223] In some aspects, computing system 1400 is a distributed system in which the functionality described in this disclosure may be distributed across a data center, multiple data centers, a peer network, etc. In some aspects, one or more of the system components described represent many such components, each performing some or all of the functionality described. In some aspects, these components may be physical or virtual devices.

[0209]

[0224] The exemplary system 1400 includes at least one processing unit (CPU or processor) 1410 and connections 1405 that communicatively couple various system components to the processor 1410, including system memory 1415, such as read-only memory (ROM) 1420 and random access memory (RAM) 1425. The computing system 1400 may include a cache 1412 of high-speed memory directly connected to, adjacent to, or integrated as part of the processor 1410.

[0210]

[0225] Processor 1410 may include any general purpose processor, hardware or software services such as services 1432, 1434, and 1436 stored in storage device 1430 configured to control processor 1410, and special purpose processors where software instructions are embedded into the actual processor design. Processor 1410 may essentially be a completely self-contained computing system including multiple cores or processors, buses, memory controllers, caches, etc. Multi-core processors may be symmetric or asymmetric.

[0211]

[0226] To enable user interaction, computing system 1400 includes input devices 1445, which may represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, a keyboard, a mouse, motion input, speech, etc. Computing system 1400 may also include output devices 1435, which may be one or more of several output mechanisms. In some cases, a multimodal system may enable a user to provide multiple types of input / output to communicate with computing system 1400.

[0212]

[0227] Computing system 1400 may include a communications interface 1440, which may generally control and manage user input and system output. The communications interface may be an audio jack / plug, a microphone jack / plug, a universal serial bus (USB) port / plug, an Apple™ Lightning™ port / plug, an Ethernet port / plug, an optical fiber port / plug, a proprietary wired port / plug, 3G, 4G, 5G, and / or other cellular data network wireless signal transmissions, Bluetooth™ wireless signal transmissions, Bluetooth™ low energy (BLE) wireless signal transmissions, IBEACON™ wireless signal transmissions, radio-frequency identification (RFID) wireless signal transmissions, near-field communications (NFC) wireless signal transmissions, dedicated short range communication (DSRC) wireless signal transmissions, 802.11 Wi-Fi wireless signal transmissions, wireless local area network (WLAN) signal transmissions, Visible Light Communication (VLC), Worldwide Interoperability for Microwave Access (WiMAX), infrared (IR) communication wireless signal transmissions, Public Switched Telephone Network (PSTN) wireless signal transmissions, and the like. The wireless communication device may perform or facilitate the reception and / or transmission of wired or wireless communications using wired and / or wireless transceivers, including those utilizing PSTN (Professional Services Digital Network) signal transmissions, Integrated Services Digital Network (ISDN) signal transmissions, ad-hoc network signal transmissions, radio wave signal transmissions, microwave signal transmissions, infrared signal transmissions, visible light signal transmissions, ultraviolet light signal transmissions, wireless signal transmissions along the electromagnetic spectrum, or any combination thereof.The communication interface 1440 may also include one or more GNSS receivers or transceivers used to determine the location of the computing system 1400 based on reception of one or more signals from one or more satellites associated with one or more Global Navigation Satellite System (GNSS) systems. GNSS systems include, but are not limited to, the United States Global Positioning System (GPS), the Russian Global Navigation Satellite System (GLONASS), the Chinese BeiDou Navigation Satellite system (BDS), and the European Galileo GNSS. There is no constraint to operate with any particular hardware configuration, and therefore the basic features herein may be easily replaced with improved hardware or firmware configurations as they are developed.

[0213]

[0228] The storage device 1430 can be a non-volatile and / or non-transitory and / or computer readable memory device, such as a hard disk, or a magnetic cassette, a flash memory card, a solid state memory device, a digital versatile disk, a cartridge, a floppy disk, a flexible disk, a hard disk, a magnetic tape, a magnetic strip / stripe, any other magnetic storage medium, a flash memory, a memristor memory, any other solid state memory, a compact disc read only memory (CD-ROM) optical disk, a rewritable compact disc (CD) optical disk, a digital video disk (DVD) optical disk, a blu-ray disc (BDD) optical disk, a holographic optical disk, other optical media, a secure digital (SD) card, a micro secure digital (microSD) card, a Memory Stick® card, a smart card chip, an EMV chip, a subscriber identity module (SID), a module, SIM card, mini / micro / nano / pico SIM card, other integrated circuit (IC) chips / cards, random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-onlyThe memory may be another type of computer readable medium capable of storing data accessible by a computer, such as a level 1 (L1) cache, a level 2 (L2) cache, a level 3 (L3) cache, a level 4 (L4) cache, a level 5 (L5) cache, or other (L#) cache, a resistive random-access memory (RRAM / ReRAM), a phase change memory (PCM), a spin transfer torque RAM (STT-RAM), other memory chips or cartridges, and / or combinations thereof.

[0214]

[0229] Storage devices 1430 may include software services, servers, services, etc., where code defining such software, when executed by processor 1410, causes the system to perform a function. In some aspects, hardware services performing a particular function may include software components stored in a computer-readable medium in association with necessary hardware components, such as processor 1410, connections 1405, output devices 1435, etc., to perform that function. The term "computer-readable medium" includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other media that can store, store, or convey instruction(s) and / or data. Computer-readable media may include non-transitory media on which data may be stored and that do not include carrier waves and / or transitory electronic signals propagating wirelessly or over wired connections. Examples of non-transitory media may include, but are not limited to, magnetic disks or tapes, optical storage media such as compact disks (CDs) or digital versatile disks (DVDs), flash memory, memories, or memory devices. A computer-readable medium may have code and / or machine-executable instructions stored thereon, which may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.

[0215]

[0230] Although specific details have been given in the above description to provide a thorough understanding of the aspects and examples provided herein, those skilled in the art will appreciate that the present application is not limited thereto. Thus, while exemplary aspects of the present application have been described in detail herein, it should be understood that the inventive concept may be embodied and employed in various other ways, and that the appended claims are intended to be construed to include such variations, except as limited by the prior art. The various features and aspects of the present application described above may be used individually or jointly. Moreover, the aspects may be utilized in any number of environments and applications other than those described herein without departing from the broader scope of the present specification. Thus, the present specification and drawings should be regarded as illustrative and not restrictive. For purposes of illustration, the methods have been described in a particular order. It should be understood that in alternative aspects, the methods may be performed in an order different from that described.

[0216]

[0231] For clarity of explanation, in some instances, the technology may be presented as including individual functional blocks comprising devices, device components, and method steps or routines embodied in software or a combination of hardware and software. Additional components other than those shown in the figures and / or described herein may be used. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form so as not to obscure the aspects in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail so as to avoid obscuring the aspects.

[0217]

[0232] Moreover, those skilled in the art will appreciate that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0218]

[0233] Individual aspects may be described above as a process or method that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although the flowcharts may describe operations as a sequential process, many of the operations may be performed in parallel or simultaneously. In addition, the order of operations may be rearranged. A process terminates when its operations are completed, but may have additional steps not included in the diagram. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or to the main function.

[0219]

[0234] The processes and methods according to the examples described above may be implemented using computer-executable instructions stored on or otherwise available from a computer-readable medium. Such instructions may include, for example, instructions and data that cause a general-purpose computer, a special-purpose computer, or a processing device to perform a particular function or group of functions, or otherwise configure a general-purpose computer, a special-purpose computer, or a processing device to perform a particular function or group of functions. Portions of the computer resources used may be accessible over a network. The computer-executable instructions may be, for example, binary, intermediate format instructions such as assembly language, firmware, source code, etc. Examples of computer-readable media that may be used to store instructions, information used, and / or information created during the methods according to the described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, network-attached storage devices, etc.

[0220]

[0235] In some aspects, computer-readable storage devices, media, and memories may include cables or wireless signals containing bit streams, etc. However, when mentioned, non-transitory computer-readable storage media specifically excludes media such as energy, carrier signals, electromagnetic waves, and the signals themselves.

[0221]

[0236] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular application, desired design, corresponding technology, etc.

[0222]

[0237] The various example logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed using hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof, and may take any of a variety of form factors. When implemented in software, firmware, middleware, or microcode, the program code or code segments (e.g., computer program product) performing the necessary tasks may be stored in a computer-readable or machine-readable medium. A processor or processors may perform the necessary tasks. Examples of form factors include laptops, smartphones, mobile phones, tablet devices or other small form factor personal computers, personal digital assistants, rack-mounted devices, standalone devices, and the like. The functionality described herein may also be embodied in a peripheral device or an add-in card. Such functionality may also be implemented on a circuit board among different chips, or on different processes executing in a single device, as further examples.

[0223]

[0238] The instructions, media for carrying such instructions, computing resources for executing such instructions, and other structures supporting such computing resources are exemplary means for providing the functionality described in this disclosure.

[0224]

[0239] The techniques described herein may also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such techniques may be implemented in any of a variety of devices, such as a general purpose computer, a wireless communication device handset, or an integrated circuit device having multiple uses, including applications in wireless communication device handsets and other devices. Any features described as modules or components may be implemented together in an integrated logic device, or separately as discrete but interoperable logic devices. If implemented in software, these techniques may be realized at least in part by a computer-readable data storage medium that includes program code that includes instructions that, when executed, perform one or more of the methods, algorithms, and / or operations described above. The computer-readable data storage medium may form part of a computer program product, which may include packaging materials. The computer-readable medium may comprise a memory or data storage medium, such as random access memory (RAM), such as synchronous dynamic random access memory (SDRAM), read only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read only memory (EEPROM), FLASH memory, magnetic or optical data storage medium, etc. The techniques may additionally or alternatively be realized at least in part by a computer-readable communications medium, such as a propagated signal or wave, that carries or communicates program code in the form of instructions or data structures and that can be accessed, read, and / or executed by a computer.

[0225]

[0240] The program code may be executed by a processor, which may include one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Such a processor may be configured to perform any of the techniques described in this disclosure. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Thus, the term "processor" as used herein may refer to any of the above structures, any combination of the above structures, or any other structure or apparatus suitable for implementing the techniques described herein.

[0226]

[0241] Those skilled in the art will understand that the less than ("<") and greater than (">") symbols or terminology used herein may be replaced with the less than or equal to ("≦") and greater than or equal to ("≧") symbols, respectively, without departing from the scope of the present specification.

[0227]

[0242] When a component is described as being "configured to" perform certain operations, such configuration may be achieved, for example, by designing electronic circuitry or other hardware to perform the operations, by programming a programmable electronic circuitry (e.g., a microprocessor or other suitable electronic circuitry) to perform the operations, or any combination thereof.

[0228]

[0243] The phrases "coupled to" or "communicatively coupled to" refer to any component that is physically connected, either directly or indirectly, to another component and / or that is in either direct or indirect communication with another component (e.g., connected to the other component via a wired or wireless connection, and / or other suitable communications interface).

[0229]

[0244] Claim language or other language reciting "at least one of" a set and / or "one or more" of a set indicates that one member of the set or multiple members of the set (in any combination) satisfy the claim. For example, a claim language reciting "at least one of A and B" or "at least one of A or B" means A, B, or A and B. In another example, a claim language reciting "at least one of A, B, and C" or "at least one of A, B, or C" means A, B, C, or A and B, or A and C, or B and C, A and B and C, or any overlapping information or data (e.g., A and A, B and B, C and C, A and A and B, etc.), or any other permutation, duplication, or combination of A, B, and C. The language "at least one of" a set and / or "one or more" of a set does not limit the set to the items listed in the set. For example, claim language reciting "at least one of A and B" or "at least one of A or B" may mean A, B, or A and B, and may further include unrecited items within the set of A and B.

[0230]

[0245] Exemplary aspects of the present disclosure include the following.

[0231]

[0246] Aspect 1. A method for wireless communication in a user equipment (UE), comprising: receiving a plurality of downlink communications, each downlink communication of the plurality of downlink communications associated with a hybrid automatic repeat request (HARQ) process; determining one or more uplink communications, each uplink communication of the one or more uplink communications including feedback associated with at least one downlink communication of the plurality of downlink communications; and transmitting the one or more uplink communications based on an uplink communication transmission configuration, the uplink communication transmission configuration determined based on a type of each downlink communication of the plurality of downlink communications.

[0232]

[0247] Aspect 2. The method of aspect 1, wherein the multiple downlink communications include one or more feedback-enabled transport blocks (TBs), each feedback-enabled TB of the one or more feedback-enabled TBs being associated with a HARQ feedback-enabled process, and the one or more feedback-enabled TBs are received according to multi-TB scheduling based on downlink control information (DCI) associated with the multi-TB scheduling.

[0233]

[0248] Aspect 3. The method of aspect 2, wherein the one or more uplink communications include HARQ feedback that has been determined for each feedback enabled TB of the one or more feedback enabled TBs, and a first uplink slot of the uplink communication transmission configuration is later than a last downlink slot associated with receiving the one or more feedback enabled TBs using multi-TB scheduling.

[0234]

[0249] Aspect 4. The method of aspect 2 or 3, further comprising receiving one or more feedback disabled TBs, each feedback disabled TB being associated with a HARQ feedback disabled process and received without using multi-TB scheduling.

[0235]

[0250] Aspect 5. The method of any of aspects 1 to 4, wherein the multiple downlink communications include one or more feedback disabled transport blocks (TBs), each feedback disabled TB being associated with a HARQ feedback disabled process, and the one or more feedback disabled TBs are received using multi-TB scheduling based on downlink control information (DCI) associated with the multi-TB scheduling.

[0236]

[0251] Aspect 6. The method of aspect 5, wherein the one or more uplink communications do not include feedback associated with one or more feedback-disabled TBs.

[0237]

[0252] Aspect 7. The method of any of aspects 1 to 5, wherein the multiple downlink communications include one or more feedback enabled transport blocks (TBs), where each feedback enabled TB of the one or more feedback enabled TBs is associated with a HARQ feedback enabled process, and one or more feedback disabled TBs, where each feedback disabled TB of the one or more feedback disabled TBs is associated with a HARQ feedback disabled process, wherein the one or more feedback enabled TBs and the one or more feedback disabled TBs are received in accordance with multi-TB scheduling based on downlink control information (DCI) associated with the multi-TB scheduling.

[0238]

[0253] Aspect 8. The method of aspect 7, wherein the one or more uplink communications include a respective HARQ feedback determined for each feedback-enabled TB of the one or more feedback-enabled TBs and a respective placeholder feedback determined for each feedback-disabled TB of the one or more feedback-disabled TBs.

[0239]

[0254] Aspect 9. The method of aspect 8, further comprising: determining an uplink communication transmission configuration based on a relative order associated with receiving one or more feedback enabled TBs and one or more feedback disabled TBs; and transmitting HARQ feedback and placeholder feedback using the same relative order associated with receiving one or more feedback enabled TBs and one or more feedback disabled TBs.

[0240]

[0255] Aspect 10. The method of any of aspects 7 to 9, wherein the one or more uplink communications include HARQ feedback determined for each feedback-enabled TB of the one or more feedback-enabled TBs, but do not include feedback associated with one or more feedback-disabled TBs.

[0241]

[0256] The method of embodiment 10, further comprising: determining an uplink communication transmission configuration based on a relative order associated with receiving one or more feedback-enabled TBs and one or more feedback-disabled TBs, wherein the uplink communication transmission configuration is determined by: for each feedback-enabled TB included in the relative order, generating a HARQ feedback transmission time interval associated with the HARQ feedback determined for the feedback-enabled TB; and for each feedback-disabled TB included in the relative order, generating an empty uplink transmission time interval associated with the feedback-disabled TB.

[0242]

[0257] Aspect 12. The method of aspect 10 or 11, wherein transmitting one or more uplink communications includes transmitting HARQ feedback that has been determined for each feedback enabled TB of the one or more feedback enabled TBs, where the HARQ feedback is transmitted in the same relative order associated with receiving the one or more feedback enabled TBs, the relative order not including the one or more feedback disabled TBs, and where the HARQ feedback is transmitted without reserving one or more uplink transmission time intervals for the one or more feedback disabled TBs.

[0243]

[0258] Aspect 13. A method according to any of aspects 7 to 12, wherein the one or more feedback-enabled TBs and the one or more feedback-disabled TBs are received as one or more TB bundles, where each feedback-enabled TB and each feedback-disabled TB is included in only one TB bundle of the one or more TB bundles, and the one or more TB bundles include at least one of feedback-enabled TB bundles, where each feedback-enabled TB bundle includes at least one feedback-enabled TB, and feedback-disabled TB bundles, where each feedback-disabled TB bundle does not include any feedback-enabled TB.

[0244]

[0259] The method of embodiment 13, wherein determining the one or more uplink communications further includes: for each feedback-enabled TB bundle of the one or more TB bundles, generating a respective HARQ feedback for each feedback-enabled TB included in the feedback-enabled TB bundle; generating a respective placeholder feedback for each feedback-disabled TB included in the feedback-enabled TB bundle; and determining a bundled HARQ feedback based on the respective HARQ feedback and the respective placeholder feedback, wherein the one or more uplink communications include the bundled HARQ feedback.

[0245]

[0260] Aspect 15. The method of aspect 14, wherein determining the bundled HARQ feedback includes computing a logical AND between each HARQ feedback and each placeholder feedback.

[0246]

[0261] Aspect 16. The method of aspect 15, wherein the placeholder feedback includes an acknowledgment (ACK) or a logical one value.

[0247]

[0262] Aspect 17. The method of any of aspects 14 to 16, further comprising determining an uplink communication transmission configuration based on a relative order associated with receiving one or more TB bundles, wherein the uplink communication transmission configuration is determined by: for each given feedback-enabled TB bundle included in the relative order, generating a HARQ feedback transmission time interval associated with the bundled HARQ feedback determined for the given feedback-enabled TB bundle; and for each given feedback-disabled TB bundle included in the relative order, generating an empty uplink transmission time interval associated with the given feedback-disabled TB bundle.

[0248]

[0263] Aspect 18. The method of any of aspects 14 to 17, wherein transmitting one or more uplink communications includes transmitting bundled HARQ feedback that has been determined for each feedback-enabled TB of the one or more TB bundles, the bundled HARQ feedback being transmitted in the same relative order associated with receiving the one or more TB bundles, the relative order not including the one or more feedback-disabled TB bundles, and the bundled HARQ feedback being transmitted without reserving one or more uplink transmission time intervals for the one or more feedback-disabled TB bundles.

[0249]

[0264] Embodiment 19. The method of any of embodiments 13 to 18, wherein the one or more TB bundles are determined using a particular TB bundling configuration selected from a plurality of TB bundling configurations.

[0250]

[0265] Aspect 20. The method of aspect 19, wherein the particular TB bundling configuration is determined based on receiving a radio resource control (RRC) downlink communication or a medium access control-control element (MAC-CE) downlink communication.

[0251]

[0266] Aspect 21. The method of any of aspects 1 to 20, wherein one or more of the plurality of downlink communications are received by an enhanced machine type communication (eMTC) UE, or one or more of the one or more uplink communications are transmitted by an eMTC UE.

[0252]

[0267] Aspect 22. The method of aspect 21, wherein an eMTC UE receives one or more of a plurality of downlink communications using a non-terrestrial network (NTN), or the eMTC UE transmits one or more uplink communications using the NTN.

[0253]

[0268] Aspect 23. The method of any of aspects 1 to 22, further comprising: receiving a first Physical Downlink Shared Channel (PDSCH) communication including at least a first downlink communication of the plurality of downlink communications, the first downlink communication including a transport block (TB) associated with a feedback disabled HARQ process; and receiving a second PDSCH communication including at least an additional downlink communication, the additional downlink communication including an additional TB associated with the feedback disabled HARQ process, wherein the first PDSCH communication and the second PDSCH communication are separated by a predefined time interval.

[0254]

[0269] Aspect 24. The method of aspect 23, wherein the UE is an eMTC UE or a Band-Limited or Coverage Enhanced (BL / CE) UE, and the predefined time interval is 4 milliseconds.

[0255]

[0270] Aspect 25. The method of any of aspects 1 to 24, wherein one or more of the downlink communications are received by a Narrowband Internet of Things (NB-IoT) UE or one or more of the uplink communications are transmitted by a NB-IoT network.

[0256]

[0271] Aspect 26. The method of aspect 25, wherein the one or more downlink communications are associated with up to four HARQ processes, the up to four HARQ processes including a subset of up to two feedback-enabled HARQ processes, and one or more HARQ processes of the up to four HARQ processes that are not included in the subset are feedback-disabled HARQ processes.

[0257]

[0272] Aspect 27. The method of aspect 26, further comprising storing a feedback enable TB associated with each feedback enabled HARQ process included in the subset of up to two feedback enabled HARQ processes in a soft buffer associated with the UE.

[0258]

[0273] Aspect 28. The method of aspect 27, further comprising determining whether soft buffer storage is required for each HARQ process of the up to four HARQ processes based on dedicated downlink control information (DCI) bits associated with the up to four HARQ processes, wherein a first value of the DCI bits indicates that soft buffer storage is required for each feedback-enabled HARQ process included in the subset, or wherein a second value of the DCI bits indicates that soft buffer storage is not required for feedback-disabled HARQ processes not included in the subset.

[0259]

[0274] Aspect 29. The method of aspect 27 or 28, further comprising determining whether each HARQ process of the up to four HARQ processes is a feedback-enabled HARQ process or a feedback-disabled HARQ process based on a dedicated DCI bit associated with the up to four HARQ processes, where a first value of the DCI bit is used for the feedback-enabled HARQ process and a second value of the DCI bit is used for the feedback-disabled HARQ process.

[0260]

[0275] Example 30. The method of example 28 or 29, further comprising using a dedicated DCI bit to implicitly or explicitly indicate a HARQ process ID number for each HARQ process of up to four HARQ processes.

[0261]

[0276] Aspect 31. The method of any of aspects 1 to 30, wherein a plurality of downlink communications are received from a network entity and one or more uplink communications are transmitted to the network entity.

[0262]

[0277] Example 32. The method of example 31, wherein the network entity is a base station.

[0263]

[0278] Aspect 33. The method of aspect 32, wherein the base station is one of a next generation node B (gNB) or an evolved node B (eNB).

[0264]

[0279] Aspect 34. The method of any one of aspects 31 to 33, wherein the network entity is at least one of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near-real-time (Near-RT) RAN intelligent controller (RIC), or a non-real-time (Non-RT) RIC of a base station.

[0265]

[0280] Aspect 35. The method of any of aspects 31 to 34, wherein the network entity is a non-terrestrial network (NTN) entity.

[0266]

[0281] Aspect 36. The method of aspect 35, wherein the NTN entity is a satellite.

[0267]

[0282] Aspect 37. A method of wireless communication in a user equipment (UE), comprising: receiving a first physical downlink shared channel (PDSCH) communication including at least a first downlink communication of a plurality of downlink communications, the first downlink communication including a transport block (TB) associated with a first feedback disabled hybrid automatic repeat request (HARQ) process; and receiving a second PDSCH communication including at least an additional downlink communication, the additional downlink communication including an additional TB associated with the first feedback disabled HARQ process, wherein the first PDSCH communication and the second PDSCH communication are separated by a predefined time interval.

[0268]

[0283] Aspect 38. The method of aspect 37, wherein the UE is an eMTC UE or a band restricted or coverage extended (BL / CE) UE, and the predefined time interval is 4 milliseconds.

[0269]

[0284] Aspect 39. A method of wireless communication in a narrowband Internet of Things (NB-IoT) user equipment (UE), comprising receiving, in the narrowband Internet of Things (NB-IoT) UE, a plurality of downlink communications, the plurality of downlink communications being associated with up to four HARQ processes, the up to four HARQ processes including a subset of up to two feedback-enabled HARQ processes, and one or more HARQ processes of the up to four HARQ processes not included in the subset being feedback-disabled HARQ processes.

[0270]

[0285] Aspect 40. The method of aspect 39, further comprising storing a feedback enable TB associated with each feedback enabled HARQ process included in the subset of up to two feedback enabled HARQ processes in a soft buffer associated with the UE.

[0271]

[0286] Aspect 41. The method of aspect 40, further comprising determining whether soft buffer storage is required for each HARQ process of the up to four HARQ processes based on dedicated downlink control information (DCI) bits associated with the up to four HARQ processes, wherein a first value of the DCI bits indicates that soft buffer storage is required for each feedback-enabled HARQ process included in the subset, or wherein a second value of the DCI bits indicates that soft buffer storage is not required for feedback-disabled HARQ processes not included in the subset.

[0272]

[0287] Aspect 42. The method of aspect 40 or 41, further comprising determining whether each HARQ process of the up to four HARQ processes is a feedback-enabled HARQ process or a feedback-disabled HARQ process based on a dedicated DCI bit associated with the up to four HARQ processes, where a first value of the DCI bit is used for the feedback-enabled HARQ process and a second value of the DCI bit is used for the feedback-disabled HARQ process, and where the HARQ process associated with the first value of the DCI bit is stored in a soft buffer.

[0273]

[0288] Example 43. The method of example 41 or 42, further comprising using a dedicated DCI bit to implicitly indicate a HARQ process ID number for each HARQ process of up to four HARQ processes.

[0274]

[0289] Aspect 44. The method of any of aspects 2 to 43, further comprising: determining a last scheduled TB for which HARQ feedback is enabled; and starting a HARQ round trip time (RTT) timer from the end of the last scheduled TB for which HARQ feedback is enabled.

[0275]

[0290] Aspect 45. A narrowband Internet of Things (NB-IoT) UE may set the duration of the HARQ RTT timer to k+(2-X) * (N+1)+RTT offset +delta PDCCH wherein k is determined as an interval between a last subframe associated with receiving a plurality of downlink communications and a first subframe associated with transmitting one or more uplink communications, N is determined as a transmission duration associated with transmitting the one or more uplink communications, the transmission duration comprising a number of subframes, and X is determined as a number of feedback disable TBs.

[0276]

[0291] Aspect 46. An enhanced machine type communication (eMTC) UE with HARQ-ACK bundling enabled may set the duration of the HARQ RTT timer to 7+(kX). * N+RTT offset 46. ​​The method of claim 44 or 45, further comprising determining, as N = k = 1, where N is determined as a repetition factor of a physical uplink communication channel (PUCCH), k is a number of HARQ feedback bundles associated with the HARQ-ACK bundling, and X is determined as a number of feedback null bundles.

[0277]

[0292] 47. k is the ceiling (N TB / M), where N TB47. The method of embodiment 46, wherein M is determined as a number of scheduled TBs indicated in a physical downlink communication channel (PDCCH) wireless communication, and M is determined as a multi-TB HARQ-ACK bundling size.

[0278]

[0293] Aspect 48. An enhanced machine type communication (eMTC) UE with HARQ-ACK bundling disabled may set the duration of the HARQ RTT timer to 7+(mX). * N+RTT offset 48. The method of any of aspects 44 to 47, further comprising determining, as N = m = 1, where N is determined as a repetition factor of a physical uplink communication channel (PUCCH), m is determined as a number of scheduled TBs included in a physical downlink communication channel (PDCCH) wireless communication, and X is determined as a number of feedback disabled TBs.

[0279]

[0294] Aspect 49. The apparatus of any of aspects 7 to 48, wherein the multi-TB scheduling includes one or more feedback enabled TBs prior to one or more feedback disabled TBs, and a last transmission time interval associated with the one or more feedback enabled TBs is earlier than a first transmission time interval associated with the one or more feedback disabled TBs.

[0280]

[0295] Aspect 50. The method of aspect 49, wherein the one or more uplink communications include a respective HARQ feedback determined for each feedback-enabled TB of the one or more feedback-enabled TBs, and at least a portion of the one or more uplink communications are transmitted after a last transmission time interval associated with the one or more feedback-enabled TBs.

[0281]

[0296] Aspect 51. The method of aspect 50, wherein at least a portion of the one or more uplink communications are transmitted prior to a last transmission time interval associated with one or more feedback disable TBs.

[0282]

[0297] Aspect 52. The method of any of aspects 1 to 51, wherein the multiple downlink communications include at least one feedback-enabled transport block (TB) associated with a first HARQ process and at least one feedback-disabled TB associated with a second HARQ process, wherein the at least one feedback-enabled TB and the at least one feedback-disabled TB are scheduled in a single TB.

[0283]

[0298] Aspect 53. The method of aspect 52, further comprising using a DCI override bit to configure at least one feedback-enabled TB as a feedback-disabled TB, or using a DCI override bit to configure at least one feedback-disabled TB as a feedback-enabled TB.

[0284]

[0299] Aspect 54. The method of aspect 53, further comprising determining whether soft buffer storage is required for each HARQ process of the up to four HARQ processes based on dedicated downlink control information (DCI) bits associated with the up to four HARQ processes, wherein a first value of the DCI bits indicates that soft buffer storage is required for each feedback-enabled HARQ process included in the subset, or wherein a second value of the DCI bits indicates that soft buffer storage is not required for feedback-disabled HARQ processes not included in the subset.

[0285]

[0300] Aspect 55. The method of aspect 53 or 54, wherein the DCI override bit is a HARQ ACK bundling flag.

[0286]

[0301] Aspect 56. An apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to receive a plurality of downlink communications, where each downlink communication of the plurality of downlink communications is associated with a hybrid automatic repeat request (HARQ) process; determine one or more uplink communications, where each uplink communication of the one or more uplink communications includes feedback associated with at least one downlink communication of the plurality of downlink communications; and transmit the one or more uplink communications based on an uplink communication transmission configuration, where the uplink communication transmission configuration is determined based on a type of each downlink communication of the plurality of downlink communications.

[0287]

[0302] Aspect 57. The apparatus of aspect 56, wherein the multiple downlink communications include one or more feedback enabled transport blocks (TBs), each feedback enabled TB of the one or more feedback enabled TBs being associated with a HARQ feedback enabled process, and the one or more feedback enabled TBs being received according to multi-TB scheduling based on downlink control information (DCI) associated with the multi-TB scheduling.

[0288]

[0303] Aspect 58. The apparatus of aspect 57, wherein the one or more uplink communications include HARQ feedback that has been determined for each feedback-enabled TB of the one or more feedback-enabled TBs, and a first uplink slot of the uplink communication transmission configuration is later than a last downlink slot associated with receiving the one or more feedback-enabled TBs using multi-TB scheduling.

[0289]

[0304] Aspect 59. The apparatus of aspect 57 or 58, wherein the at least one processor is further configured to receive one or more feedback disabled TBs, each feedback disabled TB associated with a HARQ feedback disabled process and received without using multi-TB scheduling.

[0290]

[0305] Aspect 60. The apparatus of any of aspects 56 to 59, wherein the multiple downlink communications include one or more feedback disabled transport blocks (TBs), each feedback disabled TB being associated with a HARQ feedback disabled process, and the one or more feedback disabled TBs are received using multi-TB scheduling based on downlink control information (DCI) associated with the multi-TB scheduling.

[0291]

[0306] Aspect 61. The apparatus of aspect 60, wherein the one or more uplink communications do not include feedback associated with one or more feedback-disabled TBs.

[0292]

[0307] Aspect 62. The apparatus of any of aspects 56 to 61, wherein the multiple downlink communications include one or more feedback enabled transport blocks (TBs), where each feedback enabled TB of the one or more feedback enabled TBs is associated with a HARQ feedback enabled process, and one or more feedback disabled TBs, where each feedback disabled TB of the one or more feedback disabled TBs is associated with a HARQ feedback disabled process, wherein the one or more feedback enabled TBs and the one or more feedback disabled TBs are received in accordance with multi-TB scheduling based on downlink control information (DCI) associated with the multi-TB scheduling.

[0293]

[0308] Aspect 63. The apparatus of aspect 62, wherein the one or more uplink communications include a respective HARQ feedback determined for each feedback-enabled TB of the one or more feedback-enabled TBs and a respective placeholder feedback determined for each feedback-disabled TB of the one or more feedback-disabled TBs.

[0294]

[0309] Aspect 64. The apparatus of aspect 63, wherein the at least one processor is further configured to determine an uplink communication transmission configuration based on a relative order associated with receiving one or more feedback enabled TBs and one or more feedback disabled TBs, and to transmit HARQ feedback and placeholder feedback using the same relative order associated with receiving the one or more feedback enabled TBs and one or more feedback disabled TBs.

[0295]

[0310] Aspect 65. The apparatus of any of aspects 62 to 64, wherein the one or more uplink communications include HARQ feedback determined for each feedback-enabled TB of the one or more feedback-enabled TBs, and do not include feedback associated with the one or more feedback-disabled TBs.

[0296]

[0311] Aspect 66. The apparatus of aspect 65, wherein the at least one processor is further configured to determine an uplink communication transmission configuration based on a relative order associated with receiving one or more feedback-enabled TBs and one or more feedback-disabled TBs, wherein the uplink communication transmission configuration is determined by: for each feedback-enabled TB included in the relative order, generating a HARQ feedback transmission time interval associated with the HARQ feedback determined for the feedback-enabled TB; and for each feedback-disabled TB included in the relative order, generating an empty uplink transmission time interval associated with the feedback-disabled TB.

[0297]

[0312] The apparatus of aspect 65 or 66, wherein transmitting one or more uplink communications includes transmitting HARQ feedback that has been determined for each feedback enabled TB of the one or more feedback enabled TBs, where the HARQ feedback is transmitted in the same relative order associated with receiving the one or more feedback enabled TBs, the relative order not including the one or more feedback disabled TBs, and where the HARQ feedback is transmitted without reserving one or more uplink transmission time intervals for the one or more feedback disabled TBs.

[0298]

[0313] Aspect 68. An apparatus described in any of aspects 62 to 67, wherein the one or more feedback-enabled TBs and the one or more feedback-disabled TBs are received as one or more TB bundles, where each feedback-enabled TB and each feedback-disabled TB is included in only one TB bundle of the one or more TB bundles, and the one or more TB bundles include at least one of feedback-enabled TB bundles, where each feedback-enabled TB bundle includes at least one feedback-enabled TB, and feedback-disabled TB bundles, where each feedback-disabled TB bundle does not include any feedback-enabled TBs.

[0299]

[0314] The apparatus of aspect 68, wherein to determine the one or more uplink communications, the at least one processor is further configured to: for each feedback-enabled TB bundle of the one or more TB bundles, generate a respective HARQ feedback for each feedback-enabled TB included in the feedback-enabled TB bundle, generate a respective placeholder feedback for each feedback-disabled TB included in the feedback-enabled TB bundle, and determine a bundled HARQ feedback based on the respective HARQ feedback and the respective placeholder feedback, wherein the one or more uplink communications include the bundled HARQ feedback.

[0300]

[0315] Aspect 70. The apparatus of aspect 69, wherein to determine the bundled HARQ feedback, the at least one processor is configured to calculate a logical AND between each HARQ feedback and each placeholder feedback.

[0301]

[0316] Aspect 71. The apparatus of aspect 70, wherein the placeholder feedback includes an acknowledgment (ACK) or a logical one value.

[0302]

[0317] Aspect 72. The apparatus of any of aspects 68 to 71, wherein the at least one processor is further configured to determine an uplink communication transmission configuration based on a relative order associated with receiving one or more TB bundles, wherein the uplink communication transmission configuration is determined by: for each given feedback-enabled TB bundle included in the relative order, generating a HARQ feedback transmission time interval associated with the bundled HARQ feedback determined for the given feedback-enabled TB bundle; and for each given feedback-disabled TB bundle included in the relative order, generating an empty uplink transmission time interval associated with the given feedback-disabled TB bundle.

[0303]

[0318] Aspect 73. The apparatus of any of aspects 68 to 72, wherein to transmit one or more uplink communications, at least one processor is configured to transmit bundled HARQ feedback, the bundled HARQ feedback being determined for each feedback-enabled TB of the one or more TB bundles, the bundled HARQ feedback being transmitted in the same relative order associated with receiving the one or more TB bundles, the relative order not including the one or more feedback-disabled TB bundles, and the bundled HARQ feedback being transmitted without reserving one or more uplink transmission time intervals for the one or more feedback-disabled TB bundles.

[0304]

[0319] Aspect 74. An apparatus according to any of aspects 67 to 73, wherein to determine one or more TB bundles, at least one processor is configured to determine a particular TB bundling configuration selected from a plurality of TB bundling configurations.

[0305]

[0320] Aspect 75. The apparatus of aspect 74, wherein the at least one processor is configured to determine a particular TB bundling configuration based on receiving a radio resource control (RRC) downlink communication or a medium access control-control element (MAC-CE) downlink communication.

[0306]

[0321] Aspect 76. The apparatus of any of aspects 56 to 75, wherein one or more of the downlink communications are received by an enhanced machine type communication (eMTC) UE or one or more of the uplink communications are transmitted by an eMTC UE.

[0307]

[0322] Aspect 77. The apparatus of aspect 76, wherein the eMTC UE receives one or more of a plurality of downlink communications using a non-terrestrial network (NTN), or the eMTC UE transmits one or more uplink communications using the NTN.

[0308]

[0323] Aspect 78. The apparatus of any of aspects 56 to 77, wherein the at least one processor is further configured to receive a first physical downlink shared channel (PDSCH) communication including at least a first downlink communication of the plurality of downlink communications, the first downlink communication including a transport block (TB) associated with the feedback disabled HARQ process, and a second PDSCH communication including at least an additional downlink communication including an additional TB associated with the feedback disabled HARQ process, wherein the first PDSCH communication and the second PDSCH communication are separated by a predefined time interval.

[0309]

[0324] Aspect 79. The apparatus of aspect 78, wherein the UE is an eMTC UE or a band-restricted or coverage-enhanced (BL / CE) UE, and the predefined time interval is 4 milliseconds.

[0310]

[0325] Aspect 80. The apparatus of any of aspects 56 to 79, wherein one or more of the downlink communications are received by a Narrowband Internet of Things (NB-IoT) UE or one or more of the uplink communications are transmitted by a NB-IoT network.

[0311]

[0326] Aspect 81. The apparatus of aspect 80, wherein the one or more downlink communications are associated with up to four HARQ processes, the up to four HARQ processes including a subset of up to two feedback-enabled HARQ processes, and one or more HARQ processes of the up to four HARQ processes that are not included in the subset are feedback-disabled HARQ processes.

[0312]

[0327] Aspect 82. The apparatus of aspect 81, wherein the at least one processor is further configured to store a feedback enable TB associated with each feedback enabled HARQ process included in the subset of up to two feedback enabled HARQ processes in a soft buffer associated with the UE.

[0313]

[0328] Aspect 83. The apparatus of aspect 82, wherein the at least one processor is further configured to determine whether soft buffer storage is required for each HARQ process of the up to four HARQ processes based on dedicated downlink control information (DCI) bits associated with the up to four HARQ processes, where a first value of the DCI bits indicates that soft buffer storage is required for each feedback-enabled HARQ process included in the subset, or where a second value of the DCI bits indicates that soft buffer storage is not required for feedback-disabled HARQ processes not included in the subset.

[0314]

[0329] Aspect 84. The apparatus of aspect 82 or 83, wherein the at least one processor is further configured to determine whether each HARQ process of the up to four HARQ processes is a feedback-enabled HARQ process or a feedback-disabled HARQ process based on a dedicated DCI bit associated with the up to four HARQ processes, wherein a first value of the DCI bit is used for the feedback-enabled HARQ process and a second value of the DCI bit is used for the feedback-disabled HARQ process.

[0315]

[0330] Aspect 85. The apparatus of aspect 83 or 84, wherein the at least one processor is further configured to use a dedicated DCI bit to implicitly or explicitly indicate a HARQ process ID number for each HARQ process of the up to four HARQ processes.

[0316]

[0331] Aspect 86. The apparatus of any of aspects 56 to 85, wherein a plurality of downlink communications are received from a network entity and one or more uplink communications are transmitted to the network entity.

[0317]

[0332] Aspect 87. The apparatus of aspect 86, wherein the network entity is a base station.

[0318]

[0333] Aspect 88. The apparatus of aspect 87, wherein the base station is one of a next generation node B (gNB) or an evolved node B (eNB).

[0319]

[0334] Aspect 89. The apparatus of any of aspects 86 to 88, wherein the network entity is at least one of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near-real-time (Near-RT) RAN intelligent controller (RIC), or a non-real-time (Non-RT) RIC of a base station.

[0320]

[0335] Aspect 90. The apparatus of any of aspects 86 to 89, wherein the network entity is a non-terrestrial network (NTN) entity.

[0321]

[0336] Aspect 91. The apparatus of aspect 90, wherein the NTN entity is a satellite.

[0322]

[0337] Aspect 92. An apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to receive a first Physical Downlink Shared Channel (PDSCH) communication including at least a first downlink communication of a plurality of downlink communications, the first downlink communication including a transport block (TB) associated with a first feedback disabled hybrid automatic repeat request (HARQ) process; and receive a second PDSCH communication including at least an additional downlink communication including an additional TB associated with the first feedback disabled HARQ process, wherein the first PDSCH communication and the second PDSCH communication are separated by a predefined time interval.

[0323]

[0338] Aspect 93. The apparatus of aspect 92, wherein the apparatus is an eMTC apparatus or a band-limited or coverage-enhanced (BL / CE) apparatus, and the predefined time interval is 4 milliseconds.

[0324]

[0339] Aspect 94. An apparatus for wireless communication (e.g., a Narrowband Internet of Things (NB-IoT) UE), comprising at least one memory and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to receive a plurality of downlink communications, the plurality of downlink communications being associated with up to four HARQ processes, the up to four HARQ processes including a subset of up to two feedback-enabled HARQ processes, and one or more HARQ processes of the up to four HARQ processes that are not included in the subset are feedback-disabled HARQ processes.

[0325]

[0340] Aspect 95. The apparatus of aspect 94, wherein the at least one processor is further configured to store a feedback enable TB associated with each feedback enabled HARQ process included in the subset of up to two feedback enabled HARQ processes in a soft buffer associated with the UE.

[0326]

[0341] Aspect 96. The apparatus of aspect 95, wherein the at least one processor is further configured to determine whether soft buffer storage is required for each HARQ process of the up to four HARQ processes based on dedicated downlink control information (DCI) bits associated with the up to four HARQ processes, where a first value of the DCI bits indicates that soft buffer storage is required for each feedback-enabled HARQ process included in the subset, or where a second value of the DCI bits indicates that soft buffer storage is not required for feedback-disabled HARQ processes not included in the subset.

[0327]

[0342] Aspect 97. The apparatus of aspect 95 or 96, wherein the at least one processor is further configured to determine whether each HARQ process of the up to four HARQ processes is a feedback-enabled HARQ process or a feedback-disabled HARQ process based on a dedicated DCI bit associated with the up to four HARQ processes, wherein a first value of the DCI bit is used for the feedback-enabled HARQ process and a second value of the DCI bit is used for the feedback-disabled HARQ process, and wherein the HARQ process associated with the first value of the DCI bit is stored in a soft buffer.

[0328]

[0343] Aspect 98. The apparatus of aspect 96 or 97, wherein the at least one processor is further configured to use a dedicated DCI bit to implicitly indicate a HARQ process ID number for each HARQ process of the up to four HARQ processes.

[0329]

[0344] Aspect 99. The apparatus of any of aspects 57 to 98, wherein the at least one processor is further configured to determine a last scheduled TB for which HARQ feedback is enabled and start a HARQ round trip time (RTT) timer from an end of the last scheduled TB for which HARQ feedback is enabled.

[0330]

[0345] At least one processor may be configured to, by a narrowband Internet of Things (NB-IoT) UE, set a duration of a HARQ RTT timer to k+(2-X) * (N+1)+RTT offset +delta PDCCH99. The apparatus of claim 99, further configured to determine, as: k = N + k + 1 where k is determined as an interval between a last subframe associated with receiving a plurality of downlink communications and a first subframe associated with transmitting one or more uplink communications, N is determined as a transmission duration associated with transmitting the one or more uplink communications, the transmission duration comprising a number of subframes, and X is determined as a number of feedback disable TBs.

[0331]

[0346] Aspect 101. At least one processor is configured to, by an enhanced machine type communication (eMTC) UE with HARQ-ACK bundling enabled, set the duration of the HARQ RTT timer to 7+(kX) * N+RTT offset 101. The apparatus of aspect 99 or 100, further configured to determine, where N is determined as a repetition factor of a physical uplink communication channel (PUCCH), k is a number of HARQ feedback bundles associated with the HARQ-ACK bundling, and X is determined as a number of feedback null bundles.

[0332]

[0347] At least one processor may set k to ceiling(N TB / M), wherein N TB 102. The apparatus of aspect 101, wherein Λ is determined as a number of scheduled TBs indicated in a physical downlink communication channel (PDCCH) wireless communication, and M is determined as a multi-TB HARQ-ACK bundling size.

[0333]

[0348] Aspect 103. The at least one processor is configured to, by an enhanced machine type communication (eMTC) UE with HARQ-ACK bundling disabled, set the duration of the HARQ RTT timer to 7+(mX) * N+RTT offset103. The apparatus of any of aspects 99 to 102, further configured to determine, where N is determined as a repetition factor of a physical uplink communication channel (PUCCH), m is determined as a number of scheduled TBs included in a physical downlink communication channel (PDCCH) wireless communication, and X is determined as a number of feedback disabled TBs.

[0334]

[0349] Aspect 104. The apparatus of any of aspects 62 to 103, wherein the multi-TB scheduling includes one or more feedback enabled TBs prior to one or more feedback disabled TBs, and a last transmission time interval associated with the one or more feedback enabled TBs is earlier than a first transmission time interval associated with the one or more feedback disabled TBs.

[0335]

[0350] Aspect 105. The apparatus of aspect 104, wherein the one or more uplink communications include a respective HARQ feedback determined for each feedback enabled TB of the one or more feedback enabled TBs, and at least a portion of the one or more uplink communications are transmitted after a last transmission time interval associated with the one or more feedback enabled TBs.

[0336]

[0351] Aspect 106. The apparatus of aspect 105, wherein the at least one processor is further configured to transmit at least a portion of the one or more uplink communications prior to a last transmission time interval associated with the one or more feedback disable TBs.

[0337]

[0352] Aspect 107. The apparatus of any of aspects 56 to 106, wherein the plurality of downlink communications includes at least one feedback-enabled transport block (TB) associated with a first HARQ process and at least one feedback-disabled TB associated with a second HARQ process, wherein the at least one feedback-enabled TB and the at least one feedback-disabled TB are scheduled in a single TB.

[0338]

[0353] Aspect 108. The apparatus of aspect 107, wherein the at least one processor is further configured to use a DCI override bit to configure at least one feedback-enabled TB as a feedback-disabled TB or to use a DCI override bit to configure at least one feedback-disabled TB as a feedback-enabled TB.

[0339]

[0354] Aspect 109. The apparatus of aspect 108, wherein the at least one processor is further configured to use the DCI override bit to change a radio resource control (RRC) indication feedback behavior for at least one feedback-enabled TB or at least one feedback-disabled TB, respectively.

[0340]

[0355] Aspect 110. An apparatus according to any of aspects 53 to 109, wherein the DCI override bit is a HARQ ACK bundling flag.

[0341]

[0356] Aspect 111. The method of aspect 7, wherein the multi-TB scheduling includes one or more feedback disabled TBs prior to one or more feedback disabled TBs, and a last transmission time interval associated with the one or more feedback disabled TBs is earlier than a first transmission time interval associated with the one or more feedback enabled TBs.

[0342]

[0357] Aspect 112. The apparatus of aspect 62, wherein the multi-TB scheduling includes one or more feedback disabled TBs prior to one or more feedback disabled TBs, and a last transmission time interval associated with the one or more feedback disabled TBs is earlier than a first transmission time interval associated with the one or more feedback enabled TBs.

[0343]

[0358] Aspect 113. The apparatus of aspect 56, wherein the apparatus is configured as a user equipment (UE) and further comprises at least one transceiver configured to receive a plurality of downlink communications and to transmit one or more uplink communications.

[0344]

[0359] Aspect 114. The apparatus of aspect 92, wherein the apparatus is configured as a user equipment (UE) and further comprises at least one transceiver configured to receive the first PDSCH communication and the second PDSCH communication.

[0345]

[0360] Aspect 115. The apparatus of aspect 94, wherein the apparatus is configured as a user equipment (UE) and further comprises at least one transceiver configured to receive a plurality of downlink communications.

[0346]

[0361] Aspect 116. A method for wireless communication in a network entity, comprising: transmitting a plurality of downlink communications, each downlink communication of the plurality of downlink communications associated with a hybrid automatic repeat request (HARQ) process; and receiving one or more uplink communications based on an uplink communication transmission configuration, the uplink communication transmission configuration being based on a type of each downlink communication of the plurality of downlink communications, each uplink communication of the one or more uplink communications including feedback associated with at least one downlink communication of the plurality of downlink communications.

[0347]

[0362] Example 117. The method of example 116, further comprising an operation according to any of examples 2 to 36 and / or examples 44 to 55.

[0348]

[0363] Aspect 118. The method of aspect 116, wherein the network entity is a base station.

[0349]

[0364] Aspect 119. The method of aspect 118, wherein the base station is one of a next generation node B (gNB) or an evolved node B (eNB).

[0350]

[0365] Aspect 120. The method of aspect 116, wherein the network entity is at least one of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near-real-time (Near-RT) RAN intelligent controller (RIC), or a non-real-time (Non-RT) RIC of a base station.

[0351]

[0366] Aspect 121. The method of aspect 116, wherein the network entity is a non-terrestrial network (NTN) entity.

[0352]

[0367] Aspect 122. A method of wireless communication in a network entity, comprising: transmitting, for reception by a user equipment (UE), a first physical downlink shared channel (PDSCH) communication including at least a first downlink communication of a plurality of downlink communications, the first downlink communication including at least a transport block (TB) associated with a first feedback disabled hybrid automatic repeat request (HARQ) process; and transmitting a second PDSCH communication including at least an additional downlink communication, the additional downlink communication including at least an additional TB associated with the first feedback disabled HARQ process, wherein the first PDSCH communication and the second PDSCH communication are separated by a predefined time interval.

[0353]

[0368] Aspect 123. The method of aspect 122, wherein the UE is an eMTC UE or a band-restricted or coverage-enhanced (BL / CE) UE, and the predefined time interval is 4 milliseconds.

[0354]

[0369] Aspect 124. A method of wireless communication in a network entity, comprising: transmitting a plurality of downlink communications to a Narrowband Internet of Things (NB-IoT) user equipment (UE), the plurality of downlink communications being associated with up to four HARQ processes, the maximum four HARQ processes including a subset of up to two feedback-enabled HARQ processes, and one or more HARQ processes of the maximum four HARQ processes not included in the subset being feedback-disabled HARQ processes.

[0355]

[0370]

[0046] Aspect 125. The method of aspect 124, further comprising storing a feedback enable TB associated with each feedback enabled HARQ process included in the subset of up to two feedback enabled HARQ processes in a soft buffer associated with the UE.

[0356]

[0371] Aspect 126. The method of aspect 125, further comprising determining whether soft buffer storage is required for each HARQ process of the up to four HARQ processes based on dedicated downlink control information (DCI) bits associated with the up to four HARQ processes, wherein a first value of the DCI bits indicates that soft buffer storage is required for each feedback-enabled HARQ process included in the subset, or wherein a second value of the DCI bits indicates that soft buffer storage is not required for feedback-disabled HARQ processes not included in the subset.

[0357]

[0372] Aspect 127. The method of aspect 125, further comprising determining whether each HARQ process of the up to four HARQ processes is a feedback-enabled HARQ process or a feedback-disabled HARQ process based on a dedicated DCI bit associated with the up to four HARQ processes, wherein a first value of the DCI bit is used for the feedback-enabled HARQ process and a second value of the DCI bit is used for the feedback-disabled HARQ process, and wherein the HARQ process associated with the first value of the DCI bit is stored in a soft buffer.

[0358]

[0373] Example 128. The method of example 126 or 127, further comprising using a dedicated DCI bit to implicitly indicate a HARQ process ID number for each HARQ process of up to four HARQ processes.

[0359]

[0374] Example 129. The method of example 124, wherein the network entity is a base station.

[0360]

[0375] Aspect 130. The method of aspect 129, wherein the base station is one of a next generation node B (gNB) or an evolved node B (eNB).

[0361]

[0376] Aspect 131. The method of aspect 124, wherein the network entity is at least one of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near-real-time (Near-RT) RAN intelligent controller (RIC), or a non-real-time (Non-RT) RIC of a base station.

[0362]

[0377] Aspect 132. The method of aspect 124, wherein the network entity is a non-terrestrial network (NTN) entity.

[0363]

[0378] Aspect 133. An apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to output a plurality of downlink communications for transmission, each downlink communication of the plurality of downlink communications being associated with a hybrid automatic repeat request (HARQ) process; and receive one or more uplink communications based on an uplink communication transmission configuration, the uplink communication transmission configuration being based on a type of each downlink communication of the plurality of downlink communications, each uplink communication of the one or more uplink communications including feedback associated with at least one downlink communication of the plurality of downlink communications.

[0364]

[0379] Example 134. The apparatus of example 133, further comprising operations according to any of examples 2 to 36 and / or examples 44 to 55.

[0365]

[0380] Aspect 135. The apparatus of aspect 133, wherein the apparatus is implemented as a network entity and further comprises at least one transceiver configured to transmit a plurality of downlink communications and receive one or more uplink communications.

[0366]

[0381] Aspect 136. The apparatus of aspect 135, wherein the network entity is a base station, and the base station includes one of a next generation node B (gNB) or an evolved node B (eNB).

[0367]

[0382] Aspect 137. The apparatus of aspect 135, wherein the network entity is at least one of a base station central unit (CU), a distributed unit (DU), a radio unit (RU), a near-real-time (Near-RT) RAN intelligent controller (RIC), or a non-real-time (Non-RT) RIC.

[0368]

[0383] Aspect 138. The apparatus of aspect 135, wherein the network entity is a non-terrestrial network (NTN) entity.

[0369]

[0384] Aspect 139. An apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to output a first physical downlink shared channel (PDSCH) communication for transmission to a user equipment (UE), the first downlink communication including at least a first downlink communication of a plurality of downlink communications, the first downlink communication including a transport block (TB) associated with a first feedback disabled hybrid automatic repeat request (HARQ) process; and output a second PDSCH communication for transmission, the second PDSCH communication including at least an additional downlink communication including an additional TB associated with the first feedback disabled HARQ process, wherein the first PDSCH communication and the second PDSCH communication are separated by a predefined time interval.

[0370]

[0385] Aspect 140. The apparatus of aspect 139, wherein the UE is an eMTC UE or a band-restricted or coverage-enhanced (BL / CE) UE, and the predefined time interval is 4 milliseconds.

[0371]

[0386] Aspect 141. The apparatus of aspect 139, wherein the apparatus is implemented as a network entity and further comprises at least one transceiver configured to transmit the first PDSCH communication and the second PDSCH communication.

[0372]

[0387] Aspect 142. The method of aspect 141, wherein the network entity is a base station.

[0373]

[0388] Aspect 143. The method of aspect 142, wherein the base station is one of a next generation node B (gNB) or an evolved node B (eNB).

[0374]

[0389] Aspect 144. The method of aspect 141, wherein the network entity is at least one of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near-real-time (Near-RT) RAN intelligent controller (RIC), or a non-real-time (Non-RT) RIC of a base station.

[0375]

[0390] Aspect 145. The method of aspect 141, wherein the network entity is a non-terrestrial network (NTN) entity.

[0376]

[0391] Aspect 146. An apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to output a plurality of downlink communications for transmission to a Narrowband Internet of Things (NB-IoT) user equipment (UE), the plurality of downlink communications being associated with up to four HARQ processes, the up to four HARQ processes including a subset of up to two feedback-enabled HARQ processes, and one or more HARQ processes of the up to four HARQ processes that are not included in the subset are feedback-disabled HARQ processes.

[0377]

[0392]

[0046] Aspect 147. The method of aspect 146, further comprising storing a feedback enable TB associated with each feedback enabled HARQ process included in the subset of up to two feedback enabled HARQ processes in a soft buffer associated with the UE.

[0378]

[0393] Aspect 148. The method of aspect 147, further comprising determining whether soft buffer storage is required for each HARQ process of the up to four HARQ processes based on dedicated downlink control information (DCI) bits associated with the up to four HARQ processes, wherein a first value of the DCI bits indicates that soft buffer storage is required for each feedback-enabled HARQ process included in the subset, or wherein a second value of the DCI bits indicates that soft buffer storage is not required for feedback-disabled HARQ processes not included in the subset.

[0379]

[0394] Aspect 149. The method of aspect 147, further comprising determining whether each HARQ process of the up to four HARQ processes is a feedback-enabled HARQ process or a feedback-disabled HARQ process based on a dedicated DCI bit associated with the up to four HARQ processes, wherein a first value of the DCI bit is used for the feedback-enabled HARQ process and a second value of the DCI bit is used for the feedback-disabled HARQ process, and wherein the HARQ process associated with the first value of the DCI bit is stored in a soft buffer.

[0380]

[0395]

[0046] Example 150. The method of example 148 or 149, further comprising using a dedicated DCI bit to implicitly indicate a HARQ process ID number for each HARQ process of the up to four HARQ processes.

[0381]

[0396] Aspect 151. The apparatus of aspect 146, wherein the apparatus is implemented as a network entity and further comprises at least one transceiver configured to transmit a plurality of downlink communications.

[0382]

[0397] Example 152. The method of example 151, wherein the network entity is a base station.

[0383]

[0398] Aspect 153. The method of aspect 152, wherein the base station is one of a next generation node B (gNB) or an evolved node B (eNB).

[0384]

[0399] Aspect 154. The method of aspect 151, wherein the network entity is at least one of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near-real-time (Near-RT) RAN intelligent controller (RIC), or a non-real-time (Non-RT) RIC of a base station.

[0385]

[0400] Aspect 155. The method of aspect 151, wherein the network entity is a non-terrestrial network (NTN) entity.

Claims

1. A device for wireless communication, At least one memory, The system comprises at least one processor coupled to at least one memory, and the at least one processor is Multiple downlink communications, wherein each of the multiple downlink communications is associated with a Hybrid Automatic Retransmission Request (HARQ) process, and the system receives multiple downlink communications. Determining one or more uplink communications, wherein each uplink communication of the one or more uplink communications includes feedback associated with at least one downlink communication among the plurality of downlink communications, An uplink communication transmission configuration in which the uplink communication transmission configuration transmits one or more uplink communications based on an uplink communication transmission configuration determined based on the type of each of the plurality of downlink communications. It is configured in such a way, The aforementioned multiple downlink communications, One or more feedback-enabled transport blocks (TBs), each of the one or more feedback-enabled TBs is associated with one or more feedback-enabled TBs of a HARQ feedback-enabled process, One or more feedback disable TBs, each of the one or more feedback disable TBs is associated with the HARQ feedback disable process and Includes, Herein, the one or more feedback-enabled TBs and the one or more feedback-disabled TBs are received in accordance with the multi-TB scheduling based on the downlink control information (DCI) associated with the multi-TB scheduling. The one or more feedback-enabled TBs and the one or more feedback-disabled TBs are received as one or more TB bundles, where each feedback-enabled TB and each feedback-disabled TB is included in only one of the one or more TB bundles. The aforementioned one or more TB bundles are A feedback-enabled TB bundle, where each feedback-enabled TB bundle includes at least one feedback-enabled TB, A feedback-disabled TB bundle, where each feedback-disabled TB bundle does not contain any feedback-enabled TBs, and An apparatus including at least one of the following.

2. The aforementioned multiple downlink communications, A first HARQ process is associated with at least one feedback-enabled transport block (TB), At least one feedback-disabled TB associated with the second HARQ process and Includes, Herein, the at least one feedback-enabled TB and the at least one feedback-disabled TB are scheduled in the TB, Preferably, the at least one processor is Use the DCI bit to configure at least one of the feedback-enabled TBs as a feedback-disabled TB, or The DCI bit is used to configure the at least one feedback-disabled TB as a feedback-enabled TB. It is further structured in the following way: More preferably, each of the at least one processor is further configured to use the DCI bit to modify the radio resource control (RRC) instruction feedback behavior for the at least one feedback-enabled TB or the at least one feedback-disabled TB. More preferably, the DCI bit is a HARQ ACK bundling flag. The apparatus according to claim 1.

3. The plurality of downlink communications comprises one or more feedback-enabled transport blocks (TBs), each of the one or more feedback-enabled TBs includes one or more feedback-enabled TBs associated with a HARQ feedback-enabled process. The one or more feedback-enabled TBs are received in accordance with the multi-TB scheduling based on the downlink control information (DCI) associated with the multi-TB scheduling. Preferably, The one or more uplink communications include HARQ feedback determined for each of the one or more feedback-enabled TBs. The first uplink slot of the uplink communication transmission configuration is located after the last downlink slot associated with receiving the one or more feedback-enabled TBs using the multi-TB scheduling. The apparatus according to claim 1.

4. The plurality of downlink communications comprises one or more feedback-disabled transport blocks (TBs), each feedback-disabled TB including one or more feedback-disabled TBs associated with the HARQ feedback-disabled process. The one or more feedback-disabled TBs are received using the multi-TB scheduling based on the downlink control information (DCI) associated with the multi-TB scheduling. The one or more uplink communications described above do not include feedback associated with the one or more feedback-disabled TBs. The apparatus according to claim 1.

5. The multi-TB scheduling includes the one or more feedback-enabled TBs before the one or more feedback-disabled TBs, The last transmission time interval associated with the one or more feedback-enabled TBs is earlier than the first transmission time interval associated with the one or more feedback-disabled TBs. Preferably, The one or more uplink communications include the respective HARQ feedback determined for each of the one or more feedback-enabled TBs. At least a portion of the one or more uplink communications is transmitted after the last transmission time interval associated with the one or more feedback-enabled TBs. The apparatus according to any one of claims 1 to 4.

6. The aforementioned one or more uplink communications are Each HARQ feedback determined for each of the one or more feedback-enabled TBs, The respective placeholder feedback determined for each of the one or more feedback invalid TBs and Includes, Preferably, the at least one processor is The uplink communication transmission configuration is determined based on the relative order associated with receiving the one or more feedback-enabled TBs and the one or more feedback-inactive TBs. The HARQ feedback and the placeholder feedback are transmitted using the same relative order associated with receiving the one or more feedback-enabled TBs and the one or more feedback-inactive TBs. The apparatus according to any one of claims 1 to 5, further configured as follows.

7. The one or more uplink communications include HARQ feedback determined for each of the one or more feedback-enabled TBs, and do not include feedback associated with the one or more feedback-disabled TBs, and the at least one processor, The uplink communication transmission configuration is determined based on the relative order associated with receiving the one or more feedback-enabled TBs and the one or more feedback-inactive TBs. It is further structured in the following way: Herein, the uplink communication transmission configuration is: For each feedback-enabled TB included in the aforementioned relative order, generate a HARQ feedback transmission time interval associated with the HARQ feedback determined for the feedback-enabled TB, For each feedback-disabled TB included in the aforementioned relative order, generate an empty uplink transmission time interval associated with the feedback-disabled TB. Determined by, The apparatus according to any one of claims 1 to 6.

8. In order to determine the one or more uplink communications, the at least one processor, for each feedback-enabled TB bundle of the one or more TB bundles, For each feedback-enabled TB included in the aforementioned feedback-enabled TB bundle, a corresponding HARQ feedback is generated. For each feedback-disabled TB included in the aforementioned feedback-enabled TB bundle, a placeholder feedback is generated for each TB. A bundled HARQ feedback based on each HARQ feedback and each placeholder feedback, wherein one or more uplink communications determine the bundled HARQ feedback, including the bundled HARQ feedback. It is further structured in the following way: Preferably, To determine the bundled HARQ feedback, the at least one processor is configured to calculate the logical AND between each HARQ feedback and each placeholder feedback. The placeholder feedback includes an affirmative response (ACK) or a logical 1 value. The apparatus according to any one of claims 1 to 7.

9. The apparatus according to claim 1, wherein one or more of the plurality of downlink communications are received by an extended machine type communication (eMTC) device, or one or more of the one or more uplink communications are transmitted by the eMTC device.

10. The aforementioned at least one processor is At least one of the plurality of downlink communications, the first downlink communication receives a first physical downlink shared channel (PDSCH) communication which includes at least one downlink communication which includes a transport block (TB) associated with a feedback-disabled HARQ process, Receiving a second PDSCH communication which includes at least additional downlink communication, the additional downlink communication which includes additional TB associated with the feedback disabled HARQ process. It is further structured in the following way: Here, the first PDSCH communication and the second PDSCH communication are separated by a predetermined time interval. The apparatus according to claim 1.

11. The apparatus according to claim 10, wherein the apparatus is an eMTC apparatus or a bandwidth limiting or coverage expansion (BL / CE) apparatus, and the predefined time interval is 4 milliseconds.

12. The one or more downlink communications mentioned above are up to four HARQ processes, The aforementioned up to four HARQ processes include a subset of up to two feedback-enabled HARQ processes, Of the up to four HARQ processes mentioned above, one or more HARQ processes not included in the subset are feedback-disabled HARQ processes. Associated with up to four HARQ processes, The apparatus according to claim 11.

13. The aforementioned at least one processor is The soft buffer associated with the device stores up to two feedback-enabled HARQ processes, each associated with a feedback-enabled TB included in the subset of feedback-enabled HARQ processes. The apparatus according to claim 12, further configured as follows.

14. The aforementioned at least one processor is Based on the dedicated downlink control information (DCI) bits associated with the up to four HARQ processes, it is determined whether soft buffer storage is required for each of the up to four HARQ processes. It is further structured in the following way: Here, the first value of the DCI bit indicates that storage of a soft buffer is required for each feedback-enabled HARQ process included in the subset, or Here, the second value of the DCI bit indicates that storage of the soft buffer is not required for the feedback-disabled HARQ process that is not included in the subset. Preferably, the at least one processor is Based on dedicated DCI bits associated with the up to four HARQ processes, it is determined whether each of the up to four HARQ processes is a feedback-enabled HARQ process or a feedback-disabled HARQ process, where the first value of the DCI bit is used for feedback-enabled HARQ processes, the second value of the DCI bit is used for feedback-disabled HARQ processes, or The dedicated DCI bits are used to implicitly or explicitly indicate the HARQ process ID number for each of the up to four HARQ processes. The apparatus according to claim 12, further configured as follows.

15. A device for a network entity for wireless communication, At least one memory, The system comprises at least one processor coupled to at least one memory, and the at least one processor is Multiple downlink communications for transmission, each of which outputs multiple downlink communications associated with a Hybrid Automatic Retransmission Request (HARQ) process, An uplink communication transmission configuration, wherein the uplink communication transmission configuration comprises one or more uplink communications based on the uplink communication transmission configuration, each of the one or more uplink communications receiving one or more uplink communications, each of the one or more uplink communications including feedback associated with at least one of the downlink communications. It is configured in such a way, The aforementioned multiple downlink communications, One or more feedback-enabled transport blocks (TBs), each of the one or more feedback-enabled TBs is associated with one or more feedback-enabled TBs of a HARQ feedback-enabled process, One or more feedback disable TBs, each of the one or more feedback disable TBs is associated with the HARQ feedback disable process and Includes, Herein, the one or more feedback-enabled TBs and the one or more feedback-disabled TBs are received in accordance with the multi-TB scheduling based on the downlink control information (DCI) associated with the multi-TB scheduling. The one or more feedback-enabled TBs and the one or more feedback-disabled TBs are received as one or more TB bundles, where each feedback-enabled TB and each feedback-disabled TB is included in only one of the one or more TB bundles. The aforementioned one or more TB bundles are A feedback-enabled TB bundle, where each feedback-enabled TB bundle includes at least one feedback-enabled TB, A feedback-disabled TB bundle, where each feedback-disabled TB bundle does not contain any feedback-enabled TBs, and An apparatus including at least one of the following.

Images