/
2025-11-05 RSAC Meeting notes

2025-11-05 RSAC Meeting notes

 Date

Date: Nov 5, 2025

Time: https://lists.o-ran-sc.org/calendar

WebConf: Join Zoom Meeting

 Goals

  • Define requirements for O-RAN-SC

  • Define use cases for M-Release

 Recordings

Table of Contents

Attendees

Please add yourself, if you like.

  • @bimo fransiscus asisi

  • @Peng Lu (Deactivated)

  • @Ankit Barve

  • @ASHWINI BHAGAT (Deactivated)

  • @Ray-Guang Cheng

  • @John Keeney (Ericsson EST)

  • @Saul Gill

 Discussion items

The discussion is around M-Release Planning - the table below is for discussion purpose only and does not reflect any commitment.

Time

Item

Who

Notes

00-05

admin

@Martin Skorupski

Next meetings

  • Wed 2025-11-12 noon UTC

  • Wed 2025-11-19 8am UTC

  • Wed 2025-11-26 noon UTC

  • Wed 2025-12-03 8am UTC

05-10

O-RAN-F2F

@Martin Skorupski

Who is going to demo something?
https://lf-o-ran-sc.atlassian.net/wiki/spaces/EV/pages/617938945

  • Info from Yuya Kuno: Tacker

THANKS YOU VERY MUCH FOR YOU PRESENTATIONS.

10-15

Versions

@bimo fransiscus asisi

https://lf-o-ran-sc.atlassian.net/wiki/spaces/RSAC/pages/419725360

A check should be implemented if an Clould-Infa exists or not - only then deploy an Clould-Infa for SMO.

Alignment of Milestones between the projects required → AI: @Martin Skorupski

  • target: AIMLFW should follow NonRtRic approach

15-15

O-RAN-SC O-DU integration

@Ray-Guang Cheng

O-DU LOW + xFAPI is done by Kyle @ Intel and Madhav @ Delhi University
Madhav is waiting Ankit to provide the correct repo for O-DU HIGH
Madhav will finish O-DU LOW + xFAPI + O-DU HIGH

15-25

Vision!
End-to-end use case

@bimo fransiscus asisi

SMO “one-click” deployment with selected components

  • Continue with the “SMO one-click deployment” as stared by NonRtRic team (@John Keeney (Ericsson EST) )

    • Document the requirements an steps, automated and manual check points, @phani with support of all teams (NonRtRic, SMO, Tacker, AIMLFW, OAM, SIM, …)

    • rappManager first to onboard rApps

    • chartmuseum - by INT only

ES/EE rApps and End-to-end flow

  • Continue work on https://lf-o-ran-sc.atlassian.net/wiki/spaces/IAT/pages/361758725 as started by INT team (@bimo fransiscus asisi )

    • PM Streaming according to spec

      • requires design and architecture - 3GPP/O-RAN - ASN.1/websocket - stream info

    • collaboration with e2e integration

    • rApp onboarding

    • integration with AIMLFW → with updates on call-flow

    • Alignment with Non-RT RIC team and SMO/Tacker team required for rapp onboarding management and automatic homing via O2.

      • ES-rApp and Profile merged by NonRtRic team - please have a look - (add reference)

Integration of “model learning” into the end-to-end flow above.

  • // to be updated by Subhash

R1 compliant interface

Security

  • common user management

--

Bimo has created Jira for rApp development

  • discussion between Bimo and Aravindhan

    • clean-up the env by script

    • follow-up in Jira AI: @Martin Skorupski add Jira reference

Subhash

  • installation along with SMO

  • alignment in OWL

  • share approach with Bimo

  • Jira will be created by Subhash - AI: @Martin Skorupski add Jira reference

Github Action

  • Matt - is your men

25-30

Never ending CVE

@Martin Skorupski

Does it make sense? Concerns, suggestions?

@Sridhar Rao @Matt Watkins https://gerrit.o-ran-sc.org/r/c/oam/+/14745 was merged - please let us know if you can start the implementation around it before other repos will be tagged like this.

INFO Sep 24, 2025

Agreement reached between OSFG and WG11 → to be removed from agenda

30-35

Q/A

@all?

Lab Requirement for O-DU integration with Tacker

@Martin Skorupski find lab… ongoing…

 

End of the Meeting

 

 

55-55

 

@Ray-Guang Cheng

Activities at NTUST (Taiwan Lab)

  • Presentation by @Yosafat Marselino (please see presentation in previous minutes)

  • end-to-end pipeline with O2 and OAI

  • testing pipeline

Open Points

  • How to integrate NFO extensions from Taiwan team into NFO by Tacker Team? → Toshi

  • How to integrate NFO into SMO? → Seshu

Missing function of NFO to be contributed

  • O2-DMS

    • ETSI profile to O-RAN-SC repo - SMO/O2

    • How is the integration with Tacker in this case?

  • O2-IMS

    • some extensions - where? to be answered by Seshu

AI @Martin Skorupski - reach out to Tacker and SMO team

 

Info from @John Keeney (Ericsson EST)

  • SMO deployment targets deployment of tacker and/or nephio based approach - current start is nephio

  • IMS in nephio implementations ongoing…

  • FOCOM implementation in nephio by Capgemini

Thanks Toshi for sharing the Tacker plan: <add link here>

55-55

Different implementation for similar functions

@bimo fransiscus asisi

Alignment of similar deployments within SMO

55-55

M-Release

@Martin Skorupski

Timeline

How to update

55-55

Resources in OWL

@bimo fransiscus asisi

Resource Allocation

Password Manager

Github Actions / CI/DI and impact on OWL

  • external APIs → triggered from outside

  • AccessControl and firewalls software?… - Martin/Ravi

@bimo fransiscus asisi is using srv2 until Friday

55-55

N-Release

@Martin Skorupski

Just Info - N-Release → https://lf-o-ran-sc.atlassian.net/wiki/spaces/REL/pages/495878146