Patent Description:
<CIT> discloses to determine a maximum size of a transport block (TBS) based on the UE capabilities such as memory size. The maximum TBS is reported to a base station via a non-terrestrial link. For a TB having a TBS exceeding the maximum TBS, HARQ is disabled.

<CIT> discloses to configure a plurality of HARQ configuration parameters corresponding to the capability parameters of the UE. The capabilities may include e.g. a transport block size (TBS) and a number of HARQ processes.

<CIT> discloses a user equipment (UE) indicating a capability to a base station in cellular communication. The UE capability information may be used by the base station to determine a maximum transport block size (TBS) per transmission time interval (TTI) and/or a maximum number of supportable parallel hybrid automatic repeat request (HARQ) processes for the UE in a subsequent HARQ procedure.

SAMSUNG "Enhancements on HARQ for NTN", 3GGP Draft R1-<NUM>, discloses that a UE may report its capabilities including maximum transport block size and number of HARQ processes to a non-terrestrial network entity.

The invention is defined by methods of wireless communication performed by a user equipment and performed by a non-terrestrial network entity according to independent claims <NUM> and <NUM>.

In some aspects, as shown, a cell may be provided by a base station <NUM> of a non-terrestrial network. As used herein, "non-terrestrial network" may refer to a network for which access is provided by a non-terrestrial base station, such as a base station carried by a satellite, a balloon, a dirigible, an airplane, an unmanned aerial vehicle, a high altitude platform station, and/or the like.

In some aspects, a relay station may be implemented using a non-terrestrial platform, similarly to the base station described above.

Transmit processor <NUM> may also generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS), a demodulation reference signal (DMRS), and/or the like) and synchronization signals (e.g., the primary synchronization signal (PSS) and secondary synchronization signal (SSS)).

On the uplink, at UE <NUM>, a transmit processor <NUM> may receive and process data from a data source <NUM> and control information (e.g., for reports that include RSRP, RSSI, RSRQ, CQI, and/or the like) from controller/processor <NUM>.

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with indicating maximum transport block sizes or a span for a transport block in a non-terrestrial network (NTN), as described in more detail elsewhere herein. For example, a controller/processor of an NTN entity (e.g., controller/processor <NUM> of base station <NUM>), controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform or direct operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein. A memory may store data and program codes for the NTN entity, and memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively. In some aspects, the memory for the NTN entity, memory <NUM>, and/or memory <NUM> may include a non-transitory computer-readable medium storing one or more instructions (e.g., code, program code, and/or the like) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, interpreting, and/or the like) by one or more processors of the NTN entity, the base station <NUM>, and/or the UE <NUM>, may cause the one or more processors, the NTN entity, the UE <NUM>, and/or the base station <NUM> to perform or direct operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein. In some aspects, executing instructions may include running the instructions, converting the instructions, compiling the instructions, interpreting the instructions, and/or the like.

In some aspects, the UE <NUM> includes means for transmitting a report of one or more maximum transport block sizes supported by the UE, and/or means for receiving, based at least in part on transmitting the report, one or more transport blocks that have a transport block size that does not exceed the maximum transport block sizes supported by the UE. The means for the UE <NUM> to perform operations described herein may include, for example, antenna <NUM>, demodulator <NUM>, MIMO detector <NUM>, receive processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, modulator <NUM>, controller/processor <NUM>, and/or memory <NUM>.

In some aspects, the UE <NUM> includes means for determining the one or more maximum transport block sizes based at least in part on a soft buffer size of the UE.

In some aspects, the UE <NUM> includes means for determining the one or more maximum transport block sizes based at least in part on a speed at which the UE processes received communications.

In some aspects, the UE <NUM> includes means for determining the one or more maximum transport block sizes based at least in part on a throughput requirement.

In some aspects, the NTN entity includes means for receiving a report of one or more maximum transport block sizes supported by a UE, and/or means for transmitting, to the UE and based at least in part on receiving the report, one or more transport blocks that have a transport block size that does not exceed the maximum transport block sizes. The means for the NTN entity to perform operations described herein may include, for example, components such as transmit processor <NUM>, TX MIMO processor <NUM>, modulator <NUM>, antenna <NUM>, demodulator <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or scheduler <NUM>.

