fied by DCI format 1 and PDSCH- ConfigCommon. The RAR window is configured by rar-WindowLength information element 628 Chapter 4 in a SIB message. If the UE successfully detects the PDCCH, it can decode PDSCH carry- ing the RAR message. After decoding the RAR message, the UE checks, if the random- access preamble ID (RAPID) in the RAR message matches the RAPID assigned to the UE. The PDCCH and PDSCH associated with the process are expected to use the same subcar- rier spacing and cyclic prefix as SIB1. Note that the gNB is not expecting any HARQ-ACK for the RAR message. The gNB may conclude that UE has successfully received and decoded the RAR message, if the UE does not retransmit PRACH, which would happen if the UE does not detect the DCI format 1_0 with CRC scrambled with the corresponding RA-RNTI within the RAR window, or if the UE does not correctly receive the transport block in the corresponding PDSCH within that window. In the third step, the UE must determine whether it should apply transform precoding for Msg3 on PUSCH, based on the RRC parameter msg3-transformPrecoder. The UE deter- mines the subcarrier spacing for Msg3 on PUSCH based on the RRC parameter SubcarrierSpacing in BWP-UplinkCommon. The UE then transmits Msg3 on PUSCH to the same serving cell to which it had sent the PRACH. In the fourth step, Msg4 is transmitted to the UE for contention resolution. The UE starts ra-ContentionResolutionTimer and monitors PDCCH with TC-RNTI while ra-ContentionResolutionTimer is running. The UE looks for the DCI in Type 1 PDCCH common search space. If the PDCCH is successfully detected, the UE proceed to decode PDSCH carrying the MAC control element, and at the same time, it sets the value of the C- RNTI to TC-RNTI and discards ra-ContentionResolutionTimer. The UE considers the RACH procedure as successfully completed. Once the UE successfully decodes Msg4 (con- tention resolution), it sends HARQ-ACK for the data (PDSCH carrying Msg4). In response to the PDSCH reception with the UE contention resolution identi