Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

1
Gliffy
nameCPS Notifications Overview Copy
pagePin
Table of Contents

References

...

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-2177

CPS Data Notifications

CM VES Message

https://www.rfc-editor.org/rfc/rfc8641

O1 CM Update Notification VES Message

DMi Data AVC Sample Message

SON Use Case Weekly Meeting Notes

Assumptions


#IssueNotesDecisions
1

VES Event is received via Strimzi/DMaap Kafka on DMI.


Yes. This is agreed.
2Changes in CM data will result in CPS-Core sending a CPS Data AVC irrespective the origin of the change.
  1. See #4 in the Bigger Picture below.
  2. This could later be model controlled to be more granular.


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
2Topic 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
How do we retreive

Mapping of the relevant information from the CM VES Message

  • CmHandle
  • Xpath
  • Operation that happened

Only fields that seem to suggest to have these info. are.

  1. moiChanges.operation
  2. moiChanges.value
  3. moiChanges.path ?? 

Related work in ONAP suggests this possible alternative schema:

https://wiki.o-ran-sc.org/display/SIM/Network+Slicing+Use+Case#NetworkSlicingUseCase-ExampleVESPMstndDefined

So wanted to confirm if measurements.measurement-type-instance-reference is xpath?

The fields which are of importance are :

  1. event.sourceId  ( we can extract cmHandle details from the sourceId )
  2. moiChanges.operation
  3. moiChanges.path
  4. moiChanges.value

Sample CM VES event having href and path attribute.

{
 

Mapping detailed below: VESEvent%E2%86%92DMIDataAVCMapping

CM VES related details present in CM handling guide and

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-2177

Vishal Varvate  to provide in few examples of the CM VES messages.

More information is present in the meetings recording.

Code Block
titleVES Event Sample
collapsetrue
{
  "event": {


    "commonEventHeader": {


       "domain": "stndDefined",


            "eventId": "stnddefined000001",


            "eventName": "stnddefined_Metrics",


            "lastEpochMicrosec": 1670938742757000.0,


            "nfNamingCode": "NFC",


            "nfVendorName": "Capgemini Engineering",


            "priority": "Normal",


            "reportingEntityId": "nearrtric-22_cucpserver2",


            "reportingEntityName": "honeycomb",


            "sequence": 0,


            "sourceId": "nearrtric-22_cucpserver2",


            "sourceName": "Capgemini Engineering",


            "startEpochMicrosec": 1670938742757000.0,


            "stndDefinedNamespace": "3GPP-Provisioning",


            "timeZoneOffset": "UTC+05:30",


            "version": "4.0.1",


            "vesEventListenerVersion": "7.2"


    },


    "stndDefinedFields": {


      "schemaReference": "https://forge.3gpp.org/rep/sa5/MnS/blob/Rel16/OpenAPI/provMnS.yaml#/components/schemas/NotifyMoiChanges",


      "data": {


        "href": "172.16.100.130",


        "notificationId": 1,


        "notificationType": "notifyMOIChanges",


        "eventTime": "2021-08-23T11:52:10.6Z",


        "systemDN": "xyz",


        "moiChanges": [


          {


            "notificationId": 123,


            "correlatedNotifications": [],


            "additionalText": "AdditionalTextDetails",


            "sourceIndicator": "MANAGEMENT_OPERATION",


            path="/restconf/data/ran-network:ran-network/NearRTRIC=22/GNBCUCPFunction=cucpserver2/NRCellCU=15549/NRCellRelation=14427/isHOAllowed",


            "operation": "REPLACE",


            "value": {


              "isHOAllowed": "true"


            }


          }


        ]


      },


      "stndDefinedFieldsVersion": "1.0"


    }


  }
}

}

cm-event-list-example.json

4

- Is CMNotify Message same as CM VES Message and notify more about this if this is relevant.

Image Removed

Yes. CMNotify and CM VES message are the same.


4DMI Data AVC Message


Code Block
titleDMI Data AVC Sample
collapsetrue
{
   "eventId":"nearrtric-22_cucpserver2",
   "eventCorrelationId":"nearrtric-22_cucpserver2",
   "eventTime":"2023-02-28T16:42:25-04:00",
   "eventSource":"ncmp-datastore:operational",
   "eventType":"org.onap.ncmp.cm-network-avc-event",
   "eventSchema":"org.onap.ncmp:cm-network-avc-event.rfc8641",
   "eventSchemaVersion":"1.0",
   "event":{
      "push-change-update":{
         "datastore-changes":{
            "ietf-yang-patch:yang-patch":{
               "patch-id":"34534ffd98",
               "edit":[
                  {
                     "edit-id":"ded43434-1",
                     "operation":"replace",
                     "target":"ran-network:ran-network/NearRTRIC[@id='22']/GNBCUCPFunction[@id='cucpserver2']/NRCellCU[@id='15549']/NRCellRelation[@id='14427']",
                     "value":{
                        "attributes":[
                           {
                              "isHoAllowed":true
                           }
                        ]
                     }
                  }
               ]
            }
         }
      }
   }
}


5Topic from NCMP-DMI-Plugin to NCMPThe producer is already configured.Topic name : dmi-cm-events


The Big(ger) Picture

Gliffy
nameCPS Notifications Overview
pageid15804011716514237

For more details and descriptions see CPS Data Notifications Overview

...

cm-handle-1234

VES EventDMI Data AVCNotes
#PartFieldSourceSample ValuePartFieldSourceSample Value
1HeadereventId
123435HeadereventIdDMI Plugin123435Has to be globally unique
2HeadereventTimedevice2021-11-16T16:42:25-04:00HeadereventTimeVES Event2021-11-16T16:42:25-04:00TO BE DISCUSSED see open issue #
3HeadersourceIddevicedevicenearrtric-12322_cucpserver2HeadereventSourceVES Eventdevice-123Upto DMI plugin to send. where it came from etc.
4Event-ObjectHeaderhref1234sourceId
nearrtric-22_cucpserver2HeadereventCorrelationIdVES Event & Conversionnearrtric-22_cucpserver2DMI PLugin need to map TBC
5PayloadpathManagedElement=1\Function=SomeFunction

ran-network:ran-network/NearRTRIC=22/GNBCUCPFunction=cucpserver2/
NRCellCU=15549/NRCellRelation=14427


ran-network:ran-network/NearRTRIC=11/GNBCUCPFunction=cucpserver2/
NRCellCU=15549/NRCellRelation=14427

PayloadtargetVES Event & Conversion

ManagedElement@[id='1']\Function[@id='SomeFunction']


ran-network:ran-network/NearRTRIC[@id="22"]/GNBCUCPFunction[@id="cucpserver2"]/
NRCellCU[@id="15549"]/NRCellRelation[@id="14427"]

DMI PLugin needs to convert FDN to XPath
6



Payloadpatch-idDMI Plugin329cb2e3-b41a-4347-9884-f15457f426a1Unique ID generated by DMI-Plugin
7Payloadoperationdevice'REPLACEreplace'PayloadoperationVES 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 EventTransformed VES Event ValueValue Generated by DMI-Plugin

Analysis

  • Dataspace : NFP-Operational , Schema-Set : cps-ran-schema-model , Anchor : ran-network-simulation
  • Yang Resource : cps- ran-schema-model ( tree form : network to be used. ( trimmed down version just like 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