Requirements
...
O1 RIC Health-Check (Flow #2)
Status
...
to be tested
Call flow diagram
| Expand |
|---|
| title | Click here to expand...(Copied from RSAC https: |
|---|
|
...
| //lf-o-ran-sc.atlassian.net/wiki/pages/viewpage.action?pageId=12517420) |
|
|
Delivery Status
|
| OTF | OAM | NONRTRIC | RICP | RICAPP | O-DU | Test Result | Notes |
| O1 RIC Heartbeat | 1. <<O1>> O1VES Keep Alive (RICP.O1 -> OAM) |
|
|
|
|
|
|
| RICP Heartbeat sent from VESPA |
| 2. <<O1>> O1Netconf get_config (OAM - |
< Healghy| Healthy/OK (RICP.O1 -> OAM) |
|
|
|
|
|
|
| netconf ssh connection keepalive |
| O1 RIC Health Status |
Retriebal| Retrieval | 4. Retrieve Health Status (OTF -> OAM) |
|
|
|
|
|
|
|
|
| 5. <<O1>> |
Neetconf | Netconf get alarm-list (OAM -> RICP.O1) |
|
|
|
|
|
|
|
|
| 6. <<O1>> Alarm-list (RICP.O1 -> OAM) |
|
|
|
|
|
|
|
|
| 7. Alarm list (OAM -> OTF) |
|
|
|
|
|
|
|
|
| O1 RIC On-Demand HealthCheck | 8. On-demand Healthcheck (OTF -> OAM) |
|
|
|
|
|
|
|
|
| 9. <<O1>> Perform Healthcheck (OAM -> RICP.O1) |
|
|
|
|
|
|
|
|
| 10. Request alarm update (RICP.O1 -> RICP.O1) |
|
|
|
|
|
|
|
|
| 11. Alarm update (RICP.O1 -> RICP.O1) |
|
|
|
|
|
|
| No alarm defined, may test manually with artificial alarm |
| 12. <<O1>> updated alarm-list (RICP.O1 -> OAM) |
|
|
|
|
|
|
|
|
| 13. Alarm List (OAM -> OTF) |
|
|
|
|
|
|
| Use sctp keep alive |
| 14. <<E2>> Missing heartbeat (RICP E2T to RICP O1) |
|
|
|
|
|
|
|
|
Test Manual