Skip to end of metadata
Go to start of metadata


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




Discussion items


Next meeting: 2020-10-28
Summer time ends in Europe Sunday 24-10-2020

>16:00 UTC / noon EDT / 17:00 CET 


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.


How to structure this meeting to gain efficiency?

> Scope: alignment between the groups

> addressed by pre-prepared agenda

Swami: closer collaboration related to use cases

  • AI Martin: discuss with Rittwik 
  • Guidance on use cases....

Access to Lab OSC 

  • main contact is Felix for O-RAN-SC INT
  • VPN requires a Win10 VPN Client - investigations by Alex Stancuusing other OS were not successful

Martin Skorupski @john Keeney

ONAP Honolulu - hopefully based on ODL ALU
Lasse Kaihlavirta

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

  • investigations ongoing

Topics for week

  • Application Package Structure (Mahesh - Tosca, ...)

From Mahesh Jethanandani to Everyone: 06:59 PM
Sorry, I was on mute. Saw my name flat on App package. Yes, it is TOSCA based.

  • quick round table of O-RAN-SC project

Questions and Answers




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


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:


  • 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

Action items