Versions Compared

Key

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

Table of Contents

References

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1434

Jira
serverONAP Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1407

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
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
2
.
Topic from where we will receive the CM VES Message
3.Does CPS raise any special event after the events are updated in CPS DB ?4Does CPS care about all the attributes in the CM VES Message. If not then we need to list down the attributes which CPS cares about.The CM update expected would be a change for the GNBDUFunction/nrCellDU/nrPCI ** or for the GNBCUFunction/NRCellCU/NRCellRelation/isHOAllowed . Need to confirm with the stakeholders.5Do we need to persist the CM VES Message ?6Any Performance requirements ? 7

Image Removed - Is CMNotify Message same as CM VES Message.

8How to get the cmHandle and the xpaths from the CM VES Messages.

Overview

.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

  • 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?

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

CM VES related details present in CM handling guide and

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

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"
    }
  }
}


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 Diagram
nameCPS Notifications Overview
pageid158040117

For more details and descriptions see CPS Data Notifications Overview

VES Event Flow

  • DMI Plugin to receive CM VES Message  from DMI Plugin to receive CM VES Message from the upstream( VES Collector ?? ) via a REST call or some other methodDMI will listen to a topic. ( or also can generate a VES message for testing)
  • DMI Plugin will have to convert the CM VES Message to DMI Data AVC event and publish the same to an internal topic.
  • NCMP will have logic to handle the DMI AVC event received to update the cache. ( See the highlighted portion in the attached diagram #6 in  CPS Data Notifications Overview 


Gliffy Diagram
size600
displayNameCM_VES_PROCESSING CPS Side
nameCM_VES_PROCESSING
pagePin6

Sample VES Message : sample_ves_message.json

Analysis

10

VES Event → DMI Data AVC Mapping


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 #
3HeadersourceIddevicenearrtric-22_cucpserver2HeadereventSourceVES Eventdevice-123Upto DMI plugin to send. where it came from etc.
4HeadersourceId
nearrtric-22_cucpserver2HeadereventCorrelationIdVES Event & Conversionnearrtric-22_cucpserver2DMI PLugin need to map TBC
5Payloadpath

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'replace'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
  • 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