NOTE: This page is work in progress.

...

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

...

2.2.1 Initialization

In this state, perform initialization, and transition to Cluster formation statebased on the type of notification, go to either Section 2.2.1.1 or 2.2.1.2 for next actions.

2.2.

...

1.1. Neighbor list change notification received

• 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.

2.2.1.2. FM notification received

• Store details of the FM in DB.
• Increment the number of collisions and/or confusions depending on the type of alarm received.

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).

...

If OOF has to be triggered

...

then, check if any ANR actions are ongoing by PM-child thread. If yes, transition to wait for PM-based ANR actions state.

Transition to Trigger OOF state.

   Else

                Wait for more notifications

           Fi

2.2.3. Wait for notifications

...