Versions Compared

Key

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

...

Time & Location:

Info
titleMeeting 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
Expand
titleJoin by phone
  • 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


2021-10-27:

  • 16:00 UTC, 09:00 PDT, 12:00 EDT, 17:00 BST, 18:00 CEST, 19:00 EEST, 21:30 IST, 00:00 CST (Thurs), 01:00 JST (Thurs)

2021-11-03:

  • 16:00 UTC, 09:00 PDT, 12:00 EDT,  16:00 GMT, 17:00 CET, 18:00 EET, 21:30 IST, 00:00 CST (Thurs), 01:00 JST (Thurs)
    • Note:1 hour earlier in Europe - Just this week

2021-11-10:

  • 17:00 UTC, 09:00 PST, 12:00 EST,  17:00 GMT, 18:00 CET, 19:00 EET, 22:30 IST, 01:00 CST (Thurs), 02:00 JST (Thurs)
    • Note:1 hour later in Asia, revert to normal time in Europe.

2021-11-17:

  • 17:00 UTC, 09:00 PST, 12:00 EST,  17:00 GMT, 18:00 CET, 19:00 EET, 22:30 IST, 01:00 CST (Thurs), 02:00 JST (Thurs)
    • Note:Continues like this until mid March 2022.

Please checkout the calendars:

...

...

  • https://wiki.o-ran-sc.org/display/TOC
    • We all remain somewhat confused about copyright..... will update when we know more
      • Discussions continue about SCCL license, and the CLA agreement for SCCL.
      • Still no update on using & re-distributing 3gpp specs
      Integration project PTL election completed: James from CMCC elected! (smile)

    NONRTRIC (John Keeney)

    • Working mainly on Helm chart updates ... for modular deployment of NONRTRIC functions
      • see also below re OSC/ONAP SMO deployment. PullRequest still under review, & view to merge-in new NONRTRIC charts.
    • Working on end-to-end flow for PM file delivery to Apps (towards O1→R1 PM flow)

    SIM (Alex Stancu)

    • No major update ... continuing as before.

    OAM (Martin Skorupski)

    •   Working with O-DU teams to figure out exactly what is measured for slicing use case & creating a non-3gpp version of Yang CM/PM models

    • Q from Shankar ... IS O1-PM, O1-FM using stndDefined VES mesages working in OSC. Proposal: push in ONAP Jakarta to use StndDefined throughout.

      • Martin Skorupski Uses the same functions as ONAP, so yes. O1 simulator can create some of the events to demonstrate. Aim for StndDefined throughout in F release ... and early demo/usecase for E release.
      • https://gerrit.
      Topology service available!

    OAM (Martin Skorupski)

    • Working on helm charts.
    • Struggling with licensing issues. (See below)

    O-DU (Hariom Gupta Vidhu Shekhar Pandey )

    • Hariom GuptaStill figuring out if 3GPP Yang model can be used / implemented. 

    Topology Models: 

    • Vidhu Shekhar Pandey Working with Radisys team for Cell Config values
    • Martin Skorupski Working with user-30c9d on a non-3gpp-hello-world version of Netconf/Yang model for O-DU
      • Will probably use this for release E use case
    • Vidhu Shekhar Pandey Working on VES PM messages too
      • Which VES Domain to use? Will probably use VES Measurement domain.
      • Martin Skorupski Also working on a stdDefined version. Would be good to experiment with this sooner than Release F?

    OSC Integration (James Li )

    • James Li (CMCC US) - New OSC Integration PTL!   Very Welcome (big grin)
      • Getting up to speed on current integration environment & integration test cases.
      • Initial vision is to start with a single all-inclusive integration environment, but the need for flexibility is obvious ... looking forward to engaging more with PTLs (smile)
      • Martin Skorupski We are still working on Slicing use case - even models still - hope to finish up these discussion within a week or so. Then we will put a major focus on end-to-end integration environment & test.
    • N.K. Shankaranarayanan The RANSIM work & use cases in ONAP are making good progress - may be useful for James too.
    • No model suits everyone
    • TAPI model is quite abstract / domain independent - basically functions & endpoints ( edge-point, interface, logical termination point, connection points etc)
      • Simulator/Usecases considers CUs, DUs, RUs, & their location
      • Topology model loaded/configured at start time (JSON/XML). Made available using TAPI Netconf model. (Netconf server)
    • @All - Discussion:
      • Cell/Neighbour-Relation? Not explicitly modeled ... but would it be a function, connection, logical grouping, parameter?
        • All valid for different usecases! Everyone has their own topology model for their own use case!
      • TAPI is very abstract, so a good starting point for more specific topology models.
      • Discussion continue in ONAP modelling work.
    • Is ANR (Automated Neighbor Relations) supported in O-RAN?Not O-RAN specific ... feature/usecase that can be implemented in various ways in 4g, 5g, etc ... Centralized, Distributed, Hybrid, in xApp, etc....

    ONAP SMO deployment options

    • Sebastien: Pull Request on OSC it/dep repo for existing SMO Deployment package - will overwrite existing version
    • David Johnson Mini deployment in POWDER lab seems to be working well! Will also look at SMO Deployment here & feedback.
    • Still struggling with Jenkins environment 
    • Updated pull request coming with additional tests added
    • Still working on VES collector flexibility in ONAP OOM (and overlapping work with SDNC's VES configuration): Sebastien: Also working on OOM changed (DCAE/VES Collector config for SDNC)
      https://gerrit.onap.org/r/c/oom/+/125150
    • Sebastien: Also has an issue with O-RU-use case App ... issue with HTTPS .... Python issue?

    Copyright & Licensing

    • SCCL:
      • Recent "Special TOC Call" about licensing, but was not SCCL recorded (sad)
      • SCCL does not address 3GPP license issue - Issue continues as before
        • O-RAN Alliance will try persuade 3GPP to use SCCL ... but progress stalled.
      • SCCL is currently only for O-RAN Alliance material - to be agreed to by anyone using/redistributing these specs
      • OSC is a first mover to put procedures in place
      • SCCL is copyright only - IPR licensing is a seperate issue and not addressed
      • SCCL is not an open-source license
      • We are making some progress understanding SCCL (smile) (but we're not there yet!)
      • Can SCCL specs be redistributed freely?: No.
    • 3GPP:
      • Surely there is potential to request a PoC/Demos/non-Commercial derogation from 3GPP
      • We need to keep pushing.
      • Tracy Van Brakle IIRC 3GPP does allow use for demos/poc/exhibitions ? Will check up on this! This should be enough for our requirements. 

    Simulators

    • N.K. Shankaranarayanan The RANSIM work in ONAP is making good progress!  (Ref Krishna in SON, Slicing & OOF in ONAP)
      • Tracy Van Brakle N.K. Shankaranarayanan Should all these simulators be consolidated?
        • They could be more aligned, but probably should not be "merged" - they have different priorities / simplifications embedded - by design! 
        • But they do have some shared/shareable functions/requirements, so some alignment might be helpful.
        • Tracy Van Brakle Is there something like Mininet for O-RAN/3GPP/RAN? Maybe academic contributors would be best suited to help here (smile)

    Q&A

    • Martin Skorupski James Li making good progress on an SMO deployment - will hopefully form basis for an SMO in integration environment.

    Q&A

    • David McBride Note 1 week slip for ONAP Istanbul Release.Ran out of time (sad)