Time domain resource allocation for downlink data repetition

Abstract

Methods, systems, and apparatus for wireless communications are described. In some systems, a base station may use a downlink control information (DCI) message to indicate to a user equipment (UE) timing resources for multiple downlink data repetitions in a time slot. In a first implementation, the base station may indicate an explicit time domain resource allocation (TDRA) for one repetition in the TDRA field of the DCI, and the UE may determine implicit TDRAs for other repetitions based on the explicit TDRA. In a second implementation, the base station may indicate a total TDRA for a complete set of repetitions in the TDRA field, and the UE may divide the total TDRA into individual TDRAs for the repetitions. The UE may receive downlink data repetitions based on determining the TDRA, and may respond by transmitting a feedback message based on a hybrid automatic repeat request acknowledgment (HARQ‑ACK) codebook.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. Provisional Patent Application No. 62 / 888,317, filed by KHOSHNEVISAN et al. on August 16, 2019, entitled “TIME DOMAIN RESOURCE ALLOCATION FOR DOWNLINK DATA REPETITIONS,” and U.S. Patent Application No. 16 / 993,082, filed by KHOSHNEVISAN et al. on August 13, 2020, entitled “TIME DOMAIN RESOURCE ALLOCATION FOR DOWNLINK DATA REPETITIONS,” each of which is assigned to the assignee of this application. Technical Field

[0003] The following relates generally to wireless communications and, more particularly, to time domain resource allocation (TDRA) for downlink data repetition.

[0004] background

[0005] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems), and fifth generation (5G) systems that may be referred to as new radio (NR) systems. These systems may use various 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 orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include several base stations or network access nodes, each of which simultaneously supports the communication of multiple communication devices, which may be referred to as user equipment (UE).

[0006] In some wireless communication systems, a base station may schedule multiple downlink data repetitions to a UE in a single time slot. However, indicating each data repetition in a separate downlink control information (DCI) message may significantly increase the signaling overhead on the downlink control channel. In addition, indicating the resources used for each data repetition in a single DCI message may significantly increase the DCI payload. Additionally or alternatively, the UE may provide feedback to the base station based on whether the UE successfully receives the downlink data repetition. However, providing feedback for each downlink data repetition may result in additional complexity at the UE and the base station.

[0007] Overview

[0008] The described technology relates to improved methods, systems, devices and apparatuses for supporting time domain resource allocation (TDRA) for downlink data repetition. In general, the described technology provides for scheduling multiple downlink data repetitions in a time slot using a single downlink control information (DCI) message. For example, a base station may schedule a downlink data repetition set, and may transmit a DCI message including a TDRA field to a user equipment (UE) to indicate the TDRA for the downlink data repetition. In a first implementation, the base station may indicate an explicit TDRA for one repetition in a downlink data repetition set in a TDRA field of the DCI, and the UE may determine an implicit TDRA for other repetitions based on the explicit TDRA. In a second implementation, the base station may indicate a total TDRA for a complete repetition set in a TDRA field of the DCI, and the UE may divide the total TDRA into a corresponding TDRA for each repetition in the repetition set. The base station may transmit downlink data repetitions according to the schedule, and the UE may receive these repetitions based on determining the TDRA from a single DCI message. Based on whether the UE successfully receives the data, the UE may transmit a feedback message using a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook. In a first implementation, the UE may transmit a positive or negative acknowledgement (ACK / NACK) for a downlink data opportunity corresponding to an explicit TDRA, while in a second implementation, the UE may transmit an ACK / NACK for a downlink data opportunity corresponding to a total TDRA. In some cases, the UE may use a dummy negative acknowledgement (NACK) for other downlink data opportunities that do not correspond to the TDRA indicated by the DCI message.

[0009] A method for wireless communication at a UE is described. The method may include: receiving a DCI message from a base station indicating an explicit TDRA for a first repetition of a downlink data transmission; determining one or more implicit TDRAs for one or more additional repetitions of the downlink data transmission based on the explicit TDRA; receiving the first repetition of the downlink data transmission and one or more additional repetitions of the downlink data transmission from the base station according to the explicit TDRA and the one or more implicit TDRAs; and transmitting a feedback message to the base station based on the reception and a HARQ-ACK codebook.

[0010] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: receive a DCI message indicating an explicit TDRA for a first repetition of downlink data transmission from a base station; determine one or more implicit TDRAs for one or more additional repetitions of the downlink data transmission based on the explicit TDRA; receive the first repetition of the downlink data transmission and one or more additional repetitions of the downlink data transmission from the base station according to the explicit TDRA and the one or more implicit TDRAs; and transmit a feedback message to the base station based on the reception and a HARQ-ACK codebook.

[0011] Another apparatus for wireless communication at a UE is described. The apparatus may include means for: receiving a DCI message from a base station indicating an explicit TDRA for a first repetition of a downlink data transmission; determining one or more implicit TDRAs for one or more additional repetitions of the downlink data transmission based on the explicit TDRA; receiving the first repetition of the downlink data transmission and one or more additional repetitions of the downlink data transmission from the base station based on the explicit TDRA and the one or more implicit TDRAs; and transmitting a feedback message to the base station based on the reception and a HARQ-ACK codebook.

[0012] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor for the following actions: receiving a DCI message indicating an explicit TDRA for a first repetition of a downlink data transmission from a base station; determining one or more implicit TDRAs for one or more additional repetitions of the downlink data transmission based on the explicit TDRA; receiving the first repetition of the downlink data transmission and one or more additional repetitions of the downlink data transmission from the base station according to the explicit TDRA and the one or more implicit TDRAs; and transmitting a feedback message to the base station based on the reception and a HARQ-ACK codebook.

[0013] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for the following actions: generating the HARQ-ACK codebook based on the explicit TDRA and the receiving.

[0014] In some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein, generating a HARQ-ACK codebook may include operations, features, means, or instructions for the following actions: for a first downlink data opportunity of the HARQ-ACK codebook, inserting an ACK / NACK indication for the downlink data transmission based on an explicit TDRA and the reception.

[0015] In some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein, generating a HARQ-ACK codebook may further include operations, features, apparatus, or instructions for the following actions: for one or more additional downlink data opportunities of the HARQ-ACK codebook, inserting one or more dummy NACK indications for the downlink data transmission based on the absence of an explicit TDRA corresponding to the one or more additional downlink data opportunities.

[0016] In some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein, the feedback message may be transmitted in a first time slot for feedback, and generating the HARQ-ACK codebook may further include operations, features, apparatus, or instructions for the following actions: for one or more additional downlink data opportunities of the HARQ-ACK codebook, insert one or more dummy NACK indications for the downlink data transmission in a second time slot for feedback that is different from the first time slot for feedback based on an additional explicit TDRA indication corresponding to at least one of the one or more additional downlink data opportunities.

[0017] In some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein, the size of the HARQ-ACK codebook may be based on a TDRA candidate set, wherein an explicit TDRA corresponds to a candidate in the TDRA candidate set, and the downlink data opportunity of the HARQ-ACK codebook may be based on the TDRA candidate set.

[0018] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for suppressing inclusion of a TDRA candidate in the TDRA candidate set when a symbol of the TDRA candidate is configured for an uplink, all symbols of the TDRA candidate are configured for an uplink, at most one consecutive symbol of the TDRA candidate is configured for a downlink, or a combination thereof.

[0019] In some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein, the number of repetitions for the downlink data transmission may be semi-statically configured, and some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: determining the TDRA candidate set based on the number of repetitions to cover both explicit TDRA candidates and corresponding implicit TDRA candidates.

[0020] In some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein, the HARQ-ACK codebook includes a semi-static codebook, a type 1 codebook, or a combination thereof.

[0021] Some examples of the methods, devices (apparatus) and non-transient computer-readable media described herein may further include operations, features, devices or instructions for the following actions: identifying a repetition number for the downlink data transmission, wherein determining one or more implicit TDRAs may be based on the repetition number. In some examples of the methods, devices (apparatus) and non-transient computer-readable media described herein, the repetition number may be identified based on a DCI message, a radio resource control (RRC) configuration, or a combination thereof.

[0022] In some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein, the repetition number may include a nominal repetition number, and some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: determining an actual repetition number based on the nominal repetition number and a time slot boundary, an uplink / downlink switching point, or a combination thereof, wherein determining one or more implicit TDRAs may be based on the actual repetition number.

[0023] In some examples of the methods, devices (devices) and non-transient computer-readable media described herein, no code element in the explicit TDRA can be configured for uplink. In some examples of the methods, devices (devices) and non-transient computer-readable media described herein, explicit TDRA and one or more implicit TDRAs may be within a single time slot. In some other examples of the methods, devices (devices) and non-transient computer-readable media described herein, explicit TDRA and one or more implicit TDRAs may span a time slot set, and a feedback timing indicator corresponds to the last time slot in time in the time slot set, wherein the feedback message may be transmitted based on the feedback timing indicator.

[0024] In some examples of the methods, devices (apparatus), and non-transient computer-readable media described herein, an explicit TDRA may span the set of time slots, and the first repetition of the downlink data transmission may include a first nominal repetition. Some examples of the methods, devices (apparatus), and non-transient computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: determining a first actual repetition of the downlink data transmission in a first time slot in the set of time slots based on the first nominal repetition and a second actual repetition of the downlink data transmission in a second time slot in the set of time slots that is located after the first time slot, wherein the second time slot includes the last time slot in the set of time slots.

[0025] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: modifying the TDRA candidate set based on TDRA candidates across time slot boundaries, wherein the HARQ-ACK codebook may be based on the modified TDRA candidate set.

[0026] In some examples of the methods, devices (devices) and non-transient computer-readable media described herein, the first repetition of the downlink data transmission and each of the one or more additional repetitions of the downlink data transmission may have the same length. In some examples of the methods, devices (devices) and non-transient computer-readable media described herein, the explicit TDRA is located before one or more implicit TDRAs in time. In some other examples of the methods, devices (devices) and non-transient computer-readable media described herein, the explicit TDRA is located after one or more implicit TDRAs in time. In some examples of the methods, devices (devices) and non-transient computer-readable media described herein, the explicit TDRA and one or more implicit TDRAs may be coherent in time.

[0027] In some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein, the DCI message may indicate explicit TDRA based on a start symbol, an allocation length, a start and length indicator, a mapping type, a time slot offset, or a combination thereof.

[0028] A method for wireless communication at a UE is described. The method may include: receiving a DCI message indicating a total TDRA for a repetition set of downlink data transmission from a base station; determining a TDRA set of a repetition set for the downlink data transmission based on the total TDRA and the number of repetitions for the downlink data transmission; receiving a repetition set for the downlink data transmission from the base station according to the TDRA set; and transmitting a feedback message to the base station based on the reception and a HARQ-ACK codebook.

[0029] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: receive a DCI message indicating a total TDRA for a repetition set of downlink data transmissions from a base station; determine a TDRA set for a repetition set of the downlink data transmission based on the total TDRA and the number of repetitions for the downlink data transmission; receive a repetition set of the downlink data transmission from the base station according to the TDRA set; and transmit a feedback message to the base station based on the reception and a HARQ-ACK codebook.

[0030] Another apparatus for wireless communication at a UE is described. The apparatus may include means for receiving a DCI message from a base station indicating a total TDRA for a repetition set of downlink data transmissions; determining a TDRA set for a repetition set of the downlink data transmission based on the total TDRA and the number of repetitions for the downlink data transmission; receiving a repetition set for the downlink data transmission from the base station according to the TDRA set; and transmitting a feedback message to the base station based on the reception and a HARQ-ACK codebook.

[0031] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor for the following actions: receiving a DCI message indicating a total TDRA for a repetition set of downlink data transmission from a base station; determining a TDRA set for a repetition set of the downlink data transmission based on the total TDRA and the number of repetitions for the downlink data transmission; receiving a repetition set of the downlink data transmission from the base station according to the TDRA set; and transmitting a feedback message to the base station based on the reception and a HARQ-ACK codebook.

[0032] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the TDRA set may be further determined based on a set of possible sizes of each TDRA in the TDRA set, an equal distribution of the TDRA set in the total TDRA, or a combination thereof.

[0033] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: identifying a repetition number for downlink data transmission based on a DCI message, an RRC configuration, a fixed repetition value, or a combination thereof.

[0034] Some examples of the methods, devices (apparatus), and non-transient computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: determining a TDRA candidate set based on an uplink symbol, wherein the HARQ-ACK codebook may be based on the determined TDRA candidate set. In some examples of the methods, devices (apparatus), and non-transient computer-readable media described herein, determining the TDRA candidate set may include operations, features, devices, or instructions for the following actions: when the symbol of the TDRA candidate is configured for uplink, all the symbols of the TDRA candidate are configured for uplink, at most one consecutive symbol of the TDRA candidate is configured for downlink, or a combination thereof, suppressing the inclusion of the TDRA candidate in the TDRA candidate set.

[0035] In some examples of the methods, devices (devices) and non-transient computer-readable media described herein, no code element in the total TDRA can be configured for uplink. In some examples of the methods, devices (devices) and non-transient computer-readable media described herein, the total TDRA may be within a single time slot. In some other examples of the methods, devices (devices) and non-transient computer-readable media described herein, the total TDRA may span a time slot set, and the feedback timing indicator corresponds to the last time slot in the time slot set, wherein the feedback message may be transmitted based on the feedback timing indicator. In some examples of the methods, devices (devices) and non-transient computer-readable media described herein, the TDRA set may be further determined based on the time slot boundaries of the time slot set.

[0036] In some examples of the methods, devices (apparatus) and non-transient computer-readable media described herein, the first symbol in time in each TDRA in the TDRA set corresponds to a demodulation reference signal (DMRS) symbol. In some examples of the methods, devices (apparatus) and non-transient computer-readable media described herein, the DCI message indicates the total TDRA according to a start symbol, an allocation length, a start and length indicator, a mapping type, a slot offset, or a combination thereof.

[0037] A method for wireless communication at a base station is described. The method may include transmitting a DCI message to a UE indicating an explicit TDRA for a first repetition of downlink data transmission; transmitting the first repetition of the downlink data transmission to the UE according to the explicit TDRA and transmitting one or more additional repetitions of the downlink data transmission to the UE according to one or more implicit TDRAs, wherein the one or more implicit TDRAs are based on the explicit TDRA; and receiving a feedback message based on the explicit TDRA and a HARQ-ACK codebook from the UE.

[0038] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: transmit a DCI message indicating an explicit TDRA for a first repetition of downlink data transmission to a UE; transmit the first repetition of the downlink data transmission to the UE according to the explicit TDRA and transmit one or more additional repetitions of the downlink data transmission to the UE according to one or more implicit TDRAs, wherein the one or more implicit TDRAs are based on the explicit TDRA; and receive a feedback message based on the explicit TDRA and a HARQ-ACK codebook from the UE.

[0039] Another apparatus for wireless communication at a base station is described. The apparatus may include means for transmitting a DCI message to a UE indicating an explicit TDRA for a first repetition of a downlink data transmission; transmitting the first repetition of the downlink data transmission to the UE according to the explicit TDRA and transmitting one or more additional repetitions of the downlink data transmission to the UE according to one or more implicit TDRAs, wherein the one or more implicit TDRAs are based on the explicit TDRA; and receiving a feedback message based on the explicit TDRA and a HARQ-ACK codebook from the UE.

