d therefore does not have this issue. In the uplink, there is a half-tone shift between the uplink and downlink for eMTC and NB-IoT. To support this in 5G, an optional half-tone shift was introduced. This optional shift, however, is not supported in all 5G bands, and some bands will have a half-tone misalignment. Although this introduces some interference, it can be managed by the network and does not prevent deployment of eMTC and NB-IoT on frequency bands without half-tone shift support. In Release 16, several enhancements are being studied to further improve the coexis- tence performance: Better coexistence with dynamic TDD operation in 5G: In 5G, each slot can be dynamically allocated for the downlink or uplink. However, eMTC and NB-IoT can only support LTE uplink-downlink TDD configurations which can be changed on a semi-static basis. This would either restrict how 5G TDD can be deployed, or very large guard bands around the eMTC/NB-IoT carrier would be required to minimize uplink-downlink interference. Both approaches will reduce the 5G system performance. One existing eMTC/NB-IoT feature that can be used to provide better coexistence with dynamic TDD in 5G is to use the invalid subframe bitmap. This bitmap can be used to mark a subset of eMTC/NB-IoT subframes as invalid for transmission/reception. These subframes can then be used on a dynamic basis by 14.11 loT Optimizations in 5G 5G without any restriction. Further enhancement can be considered in Release 16. For example, dynamic TDD subframe formats can be introduced for Release 16 eMTC/NB-IoT UE. Legacy eMTC/NB-IoT UEs will see this subframe marked as invalid, while Release 16 and beyond NB-IoT UEs can take advantage of the new formats. In Release 16, standalone deployment for eMTC is being specified. This will enable the use of the LTE control channel region for downlink control and data transmission. For the control channel, some of the existing symbols will be repeated in the legacy control region. For the data channel, rate matching will be used to 