This page describes how to demonstrate the entire flow from Non-Rt RIC Controlpanel Controlpanel  -> Policy Agent -> (A1 controller in SDNC) -> Near Realtime Ric Simulator. Optionally A1 controller can be left out.

...

• Open Dashboard UI at http://localhost:8080/

• Click on Config and the screen below with STD_QosNudging_0.2.0 policy type should open

Image Modified

• Click on '+' icon to create new policy

Image Modified

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

...

Call from CCSDK A1 Controller to NearRT-RIC simulator

Testing calls with Limited tests to verify just OSC CCSDK A1 Controller calls towards NearRT-RIC simulator can be done by using ODL GUI. Dashborad Dashboard and policy-agent does not need to be running are not needed in this case.

Preparation

See Release A - Build/Run for building and starting the environment. If following those instructions, just skip the following steps:

• Release A - Build/Run#RunPolicy-agentDockerContainer

• Release A - Build/Run#RunNon-RT-RICDashboardDockerContainer

...

• Open GUI: Release A - Build/Run#OpenDaylightGUI
• Click Sub API: 

  A1-ADAPTER-API(2020-01-22)

Get policy types

Payload

{
  "A1-ADAPTER-API:input": {
    "near-rt-ric-url": "http://ric1:8085/"
  }
}

Image Added

Create policy

Payload

{
  "A1-ADAPTER-API:input": {
    "near-rt-ric-url": "http://ric1:8085/",
	"policy-id": "my-policy-instance1",
    "policy-type-id": "STD_QoSNudging_0.2.0",
	"policy": '{
      "scope": {
      "qosId": "999",
      "ueId": "5001"
      },
      "statement": {
      "priorityLevel": 5
      }
    }'
  }
}

Image Added

Get policy instances

Payload

{
  "A1-ADAPTER-API:input": {
    "near-rt-ric-url": "http://ric1:8085/"
  }
}

Image Added