2024-07-24 RSAC Meeting notes

Date

Date: 24 Jul 2024

Time: 6pm PDT | 9pm EDT | 03:00 CEST +1 | 09:00 UTC 08:00 +1

Join Zoom Meeting

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

Goals

Define demo Details for O-RAN F2F in Montreal (Oct28 - Nov01)
Define requirements for O-RAN-SC

Discussion items

Time	Item	Who	Notes
05min	admin	Rittwik Jana	Next meetings Tue 2024-07-30 9pm EDT by Rittwik Jana Wed 2024-08-07 8am EDT by Martin Skorupski Tue 2024-08-13 9pm EDT by Rittwik Jana Wed 2024-08-21 8am EDT by Martin Skorupski
05min	O-RAN F2F demo	Rittwik Jana	Request to all PTLs Please think about what are you going to demonstrate at the O-RAN F2F in Montreal Oct28 to Nov01. We would like to understand how to structure the demo sessions. Format does not matter much - content matters - live demo and/or recorded, with and with out slide set - you decide Message to O-RAN: O-RAN-SC is alive and needs further support O-DU and OAI integration description by email Non-Rt-RIC - with AI/ML candidate - details will be discussed SMO - Tacker EtSI profile - fault management, performance management is target SIM Alex Stancu Hierarchical OAM functions Use Case OAM Martin Skorupski ... Martin plans to be in Montreal, but it is not finally confirmed.
20min	Blockers - general discussion:	Rittwik Jana	SMO Seshu Kumar Mudiganti Feature release is completed - is there a link? AI Martin O-DU high Ankit Barve ASN.1 issue: NTUST testing is also facing this issue while testing (Abdul Wahidis checking) Issue is still open - in email. Ankit Barve will check. Abdul Wahid is still checking this issue. Any updates? ongoing - will be started in August New release features are updated for K release. K Release OAI team is working on uplink response. Will start coordinating with them after this implementation for E2E call flow. INT bimo fransiscus asisi Question: How can we help to update this page? Discussed simplifying the NTUST INT lab with OAI UE sim Do we still need OTF (open test Framework)? Maybe start INT meetings at a regular cadence. Wait for Slack to start an INT channel to have more realtime communications O-DU high - low integration experiment options Done by OAI: OAI UE + OAI DU LOW + nFAPI（socket）+ OAI DU HIGH OAI Branch: nfapi-fixes-ntust Status: E2E is done OAI UE + O-RU + OAI DU LOW + nFAPI（socket） + OAI DU HIGH + OAI CU OAI Branch: nfapi-fixes-rebased-demo Status: E2E is done Ongoing: Option 1 - OAI UE + OAI DU LOW + nFAPI（socket） + OSC DU HIGH OAI Branch: o-du-l2 Status: UE can receive SIB 1 and send RA Option 2 - OAI UE + OAI DU LOW + FAPI（WLS） + OSC DU HIGH (on-going by EURECOM and Radisys) OAI Branch: nfapi-wls-integration Status: fixing DCI problem Option 3 - UE + RU + FlexRAN DU LOW + xFAPI + OSC DU HIGH (or, OAI DU HIGH) O-DU-high - O-DU-low integration will be focused in the next step idea: to bring it to the ToC
10min	Software release procedure	Martin Skorupski	The importance of developer guides and software release processes: Clear structure process will reduce efforts in the code contribution process and will leads to world wide know and understood processes. This way, it is also easier to get contributions from developers any developer anywhere. Well defined process and pipelines will avoid adding problematic software artifacts into releases. On the O-RAN-SC wiki we have some Developer guides, which the different teams should follow: https://wiki.o-ran-sc.org/display/ORAN/Project+Developer+Wiki LF itself has nice pages and training: https://training.linuxfoundation.org/training/beginners-guide-open-source-software-development/ https://www.linuxfoundation.org/resources/open-source-guides https://training.linuxfoundation.org/training/creating-effective-documentation-for-developers-lfc112/ Please have a look - and correct or make us aware of misleading or outdated statements. updates for new release should follow concepts of previous releases or should changes and concepts should be better documented upgrade procedures could help
05min	gerrit clean up	Martin Skorupski	https://gerrit.o-ran-sc.org/r/q/status:open,25
10min	OSC integration use case	@all	target: drive collaboration integration use case across o-ran-sc projects have a look at the MVP use cases - as inspiration MVP might be not the target int - focus on pairwise testing to focus on feature implementation by the projects
00min	Q/A	@all	if any
			End of the meeting