Table of Contents |
---|
References
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
...
...
net/wiki/display/DW/CPS+Data+Notifications+Overview - Update Diagram
...
...
...
Assumptions
# | Assumption | Notes |
---|---|---|
1 | All information included in the subscription event will be forwarded | |
2 | org.onap.ncmp:cm-avc-subscription-event.response will be received from the DMI as per CPS-1065 Spike: CM data notifications from NCMP to applications including subscriptions#SubscriptionSteps |
Issues & Decisions
- Doing via endpoint will make it complicated to forward to multiple DMIs
- New endpoint will have to be implemented on DMI
- Propose org.onap.ncmp:cm-avc-subscription-event.forward
- ID?
- timestamp?
Events
Forward Subscription Event
Follow up Implementation Proposal Page: CPS-1431: Forward Subscription Information to DMI Plugin(s)
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
- At the moment, it is up to the DMI Plugins to accept or reject
- NCMP has to reject if cached dataspace is used (Cached is currently not supported)
Code Block title AVC Subscription Forwarding
...
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": {
...
...
"
...
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//”
...
}
...
}
Subscription Event Responses
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
- NCMP will be aware of the registered DMIs and the CMHandles registered to a given DMI
- Therefore will know how many DMIs to be waiting for a response from
- Wait for timeout before sending event outcome? (30s)
Subscription Event Outcome
- NCMP is to collate Event Responses from DMI and send.
- Wait for timeout,
- if all DMIs returned send full Event Outcome
- else partial event outcomes
Component Diagram
Drawio | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Issues & Decisions
# | Issue | Notes | Decision | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Is the forwarding being done via an endpoint or an asynchronous kafka message |
| |||||||||||||||
2 | Extra data needed for forwarded message? What is the schema |
|
| ||||||||||||||
3 | Error Scenarios |
Not in scope: Future story for notifying clients that subscription failed to be created | |||||||||||||||
4 | Review Diagram in CPS Data Notifications Overview |
...