Name of Use Case:

Use Case Authors:

combination of use cases proposed by (in alphabetical order):

AT&T, China Mobil, Ericsson, Metaswitch Network, Orange

Description:

A Service Provider (SP) plans to deploy VoLTE services based on SDN/NFV.  In particular it want's to deploy the VoLTE service on a vEPC.  

The SP is able to onboard the service via ONAP. Specific sub-use cases are:

• Service onboarding
• Service configuration 
• Service termination
• Auto-scaling based on fault and/or performance
• Fault detection & correlation, and auto-healing
• Data correlation and analytics to support all sub use cases
  
  

ONAP will perform those functions in a reliable way. Which includes:

• the reliability, performance and serviceability of the ONAP platform itself
• security of the ONAP platform
• policy driven configuration management using standard APIs or scripting languages like chef/ansible (stretch goal)
• automated configuration audit and change managementmanagement (stretch goal)

To connect the vEPC ONAP different Data centers ONAP will also have to interface with legacy systems and physical function to establish VPN connectivity in a brown field deployment.

Users and Benefit:

SPs benefit from this use case through design, onboarding, and agile deployment. Through the ONAP platform, the resource can be utilized effectively, and the management can be intelligent.

VNF:

Utilize vendors VNFs in the ONAP platform.

Project Clearwater VNF, comprising

Work Flows:

Customer ordering

• Instantiation
• Termination

Auto-scaling

• VNF scaling out / in

Auto-healing

• Auto-reboot / auto-restart including reducing faults, misconfigurations (in routers for instance)

Telemetry

• Resource layer
• Service layer

Controll Automation:

• Auto-scaling

When a large-scale event, like concert, contest, is coming, the service traffic may increase continuously, the monitoring data of service may grow higher, or other similar things make the virtual resources located in TIC edge become resource-constrained. ONAP should automatically trigger VNF actions to scale out to add more virtual resource on data plane to cope with the traffic. On the contrary, when the event is done, which means the traffic goes down, ONAP should trigger VNF actions to scale in to reduce resource.

• Fault detection & correlation, and auto-healing

During the utilization of VoLTE service, it may produce some fault events, no matter what factors impact the service. ONAP should detect these fault and report to the system to do the correlation. The timely detection and accurate correlation of faults is one of the important factors to do the automatic platform. After the fault detected and correlated, ONAP should do the auto-healing to make the system back to normal. 

Open Loop

• Auto ticket creation based on the policy

Closed Loop

• Horizontal scaling to support add or remove machines into the pool of resources
• Vertical scaling to support add or remove resources (ex. CPU, Memory, Storage) from existing virtual machines
• Self-healing: auto adjust computing resources based on the pre-fixed date and time (ex. Mother’s Day or Black Friday) or by analyzing future trends based on the data feed of upcoming sports events or concerts
• ?Stretch goal?

Configuration flows (Stretch goal)Configuration flows

• Create (or onboard vendor provided) application configuration Gold standard (files) in Chef/Ansible server
• Create Chef cookbook or Ansible playbook (or onboard vendor provided artifacts) to audit and optionally update configuration on the VNF VM(s)
• Install the Chef client on the VM (Ansible doesn’t requires)
• After every upgrade or once application misconfiguration is detected, trigger auditing with update option to update configuration based on the Gold Standards
• Post-audit update, re-run audit, run healthcheck to verify application is running as expected
• Provide configuration change alert to Operation via control loop dashboard

Fault Recovery:

• For each module in ONAP
  • Introduce a failure case, and demonstrate the recover. The failure case may be particular to the module ,however killing a virtual machine or container and allowing the system to recover is a good example.

Software upgrade

• For each module in ONAP
  • Upgrade a software component and demonstrate continued operation.

Project Impact:

< list all projects that are impacted by this use case and identify any project which would have to be created >

• Modeling
  Modeling will need to be added to describe how VNFs are to be instantiated, removed, healed (restart, rebuild), scaled, how metrics related are gathered, how events are received

Modeling will need to be added to describe the connection service (underlay/overlay) between cloud Edge and Core.

• 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/SDN Agent
  Add logic to support to provision the underlay and overlay connection service between clouds, including 3^rd party commercial SDN controllers. 
• DCAE
  Support statistics collection on the VoLTE case and receipt of events as per the new model
• VNF

Support to integrate with S-VNFM/S-EMS to fulfill the NS lifecycle management and configuration.

• VFC and DCAE
  Support more complex control loops
• SO/SDNC/ SDN Agent/VFC
  Monitor the service to verify the all NSs/VNFs have been executed, and update A&AI. 
• A&AI
  Support the new data model
• Policy
  Support new policy related to the scaling and healing in VoLTE use case
• Multi-VIM
  Support multiple VIMs 

Work Commitment:

< identify who is committing to work on this use case and on which part>