Patent Description:
The following documents relate to scheduling resource in multiple frequency bands, by making use of control signalling such as DCI.

<CIT> discloses methods and apparatus wherein communication is carried out using a transmission time interval (TTI) that is suitable for a future radio communication system. A user terminal comprises a receiving section configured to receive a downlink signal; a transmitting section configured to transmit an uplink signal; and a control section configured to control a transmission time interval (TTI) used in reception of the downlink signal and/or used in transmission of the uplink signal. The control section is operable to set a second transmission time interval (TTI) that is shorter than a <NUM> first transmission time interval (TTI).

<CIT> discloses a method for adaptive transmission time intervals (TTIs) comprising the steps of transmitting, by a communications controller to a user equipment (UE), a segment of a first TDD TTI configuration of a first TDD interval and a second TDD TTI configuration of the first TDD interval, where the first TDD TTI configuration has a first pattern, where the second TDD TTI configuration has a second pattern, where the first pattern is different than the second pattern, where the first TDD TTI configuration has a first uplink TTI segment and a first downlink TTI segment. The method also comprises transmitting a first plurality of data on a first TTI in the first downlink TTI segment of the first TDD TTI configurations of the first TDD interval and receiving a second plurality of data on the first uplink segment of the first TDD TTI configuration of the first TDD interval.

<CIT> discloses a method and system in which a PDSCH segment assigned to a UE in a particular TTI not only carries data to the UE but also carries an assignment to the UE of a PDSCH in a subsequent TTI for carrying additional data to the UE in that subsequent TTI. Such an arrangement can help make good use of possibly otherwise unused PDSCH capacity and can help to manage PDCCH capacity in the subsequent TTI.

The invention is defined in the appendend independent claims. Specific embodiments are defined in the dependent claims.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the accompanying drawings and specification.

The wireless network <NUM> may include a number of BSs <NUM> (shown as BS <NUM>10a, BS 110b, BS 110c, and BS 110d) and other network entities.

In some aspects, a base station <NUM> may serve different UEs <NUM> of different categories, different UEs <NUM> that support different capabilities, and/or the like. For example, the base station <NUM> may serve a first UE 120f that has a less advanced capability (e.g., a lower capability) and a second UE <NUM> that has a more advanced capability (e.g., a higher capability). For example, the first UE 120f may be a first category of UE <NUM> (e.g., an NR-Lite UE) that is not capable of communicating using a shortened transmission time interval (TTI) (e.g., a slot length of <NUM> or less, <NUM>, <NUM>, <NUM>, <NUM>, and/or the like, depending on a sub-carrier spacing), and the second UE <NUM> may be a second category of UE <NUM> (e.g., an NR UE) that is capable of communicating using the shortened TTI. Additionally, or alternatively, the first UE 120f may have a reduced feature set compared to the second UE <NUM>. In some aspects, the first UE 120f may include an MTC UE, and eMTC UE, an IoT UE, and/or the like, as described above.

Base station <NUM> may be equipped with T antennas 234a through 234t, and UE <NUM> may be equipped with R antennas 252a through 252r, where, in general, T ≥ <NUM> and R ≥ <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 multiplexing communications of UEs that support different transmission time interval lengths, as described in more detail elsewhere herein. For example, 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>, and/or other processes as described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively. In some aspects, memory <NUM> and/or memory <NUM> may comprise a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, the one or more instructions, when executed by one or more processors of the base station <NUM> and/or the UE <NUM>, may perform or direction operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein.

In some aspects, UE <NUM> may include means for receiving (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) first DCI that schedules a start of a data communication in a first TTI on a first frequency band, wherein the first frequency band is configured with an uplink/downlink TDD pattern that is synchronized with a second frequency band; means for receiving or transmitting (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, and/or the like) a first portion of the data communication in the first TTI based at least in part on receiving the first DCI; means for receiving (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) second DCI that schedules a second portion of the data communication in a second TTI on the first frequency band, wherein the second DCI indicates that the second portion is part of the data communication; means for receiving or transmitting (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, and/or the like) the second portion of the data communication in the second TTI based at least in part on receiving the second DCI; and/or the like. In some aspects, such means may include one or more components of UE <NUM> described in connection with <FIG>, such as receive processor <NUM>, transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like.

In some aspects, base station <NUM> may include means for configuring (e.g., using controller/processor <NUM>, memory <NUM>, and/or the like) a set of TTIs on a first frequency band with an uplink/downlink TDD pattern that is synchronized with a set of overlapping TTIs on a second frequency band, wherein the first frequency band is used for a first category of UEs that are not capable of communicating using a shortened TTI and the second frequency band is used for a second category of UEs that are capable of communicating using the shortened TTI; means for transmitting (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) first DCI that schedules a start of a data communication in a first TTI of the first set of TTIs; means for receiving or transmitting (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) a first portion of the data communication in the first TTI based at least in part on transmitting the first DCI; means for transmitting (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) second DCI that schedules a second portion of the data communication in a second TTI of the first set of TTIs, wherein the second DCI indicates that the second portion is part of the data communication; means for receiving or transmitting (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) the second portion of the data communication in the second TTI based at least in part on transmitting the second DCI; and/or the like. In some aspects, such means may include one or more components of base station <NUM> described in connection with <FIG>, such as transmit processor <NUM>, receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like.

