References

  1. CPS-1489 - Getting issue details... STATUS
  2. CPS-1503 - Getting issue details... STATUS
  3. CPS Data Notifications Overview

Topics Owned by CPS Components


Use CaseHelm ChartCPS ComponentActualRequired*
#Parameter NameValue (Topic Name)OwnerSenderReceiverUserAccessSenderReceiver
1CPS Data Historical DatadataUpdatedTopiccps.data-updated-eventsCPS-TemporalCPS-CoreCPS-Temporalcps-kafka-userRead & Write
  • cps-core-ku
write
  • cps-temporal-ku
read
2CM Handle State UpdatesncmpEventsTopicncmp-eventsCPS-NCMPCPS-NCMPExternalcps-kafka-userAll
  • cps-core-ku
writeN/AN/A
3Internal ASync Dara request updatesncmpAsyncM2MTopicncmp-async-m2mCPS-NCMPDMI-plugin

CPS-NCMP

CPS-Core

cps-kafka-userAll
  • ncmp-dmi-ku
write
  • cps-core-ku
read
4CM VES Events processingdmiCmEventsTopicdmi-cm-eventsCPS-NCMPDMI-plugin

CPS-NCMP

CPS-Core

cps-kafka-userAll
  • ncmp-dmi-ku
write
  • cps-core-ku
read

Note: CPS-1503 - Getting issue details... STATUS will address the changes specified in the 'Required' section of this table

  • We will have a single Kafka user for CPS-Core and CPS-NCMP

External Topics

CPS(-NCMP) components are involved accessing but not defining these topics

#Use CaseTopic NameOwnerCPS ComponentAccess
1CM VES Events processingunauthenticated.SEC_3GPP_PROVISIONING_OUTPUTONAP VES CollectionDMI-Pluginread
2CM VES Events processingcm-eventsO-RAN Interface (TBC)CPS-NCMPwrite
3CM AVC Subscription CRUDcm-avc-subscriptionEDM CPS-NCMPread ( cps-core )

Note

topic-nameAll Topic Names marked in red in the table above are not finalized i.e. still in progress
  • No labels