Versions Compared

Key

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

Time & Location:

Info
titleNew Meeting Slot

We have now moved to new meeting slot Wednesdays at 16:00 UTC in Summer (DST), 17:00 UTC in Winter !


Please note our new Zoom Bridge

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

Meeting ID: 890 6970 8424



NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate. See the Calendar: (https://lists.o-ran-sc.org/g/main/calendar

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)

  • Meeting ID: 890 6970 8424
  • 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:


Table of Contents
minLevel2

Recording

Notes:

Housekeeping

OSC Project roundup

NONRTRIC (John Keeney)

  • Focusing on ONAP Guilin Maintenance Release for NONRTRIC functions and OSC Cherry Maintenance Release for A1 Policy functions: Both this week
  • Working hard on back end for Control Panel
  • Preparing slides about D Release for RSAC discussion at O-RAN F2F meeting
  • Also need to continue discussions at RSAC meeings about proposed O-RU FH recovery use case: Requirements and Software Architecture Committee Home

SMO (Mahesh Jethanandani )

SIM (Alex Stancu)

  • Nothing to report

OAM (Martin Skorupski)

ONAP - OSC

A1 Enrichment Information Coordinator in ONAP? Pawel Slowikowski John Keeney

  • Pawel Slowikowski Will enrichment Information Coordinator function be upstreamed from OSC to ONAP?
    • John Keeney Not sure. Probably not. Not seeing any requirement for it in ONAP, or beyond the need to re-use the function as available in OSC. It has not OSC-specific requirements so there is no reason that it cannot be used in other environments. 
    • Martin Skorupski Perhaps there is a need in ONAP? Pawel Slowikowski Not sure
    • Pawel Slowikowski If one needs a commercial NONRTRIC based on ONAP, unclear how to coordinate improvements etc. John Keeney No current plan for a Non-RT-RIC in ONAP. This would need to come through requirements sub-committee etc.  Currently Non-RT-RIC function is homed in OSC.  No requirement for a commercial deployment seen yet - but there may be a need for any commercial deployer to consider licensing & IPR considerations.

ONAP Topology Service/Model Andy Mayer

ONAP CSIT Functions

LFN vDTF Event - Session on ONAP/OSC/ORAN Alignment John Keeney Swaminathan Seetharaman Martin Skorupski

Other

  • Gajalakshmi Senthil : Re A1 Policy Management Service support - getting it up & running & checking status. Ref recent email exchange.