30 Jul 2024 

24 Jul 2024 

2024-07-24 RSAC Meeting notes

16 Jul 2024 

2024-07-16 RSAC Meeting notes

18 Jun 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. 

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?

 21 May 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.

15 May 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

Image Modified

07 May 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.   

01 May 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.

23 Apr 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

17 Apr 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.

09 Apr 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

26 Mar 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.

20 Mar 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

Image ModifiedImage ModifiedImage ModifiedImage Modified

12 Mar 2024 

1. bimo fransiscus asisi OSC O-DU Integration
   1. O-DU Integration still in progress. Currently waiting Intel to fix bug on FlexRAN.
   2. Suggested to confirm to Peng Lu  for possibility of releasing newer flexRAN version for the integration. Reason:
      
      1. Speed up the integration (skip the bug).
      2. New FlexRAN requires different OS. Different env can  cause different issue. Double effort for future integration.

      3. Fixing the bug might not be beneficial because it's an outdated version.

      4. Resources availability cannot be fixed.

Image Modified

06 Mar 2024 

TOC mtg for 3/7 will present items 1 and 2 below

Project review

1. Ankit Barve ODUHIGH
   
   1. Integration working in NTUST
   2. Integrating with ODULOW
   3. Integrating with OAI ODULOW
   4. Uncompressed Mode not available in TM500
   5. In Compressed mode payload size is incorrect
      
      1. ODULOW is debugging this, even though most commercial implementations do not use the mode. Problem appears to be in L1.
   6. BIMO to provide status update to TOC 
      
      1. ODU Integration
      2. SMO-OCloud Integration
2. Martin Skorupski  OAM
   1. Some issues with versioning between O-RAN Yang and 3GPP Yang
   2. CVE Issues how does OSC respond to those.
      1. CVE report - https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=O-RAN
      2. When is Open Source ready for such scanning
      3. When is OPen Source considered Commercial Grade
      4. Is there an intent to make OSC look bad
      5. Bring Issue to TOC (Martin/Alex)
3. John Keeney (Ericsson EST) NONRTRIC
   1. R1 rApp Management
   2. working on Service Exposure Services for R1
      1. <JK-added> Service exposure manager - aligned with 3GPP CAPIF & R1-SME  now almost ready for use</JK-added>
   3. <JK-added> Data Management & Expose (DME / NONRTRIC-ICS) remains stable</JK-added>
      1. R1-DME Specification work is moving away from current implementation, may take significant effort to re-align. Currently resources are not available.
   4. Working on A1 Service exposure over R1
   5. Sample rApp for demonstrating AI/ML training using KServe planning to review with AIMLFW project.
   6. Last 2 releases issues with A1 end point in Near-RT RIC
      1. Not sure of A1 compliance in Near-RT RIC
      2. developed work-around adapter to deal with discrepancy which allows integration. Need a regular integration test. Will work with INT to establish one.
   7. Descoping some old functionalities 
4. James Li INT
   1. 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.
5. Toshiaki Takahashi 
   1. discussing Tacker and SMO component interaction

07 Feb 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 JanaDavid Kinsey [AT&T]  

24 Jan 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

16 Jan 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

13 Dec 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 19 Dec 2023 cancelled. If it becomes needed we will need to ensure someone can open the bridge.

Wednesday 27 Dec 2023 cancelled.

Tuesday 02 Jan 2024 cancelled. If it becomes needed we will need to ensure someone can open the bridge.

Next RSAC meeting Wednesday 10 Jan 2024 

06 Dec 2023 

Use RSAC portion of next week SMO+RSAC (need to confirm with Seshu Kumar Mudiganti ) for rApp Mgmt Demo (20 minutes at end)

29 Nov 2023 

15 Nov 2023 

01 Nov 2023 

24 Oct 2023 

• F2F recap
• ES dataset: Alex Stancu has provided ES data snapshot for AI/ML project (Joseph Thaliath) to start ML model training

TIM data set representing the “Internet” usage from the network, for 2 months (Nov and Dec 2013, timestamps every 10 minutes) in our nexus: https://nexus3.o-ran-sc.org/#browse/browse:datasets

The data is parsed, meaning we pruned the voice and SMS usage, keeping only the Internet traffic. The values themselves for the usage are normalised to a value known only to TIM (assuring some anonymisation).

Other references:

• • • https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/EGZHFV
    • https://www.nature.com/articles/sdata201555

