Patent Description:
These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform-spread-OFDM (DFT-S-OFDM).

Some wireless communications systems may utilize repeated transmissions of a same transport block (TB) to meet certain reliability standards. However, in low latency systems, depending on the number of transmission repetitions, a repetition window may cross a boundary between different subframes or slots. This may result in one or more of complex multiplexing and poor or unreliable reception at a device for the repeated TB transmissions.

3GPP Draft R1-<NUM> "Downlink Enhancements for URLCC" discloses HARQ-less PDSCH repetition in different TTIs wherein the repetition factor may be dynamically indicated via (s)DCI.

3GPP Draft R2-<NUM> "PCFICH Enhancements for URLLC" teaches dynamically indicating a control format indicator (CFI) via PCFICH.

The described techniques relate to improved methods, systems, devices, and apparatuses that support repetition-based transmission. Generally, the described techniques provide for wireless devices to perform multiple transmissions, which may be referred to as repetitions, of a same TB to meet certain reliability standards or thresholds. In low latency systems, TBs may be transmitted in any transmission time interval (TTI). The systems may implement processes to handle these TB repetitions where a TB transmission may cross a slot, subframe, or eIMTA boundaries. For example, a device (e.g., a base station) may transmit control information indicating TB transmission to another device (e.g., user equipment (UE)), and the device may determine the number of transmission repetitions for the TB based on the control information. The device may implicitly or explicitly determine whether it is configured to support a TB transmission of the number of transmission repetitions that may cross slot, subframe, or eIMTA boundaries. The device may then determine how to handle the TB transmission that extends across a boundary based on whether it is configured to support boundary crossing.

The present disclosure provides a method for wireless communication according to claim <NUM>, an apparatus for wireless communications according to claim <NUM>, and a non-transitory computer-readable medium according to claim <NUM>. Preferred embodiments are subject of the dependent claims.

A user equipment (UE) and/or a base station may transmit or receive multiple transmissions, also referred to as repetitions, of a transport block (TB), to ensure compliance with a reliability standard. When low latency is a priority, these repetitions may be transmitted without relying on a hybrid automatic repeat request (HARQ) triggering mechanism, thereby allowing the same TB to be transmitted multiple times over multiple transmission time intervals (TTIs). Depending on the number of repetitions transmitted and a TTI index at which the first repetition is transmitted, two or more repetitions of the TB may be transmitted in different TTIs of a slot of subframe, which may reduce the coherency between the repetitions and degrade the quality of the TB reception.

The described techniques provide for managing the transmission and reception of multiple repetitions of a TB transmission that extend across a slot, subframe, and/or eIMTA boundary. In this way, a UE and/or a base station can receive control information that explicitly or implicitly indicates an indication of transmission repetitions of a TB for a plurality of TTIs, identifies a quantity of transmission repetitions of the TB based on the received control information, and monitors for the transmission repetitions of the TB according to a configuration of the UE and/or the base station and based on whether the TB transmission repetitions extend across a slot, subframe, and/or eIMTA boundary. As explained herein, these techniques may result in improved repetition coherency of the transmitted TB.

Aspects of the disclosure are initially described in the context of a wireless communications system. Additional aspects of the disclosure are described with reference to an example configuration and process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to repetition-based transmission.

<FIG> illustrates an example of a wireless communications system <NUM> in accordance with aspects of the present disclosure. The wireless communications system <NUM> includes base stations <NUM>, UEs <NUM>, and a core network <NUM>. In some examples, the wireless communications system <NUM> may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some cases, wireless communications system <NUM> may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, or communications with low-cost and low-complexity devices.

In one example, a base station <NUM> may use multiple antennas or antenna arrays to conduct beamforming operations for directional communications with a UE <NUM>. For instance, some signals (e.g. synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a base station <NUM> multiple times in different directions, which may include a signal being transmitted according to different beamforming weight sets associated with different directions of transmission. Transmissions in different beam directions may be used to identify (e.g., by the base station <NUM> or a receiving device, such as a UE <NUM>) a beam direction for subsequent transmission and/or reception by the base station <NUM>. Some signals, such as data signals associated with a particular receiving device, may be transmitted by a base station <NUM> in a single beam direction (e.g., a direction associated with the receiving device, such as a UE <NUM>). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based at least in in part on a signal that was transmitted in different beam directions. For example, a UE <NUM> may receive one or more of the signals transmitted by the base station <NUM> in different directions, and the UE <NUM> may report to the base station <NUM> an indication of the signal it received with a highest signal quality, or an otherwise acceptable signal quality. Although these techniques are described with reference to signals transmitted in one or more directions by a base station <NUM>, a UE <NUM> may employ similar techniques for transmitting signals multiple times in different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE <NUM>), or transmitting a signal in a single direction (e.g., for transmitting data to a receiving device).

In some examples, signal waveforms transmitted over a carrier may be made up of multiple sub-carriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or DFT-s-OFDM).

Devices of the wireless communications system <NUM> (e.g., base stations <NUM> or UEs <NUM>) may have a hardware configuration that supports communications over a particular carrier bandwidth, or may be configurable to support communications over one of a set of carrier bandwidths. In some examples, the wireless communications system <NUM> may include base stations <NUM> and/or UEs <NUM> that can support simultaneous communications via carriers associated with more than one different carrier bandwidth.

Wireless communications systems such as an NR system may utilize any combination of licensed, shared, and unlicensed spectrum bands, among others. The flexibility of eCC symbol duration and subcarrier spacing may allow for the use of eCC across multiple spectrums. In some examples, NR shared spectrum may increase spectrum utilization and spectral efficiency, specifically through dynamic vertical (e.g., across the frequency domain) and horizontal (e.g., across the time domain) sharing of resources.

