2025-04-30 RSAC Meeting notes

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

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. 

• OSC Integration Use Case: Energy Saving →  INT-OSC_E2E_Integration_Usecase_Rel_L_20250319.pptx
• Discussion End-to-End Integration
  • Architecture
  • PM Streaming ??
• Questions:
  • will the rApps (2x) and the xApps (1 to 2x) be open-sourced
    • where is the code for current rApps to inject the code into a sample rApp-frame?
    • Please see: https://github.com/bmw-ece-ntust/nonrtric-rapp-energysaving/tree/master/ES%20rApp/src
    • Please see: https://github.com/o-ran-sc/ric-app-rc 
  • can we have sample data for the AI Interface?
  • can we share E2 sample data?
    • to instruct UE to go to the remaining cell
• Reuse or create a topology for the use case
  • 1x NonRtRic, 1x O-CU-UP 1x O-CU-CP, 2x O-DU, 4x O-RU (2 per O-DU) → 4 cells → 2 cells are just used from each O-DU ? - some UEs (not part of the topology) → one UE is sufficient for that use case
  • maybe reuse: O-RAN-SC OAM Topology
• work needed on the report: https://hackmd.io/@q-eiMFW8TLa2Pa3QKECMzw/rkP1LlRyex
• request for documentation (rApp Manager)
  • please look to the "sample rApp" with producers and consumers

Configuration 

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

00min

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

• M-Release Timeline
• M-Release
• Release "M"