_proc,2corresponds to the PUSCH processing capability 2 [6, TS 38.214] assuming d2,1=0 with μ being the smallest SCS configuration between the SCS configurations of the PDCCH and of a PUSCH transmission or of an SRS transmission on the serving cell. UE may not be expected to cancel the transmission of SRS or PUSCH before the first symbol that is T_proc,2after the end of the reception of the last symbol of the PDCCH carrying the ULCI including the effect of the timing advance.

An indication by a DCI format 2_4 for a serving cell can be applicable to PUSCH or SRS transmissions on the serving cell. For the serving cell, the UE can determine the first symbol of the T_CIsymbols to be the first symbol that is after T_proc,2+d from the end of a PDCCH reception where the UE detects the DCI format 2_4, where d is provided by a higher layer parameter. T_proc,2corresponds to the PUSCH processing capability 2 [6, TS 38.214] assuming d_2,1=0 with μ being the smallest SCS configuration between the SCS configurations of the PDCCH and of a PUSCH transmission or of an SRS transmission on the serving cell. UE is not expected to cancel the transmission of SRS or PUSCH before the first symbol that is T_proc,2after the end of the reception of the last symbol of the PDCCH carrying the ULCI including the effect of the timing advance.

For UE PUSCH preparation procedure time, according to TS 38.214, if the first uplink symbol in the PUSCH allocation for a transport block, including the DM-RS, as defined by the slot offset K₂and the start and length indicator SLIV of the scheduling DCI and including the effect of the timing advance, is no earlier than at symbol L₂, where L₂is defined as the next uplink symbol with its CP starting T_proc,2=max((N₂+d_2,1) (2048+144)·κ2^−μ·T_C, d_2,2) after the end of the reception of the last symbol of the PDCCH carrying the DCI scheduling the PUSCH, then the UE shall transmit the transport block. N₂is based on μ of Table 6.4-1 and Table 6.4-2 for UE processing capability 1 and 2 respectively, where μ corresponds to the one of (μ_DL, μ_UL) resulting with the largest T_proc,2, where the μ_DLcorresponds to the subcarrier spacing of the downlink with which the PDCCH carrying the DCI scheduling the PUSCH was transmitted and μ_ULcorresponds to the subcarrier spacing of the uplink channel with which the PUSCH is to be transmitted, and K is defined in clause 4.1 of [TS 38.211]. If the first symbol of the PUSCH allocation consists of DM-RS only, then d_2,1=0, otherwise d_2,1=1. If the UE is configured with multiple active component carriers, the first uplink symbol in the PUSCH allocation further includes the effect of timing difference between component carriers as given in [TS 38.133]. If the scheduling DCI triggered a switch of BWP, d_2,2equals to the switching time as defined in [TS 38.133], otherwise d_2,2=0. For a UE that supports capability 2 on a given cell, the processing time according to UE processing capability 2 is applied if the high layer parameter processingType2Enabled in PUSCH-ServingCellConfig is configured for the cell and set to enable. If the PUSCH indicated by the DCI is overlapping with one or more PUCCH channels, then the transport block is multiplexed following the procedure in clause 9.2.5 of [TS 38.213], otherwise the transport block is transmitted on the PUSCH indicated by the DCI. Otherwise, the UE may ignore the scheduling DCI. The value of T_proc,2is used both in the case of normal and extended cyclic prefix.

TABLE 6.4-1

PUSCH preparation time for PUSCH timing capability 1

μ
PUSCH preparation time N₂[symbols]

0
10

1
12

2
23

3
36

TABLE 6.4-2

PUSCH preparation time for PUSCH timing capability 2

μ
PUSCH preparation time N₂[symbols]

0
5

1
5.5

2
11 for frequency range 1

For resource allocation for uplink transmission with configured grant, according to 38.214, when PUSCH resource allocation is semi-statically configured by higher layer parameter configuredGrantConfig in BWP-UplinkDedicated information element, and the PUSCH transmission corresponding to a configured grant, the following higher layer parameters are applied in the transmission: For Type 1 PUSCH transmissions with a configured grant, the following parameters are given in configuredGrantConfig unless mentioned otherwise: For the determination of the PUSCH repetition type, if the higher layer parameter PUSCHRepTypeIndicator-ForTypeIConfiguredgrant is configured and set to ‘pusch-RepTypeB’, PUSCH repetition type B is applied; otherwise, PUSCH repetition type A is applied. For PUSCH repetition type A, the selection of the time domain resource allocation table follows the rules for DCI format 0_0 on UE specific search space, as defined in Clause 6.1.2.1.1. For PUSCH repetition type B, the selection of the time domain resource allocation table is as follows: If PUSCHRepTypeIndicator-ForDCIFormat0_1 in pusch-Config is configured and set to ‘pusch-RepTypeB’, PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_1 in pusch-Config is used. Otherwise, PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_2 in pusch-Config is used. It is not expected that PUSCHRepTypeIndicator-ForTypeIConfiguredgrant is configured with ‘pusch-RepTypeB’ when none of PUSCHRepTypeIndicator-ForDCIFormat0_1 and PUSCHRepTypeIndicator-ForDCIFormat0_2 in pusch-Config is set to ‘pusch-RepTypeB’.

