Enterprise vCPE use case requirement November 6, 2017

E-vCPE Business drivers Enterprise customers would benefit from cloud services and automation either on-premises or in the cloud depending on their branch configurations. This will free the enterprise users from the installation, local configuration and administration of LAN/NAT/WAN/VPN networking. SPs would benefit from a more flexible platform to provide more kinds of virtual services. To implement the configuration remotely will help SPs reduce complexity of the service deployment and cut down the OPEX. The centralized traffic scheduling and optimization of backbone network is the embodiment of SDN concept in backbone network, it will help operators enhance the management ability of operation and maintenance and improve the efficiency of resource utilization. Authors: China Telecom, Huawei, ZTE, ARM

E-vCPE Usecase Description This use case is mainly used for the Enterprise Service Provider (SP) to provide the Site2site service to the tenants both efficiently and safely by deploying enterprise-based vCPE. Enterprise users could receive high-quality and cheap cloud service based on the operator’s BSS Portal and ONAP. And in here, ONAP is used to instantiate and operate the required vCPE in the access network as a cloud service. For the application scenarios of E-vCPE use case, it supports site-to-site, site-to-DC and site-to-Internet services to the customers. It not only provides the solution of ThinCPE and vCPE in the edge-DC but also CPE solution as an alternative choice for enterprise customer. The solution of vCPE in the edge-DC is an actual deployment scheme which can provide more value-added service in DC and make it easy for access control. In this case, ONAP will present its function to instantiate, configure and manage both the overlay connection between site-to-site/DC/Internet and VNFs . There are two alternative ways to set up overlay connection, including VxLAN and IPSec. It is a stretch goal to fulfill traffic scheduling in WAN network by means of path calculation and load balancing.

E-vCPE Fusion Architecture

E-vCPE related wikipage Use case description and usecase flows: https://wiki.onap.org/display/DW/Use+Case+proposal%3A+Enterprise+vCPE Use case requirement list: https://wiki.onap.org/display/DW/Merged+list+of+R2+functional+requirement+candidates Service Capability Management(project proposal): https://wiki.onap.org/display/DW/Service+Capability+Management

Functional requirement Functional Platform Requirements Priority New / Enhancement Related components Comments R40. service onboarding 1 SDC, SO, AAI, DCAE, Policy R41. service data collection 2 SDN-C, DCAE,A&AI Statistics collection on vCPE/ link connection/ delay/bandwidth utilization/jitter/topology, etc. R42. Path Selection New SDN-C,DCAE, A&AI,PCE, policy Do the selection of different access SPs networks or different core networks( MPLS/Internet) within one SP. Multiple path algorithms or pre-set strategies are supported to calculate and adjust the forwarding path according to the collected network data from SDN-C or DCAE, A&AI. Then new forwarding path is deployed to the device to realize the path selection. R43. Service Capability Management MSB,A&AI,SO,SDC

R42. Path Selection Description: Analyze and trigger Policy PCE (Path Computation Element) is a module that aims to meet the path selection requirement. It is used to conduct the path calculation and load balancing for the ONAP network. In the current network, there are multiple vendor controllers along with different path calculation method. As for overlay ,PCE can do the selection of different access SPs networks or different core networks( MPLS/Internet) within one SP using the data collected and path calculation algorithm. Through the PCE, ONAP can also analyze data collected from PNFs thus acquiring the whole network topology and flow, and then conduct path calculation uniformly for traffic scheduling and load balancing for underlay. Collection and monitoring Path calculation Configuration and deployment Analyze and trigger Policy

R42. Path Selection Flows 4.Invoke path selection

R42. ONAP Service Capability Instance Management Any dependencies on specific VNF capabilities --None VNFs that we would use to test the use cases --Any offered by ONAP Companies willing to contribute --China Telecom, Huawei, ZTE, ARM

R43. ONAP Service Capability Management Description: The Service Capability Management provides highly Identifiable, loose coupling and ready to be exposed service capability for ONAP SDC/SO with user-friendly, operator level Design time and Running time environment functions. The SCM also coming with a Graphical User Interface (GUI) to present logical correspond service capability list for the operators and end-users. SCM provides capability encapsulation based on the micro-services registered on MSB. SCM functions also includes design, administration, classification, cataloging, publishing, version management, access control , presenting for the above encapsulated service capabilities. SCM is facing service and end-user level, while micro service is facing system level. Target : Available service capability registration into SC catalogues through corresponded API Registered SC is managed / exposed to users with different levels.

R43. ONAP Service Capability Management How to support S3P Scalability: Service Capability Management (SCM) provides service capability management for the operators and end-users, and have enough scalability so as to adapt various operators and end-users. Security: Service Capability Management (SCM) adopts comprehensive and exclusive safety control system. The outside system needs to carry assigned token when they call service instance catalogues and the catalogues tree allows traverse from outside requests after result filter. Stability: Service Capability Management (SCM) provides efficient and stable 24*7 service to all users and adopts specific rules when establish the catalogues tree to ensure stability.

R43. ONAP Service Capability Management Platform requirements/dependencies, flows, identifying “what” High level architecture diagram Inner structure/inner modules of SCM Level Sequence Diagram of SCM

High level architecture diagram SCM

Inner structure of SCM Service Capability Management (SCM) uses a three-layer architecture to manage the service information. Coding rule: SCM assigns unique identification code for each directory item with the name of their textual name. System codes are assigned when the directory items are first built, and directory items name are provided by registration administrator. Then system codes of directory items are unique for the entire directory lifecycle. .（root） | -- First-level subdirectory |---- Second-level subdirectory |------ Service Capability item Service Capability directory and register items both adopt ‘(system coding, directory)’ to identify uniquely. The directory items are defined untidily by the directory Administrator. And the SC items can implement new, open, and undo through API after audit.

Level Sequence Diagram of SCM Service Capability Management Operators and end-users Root GUI Items First level subdirectory Second level subdirectory SCM SO SDNC Registration Proxy Service Gateway A&AI NFV Service Discovery MSB

A&AI-cloudInfrastructure Inner modules of SCM SDC Service API SO SCM Example for E-vCPE Service capability Design Time UI Running Time UI Resource Check L3VPN Service Name Path Admin SC1 URL1 Ver/… SC2 URL2 SC3 URL3 … Service Finder A&AI Cloud Service Auto Test Fault Tolerance …… Data Manager Micro Service SCM SDNC vnfres MSB A&AI-search vnfmgr A&AI-cloudInfrastructure Micro Service 1 Micro Service 1 Micro Service 1 ……

R43. ONAP Service Capability Management Any dependencies on specific VNF capabilities --None VNFs that we would use to test the use cases --Any offered by ONAP Companies willing to contribute --China Telecom, Huawei, ZTE, ARM

Thanks