Versions Compared

Old Version 23

changes.mady.by.user Halil Cakal

Saved on

compared with

New Version 24

changes.mady.by.user Halil Cakal

Saved on

Key

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

...


Subscription Creation Events Handling

Assumptions

#AssumptionNotes
1Forwarded Subscription Event Responses communicates asynchronously.  (
NCMP to
from DMI Plugins to NCMP)
  
 

Once off timer would be responsible to

publish

consume messages

in

into NCMP. 

2Forwarded Subscription Event Responses communicates asynchronously.  (DMI Plugins to NCMP) 

Then, the NCMP would wait a response(s) within the timeframe agreed on. (30 seconds)

TBD: A single step response

or two step responses

will be provided in the solution. Since, 

3

ACK is not feasible as of now.

2The NCMP component should create Subscription Create Outcome message and publish it into topic (cm-avc-subscription-response) in which Client Apps consumed from.The Outcome Response schema need to be decided on.

Issues & Decisions

#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 initial response and further updates
    1. Status only: COMPLETED / PARTIALLY_COMPLETED
    2. Status and % -completed based on # Participating DMI-plugins
    3. Status and %-completed based on #cm-handle-ids  registered (and participating) per Plugin
    4. Status and list of m-handle ids for which NCMP got a response

...

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

    Code Block
    languagetext
    titleCreate Event from Clients
    collapsetrue
    {
  "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 Forwarded Subscription Event.

    Message Format (NCMP→ DMI Plugin):

    Code Block
    languagetext
    titleNCMP to DMI Message Format
    collapsetrue
     {
  "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.dmi:cm-network-avc-event.rfc8641",
      "schemaVersion": "1.0"
    },
    "predicates": {
      "targets": [{
            “targets” :  [  { cmhandle : “sdsd”"cmhandle": "sdsd",
                                              cmhandle-properties” "cmhandle - properties": {
          "prop1": "prop                                       “prop1” : “prop-value”
                                   - value"
            }
                                           },
        {
                                   {  cmhandle : “slada”"cmhandle": "slada",
                                              cmhandle-properties” "cmhandle - properties": {
            "prop -                                     “prop-x” : “prop-valuex”
                                  x": "prop - valuex"
             }
                                           }, 
        {
                                   {  cmhandle : “ccde3”"cmhandle": "ccde3",
                                              cmhandle-properties” "cmhandle - properties": {
            "prop -                                     “prop-y” : “prop-valuey”
   y": "prop - valuey"
                                            }
                                           }
                                        ]     #  cmhandle targets
  ],
      "datastore": “passthrough"passthrough-operational",
        "datastore-xpath-filter": "//_3gpp-nr-nrm-gnbdufunction:GNBDUFunction/ ",
             "_3gpp-nr-nrm-nrcelldu":NRCellDU/ | //_3gpp-nr-nrm-gnbcuupfunction:GNBCUUPFunction// | "NRCellDU",
            //"_3gpp-nr-nrm-gnbcucpfunction:GNBCUCPFunction/_3gpp-nr-nrm-nrcelldu:NRCellCU// |gnbcuupfunction": "GNBCUUPFunction",
            //"_3gpp-nr-nrm-nrsectorcarrier":NRSectorCarrier//” "NRSectorCarrier"
   
 }
    }
}


    TBD Further with external team: Putting predicates back to NCMP does not sense.  Since, the predicates and CM Handles are clashing. 

  3. The communication between NCMP would publish messages (Forwarded Subscription Event) to the topic ncmp-dmi-cm-avc-subscription via once-off timer. and DMI-Plugin would be synchronously. 
  4. The DMI-Plugin would publish responses in a single step. ACK feature is not feasible as of now.
  5. Then, the NCMP would wait a response(s) within the timeframe (timeout) agreed on e.g. 30 seconds via once-off timer.
    1. Response in two stepsa single step
        Ack (response with DMI plugin detais e.g. DMI X and Y has started to processing)
      1. Process result response: 2 out of 3 DMI has responedresponded. (The percentage is %66.)
      Response in a single step
      1. Process result response: 2 out of 3 DMI has responed. (The percentage is %66.)In order to calculate the response ratio, CPS inventory CmHandleQueries could be used.

  6. Finally, the NCMP

    plugin

    create outcome message, and publish it to the topic cm-avc-subscription-response.
    The outcome message format could be like:

    Code Block
    languagetext
    collapsetrue
    Possible options for initial response and further updates
	Status only: COMPLETED / PARTIALLY_COMPLETED
	Status and % -completed based on # Participating DMI-plugins
	Status and %-completed based on #cm-handle-ids  registered (and participating) per Plugin
	Status and list of m-handle ids for which NCMP got a response


Testing Details