In some aspects, the UE <NUM> includes means for receiving, from an NTN entity, an indication of a length of a span for receiving a set of bits from channel encoder output for a transport block or a redundancy version of a transport block, and/or means for receiving, within a span having the indicated length, a set of bits from channel encoder output for a transport block or a redundancy version of a transport block. The means for the UE <NUM> to perform operations described herein may include, for example, antenna <NUM>, demodulator <NUM>, MIMO detector <NUM>, receive processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, modulator <NUM>, controller/processor <NUM>, and/or memory <NUM>.

In some aspects, the NTN entity includes means for transmitting, to a UE, an indication of a length of a span for receiving a set of bits from channel encoder output for a transport block or a redundancy version of a transport block; and/or means for transmitting, within a span having the indicated length, a set of bits from channel encoder output for a transport block or a redundancy version of a transport block. The means for the NTN entity to perform operations described herein may include, for example, components such as transmit processor <NUM>, TX MIMO processor <NUM>, modulator <NUM>, antenna <NUM>, demodulator <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or scheduler <NUM>.

In some aspects, the NTN entity includes means for determining the length of the span based at least in part on a soft buffer size of the UE.

In some aspects, the NTN entity includes means for determining the length of the span based at least in part on a speed at which the UE processes received communications.

In some aspects, the NTN entity includes means for determining the length of the span based at least in part on a throughput requirement for the UE.

<FIG> is a diagram illustrating an example <NUM> of a regenerative satellite deployment and an example <NUM> of a transparent satellite deployment in an NTN.

Example <NUM> shows a regenerative satellite deployment. In example <NUM>, a UE <NUM> is served by a satellite <NUM> via a service link <NUM>. For example, the satellite <NUM> may include a BS <NUM> (e.g., BS 110a), a gNB, and/or the like. In some aspects, the satellite <NUM> may be referred to as a non-terrestrial base station, a regenerative repeater, an on-board processing repeater, an NTN entity, and/or the like. In some aspects, the satellite <NUM> may demodulate an uplink radio frequency signal, and may modulate a baseband signal derived from the uplink radio signal to produce a downlink radio frequency transmission. The satellite <NUM> may transmit the downlink radio frequency signal on the service link <NUM>. The satellite <NUM> may provide a cell that covers the UE <NUM>.

Example <NUM> shows a transparent satellite deployment, which may also be referred to as a bent-pipe satellite deployment. In example <NUM>, a UE <NUM> is served by a satellite <NUM> via the service link <NUM>. Satellite <NUM> may also be considered to be an NTN entity. The satellite <NUM> may be a transparent satellite. The satellite <NUM> may relay a signal received from gateway <NUM> via a feeder link <NUM>. For example, the satellite may receive an uplink radio frequency transmission, and may transmit a downlink radio frequency transmission without demodulating the uplink radio frequency transmission. In some aspects, the satellite may frequency convert the uplink radio frequency transmission received on the service link <NUM> to a frequency of the uplink radio frequency transmission on the feeder link <NUM>, and may amplify and/or filter the uplink radio frequency transmission. In some aspects, the UEs <NUM> shown in example <NUM> and example <NUM> may be associated with a Global Navigation Satellite System (GNSS) capability, a Global Positioning System (GPS) capability, and/or the like, though not all UEs have such capabilities. The satellite <NUM> may provide a cell that covers the UE <NUM>.

The service link <NUM> may include a link between the satellite <NUM> and the UE <NUM>, and may include one or more of an uplink or a downlink. The feeder link <NUM> may include a link between the satellite <NUM> and the gateway <NUM>, and may include one or more of an uplink (e.g., from the UE <NUM> to the gateway <NUM>) or a downlink (e.g., from the gateway <NUM> to the UE <NUM>).

The feeder link <NUM> and the service link <NUM> may each experience Doppler effects due to the movement of the satellites <NUM> and <NUM>, and potentially movement of a UE <NUM>. These Doppler effects may be significantly larger than in a terrestrial network. The Doppler effect on the feeder link <NUM> may be compensated for to some degree, but may still be associated with some amount of uncompensated frequency error. Furthermore, the gateway <NUM> may be associated with a residual frequency error, and/or the satellite <NUM>/<NUM> may be associated with an on-board frequency error. These sources of frequency error may cause a received downlink frequency at the UE <NUM> to drift from a target downlink frequency.

Due to a distance between a UE and an NTN entity (e.g., satellite), there may be a long propagation delay for transport blocks. The UE may also use a limited quantity of hybrid automatic repeat request (HARQ) processes for transport blocks from the NTN entity. The HARQ processes may be used for HARQ feedback, including acknowledgements (ACKs) or negative acknowledgements (NACKs). To better utilize the satellite link, the size of a transport block may be increased up to a maximum transport block size.

