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.
Table of Contents
Overview of the End to End call
Details of the architecture can be found from the following link: Release A
...
End to End call from Dashboard to NearRT-RIC simulator
Preparation
See Release A - Build/Run for building and starting the environment.
Either option A or B can be setup and all end to end actions from Dashboard should work same way.
Perform Policy Operations via Dashboard
...
172.18.0.3 - - [02/Apr/2020 08:02:21] "DELETE /A1-P/v1/policies/ac3e914a-b39c-4d93-b77c-d2ebac756267 HTTP/1.1" 204 -
Call from CCSDK A1 Controller to NearRT-RIC simulator
Limited tests to verify just OSC CCSDK A1 Controller calls towards NearRT-RIC simulator can be done by using ODL GUI. Dashboard and policy-agent 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:
Now only "a1-controller-container" and "sdnc_db_container" and simulators are running.
Perform Policy Operations via Open Daylight GUI
- Open GUI: Release A - Build/Run#OpenDaylightGUI
- Click Sub API:
Get policy types
Payload
| Code Block | ||||
|---|---|---|---|---|
| ||||
{
"A1-ADAPTER-API:input": {
"near-rt-ric-url": "http://ric1:8085/"
}
} |
Create policy
Payload
| Code Block | ||||
|---|---|---|---|---|
| ||||
{
"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
}
}'
}
} |
Get policy instances
Payload
| Code Block | ||||
|---|---|---|---|---|
| ||||
{
"A1-ADAPTER-API:input": {
"near-rt-ric-url": "http://ric1:8085/"
}
} |
