In a communication system supporting time division duplex (TDD), the number of UL symbols and/or FL symbols may be less than the number of symbols that a PUSCH instance has according to a slot pattern, configuration of a type0-PDCCH common search space set and control resource set (CORESET), and/or a pattern of synchronization signal/physical broadcast channel (SS/PBCH) block. When the PUSCH repetition type A is used, a PUSCH instance may not be transmitted, and a non-transmitted PUSCH instance may not be transmitted later. The number of PUSCH repetitions may not be readjusted, and the corresponding PUSCH instance may be considered as having been transmitted. When the PUSCH repetition type B is used, a PUSCH instance may be split into split PUSCH instances, and the split PUSCH instances may be transmitted. The split PUSCH instance may have a DM-RS.
When the repeated transmission according to the PUSCH repetition type A is performed in a communication system supporting TDD, the PUSCH instance may not be transmitted in some slots. The base station may perform dynamic scheduling for retransmission of the PUSCH instance that has not been transmitted. When there are many terminals intending to extend a coverage, many PDCCHs may be required. To solve this problem, an improved PUSCH repetition type A may be needed.
For convenience of description, the improved PUSCH repetition type may be referred to as a PUSCH repetition type C. The PUSCH repetition type C may be used for the purpose of extending a coverage. When the PUSCH repetition type C is used, a PUSCH instance may be transmitted on a slot basis. In order to reduce the amount of a PDCCH, the number of transmissions of the PUSCH instance may be guaranteed.