2023-03-15 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting
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
Please checkout the calendars:
Important Note about Daylight Savings Time
Important: Daylight Savings Time: Times will change for some people in coming weeks
2023-03-08: 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)
Same as now
2023-03-15: 9am PDT | 12pm EDT | 16:00 UTC | 16:00 GMT | 17:00 CET | 18:00 EET | 21:30 IST | 00:00 CST (Thurs) | 01:00 JST (Thurs)
Meeting will be an hour earlier for some Asian attendees - and stay like this for ~6 months
Meeting time will be an hour earlier for European attendees - but will change back to 'normal' time soon
Daylight savings change in US - Meeting time will not change for US attendees
2023-03-22: 9am PDT | 12pm EDT | 16:00 UTC | 16:00 GMT | 17:00 CET | 18:00 EET | 21:30 IST | 00:00 CST (Thurs) | 01:00 JST (Thurs)
Meeting time remains an hour earlier for European attendees - but will change back to 'normal' time soon
2023-03-29: 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)
Daylight savings change in Europe - Meeting time returns to normal for European attendees
Please checkout the calendars:
Anti-Trust Notice
Date
Mar 15, 2023
Attendees
@John Keeney (Ericsson EST) (Ericsson EST & OSC NONRTRIC)
@Alex Stancu (Highstreet & OSC SIM)
@James Li (CMTI & OSC INT)
@N.K. Shankaranarayanan (ONAP)
@Seshu Kumar Mudiganti (Windriver & ONAP)
@Kevin Timoney (Ericsson EST)
@Sonia Sangari (Ericsson EST)
@Aravindhan Ayyanathan (Ericsson EST)
@Kamel Idir (Ericsson)
May not have captured a full attendee list for this meeting ... please add/remove yourself
See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)
Co-located with ONAP 2023-03-15 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
Contents
- 1 Time & Location:
- 2 Important Note about Daylight Savings Time
- 3 Anti-Trust Notice
- 4 Date
- 5 Attendees
- 6 See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)
- 7 Contents
- 8 Recording
- 9 Notes:
- 9.1 Housekeeping:
- 9.2 OSC Project roundup:
- 9.2.1 News from OSC TOC call last week
- 9.2.2 NONRTRIC (@John Keeney (Ericsson EST))
- 9.2.3 SIM (@Alex Stancu)
- 9.2.4 OAM (@Martin Skorupski)
- 9.2.5 O-DU (@Hariom Gupta @Vidhu (Deactivated))
- 9.2.6 OSC Integration / INT (@James Li )
- 9.2.7 RSAC/SMO (@David Kinsey [AT&T])
- 9.2.8 AI/ML platform project (@Joseph Thaliath)
- 9.3 ONAP Use cases (@N.K. Shankaranarayanan)
- 9.4 ONAP / OSC / O-RAN Alliance: Cooperation & Alignment
- 9.5 Questions / Comments / AOB:
Recording
Notes:
Housekeeping:
Unfortunately @Martin Skorupski cannot join us today. Get well soon.

Calendar:
This Week: 15/03/2023 9am PDT | 12pm EDT | 16:00 UTC | 16:00 GMT | 17:00 CET | 18:00 EET | 21:30 IST | 00:00 CST (+1d) | 01:00 JST (+1d)
Next Week: 22/03/2023 9am PDT | 12pm EDT | 16:00 UTC | 16:00 GMT | 17:00 CET | 18:00 EET | 21:30 IST | 00:00 CST (Thurs) | 01:00 JST (Thurs)
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 also OSC AIML Project meeting notes
OSC Project roundup:
News from OSC TOC call last week
https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/#ORANSCTechnicalOversightCommittee(TOC)
Last week's TOC (Thursday):
No major update
This week's TOC (Tomorrow):
NONRTRIC (@John Keeney (Ericsson EST))
Continuing as per last week :
Alot of work in JDK 17 & Springboot 3 updates
Consolidating PM data exposure in new repo for RAN PM functions
(R1) Service Exposure & Management
CAPIF Aligned Service Registry
Secured/Sandbox execution environment
Controlled access & exposure of service to/from rApps
(R1) Data Management & Exposure
File-based PM data → InfluxDB
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
Inference Services in rApps
Added a 'KServe Participant'
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.
SIM (@Alex Stancu)
Fixed an issue - had a hard coded timeout for VES message reception - fixed now. Now a parameter. Simulators deploy in AWS with OAM stack - in a single VM.
PM File generation
@John Keeney (Ericsson EST) @Alex StancuNo update
OAM (@Martin Skorupski)
Get well soon @Martin Skorupski. No update.
O-DU (@Hariom Gupta @Vidhu (Deactivated))
No Update
OSC Integration / INT (@James Li )
Discussions at RSAC & SMO meetings with @Thoralf Czichy @Former user (Deleted) @James Li @Bin Yang driving for O2-related integration across projects.
How to support both K8S & ETSI-aligned O2-DMSs in a multi-cloud environment. Alignment also with SMO Tacker team.
RSAC/SMO (@David Kinsey [AT&T])
Minutes: 2024 RSAC Meetings (14/3)
Taiwan lab status update
Discussion on multiple flavors of O2-DMSs in multi-cloud deployments
Will discuss OSC/ONAP cooperation next week. (See below)
AI/ML platform project (@Joseph Thaliath)
Minutes & Meeting: Meeting notes
Calendar: https://lists.o-ran-sc.org/g/main/calendar
No update this week
ONAP Use cases (@N.K. Shankaranarayanan)
ONAP SON uses case ... & others
More discussion & progress on details on CM-notification VES Message
Good example of cross-project collaboration & alignment. possible feedback to WG10 as CR for an illustrative example.
Links:
ONAP / OSC / O-RAN Alliance: Cooperation & Alignment
Request at recent RSAC calls for update on areas of overlap / common interest in OSC & ONAP. (@Timo Perala, @N.K. Shankaranarayanan)
Meeting last Friday 10th Mar @Seshu Kumar Mudiganti @Timo Perala @N.K. Shankaranarayanan @Martin Skorupski @Alex Stancu @John Keeney (Ericsson EST)
Based on discussion of topics on : https://wiki.onap.org/pages/viewpage.action?pageId=162105284
@N.K. Shankaranarayanan Slides: (Worked on / Discussed during the call)
Questions / Comments / AOB:
None this week - Ran out of time.
Meeting ends