Requirements

RIC Self-Check (Flow #1)

Status

to be tested

Call flow diagram 


RIC Self-Check SMO O-RAN RIC O-RAN Managed Function (MF) «OAM»O1 «OAM»O1 «NONRTRIC»Non-RT RIC «NONRTRIC»Non-RT RIC «RIC»A1 MED «RIC»A1 MED «RIC»O1 TERM «RIC»O1 TERM «RIC»HealthCk Function «RIC»HealthCk Function «RIC»Platform Modules «RIC»Platform Modules «RICAPP»xAPPs «RICAPP»xAPPs «RIC»E2 TERM «RIC»E2 TERM «MF»Managed Function «MF»Managed Function MF = O-CU, O-DU Alarms from individual RIC Platform Modules and xAPPs Note: Apart from Health-Checks, a platform module or xAPP may generate an alarm (orits clearing) when it encounters a failure/error (e.g., failure to reach another module) 1Platform Module Alarm/Clear 2«O1VES» Alarm or Clear 3xAPP Alarm/Clear 4«O1VES» Alarm or Clear RIC Self-Checks @ Regular Intervals Support HealthCheck Telemetry (FM, Heartbeat, PM) RIC Self-Checks Initiated loop for each Platform Module 5Perform HealthCheck Support Platform Module HealthCheck 6HealthCheck Status 7Platform Module Alarm/Clear 8«O1VES» Alarm or Clear loop for each xAPP instance deployed 9Perform HealthCheck 10HealthCheck Status Support xAPP HealthCheck 11xAPP Alarm/Clear 12«O1VES» Alarm or Clear 13«E2» keep-alive Support E2 Test Message Processing 14«E2» missed heartbeat 15E2 Alarm/Clear 16«O1VES» Alarm or Clear 17Log HC results & updatealarm-list in yang model Support Alarm Retrieval from SMO, Dashboard


Delivery Status



OTFOAMNONRTRICRICPRICAPPO-DUTest ResultNotes
Alarms from individual RICP Modules and xApps1. Platform Module Alarm/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 Intervals5. 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 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

Test Manual

  • No labels