...
- Initiate an O1 Heartbeat test to ensure that the O1 is alive
- Retrieve the health of the RIC based on the last self-check performed, and/or
- Request an on-demand health-check.
Figure 2 shows the corresponding sequence flow diagram.
The O1 Heartbeat test will enable the NB client to check whether the O1 NetConf interface to the RIC is still alive. The heartbeat from the SMO could be implemented using the already defined NetConf session health-checks (regular <get-config> requests to the RIC to query the operational tree, filtering response to send just OK). This heartbeat method could also be extended beyond the RIC to other RAN resources supporting the O1 interface. [Steps 1-2 in Figure 2]
...
- A persistent O1 NetConf session has to be established between the NB client (SMO) and RIC, and the NB client has to subscribe to the corresponding topics to receive the Health-check related asynchronous notifications. [6-7 in Figure 2]
- When an On-Demand Health-check is invoked, the RIC responds with an acknowledgement once the RIC’s Health-Check function/module successfully initiated the RIC Self-Check flow described in the previous section. [8-9]
- As results of the RIC Self-Check from platform modules and xAPPs are gathered by the Health-Check function/module, they are stored in the O1 Termination and are sent asynchronously to the NB clients.Where there are failures and/or anomalies, alarms and alerts are also emitted via O1. [10]
- When the On-Demand Health-Check is completed with results sent to the NB client, the O1 NetConf session will be terminated. [11]
- The Operations user can now use the On-Demand health results to evaluate the health of the RIC.
Figure 2 shows the corresponding sequence flow diagram.
<<insert sequence diagram and plantuml syntax>>
...