Patent Description:
3GPP draft RP-<NUM> discloses MAC corrections for NR operating in shared spectrum channel access. <CIT> discloses a method for early termination of an ongoing uplink transmission based on implicit HARQ-ACK.

The invention is defined by a method according to claim <NUM>, an apparatus for wireless communication according to claim <NUM> and a computer program according to claim <NUM>. Further details are defined by claims <NUM>-<NUM>.

When a base station configures a UE to transmit uplink data in a physical uplink shared channel (PUSCH), the base station may indicate the UE to send repetitions of its uplink data for coverage enhancement and to improve data reliability. Typically, the UE may be configured to send up to sixteen repetitions of a PUSCH transmission in response to a dynamic grant or up to eight repetitions in response to a configured grant. However, the number of repetitions may be increased above sixteen, for example, to further extend PUSCH coverage for enhanced mobile broadband (eMBB)/voice over Internet Protocol (VoIP), to support low capability UEs with extended coverage, or in other cases. Therefore, the UE may send numerous repetitions of its uplink data in order for the base station to successfully decode the uplink data.

While in some cases, the base station may successfully decode the uplink data after receiving all configured repetitions (e.g., when the UE is located a significant distance away from the base station such as at a cell edge), in other cases the base station may successfully decode the data only after receiving some of the configured repetitions. For instance, even if the base station configures the UE to transmit eight PUSCH repetitions, the base station may successfully decode the data after receiving only four PUSCH repetitions (or some other number less than <NUM>) if the UE is not at the cell edge or otherwise in a geometry with high signal quality.

Moreover, while asynchronous hybrid automatic repeat request (HARQ) acknowledgment (ACK) is supported in NR in response to downlink transmissions (e.g., HARQ-ACK from UE to base station), the base station does not conventionally provide HARQ-ACK feedback in response to PUSCH transmissions (e.g., HARQ-ACK from base station to UE). Instead, depending on whether the base station successfully decodes or fails to decode uplink data, the base station may provide downlink control information (DCI) to the UE indicating whether the UE is to retransmit the uplink data in a subsequent PUSCH transmission. In particular, if the base station fails to decode uplink data, the base station may provide DCI to the UE indicating the UE to retransmit the uplink data, while if the base station successfully decodes uplink data, the base station does not provide such DCI, and the UE assumes the data was successfully received after determining the base station has not provided such DCI within a certain period of time.

Thus, even if the base station has already decoded uplink data in a prior PUSCH transmission or repetition, the UE may not determine the base station has successfully decoded the data until the period of time for receiving the DCI has elapsed, and so the UE may continue to send unnecessary PUSCH repetitions in the interim. As a result, the UE may waste transmission power and PUSCH resources on inefficient repetitions. Therefore, it would be helpful to allow the UE to perform early termination of an ongoing PUSCH transmission (e.g., terminate inefficient repetitions) in order to save UE power and enhance resource efficiency.

Accordingly, aspects are provided for terminating repetitions of a PUSCH transmission. In a first example, the base station may provide a DCI in PDCCH that explicitly indicates successful decoding of a PUSCH transmission. The indication may be provided using configured bit values for various parameters of DCI. For instance, the DCI may have a DCI format <NUM>-<NUM> or <NUM>-<NUM> including a frequency domain resource assignment (FDRA) field or a MCS field set to all ones, and all remaining bits in one or more other parameters of the DCI (e.g., time domain resource assignment (TDRA), frequency hopping flag, etc.) set to zero. The UE may receive the PDCCH carrying the DCI in a control resource set (CORESET), and the DCI may indicate the UE to terminate subsequent repetitions of the PUSCH transmission after a time gap following the CORESET (e.g., no later than T symbols after a last symbol of the CORESET). In a second example, the base station may provide a DCI in PDCCH that implicitly indicates successful decoding of a first PUSCH transmission. For instance, the base station may provide a DCI to the UE scheduling a second PUSCH transmission in overlapping time resources with the first PUSCH transmission. The UE may receive the PDCCH carrying the DCI in a CORESET, and the DCI may indicate the UE to terminate subsequent repetitions of the first PUSCH transmission after a time gap following the CORESET (e.g., no later than T symbols after a last symbol of the CORESET). The DCI may also indicate the UE to transmit the second PUSCH transmission in an uplink slot after the time gap following the CORESET. In either the first or second example, the time gap (e.g., the value of T) may be a function of PDCCH subcarrier spacing (SCS) and PUSCH SCS, PUSCH processing capability, whether the first symbol of a PUSCH resource allocation is reserved for a demodulation reference signal (DMRS), and a PUSCH preparation time. Additionally, the time gap (T) may include an additional number of symbols Δ for UE processing margin (e.g. T = T + Δ), which duration may be a function of the PDCCH SCS and PUSCH SCS. For instance, the duration of the additional number of symbols Δ may be a function of the smaller SCS between the PDCCH SCS and PUSCH SCS.

The wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations <NUM>, user equipment(s) (UE) <NUM>, an Evolved Packet Core (EPC) <NUM>, and another core network <NUM> (e.g., a <NUM> Core (5GC)).

The base stations <NUM> configured for <NUM> Long Term Evolution (LTE) (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC <NUM> through first backhaul links <NUM> (e.g., S1 interface). The base stations <NUM> configured for <NUM> New Radio (NR) (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network <NUM> through second backhaul links <NUM>. In addition to other functions, the base stations <NUM> may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages.

The base stations <NUM> / UEs <NUM> may use spectrum up to Ymegahertz (MHz) (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction.

The wireless communications system may further include a Wi-Fi access point (AP) <NUM> in communication with Wi-Fi stations (STAs) <NUM> via communication links <NUM>, e.g., in a <NUM> gigahertz (GHz) unlicensed frequency spectrum or the like.

The EPC <NUM> may include a Mobility Management Entity (MME) <NUM>, other MMEs <NUM>, a Serving Gateway <NUM>, an MBMS Gateway <NUM>, a Broadcast Multicast Service Center (BM-SC) <NUM>, and a Packet Data Network (PDN) Gateway <NUM>.

Generally, the AMF <NUM> provides Quality of Service (QoS) flow and session management. All user IP packets are transferred through the UPF <NUM>. The IP Services <NUM> may include the Internet, an intranet, an IMS, a Packet Switch (PS) Streaming Service, and/or other IP services.

Although the present disclosure may focus on <NUM> NR, the concepts and various aspects described herein may be applicable to other similar areas, such as LTE, LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile communications (GSM), or other wireless/radio access technologies.

Referring again to <FIG>, in certain aspects, the UE <NUM> may include a physical uplink shared channel (PUSCH) termination component <NUM> that is configured to obtain information configuring an uplink data transmission and a repetition of the uplink data transmission; send the uplink data transmission to a base station; and terminate the repetition of the uplink data transmission in response to reception of downlink information in a downlink control channel, where the repetition is terminated after a time gap following a CORESET where the downlink control channel is received.

In the examples provided by <FIG>, the <NUM> NR frame structure is assumed to be TDD, with subframe <NUM> being configured with slot format <NUM> (with mostly DL), where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe <NUM> being configured with slot format <NUM> (with mostly UL).

A frame, e.g., of <NUM> milliseconds (ms), may be divided into <NUM> equally sized subframes (<NUM>). The symbols on DL may be cyclic prefix (CP) orthogonal frequency-division multiplexing (OFDM) (CP-OFDM) symbols. For slot configuration <NUM>, different numerologies µ <NUM> to <NUM> allow for <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> slots, respectively, per subframe. The subcarrier spacing may be equal to <NUM>µ * <NUM> kilohertz (kHz), where µ is the numerology <NUM> to <NUM>. <FIG> provide an example of slot configuration <NUM> with <NUM> symbols per slot and numerology µ=<NUM> with <NUM> slots per subframe. The slot duration is <NUM>, the subcarrier spacing is <NUM>, and the symbol duration is approximately <NUM>. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see <FIG>) that are frequency division multiplexed. Each BWP may have a particular numerology.

A PDCCH within one BWP may be referred to as a control resource set (CORESET). Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS)/PBCH block (also referred to as SS block (SSB)).

The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) / non-acknowledgement (NACK) feedback.