<FIG> is a diagram illustrating an example <NUM> of different transmission time interval lengths for different frequency bands, in accordance with various aspects of the present disclosure.

As described above in connection with <FIG>, in some aspects, a base station <NUM> may serve different UEs <NUM> of different categories, different UEs <NUM> that support different capabilities, and/or the like. For example, the base station <NUM> may serve a first category of UEs (such as UE 120f with reference to <FIG>) that have a less advanced capability (e.g., a lower capability) and a second category of UEs (such as UE <NUM> with reference to <FIG>) that have a more advanced capability (e.g., a higher capability). In this case, UEs of the first category may have a reduced feature set compared to UEs of the second category. For example, UEs of the first category may support a lower maximum modulation and coding scheme (MCS) than UEs of the second category (e.g., quadrature phase shift keying (QPSK) or the like as compared to <NUM>-quadrature amplitude modulation (QAM) or the like), may support a lower transmit power than UEs of the second category, may have a less advanced beamforming capability than UEs of the second category, may be capable of communicating on a narrower maximum bandwidth part than UEs of the second category, and/or the like. In some cases, UEs of the second category may be capable of communicating using a shortened TTI (e.g., a slot length of <NUM> or less, <NUM>, <NUM>, <NUM>, <NUM>, and/or the like, depending on a sub-carrier spacing), and UEs of the first category may not be capable of communicating using the shortened TTI.

To serve different UEs <NUM> of different categories and/or having different capabilities, a base station <NUM> may multiplex communications of the different UEs <NUM> in shared spectrum. In some cases, the base station <NUM> may use time division multiplexing (TDM), such as by allocating the entire spectrum to UEs of the first category, then to UEs of the second category, then back to UEs of the first category, and so on. However, this use of spectrum may be inefficient depending on the quantity of UEs <NUM> of different categories. Furthermore, some scenarios for NR support ultra-reliable low latency communication (URLLC) and other lower latency scenarios, and using TDM would increase the latency in such scenarios, making it more difficult to satisfy latency requirements (e.g., for UEs of the second category).

As shown in <FIG>, and by reference number <NUM>, the base station <NUM> may use frequency division multiplexing (FDM) to multiplex communications of the different UEs <NUM> in shared spectrum. For example, the base station <NUM> may allocate a first frequency band of the shared spectrum (e.g., a first portion of the shared spectrum) to UEs having a lower capability (e.g., a less advanced capability, such as UEs of the second category), and may allocate a second frequency band of the shared spectrum (e.g., a second portion of the shared spectrum) to UEs having a higher capability (e.g., a more advanced capability, such as UEs of the first category). Although <FIG> shows the first frequency band for UEs having the lower capability as having a higher frequency than the second frequency band for UEs having the higher capability, in some aspects, the first frequency band for UEs having the lower capability has a lower frequency than the second frequency band for UEs having the higher capability. As an example, the first frequency band may range from <NUM> to <NUM>, and the second frequency band may range from <NUM> to <NUM>.

In some aspects, the first frequency band for UEs having the lower capability may occupy less channel bandwidth and/or a lesser portion of a component carrier than the second frequency band for UEs having the higher capability. For example, the first frequency band for UEs having the lower capability may include <NUM>% of the total channel bandwidth, while the second frequency band for UEs having the higher capability may include <NUM>% of the total channel bandwidth. In one example component carrier of <NUM>, this means that the first frequency band occupies, for example, <NUM> and the second frequency band occupies <NUM>, similar to the <NUM> to <NUM> example mentioned above. Other bandwidth partitions are possible, such as <NUM>% versus <NUM>%, <NUM>% versus <NUM>%, and/or the like. In some aspects, the first frequency band and the second frequency band may be in the same frequency range (FR). For example, the first frequency band and the second frequency band may both be in, or both be a designated band within, Frequency Range <NUM> (FR1, including sub-<NUM> bands, some of which can include bands used by previous standards, for example, LTE), Frequency Range (FR2, including frequency bands above <NUM>), or the like.

As shown by reference number <NUM>, UEs having the higher capability may be capable of communicating using a shorter TTI, whereas UEs having the lower capability may not be capable of communicating using a shorter TTI. For example, the minimum TTI length supported by UEs having the higher capability may be shorter than the minimum TTI length supported by UEs having the lower capability. Because a TTI may be configured for transmission of one of uplink data or downlink data, this may result in overlapping (e.g., concurrent) TTIs on different frequency bands having different configurations. For example, as shown by reference number <NUM>, a TTI configured for downlink data (e.g., a downlink TTI) on the first frequency band may overlap with a TTI configured for uplink data (e.g., an uplink TTI) on the second frequency band, or an uplink TTI on the first frequency band may overlap with a downlink TTI on the second frequency band.

