In the O-RAN-SC meeting 2019-08-12 was clarified the expected integration of the O-RAN-SC OAM Architecture into ONAP.

The ONAP VES collectors will receive the VES messages of the O1 interface. For real-time event streaming the ONAP project provide HV-VES.

For NetConf interfacing with the different components, the functions of ONAP SDN-R will be used (subproject of SDNC and based on CCSDK). 

  • No labels

7 Comments

  1. Sandeep Shah

    Hi Martin Skorupski  - I would appreciate if you can comment on the termination point for A1 interface in the Orchestration/NMS layer?  Thanks

    1. Martin Skorupski

      In O-RAN-SC is an agreement that A1 interface and O1/NetConf/Yang are terminated on ONAP CCSDK/SDNC bases. To my knowledge - today - there is no released A1 interface specification. (if somebody knows it better, please comment add the link to the A1 Interface specification)

  2. Damian Nowak

    HV-VES stands for "High Volume VES", volume, not velocity (wink)

  3. Haseeb Akhtar

    Martin Skorupski The northbound A1 interface functionally terminates in Non-RT-RIC function within the SMO (e.g., ONAP in this case). It is up to the SMO to decide as to how the Non-RT-RIC function is implemented. From that perspective (i.e., decided by ONAP/LF OSC), it will be okay to state that A1 interface can be terminated on ONAP CCSDK/SDNC bases. 

  4. Amar Kapadia

    Martin Skorupski does ONAP support OI* (or I guess the new name is O2)? I assume yes, because without it ONAP wouldn't be able to orchestrate vRAN xNFs?

    1. Martin Skorupski

      Hi Amar Kapadia , let me say it this way (wink) The support of O2 by ONAP would be a welcome contribution to ONAP. So the "yes" could be a target for Guilin(?) or Honolulu.

      1. Lasse Kaihlavirta

        I haven't seen O2 support mentioned in any shape or form in Honolulu plans or requirements yet beyond this page: Potential ONAP <-> O-RAN collaboration use cases

        ...and even there it's just mentioned as "Availability of O2 specification (stretch goal, needed beyond H-release)" for  REQ-440 - Getting issue details... STATUS  (and that requirement itself does not refer to O2 in any way)

        Martin Skorupski , are you aware of any actual plans to support O2 in Honolulu?