The next step for an MNO can be to switch to Option 7 by utilizing 5GC. As we have discussed previously, with Option 7, ng-eNBs are the master nodes providing access to the control and user planes. That means if you do not manage the control plane with gNBs, then you cannot fully exploit all the use cases even if you deploy 5GC. For instance, the URLCC use case has stringent network delay requirements. That means that to meet this requirement, you need to carry the control plane on gNBs and not on ng-eNBs because Option 7 requires the control plane carried by the ng-eNBs and forwarded to gNBs, which causes additional delays. So, the question is why would an MNO prefer Option 7 then? There are two reasons: The first one is there is still not enough 5G coverage nationwide and the MNO just wants to boost the user throughput and experience in hot-spot areas with 5G. The second one is the device ecosystem. More 5G SA devices and mobiles will be released day by day and MNOs should improve the customer experience with improved 5G services related to a 5GC deployment. 4G to 5G migration strategies The other option for an MNO is to deploy Option 2 only for local use cases with good 5G coverage and with 5GC to fully exploit 5G use cases. For instance, the MNO can deploy 5G SA options in stadiums to provide different 5G services, such as augmented and virtual reality. As another example, it could be a smart factory where the URLLC use case is fully exploited. The next migration exists by stepping into Option 4 when there is nationwide NR coverage. With this option, gNBs will be the master nodes managing the control and user plane. Therefore, 5G use cases and features such as URLLC, network slicing, or mMTC services would be fully exploited. The advantage of Option 4 here is to support 4G mobiles and devices as well. As a very long-term strategy, MNOs can switch to Option 2 solely nationwide and start releasing the 4G network step by step. This very long-term strategy depends on the existing frequencies and bandwidths that M