The higher layer parameter timeDomainAllocation value m provides a row index m+1 pointing to the determined time domain resource allocation table, where the start symbol and length are determined following the procedure defined in Clause 6.1.2.1. Frequency domain resource allocation is determined by the N LSB bits in the higher layer parameter frequencyDomainAllocation, forming a bit sequence f₁₇, . . . , f₁, f₀, where f₀is the LSB, according to the procedure in Clause 6.1.2.2 and Nis determined as the size of frequency domain resource assignment field in DCI format 0_1 for a given resource allocation type indicated by resourceAllocation, except if useInterlacePUSCH-Dedicated is set to ‘enabled’, in which case uplink type 2 resource allocation is used wherein the UE interprets the LSB bits in the higher layer parameter frequencyDomainAllocation as for the frequency domain resource assignment field of DCI 0_1 according to the procedure in Clause 6.1.2.2.3. The I_MCSis provided by higher layer parameter mcsAndTBS. Number of DM-RS CDM groups, DM-RS ports, SRS resource indication and DM-RS sequence initialization are determined as in Clause 7.3.1.1 of [TS 38.212], and the antenna port value, the bit value for DM-RS sequence initialization, precoding information and number of layers, SRS resource indicator are provided by antennaPort, dmrs-SeqInitialization, precodingAndNumberOfLayers, and srs-ResourceIndicator respectively. When frequency hopping is enabled, the frequency offset between two frequency hops can be configured by higher layer parameter frequencyHoppingOffset.

For Type 2 PUSCH transmissions with a configured grant: the resource allocation follows the higher layer configuration according to [TS 38.321], and UL grant received on the DCI. The PUSCH repetition type and the time domain resource allocation table are determined by the PUSCH repetition type and the time domain resource allocation table associated with the UL grant received on the DCI, respectively, as defined in Clause 6.1.2.1.

For PUSCH transmissions with a Type 1 or Type 2 configured grant, the number of (nominal) repetitions K to be applied to the transmitted transport block is provided by the indexed row in the time domain resource allocation table if numberofrepetitions is present in the table. Otherwise, K is provided by the higher layer configured parameters repK.

The UE shall not transmit anything on the resources configured by configuredGrantConfig if the higher layers did not deliver a transport block to transmit on the resources allocated for uplink transmission without grant.

A set of allowed periodicities P are defined in [TS 38.331]. The higher layer parameter cg-nrofSlots-r16, provides the number of consecutive slots allocated within a configured grant period. The higher layer parameter cg-nrofPUSCH-InSlot-r16 provides the number of consecutive PUSCH allocations within a slot, where the first PUSCH allocation follows the higher layer parameter timeDomainAllocation, and the remaining PUSCH allocations have the same length and PUSCH mapping type, and are appended following the previous allocations without any gaps. The same combination of start symbol and length and PUSCH mapping type repeats over the consecutively allocated slots.

For operation with shared spectrum channel access where a UE is performing uplink transmission with configured grants in contiguous OFDM symbols on all resource blocks of an RB set, for the first such UL transmission the UE randomly determines a duration of a cyclic prefix extension T_extto be applied for transmission according to [TS 38.211] from a set of values configured by higher layers according to the following rule: If the first such UL transmission is within a channel occupancy initiated by the gNB (defined in Clause 4 of [TS 37.213]), the set of values is determined by cg-StartingFullBW-InsideCOT-r16. Otherwise, the set of values is determined by cg-StartingFullBW-OutsideCOT-r16.

For operation with shared spectrum channel access where a UE is performing uplink transmission with configured grants in contiguous OFDM symbols on fewer than all resource blocks of an RB set, for the first such UL transmission the UE determines a duration of a cyclic prefix extension T_extto be applied for transmission according to [TS 38.211] according to the following rule: If the first such UL transmission is within a channel occupancy initiated by the gNB (defined in Clause 4 of [TS 37.213]), the T_extis equal to cg-StartingPartialBW-InsideCOT-r16. Otherwise, the T_extis equal to cg-StartingPartialBW-OutsideCOT-r16.

For transport block repetition for uplink transmissions of PUSCH repetition Type A with a configured grant

