...
The OAM architecture is defined by WG1 WG10 in the O-RAN OAM architecture document. WG2 clarified the function split between non-real-time-RIC and an Orchestrator FCAPS Framework. Please see the attached document.
Integration into ONAP
In the meeting from 2019-08-12 was clarified the expected integration of the OAM Architecture into ONAP.The ONAP VES collectors will receive the VES messages of the
O1
...
For NetConf interfacing with the different components, the functions of ONAP SDN-R will be used (subproject of SDNC and based on CCSDK)
O1 Component Architecture
According to the O-RAN-OAM-interface specification (O1) each MnS Provider (ME) implements a (TLS/)NetConf interface for Configuration Management and consumes TLS/HTTP-POST messages with a json body in VES message format.
The method for the VES subscription/un-subscription must be performed via NetConf, because VES itself does not provide such function. The MnS Consumer will use the NetConf interface for such an operation.
Figure
PlantUml
...
| title | Click here to view PlantUml code... |
|---|
...
...
Integration into SMO
In the meeting from 2019-08-26 was clarified the expected integration of the OAM Architecture into a Service Management and Orchestration Framework (SMO).
The VES collectors will receive the VES messages of the O1 interface.
