Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

All four components of these Non-RT RIC function run as docker containers and communicate via a private docker network. Details of the architecture can be found from Honolulu Release page.

  • Project Requirements

  • Build Code

    • Build Policy Management Service container

      • Configure A1 Policy Management Service

      • Build the code and create docker image

    • Build A1 Adapter for Controller

      • Build the code and create docker images

  • Run Controller with OSC A1 Adapter

  • Run Near-RT RIC A1 Simulator Docker Containers

  • Run A1 Policy Management Service Docker Container

    • A1 Policy Management Service Swagger API

  • Run OSC Non-RT RIC Control Panel Docker Container

    • Open OSC NONRTRIC / A1 Policy Control Panel UI

...

Code Block
languageyml
titleapplication_configuration.json
{
  "config": {
    "//description": "Application configuration",
    "controller": [
      {
        "name": "controller1",
        "baseUrl": "http://sdnc_controller_container:8181",
        "userName": "admin",
        "password": "Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U"
      }
    ],
    "ric": [
      {
        "name": "ric1",
        "baseUrl": "http://ric1:8085/",
        "controller": "controllercontroller1",
        "managedElementIds": [
          "kista_1",
          "kista_2"
        ]
      },
      {
        "name": "ric2",
        "baseUrl": "http://ric2:8085/",
        "controller": "controllercontroller1",
        "managedElementIds": [
          "kista_3",
          "kista_4"
        ]
      },
      {
        "name": "ric3",
        "baseUrl": "http://ric3:8085/",
        "controller": "controllercontroller1",
        "managedElementIds": [
          "kista_1",
          "kista_2"
        ]
      },
      {
        "name": "ric4",
        "baseUrl": "http://ric4:8085/",
        "controller": "controllercontroller1",
        "managedElementIds": [
          "kista_1",
          "kista_2"
        ]
      }
    ]
  }
}