The procedures described in this clause apply to PUSCH transmissions of PUSCH repetition Type A with a Type 1 or Type 2 configured grant. The higher layer parameter repK-RV defines the redundancy version pattern to be applied to the repetitions. If the parameter repK-RV is not provided in the configuredGrantConfig, the redundancy version for uplink transmissions with a configured grant shall be set to 0. Otherwise, for the nth transmission occasion among K repetitions, n=1, 2, . . . , K, it is associated with (mod(n−1,4)+1)^thvalue in the configured RV sequence. If a configured grant configuration is configured with Configuredgrantconfig-StartingfromRV0 set to ‘off’, the initial transmission of a transport block may only start at the first transmission occasion of the K repetitions. Otherwise, the initial transmission of a transport block may start at the first transmission occasion of the K repetitions if the configured RV sequence is {0,2,3,1}, any of the transmission occasions of the K repetitions that are associated with RV=0 if the configured RV sequence is {0,3,0,3}, any of the transmission occasions of the K repetitions if the configured RV sequence is {0,0,0,0}, except the last transmission occasion when K≥8.

For any RV sequence, the repetitions shall be terminated after transmitting K repetitions, or at the last transmission occasion among the K repetitions within the period P, or from the starting symbol of the repetition that overlaps with a PUSCH with the same HARQ process scheduled by DCI format 0_0, 0_1 or 0_2, whichever is reached first. In addition, the UE shall terminate the repetition of a transport block in a PUSCH transmission if the UE receives a DCI format 0_1 with DFI flag provided and set to ‘1’, and if in this DCI the UE detects ACK for the HARQ process corresponding to that transport block.

The UE is not expected to be configured with the time duration for the transmission of K repetitions larger than the time duration derived by the periodicity P. If the UE determines that, for a transmission occasion, the number of symbols available for the PUSCH transmission in a slot is smaller than transmission duration L, the UE does not transmit the PUSCH in the transmission occasion.

For both Type 1 and Type 2 PUSCH transmissions with a configured grant, when K>1, the UE shall repeat the TB across the K consecutive slots applying the same symbol allocation in each slot, except if the UE is provided with higher layer parameters cg-nrofSlots-r16 and cg-nrofPUSCH-InSlot-r16, in which case the UE repeats the TB in the repK earliest consecutive transmission occasion candidates within the same configuration. A Type 1 or Type 2 PUSCH transmission with a configured grant in a slot is omitted according to the conditions in Clause 11.1 of [TS38.213].

For transport block repetition for uplink transmissions of PUSCH repetition Type B with a configured grant

The procedures described in this Clause apply to PUSCH transmissions of PUSCH repetition type B with a Type 1 or Type 2 configured grant. For PUSCH transmissions with a Type 1 or Type 2 configured grant, the nominal repetitions and the actual repetitions are determined according to the procedures for PUSCH repetition Type B defined in Clause 6.1.2.1. The higher layer configured parameters repK-RV defines the redundancy version pattern to be applied to the repetitions. If the parameter repK-RV is not provided in the configuredGrantConfig, the redundancy version for each actual repetition with a configured grant shall be set to 0. Otherwise, for the nth transmission occasion among all the actual repetitions (including the actual repetitions that are omitted) of the K nominal repetitions, it is associated with (mod(n−1,4)+1)^thvalue in the configured RV sequence. If a configured grant configuration is configured with Configuredgrantconfig-StartingfromRV0 set to ‘off’, the initial transmission of a transport block may only start at the first transmission occasion of the actual repetitions. Otherwise, the initial transmission of a transport block may start at the first transmission occasion of the actual repetitions if the configured RV sequence is {0,2,3,1}, any of the transmission occasions of the actual repetitions that are associated with RV=0 if the configured RV sequence is {0,3,0,3}, any of the transmission occasions of the actual repetitions if the configured RV sequence is {0,0,0,0}, except the actual repetitions within the last nominal repetition when K≥8.

For any RV sequence, the repetitions shall be terminated after transmitting K nominal repetitions, or at the last transmission occasion among the K nominal repetitions within the period P, or from the starting symbol of a repetition that overlaps with a PUSCH with the same HARQ process scheduled by DCI format 0_0, 0_1 or 0_2, whichever is reached first. The UE is not expected to be configured with the time duration for the transmission of K nominal repetitions larger than the time duration derived by the periodicity P.

FIG. 2 is an example illustration 200 of two received cancellation indications for the low priority CG UL transmission according to possible embodiments. The following embodiments may incorporate the above embodiments. DFI indicates ACK for the low priority UL transmission and DCI (HP) schedules a high priority UL transmission overlapping with the low priority UL transmission. The length of each repetition can be configured by higher layer signalling, where the higher layer is higher than the physical layer.