[0040] A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by a processor for the following actions: transmitting a DCI message indicating an explicit TDRA for a first repetition of downlink data transmission to a UE; transmitting the first repetition of the downlink data transmission to the UE according to the explicit TDRA and transmitting one or more additional repetitions of the downlink data transmission to the UE according to one or more implicit TDRAs, wherein the one or more implicit TDRAs are based on the explicit TDRA; and receiving a feedback message based on the explicit TDRA and a HARQ-ACK codebook from the UE.

[0041] In some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein, the HARQ-ACK codebook includes an ACK / NACK indication for the downlink data transmission based on an explicit TDRA and whether the UE successfully received a first repetition of the downlink data transmission.

[0042] Some examples of the methods, devices (apparatus), and non-transient computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: transmitting an indication of the number of repetitions for the downlink data transmission to the UE in a DCI message, an RRC configuration, or a combination thereof, wherein the one or more implicit TDRAs may be further based on the number of repetitions. In some examples of the methods, devices (apparatus), and non-transient computer-readable media described herein, the indication of the number of repetitions may indicate a nominal number of repetitions, and some examples of the methods, devices (apparatus), and non-transient computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: determining an actual number of repetitions based on the nominal number of repetitions and a time slot boundary, an uplink / downlink switching point, or a combination thereof, wherein the one or more implicit TDRAs may be further based on the actual number of repetitions.

[0043] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for scheduling an explicit TDRA such that no symbols in the explicit TDRA are configured for uplink.

[0044] Some examples of the methods, devices (apparatus) and non-transient computer-readable media described herein may further include operations, features, devices or instructions for the following actions: scheduling explicit TDRA and one or more implicit TDRAs so that the explicit TDRA and one or more implicit TDRAs are within a single time slot. Some other examples of the methods, devices (apparatus) and non-transient computer-readable media described herein may further include operations, features, devices or instructions for the following actions: scheduling explicit TDRA and one or more implicit TDRAs so that the explicit TDRA and one or more implicit TDRAs span a time slot set; and transmitting in the DCI message a feedback timing indicator corresponding to the last time slot in the time slot set, wherein the feedback message may be received based on the feedback timing indicator.

[0045] A method for wireless communication at a base station is described. The method may include: transmitting a DCI message indicating a total TDRA of a repetition set for downlink data transmission to a UE; transmitting the repetition set of the downlink data transmission to the UE according to the TDRA set, wherein the total TDRA includes a TDRA set based on the number of repetitions used for the downlink data transmission; and receiving a feedback message based on the total TDRA and a HARQ-ACK codebook from the UE.

[0046] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: transmit a DCI message indicating a total TDRA of a repetition set for downlink data transmission to a UE; transmit a repetition set of the downlink data transmission to the UE according to a TDRA set, wherein the total TDRA includes a TDRA set based on a number of repetitions for the downlink data transmission; and receive a feedback message based on the total TDRA and a HARQ-ACK codebook from the UE.

[0047] Another apparatus for wireless communication at a base station is described. The apparatus may include means for: transmitting a DCI message indicating a total TDRA for a repetition set for downlink data transmission to a UE; transmitting a repetition set for the downlink data transmission to the UE according to the TDRA set, wherein the total TDRA includes a TDRA set based on a number of repetitions for the downlink data transmission; and receiving a feedback message based on the total TDRA and a HARQ-ACK codebook from the UE.

[0048] A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by a processor for the following actions: transmitting a DCI message indicating a total TDRA for a repetition set of downlink data transmission to a UE; transmitting a repetition set of the downlink data transmission to the UE according to a TDRA set, wherein the total TDRA includes a TDRA set based on a number of repetitions for the downlink data transmission; and receiving a feedback message based on the total TDRA and a HARQ-ACK codebook from the UE.

[0049] In some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein, the HARQ-ACK codebook includes an ACK / NACK indication for the downlink data transmission based on the total TDRA and whether the UE successfully received a repetition set of the downlink data transmission.

[0050] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for transmitting, to the UE in a DCI message, an RRC configuration, or a combination thereof, an indication of the number of repetitions for the downlink data transmission.

[0051] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for scheduling the total TDRA such that no symbol in the total TDRA is configured for uplink.

[0052] Some examples of the methods, devices (apparatus), and non-transient computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: scheduling the total TDRA so that the total TDRA can be within a single time slot. Some other examples of the methods, devices (apparatus), and non-transient computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: scheduling the total TDRA so that the total TDRA spans a set of time slots; and transmitting in the DCI message a feedback timing indicator corresponding to the last time slot in the time slot set, wherein the feedback message may be received based on the feedback timing indicator. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Figure 1 and 2 An example of a wireless communication system supporting time domain resource allocation (TDRA) for downlink data repetition in accordance with aspects of the present disclosure is illustrated.

[0055] Figures 3A to 3EAn example of TDRA supporting TDRA for downlink data repetition in accordance with aspects of the present disclosure is illustrated.

[0056] Figures 4 to 6 An example of a codebook generation process supporting TDRA for downlink data repetition in accordance with aspects of the present disclosure is illustrated.

[0057] Figure 7 An example of TDRA supporting TDRA for downlink data repetition in accordance with aspects of the present disclosure is illustrated.

[0058] Figure 8 An example of a codebook generation process supporting TDRA for downlink data repetition in accordance with aspects of the present disclosure is illustrated.

[0059] Fig. 9 An example of a process flow supporting TDRA for downlink data repetition in accordance with aspects of the present disclosure is illustrated.

[0060] Fig.10 and 11 A block diagram of a device supporting TDRA for downlink data repetition in accordance with aspects of the present disclosure is shown.

[0061] Fig.12 A block diagram of a communications manager supporting TDRA for downlink data repetition is shown in accordance with aspects of the present disclosure.

[0062] Fig.13 A diagram of a system including a device supporting TDRA for downlink data repetition is shown in accordance with aspects of the present disclosure.

[0063] Fig.14 and 15 A block diagram of a device supporting TDRA for downlink data repetition in accordance with aspects of the present disclosure is shown.

[0064] Fig.16 A block diagram of a communications manager supporting TDRA for downlink data repetition is shown in accordance with aspects of the present disclosure.

[0065] Fig.17 A diagram of a system including a device supporting TDRA for downlink data repetition is shown in accordance with aspects of the present disclosure.

[0066] Figures 18 to 21 A flow chart illustrating a method of supporting TDRA for downlink data repetition in accordance with aspects of the present disclosure is shown.

[0067] Detailed Description

[0068] In some wireless communication systems, a base station may schedule multiple repetitions of downlink data transmission to a user equipment (UE) in the same transmission time interval (TTI) (e.g., a single time slot). Each repetition of downlink data transmission within a time slot may use a common modulation and coding scheme (MCS), while using the same or different redundancy versions (RVs) and transmission configuration indicator (TCI) states. The base station may use a single downlink control information (DCI) message and a single time domain resource allocation (TDRA) field in the DCI message to indicate the timing resources for downlink data repetition. In some cases, downlink data repetition may be limited to a single time slot. In other cases, downlink data repetition may span multiple time slots.

[0069] In a first implementation, the base station may set the value of the TDRA field in the DCI message to indicate timing information for a single data repetition (e.g., the first repetition, the last repetition, etc.) in the downlink data repetition. The base station may use the TDRA field to indicate an "explicit" TDRA for the single repetition, and the TDRAs for other repetitions in the downlink data repetition may be implicitly indicated by the explicit TDRA. For example, a UE receiving the DCI message may determine an explicit TDRA from the TDRA field. Using the explicit TDRA (and a set of rules or configurations for other repetitions), the UE may determine one or more "implicit" TDRAs for other repetitions in the downlink data repetition. The UE may receive downlink data repetitions based on these determined TDRAs, and may use a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook to transmit a feedback message to the base station, wherein the UE indicates a positive or negative acknowledgement (ACK / NACK) for the downlink data opportunity corresponding to the explicit TDRA. The UE may use a dummy negative acknowledgement (NACK) for downlink data opportunities without an explicit TDRA (eg, including downlink data opportunities corresponding to an implicit TDRA).

[0070] In a second implementation, the base station may set the value of the TDRA field in the DCI message to indicate the timing information for the aggregated downlink data repetition set. The base station may use the TDRA field to indicate the "total" TDRA for the downlink data repetition set, and the individual TDRA for each specific repetition in the downlink data repetition may be implicitly derived from the total TDRA. For example, the UE may receive the DCI message and determine the total TDRA from the TDRA field. Using the total TDRA (and a set of rules or configurations for individual repetitions), the UE may determine a TDRA set, where each TDRA corresponds to a corresponding repetition in the downlink data repetition. The UE may receive downlink data repetitions based on these determined TDRAs, and may use the HARQ-ACK codebook to transmit a feedback message to the base station, where the UE indicates an ACK / NACK for the downlink data opportunity corresponding to the total TDRA.

[0071] Various aspects of the present disclosure are initially described in the context of a wireless communication system. Additional aspects of the present disclosure are described with reference to TDRA and codebook generation processes. Various aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow charts related to time domain resource allocation for downlink data repetition.

[0072] Figure 1 An example of a wireless communication system 100 supporting time domain resource allocation for downlink data repetition according to various aspects of the present disclosure is illustrated. The wireless communication system 100 may include a base station 105, a UE 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, or a new radio (NR) network. In some cases, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof.

[0073] The base stations 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may be different forms of devices or devices with different capabilities. The base stations 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which the UEs 115 and the base stations 105 may establish communication links 125. The coverage area 110 may be an example of a geographic area over which the base stations 105 and the UEs 115 support signal communication according to one or more radio access technologies.

[0074] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be different forms of devices or devices with different capabilities. Figure 1 105. The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, base stations 105, and / or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment), such as Figure 1 shown.

[0075] Each base station 105 may communicate with the core network 130 or with each other or both. For example, the base station 105 may interface with the core network 130 via a backhaul link 120 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 may communicate with each other directly (e.g., directly between the base stations 105) or indirectly (e.g., via the core network 130), or directly and indirectly on the backhaul link 120 (e.g., via X2, Xn, or other interfaces). In some examples, the backhaul link 120 may be or include one or more wireless links.

[0076] The one or more base stations 105 described herein may include or may be referred to by one of ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a B node, an evolved B node (eNB), a next generation B node or a gigabit B node (any of which may be referred to as a gNB), a home B node, a home evolved B node, or other suitable terminology.

[0077] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances, vehicles, meters, etc.

[0078] The UE 115 described herein may be able to communicate with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as base stations 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 as shown in .

[0079] The UE 115 and the base station 105 may communicate wirelessly with each other via one or more communication links 125 on one or more carriers. The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to a physical layer channel for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. The UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used in conjunction with frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0080] The signal waveform transmitted on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may include a code element period (e.g., the duration of a modulation code element) and a subcarrier, where the code element period and the subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Thus, the more resource elements received by UE 115 and the higher the order of the modulation scheme, the higher the data rate of UE 115 can be. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further improve the data rate or data integrity of communication with UE 115.

[0081] The time interval of the base station 105 or the UE 115 can be expressed as a multiple of a basic time unit, and the basic time unit can be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0082] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some cases, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of code element periods (e.g., depending on the length of the cyclic prefix added before each code element period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-time slots containing one or more code elements. Excluding the cyclic prefix, each code element period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating band.

[0083] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some cases, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0084] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier, for example, using a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a number of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a UE 115. For example, a UE 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for sending control information to multiple UEs 115 and a UE-specific search space set for sending control information to a specific UE 115 .

[0085] In some examples, base stations 105 may be mobile and thus provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, and the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.

[0086] The wireless communication system 100 may be configured to support ultra-reliable communication or low latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low latency communication (URLLC) or mission-critical communication. UE 115 may be designed to support ultra-reliable, low latency or critical functions (e.g., mission-critical functions). Ultra-reliable communication may include private communication or group communication, and may be supported by one or more mission-critical services (such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions may include prioritization of services, and mission-critical services may be used for public safety or general commercial applications. The terms ultra-reliable, low latency, critical mission, and ultra-reliable low latency may be used interchangeably herein.

[0087] In some cases, UE 115 may also be able to communicate directly with other UE 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication may be within a geographic coverage area 110 of a base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of the base station 105, or may not be able to receive transmissions from the base station 105 for other reasons. In some cases, each group of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, wherein each UE 115 transmits to each other UE 115 in the group. In some examples, the base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between each UE 115 without involving the base station 105.

[0088] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and the EPC or 5GC may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a base station 105 associated with the core network 130. User IP packets may be delivered via a user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to a network operator IP service 150. Operator IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0089] Some network devices (such as base stations 105) may include subcomponents, such as access network entities 140, which may be examples of access node controllers (ANCs). Each access network entity 140 may communicate with each UE 115 through several other access network transport entities 145, which may be referred to as radio heads, smart radio heads, or transmission / reception points (TRPs). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or merged into a single network device (e.g., base station 105).

[0090] The wireless communication system 100 may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). In general, the 300 MHz to 3 GHz region is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from about 1 decimeter to 1 meter long. UHF waves may be blocked or redirected by buildings and environmental features, but these waves may penetrate various structures sufficiently for macro cells to provide service to UEs 115 located indoors. Transmissions using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmissions using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0091] The wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating in an unlicensed radio frequency spectrum band, devices (such as base stations 105 and UEs 115) may employ carrier sensing for conflict detection and avoidance. In some cases, operations in an unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in coordination with component carriers operating in a licensed band. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, D2D transmissions, and the like.

[0092] The base station 105 or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the base station 105 or UE 115 may be located in one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some cases, the antennas or antenna arrays associated with the base station 105 may be located at different geographical locations. The base station 105 may have an antenna array having antenna ports of several rows and columns that the base station 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.

[0093] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station 105 or a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each antenna element may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

[0094] UE 115 and base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data on communication link 125. HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve the throughput of the media access control (MAC) layer in poor radio conditions (e.g., low signal-to-noise ratio conditions). In some cases, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In other cases, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0095] In some wireless communication systems 100, the base station 105 may schedule multiple downlink data repetitions for a transport block (TB) within a single time slot. For example, the base station 105 may use a single DCI message to schedule time division multiplexed (TDM) repetitions at a mini-slot granularity. In some cases, using a single DCI to schedule multiple repetitions for a single time slot (e.g., multiple transmission / reception points (TRPs) and / or multi-TCI state scheduling based on a single DCI) may be referred to as "Scheme 3". For "Scheme 3", the base station 105 may schedule repetitions so that n TCI states are scheduled within a time slot with non-overlapping TDRAs. Each transmission opportunity (e.g., each repetition) of a TB may have a TCI state and an RV using a mini-slot time granularity (e.g., 2 symbols, 3 symbols, 4 symbols, 7 symbols, etc.). These TCI states and RVs may be the same or different for different transmission opportunities in a repetition set. However, all transmission opportunities for a repetition set within a slot may use a common MCS with the same demodulation reference signal (DMRS) port (e.g., a single DMRS port or multiple DMRS ports). In some cases, a downlink data repetition set may support channel estimation interpolation across mini-slots with the same TCI state (i.e., the same TCI index).

