...
...
...
This page describes how to demonstrate the entire flow for Non-Realtime RIC using Release Ean end-to-end example of manipulating A1 Policies using the F Release functions for A1 Policies.
Table of Contents
Overview of the End to End call
Details of the architecture can be found from the following link: Release EF
Preparation
It is recommended to use it/dep repo as it has ready to use helm charts and test data to create and populate data into nonrtric k8s deployment.
...
End to end call from Policy Management
End to End call from Policy Control GUI to A1 (previously called Near-RT RIC A1 Interface) simulator
Perform Policy Operations via Control Panel
...
In this case port for HTTP connection would be 30091 and for HTTPS 30092.
Pic is out of date!
- Click on Policy Control and the screen below with policy types should open
Wrong Pic?!
- For each policy type there is a '+' icon to create a new policy of that specific type. Click on '+' icon to create new policy
- Choose your ric from drop-down menu and provide any arbitrary values for QoS-ID, UE-ID and Priority
...
- Submit the policy
- An entry to the chosen A1 simulator (previously called Near-RT RIC simulator A1 Interface) console/log should appear (see, for example, kubectl logs -n nonrtric a1-sim-osc-0 in case ric1 policy was created):
...
End to end call from Information Coordinator Service
Pic is out of date!
From the Control Panel, Producer and Jobs can only be listed.
Pic is out of date!
In Kubernetes cluster setup, The Information Coordination Service (ICS) is not exposed outside the k8s clusteris not exposed outside, hence the commands for populating Information Jobs/Consumers/Producers need to be run from within the cluster.
In order to execute other local Kubernetes setup (Docker Desktop, Minikube, etc..), actions such as create, modify and delete, curl can be use to interact with ICS API using NodePort from control panel.
...