In an example situation, the UE has received a DCI scheduling a high priority, (HP) UL transmission, where the high priority UL transmission overlaps with repetition Rep ‘W’ of a low priority (LP) configured grant UL transmission shown in the illustration 200, and has received a DCI comprising CG-DFI indicating a valid ACK for a transport block of a corresponding HARQ process number being transmitted in the low priority CG UL transmission. Repetition Rep ‘W’ can be a repetition of ‘K’ repetitions. At least some of the following embodiments can define a UE procedure/behaviour to cancel the low priority UL transmission. In some embodiments, the DCI scheduling a high priority UL transmission can be the DCI activating at least one configured grant type 2 transmission. In one example, the configured grant Type 2 PUSCH transmission can be semi-persistently scheduled by an UL grant in a valid activation DCI according to Clause 10.2 of TS 38.213 after the reception of higher layer parameter configuredGrantConfig not including rrc-ConfiguredUplinkGrant.

In a first embodiment, the UE cancels the low priority UL transmission according to the termination/cancellation timeline associated with the earlier received DCI, such as the DCI scheduling high priority UL transmission in case 1 and the DCI carrying DFI in case 2 of the illustration 200.

According to example, in case 1, the UE can cancel repetition Rep ‘W’ in the middle of the repetition (according to the timeline Tproc2+d) since the UE has received DCI (HP) scheduling the high priority transmission earlier than DFI and may have already started cancellation procedure due to DCI (HP). The UE can cancel the PUSCH repetition Rep ‘W’ transmission corresponding to the configured grant that is partially or fully overlapping in time with the HP PUSCH/UL transmission scheduled by a PDCCH at latest starting M symbols (e.g., M=T_proc,2+d₁) after the end of the last symbol of the PDCCH carrying the DCI scheduling the HP PUSCH/UL transmission. Also, all repetitions after Rep ‘W’ can be cancelled due to reception of DFI with a valid ACK for a transport block of a corresponding HARQ process associated with the LP configured grant PUSCH transmission.

In case 2, the UE can cancel repetition Rep ‘W’ from the beginning of the repetition and all other repetitions after repetition Rep ‘W’ since the UE has received DFI sooner than DCI (HP). The UE can be expected to terminate the Rep ‘W’ repetition of the transport block in the LP configured grant PUSCH transmission starting from a symbol j if the gap between the end of CG-DFI PDCCH of symbol i and the start of the PUSCH transmission in symbol j is equal to or more than N2 symbols (in one example, ‘N2’ is defined in clause 6.4 of TS 38.214).

In a second embodiment, the UE cancels the low priority UL transmission according to the earliest time possible for cancellation, e.g., termination/cancellation timeline associated with any DCI among the two received DCI that results in the earliest termination/cancellation of the LP configured grant PUSCH transmission.

According to an example of the illustration 200, for both case 1 and case 2, the UE can cancel repetition Rep ‘W’ from the beginning of the repetition and all other repetitions after Rep ‘W’ since the earliest time for cancellation is the start of repetition Rep ‘W’.

In a third embodiment, the cancellation timeline/requirement corresponding to CG-DFI reception is updated from ‘N2’ symbols to ‘T_proc,2+d1’ (or the same as the cancellation timeline/requirement for reception of DCI scheduling high priority UL transmission). According to an example of the illustration 200, the UE can cancel the low priority UL transmission according to the earliest received DCI (DFI or DCI (HP)). In an example, the cancellation timeline/requirement corresponding to DFI reception can be updated from ‘N2’ symbols to ‘T_proc,2+d1’ (or the same as the cancellation timeline/requirement for reception of DCI scheduling high priority UL transmission) when the UE expects to receive a DCI scheduling high priority UL transmission, such as when the UE is configured to monitor a DCI format that can schedule high priority UL transmissions (e.g., via using a priority index Priority indicator field configured in the DCI format, or a higher layer parameter priority configured for configured grant PUSCH transmission).

In a fourth embodiment, the DCI scheduling the high priority UL transmission (e.g., DCI with a field indicating high priority for the scheduled UL transmission), can also indicate DFI for the low priority UL transmission that overlaps with the scheduled high priority transmission. Such embodiment could be useful in case the UE misses the standalone DFI (CG-DFI). Presence of a field indicating DFI in DCI (HP) can be configured. In one example, if the UE is configured to monitor a DCI format that can indicate priority of an UL transmission, a field associated with that DCI format can be configured to indicate DFI for a low priority UL transmission. In one example, if the UE is configured to monitor a DCI format that can indicate priority of an UL transmission, a field associated with that DCI format can be configured to indicate DFI/acknowledgment for the most recent low priority UL (e.g., configured grant PUSCH) transmission. In one example, if the UE is configured to monitor a DCI format that can indicate priority of an UL transmission, a field associated with that DCI format can be configured to indicate DFI/acknowledgment for the most recent high priority UL transmission (e.g., configured grant PUSCH). In one example, if the UE is configured to monitor a DCI format that can indicate priority of an UL transmission, a field associated with that DCI format can be configured to indicate DFI/acknowledgment for an UL transmission (e.g., the most recent configured grant PUSCH) having the same priority as the indicated priority. In one example, a UE can be configured to monitor a DCI format that can indicate DFI/acknowledgment for an UL transmission (e.g., the most recent configured grant PUSCH) of high priority.