The memory <NUM> maybe referred to as a computer-readable medium.

At least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM> may be configured to perform aspects in connection with PUSCH termination component <NUM> of <FIG>.

When a base station configures a UE to transmit uplink data in PUSCH, the base station may indicate the UE to send repetitions of its uplink data for coverage enhancement and to improve data reliability. For example, the base station may transmit a PUSCH configuration (e.g., pusch-Config or another name) via dedicated RRC signaling to the UE which may indicate a number of repetitions of uplink data which the UE may transmit on PUSCH in response to a dynamic grant (e.g., in a parameter pusch-AggregationFactor or another name). In another example, the base station may transmit a configured grant configuration to the UE (e.g., configuredGrantConfig or another name) which may indicate a number of repetitions of uplink data that the UE may transmit on PUSCH in response to a configured grant (e.g., in a parameter repK or another name). Typically, the UE may be configured to send up to sixteen repetitions of a PUSCH transmission in response to a dynamic grant or up to eight repetitions in response to a configured grant. However, the number of repetitions may be increased above sixteen, for example, to further extend PUSCH coverage for enhanced mobile broadband (eMBB)/voice over Internet Protocol (VoIP), to support low capability UEs with extended coverage, or in other cases. For instance, in rural or some urban areas, downlink channels typically include higher signal quality than uplink channels (e.g., by approximately <NUM>-<NUM> dB), and therefore PUSCH repetitions may serve to compensate for this degradation in signal quality.

Therefore, the UE may send numerous repetitions of its uplink data in order for the base station to successfully decode the uplink data. While in some cases, the base station may successfully decode the uplink data after receiving all configured repetitions (e.g., when the UE is located a significant distance away from the base station such as at a cell edge), in other cases the base station may successfully decode the data only after receiving some of the configured repetitions. For instance, even if the base station configures the UE to transmit eight PUSCH repetitions, the base station may successfully decode the data after receiving only four PUSCH repetitions (or some other number less than <NUM>) if the UE is not at the cell edge or otherwise in a geometry with high signal quality.

However, while asynchronous hybrid automatic repeat request (HARQ) acknowledgment (ACK) is supported in NR in response to downlink transmissions (e.g., HARQ-ACK from UE to base station), the base station does not conventionally provide HARQ-ACK feedback in response to PUSCH transmissions (e.g., HARQ-ACK from base station to UE). Instead, depending on whether the base station successfully decodes or fails to decode uplink data, the base station may provide downlink control information (DCI) to the UE indicating whether the UE is to retransmit the uplink data in a subsequent PUSCH transmission. For example, if the base station fails to decode uplink data, the base station may provide DCI to the UE indicating the UE to retransmit the uplink data, while if the base station successfully decodes uplink data, the base station does not provide such DCI, and the UE assumes the data was successfully received after determining the base station has not provided such DCI within a certain period of time. Thus, even if the base station has already decoded uplink data in a prior PUSCH transmission or repetition, the UE may not determine the base station has successfully decoded the data until the period of time for receiving the DCI has elapsed, and so the UE may continue to send unnecessary PUSCH repetitions in the interim. As a result, the UE may waste transmission power and PUSCH resources on inefficient repetitions. Therefore, it would be helpful to allow the UE to perform early termination of an ongoing PUSCH transmission (e.g., terminate inefficient repetitions) in order to save UE power and enhance resource efficiency.

In LTE enhanced machine type communication (eMTC), the UE may terminate ongoing uplink transmissions in full duplex (FD) frequency division duplex (FD-FDD) and time division duplex (TDD) deployments in response to DCI from the base station. For example, the base station may provide DCI to the UE in a MTC physical downlink control channel (MPDCCH), and the DCI may explicitly or implicitly indicate the base station has successfully decoded a prior uplink transmission. The UE may then terminate the ongoing PUSCH transmission in response to the DCI.

The indication may be explicit (serve as an effective HARQ-ACK) when the DCI includes one of two DCI formats including a certain configuration of bit values in specified DCI parameters. For instance, to explicitly acknowledge that the base station has successfully decoded the uplink transmission from the UE, the base station may provide a DCI to the UE having DCI format <NUM>-0A including a resource block assignment field set to all ones and all remaining bits (except a flag format <NUM>-0A/format <NUM>-1A differentiation and DCI subframe repetition number) set to zero. Alternatively, the base station may provide a DCI to the UE having DCI format <NUM>-0B including a modulation and coding scheme (MCS) field set to all ones and all remaining bits (except a flag format <NUM>-0B/format <NUM>-1B differentiation and DCI subframe repetition number) set to zero. On the other hand, the indication may be implicit when the base station schedules a new PUSCH transport block overlapping in time with the previously scheduled PUSCH transmission or repetitions. For instance, to implicitly acknowledge that the base station has successfully decoded the uplink transmission from the UE, the base station may provide a DCI to the UE scheduling a new PUSCH transport block in overlapping time resources.

When the UE receives in subframe N a DCI in MPDCCH, which explicitly indicates the base station has successfully decoded a prior uplink transmission using DCI formats <NUM>-0A or <NUM>-0B as described above, the UE may terminate or stop transmitting data on PUSCH no later than subframe N + k, where k is a number of subframes. For example, k may be <NUM> subframes for FDD deployments, or k may be a function of a subframe number (or slot number) and a TDD uplink/downlink configuration for TDD deployments (e.g., k = <NUM>, <NUM>, <NUM>, or <NUM>). The UE may terminate the PUSCH transmission earlier than subframe N + k in response to early decoding of the DCI in MPDCCH. Similarly, when the UE receives in subframe M a DCI in MPDCCH, which implicitly indicates the base station has successfully decoded a prior uplink transmission by scheduling a new PUSCH transmission in overlapping resources, the UE may terminate or stop transmitting data on PUSCH no later than subframe M + k. The UE may terminate the PUSCH transmission earlier than subframe M + k, for example, in response to early decoding of the DCI in MPDCCH. Additionally, the UE may transmit the new PUSCH transmission in response to the DCI beginning in subframe M + k.

