Sponsor(s): @nk.shankar@stl.tech

Synopsis:
The ONAP OOF-SON use case uses a Control Loop design for SON actions sent to RAN-Sim (simulated O-RAN network). Till Release 10, the actions were netconf configs aligned with O-RAN O1 interface. For Rel 11, the primary changes is that we are including support for O-RAN A1-based SON action in addition to O-RAN O1-based SON action. The approach has been to harmonize as much as possible with O-RAN SC work, leverage past ONAP work, and keep alignment between SON use case, Slicing use case, and other use cases.

There are small/medium changes to Policy so that O1 and A1 control loops will have separate control loop policies. We are leveraging ongoing A1 work in CC-SDK/SDN-C to continue work done for A1 support. There is a good amount of work in RAN-Sim to terminate A1 and build a RAN App abstraction.
We expect small changes to the SON-Handler MS in DCAE but perhaps little impact to DCAE platform.

ARCCOM Scheduled Review Date: June 07, 2022

Documents reviewed/referenced: ONAP_OOF_SON_R11_ArchitectureReview_20220606.pptx 

Test Plan:

Meeting Notes:

Committee Decision:

Reviewed and approved by ARCCOM on June 07, 2022