[0096] The base station 105 may use a single TDRA indication in a single DCI message to indicate different mini-slots corresponding to different scheduled downlink data repetitions (e.g., physical downlink shared channel (PDSCH) repetitions). Additionally, the base station 105 may indicate the number of repetitions, the number of TCI states, or both for a downlink data repetition set. In some examples, these values ​​may correspond to the maximum number of repetitions, the maximum number of TCI states, or both. In some cases, the base station 105 may schedule the downlink data repetition set so that the overall time allocation for repetition does not cross any time slot boundaries. In some other cases, the base station 105 may schedule the downlink data repetition set so that the overall time allocation spans one or more time slot boundaries (although individual repetitions may not span time slot boundaries). The scheduling of downlink data repetitions may affect how the UE 115 receiving the downlink data repetitions implements the HARQ-ACK codebook to provide feedback for the data. In some cases, the codebook may be an example of a semi-static (type 1) HARQ-ACK codebook.

[0097] In a first implementation, the base station 105 may indicate an explicit TDRA for one repetition in a downlink data repetition set in a TDRA field of a DCI message. A UE 115 receiving a DCI message may identify the explicit TDRA from the TDRA field, and may determine implicit TDRAs for other repetitions based on the explicit TDRA. The UE 115 may provide feedback to the base station 105 by inserting an ACK / NACK indication for the explicit TDRA into a HARQ-ACK codebook. In a second implementation, the base station 105 may indicate a total TDRA for a complete downlink data repetition set in a TDRA field of a DCI message. A UE 115 receiving a DCI message may identify a total TDRA from the TDRA field, and may derive an individual TDRA corresponding to each of the downlink data repetitions based on the total TDRA. The UE 115 may provide feedback to the base station 105 by inserting an ACK / NACK indication for the total TDRA into a HARQ-ACK codebook.

[0098] Figure 2 An example of a wireless communication system 200 supporting TDRA for downlink data repetition according to aspects of the present disclosure is illustrated. The wireless communication system 200 may include a UE 115-a and a base station 105-a, which may be referenced Figure 1 Base station 105-a may serve a geographic coverage area 110-a, which may be as described with reference to Figure 1An example of a geographic coverage area 110 is described. The base station 105-a may schedule downlink transmissions to the UE 115-a on a downlink channel 205, and the UE 115-a may transmit a message to the base station 105-a on an uplink channel 210. The downlink channel 205 may be a downlink control channel, a downlink data channel, or a representation of both a downlink control channel and a downlink data channel. Similarly, the uplink channel 210 may correspond to an uplink control channel, an uplink data channel, or both. In some cases, the base station 105-a may schedule multiple downlink data repetitions 225 to the UE 115-a in a single TTI (e.g., a single time slot). The base station 105-a may indicate the TDRA for the downlink data repetition 225 in a single DCI message 215, which reduces overhead on the downlink control channel (e.g., a physical downlink control channel (PDCCH)) compared to transmitting multiple DCI messages to schedule multiple repetitions. Additionally, the base station 105 - a may use a single TDRA field 220 in the DCI message 215 to indicate the TDRA for downlink data repetition 225 , thereby efficiently utilizing the payload of the DCI message 215 .

[0099] For a downlink grant (e.g., base station 105-a grants resources for multiple downlink data repetitions 225), base station 105-a may include a TDRA field 220 in DCI message 215. In some examples, this DCI message 215 may utilize DCI format 1_0, DCI format 1_1, or some other DCI format. The TDRA field 220 may indicate a mapping type, a slot offset (K0), a start symbol (S), an allocation length (L), a start and length indicator (SLIV), or some combination of these parameters. For example, the mapping type may indicate PDSCH mapping type A or PDSCH mapping type B for downlink data repetitions. Different mapping types may correspond to different UE capabilities and may support different values of S, L, and / or SLIV. In some cases, mapping type A may correspond to a repetition with DMRS in fixed symbols, while mapping type B may correspond to a repetition where the DMRS for each repetition can be in any symbol of the slot. Additionally, different repetitions may have different mapping types based on an explicit indication in the DCI or a fixed rule. For example, the first repetition at the start of the slot may have mapping type A, while other subsequent repetitions in the slot may have mapping type B. In this example, multiple mapping types are indicated in the DCI, or one mapping type is indicated in the DCI and may apply to a subset of the repetitions. The slot offset K0 may indicate the timing for downlink data repetition 225 (e.g., relative to DCI 215). For example, the downlink data repetition 225 (e.g., PDSCH transmission) may be transmitted in slot n+K0, where n is the slot with the scheduling DCI 215. If the downlink data repetition 225 spans multiple slots, the slot offset may indicate the first slot or the last slot in the time domain that contains the downlink data repetition 225. The start symbol S may indicate the start symbol of the TDRA, and the allocation length L may indicate the duration of the TDRA. Alternatively, SLIV may indicate S and L jointly (e.g., according to equation 1).

[0100] If (L - 1) ≤ 7, then SLIV = 14·(L - 1) + S

[0101] Otherwise SLIV = 14·(14 - L + 1) + (14 - 1 - S) (1)

[0102] where 0 < L ≤ 14 - S. In a specific example, the TDRA field 220 may indicate type A or type B for the mapping type, a value between 0 and 32 for K0, and a value between 0 and 127 for SLIV.

[0103] Additionally or alternatively, the TDRA field 220 may indicate an entity of a higher layer parameter PDSCH-TimeDomainAllocationList (PDSCH time domain allocation list), if the higher layer parameter is configured. In such a case, the TDRA field 220 may include a number of bits, depending on the number of entries in the configurable table for the time domain allocation list (e.g., 0-4 bits). Otherwise, the TDRA field 220 may indicate an entry in a default table (e.g., using a set number of bits, such as 4 bits).

[0104] The base station 105-a may schedule downlink data repetitions 225, and may determine the TDRA field 220 based on the scheduled downlink data repetitions 225. In a first example, the base station 105-a may set the value of the TDRA field 220 to indicate timing information for a single data repetition in the downlink data repetitions 225 (e.g., the first repetition in the time domain, the last repetition in the time domain, etc.). In some cases, the single data repetition indicated by the TDRA field 220 may be referred to as a "first repetition", where "first" does not have any temporal meaning (e.g., because the "first" repetition may be before or after other repetitions in the time domain). In such an example, the base station 105-a may use the TDRA field 220 to indicate an "explicit" TDRA for a single repetition, and the TDRAs for other repetitions in the downlink data repetitions 225 may be implicitly indicated by the explicit TDRA. For example, the "explicit" TDRA may be indicated using a bit in a message (e.g., the TDRA field 220). In some examples, these bits may indicate a mapping type, a K0 value, an S value, an L value, a SLIV value, or a combination of these parameters to explicitly define parameters for TDRA. An "implicit" TDRA may not be indicated using bits in a message, but may instead be determined relative to an explicit TDRA. For example, a bit in the TDRA field 220 may not indicate one or more values ​​for implicit TDRA, but the UE 115-a may determine parameters for implicit TDRA based on the relationship between implicit TDRA and explicit TDRA (or based on any other relationship configured at the UE 115-a). The UE 115-a may receive a DCI message 215 and determine an explicit TDRA from the TDRA field 220. Using an explicit TDRA (and a set of rules or configurations for other repetitions), the UE 115-a may determine one or more "implicit" TDRAs for other repetitions in the downlink data repetition 225.

[0105] In a second example, the base station 105-a may set the value of the TDRA field 220 to indicate timing information for the aggregated set of downlink data repetitions 225. In such an example, the base station 105-a may use the TDRA field 220 to indicate an "overall" TDRA for the downlink data repetitions 225, and the individual TDRAs for each specific one of the downlink data repetitions 225 may be implicitly derived from the overall TDRA. The UE 115-a may receive the DCI message 215 and determine the overall TDRA from the TDRA field 220. Using the overall TDRA (and the set of rules or configurations for the individual repetitions), the UE 115-a may determine a set of TDRAs, each of which corresponds to a respective one of the downlink data repetitions 225.

[0106] The base station 105-a may transmit downlink data repetitions 225 in scheduled timing resources (e.g., granted by a DCI message 215). The UE 115-a may receive the downlink data repetitions 225 in the allocated timing resources according to the determined TDRA. Based on whether the data reception procedure is successful, the UE 115-a may transmit a feedback message to the base station 105-a. For example, the UE 115-a may transmit HARQ-ACK information 230 to the base station 105-a in the feedback message. The HARQ-ACK information 230 may indicate whether the UE 115-a successfully received the downlink data repetitions 225 (or at least a subset of the downlink data repetitions 225). Based on the HARQ-ACK information 230, the base station 105-a may determine whether to retransmit the downlink data to the UE 115-a (e.g., if the UE 115-a fails to indicate that it successfully received the downlink data, if the UE 115-a indicates that it failed to receive the downlink data, etc.).

[0107] The HARQ-ACK information 230 may be based on a HARQ-ACK codebook. In some examples, the codebook may be an example of a semi-static (type 1) codebook. However, in other examples, other codebook formats may be used for the HARQ-ACK information 230 for the downlink data repetition 225. The size of the HARQ-ACK codebook may be determined (e.g., by UE 115-a) via semi-static information. For example, UE 115-a may determine the size of the HARQ-ACK codebook based on possible scheduling opportunities for downlink data candidates (e.g., PDSCH opportunities or opportunities for candidate PDSCH reception). UE 115-a may not take into account any PDCCH monitoring opportunities when determining the size of the HARQ-ACK codebook.

[0108] UE 115-a may determine a set of PDSCH opportunities for each downlink serving cell serving UE 115-a. For example, UE 115-a may determine a PDSCH opportunity for base station 105-a. If UE 115-a is concurrently served by another serving cell (e.g., in a carrier aggregation (CA) configuration), UE 115-a may additionally determine PDSCH opportunities for an additional serving cell (not shown). UE 115-a may determine a set of PDSCH opportunities for a downlink serving cell based on a configured PDSCH to HARQ-ACK delay (K1) value set, a TDRA candidate set, a time division duplex (TDD) configuration, or a combination thereof. For example, UE 115-a may be configured with a set of potential K1 values ​​based on a DCI type configured for a serving cell. If DCI 1_0 (rather than DCI 1_1) is configured for a serving cell, the K1 value may be from the set {1, 2, 3, 4, 5, 6, 7, 8}. If DCI 1_1 is configured for a serving cell, the K1 value may be semi-statically indicated to the UE 115-a in the dl-DataToUL-ACK field in the physical uplink control channel (PUCCH) configuration. The UE 115-a may be additionally configured with a PDSCH TDRA candidate set (within a time slot) represented by a parameter R. The configuration may be based on a configured TDRA table or a default TDRA table for the UE 115-a. The TDD configuration may indicate the uplink and downlink symbols for the UE 115-a within a time slot.

[0109] The UE 115-a may arrange the HARQ-ACK codebook in a time-first (e.g., based on the PDSCH opportunity) and cell-second manner. In some cases, the number of ACK / NACK indications or bits used by the UE 115-a per PDSCH opportunity per serving cell may depend on one or more configurations, such as the number of TBs per PDSCH (e.g., 1 or 2), the code block group (CBG) configuration (e.g., up to 8), or any other configuration. If the UE 115-a receives a DCI message 215 instructing the UE 115-a to feedback ACK / NACK information for the corresponding PDSCH in time slot n (e.g., in a PUCCH message, in a physical uplink shared channel (PUSCH) message, etc.), the UE 115-a may insert the actual ACK / NACK indication for the PDSCH opportunity in the codebook. For example, if the UE 115-a successfully receives and decodes the PDSCH, the UE 115-a may insert a positive acknowledgement (ACK) into the HARQ-ACK codebook. If UE 115-a does not successfully receive and / or decode the PDSCH, UE 115-a may insert a NACK into the HARQ-ACK codebook. Additionally or alternatively, for PDSCH opportunities for which UE 115-a did not receive instructions to provide ACK / NACK feedback in time slot n, UE 115-a may insert a NACK into the HARQ-ACK codebook. In this way, the NACK may not indicate a reception or decoding failure at UE 115-a, but may simply indicate that UE 115-a did not receive data in the PDSCH opportunity. This may also support robustness against missed DCI messages 215, because UE 115-a may report a NACK even if UE 115-a missed the DCI message 215 requesting ACK / NACK feedback.

[0110] Compared to a UE 115 supporting one TB per time slot, the size of the HARQ-ACK codebook may be larger for a UE 115 supporting a mini-time slot configuration. For example, because a mini-time slot configuration may support more than one PDSCH opportunity per time slot, a UE 115-a may feedback multiple ACK / NACK bits for multiple PDSCH opportunities. In some cases, the ACK / NACK indication may be a single bit, where one bit value of the bit (e.g., 1) indicates ACK, and another bit value of the bit (e.g., 0) indicates NACK. Additionally or alternatively, the size of the HARQ-ACK codebook may be based on the size of the K1 set, the number of serving cells (e.g., component carriers (CCs)), the number of CBG configurations, etc. In some cases, a UE 115-a may use a single HARQ-ACK codebook (e.g., based on a range of Kl values) to feedback HARQ-ACK information 230 for multiple time slots.

[0111] UE 115-a may determine the number of PDSCH opportunities (eg, per serving cell) for HARQ-ACK feedback based on the configured TDRA candidates for the time slot. In one example, UE 115-a may set PDSCH opportunity set M A,C Initialized to an empty set. UE 115-a may iterate through the K1 value set (K 1,k ∈K1). UE 115-a may consider the TDRA candidate set R and may remove the TDRA candidate set R in time slot nK. 1,k ) that conflict with the corresponding TDD uplink / downlink configuration. UE 115-a may then consider all remaining TDRA candidates R. If UE 115-a indicates a UE capability to receive more than one unicast PDSCH per time slot (e.g., UE 115-a supports receiving multiple mini-slot-based PDSCH transmissions per time slot), UE 115-a may divide the TDRA candidate set into subgroups of TDRA candidates. The number of subgroups may correspond to the maximum number of possible non-overlapping PDSCH receptions per time slot based on the rows of R (i.e., the TDRA candidates in R). Each subgroup may represent a time slot nK. 1,k In this way, a single PDSCH opportunity may correspond to one or more TDRA candidates for UE 115-a.

[0112] In the first example described herein (e.g., implementing an explicit TDRA indication in a DCI message 215), the UE 115-a may determine the HARQ-ACK information 230 based on the explicit TDRA. For example, the UE 115-a may generate a HARQ-ACK codebook by inserting an ACK / NACK for a PDSCH opportunity corresponding to an explicit TDRA while inserting a dummy NACK for any PDSCH opportunity that does not correspond to an explicit TDRA within a time slot. This may provide a one-to-one mapping between a DCI message 215 received at the UE 115-a and a corresponding ACK / NACK transmitted by the UE 115-a. That is, by avoiding inserting an ACK / NACK for an implicit TDRA implicitly indicated by the DCI message 215, the UE 115-a may avoid transmitting multiple ACK / NACKs for downlink data repetitions 225 scheduled by the same DCI message 215.

[0113] In the second example described herein (e.g., implementing the total TDRA indication in the DCI message 215), the UE 115-a may determine the HARQ-ACK information 230 based on the total TDRA. For example, the UE 115-a may generate a HARQ-ACK codebook by inserting ACK / NACK for the PDSCH opportunity corresponding to the total TDRA. If the total TDRA spans multiple time slots, the UE 115-a may insert ACK / NACK for the PDSCH opportunity in the latest time slot in the time domain.