17 Oct 2023 

20 Sep 2023 

• ES data sets,Ultan.Kelly to provide recreated synthetic data set for ES; mtg with bimo fransiscus asisi to discuss the details week of Sept 28th
• NYCU deployed ArgoCD for a SMO CI/CD environment

• briefly summarized their work on the O-Cloud, SMO, and OSC Component deployment as follows for your reference:
  1. O-Cloud (Kubernetes): 
  Have built a multi-node O-Cloud on bare-metal and virtual machines, with and without leveraging StarlingX.
  2. OSC ONAP-based SMO (OSC IT/DEP Project): 
  Have also deployed OSC ONAP-based SMO on top of the multi-node O-Cloud, again with and without StarlingX.
  3. O-RAN Deployment Container: 
  To facilitate and speed up the deployment of ONAP-based SMO, we made a portable container image that contains necessity scripts, ansible books, and prebuilt Helm charts for ONAP-based SMO deployment.
  4. CD for ONAP-based SMO deployment: 
  Currently working on Argo CD GitOps for ONAP-based SMO deployment.

   
  • 1. O-Cloud: per your demo at the RSAC meeting a few weeks back, it’s a manual process to provision/install a multi-node O-Cloud. Is there a way to automate the process for a single-node or multi-node O-Cloud?
  • What is the target environment?
  • VM or physical servers
  • With/without Starlingx (more hard to automate)
  • Should we recreate an O-Cloud for each integration test?
  • 2. Per my understanding, the deployment from the it/dep repository of the SMO will just include the OSC non-RT RIC, but without the OSC OAM components
    • OSC OAM wiki also refers to it/dep repository for Kubernetes deployment.
  • The OSC OAM reuses ONAP components such as O1ves, ODL, ...
  • The id/dep repository contains ONAP helm charts for deployment of the OSC OAM components.
  • Deployment — oam master documentation (o-ran-sc.org)
  • 3. Do you have any plan to commit the code as part of the “O-RAN Deployment Container” to OSC to facilitate and speed up the deployment of SMO as suggested? What is it different from the current deployment mechanism as part of the it/dep repo?
  • The “O-RAN Deployment Container” is a walkaround solution to reduce helm chart building time.
  • The better one is that OSC hosts its helm chart repository on OSC Nexus.
  • 4. What’s the granularity of your existing CD for ONAP-based SMO deployment?
  • We use Argo CD to deploy it/dep ONAP-based SMO with helm charts on Kubernetes.
  • The ONAP helm chart is too large for the helm, so ONAP provides a script to solve this problem.
  • It is not straightforward to integrate Argo CD and this script to deploy ONAP components (OAM), we will present the details in the RSAC meeting
  • 5. It’s desired to set up an O-Cloud and then SMO on top of it as the CI/CD base for further OSC components onboarding. Do you happen to see that your existing work can serve this purpose for OSC?
  • CI: Should we rebuild the O-Cloud and the SMO for each integration test
  • CD: May use the Argo CD GitOps

bimo fransiscus asisi to upload the slides louis li  presented here

https://wiki.o-ran-sc.org/download/attachments/3604609/20230920-ONAP-based%20SMO%20Deployment%20with%20Argo%20CD%20-%20NYCU.pptx?api=v2

29 Aug 2023 

23 Aug 2023 

Energy Savings

• ONF - Proposal #1 use Viavi to synthesize the data
  • Requires OSC $ which are not available
• ONF - Proposal #2 use RANSIM and synthesize the data
  • How can we generate
  • Alex Stancu Will look at available TIM Snapshot data sets to find if there is one. Rittwik Jana We just need UL and DL throughput data per cell.
  • Martin Skorupski 3GPP data Cells have sectors. Is our data One sector, One Frequency, per cell. Or should we plan ahead for Frequency management. Rittwik Jana Each "Site" has two frequencies. 5 sectors, 1 coverage, 4 capacity which can be turned down when capacity is not required.
  • Prof Ray
    • They are looking at using Viavi RICTest to generate some data. They may have a topology that can be used. Will report back next week.

OSC Taiwan Lab Update:

1. We pushed slice-enabled implementation to the ODU repo.
2. Shared the system design and guideline of #1 to ODU PTL via email
3. TM500 power installation still ongoing
4. O-Cloud has an issue with refusing to establish SSH connection. Will discuss with Jackie(WR) but he is currently OOO

Sprint 1 Reports

