You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Name of Use Case:

VoLTE on vEPC

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 configuration automatically (future)
  • 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:

  • assuring the overall network performance
  • the reliability and serviceability of the ONAP platform itself
  • security
  • policy driven configuration management using standard APIs or scripting languages like chef/ansible
  • automated configuration audit and change management


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


Users and Benefit:

< who would benefit from this use case, how and under what scenarios >

VNF:

< list the VNFs this use case will automate/impact/use, be both generic like EPC and specific in terms of software used e.g. which EPC code or vendor product>

Work Flows:

< describe the work flows which are part of the use case. E.g. Instantiation, Deletion of VNF >

Controll Automation:

< describe any control automation that is part of the use case E.g. auto scaling, auto fault detection or recovery>

Project Impact:

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

Work Commitment:

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


  • No labels