...

  • Start docker containers for each ric defined in oran/a1-policy-management/config/application_configuration.json in the step for "Configuration Policy Management Service" (in this example for ric1 and ric2) and providing A1 interface version OSC_2.1.0 with the following commands (use separate shells):

    Code Block
    languagebash
    $ docker run -p 8085:8085 -p 8185:8185 -e A1_VERSION=OSC_2.1.0 -e ALLOW_HTTP=true --network=nonrtric-docker-net --name=ric1 nexus3.o-ran-sc.org:10002/o-ran-sc/a1-simulator:2.1.0
    $ docker run -p 8086:8085 -p 8186:8185 -e A1_VERSION=OSC_2.1.0 -e ALLOW_HTTP=true --network=nonrtric-docker-net --name=ric2 nexus3.o-ran-sc.org:10002/o-ran-sc/a1-simulator:2.1.0
    $ docker run -p 8087:8085 -p 8187:8185 -e A1_VERSION=STD_2.0.0 -e ALLOW_HTTP=true --network=nonrtric-docker-net --name=ric1ric3 nexus3.o-ran-sc.org:10002/o-ran-sc/a1-simulator:2.1.0
    $ docker run -p 8088:8085 -p 8188:8185 -e A1_VERSION=STD_2.0.0 -e ALLOW_HTTP=true --network=nonrtric-docker-net --name=ric2ric4 nexus3.o-ran-sc.org:10002/o-ran-sc/a1-simulator:2.1.0


  • Create a policy type json to load into the A1 simulators (running version OSC.2.1.0)

    Code Block
    languagebash
    titlept1.json
    {
      "name": "pt1",
      "description": "pt1 policy type",
      "policy_type_id": 1,
      "create_schema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "title": "OSC_Type1_1.0.0",
        "description": "Type 1 policy type",
        "type": "object",
        "properties": {
          "scope": {
            "type": "object",
            "properties": {
              "ueId": {
                "type": "string"
              },
              "qosId": {
                "type": "string"
              }
            },
            "additionalProperties": false,
            "required": [
              "ueId",
              "qosId"
            ]
          },
          "qosObjectives": {
            "type": "object",
            "properties": {
              "priorityLevel": {
                "type": "number"
              }
            },
            "additionalProperties": false,
            "required": [
              "priorityLevel"
            ]
          }
        },
        "additionalProperties": false,
        "required": [
          "scope", "qosObjectives"
        ]
      }
    }


  • Put the example policy type into the started A1 simulator instances by running these curl commands (in this example to ric1 exposed to port 8085 and ric2 exposed to port 8086):

    Code Block
    languagebash
    $ curl -X PUT -v "http://localhost:8085/a1-p/policytypes/1" -H "accept: application/json" \
     -H "Content-Type: application/json" --data-binary @pt1.json
    $ curl -X PUT -v "http://localhost:8086/a1-p/policytypes/1" -H "accept: application/json" \
     -H "Content-Type: application/json" --data-binary @pt1.json


  • Create a policy type json to load into the A1 simulators (running version STD.2.0.0)

    Code Block
    languagebash
    titlestd_qos2_0.0.1.json
    {
        "policySchema": {
          "$schema": "http://json-schema.org/draft-07/schema#",
          "title": "STD_QOS2_0.1.0",
          "description": "STD QOS2 policy type",
          "type": "object",
          "properties": {
            "scope": {
              "type": "object",
              "properties": {
                "ueId": {
                  "type": "string"
                },
                "qosId": {
                  "type": "string"
                }
              },
              "additionalProperties": false,
              "required": [
                "ueId",
                "qosId"
              ]
            },
            "qosObjectives": {
              "type": "object",
              "properties": {
                "priorityLevel": {
                  "type": "number"
                }
              },
              "additionalProperties": false,
              "required": [
                "priorityLevel"
              ]
            }
          }
        },
        "statusSchema": {
          "$schema": "http://json-schema.org/draft-07/schema#",
          "title": "STD_QOS_0.2.0",
          "description": "STD QOS policy type status",
          "type": "object",
          "properties": {
            "enforceStatus": {
              "type": "string"
            },
            "enforceReason": {
              "type": "string"
            },
            "additionalProperties": false,
            "required": [
              "enforceStatus"
            ]
          }
        }
      }


  • Put the example policy type into the started A1 simulator instances by running these curl commands (in this example to ric3 exposed to port 8087 and ric4 exposed to port 8088):

    Code Block
    languagebash
    $ curl -X PUT -v "http://localhost:8087/policytype?id=STD_QOS2_0.1.0" -H "accept: application/json" \
     -H "Content-Type: application/json" --data-binary @std_qos2_0.0.1.json
    $ curl -X PUT -v "http://localhost:8088/policytypespolicytype?id=STD_QOS2_0.1.0" -H "accept: application/json" \
     -H "Content-Type: application/json" --data-binary @std_qos2_0.0.1.json


...

Code Block
languagebash
$ docker logs policy-management-service | grep "protocol versionchecked" 
20202021-1103-2316 1614:0015:2703.484805 DEBUG 1 --- [or-http-epoll-5] o.o.c.o.a.clientstasks.A1ClientFactoryRicSupervision        : Established protocol version:SDNC_OSC_OSC_V1 for Near-RT RIC: ric1
2020-11-23 16:00:27.495 Ric: ric1 checked OK
2021-03-16 14:15:03.816 DEBUG 1 --- [or-http-epoll-6] o.o.c.o.a.clients.A1ClientFactorytasks.RicSupervision           : Ric: Established protocol version:SDNC_OSC_OSC_V1 for Near-RT RIC: ric2ric3 checked OK
2021-03-16 14:15:03.835 DEBUG 1 --- [or-http-epoll-1] o.o.c.o.a.tasks.RicSupervision           : Ric: ric2 checked OK
2021-03-16 14:15:03.851 DEBUG 1 --- [or-http-epoll-2] o.o.c.o.a.tasks.RicSupervision           : Ric: ric4 checked OK

A1 Policy Management Service Swagger API

...