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:

OSC SMO Meeting Series: Reminder from previous weeks:

NOTE: DST Changeover in coming weeks!

  • Keep a close eye on the calendars!

OSC Project roundup:

News from OSC TOC call this week

NONRTRIC (John Keeney)

  • Work examining ONAP Control Loops as a basis for rApps in OSC ... looking promising
    • Still have alot of work to do, e.g. packaging & distribution, but working away
  • ONAP A1 Policy Management: Istanbul JIRA tickets to be closed before release date!
  • Short introductory-level presentation at ONES 2021

SIM (Alex Stancu)

  • Addressing in SMO deployment (see below) (Use hostname, not ip:port)

OAM (Martin Skorupski)

  • Working on a basis for an O-RAN topology model
    • Could be reused in O-RU use case.
    • N.K. Shankaranarayanan Does O-RAN Topology include O-RU?
    • Ref discussions on ONAP Topology modelling, including Andy Mayer
    • N.K. Shankaranarayanan Ref discussions in O-RAN WG1 (Cagatay - AT&T)
    • Not including Core Network.
    • Issues:
      • No agreed model, and even if there was it would not suit most peoples' requirements - everyone wants different topology models for their requirments.
      • Very hard to keep any complete topology model populated & synchronized
      • Too many layers to have a complete model ... and layering is not necessary accurate.
      • Must be model-driven.
        • A model that cannot be populated is useless!

O-DU (HariomGupta(HCL))

  • Hariom GuptaStill figuring out if 3GPP Yang model can be used. 
  • JIRAs created for cells & VES measurement events

OPS-5G (David McBride, Doug Evans)

  • See discussions 2 weeks ago
  • Introductions:
    • Andy Leidy, Arnold Alvarado, Douglass Evans (USN), Louis Raspberry, Neil Hoff, Ryan McAllister
  • Note session at ONES summit
    • Martial: Will the recordings/slides be available? (Think recordings appear on youtube in a few weeks)
    • Doug: Spotted interesting presentation re Acumos alignment (ONAP & OSC)
      • Ref work in DCAE-MOD for reusing Acumos models & work in Acumos to package models as xApps.

ONAP SMO deployment options

  • Sebastien: Working on
    • Pull Request on OSC it/dep repo for existing SMO Deployment package
    • Readme
    • Scripts
    • Testing
    • Trying to reduce footprint
    • Testing O-RU/O-DU/Topology-Server deployment
    • VES Collector configuration with SDNC
  • Pull request coming soon (this week?) for wider review & comments.
  • John Keeney & Xue Gao working together on A1 deployment ... perhaps use existing test suite to avoid having to do new tests? 
  • John Keeney We are working on modularizing NONRTRIC helm charts, which may affect work here ... ...
    • Will also look carefully at the current versions in SMO deployment ... Lots of progress already made!
      • Plan to evolve when modular helm charts are available

Q&A

  • Copyright & Licensing

    • SCCL: Any open source project can reuse SCCL artifacts - if they abide by by process for that license
      • Note SCCL is not an opensource license!
      • ONAP may want examine/reuse? the work in OSC for supporting SCCL?
    • Long discussion about 3GPP licensing:
      • Open/Public != OpenSource != Free
      • Try to keep functions model-driven as a much as possible so loosely coupled from copyrighted specs/model, so specs are not reproduced/re-distributed.
        • But this is not possible for the actual function encoding the model (e.g. a netconf server & Yang model) or function simulators/emulators, or POCs
      • We see no clear path forward for this very long running issue.
        • We need to be conservative until we have clear guidance / path forward.
        • Unwilling to risk copyright or IPR infringement
        • Likely a common-sense reuse approach is possible - with no commercial aspect involved - but we cannot assume this.