Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

DESCRIPTION

A Mobile Service Provider (SP) plans to deploy VoLTE services based on SDN/NFV.  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 management (stretch goal)

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

Topology Diagram is shown:

Image Added

The flows are at the base page.xx


ROADMAP - Use Case Evolution per Release

...

RELEASELink to Use Case
R1 AmsterdamUse Case: VoLTE(approved)

R2 Beijing

Use Case proposal: VoLTE for R2
R3 CasablancaNo Further development on this Use Case
R4 DublinNo Further development on this Use Case
R5 El AltoNo Further development on this Use Case
R6 FrankfurtNo Further development on this Use Case
R7 GuilinNo Further development on this Use Case
R8 HonoluluNo Further development on this Use Case
R9 IstanbulNo Further development on this Use Case
R10 JakartaNo Further development on this Use Case

PRIOR BASE PAGE

If a Prior "Base page" exists for this Use Case you can use it instead of this page or link to it.The base page is at: Use Case: VoLTE(approved)

KEY LINKS & KEY INFORMATION

...

This table has overview slides of the Use Case and presentations or demos

TopicDescription
Overview Slides

Overview Presentation

Demo