tree: ffd9908fe66b98cc54e9b243809a2c789e159e34 [path history] [tgz]
  1. api/
  2. src/
  3. test/
  4. .gitattributes
  5. .gitignore
  6. container-tag.yaml
  7. Dockerfile
  8. LICENSES.txt
  9. README.md
near-rt-ric-simulator/README.md

O-RAN-SC Near-RealTime RIC Simulator

The O-RAN SC Near-RealTime RIC simulates the A1 as an generic REST API which can receive and send northbound messages. The simulator validates the payload and applies policy.

The simulator supports multiple A1 interface versions (version of the open API yaml file):

  • OSC 2.1.0, version-id: OSC_2.1.0
  • A1 Standard 1.1.3, version-id: STD_1.1.3
  • 1.1.x-alpha.2 , version-id: 1.1.x-alpha.2

All versions are supported by the same container, see section 'Configuring the simulator' below for details about how to the start the simulator with the correct version.

The overall folder structure is (relative to the location of this README file): . Dockerfile and README api The open api yaml for each supported version src Python source code for each supported version test Basic test

The simulator handles the requests that are defined in the A1 open API yaml file. All these requests are in the a1.py file in the source folder. In addition, a number of administrative functions are also supported and implemented by the main.py in the source folder.

The section below outlines the supported open api REST operations as well as the adminstrative REST operations.

Supported operations in simulator OSC 2.1.0

URIs for A1:

URIs for admin operations:

Supported operations in simulator A1 Standard 1.1.3

URIs for A1:

URIs for admin operations:

Supported operations in simulator 1.1.x-alpha.2

The available requests and the addresses are currently:

Nota Bene: It could happen that this page is not updated as soon as the yaml file is. The yaml file can be found under /near-rt-ric-simulator/a1-openapi.yaml.

Additionally, there are requests that are defined in main.py as an administrative API. The goal is to handle information that couldn't be handled using the A1 interface. The available requests and the addresses are currently:

The backend server publishes live API documentation at the URL http://localhost:8085/A1-P/v1/ui/

Configuring the simulator

A env variable, A1_VERSION need to be passed to the container at start to select the desired interface version. The variable shall be set to one of the version-ids shown in the table in the first section. For example A1_VERSIION=STD_1.1.3. In docker run the full command could look like this 'docker run -it -p 8085:8085 -e A1_VERSION=STD_1.1.3 a1test' where the variable is set with the '-e' flag.

Updating the openapi specs

The openapi specifications are stored in the 'api/<version>/'. If adding/replacing with a new file, make sure to copy the 'operationId' parameter for each operation to the new file.

Start and test of the simulator

First, download the sim/a1-interface repo on gerrit: git clone "https://gerrit.o-ran-sc.org/oransc/sim/a1-interface"

Goto the main directory, 'a1-interface/near-rt-ric-simulator'. There is a folder 'test/<version>/' for each supported simulator version. This folder contains a script to build and start the simulator (as a container in interactive mode), a script for basic testing as well as json files for the test script.

Go to the test folder of the selected version, 'test/<version>/.

Build and start the simulator container using: ./build_and_start.sh This will build and start the container in interactive mode. The built container only resides in the local docker repository. Note, the default port is 8085 which can be easily changed in the the script above as well as in the test script.

In a second terminal, go to the same folder and run the basic test script, basic_test.sh or commands.sh depending on version. This script runs a number of tests towards the simulator to make sure it works properply.

Only for version 1.1.x-alpha.2 Let the simulator run in one terminal; in another terminal, one can run the command ./commands.sh. It contains the main requests, and will eventually leave the user with a policy type STD_QoSNudging_0.2.0 and a policy instance pi1 with an enforceStatus set to NOT_ENFORCED and an enforce Reason set to 300. All the response codes should be 20X, otherwise something went wrong.

License

Copyright (C) 2019 Nordix Foundation. Licensed under the Apache License, Version 2.0 (the "License") you may not use this file except in compliance with the License. You may obtain a copy of the License at

  http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

For more information about license please see the LICENSE file for details.