<FIG> illustrates an example <NUM> in which the UE terminates a PUSCH transmission <NUM> in response to a DCI explicitly indicating successful decoding of the PUSCH transmission. The base station initially provides DCI <NUM> in MPDCCH to the UE scheduling the PUSCH transmission, in response to which the UE begins to transmit its uplink data to the base station in PUSCH transmission <NUM>. While the UE is transmitting its uplink data in one or more repetitions, the base station may successfully decode the PUSCH transmission. Moreover, the base station may determine that the UE does not have additional data to send in its transmission buffer, e.g., in response to a buffer status report from the UE or in some other manner. Therefore, the base station may provide DCI <NUM> to the UE explicitly indicating that the PUSCH transmission was successfully decoded. For example, DCI <NUM> may have a DCI format <NUM>-0A or <NUM>-0B with configured bit values as described above that does not schedule a new PUSCH transmission. The UE may then terminate its PUSCH transmission in response to DCI <NUM>. For example, assuming the UE receives DCI <NUM> in subframe N, the UE may terminate the PUSCH transmission no later than subframe N + k. For instance, the UE may stop sending repetitions of its uplink data beginning at subframe N + k, as represented by terminated PUSCH transmission <NUM>.

Similarly, <FIG> illustrates an example <NUM> in which the UE terminates a first PUSCH transmission <NUM> in response to a DCI implicitly indicating successful decoding of the first PUSCH transmission and scheduling a second PUSCH transmission <NUM>. The base station initially provides DCI <NUM> in MPDCCH to the UE scheduling the first PUSCH transmission, in response to which the UE begins to transmit its uplink data to the base station in first PUSCH transmission <NUM>. While the UE is transmitting its uplink data in one or more repetitions, the base station may successfully decode the first PUSCH transmission. Moreover, the base station may determine that the UE has additional data to send in its transmission buffer, e.g., in response to a buffer status report from the UE or in some other manner. Therefore, the UE may provide DCI <NUM> to the UE implicitly indicating that the first PUSCH transmission was successfully decoded. For example, DCI <NUM> may schedule second PUSCH transmission <NUM> in overlapping time resources with first PUSCH transmission <NUM>. The UE may then terminate its first PUSCH transmission and transmit its second PUSCH transmission in response to DCI <NUM>. For example, assuming the UE receives DCI <NUM> in subframe M, the UE may terminate the first PUSCH transmission no later than subframe M + k and begin transmitting the second PUSCH transmission starting in subframe M + k. For instance, the UE may stop sending repetitions of its first uplink data beginning at subframe M + k, as represented by terminated PUSCH transmission <NUM>, as well as start sending its second uplink data beginning at subframe M + k.

However, while LTE eMTC may support early termination of PUSCH transmissions based on explicit or implicit feedback as described above, the timelines associated with such terminated PUSCH transmissions (subframes N + k and M + k) may not be maintainable in NR. For example, NR supports dynamic TDD configurations, in which the base station may dynamically change the symbol or slot format (e.g., the arrangement of downlink (DL) and uplink (UL) symbols or slots in a subframe), in contrast to the static TDD configurations supported in LTE (e.g., seven TDD UL/DL configurations <NUM>-<NUM>). Thus, attempts to terminate PUSCH transmissions k subframes after reception of DCI may fail due to conflicts with dynamic UL/DL configurations. Moreover, NR supports different numerologies between the PDCCH and PUSCH (e.g., the PDCCH and PUSCH may include different subcarrier spacing (SCS)), and thus different symbol durations between PDCCH and PUSCH, in contrast to LTE. Therefore, the dynamic values of k based on a slot number or TDD UL/DL configuration in TDD deployments, and the fixed value of k in FDD deployments, may not be suitable if the DCI and the terminated PUSCH transmission are associated with different SCS or symbol durations. Furthermore, NR supports multiple PUSCH processing capabilities for UEs, in contrast to LTE. For example, after receiving a PDCCH transmission, a UE with PUSCH processing capability <NUM> may begin sending a PUSCH transmission in approximately half the amount of time compared to a UE with PUSCH processing capability <NUM> (e.g., <NUM> symbols after receiving DCI for capability <NUM>, as opposed to <NUM> symbols after receiving DCI for capability <NUM>, assuming <NUM> SCS). Thus, terminating PUSCH transmissions k subframes after reception of DCI may be inefficient if the UE has an advanced PUSCH processing capability.

Accordingly, aspects of the present disclosure provide a timeline for terminating PUSCH transmissions which accounts for such timing considerations between NR and LTE. In a first example, the base station may provide a DCI in PDCCH that explicitly indicates successful decoding of a PUSCH transmission. For instance, the DCI may have a DCI format <NUM>-<NUM> or <NUM>-<NUM> including a frequency domain resource assignment (FDRA) field or a MCS field set to all ones, and all remaining bits in one or more other parameters of the DCI (e.g., time domain resource assignment (TDRA), frequency hopping flag, etc.) set to zero. The UE may receive the PDCCH carrying the DCI in a control resource set (CORESET), and the DCI may indicate the UE to terminate subsequent repetitions of the PUSCH transmission after a time gap following the CORESET (e.g., no later than T symbols after a last symbol of the CORESET). In a second example, the base station may provide a DCI in PDCCH that implicitly indicates successful decoding of a first PUSCH transmission. For instance, the base station may provide a DCI to the UE scheduling a second PUSCH transmission in overlapping time resources with the first PUSCH transmission. The UE may receive the PDCCH carrying the DCI in a CORESET, and the DCI may indicate the UE to terminate subsequent repetitions of the first PUSCH transmission after a time gap following the CORESET (e.g., no later than T symbols after a last symbol of the CORESET). The DCI may also indicate the UE to transmit the second PUSCH transmission in an uplink slot after the time gap following the CORESET. In either the first or second example, the time gap (e.g., the value of T) may be a function of PDCCH SCS and PUSCH SCS, PUSCH processing capability, whether the first symbol of a PUSCH resource allocation is reserved for a demodulation reference signal (DMRS), and a PUSCH preparation time. Additionally, the time gap (T) may include an additional number of symbols Δ for UE processing margin (e.g. T = T + Δ), which duration may be a function of the PDCCH SCS and PUSCH SCS. For instance, the duration of the additional number of symbols Δ may be a function of the smaller SCS between the PDCCH SCS and PUSCH SCS.

Thus, termination of PUSCH transmissions based on a timeline accounting for the different timing considerations of NR may be achieved. For example, here, the termination of PUSCH repetitions is with respect to a CORESET symbol timing reference (a last symbol of a CORESET including DCI), rather than with respect to the DCI subframe timing reference of LTE (an end of a subframe including DCI). Since the CORESET symbol timing reference is more configurable than the DCI subframe timing reference (the base station may configure the last symbol of a CORESET to be any symbol of a slot, in contrast to the end of a subframe which is fixed), more flexibility in PUSCH termination starting times may be achieved. Moreover, since the base station may configure different SCS, a dynamic, CORESET symbol timing reference as opposed to a fixed, DCI subframe timing reference may better account for the different symbol or slot durations resulting from different SCS. Furthermore, as the time gap (T) may also be a function of SCS, PUSCH processing capabilities, or other timing configurations (e.g., DMRS), various PUSCH termination starting times may be obtained.