Some examples of the wireless communications system <NUM> may support a wireless device that may implement transmission repetitions of a same TB to meet a certain reliability threshold. For example, a base station <NUM> may handle downlink transmission repetitions of a same TB to meet a certain reliability threshold in ultra-reliable low latency communications (URLLC) systems. TBs may be transmitted in any TTI within a slot or subframe (e.g., based on when a packet becomes ready for transmission) in a URLLC system. For example, a TB may be transmitted multiple times to a UE <NUM>. The base stations <NUM> and UEs <NUM> may implement processes to handle these TB repetitions near slot, subframe, or eIMTA boundaries. For example, the number of transmission repetitions for a TB may be based on a TTI index of a TTI used for an initial transmission of the TB. The quantity of repetitions corresponding to a TTI may be based on a proximity of a slot, a subframe, or an eIMTA boundary.

Legacy TDD systems may force all cells to use a same TDD configuration though it may have capability to use different configurations by changing a system information block (SIB) configuration (e.g., SIB1). In some cases, eIMTA may allow a cell or cluster of cells to dynamically adapt downlink/uplink subframe resources based on the actual traffic requirements. For example, a cell may use downlink configuration when downlink traffic is heavy (e.g., above a threshold) and vice versa. In some cases, for TDD eIMTA, these downlink/uplink subframe resources can be configured. For example, a baseline configuration (e.g., an uplink configuration) may be signaled in a SIB. In another example, downlink HARQ reference uplink/downlink configuration may be signaled using RRC. A device (e.g., base station <NUM> or UE <NUM>, or both) may signal a dynamic configuration using L1 reconfiguration DCI. In some examples, uplink subframes and special subframes per SIB configuration may be dynamically reconfigured to downlink subframes. In some cases, a subframe configuration may include one or more anchor subframes and/or non-anchor subframes. An anchor subframe may be a common subframe for a baseline configuration and downlink HARQ reference configuration, while a non-anchor subframe may be adaptively changed between uplink and downlink directions based on L1 signaling.

In some cases, the reconfiguration DCI may carry information to explicitly indicate a possible uplink/downlink configuration. A DCI size may be aligned to a DCI format (e.g., DCI format 1C). The explicit reconfiguration DCI may be transmitted in a primary cell on PDCCH CSS or SCG CSS under DCI. A periodicity of the reconfiguration DCI may span <NUM>, <NUM>, <NUM>, and/or <NUM>. A set of subframes for monitoring reconfiguration DCI may be device-specific configured via RRC. For example, for <NUM>, <NUM>, and <NUM> periodicity, subframes may correspond to subframes in a last radio frame within each periodicity. In case of TDD for a primary cell, downlink and special subframes per SIB can be configured for monitoring the reconfiguration DCI. In case of FDD for the primary cell, any subframe can be configured for monitoring the reconfiguration DCI.

In some cases, the reliability may be improved by allowing a repetition window to span across multiple slots or subframes. A base station <NUM> may schedule and indicate the transmission repetitions of a TB (e.g., a repetition factor K) for all TTIs within the repetition window to a UE <NUM> in control information (e.g., downlink control information (DCI)). A repetition window may refer to a time period spanning one or more TTIs in which a same TB is repeated. As each TTI may include a single TB transmission, a larger number of transmission repetitions may correspond to a longer repetition window (e.g., where the number of TTIs in the repetition window equals the number of TB transmission repetitions).

In some cases, a base station <NUM> may transmit the control information (e.g., in a grant) indicating the initial TTI index for the TB transmission to a UE <NUM>, and the UE <NUM> may determine the quantity of transmission repetitions for the TB based on the TTI index or an explicit indication in the control information. For example, an information field inside a DCI may indicate the total number of repetitions i.e., K. In some cases, a base station <NUM> and/or a UE <NUM> may determine that a portion of the repetitions may extend across a slot, a subframe, or an eIMTA boundary. In this case, the base station <NUM> and/or the UE <NUM> may monitor for the portion of the repetitions extending across the boundary, accordingly. In some examples the total number of repetitions i.e., K may be defined based on whether the base station <NUM> and/or the UE <NUM> are configured to support the repetitions extending across a boundary. By supporting transmission repetitions of a TB, a base station <NUM> and/or a UE <NUM> may provide an efficient manner to enhance communication (e.g., reliability) and reduce latency in the wireless communications system <NUM>.

<FIG> illustrates an example of a wireless communications system <NUM> in accordance with various aspects of the present disclosure. For example, the wireless communications system <NUM> may support repetition-based transmission for downlink and uplink transmissions. In some examples, the wireless communications system <NUM> may implement aspects of the wireless communications system <NUM>. The wireless communications system <NUM> may operate according to a radio access technology (RAT) such as <NUM> LTE or <NUM> NIL although techniques described herein may be applied to any RAT and to systems that may concurrently use two or more different RATs.

The wireless communications system <NUM> may include base station <NUM>-a and UE <NUM>-a, which may be examples of the corresponding devices described with respect to <FIG>. The base station <NUM>-a may provide service for a geographic area <NUM>-a as described with respect to <FIG>. In some examples, the wireless communications system <NUM> may also support transmission repetitions of a TB in an efficient manner to enhance communication (e.g., reliability) in the wireless communications system <NUM>. For example, the wireless communications system <NUM> may be an LTE URLLC system or an NR URLLC system, etc., in which base station <NUM>-a and/or UE <NUM>-a support transmission repetitions of a TB.

In TB repetition, the base station <NUM>-a and/or the UE <NUM>-a may transmit same TB multiple times over multiple TTIs. In some cases, these TTIs may be referred to as shortened TTIs (sTTIs) or mini-slots, and may span any length of time (e.g., two symbols, three symbols, etc.). In some cases, for reduced latency, the base station <NUM>-a and/or the UE <NUM>-a may transmit a TB as soon as a packet is generated and ready for transmission in the TB. In these cases, the device may transmit a TB in any TTI within a slot of a subframe that supports data transmission (e.g., any subframe other than a control subframe in a downlink or any subframe in an uplink).

