...
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
https://www.rfc-editor.org/rfc/rfc8641
O1 CM Update Notification VES Message
SON Use Case Weekly Meeting Notes
Assumptions
# | Issue | Notes | Decisions |
---|---|---|---|
1 | VES Event is received via Strimzi/DMaap Kafka on DMI. | Yes. This is agreed. | |
2 | Changes in CM data will result in CPS-Core sending a CPS Data AVC irrespective the origin of the change. |
| Agreed. |
Issues & Decisions
# | 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 |
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? |
The fields which are of importance are :
- event.sourceId ( we can extract cmHandle details from the sourceId )
- moiChanges.operation
- moiChanges.path
- moiChanges.value
More information is present in the meetings recording.
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 |
- Is CMNotify Message same as CM VES Message and notify more about this if this is relevant.
The Big(ger) Picture
Gliffy Diagram | ||||
---|---|---|---|---|
|
...
Gliffy Diagram | ||||||||
---|---|---|---|---|---|---|---|---|
|
Analysis
|
VES Event → DMI Data AVC Mapping
VES Event | DMI Data AVC | Notes | |||||||
---|---|---|---|---|---|---|---|---|---|
# | Part | Field | Source | Sample Value | Part | Field | Source | Sample Value | |
1 | Header | eventId | 123435 | Header | eventId | DMI Plugin | 123435 | Has to be globally unique | |
2 | Header | eventTime | device | 2021-11-16T16:42:25-04:00 | Header | eventTime | VES Event | 2021-11-16T16:42:25-04:00 | TO BE DISCUSSED see open issue # |
3 | Header | sourceId | device | nearrtric-22_cucpserver2 | Header | eventSource | VES Event | device-123 | Upto DMI plugin to send. where it came from etc. |
4 | Header | sourceId | nearrtric-22_cucpserver2 | Header | eventCorrelationId | VES Event & Conversion | nearrtric-22_cucpserver2 | DMI PLugin need to map TBC | |
5 | Payload | path | ran-network:ran-network/NearRTRIC=22/GNBCUCPFunction=cucpserver2/ ran-network:ran-network/NearRTRIC=11/GNBCUCPFunction=cucpserver2/ | Payload | target | VES Event & Conversion | ManagedElement@[id='1']\Function[@id='SomeFunction'] ran-network:ran-network/NearRTRIC[@id="22"]/GNBCUCPFunction[@id="cucpserver2"]/ | DMI PLugin needs to convert FDN to XPath | |
6 | Payload | patch-id | DMI Plugin | 329cb2e3-b41a-4347-9884-f15457f426a1 | Unique ID generated by DMI-Plugin | ||||
7 | Payload | operation | device | 'replace' | Payload | operation | VES Event & Conversion | 'replace' | DMI PLugin needs to map |
The DMI Data AVC Payload is defined by https://www.rfc-editor.org/rfc/rfc8641
Value Copied VES Event | Transformed VES Event Value | Value Generated by DMI-Plugin |
Analysis
- Dataspace : NFP-Operational
- Yang Resource : ran-network to be used. ( trimmed down version just like
- Dataspace : NFP-Operational , Schema-Set : cps-ran-schema-model , Anchor : ran-network-simulation
- Yang Resource : cps-ran-schema-model ( tree form : cps-ran-schema-model _tree.txt ) existing ran-schema will be used.
- We need to have a defined channel/topic where the VES messages are present , and NCMP should be able to listen , interpret/process and call the relevant CPS-Core APIs in order to publish the changes in the CPS DB.
Meetings
# | Participants | Recording |
---|---|---|
1 | CPS _ CM VES Message _ Discussion-20230123_140429-Meeting Recording.mp4 | |
2 | CM VES Message to DMI Data AVC Mapping Discussion-20230309_130245-Meeting Recording.mp4 | |
3 |