• TOC Report Due - 09/14
  • End-to-End Call - Pairwise Testing James Li 
  • Lab Updates - James Li 
• TOC Report Due - 09/21
  • Disaggregated SMO Flows - N.K. Shankaranarayanan 
  • Onboarding and Orchestration - Seshu Kumar Mudiganti 
• TOC Report Due - 09/28
  • RIC Platform Enhancements - Thoralf Czichy 
  • Energy Savings - Alex Stancu

1. 15 Aug 2023 

09 Aug 2023 

Feature Updates:

Disaggregated SMO Flows 

Demo - O-Cloud & SMO Deployment (Yi-Fan Li)

• • • • • 2 Control, 2 Worker, 2 Storage

Onboarding and Orchestration

Tacker Update (Toshiaki Takahashi )

RICPLT Feature Planning (Thoralf Czichy )

• • • • E2 Enhancements w/Conflict Management
      • A1 Enhancements 
      • xApp Deploy/Undeploy
      • Native IPv6 support

Deferred to Next Agenda:

Energy Savings E2E (Rittwik Jana , Alex Stancu )

ONF Collaboration

E2E Call Flow

Pairwise XTesting (James Li )

Lab Integration

OAI Collaboration

Bedminster Update (David Kinsey [AT&T] )

26 Jul 2023 

AIML - Joseph Thaliath 

• Generic Training Pipeline
• Advanced Feature Selection
• Automated Testing of AIMLFW
• Use Case Integration w/ Non-RT and Near-RT RIC
  • Can the project  use the RICAPP EnergySavings App
  • Aligns with Feature 2
• Code Refactoring (project internal)

Feature 2 - N.K. Shankaranarayanan 

• RICAPP - ES rAPP
• AIML - rApp Registration/Training
• Non-RT RIC - DME for Training; Data Publisher ; Kafka consumer
• OAM - CM; PM Schema
• SMO - VES using JSON to Kafka (Publisher)
• ODU-High - Netconf Server (CM); VES producer 

Feature 5 - James Li 

• INT - Pairwise Testing (work with participants from Feature 2)

12 Jul 2023 

I planning

• OSC + OAI interactions

• n/w lab interconnection
     (Phase 1)
     - Bedminster NJ lab operation mid Oct
     - Taiwan lab, TM500 O-DU integration, OAI-CU with OSC DU still ongoing integration test
     - CA lab
     - COSMOS lab OTIC
     (Phase 2, after I rel.)
     - POWDER lab OTIC+PAWR...
     - Northeastern uni lab (Coliseum)

• need an IP assignment network plan (OAM, CP, UP are internal to each lab currently; Can we interconnect all planes across all labs?)
         - David/Rich/Ajay Bedminster lab rep
         - Bimo, Taiwan lab rep
         - James Li CA lab rep
         - Martin/Ivan COSMOS lab rep
         - [AI] bimo fransiscus asisi Bimo to come up with rough n./w plan
             - stand up an e2e phone/data call in 1 lab 

• timeline
      - something e2e integrated up by end of Sept

• use cases
       1. e2e orchestration NF onboarding with placement/homing in 1 lab, across multiple labs [Seshu]
           - onbaoarding IMS, deploy DMS, O1 health and registration of CNF, how to add AI/ML SMOF?, 
           - Radisys O-CU CNF image as an example NF (SMO orchestrated); TM-500 not needed
           - gaps: 
           - risk: need to get candidates inside OSC and outside orgs [ONAP,...]
       2. Document Disaggregated SMO draft call flows identified from OSC as a contribution to WG1 [Shankar]
           - focus on flows and interactions between SMOFs (e.g., with energy savings)
           - what dependencies do we have?
       3. Policy SMOS/F? [defer to J rel.]
           - bring policy out to a centralized place
           - A1 policy vs SMO policy
       4. Can we discuss with Sunil on an energy savings app? [Sunil, Start in I], Tue RICAPP call
           - carrier RF on/off intermittent
           - cloud energy savings (C/P state reconfiguration)
       5. Establish an E2E call session with OSC components [James]
           - what is needed to stand up an e2e data session? UE -> RAN -> CORE -> OTT

• workplan/timeline 
       - I rel. timeplan refer to wiki

12 Jul 2023 

28 Jun 2023 

20 Jun 2023 

18 Jun 2023 

06 Jun 2023 

31 May 2023 

Japan F2F OSC demo preparation

