Date

Attendees

Goals

  • Discuss O1/VES interface
    • VES format - 7.2 vs 7.2.1?
    • VES interfaces
      • InfluxdB
      • Elasticsearch API
      • Kafka Bus
  • Discuss O1 interface
    • REST APIs
    • Post NETCONF notifications as VES events

Discussion items

TimeItemWhoNotes
5 minAgenda bashingAll
15 min O1/VES interface All 
  • Updated the team on the status of the O1/VES implementation.
  • Testing of different event type continues. Testing for both version 7.2 and 7.2.1 event types.
  • Presented the proposal of SMO supporting a Kafka bus. 
    • John Keeney suggested that a DMaaP agent might need to sit on the Kafka bus to convert the events into DMaaP format??
  • Martin Skorupski mentioned "CORS error when using elasticsearch.js" when using two external browsers trying to perform queries over Elasticsearch.
  • Link to the simulator shared by Alexandru Stancu can be found here.
15 minO1 interfaceAll
  • The O1 interface on the SMO is up, and was tested against the SIM put together by Alexandru Stancu . It currently shows/supports the O-DU, O-RU-FH and the Hello World YANG model exposed by the simulator.
  • Next step is verify the O1 session with the O-DU in the OSC lab.
    • Vidhu Shekhar Pandey updated the team on the status of the O-DU supporting the O1 interface. 
    • user-165cf send e-mail on the status of O-DU in the OSC lab.

Action items

  • Shrinivas to validate that the O1/VES interface is able to receive both a VES format version 7.2 and 7.2.1 message.
  • Alexandru Stancu where can one find a list of events supported by the SIM?
  • Martin Skorupski, is there a comprehensive list of events the O1/VES interface needs to support?
  • bhanu chandra to confirm if the O1 implementation that he is developing for SMO have ability to support Call Home.
  • bhanu chandra to test the SMO O1 interface against the O-DU in the OSC lab.

1 Comment

  1. Regrading

    • Martin Skorupski, is there a comprehensive list of events the O1/VES interface needs to support

    Please see https://www.o-ran.org/specifications

    O-RAN Operations and Maintenance Interface 4.0 - November 2020

    Please see chapter “2. management services”

    • Notify AVC
    • Notify creation
    • Notify deletion
    • Notify changes
    • Fault
    • PM
    • File-ready
    • Trace streaming
    • heartbeat
    • pnfRegistration

    The 3GPP notifications bodies are defined in 3GPP TS 28.541 V16.6.0; 5G NRM, 5GC NRM.

    According to the O-RAN OAM IF spec the ves header is optional to support pure 3GPP notification syntax.