To increase throughput with a large propagation delay, HARQ feedback for some HARQ processes may be disabled, resulting in a mix of HARQ process types. Some HARQ processes may be disabled, and some HARQ processes may be enabled. The quantity of transmissions a UE may receive during a period of time may be greater if HARQ feedback disabled rather than enabled. In the case of HARQ feedback being disabled, a UE may need to buffer the received signal if the transmission is one-shot. The UE may also need to buffer previous transmissions of a transport block if blind retransmissions are used. If the same maximum transport block sizes are used when HARQ feedback is disabled, the UE may not be able to keep up with the downlink processing, causing the UE to waste power, processing resources, and signaling resources.

According to the invention as claimed, a network may use two different maximum transport block sizes, one for if HARQ feedback is enabled and one for if HARQ feedback is disabled. The maximum transport block size for a HARQ process may also be based at least in part on factors such as throughput requirements. UEs may have different downlink processing capabilities and throughput requirements, and thus a UE may report the maximum transport block sizes for the UE to the network. For example, a UE may report one or more maximum transport block sizes that are supported by the UE, and an NTN entity may transmit, to the UE, transport blocks up to the maximum transport block sizes supported by the UE. The UE reports a maximum transport block size for if HARQ feedback is enabled, and a maximum transport block size for if HARQ feedback is disabled. The UE may also report a maximum quantity of HARQ processes the UE can support. As a result, transport blocks may be extended in size to better fill a pipe between the UE and the NTN entity, but not larger than what a buffer of the UE can handle, whether HARQ feedback is enabled and disabled. The UE conserves power, processing resources, and signaling resources that would otherwise be wasted by transport block size and UE buffer mismatches.

<FIG> is a diagram illustrating an example <NUM> of indicating maximum transport block sizes in an NTN, in accordance with various aspects of the present disclosure. As shown, <FIG> includes an NTN entity <NUM> (e.g., base station, relay station) and a UE <NUM> that may communicate with each other over a satellite link. In some aspects, UE <NUM> may include a ground station.

As shown by reference number <NUM>, UE <NUM> may determine maximum transport block sizes for UE <NUM>. There is a maximum transport block size for if HARQ feedback is enabled, and a maximum transport block size for if HARQ feedback is disabled. The quantity of communications UE <NUM> can receive in a unit of time when HARQ feedback disabled may be much larger than when HARQ feedback enabled, because the network does not need to wait for the HARQ feedback before sending the next communication.

UE <NUM> may ensure that a soft buffer size of UE <NUM> is sufficient for various downlink configurations, including for certain combinations of an MCS and a number of layers (e.g., rank). A larger soft buffer size may also mean increased hardware complexity. UE <NUM> may determine a preferred maximum transport block sizes based at least in part on the soft buffer size and/or a throughput requirement. UE <NUM> may also determine a preferred maximum transport block size based at least in part on a speed at which the UE processes received communications. For example, if the UE is processing communications rather quickly, the UE may be able to handle larger block sizes. On the other hand, if the UE is having difficulty processing all the received communications, the UE may prefer a smaller transport block size. The speed may be measured as a quantity of processed communications per unit of time. UE <NUM> may prepare a report that indicates the preferred maximum transport block sizes. As shown by reference number <NUM>, UE <NUM> may transmit the report to NTN entity <NUM>.

In some aspects, UE <NUM> may indicate, in the report, a maximum quantity of HARQ processes that the UE <NUM> may use for HARQ feedback. UE <NUM> may determine the maximum quantity of HARQ processes based at least in part on a speed at which HARQ feedback is determined and transmitted.

NTN entity <NUM> may determine a size for one or more transport blocks that are to be transmitted to UE <NUM> based at least in part on the maximum transport block sizes reported by UE <NUM>. The size for the transport blocks may be based at least in part on if HARQ feedback is enabled or disabled, and the size may be not exceed the reported maximum transport block size that corresponds to the HARQ feedback status. In some aspects, the size for the transport blocks may be right up to the reported maximum transport block size. The size of the transport blocks may also be equal to the reported maximum transport block size.

