Versions Compared

Old Version 50

changes.mady.by.user Toine Siebelink

Saved on

compared with

New Version 51

changes.mady.by.user Toine Siebelink

Saved on

Key

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

...

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

#

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.
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

CM VES related details present in CM handling guide

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-2177

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

More information is present in the meetings recording.

Sample CM VES event having


Code Block
titleSample provided byVishal Varvate  having href and path attribute.
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

Image Removed

Yes. CMNotify and CM VES message are the same.

}



The Big(ger) Picture

Gliffy Diagram
nameCPS Notifications Overview
pageid158040117

...