In some cases, depending on the TTI used for the initial TB transmission, transmitting a certain quantity of repetitions of the TB may result in the transmission repetitions crossing a defined boundary (e.g., a slot boundary, a subframe boundary, and/or an eIMTA boundary). In this case, when a transmission repetition extends across the defined boundary, the base station <NUM>-a and/or the UE <NUM>-a may or may not be able to keep a phase continuity. For example, different repetitions of the same transmission crossing such a boundary may result in complex multiplexing for longer channels for different repetitions of the TB. Such discrepancies may cause a loss of coherency between the repetitions. In some cases, this may impact the possibility for demodulation reference signal (DMRS) sharing or DMRS combining. Alternatively, for the eIMTA case, when a transmission repetition crosses an eTMTA boundary (e.g., from downlink to uplink), the phase continuity may not need to be maintained.

The wireless communications system <NUM> may support one or more repetition configurations for TBs for managing repeated transmissions that do cross these boundaries to handle these potential issues. The base station <NUM>-a and/or the UE <NUM>-a may be configured with the repetition configuration. A repetition configuration may indicate whether transmission repetitions of a TB can or cannot cross a boundary (e.g., slot, subframe, and/or eIMTA boundary). Thereby, the base station <NUM>-a and/or the UE <NUM>-a may handle repeated transmissions of a TB that do or do not cross these boundaries based on the repetition configuration. In some examples, the repetition configuration may be based on a device capability of the base station <NUM>-a and/or the UE <NUM>-a, in addition to its associated configuration signaling. Additionally, or alternatively, the repetition configuration may be based on whether DMRS sharing or DMRS combining across TTIs on either side of a boundary is provided. For example, the base station <NUM>-a and/or the UE <NUM>-a may be configured to transmit reference signals (e.g., demodulation reference signals (DMRSs)) on both sides of a boundary (e.g., within a repetition window) to support reception of the transmission repetitions <NUM>.

In some cases, the base station <NUM>-a and/or the UE <NUM>-a may determine the transmission repetitions <NUM> of a TB, and schedule the TB to be transmitted in a specific TTI corresponding to a TTI index. The number of repetitions (i.e., a repetition factor, K) of this TB may be based on the TTI index. In some cases, the repetition factor K corresponding to a TTI may depend on slot boundaries, subframe boundaries, or eIMTA boundaries. For example, to avoid transmission repetitions crossing a boundary, a TTI index indicating a TTI close to a boundary for a subsequent TTI may correspond to a lower repetition factor than a TTI index indicating a TTI farther from the boundary for the subsequent TTI. The repetition factors may or may not depend on slot, subframes, and/or eIMTA boundaries. In some examples, a repetition factor K may depend on whether the base station <NUM>-a and/or the UE <NUM>-a are configured to handle repeated transmissions of a TB that do cross a boundary. The value of the repetition factor K may be pre-determined or dynamically configured, and may correspond to any number of TTIs (e.g., K may have a value of <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, etc. or until an end of a slot or a subframe).

The base station <NUM>-a may transmit control information <NUM>, during a TTI, to the UE <NUM>-a via bidirectional link <NUM>, where the control information <NUM> indicates an indication of transmission repetitions <NUM> of a TB for multiple TTls. The control information may include DCI transmitted on a physical downlink control channel (PDCCH) during the TTI. In some cases, this indication may be an explicit indication (e.g., a TTI value indicator) or an implicit indication (e.g., based on the timing of the control information <NUM>, resources used for the control information <NUM>, etc.). In some examples, the control information <NUM> may be part of a grant and may be an example of a dynamic grant, a semi-persistent scheduling grant, or a persistent scheduling grant. The grant may be for downlink or uplink resources.

The control information <NUM> may include an explicit indication of the quantity of transmission repetitions <NUM> for the TB corresponding to the TTI index. In other cases, the UE <NUM>-a may determine the quantity of transmission repetitions <NUM> based on the received indication of the TTI index. The UE <NUM>-a may determine a repetition window based on the TTI and the number of transmission repetitions. For example, because each repetition of the TB may be transmitted in a separate TTI, the repetition window may span a number of TTIs equal to the number of transmission repetitions (and, correspondingly, equal to the value of the repetition factor), and may start with the TTI corresponding to the TTI index for the initial TB transmission. The UE <NUM> may then monitor for the transmission repetitions <NUM> of the 'TB based on the quantity of transmission repetitions of the TB and/or the repetition window.

The UE <NUM>-a may identify a TTI index for an initial transmission associated with the transmission repetitions <NUM> of the TB, and determine that a portion of the transmission repetitions <NUM> extend across a subframe, slot, and/or eIMTA boundary based on the TTI index and the received control information. In this case, the UE <NUM>-a may monitor for the transmission repetitions <NUM> of the TB based on determining whether it is configured to handle repeated transmissions of a TB that does cross one of these boundaries based on the repetition configuration (e.g., UE-capability). In some examples, this determination may be implicit or explicit. For example, the UE <NUM>-a may identify that it is not configured to support transmission repetitions <NUM> that extend across a boundary based on the identified UE-capability. In some cases, a portion of the transmission repetitions <NUM> may extend across an uplink portion of a special switching subframe (SSF) associated with a subframe, or an uplink subframe in case of a downlink transmission repetitions. In this case, the base station <NUM>-a may indicate in a DCI a reconfiguration of a subframe reconfiguration to the UE <NUM>-a. Additionally or alternatively, the UE <NUM>-a may utilize repetition windows that cross subframe boundaries. For example, the UE <NUM>-a may increase the transmission reliability by allowing repetition windows to span across more than one subframe, increasing the number of transmission repetitions of the TB. To improve the reception reliability, the UE <NUM>-a may transmit reference signals (e.g., DMRSs) on either side of the boundary if a repetition window spans across the boundary.

