2020-11-18 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)

00:00

Admin

@Martin Skorupski

Next meetings: 

2020-11-18 @Martin Skorupski

2020-11-25: @Martin Skorupski

2020-12-02: @John Keeney (Ericsson EST)

2020-12-08: @Martin Skorupski

2020-12-15: ???

00:05

O-RAN-SC

O-RAN-SC PTLs

Status reports:

• SMO:

  • init package spec 

    • standardization in O-RAN 

    • CNF package meeting 

  • package validation demo

  • This is the Gerrit submission for the Postman script. https://gerrit.o-ran-sc.org/r/c/smo/o1/+/4998

• Non-RT-RIC:

  • focus - R3 (Cherry) - code freeze - documentation in ONAP ongoing ...

  • http proxy and rest config the function 

    • Non-RT-RIC - bundle function into the same controller as OAM as deployment option

  • ONAP pull to O-RAN-SC (code is hosted in ONAP)

  • Deployment based on OOM

  • policy enrichment functions

  • end-to-end testing

    • heath check

    • Traffic steering

• SIM:

  • wiki for yang-validation: https://wiki.o-ran-sc.org/display/IAT/Sim-01+YANG+model+verification

  • by John: A1 sim is workinfg fine

• OAM:

  • documentation!!! (dont forget ) 

  • Preparation for demo videos for C-Release

    • Basic Fault 

      • VES for O1

      • NetConf notification for O-RAN Fronthaul

    • Basic PM

      • VES file ready from O1-Sim

      • FTPes to O1-Sim

      • PM-mapper

      • using a REST client for VES-PM on DMaaP

    • Basic Config

      • alarm-list

      • inventory

      • visualization and modification of O-RAN-FH parameters

00:22

Use Case

@Swaminathan Seetharaman

Use Cases

Please see:  Potential ONAP <-> O-RAN collaboration use cases

00:25

@Mahesh

Application Package Structure

• TOSCA 

Info from @Michela Bevilacqua

• ONAP enhanced TOSCA 

• API schema definition for YANG and VES

On the agenda for next week - thanks!!! 

@Zu Qiang presenting ONAP on-boarding package

--

CNF packaging and App packaging - seems there is some overlap?!?!?

00:30

Questions and Answers

• data model - from Bitbucket DM with 3GPP and O-RAN (draft - November train)

• closed loop use case with A1 and O1 

  • E2 sim functions may needed

Use Case 

•  

  • O-RAN-FH node (VES triggers O1 change)

    • VES-fault-event

    • you see it on DMaaP

    • fault to DMaaP

    • SMO app via OAM config change (see POSTMAN scripts)

  • O1 - Near-RT-RIC  (VES triggers A1 change)

    • VES-fault-event

    • you see it on DMaaP

    • Non-RT-RIC rApp reads from DMaaP

    • update A1 policy in Near-RT-RIC/xApp

APP package implementation

• once the package spec is available - what would be the next steps?

END

Backup

00:10

Mahesh

Postman scripts to interface with the SMO and in turn test O1 interface between the SMO and different parts of O-RAN instances of O-CU, O-DU, O-RU and RIC using these models. 

• yang modules

• framework for test and validate CM 

share content in in SMO gerrit and create wiki linking to the same source

• Working on a framework for vendors for OAM/YANG tests

• O-RAN-SC to host the framework

• Postman and vsCode as RestClients

• Alex about to setup a SIM in OSC lab - involve Rittwik in a O-RAN private lab

• OpenFronthaul

• 3GPP models are considered.

Feedback from Rittwik

• SMO in T-Labs

• how to run Netopeer server - req to Felix (O-RAN-SC INT PTL)

• Alex asked for VMs 

Init script (Postman) for O-RAN OAM FH M-Plane (o-ran-interface.yang augmenting ) interface demoed

RFC8040 (RestConf by IETF) support supported by ODL

00:25

@Konrad Bańka

Konrad is absent this week. The presentation will be made when Konrad is available.

O-RAN Component deployment

The question is: How to deploy the red colored CNFs/VNFs of the O-RAN-Architecture?

• CNF for O-RAN-components 

  • model of CNF - how to be configured, how many components, blueprints

  • CDS model needs to be created

  • Network-service based on several CNFs

    • CNF types

      • Near-RT-RIC

      • O-CU-UP

      • O-CU-CP

      • O-DU

For detailed discussion the following page was created:

• CNF deployment of O-RAN Components 

Package

• for Network Functions (priority)

• for Network Service (second step)

CNFs or VNFs

• both should be considered 

  • let's start with CNFs first

  • VNF is considered as additional option

• no CNFs and VNFs combined in a single package

  • maybe not for rApps → 

  • VNF should take care about internal CNFs