2025-04-30 RSAC Meeting notes

2025-04-30 RSAC Meeting notes

 Date

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

  • @Ankit Barve

  • @ASHWINI BHAGAT

  • @Ray-Guang Cheng

  • @John Keeney (Ericsson EST)





Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes

05min

admin

@Martin Skorupski

Next meetings

01min

admin

@Martin Skorupski

Info:
M Release Timeline - L Release Timeline

01min

Release Planning per Project

@Martin Skorupski

Update:
M-Release - L-Release

05min

CVE scans

@Martin Skorupski

Topic can be removed from future agendas

05min

NUST for TE&IV

Jerry from NUST

Just a follow up

Input from Jerry from NUST for TE&IV

  • high-level: config of RAN based on TE&IV data

  • call flow for get topo details (single, multi)

offline discussion between  @John Keeney (Ericsson EST) and Jerry

Topic can be removed from future agendas

10min

input from NonRtRic/AIMLFW/SIM/OAM meeting

@Martin Skorupski

https://lf-onap.atlassian.net/wiki/spaces/DW/pages/8525825/2025-04-29+Meeting+notes+ONAP+O-RAN-SC+SMO+-+Meeting+-+Agenda

  • to other projects are targeting a similar use case and use case architecture - however the logic of the rApps are different

    • ideas: common "rApp store" repo vs dedicated "rApp repos" - for sure rAppManager code should be in a different repo than rApps

    • There is the ask to the teams to create a similar wiki like Bimo already did - this will help to work efficient on the common parts and highlight the differences between the use cases and its implementations. 

30min

Integration use case

@bimo fransiscus asisi

05min

Q/A

@all?

AI by Bimo: Lab setup in Taiwan lab  - work on SMO deployment -> PNF registrations -> PM flow



End of the meeting





00min

Configuration

@John Keeney (Ericsson EST)

Configuration 

  • support by Sim ? VES from O-DU-Sim and/or O-DU-high

00min

OSC ???? use case

@all

M Release Planning

  • Brainstorming

    • follow up from L Release

    • Security?

      • TLS1.3?

    • Integration with O-Cloud (INT @bimo fransiscus asisi)

      • Resource Allocation

        • How many resource are needed? 

        • tacker integration

          • 1VM 8Cores - 16GB  SMO host

          • bare-metal - 16 CPU Core 128 GB RAM...

          • -> @Martin Skorupski contact @Ivan Seskar  

References