Release-Notes

This document provides the release notes for O-RAN SC.

Version history

Date Ver. Author Comment
2019-11-31 Amber CMCC Amber Release
       
       

Release Summary

RAN Intelligent Controller Applications (RICAPP) features

The MC xAPP, which supports calculation of a number of metrics and KPIs based on X2 messages received from UEEC.

The Acumos xAPP adapter, which contains the code needed to use an existing Acumos microservice as an O-RAN xAPP, by providing “glue” that listens and speaks RMR protocol and translates these into calls to the Acumos microservice, which is co-deployed in the same pod as the adapter.

GS-lite, which is an open-source, real-time, low-latency, high-throughput stream processing engine. It is a fork of cask/tigon (https://github.com/cdapio/tigon) maintained to serve the needs of RIC applications (currently MC xApp).

The AC xAPP, which supports full closed loop control as well as report mode operation for admission control of SgNB Addition requests, reporting of metrics over VES, and configuration of single instance policies via the A1-Interface.

The KPI Mon xAPP, which supports full closed loop control for CuCpResourceStatusReport from multiple gNBs and stores the metrics in Redis DB.

Near Realtime RAN Intelligent Controller (RIC) features

LOG, which is a thread-safe logging C API library with Mapped Diagnostics Context (MDC) support.

Golang, which is an implementation of a structured logging library with Mapped Diagnostics Context (MDC) support.

PYLOG, which implements a structured logging library with Mapped Diagnostic Context (MDC).

DBAAS, which is the needed elements to deploy database as a service (Dbaas) to kubernetes. Dbaas service is realized with a single container running Redis database. The database is configured to be non-persistent and non-redundant.

Shared Data Layer, which provides a lightweight, high-speed interface for accessing shared data storage. The purpose is to enable utilizing clients to become stateless, conforming with, e.g., the requirements of the fifth generation mobile networks.

Shared Data Layer, which provides a lightweight, high-speed interface for accessing shared data storage. The purpose is to enable utilizing clients to become stateless, conforming with, e.g., the requirements of the fifth generation mobile networks.

Jaegeradapter, which contains jaeger configuration files. This first version only supports configuration for a jaeger-all-in-one deployment.

Tracelibcpp library, which implements a function for creating a configured tracer instance. It hides the underlaying tracer implementation from the application. The library currently supports only Jaeger (https://www.jaegertracing.io/) C++ client (https://github.com/jaegertracing/jaeger-client-cpp) tracer implementation.

Tracelibgo library, which implements a function for creating a configured tracer instance. It hides the underlaying tracer implementation from the application. The trace library currently supports only Jaeger (https://www.jaegertracing.io/) golang client (https://github.com/jaegertracing/jaeger-client-go) tracer implementation.

The VESPA manager ,which uses the VES Agent (https://github.com/nokia/ONAP-VESPA) to adapt near-RT RIC internal statistics’ collection using Prometheus (xApps and platform containers) to ONAP’s VES (VNF event streaming).

Asn1-documents, which contains a description of the E2 used in the near-RT RIC implementation under O-RAN-SC.

Streaming Protobufs, which provides a Protobuf schema for selected set of X2 Application Protocol messages.

Non-RealTime RAN Intelligent Controller (NONRTRIC) features

In Bronze release, Non-RT RIC containes Policy Agent, Control Panel and A1 Simulator.

Operations and Maintenance (OAM) features

OAM which provides reference implementation according to the O-RAN OAM (WG1) documents.

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.

O-RAN Central Unit (OCU) features

OpenLTE, which is a RAN Software Reference Design for a 4G TDD

O-RAN Distributed Unit High Layers (ODUHIGH) features

O-DU Layer 2, which is O-DU layer intilaizations and exchange of F1 Setup Request, F1 Setup Response, GNB DU Config Update and GNB DU Config Update ACK between the ODU and CU STUB.

O-RAN Distributed Unit Low Layers (ODULOW) features

O-DU Layer 1, which is the O-RAN FHI Lib built on top of DPDK to perform U-plane and C-plane functions according to the ORAN Fronthaul Interface specification between O-DU and O-RU. S-Plane support requires PTP for Linux version 2.0 or later The management plane is outside of the scope of this library implementation.

Infrastructure (INF) features

Realtime Platform, which implements a real time platform to deploy the O-CU and O-DU components.

Integration and Testing (INT) features

IT-DEP hosts deployment and integration artifacts such as scripts, Helm charts, and other files used for deploying O-RAN SC software.

IT-TEST, which contains: Test automation scripts written using the robot frameworkDeployment scripts for a dev-test 1-node Kubernetes cluster. A functional simulator for the E2 protocol that acts as gNB used to test the RIC. A workload generator that is used to benchmark the RIC

IT-DEV which integrates artifacts for developing Near Realtime RAN Intelligent Controller applications (xApps).

IT-DEV includes the initial commit of the OTF platform code. Applications include otf-frontend, otf-service-api, otf-camunda, and several virtual test head microservices (ping, ssh, robot, ric). In addition setup documentation and installation guides are included to build docker containers and helm charts for deployment.