However, if the base station <NUM> is limited by a half duplex constraint, meaning that the base station <NUM> cannot concurrently transmit and receive communications, then the base station <NUM> may not be capable of concurrently transmitting a communication on the first frequency band and receiving a communication on the second frequency band, or vice versa. Some techniques and apparatuses described herein permit a base station <NUM>, subject to a half duplex constraint, to use frequency division multiplexing to serve a first category UEs that are not capable of communicating using a shortened TTI and a second category of UEs that are capable of communicating using the shortened TTI. In this way, spectrum that is shared between UEs <NUM> of the different categories may be used efficiently. Furthermore, stricter requirement for UEs of the second category (e.g., URLLC requirements, low latency requirements, and/or the like) may be satisfied.

<FIG> is a diagram illustrating an example <NUM> of multiplexing communications of UEs that support different transmission time interval lengths, in accordance with various aspects of the present disclosure.

As shown in <FIG>, shared frequency spectrum may be frequency division multiplexed for a first category of UEs that are not capable of communicating using a shortened TTI and a second category of UEs that are capable of communicating using the shortened TTI, as described above in connection with <FIG>. For example, a first portion of the shared spectrum (e.g., a first frequency band) may be used for communications with the first category of UEs, and a second portion of the shared spectrum (e.g., a second frequency band) may be used for communications with the second category of UEs. In some aspects, the first category of UEs may have a reduced feature set compared to the second category of UEs.

As shown by reference number <NUM>, a base station <NUM> may determine an uplink/downlink (UL/DL) time division duplexing (TDD) pattern configured for the second frequency band. An UL/DL TDD pattern may refer to a configuration of a set of TTIs for uplink data and downlink data, where a first subset of the set of TTIs may be configured for uplink data and a second subset of the set of TTIs may be configured for downlink data. In <FIG>, the example UL/DL TDD pattern for the second frequency band shows a first TTI configured for downlink data, a second TTI configured for uplink data, a third TTI configured for downlink data, and so on, with contiguous TTIs alternating between uplink data and downlink data. This UL/DL TDD pattern is shown as an example, and a different UL/DL TDD pattern may be used.

In some aspects, the UL/DL TDD pattern for the second frequency band may be fixed (e.g., semi-statically configured, such as in a radio resource control (RRC) configuration message). In this case, the base station <NUM> may determine the fixed UL/DL TDD pattern (e.g., based at least in part on an UL/DL TDD pattern indicated in an RRC message). Alternatively, the UL/DL TDD pattern for the second frequency band may be dynamically determined over time, such as based at least in part on a traffic load. In this case, the base station <NUM> may dynamically determine the UL/DL TDD pattern over time, as the UL/DL TDD pattern is configured. In some aspects, a semi-statically configured UL/DL TDD pattern (e.g., configured in an RRC message) may be dynamically overridden (e.g., via one or more downlink control information (DCI) messages).

As shown by reference number <NUM>, the base station <NUM> may synchronize an UL/DL TDD pattern for the first frequency band (e.g., a first UL/DL TDD pattern) with the UL/DL TDD pattern determined for the second frequency band (e.g., a second UL/DL TDD pattern). For example, the base station <NUM> may synchronize the UL/DL TDD patterns by configuring a set of TTIs on the first frequency band with an UL/DL TDD pattern that is synchronized with a set of overlapping TTIs on a second frequency band. Thus, the base station <NUM> may configure a TTI on the first frequency band for downlink data if a corresponding TTI on the second frequency band is configured for downlink data. Similarly, the base station <NUM> may configure a TTI on the first frequency band for uplink data if a corresponding TTI on the second frequency band is configured for uplink data. The corresponding TTI on the second frequency band may overlap with the TTI on the first frequency band, which may include a full overlap when the TTIs are time-aligned.

As shown by reference number <NUM>, the base station <NUM> may schedule portions of a data communication (e.g., an uplink communication or a downlink communication) in non-contiguous TTIs on the first frequency band. For example, because TTIs on the first frequency band may be configured with a shorter TTI length than that supported by the first category of UEs, the base station <NUM> may configure a data communication on the first frequency band to be divided into multiple portions that are transmitted over multiple TTIs. In this way, a lower capability UE may be capable of transmitting or receiving data communications using a TTI length that is shorter than a minimum TTI length supported by the lower capability UE, and the base station <NUM> may be capable of frequency division multiplexing communications of UEs having the lower capability and UEs having a higher capability (e.g., that supports a shorter TTI length).

<FIG> is a diagram illustrating another example <NUM> of multiplexing communications of UEs that support different transmission time interval lengths, in accordance with various aspects of the present disclosure.

