2020-10-28 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)

Next meeting: 2020-11-04
Summer time ends in NorthAmerica Sunday 01-11-2020

16:00 UTC / 8am PST/ 11:am EST / 17:00 CET - usually in summer

17:00 UTC / 9am PST/ noon EST / 18:00 CET  - usually in winter

Status reports:

• SMO:
  • ref definition using ONAP tools for packages
  • YANG test infrastructure deployed in BedminsterLab
• Non-RT-RIC: 
  • A1 enrichment info
  • extending A1-sim
    • tests
  • R1 app catalog - inti version
• SIM:
  • see YANG part of SMO
  • TOC: copyright issue - are we allowed deploy yang models.
• OAM:
  • see YANG part of SMO 
  • review of O-DU O1 implementation

Martin – 1 point: Based on the recent guidelines from LFN, we should enable password/passcode, and also waiting room for zoom meetings. Let’s discuss this also in the call today.

• update the wiki - check ONAP/O-RAN-SC/SMO Meetings → done
• Move the SDN-R meeting pages under https://wiki.onap.org/pages/viewpage.action?pageId=24641575 to another new parent page. Retain only the ONAP/O-RAN SC/SMO meetings pages. → done
• After doing (1), move https://wiki.onap.org/pages/viewpage.action?pageId=24641575 and its child pages under the main page https://wiki.onap.org/pages/viewpage.action?pageId=92997582. → done

Use Cases

• for SON PCI use case
  • using VES 7.2 - reference will be in O-RAN specs.
  • using 3GPP NRM - see https://forge.3gpp.org/rep/sa5/MnS/
• A1-Adopter - alignment with John required
• Network Slicing

POD (Policy-Management-Service) restart required for Guilin

• investigations ongoing
• solution is review ONAP OOM - https://gerrit.onap.org/r/c/oom/+/114366

Questions and Answers

• Non-RT-RIC realted - wiki are on the way to be updated
• for O-RAN-SC using DMaaP
  • please see
    • O-RAN-SC OAM:  https://wiki.o-ran-sc.org/display/OAM/Deployment and
    • O-RAN-SC INT: https://wiki.o-ran-sc.org/display/GS/SMO+Installation

END

Backup

Closer collaboration related to use cases

Please follow:

• Requirements and Software Architecture Committee

Application Package Structure

• TOSCA 

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

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