In one example, DFI field in the DCI format (HP) can be set to ACK only for a low priority UL transmission overlapping the scheduled HP UL transmission (ACK is not applicable to other non-overlapping LP UL transmissions). For instance, the LP UL repetition overlapping with the HP transmission can be cancelled. However, the rest of UL repetitions that do not overlap with the HP UL transmission may not be cancelled if not ACK'ed. Also, receiving an ACK can eliminate the need of any autonomous re-transmission. In one example, the HP UL transmission can be a PUCCH transmission corresponding to a HARQ codebook with high priority.

In one example, in the illustration 200, for case 1, if the DCI (HP) indicates ACK for the low priority transmission, repetition Rep ‘W’ can be cancelled from the beginning of the repetition W (e.g., if ‘N2’ is considered as the timeline for termination of the low priority transmission due to DFI reception).

In one example, if a configured grant UL transmission of a UE (e.g., repetition Rep ‘W’) overlaps with a PUCCH transmission (e.g., of lower priority); PUCCH can be dropped and the UCI on PUCCH can be transmitted/piggy backed on repetition Rep ‘W’. If the UE has a configured grant UL transmission overlapping with a PUCCH transmission (e.g., PUCCH overlaps with repetition Rep ‘W’ of the configured grant); and if the UE has received a DFI with a valid ACK for the TB corresponding to a HARQ process associated with the configured grant UL transmission, at least a certain number of symbols (e.g., ‘N2’ symbols) before repetition Rep ‘W’, one of the following embodiments/mechanisms can be applicable. According to a first embodiment, the PUCCH can be cancelled and repetitions starting from repetition Rep ‘W’ can be terminated. According to a second embodiment, the PUCCH may not be cancelled and repetitions starting from repetition Rep ‘W’ can be terminated. According to a third embodiment, the PUCCH may not be cancelled, if DFI with valid ACK is received certain time before repetition Rep ‘W’ (e.g., N2+delta, where delta can be a UE capability); and repetitions starting from repetition Rep ‘W’ can be terminated. According to a fourth embodiment, if a HP UL transmission also overlaps with repetition Rep ‘W’, PUCCH can be cancelled and UCI of PUCCH can be multiplexed on the HP UL transmission if a UCI multiplexing timeline is satisfied; and repetitions starting from repetition Rep ‘W’ can be terminated.

In one embodiment, the UE can cancel the low priority UL transmission according to the earliest cancellation time that is not earlier than the cancellation time determined in response to receiving a high priority UL grant.

In some examples, the embodiments described above can also be applicable for case of a high priority PUCCH UL transmission instead of a DCI scheduling a high priority (HP) UL transmission. The PUCCH UL transmission can be scheduled via a DCI scheduling the associated DL transmission. The PUCCH can be transmitted by the UE in response to the scheduled DL transmission.

The embodiments above can also be applicable for the case that the UE has received an UL CI instead of DCI (HP). UL CI can be a DCI indicating a set of resources and UE can cancel an UL transmission if it overlaps with the set of resources in time-frequency domain.

The UE can be configured to be able to start an initial transmission of a TB only from a first transmission occasion of the ‘K’ repetitions (′K′ can be configured or indicated in activation DCI in configured grant type 2) [e.g., when the higher layer parameter ConfiguredgrantconfigStartingfromRV0 set to ‘off’]. Alternately, UE can be configured to be able to start an initial transmission of a TB from some of the transmission occasions of the ‘K’ repetitions corresponding to RV0 according to rules defined in section 6.1.2.3.1 of TS 38.214.

In an embodiment, if the UE cancels/drops transmission of a low priority PUSCH in the first transmission occasion of the ‘K’ repetitions, e.g. due to reception of an UL grant scheduling high priority UL transmission or an UL CI indicating resources for cancellation, where the resources overlap with the first transmission occasion of the ‘K’ repetition; and if the UE is configured to start an initial transmission of a TB only from a first transmission occasion of the ‘K’ repetitions e.g., when the higher layer parameter ConfiguredgrantconfigStartingfromRV0 set to ‘off’; one of the following UE behaviors/procedures can be used. According to a first behavior, the UE does not transmit the TB in any of the transmission occasions of the ‘K’ repetitions. Alternately, according to a second behavior, the UE can transmit the TB in a transmission occasion (e.g., the next TO (transmission occasion) of the ‘K’ repetitions having an RV0 that is not cancelled e.g., due to overlap with high priority UL transmission or UL CI indication) of the ‘K’ repetitions of the TB associated with RV0. The UE can be configured by RRC between the two behaviors. Also, the UE can be indicated in the UL grant scheduling high priority data on whether to use the first or second behavior. A repetition associated with RV0 can be potentially decoded without need for any other repetition, whereas repetitions associated with other RVs may need a second repetition to be decodable.

