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 |
2020-06-21 |
Bronze |
CMCC |
Bronze Release |
2020-12-21 |
Cherry |
CMCC |
Cherry Release |
2021-07-15 |
D |
CMCC |
D Release |
2021-12-15 |
E |
CMCC |
E Release |
2022-7-06 |
F |
CMCC |
F Release |
2022-12-16 |
G |
CMCC |
G Release |
2023-7-04 |
H |
CMCC |
H Release |
2023-12-04 |
I |
CMCC |
I Release |
Release Summary
RAN Intelligent Controller Applications (RICAPP) features
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 HelloWorld(HW) xAPP repository contains open-source code for a prototype xAPP for near real-time RAN Intelligent Controller.
The KPI Mon xAPP, which supports full closed loop control for CuCpResourceStatusReport from multiple gNBs and stores the metrics in Redis DB.
QoE Predictor (QP) is an Xapp in the Traffic Steering O-RAN use case.
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.
The MC xAPP, which supports calculation of a number of metrics and KPIs based on X2 messages received from UEEC.
Anomaly Detection (AD) is an xApp in the Traffic Steering O-RAN use case.
This repository contains open-source code for a prototype HW-go xAPP for near real-time RAN Intelligent Controller which makes use of go Xapp Framework.
Near Realtime RAN Intelligent Controller (RIC) features
The RAN Intelligent Controller (RIC) Platform’s A1 Mediator component listens for policy type and policy instance requests sent via HTTP (the “northbound” interface), and publishes those requests to running xApps via RMR messages (the “southbound” interface).
Asn1-documents, which contains a description of the E2 used in the near-RT RIC implementation under O-RAN-SC.
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.
Golang, which is an implementation of a structured logging library with Mapped Diagnostics Context (MDC) support.
Jaegeradapter, which contains jaeger configuration files. This first version only supports configuration for a jaeger-all-in-one deployment.
LOG, which is a thread-safe logging C API library with Mapped Diagnostics Context (MDC) support.
PYLOG, which implements a structured logging library with Mapped Diagnostic Context (MDC).
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.
Streaming Protobufs, which provides a Protobuf schema for selected set of X2 Application Protocol messages.
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).
xapp-frame is a simple framework for rapid development of RIC xapps, and supports various services essential for RIC xapps such as RESTful APIs, RMR (RIC Message Routing), database backend services and watching and populating config-map changes in K8S environment
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
5G NR which is a RAN Software Reference Design for a 5G protocol stack
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
RTP O2 repository implements a reference O2 IMS and DMS service to expose O2 interface to SMO.
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-DEV which integrates artifacts for developing Near Realtime RAN Intelligent Controller applications (xApps).
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 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.
Service Management and Orchestration (SMO) features
SMO O1 repository is for the implementation, installation, and use of the O1 interface of SMO. It uses the Software Defined Netowrk (SDN) Controller for Radio (SDNR) to implement the O1 interface. The software comes in the form of Docker containers that are setup using docker-compose.
The O1/VES interface supports the monitoring side of SMO. The diagram below shows how the Network Elements interact with the O1/VES interface in the SMO.
SMO-O2 repository is for the implementation, installation, and use of the O2 interface of SMO. It uses the OpenStack Tacker to implement the O2 interface.