The time gap (T) may be a function of one or more of the following example parameters. In one example, T may be a function of a subcarrier spacing of the PDCCH carrying the DCI and a subcarrier spacing of the PUSCH. For example, T may be one value if the SCS of the DCI and the PUSCH transmission are both <NUM>, T may be another value if the SCS of the DCI and the PUSCH transmission are both <NUM>, T may be another value if the SCS of the DCI is <NUM> and the SCS of the PUSCH transmission is <NUM>, etc. Similarly, T may be a function of a subcarrier spacing of an active DL BWP over which the PDCCH is monitored and a subcarrier spacing of an active UL BWP over which the PUSCH is transmitted. For example, T may be one value if the SCS of the DL BWP carrying the DCI and the UL BWP carrying the PUSCH transmission are both <NUM>, T may be another value if the SCS of the DL BWP and the UL BWP are both <NUM>, T may be another value if the SCS of the DL ZWP is <NUM> and the SCS of the UL BWP is <NUM>, etc. In another example, T may be a function of a PUSCH processing capability of the UE. For example, T may be one value for UE PUSCH processing capability <NUM> and another value for UE PUSCH processing capability <NUM>. In a further example, T may be a function of a configuration indicating whether a first symbol of a PUSCH allocation consists only of DMRS. For example, T may be one value if the base station configures the first symbol of a slot of the PUSCH transmission to include only DMRS, while T may be another value if the base station configures the first symbol of a slot of the PUSCH transmission to include only PUSCH data, or PUSCH data and DMRS. In an additional example, T may be a function of a UE PUSCH preparation time Tproc,<NUM>, where Tproc,<NUM> is a function of PUSCH preparation time N<NUM>, where N<NUM> is based on a numerology µ for UE processing capability <NUM>, where µ corresponds to the one of (µDL, µUL) resulting with the largest Tproc,<NUM> (the smaller value or SCS between µDL, µUL), where the µDL corresponds to the subcarrier spacing at with the PDCCH carrying the DCI scheduling the PUSCH was transmitted, and where µUL corresponds to the subcarrier spacing at which the PUSCH is to be transmitted. For example, the value of T may be different for different values of N<NUM>.

In addition to being a function of one or more of the aforementioned example parameters, the time gap (T) may be increased for additional UE processing margin. For instance, an additional number of symbols (Δ) may be added to T for low capability UEs with large PUSCH preparation times, or for UEs transmitting simultaneously to multiple base stations (e.g., a source base station and a target base station during a handover). In one example, the value of Δ may be fixed. For instance, Δ may be preconfigured to a value of <NUM>, <NUM>, <NUM> or some other number. In another example, the value of Δ may be indicated to the UE, e.g., within a PUSCH configuration. For instance, when the base station provides a PUSCH configuration to the UE (e.g., pusch-Config), the PUSCH configuration may indicate a configured value of Δ (e.g., <NUM>, <NUM>, <NUM> or some other number of symbols). In a further example, the value of Δ may be dependent on UE capability. For instance, Δ may be one value if the UE is capable of PUSCH processing capability <NUM>, while Δ may be another value if the UE is only capable of PUSCH processing capability <NUM>. In either example, the duration of Δ may be a function of the SCS of the PDCCH carrying the DCI and the SCS of the PUSCH carrying the uplink transmission (e.g., the smaller SCS between the PDCCH SCS and the PUSCH SCS). For instance, the total length in time of Δ may be one value if the smaller SCS is <NUM>, the total length in time of Δ may be another value if the smaller SCS is <NUM>, etc..

<FIG> illustrates an example <NUM> of a time gap <NUM> following a CORESET <NUM> where a PDCCH carrying DCI is received. The UE may receive CORESET <NUM> in a slot <NUM> (slot N). In the illustrated example, the time gap <NUM> is T = <NUM> symbols, although in other examples the time gap may be a different number of symbols depending on SCS, UE capability, or other parameters as described above. Moreover, in this example, a last symbol <NUM> of CORESET <NUM> is the second symbol of slot <NUM> (symbol <NUM>), although in other examples the last symbol <NUM> of CORESET <NUM> may be a different symbol in slot <NUM>. Thus, in the illustrated example, the UE may terminate subsequent PUSCH repetitions of a prior PUSCH transmission no later than <NUM> symbols after the second symbol of slot <NUM>. That is, the UE may stop transmitting repetitions of the PUSCH transmission at latest starting from symbol <NUM> of subsequent slot <NUM> (slot N + <NUM>). Similarly, if the DCI schedules a second PUSCH transmission, the UE may begin transmitting the second PUSCH transmission after the time gap <NUM>. For example, the UE may begin transmitting the second PUSCH transmission starting from symbol <NUM> of subsequent slot <NUM> in response to the DCI.

<FIG> illustrates another example <NUM> of a time gap <NUM> following a CORESET <NUM> where a PDCCH carrying DCI is received. Similar to the example of <FIG>, the UE may receive CORESET <NUM> in a slot <NUM> (slot N). In the illustrated example, the time gap <NUM> is T = <NUM> symbols, although in other examples the time gap may be a different number of symbols depending on SCS, UE capability, or other parameters as described above. Moreover, similar to the example of <FIG>, here a last symbol <NUM> of CORESET <NUM> is the second symbol of slot <NUM> (symbol <NUM>), although in other examples the last symbol <NUM> of CORESET <NUM> may be a different symbol in slot <NUM>. However, unlike the example of <FIG>, here the time gap <NUM> ends in the middle of a slot, in this case, next slot <NUM> (slot N + <NUM>). Thus, if the UE were to terminate subsequent PUSCH repetitions after the time gap following the CORESET, the termination would begin in the middle of a slot. To prevent such partial slot terminations, the UE may delay the termination to the beginning of a subsequent slot <NUM> (slot N + <NUM>), such as illustrated in <FIG>. As a result, the UE may stop transmitting repetitions of the PUSCH transmission starting from symbol <NUM> of subsequent slot <NUM> (slot N + <NUM>), rather than starting from symbol <NUM> of next slot <NUM> (slot N + <NUM>). Similarly, if the DCI schedules a second PUSCH transmission, the UE may begin transmitting the second PUSCH transmission after the time gap <NUM> and additional time delay. For example, the UE may begin transmitting the second PUSCH transmission starting from symbol <NUM> of subsequent slot <NUM> in response to the DCI.

