CPS-1840 : Analysis of DMI Data AVC Event for SON use case

References

	Interface	Requirement	Additional Information	Signoff

	Interface	Requirement	Additional Information	Signoff
1

#	Error Scenario	Expected behavior

#	Error Scenario	Expected behavior
1	What happens if we receive a Cm Data AVC event for replace , but there is no corresponding record in CPS-Cache ?	CPS is not responsible for taking care of the model.
2	What happens when the updating of the cache fails ? Do we still send the messages to kafka ?

Characteristics

#	Parameter	Expectation	Notes

#	Parameter	Expectation	Notes
1	Frequency of VES Message from VES Standardized device
2	Frequency of DMI Data AVC Event sent out from DMI plugin to NCMP

Out-of-scope

#	Assumption	Notes

#	Assumption	Notes
1	The model is already present in CPS and we have the data corresponding to it.	CPS is not responsible for taking care of the model.
2	"Replace" operation is only supported.

#	Issue	Notes	Decision

#	Issue	Notes
1	Do we persist the incoming CM Data AVC Event in our database which we get from NCMP-DMI-PLUGIN ?
2	Which model to be used for the data in the cps-cache ?
3	Who will upload the model ? And which model will be used ?	primary YANG model will be in present in SDNC and during the device registration it will be loaded to CPS.
4	How will the data be uploaded which will later be updated ?	This should happen as part of the data sync operation.
5	What happens once the data is updated ? Is cps-core responsible to send out the updated events ? or the incoming "CM Data AVC Event" to cm-events topic is sufficient?	CM Data AVC Events sent to cm-events topic is sufficient.
6	Frequency of VES message , which determines the frequency of Data AVC events.
7	Which datastore to be used in CPS?	ncmp-datastore:operational