Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Near-Real-time RIC X-APPs (RICAPP)

Primary Goals:  

K release plan: 

wiki: RIC Applications (RICAPP) - RIC Applications - Confluence (o-ran-sc.org)

Latest Architecture: Architecture - RIC Applications - Confluence (o-ran-sc.org)

Components: 

Tasks / Backlog / JIRA: Near Realtime RAN Intelligent Controller Applications - ORAN Jira (o-ran-sc.org)

Gerrit / Source Code:

Jira: Count of Epics, User Stories, Tasks, and Issues:  Total (10)

Jira: Count of Epics, User Stories, Tasks, and Issues:  Total (10)

Completed Epics & Story:

RICAPP-232 - hw-rust xApp for i-release

RICAPP-230 - QP xApp (I-Release)

RICAPP-229 - Anomaly Detection xApp (I-Release)

RICAPP-224 - F1AP gnbDuConfigurationUpdate parser

RICAPP-223 - Creating UE/CELL metrics hashmap based upon the KPIS supported by each E2 node

RICAPP-222 - ASN decoders for kpm ran function description and asn encoders for action definition format1 and format3

Completed Tasks

RICAPP-231 - Fix issue of mismatch data type when AD writes data to InfluxDB

RICAPP-228 - Update RMR version and xapp frame to latest version

RICAPP-227 - dynamically adding fields to influxdb and changed the UE KPI parse logic as per indications coming from VIAVI RIC-Test

RICAPP-226 - Update KPM model to latest one

K release highlights/accomplishments:

K release source code, container images and deployment instructions

The list of container images 

Code Coverage Reports : 

...

Service Management and Orchestration Layer (SMO)

Primary Goals:

The primary goal of SMO in the H-release is to act as glue between the different components of O-RAN.

K release Feature Scope

Improve O2 DMS ETSi profile.

improve the NFO K8s profile integration with OSC-INF.

K release highlights/accomplishments ():

K release source code, container images and deployment instructions (and status)

K release source code for SMO can be found in the following repositories

The container images for SMO can be found on the Nexus server, where applicable.
The container images for OpenStack Tacker can be found in OpenStack Kolla repository.

The OpenStack Tacker container can be started with the steps in the following documentation.

The installation instructions for SMO can be found in the documentation page here.

Status

The status of the SMO project is tracked using Jira items. For the latest status refer to the items below.




...