Demo Suggestions from O-RAN Office (Zbynek):

For demos in Osaka (in case of pre-recorded videos) I would like to share a few suggestions aiming to improve the delivery of messages to the audience:

• • Make the videos rather short (2-3’) – attendees to F2F meetings may not want to spend long time in front of a screen, as the F2F agenda is very busy
  • If possible, include schemes/charts to visualize the demo scope in an easy way
  • Make the video in high quality to look good at a large screen from close look
  • Display each demo title clearly during the whole video (someone who comes in the middle of a demo could still understand what it is)
  • If possible, provide captions for the voiceover (or at least a word document with the voiceover text for postprocessing) – the sound of the screens may not be possible to be too loud and reading subtitles could help understanding

Would any postprocessing be required from O-RAN Office side, for the Osaka demo videos?

Note: For the demos that were shown in Madrid (Oct 2022), O-RAN office arranged adding demo titles to the screen and some further postprocessing to allow playing the videos in a loop. In case any assistance needed for Osaka demos, we would need the videos in advance – the postprocessing takes some days…

General note: If I recall the way OSC demos were presented in Madrid, Oct 2022, in my opinion – frankly – the content of the demos wasn’t easily digestible in the way it was presented. The videos were long (10+ minutes), rather poor quality, sound was hard to understand (and couldn’t be played loud to avoid disturbing the networking space). As O-RAN office could observe, not that many people looked at them. Hence the above suggestions to improve the presentation and delivery of desired messages.

Demos:

    Demo #1 - NTUST: Slice-enabled xApp control ODU Scheduler fransiscus bimo  

    Demo #2 -  NTUST - RIC Test with KPI-Mon

     Demo #3 - RIC E2 Reset

Japan Session Planning

     WG2, WG3, WG6, WG1 = 1 hour session

           Co-Chair or Work Item Rapporteur if associated with a work-item

     3 Questions from each PTL that would help the project. Questions should be targeted for a specific WG or WI team to answer.

23 May 2023 

 17 May 2023

• Demo/Discussion of CAPIF-based Service registry/discovery. The 3GPP CAPIF approach seems to be gaining traction as a basis for R1-SME, and we would like to show the progress we have made with our implementation. Since R1-SME (and SME in general) cross cuts several SMO-related projects
  
  • Slides: 20230517 - OSC NONRTRIC - CAPIF ServiceRegistry+Discovery.pdf
  • Video Hi-Res: 20230517 - capifdemo-hires.mp4
  • Video Lo-Res:  20230517 - capifdemo-lowres.mp4
• Demonstrate ASD-based LCM for CNFs using ONAP CNFM. The function, originally from the ONAP SO project, is used in standalone mode without the need for the rest of SO, A&AI or SDC. While this demo is quite SMO/NFO-specific I think it would also be of interest to the wider OSC community 
  • Slides: 20230517 - OSC NONRTRIC - ASD+SO-CNFM.pdf
  • Video Hi-Res: 20230517 - cnfmdemo-hires.mp4
  • Video Lo-Res: 20230517 - cnfmdemo-lowres.mp4

25 Apr 2023

RSAC mtg

O-DU high tests continuing in NTUST lab

bimo fransiscus asisi to reach out to Jon Zhang WR to help install a simple example NF and O-CU in NTUST O-Cloud; 

https://zoom.us/rec/share/7tJq7uzUmgzELk8h5Yu1TPSuPLspaWgKZ9SQaPyK45Bc5tYXpiDSQoW_BEa4Q4eQ.iHK-ayWJGm16aciT

19 Apr 2023 

Ocloud-operator.pdf

The agenda of this slides is to give a brief intro to Nephio.

Explain what and how K8s operator works.

Use of a K8s operator in the automation through Gitops.

Slide 20, depicts the different ways of integrating the operator with other open source solutions, this is NOT to promote using all of them together, but to show how and what part of the solution is being tackled by each of them and a possible way to re-use the O-cloud operator across them.

Andrea Buldorini: SMO Decomposition and how that applies to OSC

AP: Formalize NFO/FOCOM Use Cases for "H" for submittal to WG1; assigned to David Kinsey [AT&T] 

Shankar: Open-Source Harmonization with OSC

AI: Ankit Barve  requesting NTUST lab to revert to old lab so that O-DU high testing can progress. Integration testing is stalled for the moment due to ATT lab's unavailability. Dennis to ask Prof Ray and Bimo (bimo fransiscus asisi) and report back to RSAC.

