Thus, only when a single PUSCH (or TB) is scheduled by the multi-slot DCI, the CBGTI field/signaling (related to the single PUSCH (or TB)) may be configured in the corresponding DCI. When a plurality of PUSCHs (or TBs) are scheduled by the multi-slot DCI, only (re)transmission on a TB basis may be performed for the plurality of PUSCHs (or TBs), instead of configuring the CBGTI field/signaling in the DCI. Considering the structure in which the presence or absence of the CBGTI field/signaling is determined depending on to the number of scheduled PUSCHs (or TBs) scheduled, a method of determining the payload size of the multi-slot DCI (format) may be required. The reason for this is as follows: a single PUSCH and a plurality of PUSCHs may be scheduled by the same DCI format (e.g., DCI format 0_1); if the payload size of DCI scheduling a single PUSCH is different from that of DCI scheduling a plurality of PUSCHs, the UE needs to attempt blind decoding by assuming that there are two types of DCI payload sizes; and as the number of DCI payload size related assumptions increases, the number of times of blind decoding increases, which may decrease DCI decoding performance. On the other hand, if the DCI payload size is always fixed to the largest possible size, overhead may increase more than necessary. Accordingly, the following methods may be considered. For convenience of description, some parameters are defined as follows.
N: N denotes the maximum number of PUSCHs (or TBs) schedulable by a single multi-slot DCI. N may be set by the RRC parameter pusch-TimeDomainAllocationList. The maximum number of schedulable PUSCHs may be set to, for example, one integer value from 2 to 8 (2≤N≤8, where N is an integer).
K: K denotes the number of PUSCHs (or TBs) actually scheduled by a single multi-slot DCI.