...
The main actions in the various states are listed below:
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
2.1.1. Initialization
In this state, the following actions are performed:Gliffy Diagram
- Fetch Config Policy from CBS.
- Load any local configuration.
- Load data persisted in DB.
- Trigger DMaaP thread for registration of DMaaP topics (SDN-R, VES-Collector and Policy interfaces).
...
2.1.2.4. Policy response handling
...
- Response from policy is handled by a separate thread.
- When positive acknowledgement is received from the policy the cells in the response are removed from the table and when negative acknowledgement is received the negative_ack count for the cell is increased and updated in the table. When no response is received no changes are made.
- When negative_ack count of a particular cell increases beyond a threshold, it is shifted to another table.
2.1.2.5. Child Thread Status update handling
...
These child threads are spawned for handling PCI optimization primarily, though they may also trigger PCI-ANR joint optimization in some cases. The various states and associated actions are described below.
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
|
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.
...
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.
...
Handling Policy Response
- Response
...
- from policy is handled by a separate thread.
- When positive acknowledgement is received from the policy, the cells in the response are removed from the table and when negative acknowledgement is received the negative_ack count for the cell is increased and updated in the table. When no response is received no changes are made.
- When negative_ack count of a particular cell increases beyond a threshold, it is shifted to another table.
2.2.7. Wait for RAN updates
...
This child thread perform all PM-related computations, and initiate autonomous ANR updates based on HO metrics.
| Gliffy Diagram | ||
|---|---|---|
|
...
|
...
|
...
|
2.3.1. Initialization
In this state, all data structures are initialized. This includes any processing-pending PM data, processed PM data and populating details from DB.
...
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
...
.
...
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).
2.3.4. Handling Policy response
- Response from policy is handled by a separate thread.
- When positive acknowledgement is received from the policy, the cells in the response are removed from the table and when negative acknowledgement is received the negative_ack count for the cell is increased and updated in the table. When no response is received no changes are made.
- When negative_ack count of a particular cell increases beyond a threshold, it is shifted to another table.