Versions Compared

Key

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

...

Extend EPC capabilities with vSGW and vPGW. Demonstrate how to use a hybrid (PNF+VNF) solution using ONAP

Image Added


Version 0: no automatic legacy configuration. Deployment on a single OpenStack data-center based with no SDNC

...

VNF should be compliant with APP-C and DCAE using Netong/Yang for configuration and VES or SNMP for event collections


V0

On-boarding/Design phase

The ONAP designer onboards the VNF descriptors, define the Directed Graphs for the 2 VNF and the legacy MME for configuration and defines the service.

The ONAP designer defines a simple policy rule: to scale vPGW on the basis of the number of sessions and configure the MME to take into account the new vPGW

 

Open questions:

  • do we need to describe the PNF in the SDC ?
  • how to plug the legacy MME management solution to APP-C ?

 

Deployment phase

The ONAP-operating deploys the vEPC service.

As a result, one vSGW and one vPGW are deployed using SO and APP-C and updating AAI.

 

Closed loop

Triggered on a number of sessions, the policy engine executes the rule that triggers the SO to instantiate a new vPGW and will the APP-C to configure both the vPGW and the MME.

V0

On-boarding/Design phase

The ONAP designer onboards the VNF descriptors, define the Directed Graphs for the 2 VNF and the legacy MME for configuration and defines the service.

The ONAP designer defines a simple policy rule: to scale vPGW on the basis of the number of sessions and configure the MME to take into account the new vPGWImage Added

Users and benefits:

...