Architecture for Guilin Release:

Non-RT RIC components:

Policy Management GUI / NONRTRIC Dashboard (in o-ran)

Policy agent / A1 Policy Management Service

SDNC A1 Adapter

Near-RT RIC / A1 Simulator (in o-ran)

The code base for Guilin Release is in the NONRTRIC, A1-Simulator, and NONRTRIC-ControlPanel source repositories (Gerrit)

Policy Management GUI / NONRTRIC Dashboard

Graphical user interface. This tool is available in o-ran gerrit repo and is not essential for the Non-RT RIC to function.

View and Manage A1 policies in the RAN (Near-RT RICs)

Interacts with the Policy agent’s NBI (REST API)

Graphical A1 policy creation/editing is model-driven, based on policy type’s JSON schema

Frontend: Angular framework

Backend Java Springboot application

Please refer this developer guide to set up in your local environment.

A1 Policy Management Service (“Policy Agent”)

The Policy Agent is a micro service which maintains a transient repository of:

All configured A1 policies instances in the network. Each policy is targeted to a Near-RT RIC instance and is owned by a 'service' (R-APP or the NONRTRIC Dashboard).

All Near-RT RICs in the network. This information can be maintained using the ONAP CDS database (which is using the Cloudify Consul database).

All Policy types for all Near-RT RICs

All configured Policy instances in the network

It provides :

Unified REST & DMAAP APIs for managing A1 Policies in all near-RT RICs

Synchronized view of policy instances for each R-APP (soon)

Synchronized view of policy instances in all Near-RT RICs

Synchronized view of policy types in all Near-RT RICs

Policy Query API (e.g. per Near-RT RIC, per R-APP (soon), per policy type)

Unified nearRTRIC-ID to nearRTRIC-address mapping (e.g. can include mapping to A&AI, CMDBs etc to “find” Near-RT RICs - soon)

Placeholder “O1 ManagedElement” mapping database interface to find appropriate Near-RT RIC to address A1 operations for required RAN elements (e.g. connection to A&AI, RuntimeDB, other CMDBs etc - soon)

Monitors all Near-RT RICs and recovers from inconsistencies (multiple strategies - soon) – e.g. Near-RT RIC restarts

Support for different Southbound connectors per Near-RT RIC – e.g. different A1 versions, different Near-RT RIC version, different A1 adapter/controllers supports different or proprietary A1 controllers/EMSs

Controller / A1 Adapter:

Mediation point for A1 interface termination in SMO/NONRTRIC

Implemented as OSGI Feature/Bundles

A1 Rest southbound

NETCONF YANG Northbound

RESTCONF > NETCONF adapter

Mapping logic / Provider

Can be included in an any SDNC/CCSDK persona

Near-RT RIC Simulator:

Stateful A1 test stub

Used to create multiple stateful A1 providers (simulated Near-RT RICs)

Implemented as a Java Springboot application

Swagger-based northbound interface, so easy to change the A1 profile exposed