In a related embodiment, the next TO of the ‘K’ repetitions that is not cancelled e.g., due to overlap with high priority UL transmission or UL CI indication, can be assigned RV 0 (or in an example, set to RV 0 by the UE), and the RV associated with the rest of the TOs can be derived based on the TO with assigned/set RV 0 (e.g., additionally based on a configured RV sequence—e.g., for the nth transmission occasion among K repetitions starting for the TO with assigned/set RV 0, n=1, 2, . . . , K, it is associated with (mod(n−1,4)+1)^thvalue in the configured RV sequence).

In a related embodiment, the UE may not be expected to be configured (a) with ConfiguredgrantconfigStartingfromRV0 set to ‘off’ and (b) to monitor a DCI that can schedule high priority UL transmission/a DCI that can indicate UL cancellation.

According to TS 38.214, the higher layer parameter cg-nrofPUSCH-InSlot-r16 provides the number of consecutive PUSCH allocations within a slot, where the first PUSCH allocation follows the higher layer parameter timeDomainAllocation, and the remaining PUSCH allocations have the same length and PUSCH mapping type, and are appended following the previous allocations without any gaps. The same combination of start symbol and length and PUSCH mapping type repeats over the consecutively allocated slots.

In a related embodiment, if multiple TBs can be transmitted in a configured grant (e.g., 1^stTB with ‘K’ repetitions in a first set of TOs of a first PUSCH allocation, and 2^ndTB with ‘K’ repetitions in a second set of TOs of a second PUSCH allocation of the consecutive PUSCH allocations); and if the UE is configured to start an initial transmission of a TB only from a first transmission occasion of the ‘K’ repetitions (e.g., ConfiguredgrantconfigStartingfromRV0 set to ‘off’); the UE can start an initial transmission of a TB only from a first transmission occasion of the ‘K’ repetitions of each PUSCH allocation of the consecutive PUSCH allocations.

At least some embodiments can provide mechanisms to determine the cancellation timeline when the UE has received a DFI indicating an ACK for the low-priority configured grant UL transmission with multiple repetitions; and received a PDCCH scheduling a high-priority UL transmission overlapping with at least one repetition of the low-priority configured grant UL transmission or an UL cancellation indication indicating resources overlapping with at least one repetition of the low-priority configured grant UL transmission.

According to a possible embodiment, a method can be performed at a device. The method can include receiving a configured grant configuration comprising resources for uplink data transmissions. The method can include preparing a PUSCH (UL data) transmission corresponding to the configured grant; wherein a TB associated to a HARQ process is prepared to be repeated ‘K’ times in a first set of resources associated to the PUSCH. The method can include receiving a first DCI. The first DCI can indicate an ACK for the HARQ process corresponding to the TB. The method can include receiving a second DCI indicating a second set of resources. The first set of resources and the second set of resources can overlap in the time domain. The method can include determining a first cancellation/termination/dropping time associated to the prepared PUSCH based on the reception of the first DCI. The method can include determining a second cancellation/termination/dropping time associated to the prepared PUSCH based on the reception of the second DCI. The method can include determining a third cancellation/termination/dropping time associated to the prepared PUSCH based on the determined first cancellation/termination/dropping time and determined second cancellation/termination/dropping time. The method can include cancelling/terminating/dropping the prepared PUSCH according to the third cancellation/termination/dropping time.

The prepared PUSCH can be associated with low priority and the second DCI can schedule an UL transmission associated with high priority. The device can cancel/terminate the low priority PUSCH according to the earliest cancellation/termination time that is not earlier than the cancellation/termination time determined in response to receiving the second DCI. The second DCI can indicate the ACK for the HARQ process corresponding to the TB of the low priority prepared PUSCH. The second DCI can be associated with a DCI format corresponding to UL cancellation indication. The third cancellation/termination/dropping time can be the first cancellation/termination/dropping time when the first DCI is received before or not later than the second DCI. The third cancellation/termination/dropping time can be the second cancellation/termination/dropping time when the second DCI is received before or not later than the first DCI. The third cancellation/termination/dropping time can be the smaller/shorter/sooner of the first cancellation/termination/dropping time and the second cancellation/termination/dropping time. The device can cancel/terminate the prepared PUSCH according to the earliest time resulting in cancellation/termination of the prepared PUSCH.

