Before editing please read instructions here.

 Description of Use Case / Requirement:

The Network CM Proxy (NCMP) is a component in CPS that will be responsible for Network CM access and synchronization in order that CPS CM data will be maintained aligned with CM data in the network (e.g. xNF instances). The complete solution will rely on integration with other ONAP components such as SDNC. The Network CM Proxy will also in turn provide an interface to other ONAP applications to access the network CM data.

NCMP is an evolution of the CPS NF Proxy component first introduced in Rel H. For release I it is proposed to continue work on use cases such as initial data synchronization and reading and writing network CM data:

• Adding and removing xNF instances based on inventory change
• Sync network model and data (initial and re-sync)
• Pass-through read and write data
• Read cached model or data

Some NCMP functionality listed above has been deferred until next release. See https://wiki.onap.org/display/DW/CPS-333+Network+Configuration+Management+%28NCMP%29+scope+for+I+release+considerations for details.

 CPS Temporal service is a distinct CPS component that brings historical view on CPS data.
It aims to provide to its clients the knowledge about how network configuration or state evolves over time.
It can support analytic application that need to detect trends from historical data for closed loop use cases for example.

API Impact

It is expected that some new APIs will be added to CPS components as part of this work. Some existing APIs may also be deprecated.

Owners (one of these should be the Assignee - use @ notation):

eoskmal JunfengWang micbev

Link to HLD/LLD (if any):

https://wiki.onap.org/display/DW/CPS-333+Network+Configuration+Management+%28NCMP%29+scope+for+I+release+considerations

Dependency Relationships with Other Projects:

 CPS

• Impact Type: C
• Company Engagement: Ericsson
• Resources:
• Support Status: Supported
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

SDNC

• Impact Type: TO
• Company Engagement: Ericsson
• Resources:
• Support Status: S/P/N (Supported/Partially supported/Not supported)
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

AAI

• Impact Type: TO
• Company Engagement:
• Resources:
• Support Status: S/P/N (Supported/Partially supported/Not supported)
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Integration Leads (use @ notation): 

tragait