| | | |
|---|
|
|
| |
| OWL setup |
| Resources can support two ONAP installations, e.g. Dublin and El Alto.
Objectives: 1) Support ONAP/ORAN PoCs in Dec, 2) EL Alto / Frankfurt testing progress for OOF-SON. |
| Dec ONAP/ORAN PoCs |
| Versions: ONAP (a) Dublin+ & b) El Alto+) , ORAN Amber Demonstrations: a) SDNR control of RAN PNF of RAN using ORAN O1 interface (netconf/yang),
b)PNF/PlunPlay Stretch goal: Respond to RAN info
(e.g. accept VES alarm from RAN, engage ONAP CL (e.g .Collector, DCAE, Policy, SDNR) and
demonstrate SDNR action)
|
| OOF-SON Frankfurt
CM notification flow |
| See slide:
3a.
(new) VES msg with CM change from RAN-SIm goes to VES Collector
4a.
VES Collector publishes to DMaaP (existing)
(new) SDNR listens to DMaaP msg for CM msg
(existing) SDNR updates RCDB
(new) SDNR publishes RCDB change notification to MS
4b. SON MS gets change notification (existing)
4d. SON MS reads RCDB (existing. old flow calls this 4b) |
|
|
|
|
|
|
|
|