This page describes how to demonstrate the entire flow from the OSC Non-RT RIC Control-Panel → ONAP A1 Policy Management Service →  ONAP A1 controller Controller in SDNC -> OSC near-RT-RIC/A1 Simulator

...

Overview of the End to End call

Image Added

Details of the architecture can be found from the following link: Jakarta Release

Image Removed

End to End call

From OSC NONRTRIC Control Panel to OSC Near-RT RIC simulator via ONAP A1 Policy Management Service & ONAP A1 Adapter

...

See instructions on configuring & running the A1 Policy functions (Jakarta).

Perform Policy Operations via Dashboard

...

• Click on '+' icon to create new policy

• Choose your ric (ric3 or ric4) from drop-down menu and provide any arbitrary values for QoS Id, Ue Id and Priority

• Submit the policy clicking the Submit button

...

• An entry to the chosen Near-RT RIC simulator console/log should appear (see, for example, docker logs ric3 in case ric3 policy was created):

127.0.0.1 - - [23/Sep/2021 11:58:57] "PUT //A1-P/v2/policytypes/STD_QOS2_0.1.0/policies/c897eabc-82cb-4bac-baa6-a5dbaef71694 HTTP/1.0" 200 -

Other logs can also be checked, for example is A1-Adapter.log that can be found inside sdnc-controller container, path: /opt/opendaylight/data/logs

|Put A1 Policy :|http://ric3:8085//A1-P/v2/policytypes/STD_QOS2_0.1.0/policies/c897eabc-82cb-4bac-baa6-a5dbaef71694|{"qosObjectives":{"priorityLevel":2},"scope":{"qosId":"123","ueId":"234"}}|
|Setting variables for Put A1 Policy.|http://ric3:8085//A1-P/v2/policytypes/STD_QOS2_0.1.0/policies/c897eabc-82cb-4bac-baa6-a5dbaef71694|{"qosObjectives":{"priorityLevel":2},"scope":{"qosId":"123","ueId":"234"}}|

...