r virtual resources using automation (based on correlations performed during monitoring). In addition, the operations teams have the ability to intervene in the automation functions per- formed by ONAP during a VNF instance's lifecycle, via a real-time portal. 14.4.3 BVoIP SERVICES Most network functions for service platforms that support BVoIP services are also currently sup- ported on vendor-proprietary hardware. The physical implementation of the current AS complexes typically consists of a collection of commercially available hardware, including server blades in a chassis configuration, integrated with other supporting components such as layer 2 and layer 3 switches, external disk arrays, and load balancers. Most ASs run on a standard Linux operating Service Platforms AT&T Collaborate Service Complex Data Border Element (DBE) Network Border Gateway / Session Border Interconnect Session Device mgt Gateway (SBG) Border Controller Internet TDM (POTS) ATT Business Center Att.com/business Collaborate Log in, Other carrier IP Phone Device mgt. feature mgt networks Customer User integrated sales, billing, Collaborate Portal access, Web clients management, and Mobile App training portals via AT&T Business Center. FIGURE 14.22 AT&T Collaborate implementation. system, with the application software executing in either a commercially available AS container (e.g., IBM WebSphere, Tomcat/Apache), or in a vendor-provided package. AS complexes also typically include one or more database servers, again using commercially available database technology (e.g., Oracle) or a vendor-provided database. An AS complex configu- ration may consist of one or more instances of a variety of ASs and database types, each assigned to a specific blade server populated in a chassis. The strategy for virtualization of the network functions that support BVoIP services is based on needs for capacity enhancements, end-of-life hardware and software triggers, and new product needs. Design and implementation of the VNFs is in a manner that aligns with 