<FIG> illustrates an example of a configuration <NUM>-a in accordance with aspects of the present disclosure. In some examples, the configuration <NUM>-a may implement aspects of the wireless communications systems <NUM> and <NUM>. For example, the configuration <NUM>-a may support TB repetition handling for downlink and uplink transmissions. The configurations <NUM>-a may illustrate examples of repetition windows <NUM> for transmission repetitions <NUM> of TBs in an uplink or downlink, where the repetition windows <NUM> may be constrained to a single subframe. As illustrated, a subframe may span two slots and contain six TTIs <NUM> configured in a <NUM>-<NUM>-<NUM>-<NUM>-<NUM>-<NUM> pattern, which may define the respective number of OFDM symbols in each TTI of the subframe. The <NUM>-<NUM>-<NUM>-<NUM>-<NUM>-<NUM> pattern may be used to prevent one of the TTIs <NUM> from spanning a boundary <NUM>-a, which may be a slot boundary, a subframe boundary, or an eIMTA boundary, or a combination thereof. In some examples, one or more of the TTIs <NUM> may be an anchor TTI or a non-anchor TTI. In addition, a portion of the TTIs <NUM> may be allocated for downlink transmission, a second portion of the TTIs <NUM> may be allocated for uplink transmission, and a third portion of TTIs <NUM> may be allocated for downlink/uplink reconfiguration (e.g., a special TTI/subframe).

Each repetition window <NUM> may correspond to a TTI <NUM> (e.g., based on the TTI index). If an initial TB transmission occurs in a given TTI <NUM>, the base station <NUM>-a and/or the UE <NUM>-a may determine the quantity of transmission repetitions <NUM> to perform for the TB based on the TTI index for this initial transmission. The repetition windows <NUM> configured for each TTI <NUM> may be further based on the boundary <NUM>-a (e.g., slot boundary or eIMTA boundary) and another boundary <NUM>-a (e.g., a subframe boundary). For example, if an initial transmission of a TB is scheduled for TTI <NUM>-b, the base station <NUM>-a and/or the UE <NUM>-a may identify the corresponding repetition window <NUM>-a for transmission repetitions <NUM> of the TB based on the TTI index of TTI <NUM>-b. In some cases, the term "transmission repetitions" may refer to every transmission of the TB in the repetition process (e.g., including the initial transmission).

Repetition window <NUM>-a may span TTI <NUM>-a, TTI <NUM>-b, TTI <NUM>-c, and TTI <NUM>-d, corresponding to a repetition factor of K = <NUM>. The repetition factor K may indicate the number of transmissions of the same TB for the base station <NUM>-a and/or the UE <NUM>-a to perform, where the value of K is equal to the number of TTIs <NUM> spanned by the repetition window <NUM>. In the scenario described above, the base station <NUM>-a and/or the UE <NUM>-a may initially transmit a TB in TTI <NUM>-b, and may transmit the same TB again in TTI <NUM>-c, etc. Repetition window <NUM>-a may stop at TTI <NUM>-c due to the boundary <NUM>-a. Repetition windows <NUM> for the other TTI indexes may be defined in a similar manner. For example, TTI <NUM>-c may correspond to repetition window <NUM>-b with a K value of <NUM>, TTI <NUM>-d may correspond to repetition window <NUM>-c with a K value of <NUM> (e.g., where the repetition window <NUM> ends based on the boundary <NUM>-a), TTI <NUM>-e may correspond to repetition window <NUM>-d with a K value of <NUM>, and TTI <NUM>-f may correspond to repetition window <NUM>-e with a K value of <NUM>. These repetition factors K for the given repetition windows <NUM> are provided as examples, and other K values may be implemented for repetition windows <NUM> corresponding to certain TTI indexes.

In some cases where a boundary (e.g., the boundary <NUM>-a and/or the boundary <NUM>-a) cannot be crossed, the UE <NUM>-a may determine that there are not sufficient TTIs <NUM> remaining until an end of a subframe. For example, the UE <NUM>-a may receive control information including an indication of transmission repetitions <NUM> of a TB during TTI <NUM>-c where the repetition factor K value is <NUM>. As such, the UE <NUM>-a may only expect to receive three transmission repetitions (e.g., for TTI <NUM>-d, TTI <NUM>-e, and TTI <NUM>-f). Additionally, in this case, the UE <NUM>-a may determine how to handle the transmission repetitions <NUM> that extend across the boundary <NUM>-a (e.g., slot boundary and/or eIMTA boundary). For example, the UE <NUM>-a may determine a quantity of available TTIs <NUM> for the transmission repetitions <NUM> of the TB and monitor for the transmission repetitions <NUM> based on the quantity of available TTIs <NUM>. The UE <NUM>-a may determine that the quantity of available TTIs <NUM> is below the plurality of TTIs for the quantity of transmission repetitions <NUM> of the TB, and suspend monitoring at least one TTI of the plurality after an ultimate TTI <NUM> of the quantity of available TTIs <NUM>.

In some cases, the UE <NUM>-a may not expect to receive control information (e.g., DCI) indicating a K value that requires crossing a boundary (e.g., slot boundary and/or eIMTA boundary) based on its configuration, and as such may allow transmission repetitions <NUM> to go on until an end of a subframe or an eIMTA. In some cases, where TTI <NUM> may be subframes, the base station <NUM>-a and/or the UE <NUM>-a may determine that a portion of transmission repetitions <NUM> of a TB may extend across an uplink part of an SSF, an uplink subframe. In the case that the base station <NUM>-a performs this determination, it may transmit a dynamic configuration using L1 reconfiguration DCI to the UE <NUM>-a indicating that a subframe configuration may change, for example, a downlink subframe may change to an uplink subframe. Additionally, the base station <NUM>-a. and/or the UE <NUM>-a may allow transmission repetitions <NUM> to go on until an end of the uplink subframe.

<FIG> illustrates an example of a configuration <NUM>-b in accordance with aspects of the present disclosure. In some examples, the configuration <NUM>-b may implement aspects of the configuration <NUM>-a. In some examples, the configuration <NUM>-b may implement aspects of the wireless communications systems <NUM> and <NUM>. For example, the configuration <NUM>-b may support TB repetition handling for downlink and uplink transmissions. The configurations <NUM>-b may illustrate examples of repetition windows <NUM> for transmission repetitions <NUM> of TBs in an uplink or downlink, where the repetition windows <NUM> may be span one or more TTIs.