<FIG> illustrates a further example <NUM> of a time gap <NUM> following a CORESET <NUM> where a PDCCH carrying DCI is received. Similar to the examples of <FIG> and <FIG>, the UE may receive CORESET <NUM> in a slot <NUM> (slot N). Also similar to the example of <FIG>, here a last symbol <NUM> of CORESET <NUM> is the second symbol of slot <NUM> (symbol <NUM>), although in other examples the last symbol <NUM> of CORESET <NUM> may be a different symbol in slot <NUM>. However, unlike the examples of <FIG> and <FIG>, here the time gap <NUM> may include multiple portions, including a first time gap portion <NUM> (T symbols) and a second time gap portion <NUM> (Δ symbols) which the base station may separately configure. The first time gap portion <NUM> may correspond to the time gap <NUM>, <NUM> of <FIG> and <FIG>. For instance, in the illustrated example, the first time gap portion <NUM> is T = <NUM> symbols, although in other examples the first time gap portion may be a different number of symbols depending on SCS, UE capability, or other example parameters as described above. The second time gap portion <NUM> may be an additional number of symbols for additional UE processing margin. For instance, in the illustrated example, the second time gap portion <NUM> is Δ = <NUM> symbols, although in other examples the second time gap portion may be a different number of symbols depending on PDCCH SCS and PUSCH SCS as described above. Additionally, similar to the example of <FIG>, here the time gap <NUM> (including first time gap portion <NUM> and second time gap portion <NUM>) ends in the middle of a slot, in this case, next slot <NUM> (slot N + <NUM>). Thus, if the UE were to terminate subsequent PUSCH repetitions after the time gap following the CORESET, the termination would begin in the middle of a slot. To prevent such partial slot terminations, the UE may delay the termination to the beginning of a subsequent slot <NUM> (slot N + <NUM>), such as illustrated in <FIG>. As a result, the UE may stop transmitting repetitions of the PUSCH transmission starting from symbol <NUM> of subsequent slot <NUM> (slot N + <NUM>), rather than starting from symbol <NUM> of next slot <NUM> (slot N + <NUM>). Similarly, if the DCI schedules a second PUSCH transmission, the UE may begin transmitting the second PUSCH transmission after the time gap <NUM> and additional time delay. For example, the UE may begin transmitting the second PUSCH transmission starting from symbol <NUM> of subsequent slot <NUM> in response to the DCI.

Thus, the UE may terminate subsequent repetitions of a PUSCH transmission in response to a DCI which implicitly or explicitly indicates that the base station successfully decoded a prior PUSCH transmission. The DCI may implicitly indicate successful decoding when the DCI schedules a subsequent uplink transmission in overlapping resources of the repetitions of the prior uplink transmission. The DCI may explicitly indicate successful decoding (effectively serving as HARQ-ACK) when the DCI includes preconfigured bit values in its various DCI format parameters (e.g., DCI format 0_0 or 0_1). Such DCI serving as explicit HARQ-ACK does not schedule a subsequent uplink transmission.

<FIG> illustrates an example <NUM> of a DCI serving as explicit HARQ-ACK. While the illustrated example refers to DCI format 0_0, the DCI format may be different in other examples (e.g., DCI format 0_1). The DCI may various parameters, including a FDRA <NUM>, a MCS <NUM>, and other parameters <NUM> such as a TDRA, a frequency hopping flag, a new data indicator, a redundancy version, a HARQ process number, etc. To explicitly indicate that the base station has successfully decoded the PUSCH transmission, the base station may configure the bits of one or more DCI parameters according to one preconfigured bit value (e.g., a bit sequence) and the bits of one or more other DCI parameters according to a different preconfigured bit value (e.g., a different bit sequence). For instance, as illustrated in the example of <FIG>, the base station may configure the FDRA <NUM> or the MCS <NUM> (or both) to include all one bits, and one or more of the other parameters <NUM> to include all zero bits. The base station may alternatively configure the FDRA or MCS (or both) to include all zero bits, and one or more of the other parameters to include all one bits. In other examples, the base station may configure the FDRA, MCS, or other parameters of the DCI with other bit sequences to indicate an explicit HARQ-ACK. Thus, when the UE receives the DCI, the UE may determine that the DCI serves to acknowledge a prior PUSCH transmission, and therefore that the UE may terminate subsequent repetitions of its prior PUSCH transmission.

<FIG> illustrates an example <NUM> in which the UE terminates a PUSCH transmission <NUM> in response to a DCI in a CORESET <NUM> (e.g., CORESET <NUM>, <NUM>, <NUM> of <FIG>) explicitly indicating successful decoding of the PUSCH transmission. The base station initially provides DCI <NUM> in PDCCH to the UE scheduling the PUSCH transmission, in response to which the UE begins to transmit its uplink data to the base station in PUSCH transmission <NUM>. While the UE is transmitting its uplink data in one or more repetitions, the base station may successfully decode the PUSCH transmission. Moreover, the base station may determine that the UE does not have additional data to send in its transmission buffer, e.g., in response to a buffer status report from the UE or in some other manner. Therefore, the base station may provide DCI <NUM> to the UE in CORESET <NUM> explicitly indicating that the PUSCH transmission was successfully decoded. For example, DCI <NUM> may have a DCI format <NUM>-<NUM> or <NUM>-<NUM> including a FDRA field or a MCS field set to all ones, and all remaining bits in one or more other parameters of the DCI (e.g., TDRA, frequency hopping flag, etc.) set to zero, as described above with respect to <FIG>. In response to receiving DCI <NUM>, the UE may terminate its PUSCH transmission, as represented by terminated PUSCH transmission <NUM>, after a time gap <NUM> (e.g., time gap <NUM>, <NUM>, <NUM>) following the CORESET <NUM> including DCI <NUM>.

<FIG> illustrates an example <NUM> in which the UE terminates a first PUSCH transmission <NUM> in response to a DCI in a CORESET <NUM> (e.g., CORESET <NUM>, <NUM>, <NUM> of <FIG>) implicitly indicating successful decoding of the first PUSCH transmission and scheduling a second PUSCH transmission <NUM>. The base station initially provides DCI <NUM> in PDCCH to the UE scheduling the first PUSCH transmission, in response to which the UE begins to transmit its uplink data to the base station in first PUSCH transmission <NUM>. While the UE is transmitting its uplink data in one or more repetitions, the base station may successfully decode the first PUSCH transmission. Moreover, the base station may determine that the UE has additional data to send in its transmission buffer, e.g., in response to a buffer status report from the UE or in some other manner. Therefore, the UE may provide DCI <NUM> to the UE implicitly indicating that the first PUSCH transmission was successfully decoded. For example, DCI <NUM> may schedule second PUSCH transmission <NUM> in overlapping time resources with repetitions of first PUSCH transmission <NUM>. In response to receiving DCI <NUM>, the UE may terminate its PUSCH transmission, as represented by terminated PUSCH transmission <NUM>, and begin transmitting its second PUSCH transmission, after a time gap <NUM> (e.g., time gap <NUM>, <NUM>, <NUM>) following the CORESET <NUM> including DCI <NUM>.

<FIG> is an example <NUM> of a call flow between a UE <NUM> and a base station <NUM>. The UE may transmit a capability information message <NUM> to the base station. For example, in response to receiving a capability inquiry from the base station, the UE may provide a capability information message that indicates whether the UE is capable of advanced PUSCH processing capability (e.g., PUSCH processing capability <NUM>). The base station may provide a configuration <NUM> to the UE. For example, the configuration may be a PUSCH configuration indicating a number of repetitions of uplink data which the UE may transmit on PUSCH in response to a dynamic grant. Alternatively, the configuration may be a configured grant configuration indicating a number of repetitions of uplink data that the UE may transmit on PUSCH in response to a configured grant.

