2023-07-04 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting
Time & Location:
Meeting Detail: Times & Joining Info
Tuesdays at 14:00 UTC in Summer (DST), 15:00 UTC in Winter
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.
NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate.
Summer Daylight Savings time (Q2, Q3) eventually stabilizes to:
7am PDT | 10pm EDT | 14:00 UTC | 15:00 BST | 16:00 CEST | 17:00 EEST | 19:30 IST | 22:00 CST | 23:00 JSTWinter (non-DST) time (Q4, Q1) eventually stabilizes to:
7am PST | 10am EST | 15:00 UTC | 16:00 GMT | 17:00 CET | 18:00 EET | 20:30 IST | 23:00 CST (Thurs) | 00:00 JST (Thurs)(During Winter→Summer DST changeover follow US time. Summer→Winter DST changeover follow Europe time)
Please checkout the calendars:
Anti-Trust Notice
Date
Jul 4, 2023
Attendees
@John Keeney (Ericsson EST) (Ericsson EST & OSC NONRTRIC)
@Martin Skorupski (Highstreet & OSC OAM)
@Alex Stancu (Highstreet & OSC SIM)
@Sonia Sangari (Ericsson EST)
@Kevin Timoney (Ericsson EST)
@Aravindhan Ayyanathan(Ericsson EST)
@VaradarajanVaradarajan Srinivasan (Samsung)
Reduced attendance today - Public Holiday in US.
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-07-04 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
Contents
- 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 OSC Project roundup:
- 8.2.1 News from OSC TOC call last week
- 8.2.2 NONRTRIC (@John Keeney (Ericsson EST))
- 8.2.3 SIM (@Alex Stancu)
- 8.2.4 OAM (@Martin Skorupski)
- 8.2.5 O-DU @Vidhu (Deactivated))
- 8.2.6 OSC Integration / INT (@James Li )
- 8.2.7 SMO (@Seshu Kumar Mudiganti )
- 8.2.8 RSAC (@David Kinsey [AT&T] @Rittwik Jana )
- 8.2.9 AI/ML platform project (@Joseph Thaliath)
- 8.3 ONAP/OSC Usecases (@N.K. Shankaranarayanan)
- 8.4 ONAP/OSC Alignment Usecase proposal for ONAP Montreal (@N.K. Shankaranarayanan)
- 8.5 Questions / Comments / AOB:
Recording
Notes:
Housekeeping:
Meeting 04 July 2023 (Today) - Small attendance expected - Public Holiday in US.
Meeting 27 June 2023 cancelled (Key attendees unavailable)
Meeting 20 June 2023 cancelled (O-RAN F2F OSAKA)
Calendar:
7am PDT | 10pm EDT | 14:00 UTC | 15:00 BST | 16:00 CEST | 17:00 EEST | 19:30 IST | 22:00 CST | 23:00 JST
OSC SMO project calls now move to its own time slot - alternate Thursdays - TBC
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):
Release H approval delayed by one week
This week's TOC (in 2 days):
Release H approval vote expected
NONRTRIC (@John Keeney (Ericsson EST))
Full summary of OSC H release highlights & deliverable at
Release H (OSC NONRTRIC wiki space)
H Release#Non-Real-timeRIC(NONRTRIC) (OSC Releases wiki space)
SIM (@Alex Stancu)
H Release:
Highlight & more detail: H Release#Simulators(SIM)
O-RU Simulator now uses latest (Nov Train, released March) M-Plane yaml spec release
Implements feature for monitoring O-RU connection (as described by WG4) for management plane. And feedback to WG4.
Script for building O-DU simulators to use 3GPP specs (without redistributing spec docs)
No update for E2 sim
OAM (@Martin Skorupski)
Release preparations
Documentation (issue with RTD)
Possible fix example: https://gerrit.o-ran-sc.org/r/c/nonrtric/+/11110/1/docs/requirements-docs.txt
O-DU @Vidhu (Deactivated))
No update this week
OSC Integration / INT (@James Li )
No update this week
SMO (@Seshu Kumar Mudiganti )
No update this week
Meeting notes Meeting notes
RSAC (@David Kinsey [AT&T] @Rittwik Jana )
No update this week
Minutes: 2024 RSAC Meetings
AI/ML platform project (@Joseph Thaliath)
No update this week
Minutes & Meeting: Meeting notes
ONAP/OSC Usecases (@N.K. Shankaranarayanan)
No update this week
ONAP/OSC Alignment Usecase proposal for ONAP Montreal (@N.K. Shankaranarayanan)
No update this week
Questions / Comments / AOB:
@Varadarajan In NONRTRIC, what is the relation to CAPIF?
@John Keeney (Ericsson EST) As part of SME we need a service registry & APIs for service registration & discover. 3GPP already define some functions and APIs for this: CAPIF (ref: Release H - CAPIF)
... So we would like to reuse if possible, pending on-going specification in O-RAN Alliance WG2
Some discussion already in O-RAN WG2 about reusing CAPIF, so O-RAN spec alignment with SA6 CAPIF will continue there.
Please take a look at our CAPIF implementation: Hopefully aligned but not promising compliance with 3GPP spec
https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-sme
https://github.com/o-ran-sc/nonrtric-plt-sme/tree/master/capifcore
nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-plt-capifcore:1.1.0
@Varadarajan(Previously?) Worked in 3GPP SA6 team so would welcome feedback on CAPIF to SA6 delegates
@John Keeney (Ericsson EST) Have already given some feedback internally in Ericsson, but main alignment should happen between O-RAN WG2 & 3GPP SA6.
Rapporteur for O-RAN WG2 R1-SME specification: Vidyadhar Nallabothula (Ericsson)
Meeting ends 27min