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)

SIM (Alex Stancu)

  • Simulators are stable & ready to run.

OAM (Martin Skorupski)

  • Working on deployment & integration
  • Considering a DNS - especially for IPv6 address (E release maybe, if needed)
  • Working on docker-compose for integrated deployment of SMO/OAM/SIM/NONRTRIC functions
    • Topology Service:
      • Collaborative work with ONAP Modelling/O-RAN Alliance modelling

O-DU (HariomGupta(HCL))

ONAP SMO deployment options (Christophe Closset (AT&T) & Amar Kapadia (AARNA))

  • Proposal for an ONAP deployment specific for an ORAN SMO
    • Provide tuned override files in OOM for a standalone ONAP SMO
      • Can provide multiple flavours .. e.g. small/medium etc
    • Current OOM override files are quite out of date & may not be robust.
  • John Keeney Any chance of deploying non-ONAP functions? e.g. NONRTRIC functions in OSC
    • Christophe: Plan to start small with OOM initially (so no ?)
      • Could perhaps deploy non-ONAP functions (e.g. NONRTRIC, simulators etc) as CNFs ?
      • Not sure CNF is appropriate for SMO/NONRTRIC platform functions - Possibly a good idea for simulators etc that are CNFs/xNFs in the RAN
      • O2 (WG) is partly relevant for CNFs (and maybe for apps) - but not for SMO internals
  • Please discuss more before officially proposing this PoC in ONAP
  • Ref: https://jira.onap.org/browse/REQ-887
  • Recording