| | | |
|---|
Sep 4, 2024 | 2024-08-14 RSAC Meeting notes |
|
|
Aug 14, 2024 | 2024-08-14 RSAC Meeting notes |
|
|
Aug 7, 2024 | 2024-08-07 RSAC Meeting notes |
|
|
Jul 30, 2024 | 2024-07-30 Meeting notes |
| https://zoom.us/rec/share/52BEMBFuFknsrNQzzvb3XSTk9kI85uj9kSL1SEDwoLZRWIYVps2iPtOXyE-8fVQ.LoXYjUj0oMhXEKMZ |
Jul 24, 2024 | 2024-07-24 RSAC Meeting notes |
|
|
Jul 16, 2024 | 2024-07-16 RSAC Meeting notes |
| https://zoom.us/rec/share/y8uKG9K-Cbmv7lYOcdpX2bmDaaQ2qFoe_K7Xn_vM8kc-h76jjpbowMvAJ_hD3tzv.PA9SjZkAKMFjxCRP |
|
|
| https://zoom.us/rec/share/S_t2Xbc-cw74VlkCFSnUJTSJ4n_QnTlLFQVwjIicmxJrxKxLLnii0CRIz25HgQrN.vvhxGHb6DQfF8i-w |
Jun 18, 2024 | @Ankit Barve O-DU high documentation is done wiki page cannot be updated; @David Kinsey [AT&T] has been notified on this issue. CU image does not support O1. If O1 is needed, BM is the only option We would like to cloud native approach. To test E2E, better to use containerized image. Release is at the end of this month. @bimo fransiscus asisi Open RAN summit at Taipei. Topics: Open Ran and 6G; Open RAN and open source; Speed up the SMO decoupled project. Use OSC Taiwan as the implementation testbed; Energy savings use cases have been demonstrated; Viavi RIC tester. Need to wrap near-RT RIC and non-RT RIC and SMO on top of O-Cloud for OSC Taiwan lab @Peng Lu Intel is waiting for Prof Rathi's code base changes on xFAPI related to Flex RAN ODU low; Legal clearance has been obtained; Still waiting for detailed information on how to access the code; OSC Taiwan lab can potentially obtain the code (binary) from Netweb;
|
| https://zoom.us/rec/share/Q5pqZ3Pk4nNGEhSDFFQ7wZEtEbuxIatD0EmOML1tMwKvI1Mehqn0A4qCcKnTKc0o.0nXJiLydImvTv46A |
Jun 4, 2024
| Peng Lu (Intel)
- Update from 3rd party company, Netweb
- Works with Prof. Rathi integrating latest code base xFAPI
- Sindhu from Intel to obtain license for O-DULOW FlexRAN from Netweb
- Netweb got authorization from Intel
- No info from Netweb yet
- Can Intel authorize NTUST directly?
- Due to legal issues, pls obtain license from Netweb NTUST labs (Bimo, Prof. Ray)
- Prepare for Open RAN summit after F2F in Taipei demo Ankit
- Prepare for release doc and final changes
- Try to complete in 2 weeks time
- O-CU support O1 and E2 i/f?
- Docs are available from Radisys website
- Bimo looking for support of E2 and O1
- Not written in tech doc; is it possible to get support from Radisys?
- Ankit will check and get back to Prof. Ray Prof. Rathi
- xFAPI P5 is working
- P7 msg are being tested. errors ar ebeing resolved
- will be able to connect OAI with ODU high soon after P7 success
- Can you upload some src code if possible? Request from NTUST
- How to modify ODU - high?
- No need to change ODU-high since WLS is supported
- Planning to release doc soon TOC mtg
- mentioned about add detail on FAPI for WG8
- standardize shared memory architecture
- David K is coordinating a session in the F2F? |
|
|
May 21, 2024 | Still waiting for final legal clearance from Intel. Technical issues have been resolved, currently it is more of a business issue/process to finalize the legal clearance. Also waiting for access from Prof. Rathi pending presentation at the TOC which was cancelled last week. Expect that to occur this week. In the architecture presented last week the WLS code is part of the ODULOW project and is used by ODUHIGH. Since the xFAPI is below the WLS layer it should be part of ODULOW even though it provides implementation access to current ODULOW base or the OAI L1 or potentially other L1 implementations. Plan to request a WG8 session with OSC/O-RAN members to discuss Interoperability testing of different L1 implementations using the FAPI interface, which may include the transport protocols (WLS) interfaces.
|
|
|
May 15, 2024 | @ankit
OAI development for P5 messages for FAPI
requested Prof. Rathi to share xFAPI code to O-DU high team Prof. Rathi provided an overview of xFAPI; had discussions with Intel on how to release xFAPI code to OSC
one more week before sharing code
created a blueprint on how to use xFAPI for integration
xFAPI is already on K8s cloud native architecture
milestone: try to release xFAPI end of month discussions with WG8 starting to introduce xFAPI to O-RAN @bimo requested
license extension from Radisys for CU to share with NTUST
Ankit to check with Ganesh and get back to Bimo @johnkeeney
NONRTRIC - trying to tidy up svc mgr for release timeline @martin
OAM - implemented and tested published YANG model from Nov train and looking into March train @alexstancu
SIM - AI/ML telefonica dataset analyzing it
SMO - K8s profile implementation is going well,
Tacker update FM/PM discussions are in progress, sequence diagrams started
| xFAPI architecture | https://zoom.us/rec/share/v64WGduTqzUuivsXiTGKe5funy6PBmH2TTPyqFs3yj7p3XYaFKrrzoSORUWnkRr5.tvP2vX6QmEegDHiG |
May 7, 2024 | Updates from One summit @Ankit Barve Requesting Prof. Rathi's xFAPI code base to be uploaded to OSC repo @Peng Lu Intel still having conversations re Flex ran version for OSC going forward (deprecate old version and move to a new version @Ray-Guang Cheng Requesting Intel to provide resources to support the O-DU low / O-DU high integration work and also with xFAPI integration in NTUST OSC lab. @Peng Lu is looking to support this work in NTUST lab. |
| https://zoom.us/rec/share/Viv0NmRnBMYsddtC4zXkxIz1QvhA1j34CopIut35xAoqE8U3Be1ottJH36O4A9V0.06DhCzACIMneKnJn |
May 1, 2024 | Need plan from ODULOW (@Peng Lu ) on how the FAPI update from the x-FAPI (Prof Vipin) will be incorporated so we can establish some timeline expectations. lab status of NTUST
1. @ankit @ganesh the current O-CU binary is DPDK based, and we need a socket-based. The socket-based release needs to be tested then it will be released and the license will be provided at the same time. @Ankit Barve is assisting. |
|
|
Apr 23, 2024 | lab status of NTUST
1. @ankit @ganesh pls provide license extension of Radisys CU to NTUST
2. raise this issue in the TOC re license renewal
3. ODU high and low integration contact Prof. Vipin Rathi
4. OAI and ODU high status - what is the status?
5. NTUST - odu high and low integration decided to postpone
mtg with Prof. Rathi, he made some changes to flex ran code 22.07 version
Intel (@Penglu) is going to evaluate this code, in the mean time two options
- continue to support the old release
- wait to use Prof Vipin's codebase for the new version
NTUST may also need some NDA
5. near-RT RIC
- found some issue of I rel deployment
- CI/CD pairwise testing issue needs to be addressed (@JamesLi)
- E2SM CCC code base is not updated or missing
- G rel K8s v1.22 - already deprecated, need to move to v1.28
- Needs to update the helm chart
- @Bimo to send email to PTL of near-RT RIC |
|
|
Apr 17, 2024 | ODULOW has discussed progress with Prof. Vipin Rathi. It seems that there are some changes to the FlexRAN code. ODULOW believes there is some ability to use his FAPI changes into the ODULOW base and they will be collaborating with Prof Rathi to incorporate those. We then should be able to move away from the Release "F" baseline we have been using. OSC Taiwan Lab still waiting on Radisys to renew the OCU License so that we can continue to use the binaries in the end-to-end service path.
|
|
|
Apr 9, 2024 | Integration: @Ankit Barvearranging call to test with Intel
OAI testing call is in progress
Almost done with O-DU high release development features Ashwini (Intel) - repetitive messages observed on Uplane UL
Daniel from Viavi has proposed a testing call today Prof. Ray (NTUST) has linked Prof. Vipin Rathi from Delhi university
They have successfully integrated 23.07 version flexran with OSC DU-high, connected to commercial RU
plans to move 23.11 version
any more info on FAPI interface? Did they write their own FAPI? Ashwini is sending an email to Prof. Rathi for clarifications |
|
|
Mar 26, 2024 | Update on TUWU @fransiscus bimo problem in ODULOW but there is also a problem in RUSIM. Working on closing the RUSIM while the resource is available. Then need to work on OSC ODULOW. ODULOW is working on a plan on how to upgrade to a newer release. Intel is working this. It is hard to get developers/students to sign up for work on an outdated version. ODULOW @Peng Lu will look into being able to match the Viavi configuration for OAI ODULOW. This will allow easier transitions from one implementation to another.
|
| https://zoom.us/rec/share/8SoLq9WMWSkMd5evbuy7-f2hNQz56Oau03QLwaML5OX4vSTXjGDPj-kcYcQjQ8nc.4D0AJ-G7Dg_9m_MW |
Mar 20, 2024 | @Ankit Barve(O-DU high)
dynamic uncompressed mode - Intel to respond on header length issue
OAI L1 L2 data transfer
OAI making NFAPI msg implementation changes
WLS shared memory OSC has provided the changes
2 months for changes to be implemented
multiple UE per slot almost done
XML based config of ODU-High @bimo fransiscus asisi @Ray-Guang Cheng (NTUST lab)
No updates from Intel
raise to Ubuntu based version for basic testing
Prof Ray or Ankit to raise this issue
Is it possible to add the FAPI i/f to the WG8 spec?
it is not clear which version of FAPI i/f is supported in WG8
new version of FAPI can support MIMO Radisys O-CU O1 and E2 and E2SM versions?
Free 5GC is connectd with Radisys CU in NTUST lab
PDU session established between O-DU high and Radisys O-CU
NTUST lab to send Ankit O-CU config
multi UE testing error - No HARQ (being worked on separate branch)
A1 msg interactions being tested in NTUST lab @Martin Skorupski @Alex Stancu Martin/Alex OAM/SIM
working on A1 simulator for latest spec
ONES summit
feedback on YANG compliance is delayed
transition from WG5 to WG10
fixed OAM controller on netconf side
porting back to previous releases to ONAP SDN-R
working on deployment in NTUST lab @John Keeney (Ericsson EST) Non-RT RIC
continuing on rApp mgr
svc exposure 1st version available
uses a service registry registration and discovery i/f
uses a API g/w
A1 policy starting to see some specs for WG2
cleanup of existing API with acls and documentation
getting support requests from HCL, Fujitsu, Samsung, universities
looking for help from INT project (@James Li )
- for a unified deployment script
- proper integration tests for A1 policy controller and A1 mediator
traveling to ONES summit @James Li , INT project
update pairwise testing for A1 mediator
ONES mtg should get started for labs updates |
|
|
Mar 12, 2024 | @bimo fransiscus asisi OSC O-DU Integration O-DU Integration still in progress. Currently waiting Intel to fix bug on FlexRAN. Suggested to confirm to @Peng Lu for possibility of releasing newer flexRAN version for the integration. Reason:
Speed up the integration (skip the bug). New FlexRAN requires different OS. Different env can cause different issue. Double effort for future integration. Fixing the bug might not be beneficial because it's an outdated version. Resources availability cannot be fixed.
| | https://zoom.us/rec/share/uqDMA8FNNrb4oSoHxqJFXMxbAmaehT5AE-jQvvA3T3L3JL-CpDsTOL-R0JyaB6I2.q0MaRcvFVSggARCW |
Mar 6, 2024 | TOC mtg for 3/7 will present items 1 and 2 below Project review @Ankit Barve ODUHIGH
Integration working in NTUST Integrating with ODULOW Integrating with OAI ODULOW Uncompressed Mode not available in TM500 In Compressed mode payload size is incorrect
ODULOW is debugging this, even though most commercial implementations do not use the mode. Problem appears to be in L1.
BIMO to provide status update to TOC
ODU Integration SMO-OCloud Integration
@Martin Skorupski OAM Some issues with versioning between O-RAN Yang and 3GPP Yang CVE Issues how does OSC respond to those. CVE report - https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=O-RAN When is Open Source ready for such scanning When is OPen Source considered Commercial Grade Is there an intent to make OSC look bad Bring Issue to TOC (Martin/Alex)
@John Keeney (Ericsson EST) NONRTRIC R1 rApp Management working on Service Exposure Services for R1 <JK-added> Service exposure manager - aligned with 3GPP CAPIF & R1-SME now almost ready for use</JK-added>
<JK-added> Data Management & Expose (DME / NONRTRIC-ICS) remains stable</JK-added> R1-DME Specification work is moving away from current implementation, may take significant effort to re-align. Currently resources are not available.
Working on A1 Service exposure over R1 Sample rApp for demonstrating AI/ML training using KServe planning to review with AIMLFW project. Last 2 releases issues with A1 end point in Near-RT RIC Not sure of A1 compliance in Near-RT RIC developed work-around adapter to deal with discrepancy which allows integration. Need a regular integration test. Will work with INT to establish one.
Descoping some old functionalities
@James Li INT POWDER looking for joint news publication which will help POWDER. James providing information on how OSC uses POWDER for Integration. James might eventually bring such a news release to the TSC for approval.
@Toshiaki Takahashi discussing Tacker and SMO component interaction
|
| https://zoom.us/rec/share/cuTPTeOF40sr54vWtupo2iHGmS56ZGAptuqFBtNQ9ELANU-mTYiraufTqjSLo_UB.S931l5MWTYEOP0qq |
Feb 7, 2024 | project updates O-DU high (@Ankit Barve) integration in NTUST lab, PTP integration issue being resolved OAI lab interaction re FAPI implementation, L1/L2 shared memory OAM (@Martin Skorupski)- scanning Yang message specification changes and incorporating in OAM code base SIM(@Alex Stancu) - waiting for @Ultan.Kelly to finalize on procedures for Viavi simulation data release NONRTIC(@John Keeney (Ericsson EST)) - focusing on rApp mgmt INT(@James Li) - working with PTLs to document pair-wise integration scenarios SMO(@Seshu Kumar Mudiganti @Toshiaki Takahashi) - Tacker plan integration with SMO components progressing
Create RSAC slides for F2F mtg @Rittwik Jana@David Kinsey [AT&T]
|
| https://zoom.us/rec/share/VDu3O0dEwMSTv8awA4RJe8HcCzXzoMeYqr78VsFek33TuHFRvrBxeK9rjwX3Y6PJ.tHYfPDyldhd4JfGV |
Jan 24, 2024 |
| AIML ES Data set available (TIM), Viavi data is semi-private, password protect the file. A procedure needs to be in place for users to request access. Who approves this but it should be a “written” response to provide access traceability. Another option is to have the data in the labs but not in a repo/nexus. Access to the lab would provide access to the data. We need to bring to TOC to ask Viavi what procedure we should use.
Update on ODUHIGH, ODUHIGH now working again with ODULOW, tomorrow working ODUHIGH+ODULOW+TM500.
SIM
• Simulators to align with latest YANG models. No feature requests.
OAM
• Looking for November Train specifications for testing. Already noticing schema version mismatches.
NONRTRIC
• rApp Management/Execution
• Some work on Service Exposure
INT
• More Pairwise testing | https://zoom.us/rec/share/h56Ft26clrbIC9GAjfltoVWsc87QhM3ttqkrw8zS9fM35_LbKqfTzLF65dbawXbm.a46RjNseavdivWgA |
Jan 16, 2024 | O-DU high integration project for J release | @bimo fransiscus asisi Present the OSC Taiwan Lab status. Slide: https://wiki.o-ran-sc.org/download/attachments/3604609/OSC%20Taiwan%20Lab%20Status%20-%20Jan%2010%2C%202024.pptx?api=v2 | https://zoom.us/rec/share/sloIP1qERdFKjURx_yOX19IP-qNniLsbeh3tu3al6wCL5iQSKlXhhxNxZHkVMOm7.AL_M5NWfTJll8K6G |
Dec 13, 2023 | Release Readiness RSAC holiday schedule rApp Mgmt Demo (20 minutes) | Still work for projects to complete on Release "I" page to document the release by tomorrow's TOC call. Tuesday Dec 19, 2023 cancelled. If it becomes needed we will need to ensure someone can open the bridge. Wednesday Dec 27, 2023 cancelled. Tuesday Jan 2, 2024 cancelled. If it becomes needed we will need to ensure someone can open the bridge. Next RSAC meeting Wednesday Jan 10, 2024 |
|
Dec 6, 2023 | Use RSAC portion of next week SMO+RSAC (need to confirm with @Seshu Kumar Mudiganti ) for rApp Mgmt Demo (20 minutes at end) |
|
|
Nov 29, 2023 | February Demos: OAI/OSC Workshop Outcomes: Evaluate ODUHIGH to use OAI ODULOW OAI strives for compliance and certification; OSC strives for demonstration of concepts and techniques. Security as part of Open Source, is currently an after thought for OSC and might take a large effort to make it a fore thought.
ES Capabilities rApp Management (early) ES rApp (in Progress) Model Management SIM ODUHIGH
|