In example <NUM>, the size of the transport blocks does not exceed the reported maximum transport block sizes. For example, the relevant reported maximum transport block size may be the maximum transport block size for if HARQ feedback is enabled. As shown by reference number <NUM>, NTN entity <NUM> may transmit the transport blocks. As shown by reference number <NUM>, UE <NUM> may buffer transport blocks and process transport blocks from the buffer. As a result of the reported maximum transport block sizes, the satellite link is better utilized without compromising the buffer of UE <NUM>.

In some aspects, a UE may receive a transmission of a transport block. The transmission may include a set of bits from channel encoder output for the transport block or a redundancy version of the transport block. The UE may receive the transmission of the transport block within a span, which is a unit that is comparable to a transmission time interval in LTE. The span may be a time duration, or the span may be a quantity of slots. If there is a power limitation for a UE, an NTN entity may use a narrow bandwidth, which may require multiple slots for reception. However, if the span is too long, signaling resources may be wasted. If the span is too short, the UE may waste power, processing resources, and signaling resources when the UE fails to receive a transport block.

According to various aspects described herein, an NTN entity may indicate, in downlink control information (DCI), a span for a transmission of a transport block, where the transmission is a set of bits from channel encoder output for the transport block (e.g., transport block without repetition) or a redundancy version of the transport block. The span may be a time duration and/or a quantity of slots that is based at least in part on a UE capability of the UE. As a result, the UE does not waste power, processing resources, and/or signaling resources with a mismatched span for a transport block.

<FIG> is a diagram illustrating an example <NUM> of indicating a span in an NTN, in accordance with various aspects of the present disclosure. As shown, <FIG> includes an NTN entity <NUM> (e.g., base station, relay station) and a UE <NUM> that may communicate with each other on a satellite link. In some aspects, UE <NUM> may include a ground station.

As shown by reference number <NUM>, NTN entity <NUM> may determine a length of a span for a set of bits from channel encoder output for a transport block or a redundancy version of a transport block. The set of bits may be stored in a circular buffer. NTN entity <NUM> may determine the length of the span based at least in part on a capability of UE <NUM>, link conditions, a location of UE <NUM>, traffic conditions, a speed at which UE <NUM> processes communications, and/or other factors. As shown by reference number <NUM>, NTN entity <NUM> may transmit the length in DCI.

As shown by reference number <NUM>, UE <NUM> may set a length of a "time span" for receiving a set of bits from channel encoder output for a transport block or a redundancy version of the transport block scheduled by the DCI. In example <NUM>, the "time span" may be refer to time or to one or more slots. The length of the time span may be a time duration or a quantity of slots. As shown by reference number <NUM>, UE <NUM> may receive the set of bits from channel encoder output for the transport block, or the redundancy version of the transport block, within the time span. As a result, UE <NUM> may be enabled to receive a transmission of a larger transport block that UE <NUM> can support.

Alternatively, NTN entity <NUM> may transmit an indication of a length of a time span for transport blocks in a medium access control control element (MAC CE) or a radio resource control (RRC) message. In some aspects, NTN entity <NUM> may transmit an indication of a starting time for the time span. The indication of the starting time may be in the MAC CE or the RCC message. UE <NUM> may receive the bits for the transport block or the redundancy version within the time span, which starts at the indicated starting time. The starting time may be a starting symbol.

In some aspects, NTN entity <NUM> may transmit (e.g., in DCI) an indication that may be used with other fields to determine a length of a time span. For example, NTN entity <NUM> may transmit an indication of whether the time span is less than a slot, equal to a slot, or more than one slot. This indication may be represented by a radio network temporary identifier (RNTI) that can be used to scramble a cyclic redundancy check (CRC) of DCI, a demodulation reference signal (DMRS) sequences, and/or scrambling sequences applied to rate-matched bits to be modulated. If the indication is for more than one slot, UE <NUM> may reinterpret a redundancy version field in the DCI such that the redundancy version field and a time domain resource assignment (TDRA) field combine to indicate the length of the time span. A redundancy version field may indicate a quantity of repetitions and/or part of the length of the time span (e.g., quantity of slots). NTN entity <NUM> may also transmit a zeroth redundancy version of a transport block in a MAC CE or an RRC message without using the redundancy version field in DCI.

