OOF à SON-Handler MS à Policy (CL invoked) à SDN-R à RAN

Now, in above flow, upon reception of a trigger from SON Handler MS, a Control Loop is invoked in Policy, with actor as SDN-R. Policy then sends a DMaaP message to SDN-R.

Due to whatever reason, if SDN-R or RAN is unable to carry out the actions (i.e., failure or partial failure), the entity that triggered the control loop (SON-Handler MS in this case) should be informed. So we are looking at SDN-R sending a notification to Policy, which, in turn, notifies SON-Handler MS.

If we extend the original control loop so that Policy waits for response from SDN-R, this means Policy would have to maintain state perhaps. Another alternative would be SDN-R invokes a new control loop to send the response to SON-Handler MS (via Policy) – but this may not be fully in line with the original control loop philosophy. Do you see any other mechanism?

Dublin Work Flows

https://wiki.onap.org/display/DW/Dublin+Control+Loop+Workflows