FIG. 3 is an example flowchart 300 illustrating the operation of a wireless communication device, such as the UE 110, according to a possible embodiment. At 310, a configured grant configuration comprising resources for uplink data transmissions can be received. The first set of resources can be from the resources for uplink data transmission in the configured grant configuration. At 320, a PUSCH transmission corresponding to the configured grant configuration can be prepared. The PUSCH transmission can be for uplink data. A TB of the PUSCH transmission can correspond to a HARQ process. The TB can be prepared to be repeated a number, ‘K’, of times in a first set of resources configured for the PUSCH transmission.

At 330, a first DCI can be received. The first DCI can indicate an ACK for the HARQ process corresponding to the TB. The first DCI indicating the ACK can be DFI. At 340, a second DCI can be received. The second DCI can indicate a second set of resources. The first set of resources and the second set of resources can overlap in the time domain. The second DCI can be received before or after the first DCI. The PUSCH transmission can be a low priority PUSCH transmission and the second DCI can schedule a high priority UL transmission. There could be a priority index in the scheduling DCI scheduling a PUSCH transmission or a configuration parameter indicating a priority index for a configured grant PUSCH transmission.

At 350, a cancellation time associated with the PUSCH transmission can be determined based on both the received first DCI and the received second DCI. The determined cancellation time can be an absolute cancellation time or can be a time period until cancellation of the PUSCH transmission. At 360, the PUSCH transmission can be cancelled according to the cancellation time. Cancelling the PUSCH transmission can include cancelling the PUSCH transmission after it has already started. For example, at least one repetition of the PUSCH transmission can be transmitted and the remaining repetitions can be cancelled.

According to a possible embodiment, the determined cancellation time can be based on an earliest cancellation time that is not earlier than a cancellation time determined in response to receiving the second DCI. According to a possible embodiment, the second DCI can indicate the ACK for the HARQ process corresponding to the TB of the PUSCH transmission. According to a possible embodiment, the PUSCH transmission can include UCI. The UCI can be transmitted in the second set of resources.

According to a possible embodiment, the second DCI can have a DCI format that indicates UL cancellation. The indicated UL cancellation can be applicable to at least one repetition of the TB. According to a possible embodiment, determining the cancellation time can include determining the cancellation time associated with the PUSCH transmission as a cancellation time based on the earliest received DCI of the first DCI and the second DCI.

According to a possible embodiment, the first DCI can have a first associated cancellation time and the second DCI has a second associated cancellation time. Determining the cancellation time can include determining the cancellation time to be the first associated cancellation time when the first DCI is received before or not later than the second DCI and can include determining the cancellation time to be the second associated cancellation time when the second DCI is received before or not later than the first DCI. According to a possible implementation, determining the cancellation time can include determining the cancellation time to be an earliest cancellation time resulting from the first associated cancellation time and the second associated cancellation time when the first DCI is received at the same time as the second DCI.

According to a possible embodiment, the cancellation time can be a third cancellation time. A first cancellation time associated with the PUSCH transmission can be determined based on the reception of the first DCI. A second cancellation time associated with the PUSCH transmission can be determined based on the reception of the second DCI. The third cancellation time can be an earliest cancellation time resulting from the first cancellation time and the second cancellation time. Also, a time from the reception of the first DCI to the first cancellation time can be the same as the time from the reception of the second DCI to the second cancellation time.

According to a possible embodiment, the cancellation time comprises a third cancellation time. A first cancellation time associated with the prepared PUSCH can be determined based on the reception of the first DCI. A second cancellation time associated with the PUSCH transmission can be determined based on the reception of the second DCI. The third cancellation time can be determined based on the third cancellation time not being earlier than the second cancellation time.

According to a possible embodiment, the first DCI can be received not earlier than a certain time prior to the end of a repetition of the PUSCH transmission, wherein the certain time is provided by the configured grant configuration. For example, CG-minDFI-delay, a RRC parameter, can indicate an earliest time the DFI can be sent/received with respect of the end of any repetition of a PUSCH transmission.

According to a possible embodiment, determining the cancellation time can include determining a cancellation time of a repetition of the PUSCH transmission based on both the received first DCI and the received second DCI. Cancelling the PUSCH repetition can include cancelling the repetition of the PUSCH transmission according to the cancellation time. One or all of the repetitions of the PUSCH transmission can be cancelled.

It should be understood that, notwithstanding the particular steps as shown in the figures, a variety of additional or different steps can be performed depending upon the embodiment, and one or more of the particular steps can be rearranged, repeated or eliminated entirely depending upon the embodiment. Also, some of the steps performed can be repeated on an ongoing or continuous basis simultaneously while other steps are performed. Furthermore, different steps can be performed by different elements or in a single element of the disclosed embodiments. Additionally, a network entity, such as a base station, transmission and reception point, mobility management entity, or other network entity, can perform reciprocal operations of a UE. For example, the network entity can transmit signals received by the UE and can receive signals transmitted by the UE. The network entity can also process and operate on sent and received signals.

