2024-07-09 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting

2024-07-09 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting

Time & Location:

  • Time Change: This meeting is now 1 hour later - 15:00 UTC on Tuesdays

 

Meeting Detail: Times & Joining Info

Today: Tuesday at 15:00 UTC     (15:00 UTC in Winter Northern Hemisphere TBC)

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

  • Ensure you are signed into your Zoom account to join.

  • Meeting ID: 890 6970 8424. By Phone: Dial in (Local numbers): You will need a Participant ID so you will need to join the meeting from a Zoom client first to get this.

  • 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 (norther hemisphere) (Q2 & Q3) time eventually stabilizes to:
      8am PDT | 11am EDT | 15:00 UTC | 16:00 BST | 17:00 CEST | 18:00 EEST | 20:30 IST | 23:00 CST | +1d 00:00 JST (Wed)

    • Winter (non-DST) (Q1 & Q4): TBC: Probably 8am PST | 11pm EST | 16:00 UTC | 16:00 GMT | 17:00 CET | 18:00 EET | 21:30 IST | +1d 00:00 CST (Wed) | +1d 01:00 JST (Wed)

Please checkout the calendars:

Anti-Trust Notice

Date

Jul 9, 2024

Attendees

  • @John Keeney (Ericsson EST)(Ericsson EST & OSC NONRTRIC)

  • @Martin Skorupski (Highstreet & OSC OAM)

  • @Alex Stancu (Highstreet & OSC SIM)

  • @subhash (Samsung & OSC AIMLFW)

  • @Aravindhan Ayyanathan (Ericsson EST)

  • @RAVITEJA KARUMURI (EST) (Ericsson EST)

  • @Denis G Noonan (Ericsson Software Technology) (Ericsson EST)

  • @Francesco Davide Lapenta (Ericsson EST)

  • @KyeHwan Lee (NIST) (NIST)

  • @guru raja  (Tech Mahindra)

  • Srinivanas Yanamadala (Tech Mahindra)

  • @Varadarajan (Samsung)

  • @naman.gupta (Samsung)

  • @Deena Mukundan (Tech Mahindra)

  • May not have captured a full correct attendee list for this meeting  ... please add/remove yourself

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

Contents

Recording

Notes:

Housekeeping:

OSC Project roundup:

News from OSC TOC & OSFG calls last week

  • OSFG:

    • No major update

NONRTRIC (@John Keeney (Ericsson EST))

  • OSC NONRTRIC: Release J - done

  • Release K Planning:

    • No major update this week ... but will continue with: 

      • More focus on demonstrators - esp aiming towards next F2F

      • A1-Controller work in ONAP will continue.

      • Integration

        • @subhash 

          • Would like to cooperate on SME & rApp usecase & AIML framework

            • Definitely - would be good for demo at F2F too.

            • Lets start a page to capture this ... may move to RSAC later.

SIM (@Alex Stancu)

  • Release J done

  • Release K

    • Working on Python O1 & OFH M-Plane simulators

      • Still on track & ongoing

OAM (@Martin Skorupski)

  • Release K

    • O-DU team would like to support std-defined alarms - but not showing up in SDN-R - so updates needed for SDN-R/ODLUX (to get events from kafka)

      • (newAlarms, clearedAlarms)

    • Work topics: Ongoing & Discussions - As before:

      • WG11 Security updates

      • OAM model updates from WG10

      • Topology?

        • Lots of existing models -

          • 3GPP, IETF network topology, O-RAN (WG10), onf-tapi, tmforum 

        • @John Keeney (Ericsson EST) Lets work together to try get some of the data generated by Simulated Topology Generator into OSC TEIV repository - but we need to work on intermodel-relationship modelling.

OSC Integration / INT (@James Li)

  • No update this week

SMO (@Seshu Kumar Mudiganti)

  • No update this week.

  • Meeting notes Meeting notes

  • Topology & Inventory @John Keeney (Ericsson EST) :

    • No update this week

RSAC (@David Kinsey [AT&T] @Rittwik Jana)

AI/ML platform project (@subhash )

ONAP Update (@N.K. Shankaranarayanan)

  • No update this week

ONAP/OSC Usecases (@N.K. Shankaranarayanan)

  • No update this week.

Questions / Comments / AOB:

  • @subhash Anyone know if/how to implement stuff in CTRs as pre-spec implementations?

    • Please check with CR author - easier if your company is a co-author of CR.

    • After CR is approved, and spec is approved, then the 'O-RAN license' applies.

    • Gets difficult if the accepted spec-version diverges from the implemented pre-spec version

    • Need to be careful about checking copyright & protected IP of CRs, and later when approved. (60 days after approval, IP declarations should be completed)

    • ( ^ Statements above are just our understanding, and may not be correct!. Consult an IPR specialist )

Meeting ends 34 min