e. Does roaming need to be supported? Roaming is a need for macro networks deployed by service providers as an end subscriber coming in from another location may need access to the network. However, it is not necessary to have a roaming design for enterprise networks such as an IoT network or a factory floor as there won't be a possibility of device mobility outside of the region. Hence, the investment in SEPP that may be necessary for supporting a robust roaming architecture can be avoided. Does it need to support enterprise networks? Most service providers have a requirement to support enterprise networks. The most important concern for enterprises is their data security and isolation. Hence, while planning support for enterprise networks in a macro environment, considerations should be made about how to implement a VPN and how to separate the traffic of each enterprise not only in the routing domain but also end-to-end in the data center. Does it need to interact with legacy networks? Interworking is a key aspect of network design. If the network needs to support seamless handover between 4G and 5G, considerations can be made about implementing an N26 interface between MME and AMF, which would lead to faster handovers while increasing the complexity of the network greatly in terms of configuration, call flows, debuggability, and maintenance. Does it need to interwork with Wi-Fi? Wi-Fi is a great augmenting technology as it takes the load off a mobile network operator. Voice and video calls over Wi-Fi have been supported widely since 4G networks. However, interwork seamlessly with Wi-Fi, an interworking function needs to be introduced that would act as the gateway between Wi-Fi and mobile network traffic, also translating the control plane signaling between the two for compatibility. Does it need to support network slicing? Network slicing is a great feature introduced in 5G. It has caused a lot of excitement in enterprises, many of which are requesting a separate slice for their traffic. 5G Standalone Networks