...
Assumptions
| # | Issue | Notes |
|---|---|---|
| 1 | VES Event is received via Strimzi/DMaap Kafka. | |
| 2 | Changes in CM data will result in CPS-Core sending a CPS Data AVC irrespective the origin of the change. |
|
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. | ||
| 2 |
...
| Topic |
...
| 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 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. |
...
| 4 |
|
...
| 5 | How to get the cmHandle and the xpaths from the CM VES Messages. |
...
| 6 |
The Big(ger) Picture
| Gliffy | ||||
|---|---|---|---|---|
|
...