In some cases, the base station <NUM>-a and/or the UE <NUM>-a may determine that a portion of the transmission repetitions <NUM> extend across the boundary <NUM>-a and/or the boundary <NUM>-b (e.g., a slot boundary or an eIMTA boundary, or both) based at least in part on the TTI index of the initial transmission and the received control information. The UE <NUM>-a may also identify that it is configured to support extending across the boundary <NUM>-a and/or the boundary <NUM>-b. If crossing the boundary <NUM>-a and/or the boundary <NUM>-b is allowable, the base station <NUM>-a and/or the UE <NUM>-a may determine a TTI pattern in a next subframe and/or eIMTA. For example, the base station <NUM>-a and/or the UE <NUM>-a may identify a quantity of available TTIs <NUM> (e.g., <NUM>-j) in a second slot of a second subframe, occurring after the boundary <NUM>-a and/or the boundary <NUM>-b.

In some cases, the base station <NUM>-a and/or the UE <NUM>-a may not expect for a portion of the transmission repetitions <NUM> to extend across the boundary <NUM>-a and/or the boundary <NUM>-b (e.g., a slot boundary or an eIMTA boundary, or both), for example, based at least in part on a specification configuration and/or the capability of the base station <NUM>-a and/or the UE <NUM>-a. In some examples, the base station <NUM>-a and/or the UE <NUM>-a may determine that a physical downlink shared channel (PDSCH) is not mapped to resources of a TTI <NUM> in a second slot and/or a second subframe based on the quantity of available TTIs. As a result, the base station <NUM>-a and/or the UE <NUM>-a may puncture the TTI (e.g., TTI <NUM>-j) based on the PDSCH not being mapped to the TTI, and monitor the portion of the transmission repetitions based on the puncturing. For example, the UE <NUM>-a may receive a repetition factor K that may have a value that requires a portion of the transmission repetitions <NUM> to extend across the boundary <NUM>-a and/or the boundary <NUM>-b, the UE <NUM>-a may then assume that a last transmission is over a last TTI <NUM> of a current subframe, i.e., other transmission on the other side of the boundary <NUM>-a and/or the boundary <NUM>-b may be punctured.

In some cases, the base station <NUM>-a and/or the UE <NUM>-a may determine whether an initial TTI associated with the TTI index is available for the initial transmission associated with the transmission repetitions <NUM> of the TB. In some examples, the UE <NUM><NUM>-a may receive a control format indicator (CFI) transmitted via RRC that may indicate that TTI <NUM>-d is configured for control channel signaling. For example, a value of "<NUM>" in a field of a CFI may indicate that the initial TTI associated with the TTI index is available for transmissions, while a value of "<NUM>" in the field of the CFI may indicate that the initial TTI is unavailable for transmissions. In this case, the initial TB transmissions may not occur in TTI <NUM>-d, and no repetition window <NUM> may be defined to correspond to this TTI index. As such, the UE <NUM>-a may postpone the initial transmission associated with the transmission repetitions <NUM> of the TB to a later TTI, for example, TTI <NUM>-e.

In some cases, the UE <NUM>-a may be expected to receive remaining PDSCH starting right after the TTI <NUM>-d. Alternatively, the UE <NUM>-a may puncture the transmission and monitor for a subsequent transmission repetition <NUM> during a following TTI. In this case, the repetition factor K may be K-<NUM>. The UE <NUM>-a may determine whether to postpone or puncture the initial transmission based on whether the CFI is indicated dynamically or semistatically. For example, the UE <NUM>-a may receive the CFI on a physical control format indicator channel (PCFICH) or via higher layer signaling, and determine to postpone or puncture the initial transmission based on whether the CFI is indicated dynamically or semistatically.

By supporting transmission repetitions of a TB, the base station <NUM>-a and/or the UE <NUM>-a may provide an efficient manner to enhance reliability and reduce latency in the wireless communications system <NUM>. For grant-based uplink TB transmission repetitions, similar processes may be performed as described above for the downlink.

<FIG> illustrates an example of a process flow <NUM> in accordance with aspects of the present disclosure. In some examples, the process flow <NUM> may implement aspects of the wireless communications system <NUM> and <NUM>. The process flow <NUM> may also support transmission repetitions of a TB for downlink and uplink transmissions in an efficient manner to enhance communication (e.g., reliability) and reduce latency in a wireless communications system. Base station <NUM>-b and UE <NUM>-b may be examples of the corresponding devices described with reference to <FIG> and <FIG>.

In the following description of the process flow <NUM>, the operations between the base station <NUM>-b and the UE <NUM>-b may be transmitted in a different order than the exemplary order shown, or the operations performed by the base station <NUM>-b and the UE <NUM>-b may be performed in different orders or at different times. Certain operations may also be left out of the process flow <NUM>, or other operations may be added to the process flow <NUM>.

In some examples, the process flow <NUM> may commence with the base station <NUM>-b establishing a connection with the UE <NUM>-b (e.g., performing a cell acquisition procedure, a random access procedure, an RRC connection procedure, an RRC configuration procedure). The base station <NUM>-b may send grants (e.g., in control information) to the UE <NUM>-b to schedule either uplink or downlink transmission repetitions for a TB, as part of the connection establishment.

At <NUM>, the base station <NUM>-b may optionally identify a TTI index for an initial transmission of a TB. The TB may be an example of an uplink TB or a downlink TB, and the TTI may be, additionally or alternatively, part of a slot of a subframe. In some examples, the TTI may be an sTTI. At <NUM>, the base station <NUM>-b may also optionally determine a quantity of transmission repetitions for the TB based on the TTI index. In some cases, the correlation between the number of transmission repetitions and the TTI index may be based on a slot boundary, a subframe boundary, an eIMTA boundary, or a combination thereof.