Subsequently, the UE <NUM> may receive a DCI <NUM> from base station <NUM> scheduling an uplink data transmission <NUM>. For example, DCI <NUM> may correspond to DCI <NUM> or DCI <NUM> in <FIG> or <FIG>, respectively. Similarly, uplink data transmission <NUM> may correspond to PUSCH transmission <NUM> or first PUSCH transmission <NUM> in <FIG> or <FIG>, respectively. The UE may then transmit uplink data transmission <NUM> to the base station, including one or more repetitions <NUM> of the uplink data transmission as configured by configuration <NUM>.

In this example, the base station <NUM> successfully decodes the uplink data transmission <NUM> after receiving the one or more repetitions <NUM>. Therefore, the base station provides a DCI <NUM> to the UE <NUM> explicitly or implicitly indicating that the uplink data transmission was successfully decoded. For example, DCI <NUM> may correspond to DCI <NUM> in CORESET <NUM> of <FIG> if the UE does not have additional data to send in its transmission buffer. In such case, DCI <NUM> may have a DCI format <NUM>-<NUM> or <NUM>-<NUM> including one or more of its parameters configured with bit values to effectively indicate a HARQ-ACK, as described above with respect to <FIG>. Alternatively, DCI <NUM> may correspond to DCI <NUM> in CORESET <NUM> of <FIG> if the UE has additional data to send in its transmission buffer. In such case, DCI <NUM> may schedule subsequent uplink data transmission <NUM> in overlapping time resources with the one or more repetitions <NUM>.

At <NUM>, in response to receiving DCI <NUM>, the UE <NUM> may terminate subsequent repetition(s) of the uplink data transmission <NUM>. For example, if the base station <NUM> configures the UE to transmit eight repetitions of uplink data transmission <NUM>, the base station may successfully decode the data after four repetitions (the repetitions <NUM>) and provide DCI <NUM> to the UE prior to the next scheduled repetition. As a result, the UE may refrain from transmitting the remaining four repetitions to the base station, as represented by terminated uplink data repetitions <NUM> (e.g., terminated PUSCH transmission <NUM>, <NUM> of <FIG> or <FIG>, respectively). In another example, if the base station successfully decodes the uplink data transmission <NUM> before even the first configured repetition, the UE may refrain from transmitting the eight repetitions to the base station. The UE may terminate its repetitions after a time gap (e.g., time gap <NUM>, <NUM>, <NUM>, <NUM>, <NUM> of <FIG> and <FIG>) following the CORESET including the DCI <NUM>. The time gap, for example, may be a function of the SCS of the PDCCH carrying DCI <NUM>, the SCS of the PUSCH carrying uplink data transmission <NUM> or repetitions <NUM>, the PUSCH processing capability of the UE reported in capability information message <NUM>, or other factors. Moreover, if DCI <NUM> schedules subsequent uplink data transmission <NUM> in overlapping resources with terminated uplink data repetitions <NUM>, the UE may transmit the subsequent uplink data transmission in the overlapping resources.

<FIG> is a flowchart <NUM> of a method of wireless communication. The method maybe performed by a UE (e.g., the UE <NUM>, <NUM>, <NUM>; the apparatus <NUM>). Optional aspects are illustrated in dashed lines. The method allows a UE to terminate PUSCH transmissions after a time gap following a CORESET to account for different timing considerations between NR and LTE.

At <NUM>, the UE obtains information configuring an uplink data transmission and a repetition of the uplink data transmission. For example, <NUM> may be performed by obtain component <NUM>. For instance, referring to <FIG>, the UE <NUM> may obtain configuration <NUM> from base station <NUM> configuring uplink data transmission <NUM> and repetitions <NUM> of uplink data transmission <NUM>. For example, the configuration may be a PUSCH configuration indicating a number of repetitions of uplink data which the UE may transmit on PUSCH in response to a dynamic grant. In another example, the configuration may be a configured grant configuration indicating a number of repetitions of uplink data that the UE may transmit on PUSCH in response to a configured grant. Thus, the obtained information may be a PUSCH configuration, a configured grant configuration, or other configuration(s) for an uplink data transmission including uplink data repetitions. The information configuring the uplink data transmission and the repetition of the uplink data transmission may be the same information (e.g., a single configuration) or different information (e.g., different configurations).

At <NUM>, the UE sends the uplink data transmission to a base station. For example, <NUM> may be performed by send component <NUM>. For instance, referring to <FIG>, the UE <NUM> may send uplink data transmission <NUM> to base station <NUM>. The UE <NUM> may also send one or more repetitions <NUM> of the uplink data transmission. The uplink data transmission and repetitions may be scheduled by DCI <NUM>.

Finally, at <NUM>, the UE terminates the repetition of the uplink data transmission in response to reception of downlink information in a downlink control channel. For example, <NUM> may be performed by termination component <NUM>. For instance, referring to <FIG>, at <NUM>, the UE <NUM> terminates or refrains from sending one or more subsequent repetitions of uplink data transmission <NUM>, as represented by terminated uplink data repetition(s) <NUM>. The UE may refrain from sending the repetition(s) in response to receiving DCI <NUM> in PDCCH.

The repetition is terminated after a time gap following a CORESET where the downlink control channel is received. For instance, referring to <FIG>, and <NUM>-<NUM>, the UE <NUM> may terminate its repetitions at <NUM> after a time gap (e.g., time gap <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) following the CORESET (e.g., CORESET <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) where the PDCCH carrying DCI <NUM> (e.g., DCI <NUM>, <NUM>) is received.

The time gap may be equal to a length of one or more symbols following a last symbol of the CORESET. For example, referring to <FIG>, time gap <NUM> may be equal to a length of <NUM> symbols (T = <NUM> symbols) following last symbol <NUM> of CORESET <NUM>. In another example, referring to <FIG>, time gap <NUM> may be equal to a length of <NUM> symbols (T = <NUM> symbols) following last symbol <NUM> of CORESET <NUM>. The time gap may have different symbol lengths in other examples. Additionally, the time gap may end during a slot, and the terminating at <NUM> may begin in an initial symbol of a subsequent slot. For example, referring to <FIG> and <FIG>, time gap <NUM>, <NUM> may end during next slot <NUM>, <NUM> (slot N + <NUM>), and the terminated PUSCH transmissions (e.g., terminated uplink data repetition(s) <NUM> in <FIG>) may begin in symbol <NUM> of subsequent slot <NUM>, <NUM> (slot N + <NUM>).

The downlink information may indicate a HARQ-ACK. In this example, the downlink information may include a FDRA, a MCS, and other parameters, and the HARQ-ACK may be indicated by a first preconfigured bit value of the FDRA or of the MCS and a second preconfigured bit value of the other parameters. The second preconfigured bit value may be different than the first preconfigured bit value. For example, referring to <FIG> and <FIG>, the DCI <NUM>, <NUM> may explicitly indicate that the uplink data transmission <NUM> or repetition(s) <NUM> was successfully decoded. For instance, DCI <NUM>, <NUM> may have a DCI format <NUM>-<NUM> or <NUM>-<NUM> including one or more of its parameters configured with bit values to effectively indicate a HARQ-ACK, as described above with respect to <FIG>. As an example, the FDRA <NUM> or MCS <NUM> of the DCI maybe set to all ones, while the other parameters <NUM> of the DCI may be set to all zeroes. The base station <NUM> may provide this DCI, for instance, if the UE does not have additional data to send in its transmission buffer.

