CM Subscription

Developed (Increments)

Description

Notes

Subscription Schemas

Ref: cps-ncmp-events/src/main/resources/schemas/cmsubscription

DME to NCMP Subscription Request
- cm-subscription-ncmp-in-event-schema-1.0.0.json
NCMP to DMI-Plugin Subscription Request
- cm-subscription-dmi-in-event-schema-1.0.0.json
DMI-Plugin to NCMP Subscription Response
- cm-subscription-dmi-out-event-schema-1.0.0.json
NCMP to DME Subscription Response
- cm-subscription-ncmp-out-event-schema-1.0.0.json

Subscription YANG model

cmNotificationSubscriptionCache

Hazelcast map to hold the incoming subscription create request

Key

Value

Unique Subscription Id

Key	Value
Dmi-Plugin Name	DmiCmNotificationSubscriptionDetails
Dmi-Plugin Name	DmiCmNotificationSubscriptionDetails

NCMP Startup

Ref: CmSubscriptionModelLoader

Client To NCMP

Ref: CmSubscriptionNcmpInEventConsumer

Ref: CmSubscriptionValidationService

NCMP to DMI

Ref: CmSubscriptionService

06 Feb 2024Method to fetch ongoing subscription in database via datastore Type, cmHandle ID, xpath

	User Story	Tasks
1	Analysis - Merging of Subscriptions ( Positive Scenarios )
2	Update Subscription Event Schemas for Subscription Merge Use Case
3	Create POC for Merge subscriptions datastore logic
4	Onboard subscription model for merging	Deprecate use of basic subscription model Create Datastores in NCMP w/ subscription model
5	Create Client to NCMP flow	Inmemory Datastructure to track Subscription Read and validate incoming sub create request from Kafka Populate hazelcast map with cmSubscriptions Validate Subscription ID Compare Active Subscriptions (DB) with the current request
6	Create NCMP to DMI flow	Fetch subscription data from database
7	Create DMI to NCMP flow	CmSubscription service layer methods Save new subscription to database Read and send response (DMI <>NCMP) Handle response from DMI
8	Create NCMP to Client flow