Versions Compared

Key

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

...

#

Issue

Notes

Decisions

1

Schema of the outcome response message (Schema 5)

Open Questions:

  1. What headers do we need?
  2. Do we need all Accepted, Rejected, Pending targets?

2dataType section needs to be confirmed.kieran mccarthy  to confirm for all the events.
3Grouping of the response for rejected and pending to be finalized.

Overview

// End to end solution in plaintext can be put in here.

...

Code Block
languagetext
titleInput Schema (Schema 3) - Consumed
topic: ncmp-dmi-cm-avc-subscription-dminame1

id uuid
source "SCO-9989752"
specversion  "1.0"
type subscriptionCreated
time // ncmp will generate
dataschema org.onap.ncmp.dmi.cm.subscription:1.0.0
data

{
   "data":{
      "subscription":{
         "clientID":"SCO-9989752",
         "name":"cm-subscription-001",
         "isTagged":false
      },
      "dataType":{
         "dataspace":"ALL",
         "dataCategory":"CM",
         "dataProvider":"CM-SERVICE"
      },
      "predicates":{
         "targets":[             
			{"cmHandle1": ["shape":"circle"]},
			{"cmHandle2": ["shape":"square"]},
			{"cmHandle3": ["shape":"traingletriangle"]}          
		],
         "datastore":"passthrough-running",
         "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//"
      }
   }
}




Code Block
languagetext
titleOutput Schema (Schema 4) - Produced
topic: dmi-ncmp-cm-avc-subscription

id uuid - generated by dmi-plugins
source <dmiName>
specversion  "1.0"
type subscriptionStatus
time
correlationID - generated by dmi
correlationid: clientId<clientId>:subscriptionName<subscriptionName>
dataschema org.onap.ncmp.dmi.cm.subscription:1.0.0
data

{
   "clientId":"SCO-9989752",
   "subscriptionName":"cm-subscription-001",
   "dmiName":"ncmp-dmi-plugin<dmiName>",
   "subscriptionStatus":[
      { 
  		id : <cmhandleid>, 
  		status : rejected | accepted,
  		message : <some message>  // only present for rejected 
	},
      {...}
   ]
}


Notes

  1. dmiName in Output Schema is populated from application.yml of DMI-plugin.
  2. DMI-plugin subscribes to the topic to consume Input Schema given in application.yml of DMI-plugin.

...

Code Block
languagetext
topic: subscription-response

id uuid - generated by NCMP
source <dmiName><NCMP>
specversion  "1.0"
type subscriptionStatus
time
correlationID // NCMP would generate
correlationid: clientId:subscriptionName
dataschema org.onap.ncmp.dmi.cm.subscription:1.0.0
data

{
  "data": {
       “statusCode” : 201,  # Some error code reflecting partial success.  **   //  To be discussed with the whole team
       “statusMessage” : “Partially Applied Subscription”,
       “additionalInfo” : {
           “fail”“rejected” :  [{
                “details” : “faulty subscription format for target(s)”, // need to finalize the detailed message for grouping.
                “targets” : [“cmhandle1”, “cmhandle2”, “cmhandle3”]
           },
			{
                “details” : “faulty subscription format for target(s) - xyz”, // need to finalize the detailed message for grouping.
                “targets” : [“cmhandle1”]
           }
],
           “pending” : {
                “details” : “EMS/node connectivity issues, retrying”,
                “targets” : [“cmhandle4”, “cmhandle5”, “cmhandle6”]
       }
  }
}

// we dont have to send the accepted cmhandle details.
 
** 202 could indicate complete failure – 
    "data": {
       “statusCode” : 202,  # Some error code reflecting complete rejection of the request
       “statusMessage” : “Subscription rejected : Faulty Subscription Data”,
       “additionalInfo” : {
           “fail”“rejected” :  {
                “details” : “//NRxxCellDU is not a valid subscription type”
           },

Have another for Pending CMHandles gone to accepted

...