Versions Compared

Old Version 11

changes.mady.by.user N.K. Shankaranarayanan

Saved on

compared with

New Version Current

changes.mady.by.user N.K. Shankaranarayanan

Saved on

Key

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

...

  1. OSC work on CM Handling (Nov 2021). The following page
    CM handling guide - Developer Wiki - Confluence (onap.org) 
    describes a CM VES message and procedure for handling it, especially mapping the schema url to a local url. This refers to a 3GGP Rel16 scheme which needs to be updated to https://forge.3gpp.org/rep/sa5/MnS/-/blob/Rel-18/OpenAPI/TS28532_ProvMnS.yaml
  2. ONAP work on defining a CM VES message. This is an older format and does not have a path specified, but may be useful in designing the solution
    https://jira.onap.org/secure/attachment/17656/CMNotificationFormat_son_poc.json

...

Sample CM VES message for notifyMOIChanges (as of 3/1421/2023. See R12 Use Case Files - Developer Wiki - Confluence (onap.org))

{
  "event": {
    "commonEventHeader": {
       "domain": "stndDefined", 
       "eventId": "stnddefined000001", 
       "eventName": "stnddefined_Metrics", 
       "lastEpochMicrosec": 1670938742757000, 
       "nfNamingCode": "CUCP", 
       "nfVendorName": "Capgemini Engineering", 
       "priority": "Normal", 
       "reportingEntityId": "nearrtric-22_cucpserver2", 
       "reportingEntityName": "honeycomb", 
       "sequence": 0, 
       "sourceId": "nearrtric-22_cucpserver2", //strong assumption that this is globally unique among all 
       "sourceName": "Capgemini Engineering", 
       "startEpochMicrosec": 1670938742757000, 
       "stndDefinedNamespace": "3GPP-Provisioning", 
       "timeZoneOffset": "UTC+05:30", 
       "version": "4.0.1", 
       "vesEventListenerVersion": "7.2" 
    }, 
    "stndDefinedFields": {
      "schemaReference": "https://forge.3gpp.org/rep/sa5/MnS/blob/Rel-18/OpenAPI/TS28532_ProvMnS.yaml ", 
      "data": {
         "href": "https://172.16.100.130/restconf/data", 
         // added /restconf/data to be the MIB Root
         // added https://
         // url of ip server hosting the GNBCCU NF
         // 3GPP 28.532 Table 12.1.1.4.1a.8 -1: Definition of type NotifyMoiChanges description is "URI of the local root in the MIB"

         "notificationId": 1, 
         "notificationType": "notifyMOIChanges", 
         "eventTime": "2021-08-23T11:52:10.6Z", 
         "systemDN": "xyz", 
         "moiChanges": [  
           {
             "notificationId": 123, 
             "correlatedNotifications": [], 
             "additionalText": "AdditionalTextDetails", 
             "sourceIndicator": "MANAGEMENT_OPERATION", 
             "path": "/ran-network:ran-network/NearRTRIC=22/GNBCUCPFunction=cucpserver2/NRCellCU=15549/NRCellRelation=14427",
             // Added the leading / See comment from Martin in O1 CM Update Notification VES Message
             // modified to make the path relative to the "MIB Root" as defined in the href above
             // The VES msg from a RANSim GNBCU NF has NearRTRIC in the path to be aligned with the yang model used in RANSim. In general, a real GNBCU (1:1 mapping between GNB and GNBCU) yang model may not show a GNBCUCPFunction as a child of a NearRTRIC. The path identifies the object being changed, with the attributes being listed in the value field.
             "operation": "replace", 
             "value": { 
               "isHOAllowed": "true"
             }
           }
         ]
      }, 
      "stndDefinedFieldsVersion": "1.0" 
    }
  }
}



...