Architecture Choice for Frankfurt

For Frankfurt release, our architecture scope is to implement CSMF and NSMF within ONAP, while connecting to an external Core NSSMF.

(To know more about the architecture choice, you can go for here: Use Case Description and Blueprint)


Proposed Functions:

From NSI lifecycle manamgement point of view, in this release, we will implement functions in below red box, which includes NSI design and pre-provision, NSI instantiation and configuration, and NSI activation and deactivation.

In particular:

  • CSMF: Functions of slice service creation, slice service activation and deactivation, slice service deletion are implemented.
  • NSMF: Functions of NSI instantiation, NSI activation and deactivation are implemented. In addition, manual intervention is also provided in NSMF slice task management portal to ensure the selected NSI/NSSI as well as ServiceProfile and SliceProfile are fine or need adjustment.
  • Design of CST, NST and onboarding NSST that are required to support the run-time orchestration functions is also provided.
  • To connect to the external (core) NSSMF, an adaptor is implemented to provide interface between ONAP and 3rd party core NSSMF.

Impacted Modules

Click the related modules below to know more details about the impacts and interfaces .


  • No labels