O-RAN-SC OAM integration into ONAP by Martin Skorupski 2019-08 More questions than answers!

Input WG1 Some open space here, however OAM interface specification defines VES for FM, PM, and all events and NetConf/Yang for CM (read, write) 12/1/2019

Input WG2 12/1/2019

Infrastructure Management Framework Function split: A1 - O1 Service management & Orchestration Framework message bus Non-Real-Time-RIC FCAPS Framework O1* A1 O1 Infrastructure Management Framework VIM Near-Real-Time RAN Intelligent Controller (RIC) E2 O-CU-CP O-CU-UP WG1 color coding and WG2 content – no additional information – to be removed? E1 F1-c F1-u O-DU Open Fronthaul O-RU Infrastructure COTS / White Box / Peripheral Hardware & Virtualization layer ~NfVi 12/1/2019

O-RAN OAM integration in ONAP OOF Policy SO A&AI DCAE Portal AAF LOG ConfigDB DMaaP CCSDK/SDNC/Non-Real-Time-RIC CCSDK/SDNC/SDN-R (FCAPS) HV-VES Collector (FCPAS) VES Collector (FCPAS) O1* A1:REST O1:NetConf/YANG/CM O1:REST/VES/PM O1:REST/VES/CM, FM, others Infrastructure Management Framework VIM Near-Real-Time RAN Intelligent Controller (RIC) Standard VES collector for rare events like CM, FM. E2 O-CU-CP O-CU-UP E1 High Velocity VES collector (HV-VES) for real-time event streaming needed for PM. F1-c F1-u O-DU Open Fronthaul O-RU Infrastructure COTS / White Box / Peripheral Hardware & Virtualization layer ~NfVi 12/1/2019

Thank you very much! Martin Skorupski highstreet technologies System Architect O-RAN-SC: https://wiki.o-ran-sc.org/display/~demx8as6 ONAP: https://wiki.onap.org/display/~demx8as6 Skype: martin.skorupski WhatsApp: +49 172 317 04 88 E-Mail: martin.skorupski@highstreet-technologies.com Web: https://www.highstreet-technologies.com