Discuss closed loop automation use case for E-release that involves network slicing.
Notes
Can O-RAN SC use the two of the YANG models published by 3GPP? The two models are
3gpp-nr-nrm-nrcelldu.yang
3gpp-nr-nrm-rrmPolicyRatio.yang
A fallback option would be to augment the "hello" YANG model that OAM has used to include both a cell level and a du level definition for the nodes that define the CM.
Once decided, SMO/O1 team will publish the REST OpenAPI for the model.
API freeze for E-release comes up this Friday. Since we have not agreed on what YANG model can be used in O-RAN SC, it will be difficult to freeze on the API. Need an extension to the deadline.
The VES header format shared by santanu deis something that has been published by ONAP as version 7.2.1. However, O-RAN WG1 has defined the format with "stdDefined" which allows the sender to send a pointer to the schema definition that should be used to validate the event. What is that format?
The body of the measurement field will carry "measurementInterval" field, with the value set to 60s, in addition to the two fields, one for UL and DL throughput of the UE.
What will be used to generate the UE traffic for this use case? Hariom Guptashared that user-30c9dmight have a tool that can be used to generate the traffic.
Discussion items
Time
Item
Who
Notes
5 min
Agenda bashing
All
25 min
E-release closed-loop automation use case
Mahesh Jethanandani
Action items
Mahesh Jethanandanito bring up the issue in the next ToC meeting of whether O-RAN SC can use the 3GPP YANG model. In the same meeting, ToC needs to decide whether the API freeze date can be extended.
If O-RAN SC cannot use 3GPP model, Martin Skorupskiwill augment the "hello" YANG model to include the CM for a network slice both for the cell and for the O-DU, described in the two models above.
Martin Skorupski to share what the VES header format should look like for "stdDefined" that should be used to format a PM VES event.