/
Release "N"

Release "N"

Table of Contents

Subpages

 

 

Scope

This page is the RASC entry for release N.

You find the O-RAN-SC project specific details as summary in the following page: N-Release Timeline

Objectives

In the N Release the O-RAN-SC projects should show case a use case which should show the integration across the projects.

 

new functions to be demoed from @subhash 

 

O-RAN-SC Security use case (???)

to be updated

Goals: 

  • all modules in one lab / setup 

  • then we can start integration 

  • and use cases

Intelligent:  SMO - AIMLFW - NonRtRic - NearRtRic - using Viavi RAN simulators/RIC Test → Env 1

RAN: O-DU-High/Low → Env 2

→ basic-end-to-end  / system-health-check → even between both Envs - switch between both Envs makes it possible to show demos between both 

 

meaning of "health-check" use case - use case description 

  • application vs. platform

  • a description per PTL/Project

    • needed to support use case by INT

  • Idea: copy Health-Check Use Case and subpages into L-Release and then update based on current functionality

Intelligent LCM

Goals: 

  • detect vRAN application failure from O1/A1/O2 and repair the vRAN application by healing as typical telco usecase

  • End to End procedure from vRAN to RIC and NFO in SMO, and DMS and IMS in O-Cloud

  • Integration among StarlingX, OpenStack Tacker, Devtron, and RIC

Scenario 1:
vRAN
- get KPI -> O-Cloud (Prometheus & Tacker)
- metrics → NFO (Devtron analyze)
- healing request → DMS (Tacker)
- recreate resource → vRAN

  • measure KPI of vRAN by Prometheus

  • send metrics from DMS by O2 to NFO (Devtron)

  • analyze metrics by Policy in NFO (Devtron), like performance degradation

  • NFO (Devtron) request healing to DMS (Tacker)

Scenario 2 (future release):
vRAN
- alarm -> SMO
- alarm→ RIC (analyze)
- healing request → NFO (Devtron)
- healing request → DMS (Tacker)
- recreate resource → vRAN

  • vRAN detect issue as application level without resource level failure

  • RIC analyze alarm reported by O1

  • RIC request healing to DMS (Tacker) via NFO (RIC)

 

 

SMO demo 

  • tacker team - OpenStack, K8s

  • target is O2-PM

  • O2 interface

  • application deployment 

  • O-DU deployment

  • Idea: topo function from SMO for integration with other O-RAN-SC function

 

First step:

  • get the "old" health-check and other "old" use cases up and running again on the INT lab

Note: 

  • of cause pairwise use cases are expected

<to be defined>