At <NUM>, the base station <NUM>-b may transmit control information to the UE <NUM>-b. For example, the base station <NUM>-b may transmit a grant to the UE <NUM>-b. This grant may be an example of a downlink grant or an uplink grant. The grant may indicate resources to use for TB transmission or TB reception, including an indication of transmission repetitions (e.g., the repetition factor K) of a TB for a plurality of TTIs, or of the TTI index for the initial transmission of the TB, or both. In some examples of eIMTA, the wireless communications systems as described herein may determine whether repetitions in downlink can extend across an uplink subframe. The techniques describe herein for TB repetitions crossing a boundary (e.g., slot boundary, subframe boundary) may similarly be performed for downlink subframes, special subframes, uplink subframes, etc. (e.g., DSUD subframes). For example, if the base station <NUM>-b and/or the UE <NUM>-b are providing transmission repetitions using DSUD subframes, and a portion of the transmission repetitions needs to cross an uplink part of an uplink subframe to reach the next downlink subframe, the base station <NUM>-b and/or the UE <NUM>-b may support techniques describe herein for TB repetitions crossing a boundary (e.g., slot boundary, subframe boundary) and apply it to DSUD subframes (e.g., such as puncturing delaying, etc. a transmission repetition).

At <NUM>, the UE <NUM>-b may receive the control information from the base station <NUM>-b. At <NUM>, the UE <NUM>-b may identify the quantity of transmission repetitions of the TB. The identification may be based on the received control information. At <NUM>, the UE <NUM>-b may optionally determine whether the UE <NUM>-b is configured to support extending across a subframe boundary, an eIMTA boundary, or a slot boundary, or a combination thereof.

At <NUM>, the UE <NUM>-b may monitor for the transmission repetitions of the TB, for example, based on the identified quantity of transmission repetitions and/or the determination of whether the UE <NUM>-b is configured to support extending across a boundary (i.e., a subframe boundary, an eIMTA boundary, or a slot boundary, or a combination thereof). In some examples, the UE <NUM>- may monitor for the transmission repetitions of the TB based on the TTI index and the determined number of transmission repetitions. For example, UE <NUM>-b may monitor in a repetition window starting with the TTI corresponding to the indicated TTI index, and spanning a number of TTIs equal to the determined number of transmission repetitions. A repetition window may refer to a time period spanning one or more TTIs in which a same TB is repeated. As each TTI may contain a single TB transmission, a larger number of transmission repetitions may correspond to a longer repetition window (e.g., where the number of TTIs in the repetition window equals the number of TB transmission repetitions). In some examples, the UE <NUM>-b may receive the TB based on receiving one or more downlink transmission repetitions of the TB during the monitoring process. Alternatively, the UE <NUM>-b may transmit uplink transmission repetitions of the TB based on the TTI index and the identified number of transmission repetitions, for which the base station <NUM>-b may monitor for these TB repetitions in the repetition window defined by the initial TTI and the number of transmission repetitions.

<FIG> shows a block diagram <NUM> of a device <NUM> in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a device as described herein. The device <NUM> may include a receiver <NUM>, a communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver <NUM> may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to more details on supporting repetition-based transmission, etc.). Information may be passed on to other components of the device <NUM>. The receiver <NUM> may be an example of aspects of the transceiver <NUM> described with reference to <FIG>. The receiver <NUM> may utilize a single antenna or a set of antennas.

The communications manager <NUM> may receive, during a TTI of a subframe, control information including an indication of transmission repetitions of a TB for a set of TTIs, identify a quantity of transmission repetitions of the TB based on the control information, and monitor for the transmission repetitions of the TB based on the identifying. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein.

The device <NUM> or any other device described herein (e.g., a UE <NUM>) may beneficially support repetition based transmission as described herein. For example, the device <NUM> may manage the transmission, reception, or both, of multiple repetitions of a TB transmission, which may result in improved repetition coherency of the transmitted TB.

If implemented in code executed by a processor, the functions of the communications manager <NUM>, or its sub-components may be executed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

<FIG> shows a block diagram <NUM> of a device <NUM> in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a device <NUM> or a device <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver <NUM> may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to more details on supporting repetition-based transmission, etc.). For example, the receiver <NUM> may receive, during a TTI of a subframe, control information including an indication of transmission repetitions of a TB for a set of TTIs. Information may be passed on to other components of the device <NUM>. The receiver <NUM> may be an example of aspects of the transceiver <NUM> described with reference to <FIG>. The receiver <NUM> may utilize a single antenna or a set of antennas.

The communications manager <NUM> may be an example of aspects of the communications manager <NUM> as described herein. The communications manager <NUM> may include an identification component <NUM> and a monitoring component <NUM>. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein. The identification component <NUM> may identify a quantity of transmission repetitions of the TB based on the control information. The monitoring component <NUM> may monitor for the transmission repetitions of the TB based on the identifying.

<FIG> shows a block diagram <NUM> of a communications manager <NUM> in accordance with aspects of the present disclosure. The communications manager <NUM> may be an example of aspects of a communications manager <NUM>, a communications manager <NUM>, or a communications manager <NUM> described herein. The communications manager <NUM> may include an identification component <NUM>, a monitoring component <NUM>, a determination component <NUM>, a suspending component <NUM>, a puncturing component <NUM>, and a delay component <NUM>. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).

In some examples, the identification component <NUM> may identify a value in a field of a CFI associated with the control information. In some examples, the value in the field of the CFI may be <NUM>. In some examples, the identification component <NUM> may identify a configuration of a wireless device (e.g., a device <NUM>, a device <NUM>, or a UE <NUM>). In some examples, identifying the configuration may be based on a capability of the wireless device. The capability may include a DMRS sharing capability, a DMRS combining capability, a configuration signaling, or an indication of the DMRS sharing capability or the DMRS combining capability relative to TTIs on each side of a subframe boundary, or a combination thereof.

In some examples, the identification component <NUM> may identify that the device <NUM>, the device <NUM>, or a device as described herein is not configured to support extending across the subframe boundary or the slot boundary based on the configuration. In some examples, the identification component <NUM> may identify that the device <NUM>, the device <NUM>, or a device as described herein is configured to support extending across the subframe boundary or the slot boundary based on the configuration. In some examples, the identification component <NUM> may identify a quantity of available TTIs in a second slot of a second subframe based on the device <NUM>, the device <NUM>, or a device as described herein being configured to support extending across the subframe boundary or the slot boundary.

