WORK IN PROGRESS

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: NewDelhi 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 (New Delhi).

Example of a docker compose with a single simulator (A configuration for a1pms and nonrtric-gateway has to be provided)

docker compose 
services:
  a1_policy_management:
    container_name: a1policymanagmentservice
    image: nexus3.onap.org:10002/onap/ccsdk-oran-a1policymanagementservice:1.7.0
    ports:
      - "8433:8433"
      - "8081:8081"
    volumes:
      - ./application_configuration.json.nosdnc:/opt/app/policy-agent/data/application_configuration.json:ro
    networks:
      - nonrtric-docker-net    


  ric1:
    image: nexus3.o-ran-sc.org:10002/o-ran-sc/a1-simulator:2.6.1
    container_name: ric1
    environment:
      - A1_VERSION=OSC_2.1.0
      - ALLOW_HTTP=true
    ports:
      - "8085:8085"
      - "8185:8185"
    networks:
      - nonrtric-docker-net


  nonrtric-gateway:
    image: nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-gateway:1.2.0
    container_name: nonrtric-gateway
    ports:
      - "9090:9090"
    volumes:
      - ./application-nonrtricgateway.yaml:/opt/app/nonrtric-gateway/config/application.yaml:ro
    networks:
      - nonrtric-docker-net

  nonrtric-control-panel:
    image: nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-controlpanel:2.5.0
    container_name: nonrtric-control-panel
    ports:
      - "8080:8080"
    networks:
      - nonrtric-docker-net
      
networks:
  nonrtric-docker-net:
    driver: bridge



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/202x 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/202x 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/202x 13:35:22] "DELETE //A1-P/v2/policytypes/STD_QOS2_0.1.0/policies/c063a1e3-455a-41a5-b119-c25eadab7fd4 HTTP/1.0" 204 -

  • No labels