Date
Attendees
- Shrinivas Joshi
- Vidhu Shekhar Pandey
- David Kinsey
- LoreLei Rouvrais
- Alexandru Stancu
- Kiran Ambardekar
- John Keeney
- Santanu De
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
Time | Item | Who | Notes |
---|---|---|---|
5 min | Agenda bashing | All | |
15 min | O1/VES interface | All |
|
15 min | O1 interface | All |
|
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
Martin Skorupski
Regrading
Please see https://www.o-ran.org/specifications
O-RAN Operations and Maintenance Interface 4.0 - November 2020
Please see chapter “2. management services”
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.