2023-05-23 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
May 23, 2023
Attendees
@John Keeney (Ericsson EST) (Ericsson EST & OSC NONRTRIC)
@Martin Skorupski (Highstreet & OSC OAM)
@Alex Stancu (Highstreet & OSC OAM)
@N.K. Shankaranarayanan(ONAP)
@Aravindhan Ayyanathan(Ericsson EST)
@Kevin Timoney (Ericsson EST)
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-05-23 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 New time for this call!
- 8.3 OSC Project roundup:
- 8.3.1 News from OSC TOC call 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 O-DU @Vidhu (Deactivated))
- 8.3.6 OSC Integration / INT (@James Li )
- 8.3.7 SMO (@Seshu Kumar Mudiganti )
- 8.3.8 RSAC (@David Kinsey [AT&T] @Rittwik Jana )
- 8.3.9 AI/ML platform project (@Joseph Thaliath)
- 8.4 ONAP/OSC Usecases(@N.K. Shankaranarayanan)
- 8.5 ONAP/OSC Alignment Usecase proposal for ONAP Montreal(@N.K. Shankaranarayanan)
- 8.6 Questions / Comments / AOB:
Recording
Notes:
Housekeeping:
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
@John Keeney (Ericsson EST) Away last week
New time for this call!
Tuesdays at 14:00 UTC.
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 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):
Update from several projects, including SMO & NONRTRIC (See below)
This week's TOC (in 2 days):
New meeting format with updates from relevant PTL etc
week 0: RSAC, Integration I (cross-project testing related), Infrastructure
Week 1 : RIC, RICAPP, AIMLFW
Week 2: NONRTRIC, SMO, OAM, SIM
Week 3: Integration II (lab related), O-DU-HIGH, O-DU-LOW
This week:
SIM, OAM, RICAPP, O-DU-HIGH, O-DU-LOW, DOC
NONRTRIC (@John Keeney (Ericsson EST))
Demo: "LCM of ASD-based CNFs using ONAP CNFM function in Standalone mode" @Aravindhan Ayyanathan
At last weeks RSAC committee Meeting (17 May 2023)
Demonstrate ASD-based LCM for CNFs using a cut-down version of the CNFM function originally from the ONAP SO project. The function can be used in standalone mode without the need for the rest of SO, A&AI or SDC.
Video: Hi-Res
Video Lo-Res
Slides:
Demo: "CAPIF for Service Registration & Service Discovery" @Yennifer Chacon
At last weeks RSAC committee Meeting (17 May 2023)
Demonstrate Demo/Discussion of CAPIF-based Service registry/discovery. The 3GPP CAPIF approach seems to be gaining traction as a basis for R1-SME, and we would like to show the progress we have made with our implementation.
Video: Hi-Res
Video Lo-Res
Slides:
TOC Update:
Slides:
Working on improving documentation - especially for RAN PM functions:
Making some initial progress on consolidated rApp manager ... but just starting still
Experimenting with using Avro for PM data serialization ...
Will try to expedite release processes for ONAP & OSC due to teams vacation & availability plans
Previous weeks:
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)
Preparing for TOC update tomorrow
Still looking at PM file passing:
Some additional useful info: https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-ranpm/en/latest/
OAM (@Martin Skorupski)
Preparing for update to TOC tomorrow.
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 )
Minutes: 2024 RSAC Meetings (17 May)
See Demos in NONRTRIC above
This week:
AI/ML platform project (@Joseph Thaliath)
Minutes & Meeting: Meeting notes
ONAP/OSC Usecases(@N.K. Shankaranarayanan)
SON Usecase
Moving towards release prepartation
NETSIM in ONAP needs some update (Honeycomb not available?
ONAP/OSC Alignment Usecase proposal for ONAP Montreal(@N.K. Shankaranarayanan)
As discussed last week here.
Discussed at ONAP TSC call last week: https://wiki.onap.org/display/Meetings/TSC+2023-05-18
Lots of interest in ONAP TSC
Emails to OSC TOC/RSAC chairs. Lots of interest
"ONAP/OSC SMO Automation use case." (Umbrella of use cases )
Use cases will need an rApp
Could align with ONAP ACM team to show 'hello-world' type rApps/compositions to show the end-to-end nature.
rApps would have very limited intelligence or functionality - little more than stubs.
The word "Use-case" is very overloaded
In OSC we are aiming more for an "Integration Demonstrator" (use-case may not be the best word)
In ONAP 'use-case' is good (Integration has different connotations in ONAP)
Questions / Comments / AOB:
Nothing additional this week.
Meeting ends 30min