As shown in <FIG>, a base station <NUM> and a UE <NUM> (e.g., UE 120f having a lower capability, as shown in <FIG>) may communicate with one another. The base station <NUM> may serve a first category of UEs that are not capable of communicating using a shortened TTI and may serve a second category of UEs that are capable of communicating using the shortened TTI. As described above, a first frequency band may be used to communicate with UEs of the first category, and a second frequency band may be used to communicate with UEs of the second category. The UE 120f shown in <FIG> may be a UE of the first category, and may communicate with the base station <NUM> using the first frequency band. Thus, the UE 120f may have a reduced feature set as compared to UEs (e.g., UEs <NUM> as per <FIG>) that communicate with the base station <NUM> using the second frequency band. Although the UE 120f is shown as a smartphone, in some aspects, the UE 120f may be an MTC UE, and eMTC UE, an IoT UE, and/or the like, as described above in connection with <FIG>.

As shown by reference number <NUM>, the base station <NUM> may configure a set of TTIs on the first frequency band with an UL/DL TDD pattern that is synchronized with a set of overlapping TTIs on a second frequency band, as described above in connection with <FIG>. For example, the base station <NUM> may configure a TTI on the first frequency band for downlink data if a corresponding TTI (e.g., that overlaps with the TTI) on the second frequency band is configured for downlink data, or may configure the TTI for uplink data if the corresponding TTI is configured for uplink data.

In some aspects, the base station <NUM> may indicate the UL/DL TDD pattern for the first frequency band to the UE 120f. For example, the base station <NUM> may transmit a configuration message (e.g., a radio resource control (RRC) message and/or the like) that indicates the UL/DL TDD pattern for the first frequency band. The base station <NUM> may indicate the UL/DL TDD pattern for the first frequency band in the configuration message when, for example, the UL/DL TDD pattern for the second frequency band is fixed and/or is semi-statically configured (e.g., in the RRC message).

Additionally, or alternatively, the base station <NUM> may indicate the UL/DL TDD pattern for the first frequency band (or a part of the UL/DL TDD pattern) in DCI. For example, the DCI may indicate whether a TTI, corresponding to the DCI (e.g., a TTI for which a data communication is scheduled by the DCI), is configured for uplink data or downlink data. The base station <NUM> may indicate the UL/DL TDD pattern for the first frequency band (e.g., for one or more TTIs) in DCI when, for example, the UL/DL TDD pattern for the second frequency band is dynamically configured (e.g., in DCI). In some aspects, the base station <NUM> may use both a configuration message and DCI to indicate the UL/DL TDD pattern, such as by indicating a semi-static UL/DL TDD pattern using the configuration message and by overriding parts of the UL/DL TDD pattern (e.g., an UL/DL configuration for one or more TTIs) using DCI.

As shown by reference number <NUM>, the base station <NUM> may transmit, and the UE 120f may receive, downlink control information (DCI) (shown as DCI <NUM>) that schedules a start of a data communication in a TTI of the configured set of TTIs (e.g., on the first frequency band), shown as TTI <NUM>. In <FIG>, this data communication is shown as packet <NUM>, and is a downlink data communication. In example <NUM>, DCI <NUM> schedules the start of packet <NUM> to occur in a same TTI in which DCI <NUM> is transmitted (shown as TTI <NUM>), such as by indicating a timing value of zero in DCI <NUM>. The timing value may be a physical downlink control channel (PDCCH) to physical downlink shared channel (PDSCH) timing value (e.g., a k0 value) for a downlink data communication, or may be a PDCCH to physical uplink shared channel (PUSCH) timing value (e.g., a k2 value) for an uplink data communication. This timing value is shown as an example, and other timing values may be used. Thus, the DCI and the data communication may occur in different TTIs.

As shown by reference number <NUM>, the base station <NUM> may transmit, and the UE 120f may receive, a first portion of the downlink data communication (packet <NUM>) in TTI <NUM>, as scheduled by DCI <NUM>. In <FIG>, the first portion of packet <NUM> is shown as Data <NUM>, to indicate a first portion of a first packet in TTI <NUM>. In some aspects, the UE 120f may store the first portion in a buffer until all portions of the first packet are received.

As shown by reference number <NUM>, the base station <NUM> may transmit, and the UE 120f may receive, DCI <NUM> that schedules a start of a data communication in another TTI of the configured set of TTIs (e.g., on the first frequency band), shown as TTI <NUM>. In <FIG>, this data communication is shown as packet <NUM>, and is an uplink data communication. In example <NUM>, DCI <NUM> schedules the start of packet <NUM> to occur in a same TTI in which DCI <NUM> is transmitted (shown as TTI <NUM>), such as by indicating a timing value of zero in DCI <NUM>. As described above, other timing values may be used, and the DCI and the data communication may occur in different TTIs.

As shown by reference number <NUM>, the UE 120f may transmit, and the base station <NUM> may receive, a first portion of the uplink data communication (packet <NUM>) in TTI <NUM>, as scheduled by DCI <NUM>. In <FIG>, the first portion of packet <NUM> is shown as Data <NUM>, to indicate a first portion of a second packet in TTI <NUM>. In some aspects, the base station <NUM> may store the first portion in a buffer until all portions of the second packet are received.