[0114] For some codebooks, UE 115 or base station 105 may determine the PDSCH timing based on TDD configuration or mode. For example, if at least one symbol of a TDRA candidate is configured for uplink, UE 115 or base station 105 may remove the TDRA candidate from the TDRA candidate list. However, in other cases, if the nominal candidate can be split into multiple repetitions based on downlink / uplink switching, the device may not remove the TDRA candidate with at least one uplink symbol. For example, if UE115-a supports splitting the nominal repetition into multiple actual repetitions due to downlink / uplink switching, UE 115-a may handle the TDRA candidate with one or more symbols configured as uplink. In the first example, UE 115-a may not remove the TDRA candidate with the symbol configured for uplink. In the second example, if all symbols of the TDRA candidate are configured for uplink, UE 115-a may remove the TDRA candidate, otherwise the TDRA candidate may be maintained. In a third example, if no two consecutive symbols remain configured for downlink after omitting the symbols configured for uplink, UE 115-a may remove the TDRA candidate, otherwise the TDRA candidate may be maintained. That is, if no valid mini-slot remains for the actual candidate after the split, UE 115-a may remove the TDRA candidate. Base station 105-a may implement the same rules.

[0115] In some other cases, the base station 105-a may schedule the TDRA so that there are no repetitions that conflict with the TDD mode. For example, the TDRA indicated in the DCI 215 (whether explicit TDRA or total TDRA) may not include any symbols configured for uplink. The scheduling may be implemented by the network, and the UE 115-a may remove TDRA candidates based on TDD mode conflicts (e.g., due to scheduling handled by the base station 105-a).

[0116] Figures 3A to 3EAn example of a TDRA 300 supporting TDRA for downlink data repetitions in accordance with aspects of the present disclosure is illustrated. In some cases, the TDRA field in the DCI message may indicate a time domain resource for one repetition in a set of multiple downlink data repetitions (e.g., as described herein with reference to Figure 2 310). This may be referred to as an "explicit" TDRA 310 for this one repetition. In some examples, the TDRA may be the first TDRA in the time domain. In some other examples, the TDRA may be the last TDRA in the time domain. The base station 105 transmitting the DCI and the UE 115 receiving the DCI may be configured to determine whether the explicit TDRA 310 corresponds to the first or last TDRA in the time domain. Other repetitions in the set of multiple downlink data repetitions may have the same length as the explicit TDRA 310 and may be contiguous with the explicit TDRA 310. For example, based on whether the explicit TDRA 310 is the first or last TDRA in the time domain, other TDRAs may be immediately after or before the explicit TDRA in a sequential manner. In this way, the UE 115 receiving the explicit TDRA 310 may implicitly derive other TDRAs (i.e., "implicit" TDRA 315) from the timing (e.g., start symbol and length) and number of repetitions of the explicit TDRA 310.

[0117] In some cases, the base station 105 may separately indicate the number of repetitions to the UE 115 (e.g., dynamically via DCI, semi-statically via radio resource control (RRC) configuration, etc.). Each repetition (e.g., an indicated number of repetitions, repetitions explicitly indicated in the TDRA field, etc.) may be an actual repetition or a nominal repetition. The nominal repetition may be further split into multiple actual repetitions based on a slot boundary, a downlink / uplink switching point, or both. The actual repetition may not be split into multiple repetitions (and accordingly, may not cross a slot boundary).

[0118] The base station 105 may schedule a downlink data repetition set based on one or more rules or configurations. In a first example, the base station 105 may schedule repetitions so that all repetitions are in the same time slot (e.g., the same TTI). In such examples, explicit TDRA may be used for the first repetition in the time domain or the last repetition in the time domain. In a second example, the base station 105 may schedule repetitions so that a complete repetition set may cross a time slot boundary, while each individual repetition may not cross a time slot boundary. In a third example, the base station 105 may schedule repetitions so that repetitions may cross a time slot boundary. Repetitions across time slot boundaries may correspond to nominal repetitions, which may be split into multiple repetitions. In the second example, the third example, or both, explicit TDRA may be used for the last repetition in the time domain. For example, since different repetitions may be in different time slots, the K1 value (e.g., PDSCH to HARQ feedback timing indicator) may indicate a HARQ-ACK delay starting from the last time slot in time containing the repetition (e.g., to support sufficient processing time for UE 115 to process data and determine ACK / NACK feedback). For these examples, making explicit TDRA correspond to the last repetition in time (and accordingly, the last time slot) can support sufficient timing delay for HARQ feedback and can simplify semi-static HARQ-ACK codebook construction. However, in some cases, for the second and third examples, explicit TDRA can be used for the first repetition in the time domain.

[0119] Figure 3A An example of a TDRA 300-a limited to a single time slot 305-a is illustrated, wherein an explicit TDRA 310 is the first TDRA in the time domain. The UE 115 may receive a DCI message indicating an explicit TDRA 310 with a start symbol S=2 and a length L=4. Additionally, the UE 115 may determine that the downlink data repetition set includes two repetitions (e.g., based on a DCI message, an RRC message, a preconfigured value, etc.). Based on the explicit TDRA 310, the UE 115 may identify the timing resources for the first repetition 320-a. In addition, based on the timing and repetition number for the explicit TDRA 310, the UE 115 may determine an implicit TDRA 315 for the second repetition 320-b. That is, the UE 115 may determine that the second repetition 320-b is immediately after the first repetition 320-a in time and has the same length as the first repetition 320-a. In this manner, UE 115 may implicitly determine the TDRA for a downlink data repetition set based on an indication of the TDRA information for a single repetition.

[0120] Figure 3BAn example of a TDRA 300-b limited to a single time slot 305-b is illustrated, wherein an explicit TDRA 310 is the last TDRA in the time domain. The UE 115 may receive a DCI message indicating an explicit TDRA 310 with a start symbol S=10 and a length L=4. Additionally, the UE 115 may determine that a downlink data repetition set includes three repetitions. Based on the explicit TDRA 310, the UE 115 may identify a timing resource for a first repetition 320-e. In addition, based on the timing and repetition number for the explicit TDRA 310, the UE 115 may determine an implicit TDRA 315 for a second repetition 320-d and a third repetition 320-c. For example, the second repetition 320-d may immediately precede the first repetition 320-e in time and have the same duration as the first repetition 320-e, and the third repetition 320-c may immediately precede the second repetition 320-d in time and also have the same duration.

[0121] Figure 3C An example of a TDRA 300-c spread across multiple time slots 305 is illustrated, wherein an explicit TDRA 310 is the last TDRA in the time domain and does not cross a time slot boundary. That is, a base station 105 that schedules downlink data repetitions may schedule repetitions so that S+L for the explicit TDRA 310 is not greater than 14. A UE 115 may receive a DCI message indicating an explicit TDRA 310 with a start symbol S=4 and a length L=4. Additionally, a UE 115 may determine that a downlink data repetition set includes three repetitions. Based on the explicit TDRA 310, a UE 115 may identify a timing resource for a first repetition 320-h. In addition, based on the timing and repetition number for the explicit TDRA 310, a UE 115 may determine an implicit TDRA 315 for a second repetition 320-g and a third repetition 320-f. For example, the second repetition 320-g may be immediately before the first repetition 320-h in time and have the same duration as the first repetition 320-h, while the third repetition 320-f may be immediately before the second repetition 320-g in time and also have the same duration. Although the explicit TDRA 310 is scheduled for time slot 305-d, the downlink data repetition set may span into time slot 305-c (e.g., the previous time slot). As illustrated, no individual repetition may span a time slot boundary, so the number of repetitions (i.e., three) may correspond to the actual number of repetitions.

[0122] Figure 3DAn example of a TDRA 300-d spread across multiple time slots 305 is illustrated, wherein an explicit TDRA 310 is the last TDRA in the time domain and does not cross a time slot boundary. That is, a base station 105 that schedules downlink data repetitions may schedule repetitions so that S+L for the explicit TDRA 310 is not greater than 14. A UE 115 may receive a DCI message indicating an explicit TDRA 310 with a start symbol S=2 and a length L=7. Additionally, a UE 115 may determine that a downlink data repetition set includes two repetitions. Based on the explicit TDRA 310, a UE 115 may identify a timing resource for a first repetition 320-k. In addition, based on the timing and repetition number for the explicit TDRA 310, a UE 115 may determine an implicit TDRA 315 for a second repetition 320-j and a third repetition 320-i. That is, UE 115 may determine a nominal repetition having the same length as repetition 320-k directly before repetition 320-k. However, UE 115 may identify that the nominal repetition crosses the time slot boundary between time slot 305-e and time slot 305-f. Thus, due to crossing the time slot boundary, UE 115 may split the nominal repetition into multiple actual repetitions, wherein the actual repetition does not cross the time slot boundary. Due to the splitting procedure, these actual repetitions 320-i and 320-j may not have the same length as explicit TDRA 310. Based on this configuration, the last repetition 320-k (i.e., the repetition corresponding to explicit TDRA 310) may not cross the time slot boundary, but different repetitions may be in different consecutive time slots 305.

[0123] Figure 3EAn example of a TDRA 300-e spread across multiple time slots 305 is illustrated, wherein an explicit TDRA 310 may span a time slot boundary. That is, a base station 105 that schedules downlink data repetitions may schedule repetitions so that S+L for explicit TDRA 310 is greater than 14. A UE 115 may receive a DCI message indicating an explicit TDRA 310 with a start symbol S=10 and a length L=8. Additionally, a UE 115 may determine that a downlink data repetition set includes two repetitions. Based on the explicit TDRA 310, a UE 115 may identify that an explicit TDRA 310 spans a time slot boundary between a time slot 305-g and a time slot 305-h. That is, a repetition corresponding to an explicit TDRA 310 may be an example of a nominal repetition, and due to spanning a time slot boundary, a UE 115 may split the nominal repetition into an actual repetition. UE 115 may determine actual repetitions 320-m and 320-n based on explicit TDRA 310 (so that the actual repetitions do not cross time slot boundaries) and may determine implicit TDRA 315 for repetition 320-1 based on explicit TDRA 310 and the indicated number of repetitions. In this example, the indicated number of repetitions is nominal and the actual number of repetitions is greater than the indicated number of repetitions.

[0124] Figure 4 An example of a codebook generation process 400 supporting TDRA for downlink data repetition according to aspects of the present disclosure is illustrated. The codebook generation process 400 may be referred to as Figure 1 and 210. The UE 115 described in the embodiment of the present invention may be performed. For example, the UE 115 may support a set of TDRA candidates 420 for the time slot 405. The set of TDRA candidates 420 (e.g., eight TDRA candidates) may correspond to three downlink data opportunities 425 (e.g., PDSCH opportunities 425). For example, the UE 115 may divide the TDRA candidates 420 into subgroups. The UE 115 may identify the TDRA candidate 420 that ends earliest in the time slot 405 (i.e., the second TDRA candidate 420 that ends in symbol 5), and may identify each other TDRA candidate 420 that overlaps with the TDRA candidate 420 in at least one symbol. These identified TDRA candidates 420 may correspond to the first PDSCH opportunity 425-a. The UE 115 may then identify the TDRA candidate 420 that ends earliest in the time slot 405 (i.e., the fifth and sixth TDRA candidates 420 that end in symbol 10) from the remaining candidates that have not yet been assigned to the PDSCH opportunity 425. UE 115 may identify each other TDRA candidate 420 that overlaps with these TDRA candidates 420 in at least one symbol and may assign these TDRA candidates 420 to PDSCH opportunities 425-b. UE 115 may continue this process until all TDRA candidates 420 are assigned to PDSCH opportunities 425. In this way, UE 115 may determine PDSCH opportunities 425-a (corresponding to the first four TDRA candidates 420), PDSCH opportunities 425-b (corresponding to the next three TDRA candidates 420), and PDSCH opportunities 425-c (corresponding to the last TDRA candidate 420).

[0125] UE 115 may receive a DCI message indicating an explicit TDRA 410 and may determine an implicit TDRA 415 based on the explicit TDRA 410 and the number of repetitions. The TDRA set may be limited to a single time slot 405. For example, UE 115 may receive an explicit TDRA 410 with a start symbol S=3 and a length L=4, wherein the explicit TDRA 410 corresponds to the first repetition in the time domain. The explicit TDRA 410 may correspond to a TDRA candidate 420 in a PDSCH opportunity 425-a. In order to create a HARQ-ACK codebook 430 (e.g., a semi-static codebook) for feedback in the time slot 405, UE 115 may use the PDSCH opportunity 425-a for the explicit TDRA 410 repetition. That is, when a mini-slot repetition is transmitted by the base station 105, the ACK / NACK 435 in the codebook 430 may correspond to the explicit TDRA 410. UE 115 may insert ACK / NACK 435 at a position in codebook 430 corresponding to PDSCH opportunity 425-a (e.g., because explicit TDRA 410 is scheduled in PDSCH opportunity 425-a). For other PDSCH opportunities 425 in slot 405 that do not correspond to explicit TDRA 410, UE 115 may insert dummy NACK 440. For example, UE 115 may insert dummy NACK 440-a at a position in codebook 430 corresponding to PDSCH opportunity 425-b, and insert dummy NACK 440-b at a position in codebook 430 corresponding to PDSCH opportunity 425-c. As illustrated, even though UE 115 may receive implicit TDRA 415 in opportunity 425-b, UE 115 may send a NACK for opportunity 425-b (i.e., dummy NACK 440-a) to support reduced complexity and one-to-one mapping between DCI messages and ACK / NACK 435. UE 115 may use HARQ-ACK codebook 430 to transmit feedback information to base station 105 that sent downlink data repetitions.

[0126] Figure 5 An example of a codebook generation process 500 supporting TDRA for downlink data repetition according to aspects of the present disclosure is illustrated. The codebook generation process 500 may be referred to as Figure 1 and 2 For example, the UE 115 may support a set of TDRA candidates 520 for the time slot 505-b. The set of TDRA candidates 520 (eg, eight TDRA candidates) may correspond to three downlink data opportunities 525 (eg, PDSCH opportunities 525).

[0127] UE 115 may receive a DCI message indicating an explicit TDRA 510 and may determine one or more implicit TDRAs 515 based on the explicit TDRA 510 and the number of repetitions. A TDRA set may cross a time slot boundary into a second time slot 505-a (e.g., a previous time slot). For example, UE 115 may receive an explicit TDRA 510 with a start symbol S=2 and a length L=4, wherein the explicit TDRA 510 corresponds to the last repetition in the time domain. UE 115 may determine a nominal implicit TDRA that crosses a time slot boundary before the explicit TDRA 510 and may split the nominal implicit TDRA into an actual implicit TDRA 515 that does not cross a time slot boundary. A downlink data repetition set spans time slots 505-a and 505-b.

[0128] The explicit TDRA 510 may correspond to the TDRA candidate 520 in the PDSCH opportunity 525-a. In order to create a HARQ-ACK codebook 530 (e.g., a semi-static codebook) for feedback, the UE 115 may use the PDSCH opportunity 525-a for the explicit TDRA 510 repetition. That is, when the mini-slot repetition is transmitted by the base station 105, the ACK / NACK 535 in the codebook 530 may correspond to the explicit TDRA 510. Since the downlink data repetition spans multiple time slots, the Kl value indicated in the DCI message K1 (e.g., PDSCH to HARQ_Feedback Timing Indicator) field may start from the time slot 505 (e.g., time slot 505-b) containing the last repetition in time. The explicit TDRA 510 (i.e., corresponding to the last repetition in time) may not cross the time slot boundary. In this way, the UE 115 may insert the ACK / NACK 535 at a position in the codebook 530 corresponding to the PDSCH opportunity 525-a in the last time slot 505-b (e.g., because the explicit TDRA 510 is scheduled in the PDSCH opportunity 525-a of the time slot 505-b). For other PDSCH opportunities 525 in the time slot 505 that do not correspond to the explicit TDRA 510, the UE 115 may insert a dummy NACK 540. For example, the UE 115 may insert dummy NACKs 540-a, 540-b, and 540-c for the PDSCH opportunity 525 in the time slot 505-a, and may insert dummy NACKs 540-d and 540-e for the PDSCH opportunities 525-b and 525-c of the time slot 505-b. The UE 115 may use the HARQ-ACK codebook 530 to transmit feedback information to the base station 105 that sent the downlink data repetitions.

