uture realized. Automated detection and notification for specific use cases including international call fraud, registrations failing, no dial tone, and call storm detection is also supported. 14.5 TOPICS FOR FUTURE STUDY With the initial deployment of virtualized services, there were some major learnings in the areas of resiliency. Virtualized services need to have a heavy emphasis on recovery from cloud failures. Also, virtualized services need to be deployed in a highly distributed fashion across multiple geo- resilient sites in order to meet the reliability needs of a service. As an example, a service must be deployed minimally at four sites in order to meet five 9's availability to account for downtimes resulting from cloud upgrades. Services must support the ability to redirect traffic from a site for cloud upgrades and the ability to gracefully shut down specific VNFs at a site. Fully qualified domain names (FQDNs) must be supported for routing traffic to VNFs in order to enable this. At the time of writing, some areas of consideration for virtualized service instantiations are in the Internet of things (IoT) and other novel services enabled by 5G, distributed placement of services, next generation access agnostic core, cloud solutions, standards, database evolution, and efficiency of control loops. The current forecast of nearly 20 billion IoT units by 2020 forces the network operator to look at service enablement of IoT services at scale, which entails Enabling agile creation of vertical solutions via service-specific overlays. Leveraging SDN/NFV to enable designing reusable common network/platform capabilities. Using SDN/NFV and decomposition/composition of VNFs for a modular architecture. Using network slicing and service-specific instantiation to minimize the overall cost per service. Using API exposure via a mature common service enablement platform to create and deliver broad IoT enablement services. Leveraging common service enablers (e.g., voice, video, etc.) and light-weight technologies (e.g., W