Versions Compared

Old Version 17

changes.mady.by.user Halil Cakal

Saved on

compared with

New Version 18

changes.mady.by.user Halil Cakal

Saved on

Key

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

...

#IssueNotes Decision
1Possible 'timeframe' period for timeoutDMI to NCMP response timeout

30 sec (Configurable param/property)

2Response in two steps or in a single step should be discussed with shareholders.from DMI to NCMP responsesIs the ACK would be required?
3Response schema should be decided

from DMI to NCMP response schemas should be decided for both two steps response and single step response

  • Should DMI Plugins detail cm-hande IDs in response?

4Subscription event outcome schema should be decided

from DMI to Client Apps

  • Possible options for intial reponse initial response and furrther updatefurther update
    1. Status only: COMPLETED / PARTIALLY_COMPLETED
    2. % -completed based on # Participating DMI-plugins
    3. %-completed based on #cm-handle-ids  registered (adn participating) per Plugin
    4. list of 

Possible Topic Names

#SourceContentTopic NameDestination
1Client AppsSubscription Create Eventcm-avc-subscriptionNCMP
2NCMPForwarded Subscription Create Event

ncmp-dmi-cm-avc-subscription


DMI Plugins

3DMI PluginsForwarded Subscription Create Event Responsedmi-ncmp-cm-avc-subscriptionNCMP
4NCMPSubscription Create Event Outcomecm-avc-subscription-responseClient Apps

...

  1. Client apps e.g. DME would publish Subscription Create Event to the topic cm-avc-subscription. 
    Message Format (Client → NCMP):

    JSON Viewer
    {
  "version": "1.0",
  "eventType": "subscriptionCreated",
  "event": {
    "subscription": {
      "clientID": "SCO-9989752",
      "name": "cm-subscription-001"
    },
    "dataType": {
      "dataspace": "ALL",
      "dataCategory": "CM",
      "dataProvider": "CM-SERVICE"
      "schemaName": "org.onap.ncmp:cm-network-avc-event.rfc8641"
      "schemaVersion": "1.0"
    },
    "predicates": {
                   “targets” :  [“sdsd”, “slada”, “ccde3”]     #  cmhandle targets
        "datastore": “passthrough-operational",
        "datastore-xpath-filter": "//_3gpp-nr-nrm-gnbdufunction:GNBDUFunction/ 
             _3gpp-nr-nrm-nrcelldu:NRCellDU/ | //_3gpp-nr-nrm-gnbcuupfunction:GNBCUUPFunction// |
            //_3gpp-nr-nrm-gnbcucpfunction:GNBCUCPFunction/_3gpp-nr-nrm-nrcelldu:NRCellCU// |
            //_3gpp-nr-nrm-nrsectorcarrier:NRSectorCarrier//”  
 
    }
}


  2. The NCMP would consume the messages from cm-avc-subscription topic, and  create Forwareded Subscription Event.
  3. The NCMP would publish messages (Forwarded Subscription Event) to the topic ncmp-dmi-cm-avc-subscription via once-off timer. 
  4. Then, the NCMP would wait a response(s) within the timeframe (timeout) agreed on e.g. 30 seconds.
    1. Response in two steps
      1. Ack (response with DMI plugin detais e.g. DMI X and Y has started to processing)
      2. Process result response: 2 out of 3 DMI has responed. (The percentage is %66.)
    2. Response in a single step
      1. Process result response: 2 out of 3 DMI has responed. (The percentage is %66.)
  5. Finally, the NCMP plugin create outcome message, and publish it to the topic cm-avc-subscription-response.

...