As an ONAP Drools Policy Designer, I want to ensure that the usecases.drl can support the 5G OOF SON use case in that it handles incoming Control Loop Events so that events do not get removed from Drools working memory if CLC returns a “deny”. In the current scenario, when CL event is sent to policy, and the CLC response for the event is a deny, the event errors out and is removed from the memory. Semantically, the CLC “deny” primarily due to the fact that at that moment, other control loops are running which conflict with the current request. Hence, instead of dropping the event, policy must queue the event and query CLC again at a later time. To achieve this, a 1 element queue must be maintained by policy with the following queue characteristics:

• Mechanism to cancel the queue — sent by the sender
• Mechanism to tell the requester to tell that I am holding the queue — so hold back further messages
• Hold just one message in the queue — and tell the sender MS that it is a deny
• Retry based on a time interval or response from SDNR