2024-12-11 RSAC Meeting notes

05min

admin

@Martin Skorupski

Next meetings

K Release Timeline

10min

Email Thread:
Access to OSC INT Server

@all

Summary of 

1. Initial Issue:
   Fransiscus Bimo reported issues reproducing the success of integrating xFAPI and L1, despite discussions with Prof. Vipin’s team. Errors include failure in "API (UL/DL)" and mismatched parameters. Bimo requested a debugging session for resolution.

2. Debugging Attempts:

   • Ray-Guang Cheng (NTUST) identified two potential issues:

     1. L2 not sending DL/UL configurations.

     2. xFAPI failing during conversion.

   • Vipin’s team and collaborators (Ashwini Bhagat, Ankit Barve, Sheryl Lai) conducted debugging and suggested further checks on L2 and FlexRAN environments.

3. Current Status:

   • Installation steps for xFAPI are documented in the updated Deployment Guide (shared by Vipin).

   • Vipin confirmed successful integration of FlexRAN and OSC DU High at NTUST, but issues persist in other environments.

   • Scheduling of meetings has been proposed to expedite debugging.

4. Actions Taken:

   • Ashwini modified phycfg_xran.xml and confirmed some fixes in Testmac mode but highlighted lingering issues in FlexRAN + xFAPI integrations.

   • Discussions are ongoing about time zones and meeting slots for further collaboration.

5. Next Steps:

   • Follow-up meetings or calls are required to address specific issues in xFAPI and L1 integration, especially debugging failures in configurations and environments.

   • Feedback on the updated deployment guide is awaited.

Debugging session are scheduled! 

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.

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

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 

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