User Space SMO/Non-RT RIC Framework O-CU O-DU O-RU Tester Tester «INT» OTF «INT» OTF «OAM» Message-Router «OAM» Message-Router «SMO» VES-Collector «SMO» VES-Collector «OAM» OAM-Controller «OAM» OAM-Controller «NonrtRIC» Link Monitor «NonrtRIC» Link Monitor «SMO» DHCP «SMO» DHCP «INT» CA «INT» CA O-CU-CP O-CU-CP O-DU-High O-DU-High O-DU-Low O-DU-Low O-RU O-RU Begin Use Case 1 Edit DU Config to disable CUS 2 «O1» Edit-Config 3 «FAPI» Link Stop 4 «FAPI» Link Status 5 «F1c» Cell Status 6 edit-config Complete 7 200 OK 8 «FHMP» Alarm Notify (Link Failure) 9 «O1» Fault Notify (Fault) 10 Publish Fault Notification (Fault) 11 Get Event (Fault) Alarm Triggered seek Clear Detect 12 Get Event (Fault) 13 Filter for CUS Link Failure alarm alt [if Link Failure Detected] Act 14 ODU Config for Link Enable 15 «O1» Edit-Config CUS Link Establishment See processing block on ODU Init 16 edit-config Complete 17 200 OK 18 «FHMP» Alarm Notify (Clear) 19 «O1» Fault Notify (Clear) 20 Publish Fault Notification (Clear) Verify 21 Get Event (Clear) 22 Use Clear to Verify Loop Action Successful 23 Get Event (Clear) 24 Test Complete
1 Comment
Martin Skorupski
Regarding flow #8 - Alarm Notify Link Failure
I'd like to propose using o-ran-fm:alarm-notif/fault-id = 30 (interface fail) according to O-RAN WG4 M-Plane v4 - See annex A.
The detailed mapping to ves:fault is described in wiki o-ran-fm:alarm-notif to ves:fault#MappingtoVESfaultfields