...
The A1 Policy Management Service and the (optional) A1-enabled Controller (SDNC with A1-Adapter) will run in a local demonstrative deployment with four near-RT-RIC A1 simulator instances (docker containers). These simulators will be configured to emulate devices implementing either the "OSC_2.1.0" version or "STD_2.0.0" version of the O-RAN A1 interface. (For more information on the OSC A1 Simulator functions see OSC NONRTRIC Wiki page (Release D))
...
Copy the file oran/a1-policy-management/config/application_configuration.json to the current directory and update it with the configuration below.
(Note the configuration below is just a sample, and should be updated to match particular deployments. The deployment below assumes 4 near-RT-RICs exist - addressable at the urls given.)The controller hostname and port values come from and must match those defined in in the sdnc/oam repo oam/installation/src/main/yaml/docker-compose.yml (see the step "Run A1 Controller" further below). The port for http is 8181.
(Note the configuration below is just a sample, and should be updated to match particular deployments. The deployment below assumes an A1 Controller function (SDNC) exists - addressable at the url given, using the authentication credentials given.)Any defined ric host names (in the name and baseUrl for each ric) must match the given docker container names in near-RT-RIC simulator startup - port is always the simulator's internal port 8085 for http or 8185 for https.
- It The A1 Policy Management service can entirely by-pass the A1-Controller if required - it is optional to access the near-RT-RIC through a controller. The an A1-Controller.
In the configuration the "controller" property is optional in the "ric" objects. The A1 Policy Management service can entirely by-pass the A1-Controller if required.
If no controller is used, the whole , and the "controller" object at the top can be omitted if no controller is used.
There is no functional gain in accessing the near-RT-RIC through an A1 controller.
...