AI: Ankit Barve  requesting O-DU Low PTL (Lvfarias (Deactivated)) for new release s/w version 22. O-DU high is currently using version 21 of O-DU low s/w. 

Timo Perala (ONAP requirements co-chair) provided an update on ONAP projects that are related to OSC.

AI: Timo to work with N.K. Shankaranarayanan, John Keeney (Ericsson EST) and Martin Skorupski  to come up with a list of projects that have synergies/touchpoints with OSC

AI/ML Deployment Options

• Separate Project
  • It has integration touch points with several projects
  • inside one may cause neglecting others (NonRTRIC, RICAPP, RICPLT)
  • Clear boundaries need to be defined to ensure non-overlapping scope.
  • Propose separate project - Avinash will work project description containing details articulated by John-Paul and Thoralf:
    • John-Paul Lane: If we decide the AI/ML proposal should be in its own dedicated project, we need a project proposal which TOC can review and vote on. As John Keeney (Ericsson EST) has pointed out, understanding scope of the project, its ambition and how it interacts with other projects is key input to the proposal.
    • Thoralf Czichy : in Order to define the scope in more detail…
      • (1) discuss data architecture (data flows)
      • (2) overlap in model manegement and r/xApp LCM
      • (3) define interfaces with existing projects
      • (4) define an example set of r/xApps that are being developed in parallel as a proof of concept
    • From John-Paul Lane: Some pointers to creating a new project proposal are included here Seed Code Contribution/ New Project Proposal Process (DRAFT) Also, it is interesting that there is an attempt to define when a new project can / should be created. There are examples of new project proposals which have been presented to TOC previously. Maybe @Mahesh could share the SMO proposal? Or if there are others they could be shared too.
• If inside existing which one
  • No Good fit
  • Would require a clear integration vision

Release "G" Feature Planning

• RICPLT - Deferred to post project meeting
• SMO
  • Integration with ODU for PM Reporting
  • TACKER to deploy CNF or VNF to be selected later
• RICAPP - Deferred
• SIM - Deferred

Lab Status

• TUWU

Lab update

• OTF integration ongoing. Bringing up a simple rApp using OTF (James Li, John Keeney)
• Nokia Front haul gateway configuration plan and ETA? Need to close this item asap. 
• TM500 availability
• PTP installation and configuration. Need to close this item. 

Meeting recording

• https://zoom.us/rec/share/MFXpM1wTR3ukFLVa7RkhFPJn_6y2d9H7hoti-z4FT_V5ITvYP-x-tjKIQQ-nCWEd.v_Z6OIflw9iHK8rG

Lab update

• OTF integration in Duplex O-Cloud (Alex C, David K, James Li, Bin Yang)
• Template file preparation for O-CU (Ankit Barve )
• PTP installation and configuration (Rich Wright ATT, David Kinsey [AT&T] )

Lab Status

• NJ- David IXR received, PTP-GM still an issue.
• CA - James (Software Centric)
• TU - Working with James

"E" Release Status

• RICAPP
• RIC
• ODU-H/ODU-L?
• OAM - Alex Stancu Model Complete
• SIM - Alex Stancu Updating Simulator
• SMO - Mahesh Jethanandani Disaggregated VES Commited, DMaaP Adapter out for review
• NONRTRIC - Need to reach out to John Keeney (Ericsson EST) for Status
  
  • Issues around the events and actions not being available yet.
  • Concern on testing/availability of SMO's new Kafka->DMaaP -API-adapter.
• INF

"F" Release Planning

• Per Project Release OTF Demo
  • RICAPP
  • RIC
  • ODU-H/ODU-L?
  • OAM
  • SIM
  • SMO
  • NONRTRIC
  • INF

O1 CR Status

• Rationale presented in O1 and RSAC.

NJ OSC Lab

• Waiting on IXR to be received
• Long cable will be shipped separate
• Ken will check to see if Block House installation of PTP-GM will be too far, estimating to be 100M from the lab.
• David Kinsey [AT&T]to send Lab editable diagram to Bimo.

Taiwan OSC Lab

• Nov 10 working with Viavi for SW License
• Integrate near-RT RIC/ODU-H: Complete
• Still working on RU Simulator planning for EOY
• Still having troubles logging into the TM500 in NJ

ODU-H

Integration Testing

• new PTL James Li

