• Antitrust Policy Notice

• Antitrust Policy

Jan 11, 2023

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

• @Martin Skorupski (Highstreet & OSC OAM)

• @Alex Stancu  (Highstreet & OSC SIM)

• @James Li (China Mobile & OSC INT)

• @N.K. Shankaranarayanan (ONAP TSC)

• Pawel Pawlak (F5 & ONAP TSC chair)

• @Magnus Buhrgard (Ericsson & ONAP TSC)

• @Ranny Haiby (LF)

• Bob Heinemann (MITRE)

• @Halil Cakal (Ericsson EST)

• @Aravindhan Ayyanathan (Ericsson EST)

• @Kevin Timoney (Ericsson EST)

• @Sonia Sangari (Ericsson EST)

• @Carsten Höseler(TU-Dortmund)

• @Former user (Deleted) (Fujitsu)

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

• Co-located with ONAP 2023-01-11 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)

• Recording (MP4 - lo res)

• Happy new year!

• Calendar:

  • https://lists.o-ran-sc.org/g/main/calendar

  • https://lists.onap.org/g/onap-meetings/calendar

  • 09:00 PST | 12:00 EST | 17:00 UTC | 17:00 GMT | 18:00 CET | 22:30 IST | 01:00 (+1d) CST

• OSC SMO project calls now move to its own time slot - alternate Thursdays

  • See OSC RSAC Calendar: https://lf-o-ran-sc.atlassian.net/wiki/display/RSAC/calendars

  • See also OSC Meetings calendar: https://lists.o-ran-sc.org/g/main/calendar

  • (Note this meeting to open to anyone, including non-ORAN members)

  • We will maintain this slot for ONAP Alignment, and try flag issues/question to/from SMO meetings.

  • See OSC SMO Project meeting notes

• See also OSC AIML Project meeting notes

• https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/#ORANSCTechnicalOversightCommittee(TOC)

  • Last week's TOC (Thursday):

    • Cancelled

    • No update.

  • This week's TOC (Tomorrow):

    • No update.

• Release G completed before Christmas/New Year break.

  • OSC NONRTRIC Release G

• Release H Planning continues:

  • (R1) Service Exposure & Management

    • CAPIF Aligned Service Registry

    • Secured/Sandbox execution environment

    • Controlled access & exposure of service to/from rApps

  • (R1) Data Management & Exposure

    • Previous focus on PM data - but will extend to other use cases too

    • Aim to work with AIML project for Training (and Inference ?) data access

  • rApp Management

    • Built on ONAP “Automation Composition” model & platform to implement rApp use cases

      • rApp-specific extensions needed

    • Packaging, Onboarding & Orchestration of rApps

      • rApp-specific packaging & Onboarding

        • Aim to align with / inform ongoing work in O-RAN (& OSC) about Common App packaging & Onboarding.

      • (rApps with & without µService)

    • Overlap with Service Exposure work to examine role of an rApp Manager to support controlled exposure & LCM of µService and non-µService parts of an rApp

  • Continued A1-Policy & A1-Enrichment-Information evolution (& R1-A1)

    • A1 Spec evolution

    • A1-Policy work in ONAP (continues in ONAP London) - candidate for R1-A1(P)

    • A1-EI management as part of DME - candidate for how to include A1-EI in R1-DME

  • Sample use cases (rApps)

    • Requirements Drivers for rApp/R1 development

    • High degree of cross-project integration activity

  • Testing, Maintenance & Housekeeping

    • Function Test & Integration Test environment,

    • Support integration, deployment & configuration of SMO/Non-RT-RIC related functions & usecases in OSC Integration env.

    • Project coordination, Documentation, Delivery, Reporting, Cross-project alignment, Community demos, O-RAN Standardization support, etc.

• Still working on OSC H Release Planning

• Looking at OAM Specs from O-RAN Alliance & 3GPP REL 18

  • e.g. Updating VES stddefined support etc, new versions of SDNR etc. 

• No Update

• Plan to use XTesting integration tests with INF project (esp for O2)

