The SMO O1 controller based on ONAP CCSDK/OpenDaylight exposes northbound a ResConf API for Software Management derived from O-RAN Fronthaul M-Plane.
This page shows the steps for a µServer northbound of the O1-controller implementing Software Management functions on SMO.
Please see the RestConf API generated from YANG by ODL: https://sdn-r-dev.open5g-test.com/apidoc/apis/mounts/2/o-ran-software-management(2019-06-05)
O-RAN Members please see Chapter 5 "Software Management" - https://www.o-ran.org/s/O-RAN-Fronthaul-Specifications-v20-2019-07.zip
Please see attached bash example to retrieve the Software-Inventory.
O-RAN RU Fronthaul Software Management SMO Network User User Software Manager(µService) Software Manager(µService) Message Bus(ONAP DMaaP) Message Bus(ONAP DMaaP) O1-Controller(ONAP-CCDSK/SDNC) O1-Controller(ONAP-CCDSK/SDNC) O-RAN RU(managed-function) O-RAN RU(managed-function) Initialization [01]manual VES subscription (automated VES subscription under discussion between O-RAN and 3GPP) [02]Subscribe and poll for VES [03]Establish NetConf Session Start [04]provide new software packages for managed-function [05]trigger software update [06]"GET-software-inventory of device" [07]"<get-config><software-inventory>" [08]"list of <software-inventory>" [09]"list of <software-inventory>" [10]Inform about software inventory [11]"Analyse situation" File transfer [12]trigger software-download [13]trigger software-download [14]trigger software-download STATUS [15]trigger software-download STATUS [16]Inform about software download status [17]FTPeSstart download [18]FTPeSFile tranfer (software package) [19]download-event "COMPLETED" [20]download-event "COMPLETED" [21]Inform about software download status Installation [22]trigger software-install [23]trigger software-install [24]trigger software-install STATUS [25]trigger software-install STATUS [26]Inform about software install status [27]install-event "COMPLETED" [28]install-event "COMPLETED" [29]Inform about software install status Activation [30]trigger software-activate [31]trigger software-activate [32]trigger software-activate STATUS [33]trigger software-activate STATUS [34]Inform about software activate status [35]activate-event "COMPLETED" [36]activate-event "COMPLETED" [37]Inform about software activate status Verification [38]"GET-software-inventory of device" [39]"<get-config><software-inventory>" [40]"list of <software-inventory>" [41]"list of <software-inventory>" [42]Inform about software inventoryLicenseApache 2.0Thanks to plantUml!2020-03-07 | onap.org | o-ran-sc.org
This solution is expected to work with minimal or no incremental systems development for all vendors with RUs that comply with O-RAN WG4 Open FH M-Plane specification ... more to follow wrt O1 spec for SWM
1 Comment
Tracy Van Brakle
This solution is expected to work with minimal or no incremental systems development for all vendors with RUs that comply with O-RAN WG4 Open FH M-Plane specification ... more to follow wrt O1 spec for SWM