er, it may not be possible to align subcarriers for both 5G and eMTC/NB-IoT. In this case, 5G supports multiple bandwidth parts within the same carrier, where each bandwidth part can be configured with a different subcarrier spacing. This allows eMTC/NB-IoT to easily coexist with 5G even if they employ different numerology. In addition to supporting different bandwidth parts, 5G also support a resource reser- vation scheme. In this case, 5G can reserve time and frequency resources for deployment of eMTC and NB-IoT. This is done using a PRB-level bitmap in the frequency domain and a symbol-level bitmap with repetition pattern in the time domain. 5G UEs will ignore these reserved resources. This allows for efficient coexistence of eMTC/NB-IoT and 5G. For example, 5G resources can be reserved for always-on eMTC and NB-IoT signals and channels such as reference signals and broadcast channels. In addition, when there is no eMTC/NB-IoT data traffic, the gNodeB can schedule unused eMTC/NB-IoT resources to the 5G UE. Sixteen frequency bands have been specified in 3GPP that can support both 5G and eMTC, for example, Band 8 at 900 MHz. Twelve different frequency bands have been specified that can support both 5G and NB-IoT. So far, only 5G bands below 2.7 GHz support eMTC and NB-IoT deployment as high-frequency bands are not suitable for IoT services due to limited coverage. Almost all common 5G and eMTC/NB-IoT bands share a common 100 kHz raster, SO the raster grid for the two systems can be aligned. Band 41, however, supports the 5G channel raster of 15 and 30 kHz, SO there are limited locations where eMTC/NB-IoT with 100 kHz channel raster can be deployed. Although it is possible to align 5G and eMTC on the subcarrier level, it is not possible to align them on the PRB level on the downlink. This is because eMTC utilizes a direct current (DC) subcarrier, whereas 5G does not. This slight mismatch means than 1 addi- tional 5G PRB may need to be reserved for eMTC deployment. NB-IoT, however, does not have a DC subcarrier an