References

Use case overview and impacted components are described in the 5G OOF PCI optimization main wiki page.

1. Architecture

This architecture depicts a standalone PCI micro-service. When this is moved to DCAE, it may undergo some adaptations, for e.g., the interfaces have to be adapted appropriately.

...

This is a PostgreSQL DB, and is intended to persist information such as the following:

• PCI-Handler MS Config information (e.g., thresholds, timer values, OOF algorithm name, etc.)
• Pre-processing results and other related information (e.g., neighbor list)
• Buffered notifications (i.e., notifications not yet processed at all)
• State information
• Association between pnf-name and CellId

1.3. DMaaP Client

This is responsible for registering with the DMaaP client for the DMaaP notifications from SDN-R, and to Policy.

2. Core Logic components and Pre-processing algorithm

...

2.2.1 Initialization

In this state, perform initialization, and transition to Cluster formation state.

...

Upon trigger from main thread with OOF PCI optimization result, prepare and send a DMaaP message to Policy (message layout available in Policy sub-page. The message payload layout shall be the same as the yang model contents for the configuration update to be sent by SDN-R towards the RAN. The pnf-name corresponding to the cell-ids can be fetched from Config DB of SDN-R (using REST API). (Note: The layout of the message from SDN-R to RAN is available in the SDN-R sub-page).

After sending the message to Policy, a status update is provided to the Main Thread for further actions.

...