[0129] Figure 6 An example of a codebook generation process 600 supporting TDRA for downlink data repetition according to aspects of the present disclosure is illustrated. The codebook generation process 600 may be referred to as Figure 1 and 2 115 may be performed by the UE 115 described in the embodiment of the present invention. The UE 115 may receive a DCI message indicating an explicit TDRA 610 and may determine one or more implicit TDRAs 615 based on the explicit TDRA 610 and the number of repetitions. The explicit TDRA 610 may be the last repetition of the downlink data repetition set in the time domain. Accordingly, the K1 (e.g., PDSCH to HARQ_feedback timing indicator) field may start from the time slot 605 containing the last repetition in time. If the explicit TDRA 610 crosses a time slot boundary, the K1 value may start from the time slot containing the last actual repetition in time (e.g., after the explicit TDRA 610 is split into multiple actual repetitions due to crossing the boundary).

[0130] UE 115 may determine modified TDRA candidates 620 based on candidates that potentially cross slot boundaries (e.g., by considering two or more consecutive slots 605). For example, UE 115 may include in the set of TDRA candidates 620 TDRA candidates 620 corresponding to potential timing resources for the last actual repetition after the split procedure. For example, as illustrated, slot 605-a may include TDRA candidates 620 that may cross slot boundaries and enter slot 605-b. The portion of these candidates that spans into slot 605-b may be added as TDRA candidates 620 in slot 605-b. These may be TDRA candidates 620 corresponding to PDSCH opportunities 625-a. That is, for the purpose of HARQ-ACK codebook 630 generation, the possible position of the last actual repetition in a single slot 605-b (after splitting) may be added to the possible TDRA candidates 620. Adding these TDRA candidates 620 can be based on the original TDRA candidates 620 of S+L>14 starting in the previous time slot 605-a, wherein the added TDRA candidates 620 correspond to the last actual repetition in the current time slot 605-b due to crossing the time slot boundary. In addition, the original TDRA candidates 620 of S+L>14 starting in the current time slot 605-b can be removed (because these will cause the last actual repetition in the subsequent time slot). The resulting new TDRA candidate 620 set can represent the possible timing position for the last actual repetition and can be limited to a single time slot 605. UE 115 can identify downlink data opportunities 625 (for example, based on the modification procedure for handling the splitting of explicit TDRA 610) from the new TDRA candidate 620 set. For example, UE 115 can identify PDSCH opportunities 625-a, PDSCH opportunities 625-b and PDSCH opportunities 625-c.

[0131] UE 115 may receive an explicit TDRA 610 with a start symbol S=10 and a length L=8, wherein the explicit TDRA 610 corresponds to the last repetition in the time domain. UE 115 may determine that the explicit TDRA 610 is a nominal TDRA (e.g., based on the fact that the explicit TDRA 610 spans a time slot boundary between time slot 605-a and time slot 605-b) and may split the explicit TDRA 610 into separate actual TDRAs for separate repetitions. UE 115 may additionally determine one or more implicit TDRAs 615 based on the explicit TDRA 610.

[0132] UE 115 may create a semi-static codebook 630 based on the PDSCH opportunity 625 for the explicit TDRA 610 repetition. For example, when the mini-slot repetition is transmitted by the base station 105, the ACK / NACK 635 in the codebook 630 may correspond to the explicit TDRA 610. However, if the explicit TDRA 610 crosses the time slot boundary (i.e., for the explicit TDRA 610, S+L>14), the portion of the last time slot 605-b of the explicit TDRA 610 in the time domain is used. The portion may correspond to the new TDRA candidate 620 added to the set of TDRA candidates 620 of the time slot 605-b as described above. Accordingly, the UE 115 may insert ACK / NACK 635 into the codebook 630 for the PDSCH opportunity 625-a of the time slot 605-b based on the explicit TDRA 610 in the last time slot 605-b. The UE 115 may insert dummy NACKs 640 for other PDSCH opportunities 625 that do not correspond to explicit TDRA 610 within slot 605-b (and any other slots 605 that correspond to the same HARQ-ACK feedback message). For example, the UE 115 may insert dummy NACKs 640-a, 640-b, and 640-c for PDSCH opportunities 625 in slot 605-a, and may insert dummy NACKs 640-d and 640-e for PDSCH opportunities 625-b and 625-c of slot 605-b. The UE 115 may use the HARQ-ACK codebook 630 to transmit feedback information to the base station 105 that sent the downlink data repetition.

[0133] Figure 7 An example of a TDRA 700 supporting TDRA for downlink data repetitions in accordance with aspects of the present disclosure is illustrated. In some cases, the TDRA field 715 in the DCI message 710 may indicate the time domain resources for all repetitions in a set of multiple downlink data repetitions (e.g., as described herein with reference to Figure 2715). This may be referred to as an “overall” TDRA for a downlink data repetition set. Base station 105 may transmit DCI message 710 indicating the overall TDRA, and UE 115 may receive DCI message 710, identify the overall TDRA based on TDRA field 715, and derive the individual TDRAs for downlink data repetitions 720. Base station 105 and UE 115 may be referenced Figure 1 and 2 Examples of devices described.

[0134] For example, the UE 115 may identify the total TDRA based on the start symbol S=2 and the length L=8 indicated in the TDRA field 715. The UE 115 may derive the plurality of repetitions 720 from the set of symbols indicated in the TDRA field 715 (e.g., the set of symbols including the total TDRA) based on one or more rules and / or configurations. In a first example, the UE 115 may identify the repetitions 720 that are evenly distributed within the total TDRA. For example, for two repetitions, the first L / 2 symbols may belong to the first repetition 720-a, and the last L / 2 symbols may belong to the second repetition 720-b. In a second example, the UE 115 may identify the repetition 720 (e.g., the TDRA for the repetition 720) based on the non-arbitrary length of each repetition 720. For example, the UE 115 may implement a rule for dividing the total TDRA into a plurality of repetitions 720 based on a finite set of symbol lengths (e.g., {2, 4, 7}) corresponding to the effective mini-slot duration for the downlink data repetition 720. In a third example, the UE 115 may implement one or more additional or alternative rules for dividing the total TDRA into respective TDRAs for each repetition 720. The base station 105 scheduling the repetition 720 may use the same set of rules to determine the total TDRA to be indicated in the TDRA field 715, which accurately indicates the downlink data repetition 720 to the UE 115. The first symbol for each repetition 720 in the time domain (e.g., after dividing the total TDRA) may be a DMRS symbol. In some cases, the number of repetitions 720 may be fixed, configured via RRC, dynamically indicated in DCI signaling, or some combination thereof.

[0135] In some cases, in order to perform more scheduling control at the base station 105, the base station 105 may indicate the partition across the repetition 720. For example, in the DCI message 710, the base station 105 may include an indication of how to partition the total TDRA (e.g., in the TDRA field 715 or in another DCI field). In a first example, the partition across the repetition 720 may be indicated by defining multiple repeated TDRA entries (e.g., indicating that symbols 2-5 are used for repetition 720-a and symbols 6-9 are used for repetition 720-b). In a second example, the partition may be indicated by indicating a separate start symbol for each repetition 720.

[0136] In some cases, the total TDRA may be contained within the time slot 705. For example, if S+L≤14, all repetitions 720 may be within the same time slot 705. In some such cases, the UE 115 may implement a HARQ-ACK codebook based on the total TDRA (e.g., a semi-static (type 1) HARQ-ACK codebook). Since the total TDRA includes all repetitions 720 and is within a single time slot 705, the UE 115 may insert ACK / NACK indications into the codebook for the PDSCH opportunities corresponding to the total TDRA.

[0137] In some other cases, the total TDRA may span multiple time slots 705 (not shown). For example, if S+L>14, the set of repetitions 720 may span multiple time slots 705. In some such cases, the UE 115 may implement a rule for dividing the total TDRA based on time slot boundaries (e.g., such that after dividing the total TDRA into downlink data repetitions 720, no repetition 720 spans a time slot boundary). The UE 115 may implement a HARQ-ACK codebook (e.g., a semi-static (Type 1) HARQ-ACK codebook) based on the total TDRA and the same as described herein with reference to Figure 6 For example, UE 115 may provide an ACK / NACK for the total TDRA corresponding to the last slot in the time domain for a set of slots. The ACK / NACK may be inserted for PDSCH opportunities added to the slot based on the TDRA candidate entering the slot across a slot boundary.

[0138] Figure 8 An example of a codebook generation process 800 supporting TDRA for downlink data repetition according to aspects of the present disclosure is illustrated. The codebook generation process 800 may be referred to as Figure 1 and 2105. The UE 115 may identify a semi-static repetition number of downlink data repetitions from the base station 105. For example, the repetition number may be pre-configured at the UE 115, semi-statically configured via RRC signaling, or a combination thereof (i.e., the repetition number does not dynamically change via DCI signaling). In some such situations, the UE 115 may implement techniques (e.g., optimization) that reduce the number of downlink data opportunities 825 tracked by the UE 115. When implementing explicit TDRA 810, reducing the number of PDSCH opportunities 825 may correspondingly reduce the number of redundant feedback bits.

[0139] In a time slot 805 including an explicit TDRA 810, the UE 115 may extend the TDRA candidates 820 based on the explicit TDRA 810 and a repetition number (e.g., a fixed downlink data repetition number) to additionally cover the implicit TDRA 815. The extended TDRA candidates 820 may be based on an implicit TDRA rule implemented by the base station 105 transmitting the downlink data repetitions and the UE 115 receiving the downlink data repetitions.

[0140] As illustrated, if the downlink data repetition set is limited to a single time slot 805, the UE 115 may remove any extended TDRA candidates 820 that cross into another time slot. The UE 115 may determine the PDSCH opportunity 825 using a modified set of TDRA candidates 840, wherein the modified set includes an extended TDRA candidate (e.g., based on a fixed repetition number of 2) that does not cross any time slot boundary. Based on the reduced number of TDRA candidates and the extended length of the TDRA candidates, the modified set of TDRA candidates 840 may correspond to a reduced set of PDSCH opportunities 825. For example, the modified set of TDRA candidates 840 may correspond to a single PDSCH opportunity 825. When the UE 115 receives an explicit TDRA 810, determines an implicit TDRA 815, and receives a corresponding downlink data repetition, the UE 115 may provide a single ACK / NACK 835 corresponding to a single PDSCH opportunity 825 for a DCI message in the codebook 830. Based on reducing the number of PDSCH opportunities 825 using a semi-static repetition number, the codebook 830 may not include additional bits (eg, dummy NACKs for other PDSCH opportunities). The UE 115 may transmit a feedback message with a reduced payload based on the reduced HARQ-ACK codebook 830 size.

[0141] In the case where the TDRA candidates 820 may span multiple time slots, the UE 115 may use the last time slot in the time domain for HARQ-ACK feedback. Extended TDRA candidates 820 (e.g., based on explicit TDRA 810 and implicit TDRA 815) in the time slots after the last time slot may be removed from the modified TDRA candidate 840 set because these will not correspond to the last time slot. The UE 115 may also use the modified TDRA candidate 840 set to calculate the PDSCH opportunity 825 for these situations, thereby effectively reducing the HARQ-ACK payload.

[0142] Fig. 9 An example of a process flow 900 for supporting TDRA for downlink data repetition according to aspects of the present disclosure is illustrated. In some examples, the process flow 900 may include a base station 105-b and a UE 115-b, which may be referenced Figure 1 and 2 Examples of corresponding devices described. Base station 105-b and UE 115-b may support scheduling multiple downlink data repetitions using a single DCI message. The following alternative examples may be implemented, in which some of the steps are performed in a different order than described or not performed at all. In some cases, each step may include additional features not mentioned below, or further steps may be added.

[0143] At 905, base station 105-b may transmit a DCI message to UE 115-b. The DCI message may include a TDRA field. In a first implementation, the DCI message may indicate an explicit TDRA for a single repetition (e.g., a "first" repetition) of downlink data transmission. In a second implementation, the DCI message may indicate a total TDRA for a set of repetitions of downlink data transmission.

[0144] At 910, UE 115-b may determine a TDRA based on the TDRA indicated in the TDRA field. In a first implementation, UE 115-b may determine one or more implicit TDRAs for one or more additional repetitions of downlink data transmission based on the explicit TDRA (e.g., and the number of repetitions). In a second implementation, UE 115-b may determine a TDRA set of repetition sets for downlink data transmission based on the total TDRA and the number of repetitions of the downlink data transmission.

[0145] At 915, the base station 105-b may transmit a repetition of the downlink data transmission to the UE 115-b. The UE 115-b may receive the repetition of the downlink data transmission based on the determined TDRA. In a first implementation, the UE 115-b may receive a "first" repetition of the downlink data transmission and one or more additional repetitions of the downlink data transmission from the base station 105-b according to the explicit TDRA and one or more implicit TDRAs. In a second implementation, the UE 115-b may receive a set of repetitions of the downlink data transmission from the base station 105-b according to the set of TDRAs.

[0146] At 920, UE 115-b may generate a HARQ-ACK codebook (e.g., a semi-static (type 1) HARQ-ACK codebook). In a first implementation, UE 115-b may generate the HARQ-ACK codebook based on an explicit TDRA (e.g., corresponding to the last time slot in the time domain that contains a repetition of downlink data transmission). In a second implementation, UE 115-b may generate the HARQ-ACK codebook based on a total TDRA. At 925, UE 115-b may transmit a feedback message to base station 105-b based on the HARQ-ACK codebook. Base station 105-b may receive the feedback message and may determine whether to retransmit the downlink data transmission to UE 115-b based on the feedback.

[0147] Fig.10 A block diagram 1000 of a device 1005 supporting TDRA for downlink data repetition according to aspects of the present disclosure is shown. The device 1005 may be an example of aspects of a UE 115 as described herein. The device 1005 may include a receiver 1010, a communication manager 1015, and a transmitter 1020. The device 1005 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0148] The receiver 1010 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 TDRA for downlink data repetition, etc.). The information may be passed to other components of the device 1005. The receiver 1010 may be a reference Fig.13 Examples of various aspects of the transceiver 1320 are described. The receiver 1010 may utilize a single antenna or a collection of antennas.

[0149] In some examples, the communication manager 1015 may receive a DCI message from a base station indicating an explicit TDRA for a first repetition of downlink data transmission; determine one or more implicit TDRAs for one or more additional repetitions of the downlink data transmission based on the explicit TDRA; receive the first repetition of the downlink data transmission and one or more additional repetitions of the downlink data transmission from the base station based on the explicit TDRA and the one or more implicit TDRAs; and transmit a feedback message to the base station based on the reception and the HARQ-ACK codebook.

[0150] In some other examples, the communication manager 1015 may receive a DCI message indicating a total TDRA for a repetition set used for downlink data transmission from a base station; determine a TDRA set of repetition sets used for the downlink data transmission based on the total TDRA and the number of repetitions used for the downlink data transmission; receive a repetition set for the downlink data transmission from the base station according to the TDRA set; and transmit a feedback message to the base station based on the reception and the HARQ-ACK codebook.

