References
CPS-1434 - Getting issue details... STATUS
CPS-1407 - Getting issue details... STATUS
Assumptions
Issues & Decisions
# Issue Notes Decisions CM VES Message format schema. Who will own it ?1. In order to process the message DMI plugin / NCMP should be aware of the schema of the incoming message it is going to be consume. 2. Topic/REST API from where we will receive the CM VES Message. 3. Does CPS raise any special event after the events are updated in CPS DB ? 4 Does CPS care about all the attributes in the CM VES Message. If not then we need to list down the attributes which CPS cares about. The CM update expected would be a change for the GNBDUFunction/nrCellDU/nrPCI ** or for the GNBCUFunction/NRCellCU/NRCellRelation/isHOAllowed . Need to confirm with the stakeholders. 5 Do we need to persist the CM VES Message ? 6 Any Performance requirements ? 7 
- Is CMNotify Message same as CM VES Message and notify more about this if this is relevant.8 How to get the cmHandle and the xpaths from the CM VES Messages. Overview
The Big(ger) Picture
For more details and descriptions see CPS Data Notifications Overview
VES Event Flow
- DMI Plugin to receive CM VES Message from the upstream( VES Collector ?? ) via a REST call or DMI will listen to a topic. ( or also can generate a VES message for testing)
- DMI Plugin will have to convert the CM VES Message to DMI Data AVC event and publish the same to an internal topic.
- NCMP will have logic to handle the DMI AVC event received to update the cache. ( See #6 in CPS Data Notifications Overview )
Analysis
- Dataspace : NFP-Operational , Schema-Set : cps-ran-schema-model , Anchor : ran-network-simulation
- Yang Resource : cps-ran-schema-model ( tree form : cps-ran-schema-model_tree.txt ) existing ran-schema will be used.
- We need to have a defined channel/topic where the VES messages are present , and NCMP should be able to listen , interpret/process and call the relevant CPS-Core APIs in order to publish the changes in the CPS DB.