Table of Contents |
---|
...
# | Issue | Notes | Decisions | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | CM VES Message format schema. Who will own it ? | In order to process the message DMI plugin / NCMP should be aware of the schema of the incoming message it is going to be consume. | VES format primary reference is here: [INT-2180] Define CM VES message aligned with 3GPP/O-RAN O1 - ONAP JIRA | |||||||||||||||
2 | Topic from where we will receive the CM VES Message. | Existing channel or channel owned by NCMP/DMI | Vishal Varvate to provide the topic details. Priyank Maheshwari ,please use below topic unauthenticated.SEC_3GPP_PROVISIONING_OUTPUT | |||||||||||||||
3 | Mapping of the relevant information from the CM VES Message
| Only fields that seem to suggest to have these info. are.
Related work in ONAP suggests this possible alternative schema: So wanted to confirm if measurements.measurement-type-instance-reference is xpath? | Mapping detailed below: VESEvent%E2%86%92DMIDataAVCMapping CM VES related details present in CM handling guide and
| |||||||||||||||
4 | DMI Data AVC Message |
| ||||||||||||||||
5 | Topic from NCMP-DMI-Plugin to NCMP | The producer is already configured. | Topic name : dmi-cm-events |
...