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 1Edit DU Config to disable CUS 2«O1» Edit-Config 3«FAPI» Link Stop 4«FAPI» Link Status 5«F1c» Cell Status 6edit-config Complete 7200 OK 8«FHMP» Alarm Notify (Link Failure) 9«O1» Fault Notify (Fault) 10Publish Fault Notification (Fault) 11Get Event (Fault) Alarm Triggered seek Clear Detect 12Get Event (Fault) 13  Filter for CUS Link Failure alarm alt[if Link Failure Detected] Act 14ODU Config for Link Enable 15«O1» Edit-Config CUS Link Establishment See processing block on ODU Init 16edit-config Complete 17200 OK 18«FHMP» Alarm Notify (Clear) 19«O1» Fault Notify (Clear) 20Publish Fault Notification (Clear) Verify 21Get Event (Clear) 22  Use Clear to Verify Loop Action Successful 23Get Event (Clear) 24Test Complete

  • No labels

1 Comment

  1. 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