...
| OTF | OAM | NONRTRIC | RICP | RICAPP | O-DU | Test Result | Notes | ||
| Alarms from individual RICP Modules and xApps | 1. Platform Module ClarmAlarm/Clear (RICP.O1 -> OAM) | RIC implements Alarm system following: RIC Alarm System. In this implementation, alarms injected into Prometheus AlertManger from individual modules using Alarm Adapter. AlterManager pushes alarms to VESPA, then to VES collector entering SMO. No RIC component implemented such alarm reporting mechanism other than AlarmAdapter, a demo/testing CLI for manually injecting alarms into the system. | |||||||
| 2. <<O1VES>> Alarm or Clear(RICP.O1 -> OAM) | |||||||||
| 3. xApp Alarm/Clear (RICAPP -> RICP.O1) | |||||||||
| 4. <<O1VES>> Alarm or Clear(RICP.O1 -> OAM) | |||||||||
| RIC Self-checks @Regular Intervals | 5. Perform Healthcheck (RICP.O1 -> RICP.*) | RIC healthcheck is performed by Prometheus periodically polling components healthcheck API, no O1 involvement. Tested | |||||||
| 6. Healthcheck Status (RICP components -> RICP.O1) | O1 polling Prometheus Alert Manager tested. | ||||||||
| 7. Platform Module Alarm/Clear (RICP.O1 -> RICP.O1) | No platform component | ||||||||
| 8. <<O1VES>> Alarm or Clear(RICP.O1 -> OAM) | Problem: RIC deployment is not configured for completing this flow. | ||||||||
| 9. Perform Healghcheck Healthcheck (RICP.O1 -> RICAPP components) | |||||||||
| 10. Healthcheck Status (RICP components -> RICP.O1) | |||||||||
| 11. xApp Alarm/Clear | RICP: No alarm defined, may test manually with artificial alarm | ||||||||
| 12. <<O1VES>> Alarm or Clear(RICP.O1 -> OAM) | |||||||||
| 13. <E2> Alive (O-DU High -> RICP.E2T) | Use sctp keep alive, E2 Setup/response completed | ||||||||
| 14. <<E2>> Missing heartbeat (RICP.E2T to RICP.O1) | |||||||||
| 15. E2 Alarm/Clear (RICP.O1 -> RICP.O1) | |||||||||
| 16. <<O1VES>> Alarm or Clear(RICP.O1 -> OAM) | |||||||||
| 17. Log HC results and update alarm list in yang model | RICP: Logging implemented, not alarming |
...