Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

References

CPS-2166 - Getting issue details... STATUS

Assumptions


AssumptionNotes
1Topic name extracted from Subscription ID
2One client can have multiple subs
3Topic is setup correct and can write 

Issues & Decisions


IssueNotes Decision
1Choose 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
Option 3 further expanded as functional requirements 1 &2
2Even if clients specify the topic upon subscription creation, can multiple client share the same topic?Only applies to alternative #3 above

Requirements

Charact


PeAdditional Informatio
Signoff
1

Each NCMP instance shall support 150M CM notification change events per day




2

NCMP shall support horizontal scaling to support > 150M CM notification change events





3

NCMP shall support processing CM notification change events with the following subscription profile :

  • 40% of subscriptions shall process 5% of all network change notification events
  • 30% of subscriptions shall process 10% of all network change notification events
  • 15% of subscriptions shall process 30% of all network change notification events
  • 9% of subscriptions shall process 50% of all network change notification events
  • 5% of subscriptions shall process 70% of all network change notification events
  • 1% of subscriptions shall process 100% of all network change notification events






Req

Functional



InterfaceRequirementAdditional InformationSignoff
1

Client application shall ONLY receive notification they subscribed on



2
Client application shall not see notification they did not subscribed on

Error Handling






1



Overview

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)
  • No labels