Versions Compared

Key

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

...

4b: Update RuntimeDB/ConfigDB using REST API


3. VES Message Format

This POC does not use VES messages, but would leverage the configuration change payload that should be included in the VES message notificationFields. This POC assumes that appropriate DMAAP message will be published by relevant ONAP components (VES Collector/DCAE) that will include the configuration change payload.  It is also expected that payload aligns with the YANG model defined for respective notifications.

For this POC, following VES message is assumed, and also includes configuration change payload (neighbor list change) highlighted in YELLOW below.

{
"event": {
"commonEventHeader": {
"version": "4.0.1",
"vesEventListenerVersion": "7.0.1",
"domain": "notification",
"eventName": "Notif_RansimAgent-Wipro_RanPCIProblem",
"eventId": "Notif000001",
"sequence": 1,
"priority": "High

...

",
"reportingEntityId": "de305d54-75b4-431b-adb2-eb6b9e546014",
"reportingEntityName": "ncserver1",
"sourceId": "cc305d54-75b4-431b-adb2-eb6b9e541234",
"sourceName": "Chn0001",
"startEpochMicrosec": 1451772223000000,
"lastEpochMicrosec": 1451772403000000,
"timeZoneOffset": "UTC-05:30",
"nfNamingCode": "RansimAgent",
"nfVendorName": "Wipro"
},
"notificationFields": {
"notificationFieldsVersion": "2.0",
"changeType": "Neighbour list changed",
"changeIdentifier": "ncserver1",
"additionalFields": {
"networkId": "NTWK005",
"configurationChange": "{ \"fap-service-number-of-entries-changed\":1, \"fap-service\":[ { \"alias\":\"Chn0001\", \"cid\":\"Chn0001\", \"lte-cell-number-of-entries\":1, \"lte-ran-neighbor-list-in-use-lte-cell-changed\":[ { \"plmnid\":\"ran-1\", \"cid\":\"Chn0002\", \"phy-cell-id\":4, \"pnf-name\":\"ncserver1\", \"blacklisted\":false } ] } ] }"
}
}
}
}





4. North-bound RPC YANG Model

...