Versions Compared

Old Version 3

changes.mady.by.user Toine Siebelink

Saved on

compared with

New Version 4

changes.mady.by.user Toine Siebelink

Saved on

Key

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

Table of Contents

References

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-2166

Assumptions


#AssumptionNotes
1

Issues & Decisions

#


IssueNotes Decision
1
This is an open issue

Analysis

Given the above . This table details 
Choose alternative for forwarding

Alternatives
NCMP forwards the CM Data Notification:

  1. as multiple CM Data Notifications on a common external topic with a special header indicating the client-id so the client can filter
  2. as one CM Data Notification on a common external topic with a special header containing ALL  client-ids (Array or String with special token separation)
  3. to topic(s) registered by client(s) during Subscription creation

2Even if clients specify the topic upon subscription creation, can multiple client share the same topic?Only applies to alternative #3 above

Overview

Gliffy Diagram
size1200
displayNameSubscription Merge Example
nameSubscription Merge Example
pageid177080337

CM Data Notifications Overview
Which are of interest to which Client (subscription ID)


Cm HandlePathA-10B-52
1CH-1/p/c1YesNo
2CH-1/p/c2YesYes
3CH-1/p/c3NoYes
4CH-4/p/c2NoYes
5CH-4/p/c3NoYes
6CH-1/p/c4NoNo




Solution Proposal

  1. NCMP (currently) listens to all CM Data Notifications (on an 'internal' topic
  2. NCMP queries its own persistence service to find out which Client(s) are interested in the notifications A-10 and/or B-52
  3.  (3 alternatives, see issue #2)
Alternatives