Versions Compared

Version Old Version 22 New Version Current
Changes made by

Halil Cakal

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
communicates asynchronously.  (NCMP to DMI Plugins)  Once off timer would be responsible to publish messages in NCMP. 2Forwarded Subscription Event Responses communicates 3
Responses communicate asynchronously.  (from DMI Plugins to NCMP) 

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

TBD: A single step response or two step responses will be provided in the solution. 


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

Issues & Decisions

DMI NCMP (Configurable param/property)
#IssueNotes Decision
1Possible 'timeframe' period for timeoutNCMP to Client Apps response timeout

30 sec

.

2Response in two steps or in a single step should be discussed with shareholders.(as of now)from DMI to NCMP responses

Is the ACK would be required? No

DMI-Plugin would publish actual response to NCMP

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? Yes

Accept or Decline


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 responseList of accepted CM Handle IDs
    5. List of declined CM Handle IDs

We include : 

  1. Status only: COMPLETED / PARTIALLY_COMPLETED
  2. List of accepted CM Handle IDs
  3. List of declined CM Handle IDs

Note : Avoid for wild card * (for all cm handles)

Possible Topic Names

NCMPDMI PluginsNCMP
#SourceDestinationContentTopic NameDestination
1Client AppsNCMPSubscription Create Eventcm-avc-subscription
2NCMPDMI Plugins

Forwarded Subscription Create Event

ncmp-dmi-cm-avc-subscription

-{DMI-DATA-SERVICE-NAME}


3DMI PluginsNCMPForwarded Subscription Create Event Responsedmi-ncmp-cm-avc-subscription
4NCMPClient AppsSubscription Create Event Outcomecm-avc-subscription-responseClient Apps

Implementation Details

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//
    }
}

The NCMP would consume the messages from cm-avc-subscription topic, and  create Forwareded Subscription Event.

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” :  [  { cmhandle : “sdsd”,
                                              cmhandle-properties” : {
                                                  “prop1” : “prop-value”
                                               }
                                           },
                                           {  cmhandle : “slada”,
                                              cmhandle-properties” : {
                                                  “prop-x” : “prop-valuex”
                                               }
                                           }, 
                                           {  cmhandle : “ccde3”,
                                              cmhandle-properties” : {
                                                  “prop-y” : “prop-valuey”
                                               }
                                           }
                                        ]     #  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//”  
 
    }
}

...

  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.)

...


Testing Details