Reviewed Slicing End-to-End call flows presented by Former user (Deleted). Need verification from Viavi on pre-configuration of Slices within Core and UE simulator to request admission to a Slice.

Reviewed VES Project to EPIC list presented by David Kinsey [AT&T], need to work on iteration and resource mapping. Need OAM, SMO, and SIM PTLs

Discussed PTP Grand Master availability in the lab. David Kinsey [AT&T] to reach out to Nokia for status on FHG and how it provides/interfaces to PTP. E-mail sent today.

Meeting Held for discussion on Release "E" Disaggregated VES

Reviewed proposal and discussed options. No Conclusions yet as this was more informatory. Next Meeting will try to work on specific deliverables by project.

The attached presentation includes comments and on-going work between David Kinsey [AT&T] and Martin Skorupski which will be reviewed with the larger team at the next RSAC call.

Meeting recording to be listed to the right once it is available.

Went through Release "D" Flow:

• ODU-High still working a segmentation fault but have sent one message to O-DU low and should be enough to verify ODU-Low to O-RU
• Other Messages to follow working for UE Attach
• O-CU binary has been delivered to lab next step is to integrate with ODU-High and Core Simulator
• Once all these are done should be able to UE attach
• For ODU-High to SMO verified PNP VES will trigger netconf hello
• Simple Yang will be provided by Martin Skorupski which allows control of the link
  • Please see
    • wiki: Use case driven YANG modules for O-DU

    • Jira Legacy
      server System Jira serverId 3122c0e4-6090-3a7d-9725-8b5a32a8eaeb key ODUHIGH-322

    • gerrit: https://gerrit.o-ran-sc.org/r/c/scp/oam/modeling/+/5870
    • email: https://lists.o-ran-sc.org/g/toc/topic/api_modification_process/81994146?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,81994146
• near-RT RIC will get the O-DU ID and send the change state to "ACTIVE".
• David Kinsey [AT&T]took an action to get an OTF/INT project representative for the RSAC.

Meeting recording listed to the right.

Went through Release "D" Control Loop:

• Alignment of DMaaP Topics across projects
• Confirmed proposed YANG for O-DU is being analyzed by the O-DU team, should have an answer by next weeks call.
• Confirmed Config was sent to O-RU team, ODU Team needs to know how to initiate pairwise testing
• Reaching out to contributors for E2SIM modifications for Traffic Steering Use case
• David Kinsey [AT&T]will Reach out to OTF team for OTF E2SIM integration at the same time
• David Kinsey [AT&T] will work with Former user (Deleted) to work with Taiwan University to see how best to use them for Integration Project. They likely will not have a FHG in their environment and therefore are missing O-DU functionality for Hybrid or Hierarchical support models to the O-RU.
• SMO discussion was deferred as Mahesh had another meeting commitment. Nothing major pending.

