Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

Info
titleDate

Date:

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

TimeItemWhoNotes
05minadmin
05minO-RAN F2F demo

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 

OAM Martin Skorupski 

  • ...
  • Martin plans to be in Montreal, but it is not finally confirmed.

30min20min

Blockers - general discussion:
  •  O-DU high Ankit Barve 
    • Permission to edit wiki page is still not there for Ankit reopened ticket to LF
      • It topic closed and can be removed from agenda Resolved
        •  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
The importance of developer guides and software release processes:
  1. 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.
  2. 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:


LF itself has nice pages and trainingstraining:

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 uphttps://gerrit.o-ran-sc.org/r/q/status:open,2505min

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 

00minQ/A@all
  • if any



End of the meeting

 Action items

  •  

 Decisions

  • if any

References

  • if any

Table of Contents

Table of Contents

Attendees

Please add yourself, if you like.


Recordings

https://zoom.us/rec/share/vU94LjdQoFCHiNWZBKBKNx9tp4dZJZG3S8FU5KA_HBvrCiyVZ8vEOYnEpTGcIKSa.C-CJkO4hbltB_qHAcloud-highstreet-technologies.com/s/4RSXtB5afibppR2

(sorry - recorded to computer and not to cloud - I will do it better next time)