The downlink information may schedule a subsequent uplink data transmission after the time gap. For example, referring to <FIG> and <FIG>, the DCI <NUM>, <NUM> may implicitly indicate that the uplink data transmission <NUM> or repetition(s) <NUM> was successfully decoded. For instance, DCI <NUM> may schedule subsequent uplink data transmission <NUM> in overlapping time resources with the one or more repetitions <NUM> after time gap <NUM>, <NUM>, <NUM>, <NUM>. Moreover, the time gap may end during a slot, and the subsequent uplink data transmission may begin in an initial symbol of a subsequent slot. For example, referring to <FIG>, time gap <NUM> may end during next slot <NUM> (slot N + <NUM>), and the subsequent PUSCH transmission (e.g., subsequent uplink data transmission <NUM> in <FIG>) may begin in symbol <NUM> of subsequent slot <NUM> (slot N + <NUM>).

The time gap may be a function of a first SCS of a PDCCH carrying the downlink information and a second SCS of a PUSCH carrying the uplink data transmission. For example, referring to <FIG> and <FIG>, the time gap <NUM>, <NUM>, <NUM>, <NUM>, <NUM> (T) may be a function of a subcarrier spacing of the PDCCH carrying the DCI <NUM>, <NUM>, <NUM> and a subcarrier spacing of the PUSCH carrying the uplink data transmission <NUM> or repetition(s) <NUM>. For example, T may be one value if the SCS of the DCI and the PUSCH transmission are both <NUM>, T may be another value if the SCS of the DCI and the PUSCH transmission are both <NUM>, T may be another value if the SCS of the DCI is <NUM> and the SCS of the PUSCH transmission is <NUM>, etc..

The time gap may be a function of a first SCS of a downlink BWP including a PDCCH and a second SCS of an uplink BWP including a PUSCH. For example, referring to <FIG> and <FIG>, the time gap <NUM>, <NUM>, <NUM>, <NUM>, <NUM> (T) may be a function of a subcarrier spacing of an active DL BWP over which the PDCCH carrying the DCI <NUM>, <NUM>, <NUM> is monitored and a subcarrier spacing of an active UL BWP over which the PUSCH carrying the uplink data transmission <NUM> or repetition(s) <NUM> is transmitted. For example, T may be one value if the SCS of the DL BWP carrying the DCI and the UL BWP carrying the PUSCH transmission are both <NUM>, T may be another value if the SCS of the DL BWP and the UL BWP are both <NUM>, T may be another value if the SCS of the DL ZWP is <NUM> and the SCS of the UL BWP is <NUM>, etc..

The time gap may be a function of a UE PUSCH processing capability. For example, referring to <FIG> and <FIG>, the time gap <NUM>, <NUM>, <NUM>, <NUM>, <NUM> (T) may be a function of a PUSCH processing capability of the UE. For example, T may be one value for UE PUSCH processing capability <NUM> and another value for UE PUSCH processing capability <NUM>. The PUSCH processing capability of the UE may be indicated, for example, in capability information message <NUM> of <FIG>.

The time gap may be a function of a configuration indicating whether a first symbol of the uplink data transmission is reserved for a DMRS. For example, referring to <FIG> and <FIG>, the time gap <NUM>, <NUM>, <NUM>, <NUM>, <NUM> (T) may be a function of a configuration (e.g., configuration <NUM> or a different configuration) indicating whether a first symbol of a PUSCH allocation for the uplink data transmission <NUM> or repetition(s) <NUM> consists only of DMRS. For example, T may be one value if the base station configures the first symbol of a slot of the PUSCH transmission to include only DMRS, while T may be another value if the base station configures the first symbol of a slot of the PUSCH transmission to include only PUSCH data, or PUSCH data and DMRS.

The time gap may be a function of a PUSCH preparation time. For example, referring to <FIG> and <FIG>, the time gap <NUM>, <NUM>, <NUM>, <NUM>, <NUM> (T) may be a function of a UE PUSCH preparation time Tproc,<NUM>, where Tproc,<NUM> is a function of PUSCH preparation time N<NUM>, where N<NUM> is based on a numerology µ for UE processing capability <NUM>, where µ corresponds to the one of (µDL, µUL) resulting with the largest Tproc,<NUM> (the smaller value or SCS between µDL, µUL), where the µDL corresponds to the subcarrier spacing at with the PDCCH carrying the DCI scheduling the PUSCH was transmitted, and where µUL corresponds to the subcarrier spacing at which the PUSCH is to be transmitted. For instance, the value of T may be different for different values of N<NUM>.

The time gap may comprise a plurality of separately configurable portions. For instance, referring to <FIG>, time gap <NUM> may include multiple portions, including a first time gap portion <NUM> (T symbols) and a second time gap portion <NUM> (Δ symbols) which the base station may separately configure. One of the separately configurable portions (e.g., second time gap portion <NUM>) may be pre-configured (e.g., fixed), indicated in a PUSCH configuration (e.g., configuration <NUM> or a different configuration), or dependent on UE capability. For instance, in one example, the value of Δ may be fixed to a value of <NUM>, <NUM>, <NUM> or some other number. In another example, the base station may dynamically indicate the value of Δ to the UE within a PUSCH configuration (e.g., <NUM>, <NUM>, <NUM> or some other number of symbols). In a further example, the value of Δ may be dependent on UE capability. For instance, Δ may be one value if the UE is capable of PUSCH processing capability <NUM>, while Δ may be another value if the UE is only capable of PUSCH processing capability <NUM>.

Additionally, one of the separately configurable portions (e.g., second time gap portion <NUM>) may be a function of a first SCS of a PDCCH carrying the downlink information and a second SCS of a PUSCH carrying the uplink data transmission. For example, the duration of Δ may be a function of the SCS of the PDCCH carrying the DCI <NUM> and the SCS of the PUSCH carrying the uplink data transmission <NUM> or repetition(s) <NUM> (e.g., the smaller SCS between the PDCCH SCS and the PUSCH SCS). For instance, the total length in time of Δ may be one value if the smaller SCS is <NUM>, the total length in time of Δ may be another value if the smaller SCS is <NUM>, etc..

In one configuration, the apparatus <NUM> maybe a modem chip and include just the baseband processor <NUM>, and in another configuration, the apparatus <NUM> maybe the entire UE (e.g., see <NUM> of <FIG>) and include the aforediscussed additional modules of the apparatus <NUM>.

The communication manager <NUM> includes an obtain component <NUM> that is configured to obtain information configuring an uplink data transmission and a repetition of the uplink data transmission, e.g., as described in connection with <NUM>. <FIG> illustrates an example <NUM> of a process or algorithm performed by obtain component <NUM>. The obtain component may be implemented, for example, in RX processor <NUM>. At <NUM>, the obtain component <NUM> receives the information. For example, referring to <FIG>, the obtain component <NUM> may receive a signal carrying the information from base station <NUM> through one or more respective antennas <NUM>. Then, at <NUM>, the obtain component <NUM> decodes the received information. For example, referring to <FIG>, the obtain component may demodulate the received information based on a modulation scheme (e.g., BPSK, QPSK, M-PSK, M-QAM, etc.).

