R12 Use Case Files

The intent is to maintain the latest version of the CM VES msg for the SON Use Case Rel 12 as cm_ves_rel12

Priyank Maheshwari N.K. Shankaranarayanan Toine Siebelink 

Following on from meeting earlier today ...

On the cm_ves_rel12.json,  Suggest that the path makes more sense to be relative to the model and the href is the root of the MIB which for me is the root of the model tree.

Suggested updates to href and path as below ...

    "stndDefinedFields": {
      "schemaReference": "https://forge.3gpp.org/rep/sa5/MnS/blob/Rel-18/OpenAPI/TS28532_ProvMnS.yaml ", 
      "data": {
         "href": "172.16.100.130/restconf/data",    // added "/restconf/data" to be the MIB Root
         // 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",      // 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" 
    }

Additionla Note on Root.

Restconf specification Section 3.1 details getting the root (at least up to "data" or "operations"). 
Following from that the proposal above is that CM notifications are relative to "{restconf-root}/data" as the root of the yang tree data.

Vishal Varvate Priyank Maheshwari kieran mccarthy Martin Skorupski Toine Siebelink 

Uploaded v4 after discussion with Vishal and review of Martin's comment in O1 CM Update Notification VES Message. v4 changes

• Added "https://" in href and re-inserted the leading "/" in path