As shown by reference number <NUM>, the base station <NUM> may transmit, and the UE 120f may receive, DCI <NUM> that schedules a second portion (e.g., a continuation) of the downlink data communication in a TTI of the configured set of TTIs (e.g., on the first frequency band), shown as TTI <NUM>. In example <NUM>, DCI <NUM> schedules the second portion of packet <NUM> to occur in a same TTI in which DCI <NUM> is transmitted (shown as TTI <NUM>), but a different PDCCH-to-PDSCH timing may be used. As shown, DCI <NUM> may indicate that the communication scheduled by DCI <NUM> is a continuation of a previous downlink data communication. For example, DCI <NUM> may indicate that the second portion, scheduled by DCI <NUM>, is part of the downlink data communication scheduled by DCI <NUM>. In some aspects, this indication may be a single bit that indicates whether a communication scheduled by DCI <NUM> is part of a prior data communication. In this case, a first value of the bit (e.g., <NUM>) may indicate that the communication scheduled by DCI <NUM> is part of a prior data communication (e.g., in this case, packet <NUM>, which is a prior downlink data communication), and a second value of the bit (e.g., <NUM>) may indicate that the communication scheduled by DCI <NUM> is not part of a prior data communication (e.g., is a start of a new downlink data communication).

In some aspects, DCI (e.g., a first DCI) that schedules a start (e.g., a first portion) of a data communication (e.g., DCI <NUM> of <FIG>) may have a first DCI format, and DCI (e.g., a subsequent DCI, a second DCI, a third DCI, and/or the like) that schedules a continuation (e.g., a second portion, a third portion, and so on) of the data communication (e.g., DCI <NUM> of <FIG>) may have a second, different DCI format. For example, DCI having the first DCI format may indicate that the first TTI is for either uplink data or downlink data, a UE identifier of the UE 120f, a modulation and coding scheme (MCS) for the data communication, a resource allocation for the data communication, and/or the like. In some aspects, DCI having the second DCI format may exclude an MCS and/or a resource allocation. Additionally, or alternatively, DCI having the second DCI format may indicate that a communication scheduled by such DCI is a continuation of a previous data communication, may indicate whether a communication scheduled by such DCI is the last portion of a data communication, and/or the like (and such information may not be included in DCI having the first DCI format).

In some aspects, DCI that schedules a continuation of a data communication may indicate whether a TTI, in which the continuation is scheduled, is configured for uplink data or downlink data in conformity with the first DCI. This may enable the UE 120f to determine that the second DCI schedules the second portion of the data communication. In this way, the UE 120f may transmit or receive data appropriately. For example, if the DCI indicates that the TTI is configured for uplink data, then the UE 120f may continue a data communication by transmitting a portion of an uplink data communication. Similarly, if the DCI indicates that the TTI is configured for downlink data, then the UE 120f may continue a data communication by receiving a portion of a downlink data communication. Additionally, or alternatively, the UE 120f may refrain from monitoring a TTI based at least in part on whether the TTI is configured for uplink data or downlink data, which may be determined based at least in part on the indication in DCI. For example, if any given DCI indicates that a corresponding TTI is configured for uplink data and the UE 120f is not in the process of transmitting uplink data (e.g., does not have data stored in a buffer for uplink transmission), then the UE 120f may refrain from monitoring (e.g., may skip) the TTI. Similarly, if any given DCI indicates that a corresponding TTI is configured for downlink data and the UE 120f is not in the process of receiving downlink data (e.g., has not received any portions of a downlink data communication), then the UE 120f may refrain from monitoring (e.g., may skip) the TTI.

As shown by reference number <NUM>, the base station <NUM> may transmit, and the UE 120f may receive, the second portion of the downlink data communication (packet <NUM>) in TTI <NUM>, as scheduled by DCI <NUM>. Thus, different portions of a data communication (e.g., an uplink data communication or a downlink data communication) may be scheduled in non-contiguous TTIs (e.g., TTI <NUM> and TTI <NUM>). In <FIG>, the second portion of packet <NUM> is shown as Data <NUM>, to indicate a second portion of a first packet in TTI <NUM>. In some aspects, the UE 120f may store the second portion in a buffer until all portions of the first packet are received.

As shown by reference number <NUM>, the base station <NUM> may transmit, and the UE 120f may receive, DCI <NUM> that schedules a second portion (e.g., a continuation) of the uplink data communication in a TTI of the configured set of TTIs (e.g., on the first frequency band), shown as TTI <NUM>. In example <NUM>, DCI <NUM> schedules the second portion of packet <NUM> to occur in a same TTI in which DCI <NUM> is transmitted (shown as TTI <NUM>), but a different PDCCH-to-PUSCH timing may be used. As shown, DCI <NUM> may indicate that the communication scheduled by DCI <NUM> is a continuation of a previous uplink data communication. For example, DCI <NUM> may indicate that the second portion, scheduled by DCI <NUM>, is part of the uplink data communication scheduled by DCI <NUM>. In some aspects, this indication may be a single bit that indicates whether a communication scheduled by DCI <NUM> is part of a prior data communication. In this case, a first value of the bit (e.g., <NUM>) may indicate that the communication scheduled by DCI <NUM> is part of a prior data communication (e.g., in this case, packet <NUM>, which is a prior uplink data communication), and a second value of the bit (e.g., <NUM>) may indicate that the communication scheduled by DCI <NUM> is not part of a prior data communication (e.g., is a start of a new uplink data communication).

