Page Comparison

Date

Info

title	Date

Date: 08 Jan 2025

Time: 4am PST | 7am EST | noon UTC | 13:00 CET

Join Zoom Meeting

Please subscribe to: https://lists.o-ran-sc.org/calendar (only there is the truth)

Goals

Define requirements for O-RAN-SC
Define use cased for L-Release

Recordings

< to be added>

Table of Contents

Table of Contents

Attendees

Please add yourself, if you like.

Discussion items

Time	Item	Who	Notes
05min	admin

Martin Skorupski

bimo fransiscus asisi	Next meetings Wed 2025-01-08 8am EST by Martin Skorupski Tue 2025-01-14 9pm EST by Rittwik Jana Wed 2025-01-22 8am EST by Martin Skorupski Tue 20245-01-28 9pm EST by Rittwik Jana K Release Timeline
10min	Email Thread: Access to OSC INT Server	@all	Related debugging session are scheduled. Any think to be discussed here? Jackie has issue remote access to O-Cloud. Ashutosh has no similar access issue. Will try to use OpenVPN instead of Wireguard. Bimo will share OVPN account to Ashutosh and Jackie.
10min	E2E testing		Creation of a link list to get an overview (docs, readmes, wiki, ....): Existing Information AM/ML ODU-High OAM/SIM Rest missing needs to be discussed by email (ptl-private) did not happen - sorry k-Release reported page for deployment testing continuous of functionality - > xTesting - robot test integration issue between robot and xTesting PTLs → common template https://hackmd.io/@q-eiMFW8TLa2Pa3QKECMzw/SJXLyJDNJg input preferred from James about xTesting and its advantages. L-Release it/test continuation needs confirmation from RIC and AIMLFW PTL to update the robot test file
15min	OSC integration use case	@all	Details should be documented here: Release "L" copy from B and reuse for L use case setup by INT or by PTLs each PTL provides a proper documentation feedback by INT if it works validates and approves documentation INT requires definition of use cases definition by PTLs describe flows to be integrated and tested AI: Martin send to PTLs OAM/SIM / O-DU /OAI (example) deploy OAM → connection supervision what is a health check PM to OAM to Grafana flow related FM flow Ankit Barve will take the lead for OAI + WLS + OSC DU HIGH integration integration lab must work!!! xFapi Servers required currently in OAI lab and Radisys lab NTUST: end-to-end test - see also slack AT&T-Lab → COSMOS-lab → Ivan Seskar AI: Martin: kick off an email no answer follow up by Martin

discussion ongoing ..

There are options for O-RAN f2f ... but some requirements should be exchanged see O-RAN-SC RSAC Slack.... https://o-ran-sc-lf.slack.com/archives/C07CT61549M/p1735998051389359 OAI team will be back from new years vacation and will start discussion this week with Ankit. Goal: O-DU Integration with RU-sim UE-emulated Ankit share the parameters that need to be tested. Table for ODU High parameters in https://hackmd.io/fx7gYOpHSNSJOe0De1aaRA?view#Configuration have been confirmed Ankit(parameters are OK). Slack discussion is ongoing but no response from Intel yet. Ankit: RAN Integration should be come together since need expertise from each component and cannot be done by only a single person. Suggest to have debugging call regular week to solve the blocker. ODU High still testing K release so stick with I Release. How to address e2e?!?!? required for e2e testing What are O-RAN WGs/FGs defining! Module up health check ??? → O2?!??!? Interface periodically health check e.g. OAM O1 WG#10 → ves healthcheck e.g OFHM WG#4 → supervision best practice from OTIC → TIFG AI working on it! security e2, a1, o2, r1, ... 3gPP interface → F1, E1
05min	O-RAN F2F Paris 2025-02-24+	Martin Skorupski	Per ToC - would be nice of have a running demo in the "networking area" time until ~mid January Martin - reach out to OAI for a joined Email conversation is ongoing - no decisions yet...
00min	gerrit clean up	Martin Skorupski	https://gerrit.o-ran-sc.org/r/q/status:open,25
10min	Q/A	@all	bimo fransiscus asisi K Release Integration and Testing Verify Deployment Guideline Meeting time for this meeting SMO - UTC → one our before - noon UTC - in summer and in winter Decision from 2025 onward we use noon UTC !!! calendar must be updated