Name of Use Case:      

Enterprise vCPE Use Case

Use Case Authors:

China Telecom

Description:

An Enterprise Service Provider (SP) plans to deploy enterprise-based vCPE to provide the Enterprise2DC service to the tenants conveniently and quickly. Enterprise users could receive high-quality and cheap cloud service by the operator’s BSS Portal and ONAP. ONAP is used to instantiate and operate the required vCPE in the access network as a cloud service.

The Operator should complete provisioning of the Network Infrastructure, and then setup the overlay network connection with VxLAN.

• The Operator: create MPLS-TP L2VPN and L3 Bridge in the IPRAN Network
• The Operator: create MPLS BGP L3VPN in the WAN Network
•  The Operator: connect the links through VLAN

Note: the allocation of underlay network is a stretch goal for Release 1.

Enterprise vCPE Scenario diagram as shown below:

Users and Benefit:

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.

VNF:

PNF

ONAP Flows:

• VNFs onboarding
• Service design
• Customer ordering
  • Instantiation
  • Per service activation
  • Cut service
• Self-service
  • Tiered bandwidth
  • Bandwidth on Demand(future)
  • Change internet access bandwidth
• Software management
  • Upgrade service
  • Upgrade a specific element (VNF) of the service
  • Delete service
• Scaling
  • Storage (future)
• Auto-healing
  • Automatic reboot/restart
  • Rebuild

Control Automation:

• Fault detection and correlation between L2-L3 connectivity services and Internet, E2E Link.

• Manage localized enterprise services by automatically performing the health check of the access connectivity, virtual switching/routing and auditing of service-related configurations

• Deliver high availability service requirements for emergency communications and surveillance services

• All control automation should be done on VNFs stood up in the operator’s cloud as well as on the CPE

Project Impact:

• Modeling
  The enterprise gateway will typically implement a proprietary VIM. Modeling will need to be added to describe how VNFs are to be instantiated, removed, healed (restart, rebuild), how statistics are gathered, how events are received
• SDC
  Add logic to use the new modeling when designing the service, and then distribute the resulting artifacts
• SO
  Add logic to understand the new artifacts; orchestrate/manage changes according to it
• SDNC
  Add logic to issue the proper commands to the CPE to support instantiation, chaining, configuration, healing, etc.
• DCAE
  Support statistics collection on the CPE and receipt of events as per the new model
• APPC and DCAE
  Support more complex control loops
• SO or SDNC
  Monitor the CPE to verify the all VNFs and chaining have been executed, and update A&AI. Is more granular information needed? (e.g. on which vServer each VNF is stood up)
• A&AI
  Support the new data model
• Policy
  Support new policy related to the connectivity to the CPE

Work Commitment: