Versions Compared

Key

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

Date

16  16:00 UTC / noon EDT / 18:00 CEST

Zoomhttps://zoom.us/j/619914482(O-RAN-SChttps://zoom.us/j/436210993)

Attendees


Informed

Discussion items

TimeItemWhoNotes
00:00Admin

Next meeting: 2020-

09-23ONAP/

10-07

Note: Next week are conflicts with OTIC and other events.

00:05
Admin

Mahesh

Postman scripts to interface with the SMO and in turn test O1 interface between the SMO and different parts of O-RAN

-SC

Agreement on the zoom link:

In future we will use: https://zoom.us/j/436210993

AI Martin update calendars and pages accordingly

00:10@Mahesh Jethanandani

Introduction to the O-RAN-SC Project:

  • compare VNF and CNF packages between ONAP and ESTI
  • O1 test tooling 
    • Idea: dynamic creation of a NetConf server by uploading yang modules.
00:1000:0000@all

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



00:30

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:


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



Questions and Answers


Action items

  •