ervices code point (DSCP) markings by VNFs are used to maintain quality of ser- vice for specific traffic types (media, signaling, OA&M) routed in the cloud environment. 14.4.1.3.9 Licensing The mechanism of a universal license key or a pool of licenses provided by VNF vendors is used to enable automated instantiation, automated recovery, and scaling of traffic in a cloud environment. 14.4.1.3.10 Common NPaaS Services Common platform services are provided by the NPaaS layer of SDSF and include the following: DNS services that can be used to distribute traffic Cloud databases that can be used to store application and network subscriber data Cloud databases that can be used to store state data Load balancers that can be used to distribute load to the VNFs vTaps services that can be used for probes 14.4.1.3.11 VNF Catalog list of reusable VNFs that are added to the VNF catalog for IMS service implementations is shown below: Application subscriber database State persistence database Access signaling SBC Access media SBC Building the Network of the Future Interconnect signaling SBC Interconnect media SBC Transcoding Audio conferencing MRF Video conferencing MRF HSS-FE HSS-BE Virtualized probes 14.4.1.3.12 Integration with ONAP With the virtual services control loop framework and integration with ONAP capabilities, the fol- lowing critical automation capabilities are designed and engineered for virtualized IMS service platforms: 1. Rapid service creation and orchestration 2. All VNFs will send fault and performance data directly to the DCAE component of ONAP 3. DCAE will support performance reports and data collection from VNFs, PNFs, and vTaps for performance monitoring and fault management 4. Universal license keys or pools of licenses will be supported to enable auto-scaling 5. Auto-recovery will be supported for all VNFs via closed-loop automation Elasticity will be provided initially by triggers from operations and with control loop auto- mation for scaling actions based on predictive analysis and preprovisioned b