[0151] The actions performed by the communication manager 1015 as described herein may be implemented to achieve one or more potential advantages. For example, determining multiple TDRAs (e.g., implicit TDRAs, TDRAs from total TDRAs, etc.) from a single DCI message may reduce control channel overhead. Additionally, determining multiple TDRAs based on a single TDRA field may limit the payload size of the DCI, thereby efficiently utilizing the DCI field. In addition, providing an ACK / NACK indication for a DCI message (e.g., in a feedback message) may reduce complexity by maintaining a one-to-one correlation between ACK / NACK feedback and the DCI message.

[0152] Based on determining the downlink data TDRA from a single DCI message, the processor of UE 115 (e.g., a processor controlling receiver 1010, communication manager 1015, transmitter 1020, etc.) can reduce the processing resources used for downlink reception. For example, UE 115 can receive a single DCI and decode a single TDRA field to determine multiple downlink data repetitions. In this way, UE 115 can reduce the number of times the processor ramps up the processing power and turns on the processing unit to handle DCI reception and / or decoding. In addition, reducing the number of DCI messages can reduce the signaling overhead on the downlink control channel. Additionally, considering the TDRA indicated in the DCI message for HARQ feedback (e.g., rather than implicit TDRA or each individual TDRA) can reduce the processing resources used for HARQ feedback (e.g., due to determining a single ACK / NACK for a set of multiple downlink data repetitions).

[0153] The communication manager 1015 may be an example of aspects of the communication manager 1310 described herein. The communication manager 1015 or its subcomponents may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1015 or its subcomponents may be performed 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.

[0154] The communication manager 1015 or its subcomponents may be physically located at various locations, including being distributed such that portions of functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 1015 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 1015 or its subcomponents may be combined with one or more other hardware components (including, but not limited to, input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof).

[0155] The transmitter 1020 may transmit signals generated by other components of the device 1005. In some examples, the transmitter 1020 may be co-located with the receiver 1010 in a transceiver module. For example, the transmitter 1020 may be a reference Fig.13 Examples of various aspects of the transceiver 1320 are described. The transmitter 1020 may utilize a single antenna or a collection of antennas.

[0156] Fig.11 A block diagram 1100 of a device 1105 supporting TDRA for downlink data repetition according to aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or UE 115 as described herein. The device 1105 may include a receiver 1110, a communication manager 1115, and a transmitter 1150. The device 1105 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0157] The receiver 1110 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 TDRA for downlink data repetition, etc.). The information may be passed to other components of the device 1105. The receiver 1110 may be a reference Fig.13Examples of various aspects of transceiver 1320 are described. Receiver 1110 may utilize a single antenna or a collection of antennas.

[0158] The communication manager 1115 may be an example of aspects of the communication manager 1015 as described herein. The communication manager 1115 may include an explicit TDRA component 1120, an implicit TDRA component 1125, a data receiving component 1130, a feedback component 1135, an overall TDRA component 1140, an overall TDRA divider 1145, or some combination thereof. The communication manager 1115 may be an example of aspects of the communication manager 1310 described herein.

[0159] In some cases, the explicit TDRA component 1120 may receive a DCI message from the base station indicating an explicit TDRA for a first repetition of downlink data transmission. The implicit TDRA component 1125 may determine one or more implicit TDRAs for one or more additional repetitions of the downlink data transmission based on the explicit TDRA. The data receiving component 1130 may receive the first repetition of the downlink data transmission and one or more additional repetitions of the downlink data transmission from the base station based on the explicit TDRA and one or more implicit TDRAs. The feedback component 1135 may transmit a feedback message to the base station based on the reception and the HARQ-ACK codebook.

[0160] In some other cases, the total TDRA component 1140 may receive a DCI message indicating the total TDRA of the repetition set for downlink data transmission from the base station. The total TDRA divider 1145 may determine the TDRA set of the repetition set for the downlink data transmission based on the total TDRA and the number of repetitions for the downlink data transmission. The data receiving component 1130 may receive the repetition set of the downlink data transmission from the base station according to the TDRA set. The feedback component 1135 may transmit a feedback message to the base station based on the reception and the HARQ-ACK codebook.

[0161] The transmitter 1150 may transmit signals generated by other components of the device 1105. In some examples, the transmitter 1150 may be co-located with the receiver 1110 in a transceiver module. For example, the transmitter 1150 may be a reference Fig.13 Examples of various aspects of the transceiver 1320 are described. The transmitter 1150 may utilize a single antenna or a collection of antennas.

[0162] Fig.12A block diagram 1200 of a communication manager 1205 supporting TDRA for downlink data repetition according to aspects of the present disclosure is shown. The communication manager 1205 may be an example of aspects of the communication manager 1015, the communication manager 1115, or the communication manager 1310 described herein. The communication manager 1205 may include an explicit TDRA component 1210, an implicit TDRA component 1215, a data receiving component 1220, a feedback component 1225, a HARQ-ACK codebook component 1230, a TDRA candidate component 1235, a repetition number component 1240, a total TDRA component 1245, a total TDRA divider 1250, or a combination thereof. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0163] In a first implementation, explicit TDRA component 1210 may receive a DCI message indicating an explicit TDRA for a first repetition of downlink data transmission from a base station. In some cases, the DCI message indicates explicit TDRA according to a start symbol, an allocation length, a SLIV, a mapping type, a slot offset, or a combination thereof. In some examples, no symbol is configured to be used for uplink in explicit TDRA.

[0164] Implicit TDRA component 1215 can determine one or more implicit TDRAs for one or more additional repetitions of the downlink data transmission based on explicit TDRA. In some cases, explicit TDRA and one or more implicit TDRAs are in a single time slot. In some other cases, explicit TDRA and one or more implicit TDRAs span time slot sets. In some such cases, the feedback timing indicator may correspond to the last time slot in the time slot set, wherein the feedback message is transmitted based on the feedback timing indicator. In some cases, explicit TDRA spans time slot sets. In some such cases, the first repetition of downlink data transmission is the first nominal repetition, and the repetition number component 1240 can determine the first actual repetition of the downlink data transmission in the first time slot in the time slot set and the second actual repetition of the downlink data transmission in the second time slot after the first time slot in the time slot set based on the first nominal repetition, wherein the second time slot is the last time slot in the time slot set. In some cases, the TDRA candidate component 1235 may modify the TDRA candidate set based on the TDRA candidates that cross the slot boundary, wherein the HARQ-ACK codebook is based on the modified TDRA candidate set.

[0165] In some cases, the first repetition of the downlink data transmission and each of the one or more additional repetitions of the downlink data transmission are of the same length. In some cases, the explicit TDRA is located before one or more implicit TDRAs in time. In some other cases, the explicit TDRA is located after one or more implicit TDRAs in time. In some cases, the explicit TDRA and one or more implicit TDRAs are coherent in time.

[0166] Data receiving component 1220 can receive a first repetition of the downlink data transmission and one or more additional repetitions of the downlink data transmission from the base station according to the explicit TDRA and one or more implicit TDRAs. Feedback component 1225 can transmit a feedback message to the base station based on the reception and the HARQ-ACK codebook.

[0167] The HARQ-ACK codebook component 1230 may generate the HARQ-ACK codebook based on the explicit TDRA and the reception. In some examples, generating the HARQ-ACK codebook may involve: the HARQ-ACK codebook component 1230 inserts an ACK / NACK indication for the downlink data transmission based on the explicit TDRA and the reception for the first downlink data opportunity of the HARQ-ACK codebook. In some examples, generating the HARQ-ACK codebook may further involve: the HARQ-ACK codebook component 1230 inserts one or more dummy NACK indications for the downlink data transmission based on the absence of an explicit TDRA corresponding to the one or more additional downlink data opportunities for the HARQ-ACK codebook. Additionally or alternatively, if the feedback message is transmitted in a first time slot for feedback, the HARQ-ACK codebook component 1230 may, for one or more additional downlink data opportunities of the HARQ-ACK codebook, insert one or more dummy NACK indications for the downlink data transmission in a second time slot for feedback that is different from the first time slot for feedback based on an additional explicit TDRA indication corresponding to at least one of the one or more additional downlink data opportunities.

[0168] In some cases, the size of the HARQ-ACK codebook is based on a TDRA candidate set, wherein an explicit TDRA corresponds to a candidate in the TDRA candidate set, and a downlink data opportunity of the HARQ-ACK codebook is based on the TDRA candidate set. In some cases, the HARQ-ACK codebook is an example of a semi-static codebook, a type 1 codebook, or both.

[0169] In some examples, the TDRA candidate component 1235 may suppress including the TDRA candidate in the TDRA candidate set when the symbol of the TDRA candidate is configured for uplink, all symbols of the TDRA candidate are configured for uplink, at most one consecutive symbol of the TDRA candidate is configured for downlink, or a combination thereof. In some examples, the number of repetitions for the downlink data transmission is semi-statically configured, and the TDRA candidate component 1235 may determine the TDRA candidate set based on the number of repetitions to cover both the explicit TDRA candidate and the corresponding implicit TDRA candidate.

[0170] The repetition number component 1240 may identify the repetition number of the downlink data transmission, wherein determining one or more implicit TDRAs is based on the repetition number. In some cases, the repetition number is identified based on a DCI message, an RRC configuration, or a combination thereof. In some examples, the repetition number is a nominal repetition number, and the repetition number component 1240 may determine an actual repetition number based on the nominal repetition number and a slot boundary, an uplink / downlink switching point, or a combination thereof, wherein determining one or more implicit TDRAs is based on the actual repetition number.

[0171] In a second implementation, the total TDRA component 1245 may receive a DCI message indicating the total TDRA of a repetition set for downlink data transmission from a base station. In some examples, no symbol in the total TDRA is configured for uplink. In some cases, the total TDRA is within a single time slot. In some other cases, the total TDRA spans a time slot set. The DCI message may indicate the total TDRA according to a start symbol, an allocation length, a SLIV, a mapping type, a time slot offset, or a combination thereof.

[0172] The total TDRA divider 1250 can determine the TDRA set of the repetition set for the downlink data transmission based on the total TDRA and the number of repetitions for the downlink data transmission. In some cases, the TDRA set is further determined based on the possible size set of each TDRA in the TDRA set, the equal distribution of the TDRA set in the total TDRA, or a combination thereof. In some cases, the first symbol of each TDRA in the TDRA set in time corresponds to a DMRS symbol.

[0173] Data receiving component 1220 can receive a repetition set of the downlink data transmission from the base station according to the TDRA set. Feedback component 1225 can transmit a feedback message to the base station based on the reception and the HARQ-ACK codebook.

[0174] In some examples, repetition number component 1240 may identify a repetition number for downlink data transmission based on a DCI message, an RRC configuration, a fixed repetition value, or a combination thereof.

[0175] In some examples, the TDRA candidate component 1235 may determine a TDRA candidate set based on an uplink symbol, wherein the HARQ-ACK codebook is based on the determined TDRA candidate set. In some cases, determining the TDRA candidate set may involve: the TDRA candidate component 1235 suppresses including the TDRA candidate in the TDRA candidate set when the TDRA candidate's symbol is configured for uplink, all symbols of the TDRA candidate are configured for uplink, at most one consecutive symbol of the TDRA candidate is configured for downlink, or a combination thereof.

[0176] In some cases, if the total TDRA spans multiple time slots, the TDRA set may be further determined based on the time slot boundaries of the time slot set. In some cases, the feedback timing indicator may correspond to the last time slot in time in the time slot set, wherein the feedback message is transmitted based on the feedback timing indicator.

[0177] Fig.13 A diagram of a system 1300 including a device 1305 supporting TDRA for downlink data repetition according to various aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a UE 115 as described herein or include a component of the device 1005, the device 1105, or the UE 115. The device 1305 may include components for two-way voice and data communications, including components for transmitting and receiving communications, including a communication manager 1310, an I / O controller 1315, a transceiver 1320, an antenna 1325, a memory 1330, and a processor 1340. These components may be in electronic communication via one or more buses (e.g., a bus 1345).

[0178] The communication manager 1310 may receive a DCI message indicating an explicit TDRA for a first repetition of downlink data transmission from a base station; determine one or more implicit TDRAs for one or more additional repetitions of the downlink data transmission based on the explicit TDRA; receive the first repetition of the downlink data transmission and one or more additional repetitions of the downlink data transmission from the base station according to the explicit TDRA and the one or more implicit TDRAs; and transmit a feedback message to the base station based on the reception and the HARQ-ACK codebook.

[0179] Additionally or alternatively, the communication manager 1310 may receive a DCI message indicating a total TDRA of a repetition set for downlink data transmission from a base station; determine a TDRA set of a repetition set for the downlink data transmission based on the total TDRA and the number of repetitions used for the downlink data transmission; receive a repetition set for the downlink data transmission from the base station according to the TDRA set; and transmit a feedback message to the base station based on the reception and the HARQ-ACK codebook.

[0180] I / O controller 1315 can manage input and output signals for device 1305. I / O controller 1315 can also manage peripheral devices that are not integrated into device 1305. In some cases, I / O controller 1315 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1315 can utilize an operating system, such as or another known operating system. In other cases, I / O controller 1315 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1315 may be implemented as part of a processor. In some cases, a user may interact with device 1305 via I / O controller 1315 or via hardware components controlled by I / O controller 1315.

[0181] The transceiver 1320 can communicate bidirectionally via one or more antennas, wired or wireless links, as described above. For example, the transceiver 1320 may represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1320 may also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, and demodulate packets received from an antenna.

[0182] In some cases, a wireless device may include a single antenna 1325. However, in some cases, the device may have more than one antenna 1325, which may be capable of transmitting or receiving multiple wireless transmissions concurrently.

[0183] Memory 1330 may include random access memory (RAM) and read-only memory (ROM). Memory 1330 may store computer-readable, computer-executable code 1335 including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, memory 1330 may include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0184] The code 1335 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1335 may be stored in a non-transitory computer-readable medium, such as a system memory or other type of memory. In some cases, the code 1335 may not be directly executed by the processor 1340, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0185] Processor 1340 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a central processing unit (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, processor 1340 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 1340. Processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to cause device 1305 to perform various functions (e.g., functions or tasks of supporting TDRA for downlink data repetition).

[0186] Fig.14 A block diagram 1400 of a device 1405 supporting TDRA for downlink data repetition according to aspects of the present disclosure is shown. The device 1405 may be an example of aspects of a base station 105 as described herein. The device 1405 may include a receiver 1410, a communication manager 1415, and a transmitter 1420. The device 1405 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0187] Receiver 1410 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 TDRA for downlink data repetition, etc.). The information may be passed to other components of device 1405. Receiver 1410 may be a reference Fig.17 Examples of various aspects of the transceiver 1720 are described. The receiver 1410 may utilize a single antenna or a collection of antennas.

[0188] In some examples, the communication manager 1415 may transmit a DCI message to the UE indicating an explicit TDRA for a first repetition of downlink data transmission; transmit the first repetition of the downlink data transmission to the UE according to the explicit TDRA and transmit one or more additional repetitions of the downlink data transmission to the UE according to one or more implicit TDRAs, wherein the one or more implicit TDRAs are based on the explicit TDRA; and receive a feedback message based on the explicit TDRA and the HARQ-ACK codebook from the UE.

