London - Testing end-to-end call

Owned by Sonia Sangari
Last updated: Sept 15, 2023 by John Keeney (Ericsson EST)
3 min read

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 in SDNC -> OSC near-RT-RIC/A1 Simulator

Overview of the End to End call


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

End to End call

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

Preparation

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

Perform Policy Operations via Dashboard

  • Click on Policy Control and the screen below with STD_QOS2_0.1.0 policy type should open


  • 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/Aug/2023 11:18:56] "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"}}|

  • You may repeat the creation process a few times for different rics - below we see several policy created to different rics.


  • Click the pen icon to modify any policy


  • Modifications are submitted in the same way as in creation, and the resulting simulator log should also be same as the one we saw in creation

127.0.0.1 - - [23/Aug/2023 13:32:09] "PUT //A1-P/v2/policytypes/STD_QOS2_0.1.0/policies/c063a1e3-455a-41a5-b119-c25eadab7fd4 HTTP/1.0" 200 -

  • Delete any policy by clicking the red trashcan icon

  • Confirm deletion and verify the log on simulator side:

127.0.0.1 - - [23/Aug/2023 13:35:22] "DELETE //A1-P/v2/policytypes/STD_QOS2_0.1.0/policies/c063a1e3-455a-41a5-b119-c25eadab7fd4 HTTP/1.0" 204 -