In some aspects, a frequency domain resource allocation (FDRA) for a transport block may be less than one RB, and may include a quantity of any subset of subcarriers. The length of the time span may impact various timing relationships, such as a timing for a first slot of a physical downlink shared channel (PDSCH) communication (e.g., K0), a timing from the PDSCH communication to HARQ ACK timing (e.g., K1), a timing from the PDSCH communication or DCI to a first slot of a physical uplink shared channel (PUSCH) (e.g., K2), and/or a K_offset (a delay parameter applied in addition to K1 and K2 to account for the large propagation delay). The configuration of a time span and/or timing relationship may be different for uplink than for downlink. For example, a time span may be one slot for downlink and multiple slots for uplink. UE <NUM> may report a preferred time span of a redundancy version based at least in part on a maximum transmit power, a path loss, and/or quality of service requirements. The preferred time span may be indicated as slots and/or symbols. In some aspects, NTN entity <NUM> may indicate a granularity of the FDRA, such as whether the FDRA is an RB or a sub-RB using different RNTIs that can be used to scramble a CRC of DCI, different DMRS sequences, and/or different scrambling sequences applied to rate-matched bits to be modulated.

<FIG> is a diagram illustrating an example <NUM> of indicating a span in an NTN, in accordance with various aspects of the present disclosure.

Example <NUM> shows a transmission of a transport block that is received within a span of <NUM> slots. The UE may support slot aggregation, where a subset of multiple slots are scheduled for a UE, each carrying a redundancy version. Different redundancy versions may have overlapping bits. Example <NUM> also shows a set of bits in channel encoder output for a transport block or a redundancy version of a transport block that is received within a span of <NUM> slots. In some aspects, a length of a span may be <NUM> slots, but bits for the transport block may be received in <NUM> or <NUM> slots. Example <NUM> also shows a repetition of two redundancy versions.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where the UE (e.g., UE <NUM> depicted in <FIG>, UE <NUM> depicted in <FIG>) performs operations associated with indicating maximum transport block sizes in an NTN.

As shown in <FIG>, in some aspects, process <NUM> may include transmitting a report of one or more maximum transport block sizes supported by the UE (block <NUM>). For example, the UE (e.g., using transmission component <NUM> depicted in <FIG>) may transmit a report of one or more maximum transport block sizes supported by the UE, as described in connection with <FIG>.

In a first aspect, the one or more maximum transport block sizes include a maximum transport block size for if HARQ feedback is enabled and a maximum transport block size for if HARQ feedback is disabled.

In a second aspect, alone or in combination with the first aspect, the report indicates a maximum quantity of HARQ processes.

In a third aspect, alone or in combination with one or more of the first and second aspects, process <NUM> includes determining the one or more maximum transport block sizes based at least in part on a soft buffer size of the UE.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, process <NUM> includes determining the one or more maximum transport block sizes based at least in part on an MCS or a quantity of layers.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, process <NUM> includes determining the one or more maximum transport block sizes based at least in part on a throughput requirement.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process <NUM> includes determining the one or more maximum transport block sizes based at least in part on a speed at which the UE processes received communications.

As further shown in <FIG>, in some aspects, process <NUM> may include receiving, based at least in part on transmitting the report, one or more transport blocks that have a transport block size equal to one of the maximum transport block sizes supported by the UE (block <NUM>). For example, the UE (e.g., using reception component <NUM> depicted in <FIG>) may receive, based at least in part on transmitting the report, one or more transport blocks that have a transport block size equal to one of the maximum transport block sizes supported by the UE, as described in connection with <FIG>.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by an NTN entity, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where the NTN entity (e.g., base station <NUM> depicted in <FIG>, NTN entity depicted in <FIG>, NTN entity <NUM> or NTN entity <NUM> depicted in <FIG>, NTN entity <NUM> depicted in <FIG>) performs operations associated with indicating maximum transport block sizes in an NTN.

As shown in <FIG>, in some aspects, process <NUM> may include receiving a report of one or more maximum transport block sizes supported by a UE (block <NUM>). For example, the NTN entity (e.g., using reception component <NUM> depicted in <FIG>) may receive a report of one or more maximum transport block sizes supported by a UE, as described in connection with <FIG>.

In a third aspect, alone or in combination with one or more of the first and second aspects, the one or more maximum transport block sizes are associated with a soft buffer size of the UE.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the one or more maximum transport block sizes are associated with an MCS or a quantity of layers.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the one or more maximum transport block sizes are associated with a throughput requirement for the UE.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the one or more maximum transport block sizes are associated with a speed at which the UE processes received communications.

