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 based on the type of notification, go to either Section 2.2.1.1 or 2.2.1.2 for next actions.

...

Go to Step 2.2.1.5 below

else

Go to "wait Wait for notifications/alarms" state (Section

...

• Send a PCI_opt request to OOF with cells triggering the request along with the trigger type
• Store details of request in DB.
• Wait for OOF optimization result.

• Upon trigger from main thread with OOF PCI optimization result, prepare and send a DMaaP message messages 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: for the cells whose PCI value has changed, as well as to all the neighbors of the cells whose PCI value has changed. 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.

  Upon reception of response from OOF, prepare 
• Start Policy_rsp timer and wait for Policy response by going to "Wait for Policy Response" state (Section 2.2.6).

2.2.5. Trigger OOF, wait for PCI-ANR optimization results

• Fetch the list of cell pairs whose HO success is less than thresold_poor, but >= threshold_bad (this would have been prepared already by PM child thread and stored in DB).
• Send a Joint_PCI_ANR_opt request to OOF with cells triggering the request along with the trigger type, and list of 'removable neighbors'
• Store details of request in DB.
• Wait for OOF optimization result.

...

• .

...

• Start notif_timer if not started already, and wait for more notifications
• If a new notification is received, transition to Cluster modification state. If notif_timer expires, transition to Trigger OOF state.

2.2.6. Send PCI recommendations to Policy

• Upon trigger from main thread with OOF ANR-PCI optimization result

...

if response contains PCI updates

then

Prepare DMaaP messages to Policy for the cells whose PCI value has changed, as well as to all the neighbors of the cells whose PCI value has changed. 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)

fi

if response contains NRT updates (corresponding to ANR)

Update/prepare DMaaP messages to Policy for the cells whose neighbors have undergone updates. 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)

...

fi

• Send prepared message(s) to Policy. 

• Start Policy_rsp timer and wait for Policy response by going to "Wait for Policy Response" state (Section 2.2.6).

2.2.

...

6. Wait for Policy Response

Wait in this state until response is received from Policy or Policy_rsp timer expires. If any notification/alarm is received in this state, simply buffer/store them. Upon reception of Policy response or upon Policy_rsp timer expiry, log the details, start buf_timer (

...

to wait for updates from RAN) and transition to "Wait for RAN updates" state (Section 2.27).

2.2.7. Wait for RAN updates

Wait in this state until buf_timer expires. If any notification/alarm is received in this state, simply buffer/store them. Upon expiry of buf_timer,

...

Note: This is to allow changes to be implemented in that cluster by SDN-R, and RAN to send any new notifications upon neighbor list change (i.e., to minimize running the optimization algorithm unnecessarily).

check if there are any buffered notifications.

if there are buffered notifications/alarms

then

• Alarms: Based on OOF results and/or PM-based ANR updates check if any new alarms are automatically inapplicable, and remove them.
• Notifications: Based on OOF results and/or PM-based ANR updates check if any new neighbor list change notifications are automatically inapplicable (partially), and update them.
• Determine collisions/confusions, perform correlation of pending alarms and notifications to remove duplicate entries. Go to Step 2.2.1.3.

else

• Inform main thread of action completion

fi

2.3. PM-child thread

This child thread perform all PM-related computations, and initiate autonomous ANR updates based on HO metrics.

Gliffy
name PM child thread pagePin 7

2.3.1. Initialization