In some aspects, DCI that schedules a continuation of a data communication may indicate whether a TTI, in which the continuation is scheduled, includes a last portion of the data communication (e.g., may indicate whether a portion of the data communication, scheduled by the DCI, is a last portion of the data communication). In this way, the UE 120f or the base station <NUM> may combine received communications for decoding, demodulation, and/or the like. For example, if the DCI indicates that a scheduled portion is the last portion of a downlink data communication, then the UE 120f may decode and/or demodulate the downlink data communication upon reception of the scheduled portion (e.g., by combining that portion with other portions received by the UE 120f). Similarly, if the DCI indicates that a scheduled portion is the last portion of an uplink data communication, then the base station <NUM> may decode and/or demodulate the uplink data communication upon reception of the scheduled portion (e.g., by combining that portion with other portions received by the base station <NUM>).

According to the invention, DCI that schedules a start of a data communication (e.g., a first portion of the data communication) indicates a number of TTIs that include corresponding portions of the data communication. The DCI includes an MCS that indicates the number of TTIs. In some aspects, the MCS may indicate a block size (e.g., a transport block (TB) size that indicates the number of TTIs. DCI that schedules a continuation of the data communication excludes an indication of whether a portion scheduled by that DCI is a last portion because the UE 120f would be able to determine that the portion is the last portion based at least in part on the indicated number of TTIs. In an example, the MCS may not indicate the block size and/or the number of TTIs. In this case, DCI that schedules a continuation of the data communication may include an indication of whether a portion scheduled by that DCI is a last portion so that the UE 120f can determine whether the portion is the last portion.

As shown by reference number <NUM>, the UE 120f may transmit, and the base station <NUM> may receive, the second portion of the uplink data communication (packet <NUM>) in TTI <NUM>, as scheduled by DCI <NUM>. Thus, different portions of a data communication (e.g., an uplink data communication or a downlink data communication) may be scheduled in non-contiguous TTIs (e.g., TTI <NUM> and TTI <NUM>). In <FIG>, the second portion of packet <NUM> is shown as Data <NUM>, to indicate a second portion of a second packet in TTI <NUM>. In some aspects, the base station <NUM> may store the second portion in a buffer until all portions of the second packet are received. In example <NUM>, the second portion of the uplink data communication is the last portion, which may be indicated by DCI <NUM> (e.g., using an MCS that indicates that the uplink data communication spans two TTIs) and/or by DCI <NUM> (e.g., using a bit that indicates that the second portion is the last portion). Thus, upon receiving the second portion, the base station <NUM> may process the uplink data communication.

As shown by reference number <NUM>, the base station <NUM> may transmit, and the UE 120f may receive, DCI <NUM> that schedules a third portion (e.g., a continuation) of the downlink data communication in a TTI of the configured set of TTIs (e.g., on the first frequency band), shown as TTI <NUM>. In example <NUM>, DCI <NUM> schedules the third portion of packet <NUM> to occur in a same TTI in which DCI <NUM> is transmitted (shown as TTI <NUM>), but a different PDCCH-to-PDSCH timing may be used. As shown, DCI <NUM> may indicate that the communication scheduled by DCI <NUM> is a continuation of a previous downlink data communication. For example, DCI <NUM> may indicate that the third portion, scheduled by DCI <NUM>, is part of the downlink data communication scheduled by DCI <NUM> (and DCI <NUM>), in a similar manner as described above. In some aspects, DCI <NUM> and/or DCI <NUM> may indicate that the third portion is the last portion of the downlink data communication, as described above.

In some aspects, the UE 120f may monitor for DCI in a TTI on the first frequency band based at least in part on a determination that a previously-received portion of a data communication is not the last portion of the data communication. For example, as described above, the base station <NUM> may indicate whether a scheduled portion of a data communication is a last portion of the data communication. When a portion scheduled by a TTI is not the last portion, the UE 120f may continue to monitor for DCI on subsequent TTIs until the last portion is scheduled and/or received. In example <NUM>, the UE 120f may determine that the second portion of packet <NUM> is not the last portion (e.g., due to an indication in DCI <NUM> and/or DCI <NUM>). In this case, the UE 120f may monitor for DCI in TTI <NUM>.

As shown by reference number <NUM>, the base station <NUM> may transmit, and the UE 120f may receive, the third portion of the downlink data communication (packet <NUM>) in TTI <NUM>, as scheduled by DCI <NUM>. In <FIG>, the third portion of packet <NUM> is shown as Data <NUM>, to indicate a third portion of a first packet in TTI <NUM>. In some aspects, the UE 120f may store the second portion in a buffer until all portions of the first packet are received. In example <NUM>, the third portion of the downlink data communication is the last portion, which may be indicated by DCI <NUM> (e.g., using an MCS that indicates that the downlink data communication spans three TTIs) and/or by DCI <NUM> (e.g., using a bit that indicates that the third portion is the last portion). Thus, upon receiving the third portion, the UE 120f may process the uplink data communication.

<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 a UE (e.g., UE <NUM>, UE 120f, and/or the like) performs operations associated with multiplexing communications of UEs that support different TTI lengths.

As shown in <FIG>, in some aspects, process <NUM> may include receiving first downlink control information (DCI) that schedules a start of a data communication in a first transmission time interval (TTI) on a first frequency band, wherein the first frequency band is configured with an uplink/downlink time division duplexing (TDD) pattern that is synchronized with a second frequency band (block <NUM>). For example, the UE (e.g., using receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may receive first DCI that schedules a start of a data communication in a first TTI on a first frequency band, as described above in connection with <FIG> and <FIG>. In some aspects, the first frequency band is configured with an UL/DL TDD pattern that is synchronized with a second frequency band.

As further shown in <FIG>, in some aspects, process <NUM> may include receiving or transmitting a first portion of the data communication in the first TTI based at least in part on receiving the first DCI (block <NUM>). For example, the UE (e.g., using receive processor <NUM>, transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may receive or transmit a first portion of the data communication in the first TTI based at least in part on receiving the first DCI, as described above in connection with <FIG> and <FIG>.

As further shown in <FIG>, in some aspects, process <NUM> may include receiving second DCI that schedules a second portion of the data communication in a second TTI on the first frequency band, wherein the second DCI indicates that the second portion is part of the data communication (block <NUM>). For example, the UE (e.g., using receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may receive second DCI that schedules a second portion of the data communication in a second TTI on the first frequency band, as described above in connection with <FIG> and <FIG>. In some aspects, the second DCI indicates that the second portion is part of the data communication.

As further shown in <FIG>, in some aspects, process <NUM> may include receiving or transmitting the second portion of the data communication in the second TTI based at least in part on receiving the second DCI (block <NUM>). For example, the UE (e.g., using receive processor <NUM>, transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may receive or transmit the second portion of the data communication in the second TTI based at least in part on receiving the second DCI, as described above in connection with <FIG> and <FIG>.

In a first aspect, the second DCI further indicates whether the second portion is a last portion of the data communication.

In a second aspect, alone or in combination with the first aspect, the second DCI has a different format than the first DCI.

In a third aspect, alone or in combination with one or more of the first and second aspects, the first DCI includes an indication of one of uplink data or downlink data, a UE identifier of the UE, an MCS for the data communication, and a resource allocation for the data communication, and wherein the second DCI indicates the one of uplink data or downlink data in conformity with the first DCI to enable the UE to determine that the second DCI schedules the second portion of the data communication.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the MCS indicates a number of TTIs that include corresponding portions of the data communication and the second DCI excludes an indication of whether the second portion is a last portion of the data communication.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the MCS does not indicate a number of TTIs that include corresponding portions of the data communication and the second DCI includes an indication of whether the second portion is a last portion of the data communication.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the first TTI and the second TTI are non-contiguous.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the first frequency band is used for a first category of UEs that are not capable of communicating using a shortened TTI, and the second frequency band is used for a second category of UEs that are capable of communicating using the shortened TTI.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the UE has a reduced feature set compared to UEs that communicate using the second frequency band.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the data communication is a downlink data communication, receiving or transmitting the first portion comprises receiving the first portion, and receiving or transmitting the second portion comprises receiving the second portion.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the data communication is an uplink data communication, receiving or transmitting the first portion comprises transmitting the first portion, and receiving or transmitting the second portion comprises transmitting the second portion.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process <NUM> includes monitoring for third DCI on the first frequency band based at least in part on a determination that the second portion is not a last portion of the data communication.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the uplink/downlink TDD pattern is indicated in a configuration message received by the UE.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the first DCI indicates whether the first TTI is configured for uplink data or downlink data, and the second DCI indicates whether the second TTI is configured for uplink data or downlink data in conformity with the first DCI.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the data communication is for one of uplink data or downlink data, and the UE is configured to refrain from monitoring a TTI configured for the other of uplink data or downlink data.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a base station, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a base station (e.g., base station <NUM> and/or the like) performs operations associated with multiplexing communications of UEs that support different TTI lengths.

As shown in <FIG>, in some aspects, process <NUM> may include configuring a set of transmission time intervals (TTIs) on a first frequency band with an uplink/downlink time division duplexing (TDD) pattern that is synchronized with a set of overlapping TTIs on a second frequency band, wherein the first frequency band is used for a first category of user equipment (UEs) that are not capable of communicating using a shortened TTI and the second frequency band is used for a second category of UEs that are capable of communicating using the shortened TTI (block <NUM>). For example, the base station (e.g., using transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may configure a set of TTIs on a first frequency band with an UL/DL TDD pattern that is synchronized with a set of overlapping TTIs on a second frequency band, as described above in connection with <FIG> and <FIG>. In some aspects, the first frequency band is used for a first category of UEs that are not capable of communicating using a shortened TTI and the second frequency band is used for a second category of UEs that are capable of communicating using the shortened TTI.

As further shown in <FIG>, in some aspects, process <NUM> may include transmitting first downlink control information (DCI) that schedules a start of a data communication in a first TTI of the first set of TTIs (block <NUM>). For example, the base station (e.g., using transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may transmit first DCI that schedules a start of a data communication in a first TTI of the first set of TTIs, as described above in connection with <FIG> and <FIG>.

As further shown in <FIG>, in some aspects, process <NUM> may include receiving or transmitting a first portion of the data communication in the first TTI based at least in part on transmitting the first DCI (block <NUM>). For example, the base station (e.g., using transmit processor <NUM>, receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may receive or transmit a first portion of the data communication in the first TTI based at least in part on transmitting the first DCI, as described above in connection with <FIG> and <FIG>.

As further shown in <FIG>, in some aspects, process <NUM> may include transmitting second DCI that schedules a second portion of the data communication in a second TTI of the first set of TTIs, wherein the second DCI indicates that the second portion is part of the data communication (block <NUM>). For example, the base station (e.g., using transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may transmit second DCI that schedules a second portion of the data communication in a second TTI of the first set of TTIs, as described above in connection with <FIG> and <FIG>. In some aspects, the second DCI indicates that the second portion is part of the data communication.

As further shown in <FIG>, in some aspects, process <NUM> may include receiving or transmitting the second portion of the data communication in the second TTI based at least in part on transmitting the second DCI (block <NUM>). For example, the base station (e.g., using transmit processor <NUM>, receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may receive or transmit the second portion of the data communication in the second TTI based at least in part on transmitting the second DCI, as described above in connection with <FIG> and <FIG>.

In a first aspect, the first TTI is configured for downlink data if a corresponding TTI, in the set of overlapping TTIs, that overlaps with the first TTI is configured for downlink data, or the first TTI is configured for uplink data if the corresponding TTI is configured for uplink data.

In a second aspect, alone or in combination with the first aspect, the second DCI further indicates whether the second portion is a last portion of the data communication.

In a third aspect, alone or in combination with one or more of the first and second aspects, the second DCI has a different format than the first DCI.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the first DCI includes an indication of one of uplink data or downlink data, a UE identifier of the UE, an MCS for the data communication, and a resource allocation for the data communication, and wherein the second DCI indicates the one of uplink data or downlink data in conformity with the first DCI to enable the UE to determine that the second DCI schedules the second portion of the data communication.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the MCS indicates a number of slots that include portions of the data communication and the second DCI excludes an indication of whether the second portion is a last portion of the data communication.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the MCS does not indicate a number of slots that include portions of the data communication and the second DCI includes an indication of whether the second portion is a last portion of the data communication.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the first TTI and the second TTI are non-contiguous.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the data communication is a downlink data communication, receiving or transmitting the first portion comprises transmitting the first portion, and receiving or transmitting the second portion comprises transmitting the second portion.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the data communication is an uplink data communication, receiving or transmitting the first portion comprises receiving the first portion, and receiving or transmitting the second portion comprises receiving the second portion.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process <NUM> includes transmitting a configuration message that indicates the uplink/downlink TDD pattern.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the first DCI indicates whether the first TTI is configured for uplink data or downlink data, and the second DCI indicates whether the second TTI is configured for uplink data or downlink data in conformity with the first DCI.

Claim 1:
A method (<NUM>) of wireless communication performed by a user equipment, UE, comprising:
receiving (<NUM>) first downlink control information, DCI, that schedules a start of a data communication in a first transmission time interval, TTI, on a first frequency band, wherein the first frequency band is configured with an uplink/downlink time division duplexing, TDD, pattern that is synchronized with a second frequency band,
wherein the first DCI includes an indication of one of uplink data or downlink data, a UE identifier of the UE, a modulation and coding scheme, MCS, for the data communication, and a resource allocation for the data communication;
receiving (<NUM>) or transmitting a first portion of the data communication in the first TTI based at least in part on receiving the first DCI;
receiving (<NUM>) second DCI that schedules a second portion of the data communication in a second TTI on the first frequency band, wherein the second DCI indicates that the second portion is part of the data communication, and
wherein the second DCI further indicates the one of uplink data or downlink data in conformity with the first DCI to enable the UE to determine that the second DCI schedules the second portion of the data communication, and
wherein the MCS indicates a number of TTIs that include corresponding portions of the data communication and the second DCI excludes an indication of whether the second portion is a last portion of the data communication; and
receiving (<NUM>) or transmitting the second portion of the data communication in the second TTI based at least in part on receiving the second DCI.