FIG. 4 is an example block diagram of an apparatus 400, such as the UE 110, the network entity 120, or any other wireless communication device disclosed herein, according to a possible embodiment. The apparatus 400 can include a housing 410, a controller 420 coupled to the housing 410, audio input and output circuitry 430 coupled to the controller 420, a display 440 coupled to the controller 420, a memory 450 coupled to the controller 420, a user interface 460 coupled to the controller 420, a transceiver 470 coupled to the controller 420, at least one antenna port 475, such as at least one antenna, coupled to the transceiver 470, and a network interface 480 coupled to the controller 420. The apparatus 400 may not necessarily include all of the illustrated elements for different embodiments of the present disclosure. The apparatus 400 can perform the methods described in all the embodiments.

The display 440 can be a viewfinder, an LCD, an LED display, an OLED display, a plasma display, a projection display, a touch screen, or any other device that displays information. The transceiver 470 can be one or more transceivers that can include a transmitter and/or a receiver. The audio input and output circuitry 430 can include a microphone, a speaker, a transducer, or any other audio input and output circuitry. The user interface 460 can include a keypad, a keyboard, buttons, a touch pad, a joystick, a touch screen display, another additional display, or any other device useful for providing an interface between a user and an electronic device. The network interface 480 can be a USB port, an Ethernet port, an infrared transmitter/receiver, an IEEE 1394 port, a wireless transceiver, a WLAN transceiver, or any other interface that can connect an apparatus to a network, device, and/or computer and that can transmit and receive data communication signals. The memory 450 can include a RAM, a ROM, an EPROM, an optical memory, a solid-state memory, a flash memory, a removable memory, a hard drive, a cache, or any other memory that can be coupled to an apparatus.

The apparatus 400 or the controller 420 may implement any operating system, such as Microsoft Windows®, UNIX®, LINUX®, Android™, or any other operating system. Apparatus operation software may be written in any programming language, such as C, C++, Java, or Visual Basic, for example. Apparatus software may also run on an application framework, such as, for example, a Java® framework, a .NET® framework, or any other application framework. The software and/or the operating system may be stored in the memory 450, elsewhere on the apparatus 400, in cloud storage, and/or anywhere else that can store software and/or an operating system. For example, coding for operations can be implemented as firmware programmed into ROM. The apparatus 400 or the controller 420 may also use hardware to implement disclosed operations. For example, the controller 420 may be any programmable processor. Furthermore, the controller 420 may perform some or all of the disclosed operations. For example, at least some operations can be performed using cloud computing and the controller 420 may perform other operations. At least some operations can also be performed computer executable instructions executed by at least one computer processor. Disclosed embodiments may also be implemented on a general-purpose or a special purpose computer, a programmed microprocessor or microprocessor, peripheral integrated circuit elements, an application-specific integrated circuit or other integrated circuits, hardware/electronic logic circuits, such as a discrete element circuit, a programmable logic device, such as a programmable logic array, field programmable gate-array, or the like. In general, the controller 420 may be any controller or processor device or devices capable of operating an apparatus and implementing the disclosed embodiments. Some or all of the additional elements of the apparatus 400 can also perform some or all of the operations of the disclosed embodiments.

In operation, the apparatus 400 can perform the methods and operations of the disclosed embodiments. The transceiver 470 can transmit and receive signals, including data signals and control signals that can include respective data and control information. The controller 420 can generate and process the transmitted and received signals and information.

According to a possible embodiment, the transceiver 470 can receive a configured grant configuration comprising resources for uplink data transmissions. The controller 420 can prepare a PUSCH transmission corresponding to the configured grant configuration. A TB of the PUSCH transmission can correspond to a HARQ process and can be prepared to be repeated a number, ‘K’, of times in a first set of resources configured for the PUSCH transmission. The transceiver 470 can receive a first DCI. The first DCI can indicate an ACK for the HARQ process corresponding to the TB. The transceiver 470 can receive a second DCI indicating a second set of resources. The first set of resources and the second set of resources can overlap in the time domain. The controller 420 can determine a cancellation time associated with the PUSCH transmission based on both the received first DCI and the received second DCI. The controller 420 can cancel the PUSCH transmission according to the cancellation time.

According to a possible embodiment, the PUSCH transmission can be a low priority PUSCH transmission and the second DCI can schedule a high priority UL transmission. According to a possible embodiment, the determined cancellation time can be based on an earliest cancellation time that is not earlier than a cancellation time determined in response to receiving the second DCI. According to a possible embodiment, the second DCI can indicate the ACK for the HARQ process corresponding to the TB of the PUSCH transmission. According to a possible embodiment, determining the cancellation time can include determining the cancellation time associated with the PUSCH transmission as a cancellation time based on an earliest received DCI of the first DCI and the second DCI.