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
...
Update/prepare DMaaP messages to Policy for the cells whose neighbors have undergone updates (with indication "HO prohibited"). 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)
...
This child thread perform all PM-related computations, and initiate autonomous ANR updates based on HO metrics.
Gliffy | |||
---|---|---|---|
|
...
|
2.3.1. Initialization
Gliffy
2.3.2. Wait for PM inputs
In this state PM inputs are awaited. Upon reception of PM inputs, do the following:
2.3.2.1 Handle PM inputs
- Compute HO success metrics for every source-destination cell pair, and store in DB.
- Store the details separately of the cell pair(s) whose HO success is consistently:
- < threshold_bad
- < threshold_poor, but >= threshold_bad
- Perform DB book-keeping actions (delete old PM entries).
- if any pair has a consistently HO success < threshold_bad
then
2.3.2.2. Check readiness for ANR actions and carry out next steps
if ANR actions can be carried out (i.e., any PCI-ANR actions are ongoing by a PCI-ANR child thread)
then
if Policy_rsp is not pending
then
2.3.2.2.1. Prepare and send message(s) to Policy
Prepare and send DMaaP messages to Policy for all the cells whose neighbors have to be updated with "HO prohibited".
Start policy_rsp timer
Go to "Wait for Policy response" state (Section 2.3.4)
else
Go to "Wait for Policy response" state (Section 2.3.4)
fi
else
Go to "Wait for PCI-ANR child thread(s) action completion" state (Section 2.3.3 )
fi
else
Remain in "Wait for PM inputs" state (Section 2.3.2).
fi
2.3.3. Wait for PCI-ANR child thread(s) action completion
When an indication that PCI-ANR child thread(s)' actions are completed is received, go to Step 2.3.2.2.1. If any PM inputs are received, go to Step 2.3.2.
2.3.4. Wait for Policy response
Upon reception of Policy response or Policy_rsp timeout, check if any pending ANR updates are to be sent to Policy. If any present, then go to Step 2.3.2.2, else update PM-based ANR actions are completed, and go to "Wait for PM inputs" state (Section 2.3.2).