In some examples, the identification component <NUM> may identify a TTI index for an initial transmission associated with the transmission repetitions of the TB. In some examples, the identification component <NUM> may identify a value in a field of a CFI associated with the control information, where determining whether the initial TTI is available for the initial transmission is further based on the value in the field of the CFI.

In some examples, the identification component <NUM> may identify that the device <NUM>, the device <NUM>, or a device as described herein is not configured to support extending across an eIMTA boundary based on the configuration, where monitoring for the transmission repetitions of the TB further includes suspending monitoring a portion of the transmission repetitions occurring after the eIMTA boundary based on the device <NUM>, the device <NUM>, or a device as described herein not being configured to support extending across the eIMTA boundary. In some examples, the identification component <NUM> may identify that the device <NUM>, the device <NUM>, or a device as described herein is configured to support extending across the eIMTA boundary based on the configuration, where monitoring for the transmission repetitions of the TB further includes monitoring for the portion of the transmission repetitions occurring after the eIMTA boundary based on the device <NUM>, the device <NUM>, or a device as described herein being configured to support extending across the eIMTA boundary. In some examples, the identification component <NUM> may identify a quantity of available TTIs in a second slot of a second subframe based on the device <NUM>, the device <NUM>, or a device as described herein being configured to support extending across the eIMTA boundary.

The monitoring component <NUM> may monitor for the transmission repetitions of the TB based on the identifying. In some examples, the monitoring component <NUM> may monitor the portion of the transmission repetitions extending across the subframe boundary or the slot boundary based on the configuration. In some examples, the monitoring component <NUM> may monitor the portion of the transmission repetitions during the second slot of the second subframe based on the puncturing. In some examples, the monitoring component <NUM> may monitor for a subsequent TB transmission of the quantity of transmission repetitions during a second TTI after the initial TTI. In some examples, the monitoring component <NUM> may monitor the portion of the transmission repetitions extending across the eIMTA boundary based on the configuration.

In some examples, the monitoring component <NUM> may monitor a PDSCH for the transmission repetitions of the TB. The determination component <NUM> may determining that a second TTI is not available for transmitting one of the transmission repetitions of the TB based at least in part on the value in the field of the CFI. In some examples, the second TTI may be a mini-slot. In some examples, the determination component <NUM> may enable a wireless device (e.g., a device <NUM>, a device <NUM>, or a UE <NUM>) to realize one or more of the advantages described herein. For example, the determination component <NUM> may enable a wireless device to avoid monitoring the second TTI, which may result in lower computational complexity, beneficial power savings, among other advantages.

In some examples, the determination component <NUM> may determine whether the device <NUM>, the device <NUM>, or a device as described herein is configured to support extending across a subframe boundary or a slot boundary based on the configuration. In some examples, the determination component <NUM> may determine that a portion of the transmission repetitions extend across the subframe boundary or the slot boundary based on the TTI index of the initial transmission and the control information.

In some examples, the determination component <NUM> may determine a quantity of available TTIs for the transmission repetitions of the TB based on the device <NUM>, the device <NUM>, or a device as described herein not being configured to support extending across the subframe boundary or the slot boundary. In some examples, the determination component <NUM> may determine that the quantity of available TTIs is below the set of TTIs for the quantity of transmission repetitions of the TB. In some examples, the determination component <NUM> may determine that a portion of the transmission repetitions extend across the subframe boundary or the slot boundary based on the TTI index of the initial transmission and the control information. In some examples, the determination component <NUM> may determine that a PDSCH is not mapped to resources of a TTI in the second slot of the second subframe based on identifying the quantity of available TTIs.

In some examples, the determination component <NUM> may determine whether an initial TTI associated with the TTI index is available for the initial transmission associated with the transmission repetitions of the TB based on the control information. In some examples, the determination component <NUM> may determine that the initial TTI associated with the TTI index is unavailable for the initial transmission based on the value in the field of the CFI. In some examples, the determination component <NUM> may determine that the initial TTI associated with the TTI index is unavailable for the initial transmission based on the value in the field of the CFI,.

In some examples, the determination component <NUM> may determine whether the device <NUM>, the device <NUM>, or a device as described herein is configured to support extending across an eIMTA boundary based on the configuration. In some examples, the determination component <NUM> may determine a subframe configuration of the subframe based on the control information. In some examples, the determination component <NUM> may determine that a portion of the transmission repetitions extend across the eIMTA boundary based on the subframe configuration.

In some examples, the determination component <NUM> may determine a quantity of available TTIs for the transmission repetitions of the TB based on the device <NUM>, the device <NUM>, or a device as described herein not being configured to support extending across the eIMTA boundary, where monitoring for the transmission repetitions of the TB is further based on the quantity of available TTIs. In some examples, the determination component <NUM> may determine that a portion of the transmission repetitions extend across the eIMTA boundary based on the TTI index of the initial transmission and the control information. In some examples, the determination component <NUM> may determine to monitoring for the transmission repetitions of the TB until an ultimate TTI of the quantity of available TTIs based at least in part on an indication received in a DCI.

In some examples, the determination component <NUM> may determine that the portion of the transmission repetitions extend across an uplink portion of a special switching subframe (SSF) associated with the subframe configuration, where monitoring for the transmission repetitions of the TB further comprises suspending monitoring the portion of the transmission repetitions occurring after the uplink portion of the SSF based at least in part on the wireless device not being configured to support extending across the SSF. In some examples, the determination component <NUM> may determine that the portion of the transmission repetitions extend across an uplink subframe associated with the subframe configuration, where the transmission repetitions are in a downlink transmission and monitoring for the transmission repetitions of the TB further comprises suspending monitoring the portion of the transmission repetitions occurring after the uplink subframe based at least in part on the wireless device not being configured to support extending across the uplink subframe.

