Versions Compared

Version Old Version 38 New Version 39
Changes made by

Priyank Maheshwari

Priyank Maheshwari

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

References

...

CM VES Message

Assumptions


#IssueNotes
1

VES Event is received via Strimzi/DMaap Kafka.


2Changes in CM data will result in CPS-Core sending a CPS Data AVC irrespective the origin of the change.
  1. See #4 in the Bigger Picture below.
  2. This could later be model controlled to be more granular.


Issues & Decisions


#

Issue

Notes

Decisions

1

CM VES Message format schema.

Who will own it ?

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.
2Topic from where we will receive the CM VES Message.Existing channel or channel owned by NCMP/DMI
3
Does CPS care about all the attributes in

How do we retreive the relevant information from 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 .

  • CmHandle
  • Xpath
  • Operation that happened

Only fields that seem to suggest to have these info. are.

  1. moiChanges.operation
  2. moiChanges.value

  3. moiChanges.path ?? 

Need to confirm with the stakeholders.
4

Image Modified - Is CMNotify Message same as CM VES Message and notify more about this if this is relevant.



5How to get the cmHandle and the xpaths from the CM VES Messages.

6



The Big(ger) Picture

Gliffy
nameCPS Notifications Overview
pageid158040117

...