This Jira is a placeholder for any change needed in Policy for SON Use Case.

The SON Use Case has two types of DMaaP Control Loop messages. One for ANR and one for PCI.

#ANR message sample
{"closedLoopControlName":"ControlLoop-vSONH-7d4baf04-8875-4d1f-946d-06b874048b61",
..
"Action":"ModifyConfigANR"}

The second is for PCI

#PCI message sample
{
   "closedLoopControlName":"ControlLoop-vPCI-fb41f388-a5f2-11e8-98d0-529269fb1459",
..
   "Action":"ModifyConfig" }
{color:#de350b}}

Both are received by Policy over DMaaP from SON-Handler, and both are forwarded by Policy over DMaaP to SDN-R. For Kohn release there is no change to the PCI message flow, and SDN-R will process this as a netconf edit action sent to RAN-Sim and send back an acknowledgment.

For ANR, there is a change for Kohn release in the way this message is generated in SON-Handler MS and the way it is processed in SDN-R which sends a A1 policy message to RAN-Sim. We need to explore what change is needed in Policy to support a use case with both O1 and A1 based actions.