SDN-R interfacing with Configuration & Persistency Service

Design Principals

• the entire communication between SDN-R and CPS is via DMaaP
• an exception might be when SDN-R uses CPS as lookup DB to complete a request to the network (lookup)

ONAP internal data  vs. Network Function specific data

For backup or Initial (startup) configuration CPS could store the configuration data according to the Network Function (VNP, PNF) specific data models. 

Such data is most likely not abstracted to be used for multi-vendor, multi-layer, multi-technology use cases and should/could not be used by µServices addressing such use cases.

Multi-vendor, multi-layer, multi-technology µServices require an abstract view of the network. Therefore a translation service is required to translate between ONAP internal data models and Network Function specific data models.