As further shown in <FIG>, in some aspects, process <NUM> may include transmitting, to the UE, one or more transport blocks that have a transport block size equal to one of the maximum transport block sizes, where the transmitting is based at least in part on receiving the report (block <NUM>). For example, the NTN entity (e.g., using transmission component <NUM> depicted in <FIG>) may transmit, to the UE, one or more transport blocks that have a transport block size equal to one of the maximum transport block sizes based at least in part on receiving the report, as described in connection with <FIG>.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where the UE (e.g., UE <NUM> depicted in <FIG>, UE <NUM> depicted in <FIG>) performs operations associated with indicating a span for a transport block in an NTN.

As shown in <FIG>, in some aspects, process <NUM> may include receiving, from an NTN entity, an indication of a length of a span for receiving a set of bits from channel encoder output for a transport block or a redundancy version of a transport block (block <NUM>). For example, the UE (e.g., using reception component <NUM> depicted in <FIG>) may receive, from an NTN entity, an indication of a length of a span for receiving a set of bits from channel encoder output for a transport block or a redundancy version of a transport block, as described in connection with <FIG>.

In a first aspect, process <NUM> includes receiving an indication of a starting time for the span, and the span starts at the starting time.

In a second aspect, alone or in combination with the first aspect, process <NUM> includes determining that the length of the span is less than a slot, equal to a slot, or more than a slot based at least in part on an RNTI used to scramble a CRC of DCI.

In a third aspect, alone or in combination with one or more of the first and second aspects, process <NUM> includes determining that the length of the span is less than a slot, equal to a slot, or more than a slot based at least in part on a DMRS sequence in DCI.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, process <NUM> includes determining that the length of the span is less than a slot, equal to a slot, or more than a slot based at least in part on a scrambling sequence applied to rate-matched bits to be modulated.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, process <NUM> includes determining the length of the span from a combination of a redundancy version field and a TDRA, based at least in part on a determination that the length of the span is more than a slot.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, receiving the indication includes receiving the indication of the length of the span in an RRC message, a MAC CE, or DCI that schedules the transport block.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process <NUM> includes determining a recommended length of a span based at least in part on one or more of a maximum transmit power, a path loss, or a quality of service requirement, and transmitting the recommended length of the span.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the length of the span is associated with a soft buffer size of the UE.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the length of the span is associated with an MCS or a quantity of layers.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the length of the span is associated with a throughput requirement.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the length of the span is indicated as a quantity of slots or a time duration.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, receiving the indication includes receiving the indication of the length of the span in a MAC CE, an RRC message, or DCI that schedules the transport block or the redundancy version of the transport block.

As further shown in <FIG>, in some aspects, process <NUM> may include receiving, within a span having the indicated length, a set of bits from channel encoder output for a transport block or a redundancy version of a transport block (block <NUM>). For example, the UE (e.g., using reception component <NUM> depicted in <FIG>) may receive, within a span having the indicated length, a set of bits from channel encoder output for a transport block or a redundancy version of a transport block, as described in connection with <FIG>.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by an NTN entity, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where the NTN entity (e.g., base station <NUM> depicted in <FIG>, NTN entity depicted in <FIG>, NTN entity <NUM> or NTN entity <NUM> depicted in <FIG>, NTN entity <NUM> depicted in <FIG>) performs operations associated with indicating a span for a transport block in an NTN.

As shown in <FIG>, in some aspects, process <NUM> may include transmitting, to a UE, an indication of a length of a span for receiving a set of bits from channel encoder output for a transport block or a redundancy version of a transport block (block <NUM>). For example, the NTN entity (e.g., using transmission component <NUM> depicted in <FIG>) may transmit, to a UE, an indication of a length of a span for receiving a set of bits from channel encoder output for a transport block or a redundancy version of a transport block, as described in connection with <FIG>.

In a first aspect, process <NUM> includes determining a starting time for the span, and transmitting an indication of the starting time.

In a second aspect, alone or in combination with the first aspect, the indication includes an RNTI used to scramble a CRC of DCI, and the RNTI indicates whether the length of the span is less than a slot, equal to a slot, or more than a slot.