[0189] In some other examples, the communication manager 1415 may transmit a DCI message to the UE indicating a total TDRA of a repetition set for downlink data transmission; transmit the repetition set of the downlink data transmission to the UE according to the TDRA set, wherein the total TDRA includes a TDRA set based on the number of repetitions used for the downlink data transmission; and receive a feedback message based on the total TDRA and the HARQ-ACK codebook from the UE.

[0190] The actions performed by the communication manager 1415 as described herein may be implemented to achieve one or more potential advantages. For example, using a single DCI transmission to indicate multiple TDRAs (e.g., implicit TDRAs, TDRAs from a total TDRA, etc.) may reduce control channel overhead. Additionally, using a single TDRA field to indicate multiple TDRAs may limit the payload size of the DCI, thereby efficiently utilizing the DCI field. Furthermore, receiving an ACK / NACK indication for a DCI message (e.g., in a feedback message) may reduce complexity by maintaining a one-to-one correlation between the ACK / NACK feedback and the DCI message.

[0191] Based on using a single DCI message to indicate the downlink data TDRA, the processor of the base station 105 (e.g., a processor controlling the receiver 1410, the communication manager 1415, the transmitter 1420, etc.) can reduce the processing resources used for downlink transmission. For example, the base station 105 can encode a single TDRA field and transmit a single DCI to indicate multiple downlink data repetitions. In this way, the base station 105 can reduce the number of times the processor ramps up the processing power and turns on the processing unit to handle DCI encoding and / or transmission. In addition, reducing the number of DCI messages can reduce the signaling overhead on the downlink control channel. Additionally, considering that the TDRA indicated in the DCI message is used for HARQ feedback (e.g., rather than implicit TDRA or each individual TDRA) can reduce the processing resources used to handle HARQ feedback (e.g., due to receiving and checking a single ACK / NACK for a set of multiple downlink data repetitions).

[0192] The communication manager 1415 may be an example of aspects of the communication manager 1710 described herein. The communication manager 1415 or its subcomponents may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1415 or its subcomponents may be performed by a general purpose processor, DSP, ASIC, FPGA or other programmable logic device designed to perform the functions described in this disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.

[0193] The communication manager 1415 or its subcomponents may be physically located at various locations, including being distributed such that portions of functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 1415 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 1415 or its subcomponents may be combined with one or more other hardware components (including, but not limited to, I / O components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof).

[0194] Transmitter 1420 may transmit signals generated by other components of device 1405. In some examples, transmitter 1420 may be co-located with receiver 1410 in a transceiver module. For example, transmitter 1420 may be a reference Fig.17 Examples of various aspects of the transceiver 1720 are described. The transmitter 1420 may utilize a single antenna or a collection of antennas.

[0195] Fig.15 A block diagram 1500 of a device 1505 supporting TDRA for downlink data repetition according to aspects of the present disclosure is shown. The device 1505 may be an example of aspects of the device 1405 or base station 105 as described herein. The device 1505 may include a receiver 1510, a communication manager 1515, and a transmitter 1535. The device 1505 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0196] Receiver 1510 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 TDRA for downlink data repetition, etc.). The information may be passed to other components of device 1505. Receiver 1510 may be a reference Fig.17 Examples of various aspects of the transceiver 1720 are described. The receiver 1510 may utilize a single antenna or a collection of antennas.

[0197] The communication manager 1515 may be an example of aspects of the communication manager 1415 as described herein. The communication manager 1515 may include a DCI component 1520, a data duplication component 1525, and a feedback receiving component 1530. The communication manager 1515 may be an example of aspects of the communication manager 1710 described herein.

[0198] In some cases, the DCI component 1520 may transmit a DCI message to the UE indicating an explicit TDRA for a first repetition of a downlink data transmission. The data repetition component 1525 may transmit the first repetition of the downlink data transmission to the UE according to the explicit TDRA and transmit one or more additional repetitions of the downlink data transmission to the UE according to one or more implicit TDRAs, wherein the one or more implicit TDRAs are based on the explicit TDRA. The feedback receiving component 1530 may receive a feedback message based on the explicit TDRA and the HARQ-ACK codebook from the UE.

[0199] In some other cases, the DCI component 1520 may transmit a DCI message indicating the total TDRA of the repetition set for downlink data transmission to the UE. The data repetition component 1525 may transmit the repetition set of the downlink data transmission to the UE according to the TDRA set, wherein the total TDRA includes a TDRA set based on the number of repetitions used for the downlink data transmission. The feedback receiving component 1530 may receive a feedback message based on the total TDRA and the HARQ-ACK codebook from the UE.

[0200] Transmitter 1535 may transmit signals generated by other components of device 1505. In some examples, transmitter 1535 may be co-located with receiver 1510 in a transceiver module. Fig.17 Examples of various aspects of the transceiver 1720 are described. The transmitter 1535 may utilize a single antenna or a collection of antennas.

[0201] Fig.16 A block diagram 1600 of a communication manager 1605 supporting TDRA for downlink data repetition in accordance with aspects of the present disclosure is shown. The communication manager 1605 may be an example of aspects of the communication manager 1415, the communication manager 1515, or the communication manager 1710 described herein. The communication manager 1605 may include a DCI component 1610, a data repetition component 1615, a feedback reception component 1620, a repetition indication component 1625, a scheduler 1630, a feedback timing indication component 1635, or a combination thereof. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0202] In a first implementation, the DCI component 1610 may transmit a DCI message indicating an explicit TDRA for a first repetition of a downlink data transmission to the UE. The data repetition component 1615 may transmit the first repetition of the downlink data transmission to the UE according to the explicit TDRA and transmit one or more additional repetitions of the downlink data transmission to the UE according to one or more implicit TDRAs, wherein the one or more implicit TDRAs are based on the explicit TDRA. The feedback receiving component 1620 may receive a feedback message based on the explicit TDRA and the HARQ-ACK codebook from the UE.

[0203] In some cases, the HARQ-ACK codebook includes an ACK / NACK indication for the downlink data transmission based on an explicit TDRA and whether the UE successfully received a first repetition of the downlink data transmission.

[0204] The repetition indication component 1625 may transmit an indication of the number of repetitions for the downlink data transmission to the UE in a DCI message, an RRC configuration, or a combination thereof, wherein one or more implicit TDRAs are further based on the number of repetitions. In some examples, the indication of the number of repetitions indicates a nominal number of repetitions, and the repetition indication component 1625 may determine an actual number of repetitions based on the nominal number of repetitions and a slot boundary, an uplink / downlink switching point, or a combination thereof, wherein one or more implicit TDRAs are further based on the actual number of repetitions.

[0205] In some examples, the scheduler 1630 may schedule explicit TDRA so that no symbol is configured for uplink in the explicit TDRA. In some cases, the scheduler 1630 may schedule explicit TDRA and one or more implicit TDRAs so that the explicit TDRA and one or more implicit TDRAs are in a single time slot. In some other cases, the scheduler 1630 may schedule explicit TDRA and one or more implicit TDRAs so that the explicit TDRA and one or more implicit TDRAs span a time slot set. The feedback timing indication component 1635 may transmit a feedback timing indicator corresponding to the last time slot in the time slot set in the DCI message, wherein the feedback message is received based on the feedback timing indicator.

[0206] In a second implementation, the DCI component 1610 may transmit a DCI message indicating a total TDRA for a repetition set for downlink data transmission to the UE. The data repetition component 1615 may transmit a repetition set for the downlink data transmission to the UE according to the TDRA set, wherein the total TDRA includes a TDRA set based on the number of repetitions for the downlink data transmission. The feedback receiving component 1620 may receive a feedback message based on the total TDRA and the HARQ-ACK codebook from the UE.

[0207] In some cases, the HARQ-ACK codebook includes an ACK / NACK indication for the downlink data transmission based on the total TDRA and whether the UE successfully received a repetition set of the downlink data transmission.

[0208] The repetition indication component 1625 can transmit an indication of a number of repetitions for the downlink data transmission to the UE in a DCI message, an RRC configuration, or a combination thereof.

[0209] In some examples, the scheduler 1630 may schedule the total TDRA so that no symbol in the total TDRA is configured for uplink. In some cases, the scheduler 1630 may schedule the total TDRA so that the total TDRA is within a single time slot. In some other cases, the scheduler 1630 may schedule the total TDRA so that the total TDRA spans a set of time slots. In some examples, the feedback timing indication component 1635 may transmit a feedback timing indicator corresponding to the last time slot in the time slot set in the DCI message, wherein the feedback message is received based on the feedback timing indicator.

[0210] Fig.17 A diagram of a system 1700 including a device 1705 supporting TDRA for downlink data repetition according to various aspects of the present disclosure is shown. The device 1705 may be an example of a device 1405, a device 1505, or a base station 105 as described herein or include components of these devices. The device 1705 may include components for two-way voice and data communications, including components for transmitting and receiving communications, including a communication manager 1710, a network communication manager 1715, a transceiver 1720, an antenna 1725, a memory 1730, a processor 1740, and an inter-station communication manager 1745. These components may be in electronic communication via one or more buses (e.g., a bus 1750).

[0211] The communication manager 1710 may transmit a DCI message indicating an explicit TDRA for a first repetition of downlink data transmission to the UE; transmit the first repetition of the downlink data transmission to the UE according to the explicit TDRA and transmit one or more additional repetitions of the downlink data transmission to the UE according to one or more implicit TDRAs, wherein the one or more implicit TDRAs are based on the explicit TDRA; and receive a feedback message based on the explicit TDRA and the HARQ-ACK codebook from the UE.

[0212] Additionally or alternatively, the communication manager 1710 may transmit a DCI message indicating a total TDRA of a repetition set for downlink data transmission to the UE; transmit the repetition set of the downlink data transmission to the UE according to the TDRA set, wherein the total TDRA includes a TDRA set based on the number of repetitions used for the downlink data transmission; and receive a feedback message based on the total TDRA and the HARQ-ACK codebook from the UE.

[0213] The network communications manager 1715 may manage communications with the core network 130 (eg, via one or more wired backhaul links). For example, the network communications manager 1715 may manage the delivery of data communications for client devices, such as one or more UEs 115.

[0214] The transceiver 1720 may communicate bidirectionally via one or more antennas, wired or wireless links, as described above. For example, the transceiver 1720 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1720 may also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, and demodulate packets received from an antenna.

[0215] In some cases, a wireless device may include a single antenna 1725. However, in some cases, the device may have more than one antenna 1725, which may be capable of transmitting or receiving multiple wireless transmissions concurrently.

[0216] Memory 1730 may include RAM, ROM, or a combination thereof. Memory 1730 may store computer readable code 1735 including instructions that, when executed by a processor (e.g., processor 1740), cause the device to perform various functions described herein. In some cases, memory 1730 may include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0217] Processor 1740 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, processor 1740 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into processor 1740. Processor 1740 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1730) so that device 1705 performs various functions (e.g., functions or tasks of supporting TDRA for downlink data repetition).

[0218] The inter-site communication manager 1745 may manage communications with other base stations 105 and may include a controller or scheduler for controlling communications with UE 115 in cooperation with other base stations 105. For example, the inter-site communication manager 1745 may coordinate the scheduling of transmissions to UE 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-site communication manager 1745 may provide an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between base stations 105.

[0219] The code 1735 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1735 may be stored in a non-transitory computer-readable medium, such as a system memory or other type of memory. In some cases, the code 1735 may not be directly executed by the processor 1740, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0220] Fig.18 1 is a flow chart illustrating a method 1800 for supporting TDRA for downlink data repetition according to aspects of the present disclosure. The operations of the method 1800 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of the method 1800 may be implemented by a UE 115 or components thereof as described herein. Figures 10 to 13 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the following functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the following functions.

[0221] At 1805, the UE may receive a DCI message from a base station indicating an explicit TDRA for a first repetition of downlink data transmission. The operations of 1805 may be performed according to the methods described herein. In some examples, aspects of the operations of 1805 may be performed as described with reference to Figures 10 to 13 The explicit TDRA components described are implemented.

[0222] At 1810, the UE may determine one or more implicit TDRAs for one or more additional repetitions of the downlink data transmission based on the explicit TDRA. The operations of 1810 may be performed according to the methods described herein. In some examples, aspects of the operations of 1810 may be as described with reference to Figures 10 to 13 The implicit TDRA component described is implemented.

[0223] At 1815, the UE may receive a first repetition of the downlink data transmission and one or more additional repetitions of the downlink data transmission from the base station according to the explicit TDRA and one or more implicit TDRAs. The operations of 1815 may be performed according to the methods described herein. In some examples, aspects of the operations of 1815 may be performed as described with reference to Figures 10 to 13 The data receiving component described is executed.

[0224] At 1820, the UE may transmit a feedback message to the base station based on the received and HARQ-ACK codebook. The operations of 1820 may be performed according to the methods described herein. In some examples, aspects of the operations of 1820 may be performed as described with reference to Figures 10 to 13 Describes the feedback component to perform.

[0225] Fig.19 1 is a flow chart illustrating a method 1900 for supporting TDRA for downlink data repetition according to aspects of the present disclosure. The operations of the method 1900 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of the method 1900 may be implemented by a UE 115 or components thereof as described herein. Figures 10 to 13 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the following functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the following functions.

[0226] At 1905, the UE may receive a DCI message from a base station indicating a total TDRA for a repetition set of downlink data transmissions. The operations of 1905 may be performed according to the methods described herein. In some examples, aspects of the operations of 1905 may be performed as described with reference to Figures 10 to 13 Describes the overall TDRA components to be performed.

[0227] At 1910, the UE may determine a TDRA set of a repetition set for the downlink data transmission based on the total TDRA and the number of repetitions for the downlink data transmission. The operations of 1910 may be performed according to the methods described herein. In some examples, aspects of the operations of 1910 may be performed as described with reference to Figures 10 to 13 The overall TDRA divider described is performed.

[0228] At 1915, the UE may receive a repetition set of the downlink data transmission from the base station according to the TDRA set. The operations of 1915 may be performed according to the methods described herein. In some examples, aspects of the operations of 1915 may be performed as described with reference to Figures 10 to 13 The data receiving component described is executed.

[0229] At 1920, the UE may transmit a feedback message to the base station based on the received and HARQ-ACK codebook. The operations of 1920 may be performed according to the methods described herein. In some examples, various aspects of the operations of 1920 may be performed as described with reference to Figures 10 to 13 Describes the feedback component to perform.

[0230] Fig. 20 1 is a flow chart illustrating a method 2000 for supporting TDRA for downlink data repetition according to aspects of the present disclosure. The operations of the method 2000 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of the method 2000 may be implemented by a base station 105 or components thereof as described herein. Figures 14 to 17 In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0231] At 2005, the base station may transmit a DCI message to the UE indicating a first repetition of an explicit TDRA for downlink data transmission. The operations of 2005 may be performed according to the methods described herein. In some examples, aspects of the operations of 2005 may be performed as described with reference to Figures 14 to 17 The DCI components described are performed.

[0232] At 2010, the base station may transmit a first repetition of the downlink data transmission to the UE according to an explicit TDRA and transmit one or more additional repetitions of the downlink data transmission to the UE according to one or more implicit TDRAs, wherein the one or more implicit TDRAs are based on the explicit TDRA. The operations of 2010 may be performed according to the methods described herein. In some examples, aspects of the operations of 2010 may be performed as described with reference to Figures 14 to 17 Describes the data repeating components to perform.

