G release highlights/accomplishments (16-Dec-2022):

AD xApp :-

• Removal of pushing data into influxdb when xApp starts.

1. Either UE's KPIs should be continuously stored into influxDB from KPIMON OR
2. We will need to run script manually to populate influxDB from .csv separately 

• changes in AD xApp to read live data from influxDB for inference
• Addition of Python script to read static data and keep pushing into RICPLT lnfluxDB
• Addition of exception module to handle errors and exceptions
• Addition of configuration module to update
  • InfluxDB configuration (near RT RIC instance or external)
  • KPIs 
• parameter tuning and functionality addition for improvements

QP xApp :-

• Removal of pushing data into influxdb when xApp starts.

1. Either UE's KPIs should be continuously stored into influxDB from KPIMON OR
2. We will need to run script manually to populate influxDB from .csv separately 

• changes in QP xApp to read live data from influxDB for inference
• Addition of Python script to read static data from .csv and keep pushing into RICPLT lnfluxDB
• Addition of exception module to handle errors and exceptions
• Addition of configuration module to update
  • InfluxDB configuration (near RT RIC instance or external)
  • KPIs 
• Model validation, parameter tuning and functionality addition for improvements

Gerrit Reviews

KPIMON-GO xApp :-

• E2SM KPM version upgraded to 2.0
• Added a feature to build a RAN cell map. 

RC xApp:

• Upgrading the RC service model to 1.0.3.

Bugs fixes:→

• The E2SM RC control request structure was not properly set. (Ran parameter id 3 is missing in final Rc control structure)
• values in control request header and control request message are incorrectly set.

TS xApp:

• upgraded proto file in order to match with the proto file of latest RC xApp.
• modified - NodebHandler to build CELL-RAN map (cell_map) properly.

G release source code, container images and deployment instructions

The list of container images for the G release (link)

Code Coverage Reports : Latest reports can be found at the following Link: Projects - O-RAN Software Community (sonarcloud.io).

Primary Goals:

The SMO acts as an uber identity that overlooks the different aspects of the O-RAN deployment. Starting with how solutions are deployed, to how they interact with each other, to how they are managed.

G release Feature Scope: 

The focus for the G release in SMO is interoperability. Every sub-project within SMO has at least one item that focuses on interoperating with one other entity outside of SMO. For example,

• On the O1 interface, the focus is on trying to bring-up O-DU using NETCONF and YANG models defined for O-DU.
• On the O1/VES interface, it is ability to generate network slicing PM events in the O-DU, and the ability to receive them in SMO dashboard, and store them in InfluxdB.
• On the O2 interface, it will be the ability to instantiate an instance of a Network Function (NF) like the O-DU in the O-Cloud.

Separate from this, each sub-project within SMO has other features/capabilities it will address as part of the G-release. For details please refer to the minutes of the SMO meeting here.