...
# | Description | Source | Topic | Destination | Trigger | R12 Work Item | Notes | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | CPS-Temporal data updates | CPS-Core | cps.data-updated-events | CPS-Temporal | CPS-Core Data Update | N/A |
| ||||||||||||
2 | NCMP CM-Handle LCM (LifeCycle Management) events | NCMP | ncmp-events | External (NCMP) Clients | NCMP CM-Handle State Change (registration use-case) | N/A |
| ||||||||||||
3 | NCMP Data AVC (forwarding #5) | NCMP |
| External (NCMP) Clients | DMI Data AVC on passthrough datastore & NCMP Subscription | #6a | Open issue: can multiple subscriptions result in multiple events on different channels?! (RBAC TBAC ? The notifications should be on the set of topics specified by the union of all relevant subscriptions. This is why there is a difference between the subscription model (visible to a client/subscriber) and the subscription model used internally – The notification should not need to calculate, only look up the set of topics to emit on. | ||||||||||||
4 | CPS-Core Data AVC | CPS-Core |
| Data Change & CPS-Core Subscription | #7Open issue: wil ONAP client HAVE to create a subscription to receive CPS COre to start emitting these for a given dataspace? | Any client can subscribe to CPS-Core for any data subscription. The subscription wil include the topic to be used | |||||||||||||
5 | DMI Data AVC (Attribute Value Change) | DMI-Plugin | NCMP | Depends on DMI-Plugin
| #6a #7 |
| |||||||||||||
6 | VES Event | ONAP Devices | ONAP DMI Plugin | Change on Device | #7 |
| |||||||||||||
7 | Notification Subscription Event | DME (Data Mgmt and Exposure) | cm-avc-subscription | NCMP | User driven? CRUD operation Notification Subscriptions | #6b | The source can be anything that is authorized and knows the subscription event schema. It will be up to the encapsulating 'product' e.g. ONAP to decide if applications should use this interface directly. From NCMP perspective this is an access control challenge – If you are authorized to write to the cm-avc-subscription topic, NCMP will react | ||||||||||||
8 | Proprietary AVC | Proprietary Devices | N/A | Proprietary DMI Plugin | Change on Device | N/A | Irrelevant to ONAP Solution might not even by an 'event'. As long as it can be converted into a DMI Data AVC (#5) |
...