[0233] At 2015, the base station may receive a feedback message based on an explicit TDRA and HARQ-ACK codebook from the UE. The operations of 2015 may be performed according to the methods described herein. In some examples, various aspects of the operations of 2015 may be performed as described with reference to Figures 14 to 17 The feedback receiving component described is executed.

[0234] Fig.21 2 is a flowchart illustrating a method 2100 for supporting TDRA for downlink data repetition according to aspects of the present disclosure. The operations of the method 2100 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of the method 2100 may be implemented by a base station 105 or components thereof as described herein. Figures 14 to 17In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0235] At 2105, the base station may transmit a DCI message to the UE indicating the total TDRA for the repetition set for downlink data transmission. The operations of 2105 may be performed according to the methods described herein. In some examples, aspects of the operations of 2105 may be performed as described with reference to Figures 14 to 17 The DCI components described are performed.

[0236] At 2110, the base station may transmit a repetition set of the downlink data transmission to the UE according to the TDRA set, wherein the total TDRA includes a TDRA set based on the number of repetitions used for the downlink data transmission. The operations of 2110 may be performed according to the methods described herein. In some examples, aspects of the operations of 2110 may be performed as described with reference to Figures 14 to 17 Describes the data repeating components to perform.

[0237] At 2115, the base station may receive a feedback message based on the total TDRA and HARQ-ACK codebook from the UE. The operations of 2115 may be performed according to the methods described herein. In some examples, various aspects of the operations of 2115 may be performed as described with reference to Figures 14 to 17 The feedback receiving component described is executed.

[0238] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0239] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applied to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0240] The information and signals described herein may be represented using any of a variety of different techniques and technologies. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout this description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0241] The various illustrative blocks and modules described in conjunction with the disclosure herein may be implemented or executed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0242] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Other examples and implementations fall within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features that implement the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented at different physical locations.

[0243] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to transfer from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.As an example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, disk storage or other magnetic storage device, or can be used to carry or store instruction or data structure form of desired program code means and can be accessed by general or special-purpose computer or general or special-purpose processor any other non-transient medium.Similarly, any connection is also properly referred to as computer-readable medium.For example, if software is transmitted from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then this coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are just included in the definition of computer-readable medium. Disk and disc as used herein include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0244] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Similarly, as used herein, the phrase "based on" should not be interpreted as referring to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0245] In the accompanying drawings, similar components or features may have the same reference number. In addition, various components of the same type may be distinguished by following the reference number with a dash and a second reference number that distinguishes between similar components. If only the first reference number is used in the specification, the description may apply to any of the similar components having the same first reference number regardless of the second reference number, or other subsequent reference numbers.

[0246] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or that fall within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration" and does not mean "better than" or "better than other examples." This detailed description includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0247] The description herein is provided to enable those skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the universal principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment UE, comprising: receiving, from a network device, a downlink control information message indicating an explicit time-domain resource allocation for a first repetition of a downlink data transmission; receiving, from the network device, the first repetition of the downlink data transmission and one or more additional repetitions of the downlink data transmission in accordance with the explicit time-domain resource allocation and one or more implicit time-domain resource allocations, the one or more implicit time-domain resource allocations being used for the one or more additional repetitions of the downlink data transmission and being based at least in part on the explicit time-domain resource allocation; generating a hybrid automatic repeat request acknowledgment codebook based at least in part on the explicit time-domain resource allocation and the first repetition of the downlink data transmission and the one or more additional repetitions of the downlink data transmission; and A message is transmitted to the network device based at least in part on the hybrid automatic repeat request acknowledgment codebook.

2. The method of claim 1, wherein the explicit time-domain resource allocation and the one or more implicit time-domain resource allocations are within a single time slot.

3. The method of claim 1, wherein the explicit time-domain resource allocation temporally precedes the one or more implicit time-domain resource allocations.

4. The method of claim 1, wherein the one or more implicit time-domain resource allocations are determined based at least in part on a number of repetitions for the downlink data transmission.

5. The method of claim 4, further comprising: An indication of the number of repetitions is received in a downlink control information message, a radio resource control configuration, or a combination thereof.

6. The method of claim 1, further comprising: A repetition number for the downlink data transmission is identified, wherein determining the one or more implicit time-domain resource allocations is based at least in part on the repetition number.

7. The method of claim 6, wherein the number of repetitions is identified based at least in part on the downlink control information message, a radio resource control configuration, or a combination thereof.

8. The method of claim 6, wherein the number of repetitions comprises a nominal number of repetitions, the method further comprising: An actual repetition number is determined based at least in part on the nominal repetition number and a slot boundary, an uplink / downlink switching point, or a combination thereof, wherein determining the one or more implicit time-domain resource allocations is based at least in part on the actual repetition number.

9. The method of claim 1, wherein the first repetition of the downlink data transmission and each of the one or more additional repetitions of the downlink data transmission comprise a same length.

10. The method of claim 1, wherein the downlink control information message indicates the explicit time domain resource allocation according to a start symbol, an allocation length, a start and length indicator, a mapping type, a slot offset, or a combination thereof.

11. The method of claim 1 , wherein for a first downlink data opportunity of the hybrid automatic repeat request acknowledgment codebook, the message comprises a positive acknowledgment or negative acknowledgment indication for the downlink data transmission based at least in part on the explicit time domain resource allocation.

12. The method of claim 1 , wherein for one or more additional downlink data opportunities of the hybrid automatic repeat request acknowledgment codebook, the message includes one or more dummy negative acknowledgment indications for the downlink data transmission based at least in part on the absence of an explicit time-domain resource allocation corresponding to the one or more additional downlink data opportunities.

13. The method of claim 1, wherein generating the hybrid automatic repeat request acknowledgement codebook comprises: For a first downlink data opportunity of the hybrid automatic repeat request acknowledgment codebook, a positive acknowledgment or negative acknowledgment indication for the downlink data transmission is inserted based at least in part on the explicit time domain resource allocation and the receiving.

14. The method of claim 13, wherein generating the hybrid automatic repeat request acknowledgement codebook further comprises: For one or more additional downlink data opportunities of the hybrid automatic repeat request acknowledgment codebook, one or more dummy negative acknowledgment indications for the downlink data transmission are inserted based at least in part on the absence of explicit time-domain resource allocations corresponding to the one or more additional downlink data opportunities.

15. The method of claim 13, wherein the message is transmitted in a first time slot for feedback, and generating the hybrid automatic repeat request acknowledgement codebook further comprises: For one or more additional downlink data opportunities of the hybrid automatic repeat request acknowledgment codebook, one or more dummy negative acknowledgment indications for the downlink data transmission are inserted based at least in part on an additional explicit time domain resource allocation indication corresponding to at least one of the one or more additional downlink data opportunities and a second time slot for feedback that is different from the first time slot for feedback.

16. The method of claim 1 , wherein a size of the hybrid automatic repeat request acknowledgment codebook is based at least in part on a plurality of time domain resource allocation candidates, wherein the explicit time domain resource allocation corresponds to a candidate among the plurality of time domain resource allocation candidates, and a downlink data opportunity of the hybrid automatic repeat request acknowledgment codebook is based at least in part on the plurality of time domain resource allocation candidates.

17. The method of claim 16, further comprising: In the case where a codeword of the time domain resource allocation candidate is configured for uplink, all codewords of the time domain resource allocation candidate are configured for uplink, at most one consecutive codeword of the time domain resource allocation candidate is configured for downlink, or a combination thereof, the time domain resource allocation candidate is suppressed from being included in the multiple time domain resource allocation candidates.

18. The method of claim 16, wherein the number of repetitions for the downlink data transmission is semi-statically configured, the method further comprising: The plurality of time domain resource allocation candidates are determined based at least in part on the number of repetitions to cover both explicit time domain resource allocation candidates and corresponding implicit time domain resource allocation candidates.

19. The method of claim 1, wherein the hybrid automatic repeat request acknowledgment codebook comprises a semi-static codebook, a type 1 codebook, or a combination thereof.

20. The method of claim 1, wherein: No symbols in the explicit time domain resource allocation are configured for uplink.

21. The method of claim 1, wherein: The explicit time domain resource allocation and the one or more implicit time domain resource allocations span multiple time slots; as well as The feedback timing indicator corresponds to a last time slot in time of the plurality of time slots, wherein the message is transmitted based at least in part on the feedback timing indicator.

22. The method of claim 21, wherein: The explicit time-domain resource allocation spans the plurality of time slots; and The first repetition of the downlink data transmission comprises a first nominal repetition, the method further comprising: A first actual repetition of the downlink data transmission in a first time slot of the plurality of time slots and a second actual repetition of the downlink data transmission in a second time slot of the plurality of time slots that is subsequent to the first time slot are determined based at least in part on the first nominal repetition, wherein the second time slot includes the last time slot of the plurality of time slots.

23. The method of claim 21, further comprising: A plurality of time domain resource allocation candidates are modified based at least in part on the time domain resource allocation candidates crossing a time slot boundary, wherein the hybrid automatic repeat request acknowledgment codebook is based at least in part on the modified plurality of time domain resource allocation candidates.

24. The method of claim 1, wherein the explicit time-domain resource allocation is temporally subsequent to the one or more implicit time-domain resource allocations.

25. The method of claim 1, wherein the explicit time-domain resource allocation and the one or more implicit time-domain resource allocations are contiguous in time.

26. A method for wireless communication at a network device, comprising: transmitting a downlink control information message indicating an explicit time domain resource allocation for a first repetition of downlink data transmission to a user equipment UE; transmitting the first repetition of the downlink data transmission to the UE in accordance with the explicit time-domain resource allocation and transmitting one or more additional repetitions of the downlink data transmission to the UE in accordance with one or more implicit time-domain resource allocations, wherein the one or more implicit time-domain resource allocations are based at least in part on the explicit time-domain resource allocation; as well as receiving, from the UE, a message based at least in part on the explicit time-domain resource allocation and a hybrid automatic repeat request acknowledgment codebook based at least in part on the explicit time-domain resource allocation and the first repetition of the downlink data transmission and the one or more additional repetitions of the downlink data transmission.

27. The method of claim 26, further comprising: The explicit time domain resource allocation and the one or more implicit time domain resource allocations are scheduled such that the explicit time domain resource allocation and the one or more implicit time domain resource allocations are within a single time slot.

28. The method of claim 26, further comprising: An indication of a repetition number for the downlink data transmission is transmitted to the UE in the downlink control information message, a radio resource control configuration, or a combination thereof, wherein the one or more implicit time-domain resource allocations are further based at least in part on the repetition number.

29. The method of claim 28, wherein said indication of said number of repetitions indicates a nominal number of repetitions, said method further comprising: An actual repetition number is determined based at least in part on the nominal repetition number and a slot boundary, an uplink / downlink switching point, or a combination thereof, wherein the one or more implicit time-domain resource allocations are further based at least in part on the actual repetition number.

30. The method of claim 26, wherein the hybrid automatic repeat request acknowledgment codebook comprises a positive acknowledgment or negative acknowledgment indication for the downlink data transmission based at least in part on the explicit time-domain resource allocation and whether the UE successfully received the downlink data transmission.

31. The method of claim 26, further comprising: The explicit time-domain resource allocation is scheduled such that no symbols in the explicit time-domain resource allocation are configured for uplink.

32. The method of claim 26, further comprising: scheduling the explicit time domain resource allocation and the one or more implicit time domain resource allocations such that the explicit time domain resource allocation and the one or more implicit time domain resource allocations span a plurality of time slots; as well as A feedback timing indicator corresponding to a last time slot in the plurality of time slots is transmitted in the downlink control information message, wherein the message is received based at least in part on the feedback timing indicator.

33. An apparatus for wireless communication at a user equipment (UE), comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to: receiving, from a network device, a downlink control information message indicating an explicit time-domain resource allocation for a first repetition of a downlink data transmission; receiving, from the network device, the first repetition of the downlink data transmission and the one or more additional repetitions of the downlink data transmission in accordance with the explicit time-domain resource allocation and one or more implicit time-domain resource allocations, the one or more implicit time-domain resource allocations being used for the one or more additional repetitions of the downlink data transmission and being based at least in part on the explicit time-domain resource allocation; generating a hybrid automatic repeat request acknowledgment codebook based at least in part on the explicit time-domain resource allocation and the first repetition of the downlink data transmission and the one or more additional repetitions of the downlink data transmission; and A message is transmitted to the network device based at least in part on the hybrid automatic repeat request acknowledgment codebook.

34. The apparatus of claim 33, further comprising: Instructions stored in the memory, which are executable by the processor to cause the apparatus to perform a method as claimed in any one of claims 2 to 25.

35. An apparatus for wireless communication at a network device, comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to: transmitting a downlink control information message indicating an explicit time domain resource allocation for a first repetition of downlink data transmission to a user equipment UE; transmitting the first repetition of the downlink data transmission to the UE in accordance with the explicit time-domain resource allocation and transmitting one or more additional repetitions of the downlink data transmission to the UE in accordance with one or more implicit time-domain resource allocations, wherein the one or more implicit time-domain resource allocations are based at least in part on the explicit time-domain resource allocation; as well as receiving, from the UE, a message based at least in part on the explicit time-domain resource allocation and a hybrid automatic repeat request acknowledgment codebook based at least in part on the explicit time-domain resource allocation and the first repetition of the downlink data transmission and the one or more additional repetitions of the downlink data transmission.

36. The apparatus of claim 35, further comprising: Instructions stored in the memory, which are executable by the processor to cause the apparatus to perform a method as claimed in any one of claims 27 to 32.

37. A non-transitory computer readable medium storing code for wireless communication at a user equipment (UE), the code comprising instructions executable by a processor to: receiving, from a network device, a downlink control information message indicating an explicit time-domain resource allocation for a first repetition of a downlink data transmission; receiving, from the network device, the first repetition of the downlink data transmission and the one or more additional repetitions of the downlink data transmission in accordance with the explicit time-domain resource allocation and one or more implicit time-domain resource allocations, the one or more implicit time-domain resource allocations being used for the one or more additional repetitions of the downlink data transmission and being based at least in part on the explicit time-domain resource allocation; generating a hybrid automatic repeat request acknowledgment codebook based at least in part on the explicit time-domain resource allocation and the first repetition of the downlink data transmission and the one or more additional repetitions of the downlink data transmission; and A message is transmitted to the network device based at least in part on the hybrid automatic repeat request acknowledgment codebook.

38. The non-transitory computer-readable medium of claim 37, wherein the instructions are executable by the processor of the UE to further cause the processor to perform the method of any one of claims 2-25.

39. A non-transitory computer-readable medium storing code for wireless communication at a network device, the code comprising instructions executable by a processor to: transmitting a downlink control information message indicating an explicit time domain resource allocation for a first repetition of downlink data transmission to a user equipment UE; transmitting the first repetition of the downlink data transmission to the UE in accordance with the explicit time-domain resource allocation and transmitting one or more additional repetitions of the downlink data transmission to the UE in accordance with one or more implicit time-domain resource allocations, wherein the one or more implicit time-domain resource allocations are based at least in part on the explicit time-domain resource allocation; and receiving, from the UE, a message based at least in part on the explicit time-domain resource allocation and a hybrid automatic repeat request acknowledgment codebook based at least in part on the explicit time-domain resource allocation and the first repetition of the downlink data transmission and the one or more additional repetitions of the downlink data transmission.

40. The non-transitory computer readable medium of claim 39, wherein the instructions are executable by the processor of the network device to further cause the processor to perform the method of any of claims 27-32.

Images