In a third aspect, alone or in combination with one or more of the first and second aspects, the indication includes a DMRS sequence that indicates whether the length of the span is less than a slot, equal to a slot, or more than a slot.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the indication includes a scrambling sequence applied to rate-matched bits to be modulated, and the scrambling sequence indicates whether the length of the span is less than a slot, equal to a slot, or more than a slot.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the indication includes a combination of a redundancy version field and a TDRA, where the combination indicates the length of the span based at least in part on a determination that the length of the span is more than a slot.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process <NUM> includes determining the length of the span based at least in part on a throughput requirement for the UE.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the length of the span is indicated as a quantity of slots or a time duration.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, transmitting the indication includes transmitting the indication of the length of the span in an RRC message, a MAC CE, or DCI that schedules the transport block.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process <NUM> includes receiving, from the UE, a recommended length of a span, and determining the length of the span based at least in part on the recommended length of a span.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process <NUM> includes determining the length of the span based at least in part on a soft buffer size of the UE.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process <NUM> includes determining the length of the span based at least in part on an MCS or a quantity of layers.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process <NUM> includes determining a starting time for the span and transmitting an indication of the starting time.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process <NUM> includes determining whether a resource allocation is less than a resource block and includes a subset of subcarriers based at least in part on one or more of an RNTI used to scramble a CRC of DCI, a DMRS sequence in DCI, or a scrambling sequence applied to rate-matched bits to be modulated.

As further shown in <FIG>, in some aspects, process <NUM> may include transmitting, within a span having the indicated length, a set of bits from channel encoder output for a transport block or a redundancy version of a transport block (block <NUM>). For example, the NTN entity (e.g., using transmission component <NUM> depicted in <FIG>) may transmit, within a span having the indicated length, a set of bits from channel encoder output for a transport block or a redundancy version of a transport block, as described in connection with <FIG>.

<FIG> is a block diagram of an example apparatus <NUM> for wireless communication. The apparatus <NUM> may be a UE, or a UE may include the apparatus <NUM>. In some aspects, the apparatus <NUM> includes a reception component <NUM> and a transmission component <NUM>, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus <NUM> may communicate with another apparatus <NUM> (such as a UE, a base station, an NTN entity, or another wireless communication device) using the reception component <NUM> and the transmission component <NUM>. As further shown, the apparatus <NUM> may include a determination component <NUM>, among other examples.

In some aspects, the apparatus <NUM> may be configured to perform one or more operations described herein in connection with <FIG>. Additionally, or alternatively, the apparatus <NUM> may be configured to perform one or more processes described herein, such as process <NUM> of <FIG>. In some aspects, the apparatus <NUM> and/or one or more components shown in <FIG> may include one or more components of the UE described above in connection with <FIG>. Additionally, or alternatively, one or more components shown in <FIG> may be implemented within one or more components described above in connection with <FIG>. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

The transmission component <NUM> may transmit a report of one or more maximum transport block sizes supported by the UE. The reception component <NUM> may receive, based at least in part on transmitting the report, one or more transport blocks that have a transport block size equal to one of the maximum transport block sizes supported by the UE. There may be a maximum transport block size for if HARQ feedback is enabled, and a maximum transport block size for if HARQ feedback is disabled.

The determination component <NUM> may determine the one or more maximum transport block sizes based at least in part on a soft buffer size of the UE. In some aspects, the determination component <NUM> may include a demodulator, a MIMO detector, a receive processor, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described above in connection with <FIG>. The determination component <NUM> may determine the one or more maximum transport block sizes based at least in part on a speed at which the UE processes received communications. The determination component <NUM> may determine the one or more maximum transport block sizes based at least in part on a throughput requirement.

<FIG> is a block diagram of an example apparatus <NUM> for wireless communication. The apparatus <NUM> may be an NTN entity, or an NTN entity may include the apparatus <NUM>. In some aspects, the apparatus <NUM> includes a reception component <NUM> and a transmission component <NUM>, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus <NUM> may communicate with another apparatus <NUM> (such as a UE, a base station, or another wireless communication device) using the reception component <NUM> and the transmission component <NUM>. As further shown, the apparatus <NUM> may include a determination component <NUM>, among other examples.

In some aspects, the apparatus <NUM> may be configured to perform one or more operations described herein in connection with <FIG>. Additionally, or alternatively, the apparatus <NUM> may be configured to perform one or more processes described herein, such as process <NUM> of <FIG>. In some aspects, the apparatus <NUM> and/or one or more components shown in <FIG> may include one or more components of the NTN entity described above in connection with <FIG>. Additionally, or alternatively, one or more components shown in <FIG> may be implemented within one or more components described above in connection with <FIG>. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

In some aspects, the reception component <NUM> may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the NTN entity described above in connection with <FIG>.

In some aspects, the transmission component <NUM> may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the NTN entity described above in connection with <FIG>.