• Ref: 2024 RSAC Meetings

• Update from AIML project re Release H plans

  • Included discussion on overlap/alignment/integration opportunities with NONRTRIC, SMO, Near-RT-RIC, RICAPPs, OAM projects.

• Update from O-DU HIgh project re Release H plans

• Update from SMO Tacker project re Release H plans

• OSC/ONAP 

  • Mentioned this meeting - Unfortunately @David Kinsey [AT&T] cannot attend today - meeting clash.

• Upcoming Open RAN workshop

  • (... will add a link when i find it: https://www.knaintl.com.tw/2023OpenRan/ ??)

• Minutes & Meeting: Meeting notes

• Calendar: https://lists.o-ran-sc.org/g/main/calendar

• No update this week

  • See discussion at RSAC this week.

  • Also some good discussions at this week AIMLFW Project meeting

• No time for an update this week

Discussion: ONAP TSC Would like to better formalize relations between ONAP & O-RAN SC, and ONAP & O-RAN Alliance

• @00:13:00 in Recording

• Pawel, @Magnus Buhrgard, Bob, @N.K. Shankaranarayanan 

• Also trying to establish a snapshot of interactions currently

• How to improve cooperation

• Goal: Avoid fragmentation, improve synergy, avoid duplication, raise awareness

• (Unfortunately .. (or fortunately) ONAP TSC & OSC TOC calls are at the same time)

• Areas being considered in ONAP: Is there a need to streamline requirements gathering process & cadence, release processes & cadence, integrated platforms vs services, using licensed specs

  • Same considerations could be looked at in OSC too - to have a 2-way flow of awareness, requirements, software,

  • For example, there can be a very significant lag between a requirement becoming obvious in one project, and released software being available in the other ... often Many months.

    • Rule of thumb: A project should only use 'released' software from other communities

    • It would be better to have a much more flexible, continuous, faster cadence of requirements planning & interim or continuous software releases. (while also keeping the periodic Major Release time scales)

• Would be good to have better cooperation between specification work & implementation (pre-spec & post-spec)

  • Note: Any project - not just OSC - including ONAP - can consume/feedback to O-RAN Alliance on a equal basis

    • Would be good to better understand if/what 'special relationship' between OSC & O-RAN Alliance. No blocker exists to other projects.

  • O-RAN Licensing remains an issue for all opensource projects - including ONAP & OSC

• Some topics where there is a clear interaction ONAP/OSC - and alignment would be beneficial:

  • release cadence

  • non-rt-ric / smo

  • rapps

  • oam

  • orchestration and cloud

  • simulator (O-CU, O-DU, O-RU)

  • use cases alignment 

  • integration

  • license issues

• Potential actions

  • Invite attendees from ONAP REQ and O-RAN-SC RSAC to join the other - Even if just a once off initially

    • Just a "hello" to start?  

    • Links:

      • OSC Requirements & Software Architecture Committee: https://lf-o-ran-sc.atlassian.net/wiki/display/RSAC/ 

      • ONAP Requirements Subcommittee: https://wiki.onap.org/display/DW/Requirements+subcommittee 

  • Invite attendees from ONAP TSC and O-RAN-SC TOC to join the other - Even if just a once off initially

    • Just a "hello" to start ?

    • Links:

      • ONAP TSC: https://wiki.onap.org/pages/viewpage.action?pageId=4719160 & https://www.onap.org/about/tsc

      • O-RAN SC TOC: https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/ 

  • Further discussion in ONAP TSC about ways forward.

  • Explanation of the difference between O-RAN Alliance and O-RAN SC

    • Clarify if there is a 'special relationship'

• Follow up Note on opensource/specification alignment: :

  • @Magnus Buhrgard, @Martin Skorupski, @John Keeney (Ericsson EST)  

    • Would be good to have a separate discussion about how opensource and specification activities could benefit each other better if there was better interactions.

    • O-RAN Alliance seems like a particularly good candidate to examine this

    • Lets discuss this further in another call.

• No more time this week

Meeting ends