Time & Location:

Meeting Detail: Times & Joining Info

Wednesdays at 16:00 UTC in Summer (DST), 17:00 UTC in Winter !

Zoom Bridge :  https://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09

  • Ensure you are signed into your Zoom account to join.
  • Meeting ID: 890 6970 8424.
  • See the Calendar: (https://lists.o-ran-sc.org/g/main/calendar)
  • NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate. 
    • Summer Daylight Savings time eventually stabilizes to: 9am PDT | 12pm EDT | 16:00 UTC | 17:00 BST | 18:00 CEST | 19:00 EEST | 21:30 IST | 00:00 CST (Thurs) | 01:00 JST (Thurs)
    • Winter (non-DST) time eventually stabilizes to: 9am PST | 12pm EST | 17:00 UTC | 17:00 GMT | 18:00 CET | 19:00 EET | 22:30 IST | 01:00 CST (Thurs) | 02:00 JST (Thurs)
    • (During Winter→Summer DST changeover follow US time. Summer→Winter DST changeover follow Europe time
  • Meeting ID: 890 6970 8424
  • You will need a Participant ID so you will need to join the meeting from a Zoom client first to get this.
  • Dial in: (Local numbers)
    • +1 646 558 8656 US (New York)
    • +49 30 5679 5800 Germany
    • +49 69 3807 9883 Germany
    • +353 1 240 8941 Ireland
    • +46 8 4468 2488 Sweden
    • +46 8 5016 3827 Sweden
    • +358 3 4109 2129 Finland
    • +358 9 7252 2471 Finland

Date

Attendees

See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)

Contents:


Recording

Notes:

Housekeeping:

  • Reminder from previous weeks:
  • O-RAN has declared that recording are kept for 2 weeks only. Does this apply to us? 
    • Is this a requirement, a privacy issue or a cost issue?
    • Not sure - the recording storage quota that we use is currently full - so we may need to delete old cloud recording?
    • All past recording are also available as files uploaded to the wiki pages - May be a  storage issue later, but no plans to delete as yet.

OSC Project roundup:

NONRTRIC (John Keeney)

  • Continuing work as reported in past weeks - working toward OSC D code freeze
    • We are testing a first version of a script for the O-RU recovery use case - Script version and ONAP-Policy version
    • Finishing touches to Control Panel upgrade activities
  • Integration tasks will likely run over into the Integration sprints. - e.g. deployment scripts, tests, etc.

SIM (Alex Stancu)

OAM (Martin Skorupski)

LFN ONAP Honolulu Webinar

Topology Modelling

  • Andy Mayer - Confident work on topology modelling will be a big help for slicing. Can including slicing concepts in Topolgy model
  • https://wiki.onap.org/display/DW/Abstract+Topology+Model
  • Karthik (?) working with Andy Mayer around TAPI topology model
  • Alex Stancu working on a service to expose TAPI models for topology modelling - Research activity - can hopefully make available in opensource & maybe input for O1?
    • Andy Mayer MEF are already looking at this - based on TAPI (part of Presto API) - especially for Ethernet etc - could be extended into a general topology model? Could/Should coordinate ONAP/O-RAN & MEF?
    • Alex Stancu Wondering if anyone knows if TAPI will move to Yang 1.1 (currently 1.0)? - Should ask Karthik? - Could ask at ONF/TAPI call on Tuesday or ONAP modelling call on Friday?
  • Discussion about implementing a Topology Service:
    • Is it an O1 and A1 activity? : John Keeney O1 is most useful for RAN topology
    • John Keeney Most important to have a solid model first before implementing. Service that the SMO should provide.
    • Also need to consider core, transport topology too - so not just O-RAN.
  • Andy Mayer Needs to be use case driven
    • Proposed model sketch: https://wiki.onap.org/display/DW/Proposed+Topology+IM+Sketch - but needs to be used/populated to verify.
    • NK Shankar: Is TAPI the best place to start? Maybe should start with something simple - e.g for the SON use case - cells, neighbors, etc is very different from actual connections (logical vs physical views)
      • Likely need simplified logical views .
      • Andy Mayer Best to sketch out some use cases - will verify model & drive requirements.
      • John Keeney Probably need a well-thought out base/canonical model to act a base for other logical view.
        • Source of truth is config data (O1) and Inventory.
      • NK Shankar - This is very hard to achieve - simpler logical views is easier to achieve & work with John Keeney Needs to be grounded in reality though
      • John Keeney For example for NON-RT-RIC use cases we need live topology information about UEs - which makes the topology service very difficult!
      • NK Shankar - lots of layers/views - probably can't implement the whole thing from scratch - need to make simplifications.
  • Needs further discussion at ONAP Modelling subcommittee meeting https://wiki.onap.org/display/DW/Modeling+sub-committee+meetings

O-RAN F2F - 01-14 June 2021

  • No update

ONAP Q/A

  • Vidhu Shekhar Pandey - Needs access to O-RAN SC lab lab to try O-DU for integration tests to test/demo O-DU. O-DU runs in a VM directly - not a Docker image so a but difficult to do without lab access.

Follow up note:

  • Swaminathan Seetharaman - who had to leave the meeting midway -  informed us all recently that he is changing roles
    • We are sorry to see him go. Thanks for helping alot with this meeting series over the past few months. (smile)