...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
NOTE:
...
This page is work in progress.
References
Use case overview and impacted components are described in the 5G OOF PCI optimization main wiki page.
...
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
- PM/FM data
1.3. DMaaP Client
This is responsible for registering with the DMaaP client for the DMaaP notifications from SDN-R and VES-Collector, and to Policy.
2. Core Logic components and Pre-processing algorithm
...
Gliffy | ||||
---|---|---|---|---|
|
2.2.2. Cluster formation
Store details of the cell (which sent the neighbor list change notification) and its neighbors in DB.For each of the neighbors, fetch the neighbor list (via REST API) from SDN-R Config DB (i.e., fetch neighbor of neighbors of the cell that sent the neighbor list change notification).Form a cluster with the cell, its neighbors and neighbors of each of the neighbors.Assign a cluster id.Determine collision/confusion by calling method determine_collision_confusion.Based on number of collisions/confusions and config policy, determine if OOF has to be triggered or more notifications should be awaited (handle also timeout case).
...