Alternatively, a PRACH or a Msg3 (i.e., RRC connection request message) of the RACH procedure may always be transmitted irrespective of semi-static UL resource split. Accordingly, a PRACH transmission opportunity may be guaranteed, and the RACH procedure may be improved. If a resource is allocated to a different CG, the UE may omit data transmission in the different CG. If transmission of a PRACH/Msg3 in one CG collides with transmission of a PRACH/Msg3 in a different CG, transmission of a master CG or first CG may be prioritized. In a similar manner, HARQ-ACK transmission corresponding to a Msg4 (i.e., collision resolution message) of the RACH procedure may also be prioritized over other transmissions. That is, in general, the semi-static UL resource split may be applied only to a data and SRS related procedure, and PRACH/Msg3 transmission and related HARQ-ACK feedback may be transmitted with a higher priority irrespective of the semi-static UL resource split.
According to the PRACH/Msg3 transmission and related HARQ-ACK feedback transmission, the omitted PUSCH/PUCCH may be immediately retransmitted when UL is available. In addition, to guarantee a PRACH transmission opportunity in NR, a resource may be configured in a last symbol (which may be an SRS symbol). To realize this, the semi-static UL resource split may not be configured between different CGs before the RACH procedure is not complete. However, the semi-static UL resource split may be configured between different CGs even before the RACH procedure is complete. The aforementioned method may be applied when there is switching between UL transmissions each having a different TA.