Page Comparison

1. Separate alarms for PCIConfusion and PCICollision.
2. Source Entity is cell name
3. specificProblem:
   Lists one cell for PCICollision.
   Lists one or more cells for PCIConfusion.

There is a CM Notify implementation
CM Notification Support in ONAP
Point of discussion about what is the status of this in ORAN.

We are assuming that CM notification will come over VES. Martin said this on 2/19 call. Claudio also verified today.
If CM Notify requires VES 7.2, and FM VES msg recommedation is VES7.1, then we need to check how the DCAE VES Collector will handle such messages.

They could be collected and passed on, but what is the support for some VES format conversion. How is this to be handled?

Should we use the config change information contained in the FM message
to update or annotate CPSDB. Who should own this.
1) In near-term we may not have CM Notify implemented
2) In future, a CM Notify message may get lost
Notes:
1. We cannot do a local update or modification to the config data within the MS since
OOF has to read the information from CPSDB. So any config updates using FM must be reflected in CPSDC/TDMT.

2. There is a CPSDB discussion of having a parallel datastore of intended update. It may be possible to leverage that
for updates from FM which may be a reliable-partial-update (reliable since it came from RAN, partial since any change which
did not result in alarm may not be included).

3. If we have updates to main CPSDB from CM and also from FM, there can be a race condition with time variations.
The last arriving update will change the DB. This needs to be managed explicitly even for CM. But there may be more issues if updates from FM are also used.

4. Problem remains that if we do not have CM Notify, can we proceed if we have an FM implementation?