1. Background
CMNotify is a RESTFUL notification that supports the 3GPP fields defined for sending notifications when managed objects are created, deleted or modified. Any configuration changes (such as, neighbor list change) in the underlying RAN network will be communicated via CM REST notifications, and will trigger any follow-on activities, such as closed-loop automation (e.g. SON use cases). This is a POC effort to demonstrate how CM Notification could be supported in ONAP.
2. High-Level Architecture and Use Cases
Please refer to the presentation for detailed architecture considerations for CM Notification support. The below picture depicts the workflow for this POC effort.
The workflow:
3a: Publish CM Notification DMAAP message that includes relevant VES payload. For testing, DMAAP message will be published via Postman or CURL, onto CM-NOTIFICATION topic
4a: SDNR to consume DMAAP message, and trigger pertinent DG to update RuntimeDB/ConfigDB platform
4b: Update RuntimeDB/ConfigDB using REST API