-blocks), to the service that must run on bare metal. Note that the latter could still benefit from orchestration from an operations perspective. The virtualized functions must have the capability to directly interact with INF or indirectly through MANO SO that the operation requirements (e.g. computation, Downloaded: 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 Virtualizing Network Functions in Software-Defined Networks storage, security, QOS, memory resources) and support requirements (monitoring, metering, and billing) can be identified. Their proposed Control Signal Processing Function Group will focus on authentication/authorization policy, state management, mobility, and mobility-related support functions, including call record collection and lawful intercept. Their proposed User Data Processing FG will focus on packet forwarding, duplication, counting, processing, load balancing, and application layer steering (i.e., proxy). Their proposed Data and Storage FG will focus on data storage and management. Network Function Virtualization vs. Cloud Implementations A demonstration was hosted at Telefónica's NFV Reference Lab, Madrid which provides two different deployment environments: An NFV-ready NFVI pool, with a Telefónica, developed NFV ready VIM implementing the requisite Enhanced Platform Awareness (EPA) and a Cyan NFV-Orchestrator which supports advanced VNF deployment using enhanced NFV information models. A standard cloud infrastructure pool ala classic cloud computing, with the same Telefónica VIM, connected to the same Cyan NFV-Orchestrator but not using the enhanced information model as the basis for the deployment. Optimized Deployment of Network Function Virtualization The correct NFV TOSCA model is used in the primary deployment whereas the VNFD models are used in secondary deployment. The information in the model facilitates the Planet Blue orchestrator to optimally deploy Brocade configuration through the Telefónica VIM. The result is the achievement of full line ra