RIC Dashboard Overview

The O-RAN SC RIC Dashboard provides administrative and operator functions for a radio access network (RAN) controller. The web app is built as a single-page app using an Angular (version 8) front end and a Java (version 11) Spring-Boot (version 2.1) back end.

Project Resources

The source code is available from the Linux Foundation Gerrit server:

The build (CI) jobs are in the Linux Foundation Jenkins server:

Issues are tracked in the Linux Foundation Jira server:

Project information is available in the Linux Foundation Wiki:

A1 Mediator

The Dashboard interfaces with the A1 Mediator. This platform component is accessed via HTTP/REST requests using a client that is generated from an API specification published by the A1 Mediator team.

The A1 Mediator supports fetching and storing configuration of applications, which is referred to as getting or setting a policy. The Dashboard UI provides screens to view and modify configuration data for such applications. As of this writing, the only application that is managed via the A1 Mediator interface is the Admission Control (“AC”) application.

Application Manager

The Dashboard interfaces with the Application Manager. This platform component is accessed via HTTP/REST requests using a client that is generated from an API specification published by the Application Manager team.

The Application Manager supports deploying, undeploying and configuring applications in the RIC. The Dashboard UI provides screens for these functions.

Automatic Neighbor Relation Application

The Dashboard interfaces with the Automatic Neighbor Relation (ANR) application. This RIC application is accessed via HTTP/REST requests using a client that is generated from an API specification published by the ANR team.

This RIC application discovers and manages the Neighbor Cell Relation Table (NCRT). The Dashboard UI provides screens to view and modify NCRT data.

E2 Manager

The Dashboard interfaces with the E2 Manager. This platform component is accessed via HTTP/REST requests using a client that is generated from an API specification published by the E2 Manager team.

The E2 Manager platform component supports connecting and disconnecting RAN elements. The Dashboard UI provides controls for operators to create “ENDC” and “X2” connections, and to disconnect RAN elements.