The communication manager <NUM> further includes a send component <NUM> that receives input in the form of the information from the obtain component <NUM> and is configured to send the uplink data transmission to a base station, e.g., as described in connection with <NUM>. <FIG> illustrates an example <NUM> of a process or algorithm performed by send component <NUM>. The send component may be implemented, for example, in TX processor <NUM>. At <NUM>, the send component <NUM> encodes uplink data. For example, referring to <FIG>, the send component <NUM> may modulate uplink data based on a modulation scheme (e.g., BPSK, QPSK, M-PSK, M-QAM, etc.). Then, at <NUM>, the send component <NUM> transmits the encoded uplink data. For example, referring to <FIG>, the send component may transmit the encoded uplink data to base station <NUM> through one or more respective antennas <NUM>.

The communication manager <NUM> further includes a termination component <NUM> that receives input in the form of the information from the obtain component <NUM> and is configured to terminate the repetition of the uplink data transmission in response to reception of downlink information in a downlink control channel, e.g., as described in connection with <NUM>. <FIG> illustrates an example <NUM> of a process or algorithm performed by termination component <NUM>. The termination component may be implemented, for example, in controller/processor <NUM>. At <NUM>, the termination component <NUM> receives the downlink information. For example, referring to <FIG>, the termination component <NUM> may receive a DCI from the RX processor <NUM> (or the obtain component <NUM> of RX processor <NUM>). For instance, the obtain component <NUM> in RX processor <NUM> may receive a signal carrying a PDCCH payload including DCI from base station <NUM> through one or more respective antennas <NUM>, demodulate the PDCCH payload based on a modulation scheme (e.g., BPSK, QPSK, M-PSK, M-QAM, etc.), and provide the demodulated PDCCH payload including the DCI to the termination component <NUM> in controller/processor <NUM>. The termination component <NUM> may then decode the demodulated PDCCH payload to receive the DCI. Then, at <NUM>, the termination component <NUM> refrains from transmitting the repetition in response to the received downlink information. For example, referring to <FIG>, the termination component <NUM> may stop delivery of uplink data repetitions to the TX processor <NUM> (or the send component <NUM> of the TX processor).

In one configuration, the apparatus <NUM>, and in particular the cellular baseband processor <NUM>, includes means for obtaining information configuring an uplink data transmission and a repetition of the uplink data transmission, means for sending the uplink data transmission to a base station, and means for terminating the repetition of the uplink data transmission in response to reception of downlink information in a downlink control channel. The repetition is terminated after a time gap following a CORESET where the downlink control channel is received.

In one configuration, the time gap may be equal to a length of one or more symbols following a last symbol of the CORESET.

In one configuration, the time gap may end during a slot, and the terminating may begin in an initial symbol of a subsequent slot.

In one configuration, the downlink information may indicate a HARQ-ACK. In one configuration, the downlink information may include a FDRA, a MCS, and other parameters, and the HARQ-ACK may be indicated by a first preconfigured bit value of the FDRA or of the MCS and a second preconfigured bit value of the other parameters, the second preconfigured bit value being different than the first preconfigured bit value.

In one configuration, the downlink information may schedule a subsequent uplink data transmission after the time gap. In one configuration, the time gap may end during a slot, and the subsequent uplink data transmission may begin in an initial symbol of a subsequent slot.

In one configuration, the time gap may be a function of a first SCS of a PDCCH carrying the downlink information and a second SCS of a PUSCH carrying the uplink data transmission.

In one configuration, the time gap may be a function of a first SCS of a downlink BWP including a PDCCH and a second SCS of an uplink BWP including a PUSCH.

In one configuration, the time gap may be a function of a UE PUSCH processing capability.

In one configuration, the time gap may be a function of a configuration indicating whether a first symbol of the uplink data transmission is reserved for a DMRS.

In one configuration, the time gap may be a function of a PUSCH preparation time.

In one configuration, the time gap may comprise a plurality of separately configurable portions. In one configuration, one of the separately configurable portions is pre-configured, indicated in a PUSCH configuration, or dependent on UE capability. In one configuration, one of the separately configurable portions may be a function of a first SCS of a PDCCH carrying the downlink information and a second SCS of a PUSCH carrying the uplink data transmission.

The aforementioned means may be one or more of the aforementioned components of the apparatus <NUM> configured to perform the functions recited by the aforementioned means. As described supra, the apparatus <NUM> may include the TX Processor <NUM>, the RX Processor <NUM>, and the controller/processor <NUM>.

If a base station has already decoded uplink data in a prior PUSCH transmission or repetition, the UE may continue to send unnecessary PUSCH repetitions due to a conventional lack of HARQ feedback for PUSCH in NR. As a result, the UE may waste transmission power and PUSCH resources on inefficient repetitions. To address this waste of power and inefficiency, the base station may provide a DCI to the UE which explicitly or implicitly indicates whether a prior PUSCH transmission was successfully decoded, and the UE may perform early termination of an ongoing PUSCH transmission (e.g., terminate inefficient repetitions). Thus, UE power reduction and enhanced resource efficiency may be achieved. Moreover, the UE may terminate PUSCH transmissions after a time gap (T symbols) following a CORESET including the PDCCH carrying the DCI, rather than after a number of subframes (k subframes) following a subframe containing the DCI. The time gap may be a function of various parameters, such as PDCCH SCS (or DL BWP SCS), PUSCH SCS (or UL BWP SCS), UE PUSCH processing capability, DMRS configuration, or PUSCH preparation time. Such configurable timing may accommodate and minimize conflicts with various timing configurations present in NR (e.g., dynamic TDD, different numerologies between PDCCH and PUSCH, and multiple PUSCH processing capabilities). Additionally, the time gap may be divided into separately configurable portions, where one of the portions may also be a function of PDCCH SCS and PUSCH SCS. Such configured portions may provide additional UE processing margin for low capability UEs while similarly accounting for the various timing configurations present in NR as described above.

Claim 1:
A method (<NUM>) of wireless communication at a user equipment, UE, (<NUM>, <NUM>, <NUM>, <NUM>), comprising:
obtaining (<NUM>) information configuring an uplink data transmission and a repetition of the uplink data transmission;
sending (<NUM>) the uplink data transmission to a base station; and
terminating (<NUM>) the repetition of the uplink data transmission in response to reception of downlink information in a downlink control channel,
wherein the repetition is terminated after a time gap following a control resource set, CORESET, where the downlink control channel is received;
wherein the downlink information indicates a hybrid automatic repeat request, HARQ, acknowledgment, HARQ-ACK; and the method is characterized in:
wherein the downlink information includes a frequency domain resource assignment, FDRA, a modulation and coding scheme, MCS, and other parameters, and the HARQ-ACK is indicated by a first preconfigured bit value of the FDRA or of the MCS and a second preconfigured bit value of the other parameters, the second preconfigured bit value being different than the first preconfigured bit value.