Date
Attendees
Agenda
Jakarta Requirements - - CCSDK-3532Getting issue details... STATUS
Jakarta Requirements - DCAEGEN2-2986Getting issue details... STATUS
Notes
Item | Who | Notes |
---|---|---|
Jakarata Release | 11/08 - SON Use Case Jakarata plan presented in Requirements Subcommittee on 11/08/20201 call Jakarta release - functional requirements proposed list#5GOOFSONUseCase | |
CCSDK-3532 | ||
DCAEGEN2-2986 (PM VES formats) | Discussion focused on PM VES messages. Thanks to information from Martin and Alex. There is very relevant work in O-RAN WG10. See https://oranalliance.atlassian.net/wiki/spaces/OAMWG/pages/2227307301/PM+Coordination+Team In particular, see the Excel table with a list of PM metrics relevant to O-RAN FCAPS There is consensus in ONAP/OSC/O-RAN to use VES stndDefined domain. We believe that this will be acceptable to 3GPP and O-RAN. stndDefined domain Note that the sample PM message uploaded in - DCAEGEN2-2986Getting issue details... STATUS does not have a schema and is thus incomplete. Note that OSC smo project is using VES measurement domain now but wants to move to stndDefined. Lot of detail about PM metrics and schema have been added in comments in - DCAEGEN2-2986Getting issue details... STATUS There are two approaches to provide a reference to the metrics to the systems processing the PM VES message: 1) Current OSC approach: VES message refers to schema and yang model which points to the measurements in the VES message payload 2) Current ONAP approach: VES message assumes that a PM Dictionary is loaded initially and this provides a reference for the measurements in the VES payload. This is supported by the ONAP VES Collector. In either case, there is more work needed to align with the PM metrics being defined in O-RAN WG10 (based on 3GPP). | |