...
O-DU modules are developed as shown in the below diagram.
O-DU High Thread Architecture
...
O1 Module
O1 Architecture
As shown in the figure O1 module runs as a thread in O-DU High. Alarm communication happens over a Unix socket between the O1 and O-DU threads. O1 module uses API calls for interacting with the Netconf server(Netopeer) and datastore(sysrepo) for providing the Netconf interface.
O1 architecture has following components:
Netconf Session Handler: Subscribe to Netconf YANG modules and events. Register callback handler methods.
VES Agent : Sends the VES events to SMO
Alarm Manager: Stores and manages(add/updated/delete) alarms.
Alarm Interface : Provides an interface to O-DU High threads for sending the alarm messages to O1 module over Unix socket.
Config Interface : Interface to handle the configurations sent from SMO to the stack
Netopeer server: Serves the northbound SMO/OAM Netconf requests.
O-DU-High Interfaces
This section describes the other modules that O-DU High interfaces with, as shown in below diagram.
...