The reception component <NUM> may receive a report of one or more maximum transport block sizes supported by a UE. The determination component <NUM> may determine to transmit a transport block of a maximum transport block size for the UE. In some aspects, the determination component <NUM> may include a controller/processor, a memory, or a combination thereof, of the NTN entity described above in connection with <FIG>. The transmission component <NUM> may transmit, to the UE, one or more transport blocks that have a transport block size equal to one of the maximum transport block sizes based at least in part on receiving the report.

<FIG> is a block diagram of an example apparatus <NUM> for wireless communication. The apparatus <NUM> may be a UE, or a UE may include the apparatus <NUM>. In some aspects, the apparatus <NUM> includes a reception component <NUM> and a transmission component <NUM>, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus <NUM> may communicate with another apparatus <NUM> (such as a UE, a base station, an NTN entity, or another wireless communication device) using the reception component <NUM> and the transmission component <NUM>. As further shown, the apparatus <NUM> may include a timing component <NUM>, among other examples.

The reception component <NUM> may receive, from an NTN entity, an indication of a length of a span for receiving a set of bits from channel encoder output for a transport block or a redundancy version of a transport block. The timing component <NUM> may adjust a length of a span for receiving a transport block based at least in part on the indicated length. In some aspects, the timing component <NUM> may include a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described above in connection with <FIG>. The timing component <NUM> may determine that the length of the span is less than a slot, equal to a slot, or more than a slot based at least in part on an RNTI used to scramble a CRC of DCI. The timing component <NUM> may determine that the length of the span is less than a slot, equal to a slot, or more than a slot based at least in part on a DMRS sequence in DCI. The timing component <NUM> may determine that the length of the span is less than a slot, equal to a slot, or more than a slot based at least in part on a scrambling sequence applied to rate-matched bits to be modulated. The timing component <NUM> may determine the length of the span from a combination of a redundancy version field and a TDRA, based at least in part on a determination that the length of the span is more than a slot.

The reception component <NUM> may receive, within a span having the indicated length, a set of bits from channel encoder output for a transport block or a redundancy version of a transport block. The reception component <NUM> may receive an indication of a starting time for the span, and wherein the span starts at the starting time. The reception component <NUM> may receive an indication, and the timing component <NUM> may use the indication to determine whether a resource allocation is less than a resource block and includes a subset of subcarriers. The indication may be an RNTI used to scramble a CRC of DCI, a DMRS sequence in DCI, or a scrambling sequence applied to rate-matched bits to be modulated.

The transmission component <NUM> may transmit, to a UE, an indication of a length of a span for receiving a set of bits from channel encoder output for a transport block or a redundancy version of a transport block. The transmission component <NUM> may transmit, within a span having the indicated length, a set of bits from channel encoder output for a transport block or a redundancy version of a transport block.

The determination component <NUM> may determine a starting time for the span, and the transmission component <NUM> may transmit an indication of the starting time. The determination component <NUM> may determine the length of the span based at least in part on a soft buffer size of the UE. In some aspects, the determination component <NUM> may include a demodulator, a MIMO detector, a receive processor, a modulator, a controller/processor, a memory, or a combination thereof, of the NTN entity described above in connection with <FIG>. The determination component <NUM> may determine the length of the span based at least in part on a speed at which the UE processes received communications. The determination component <NUM> may determine the length of the span based at least in part on a throughput requirement for the UE. The transmission component <NUM> may transmit an indication of whether a resource allocation (e.g., FDRA) is less than a resource block and includes a subset of subcarriers, where the indication includes an RNTI used to scramble a CRC of DCI, a DMRS sequence in DCI, or a scrambling sequence applied to rate-matched bits to be modulated.

As an example, "at least one of a, b, or c" is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

Claim 1:
A method of wireless communication performed by a user equipment (UE), comprising:
transmitting, to a non-terrestrial network, NTR, entity, a report of one or more maximum transport block sizes supported by the UE, wherein the report includes a first maximum transport block size, of the one or more maximum transport block sizes for when hybrid automatic repeat request, HARQ, feedback is enabled and a second maximum transport block size, of the one or more maximum transport block sizes, for when HARQ feedback is disabled; and
receiving, based at least in part on transmitting the report, one or more transport blocks that have a transport block size that does not exceed the first maximum transport block size, when the HARQ feedback is enabled, or the second maximum transport block size when the HARQ feedback is disabled.