In some examples, the determination component <NUM> may determine that the portion of the transmission repetitions extend across an uplink portion of a SSF associated with the subframe configuration, where monitoring for the transmission repetitions of the TB further comprises delaying or puncturing a subframe following the SSF for monitoring the portion of the transmission repetitions occurring after the uplink portion of the SSF based at least in part on the wireless device being configured to support extending across the SSF. In some examples, the determination component <NUM> may determine that the portion of the transmission repetitions extend across an uplink subframe associated with the subframe configuration, where the transmission repetitions are in a downlink transmission and monitoring for the transmission repetitions of the TB further comprises delaying or puncturing a subframe following the uplink subframe for monitoring the portion of the transmission repetitions occurring after the uplink subframe based at least in part on the wireless device being configured to support extending across the uplink subframe.

The suspending component <NUM> may suspend monitoring at least one TTI of the set after an ultimate TTI of the quantity of available TTIs. The puncturing component <NUM> may puncture the TTI in the second slot of the second subframe based on the PDSCH not being mapped to the TTI. In some examples, the puncturing component <NUM> may puncture the initial TTI based on determining that the initial TTI is unavailable. In some examples, the puncturing component <NUM> may puncture the TTI in the second slot of the second subframe based on the PDSCH not being mapped to the TTI. The delay component <NUM> may delay the initial transmission to a second TTI after the initial TTI.

<FIG> shows a diagram of a system <NUM> including a device <NUM> in accordance with aspects of the present disclosure. The device <NUM> may be an example of or include the components of device <NUM>, device <NUM>, or a device as described herein. The device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager <NUM>, an I/O controller <NUM>, a transceiver <NUM>, an antenna <NUM>, memory <NUM>, and a processor <NUM>. These components may be in electronic communication via one or more buses (e.g., bus <NUM>).

The communications manager <NUM> may receive, during a TTI of a subframe, control information including an indication of transmission repetitions of a TB for a set of TTIs, identify a quantity of transmission repetitions of the TB based on the control information, and monitor for the transmission repetitions of the TB based on the identifying.

In some cases, the I/O controller <NUM> may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS2®, UNIX®, LINUX®, or another known operating system.

The processor <NUM> may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor <NUM> may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into the processor <NUM>. The processor <NUM> may be configured to execute computer-readable instructions stored in a memory (e.g., the memory <NUM>) to cause the device <NUM> to perform various functions (e.g., functions or tasks supporting more details on supporting repetition-based transmission for downlink and/or uplink).

<FIG> shows a flowchart illustrating a method <NUM> in accordance with aspects of the present disclosure. The operations of method <NUM> may be implemented by a device or its components as described herein. For example, the operations of method <NUM> may be performed by a communications manager as described with reference to <FIG>. In some examples, a device may execute a set of instructions to control the functional elements of the device to perform the functions described below. Additionally or alternatively, a device may perform aspects of the functions described below using special-purpose hardware.

At <NUM>, the device may receive, during a TTI of a subframe, control information including an indication of transmission repetitions of a TB for a set of TTIs. In some examples, the receiving of the control information may occur during the TTI of a slot (e.g., a first slot or a second slot) of the subframe. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a receiver as described with reference to <FIG>.

At <NUM>, the device may identify a quantity of transmission repetitions of the TB based on the received control information. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by an identification component as described with reference to <FIG>.

At <NUM>, the device may monitor for the transmission repetitions of the TB based on the identifying. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a monitoring component as described with reference to <FIG>.

At <NUM>, the device may receive, during a TTI of a subframe, control information including an indication of transmission repetitions of a TB for a set of TTIs. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a receiver as described with reference to <FIG>.

At <NUM>, the device may identify a quantity of transmission repetitions of the TB based on the control information. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by an identification component as described with reference to <FIG>.

At <NUM>, the device may identify a configuration of the device. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by an identification component as described with reference to <FIG>.

At <NUM>, the device may determine whether the device is configured to support extending across a subframe boundary or a slot boundary based on the configuration. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a determination component as described with reference to <FIG>.

At <NUM>, the device may determine whether the device is configured to support extending across an eIMTA boundary based on the configuration. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a determination component as described with reference to <FIG>.

At <NUM>, the device may monitor for the transmission repetitions of the TB. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a monitoring component as described with reference to <FIG>.

<FIG> shows a flowchart illustrating a method <NUM> in accordance with aspects of the present disclosure. The operations of method <NUM> may be implemented by a device or its components as described herein. For example, the operations of method <NUM> may be performed by a communications manager as described with reference to <FIG>. In some examples, a device may execute a set of structions to control the functional elements of the device to perform the functions described below. Additionally or alternatively, a device may perform aspects of the functions described below using special-purpose hardware.

At <NUM>, the device may determine a subframe configuration of the subframe based on the control information. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a determination component as described with reference to <FIG>.

At <NUM>, the device may determine that a portion of the transmission repetitions extend across the eIMTA boundary based on the subframe configuration. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a determination component as described with reference to <FIG>.

An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) <NUM> (Wi-Fi), IEEE <NUM> (WiMAX), IEEE <NUM>, Flasli-OFDM, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS).

The various illustrative blocks and modules described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.

By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable read only memory (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

Claim 1:
A method for wireless communications at a wireless device (<NUM>; <NUM>; <NUM>; <NUM>), comprising:
receiving (<NUM>; <NUM>; <NUM>; <NUM>; <NUM>), during a transmission time interval, TTI (<NUM>), of a subframe, control information (<NUM>) comprising an indication of transmission repetitions (<NUM>) of a transport block, TB, for a plurality of TTIs;
identifying (<NUM>; <NUM>; <NUM>; <NUM>; <NUM>) a quantity of transmission repetitions of the TB based at least in part on the control information;
identifying a value in a field of a control format indicator, CFI, associated with the control information;
determining that a second TTI is not available for transmitting one of the transmission repetitions of the TB based at least in part on the value in the field of the CFI; and
monitoring (<NUM>; <NUM>; <NUM>; <NUM>; <NUM>) for the transmission repetitions of the TB based at least in part on the identified quantity of transmission repetitions and the determination that the second TTI is not available.