The page will discuss and document the necessary yang modules to be supported by O-DU to ensure the end-to-end functionality of the D-Release use case "Closed loop".
As O-RAN alliance does not provide solid yang models yet, other data models needs to be defined or selected.
Idea
From SMO point of view the O-DU should provide a capability to "manage" the expected NetConf Server connections (O-RAN OpenFronthaul M-Plane) representing O-RUs.
The O-RU will connect via NetConf Call Home/TLS to the O-DU. Therefore the O-DU must be configured in advance with the public key of potential O-RUs.
Exactly this function is implemented by the OpenDaylight project and YANG modules to mimic a potential O1 interface are available.
However, OpenDaylight also supports pre-configured NetConf servers with all its connection related details and NetConf Call Home via SSH. Those parameters and object classes could be ignored for the O-RAN-SC D-Release Use Case.
All the YANG modules can be found in the attachments:
File
Modified
Minimum parameter set to be supported
The following yang tree shows only a necessary (to be discussed) selection of parameters within the yang capabilities of OpenDaylight forconfiguration and supervision of NetConf Servers by a NetConf Client (O-DU).