Skip to end of metadata
Go to start of metadata

Date

 | 9am PST |  noon EST | 17:00 UTC | 18:00 CET | 21:30 IST |

Zoom: https://zoom.us/j/436210993

Attendees


Informed

Discussion items

TimeItemWhoNotes
00:00Admin

Next meetings: 

2020-11-25: Martin Skorupski

2020-12-02John Keeney

2020-12-09: Martin Skorupski

2020-12-16: ???

2020-12-23: canceled 

2020-12-30: canceled

2021-01-06: Martin Skorupski

00:05O-RAN-SCO-RAN-SC PTLs

Status reports:

00:23Use Case


AI: use case on O-RAN-SC towards ONAP

00:30Closed loopJohn Keeney

Use Case 

    • O-RAN-FH node (VES triggers O1 change)
      • VES-fault-event
      • you see it on DMaaP
      • fault to DMaaP
      • rApp (µService, app, ....??? ) via OAM config change (see POSTMAN scripts)

        • Next steps
          • define the message flow and involved projects/components
          • O-DU interface goes down - O-RU detects interface to O-DU is down and sends VES 
          • SMO should send message to O-DU to bring the interface back
    • 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
00:50

Questions and Answers

  • wiki for yang-validation in OSC LAB - instructions Alex Stancu- provide link 

END


Backup






@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!!! (wink)

Zu Qiang (Ericsson) presenting ONAP on-boarding package


--

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




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

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 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:


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


Action items