Former user (Deleted)to share Config spreadsheet to Ken Trudgeon (O-DU--O-RU interactions

Mahesh Jethanandani Review recording for APP onboarding schema (from David K) for D rel implementation

Discussed RU failure recover use case

Zhe Huang (Felix) to provide DHCP and CA server in OSC lab to bootstrap RU startup

Viavi to check steps 1-8 in O-RU startup in 2. ORU Startup

Viavi to check steps26-27 in O-DU startup re Alarm subscription in 3. ODU Startup 

Former user (Deleted)to check steps 12-23 in 3. ODU Startup – implementation task

Discussed RU failure and recovery use case (ppt attached)

Former user (Deleted) to create call flow for use case

Discussed O1/A1 use case for Dawn

Image ModifiedImage Modified

Intel servers configured in OSC lab for O-DU testing

Intel and Radisys installing DU-low and DU-high s/w this week; SCTP libraries need to be installed; Former user (Deleted)to reach out to Rich for help

Ganesh Shenbagaraman checking internally for compatibility for O-CU s/w contribution from Radisys (closed source)

Ron Shacham to provide simulated trace files to Alex Stancu  from Viavi sim into SIM repo  

Former user (Deleted) David Kinsey [AT&T] to draft preliminary plan for D release;  

Requesting All PTLs to start thinking about D release work epics and Cherry flow over items

• Discussion regarding O-CU MVP requirements for OSC
  • Implement HO for traffic steering, defer E1 interface for Cherry
  • Ganesh Shenbagaraman to raise topic to TOC for 8/19
• Discussion regarding OSC and TIFG MVP requirements 
  • Slides from Eng Koo

TIFG-OSC meeting slides

• Discussion with Radisys on O-DU activity
• INF project installing OS and O-DU getting installed. Ganesh Shenbagaraman Sachin Srivastavato provide quick update on O-DU status
• Discussed about SMO project initiation and PTL election
• Discussed main challenges slide in OSC to be presented to EC by Jack Murray   huangjinri@chinamobile.com

  Start Time : Jul 28, 2020 09:03 PM

O-DU High status (PPT attached)

• O-DU and O-RU stub testing (Bronze maint.) (Zhimin Yuan (Deactivated) , Former user (Deleted) ); Have access to the box, waiting for Windriver to complete SW install before their SW can be installed
• KPIMON xAPP integration with Near-RT RIC (Matti Hiltunen , Ron Shacham, Eng Koo )
  • Working with Samsung and Near-RT RIC, problem with Subscription Mgr
  • E2SIM has Viavi Schema and has demonstrated flow, waiting on 10 minute playback file from Viavi.
  • Viavi indicates file wont be available until 7/24. Could work and lower risk with shorter file, Viavi will look into that.
• Cherry SMO Proposal (Martin Skorupski , Tracy Van Brakle )
  • Proposal presented
  • Discussion on external SMO open source alignment (John Keeney (Ericsson EST) )
  • Discussed possibility of sub-project instead of new project (John Keeney (Ericsson EST) )
• SMO LCM and Application Deploy Scenarios (Martin Skorupski )
  • LInk to recorded presentation available on OAM project meeting page. Separate link to also be added to Non-RT RIC page.

    
    

  • Start Time : Jul 21, 2020 08:50 AM

    
    

    
    

Sachin Srivastava Zhimin Yuan (Deactivated) to discuss on bronze maintenance release testing (P5 msg exchange, etc.)

Xiaohua Zhang to check for testing possibilities for DU-LOW and DU-HIGH at Windriver 

Former user (Deleted) Former user (Deleted) to check on OSC lab status for L1 stack  by 6/30

Eng Koo to check with Ken and Ultan on Viavi providing sim log files for TS scenario by 6/30

Eng Koo to share common config file IOT profile between O-RU, DU-Low and DU-high 

Common IOT profile 

Eng Koo to setup meeting with Former user (Deleted) Ron Shacham to discuss Viavi simulation parameters for traffic steering 

Sachin Srivastava Ganesh Shenbagaraman to setup meeting with Eng Koo to discuss Viavi testing with O-DU HIGH

Martin Skorupski to draw up some some slides on cherry release requirement for s/w mgmt of X-RAN RU to O-RAN RU

Alex Stancu to setup meeting with Ron Shacham for 4/13 on E2 simulator enhancement

• Setup meeting between TIFG, OSC and Viavi William DIEGO
• ONAP-ORAN harmonization and inputs to ONAP Guilan, John Keeney (Ericsson EST) David Kinsey [AT&T] to present one slide to TOC next week
• Matti Hiltunen to send John Keeney TS xApp policy details

Viavi's short term and long term proposal for OSC  

Bronze rel. – PTL reports from RICAPP, O-CU, ODU HIGH

O-CU

Viavi presented a range of simulators that will be valuable for OSC use case testing and validation. Slides - 

Action: Discuss in OSC TOC meeting regarding Viavi 

OSC and WG review meeting 1

Reviewed Epics

Start planning for Release B - Can we use JIRA for the planning phase in addition to the Word doc?

Move Release planning cadence to once a week. Alternate between evening and day every other week.

Where is the Integration and Test Environment? How do we set up the test env? Couple of possibilities. Check with Jack Murray

• Tlab (AT&T)
• OTIC (O-RAN Test and Integration Centre - Asia/Europe/North America (inter-connected)
• Windriver lab ?
• CMCC ?

Reviewed epics

• INT-A-F212 clarification added in annex for PNF registration
  • Need John Keeney (Ericsson EST) Martin Skorupski to develop use case design doc
• RICNRT-A-F10 for OSC  Rel A ?
  • Need John Keeney (Ericsson EST) and Tommy Carpenter to develop minimal use case
• INF-A-F01 epic clarification needed from Paul Carver
• INT-A-F013 - recruit Eliza Celenti to stand up OTF framework for Rel A
• RICAPP-A-F110 - UE Monitor for slicing
  • Jun Hyuk Song to provide clarification of this epic, UE-NIB, overlap with UE Manager xApp