2025-03-25 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting

No meeting. Only a few attendees - so just an informal chat for a few minutes.

Note: Meeting has now moved to our new "Summer" time: 15:00 UTC. Please check the calendar:

Time & Location:

Meeting Detail: Times & Joining Info

Today: Tuesday at 15:00 UTC

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 (northern hemisphere) (Q2 & Q3): 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 (northern hemisphere) (non-DST) (Q1 & Q4): 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

Mar 25, 2025

Attendees

@Alex Stancu
@Martin Skorupski
@John Keeney (Ericsson EST)
@subhash
@fransiscus bimo
@Sunil N
Julien Boudani
... others. Please add yourself
May not have captured a full correct attendee list for this meeting ... please add/remove yourself

1 Time & Location:
2 Anti-Trust Notice
3 Date
4 Attendees
5 See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)
6 Contents
7 Recording
8 Notes:
- 8.1 Housekeeping:
- 8.2 Discussion on scope / time
- 8.3 OSC Project roundup:
  - 8.3.1 News from OSC TOC & OSFG & RSAC calls last week
  - 8.3.2 NONRTRIC (@John Keeney (Ericsson EST))
  - 8.3.3 SIM (@Alex Stancu)
  - 8.3.4 OAM (@Martin Skorupski)
  - 8.3.5 AI/ML platform project (@subhash)
  - 8.3.6 SMO (@Seshu Kumar Mudiganti)
  - 8.3.7 OSC Integration / INT (@fransiscus bimo )

Recording

Notes:

Housekeeping:

Next Meetings:
- Need to find a way to improve attendance - either change the time, or format ... see below
Calendar:
- https://lists.o-ran-sc.org/g/main/calendar
- https://lists.onap.org/g/onap-meetings/calendar
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

Discussion on scope / time

To improve attendance / relevance ...
@subhash - Could try to add more technical discussion
- Need to focus more on agenda & inviting appropriate people for specific topics
- Would be better to have prepared topics & make sure people are aware & invited.
  - e.g. demos announced in advance
Julien Boudani (Orange) - Mainly here to get context & Info
- ... but there are alot of meetings, Consolidation is better if possible
- ... need to capture discussion & be able to look back at notes
@John Keeney (Ericsson EST) Would it possible to show Jira boards / backlog
- Should add links to boards / epics for each project.

OSC Project roundup:

News from OSC TOC & OSFG & RSAC calls last week

TOC:
- https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/#ORANSCTechnicalOversightCommittee(TOC)
- Last week's TOC (Thursday):
- This week's TOC (Thursday):
  - Workshop in coming months?

OSFG: (@Martin Skorupski)
- No update or significant progress this week

RSAC (@Martin Skorupski )
- Minutes: RSAC Meeting notes
- Moving slots for the RSAC meetings occuring during night Europe-time. Suggestion to move to early Europe time - still possible for Asian attendees (late), but no possible for most US.
- No nomination yet for 2nd RSAC CoChair (with @Martin Skorupski) now that @Rittwik Jana is stepping down

NONRTRIC (@John Keeney (Ericsson EST))

Walked through Jira links for NONRTRIC / ONAP A1 in L-Release
- ONAP A1 - Epic CCSDK-4071: A1 Adapter and A1 Policy Management Enhancement in Paris Release – CCSDKOpen
- OSC NONRTRIC -Backlog: Non Realtime RAN Intelligent Controller | Backlog
- OSC SMO - TEIV SMO-174: Topology & Inventory Exposure SMOS - Release LIn Progress

SIM (@Alex Stancu)

No Update this week: See previous weeks

OAM (@Martin Skorupski)

Updating to latest specs from O-RAN
Updating Release L wiki page
Jira
- https://lf-o-ran-sc.atlassian.net/browse/OAM-429
- L-Release

AI/ML platform project (@subhash)

SMO (@Seshu Kumar Mudiganti)

Meeting notes Meeting notes
No specific update
Topology & Inventory: (@John Keeney (Ericsson EST) :
- Lots of small updates in K-Release & ongoing. Focus on ingestion adapters in this release.

OSC Integration / INT (@fransiscus bimo )

Minutes: https://lf-o-ran-sc.atlassian.net/wiki/display/IAT/Current+Meetings
Last week:
- Looking at contributing about Intent Management
  - Requires a capability store to describe rApp capailities
    - Service/API Registry from SME in NonRTRIC?
      - @John Keeney (Ericsson EST) - Really only for APIs - doesn't really describe capabilities in a way usefull for Intent Management
        e.g. "SupportedFeatures" SME/Capif response - but that field is specific for a single exposure. Bit mask field - so likely is not a plain test string that could be reused.
        e.g. in TEIV - again unlikely to be useful, since TEIV data model is specifically targeting topology (with yang extension)
        e.g. in rApp Manager - but this is only for rApps then - cannot capture capabilites for other services, e.g. SMOSs
        So might need a dedicated capability store? (Some advantages to using a semantic/RDF store ...? Or maybe CPS if yang based data? ) - depends on type/format of data

Meeting ends 56min