Page History

...

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

   Code Block
   language text title Create Event from Clients collapse true
   { "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// } }

   
   

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.

...