/
Project meetings

Project meetings

Owned by Thoralf Czichy
Last updated: Nov 26, 2024 by abdulwahid.w

Meeting Info

RIC project meetings are open to the public and held on Tuesdays at 2pm UTC (winter) and 1pm UTC (summer).  World Time Zone Map

Zoom 1 Info:

UTC-timeevery 2nd Tuesday, check from calendar

https://zoom.us/j/9644759813

New York (EDT / UTC-4 during DST (-5 in the winter))every 2nd Tuesday, check from calendar+1 669 900 6833 // +1 646 558 8656 // 855 880 1246 (Toll Free) // 877 369 0926 (Toll Free)
Paris (CEST / UTC+1 in the winter (+2 during DST))every 2nd Tuesday, check from calendar+33 7 5678 4048 // +33 1 8288 0188 // 805 082 588 (Toll Free)
Beijing (CST / UTC+8)every 2nd Tuesday, check from calendar+86 10 87833177 // +86 10 53876330 // 400 616 8835 (Toll Free) // 400 669 9381 (Toll Free)
Tokyo (JST / UTC+9) every 2nd Tuesday, check from calendar+81 524 564 439 // +81 3 4578 1488 // 0 800 100 5040 (Toll Free)
Helsinki  (EEST / UTC+2 in the winter (+3 during DST))every 2nd Tuesday, check from calendar

+358 341092129

Delhi (IST // UTC +5:30every 2nd Tuesday, check from calendarTODO


Other international numbers

World Time Zone Map

International numbers available: https://zoom.us/u/acyy3hylQi

2024-11-26

Recording: meeting recording

  1. NearRT RIC's comparision: RIC_Comparison_Meeting_1.pdf Near-RT RIC Comparison - Draft 1.pdf
  2. 26.11: To organise projetc meeting on mondays as its suitable for most.
    1. 26.11: hw-python and hw-go xapp needs to updated. Last commit is Dec 2022.
    2. 26.11: RIC subscription response is not working between submgr and xapp with hw-go xapp. connection refused error. RMR service name is binding with REST port (8080).
    3. 26.11: RIC subscription response is not working between submgr and xapp with hw-rust xapp. http error code=404,most likley xapp doesn't implement.
    4. 26.11: Jira Issues to be created for b) and c)
    5. 26.11: Need committers for hw xapps, Naman left Samsung and Shubash is busy with other work. Sunil(HCL) to check with his team.
    6. 26.11: Sunil was asking if near Real time RIC support A1 for AI modelling
    7. 12.11: e2sim node fails when trying to send an indication due to ASN.1 sanity check failure
    8. 12.11: RAN_FUNC_ID check fails with latest E2 sim. Explictly needed to export this variable.
    9. 12.11: crictl runtime is not able to pull the image due to tls check in https.
  3. 27.08 : influx 2.x in incompatible with current xapps. NRT RIC installation should install only influx 1.x version. Jira ticket to be raised by Sunil N.08.10: influx2.x works with the xapps, however with e2simulator there is some issue.  Sunil to check.
  4. 12.11: Demo by Ashish Singh (Capgemini) on Conflict Manager
  5. 12.11: Sunil requested for security (IPSec) in RIC PLT. Currently this is not implemented.

2024-11-12

Recording: meeting recording

  1. NearRT RIC's comparision: RIC_Comparison_Meeting_1.pdf Near-RT RIC Comparison - Draft 1.pdf
    1. 12.11: e2sim node fails when trying to send an indication due to ASN.1 sanity check failure
    2. 12.11: RAN_FUNC_ID check fails with latest E2 sim. Explictly needed to export this variable.
    3. 12.11: crictl runtime is not able to pull the image due to tls check in https.
  2. 27.08 : influx 2.x in incompatible with current xapps. NRT RIC installation should install only influx 1.x version. Jira ticket to be raised by Sunil N.08.10: influx2.x works with the xapps, however with e2simulator there is some issue.  Sunil to check.
  3. 12.11: Demo by Ashish Singh (Capgemini) on Conflict Manager
  4. 12.11: Sunil requested for security (IPSec) in RIC PLT. Currently this is not implemented.

2024-10-08

Recording: meeting recording

  1. NearRT RIC's comparision: RIC_Comparison_Meeting_1.pdf Near-RT RIC Comparison - Draft 1.pdf
  2. 27.08 : influx 2.x in incompatible with current xapps. NRT RIC installation should install only influx 1.x version. Jira ticket to be raised by Sunil N.

    08.10: influx2.x works with the xapps, however with e2simulator there is some issue.  Sunil to check.

2024-09-24

No attendees for this day's meeting.

2024-09-10

Recording: meeting recording

  1. Agenda for "K" release :
    • E2 Conflict management between xApps:  Commits raised, to review and merge.  
    • 10.09.2024: Gunja Rastogi confirmed to give a demo on 24.09.2024. The commits are still not merged.
    • scale-in and scale out using K8S operators
    • Enhancements to XApp Rust Framework for Next Release 
    • 10.09.2024: Abhijit's participation is very very limited due to new work.
  2. 27.08 : influx 2.x in incompatible with current xapps. NRT RIC installation should install only influx 1.x version. Jira ticket to be raised by Sunil N.

                      08.10: influx2.x works with the xapps, however with e2simulator there is some issue. 

  1. RICAPP agenda: RICAPP Meetings.

2024-08-27

Recording: meeting recording

  1. Agenda for "K" release :
    1. E2 Conflict management between xApps:  Commits raised, to review and merge.

    2. scale-in and scale out using K8S operators

    3. Enhancements to XApp Rust Framework for Next Release 
  2. 27.08 : influx 2.x in incompatible with current xapps. NRT RIC installation should install only influx 1.x version. Jira ticket to be raised by Sunil N.
  3. RICAPP agenda: RICAPP Meetings.

2024-08-13

Recording: meeting recording

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. Compliant
  2. every second time: Review code coverage stats and blocker code smells
    1. We take a look at the two links in the beginning of this page: Code coverage reports..
    2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
    3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link

    1. RIC-1062 Error while running hw-go and Bouncer xApps 04-06: Sunil to check

    2. RIC-1057 gNB unable to connect during high amount of Subscription Requests - Assigned to Amit Mishra - able to reproduce this issue, some timing issue to reduce to 2s. AbdulWahid to check with Aditya on the 10s timer in E2Manager. 02-07: Review request raised.
    3. RIC-1056 Crashing e2mgr after sending high amount of Subscription Requests - Assigned to Dhiraj
    4. RIC-1055 Unrestricted Registration of RMR Routing Information by xApp
    5. RIC-1054 Kong pod is in crash loopback due to Ingress controller container is not coming up in 1.28 k8s installation- mostly needs kongversion upgrade. Abhijit provided hints.
    6. RIC-1051 Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - hwgo is gettong onboarded, still some issues with kpimon-go. 04-06: No issues seen with latest version of xapps.
    7. RIC-1047 crash in E2T metric increment code - WIP- Unable to reproduce the issue. 04-06:possible solution identified. Amit can raise the review issue.
                      02-07: Still unable to reproduce. Will commit the possible solution.
    8. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
    9. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  - code already committed. Wahid to check with Aditya for merging. 02-07: Followup with Aditya to give +1.
    10. RIC-1043 Crash in E2T buildPrometheusList Function  - WIP - 02-07:  Unable to reproduce the issue.
    11. RIC-1042 Can't register xApp
    12. RIC-1031 Data model is not compliant with latest A1 spec → Naman (02-07: planned to start work in next week, )
    13. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
    14. RIC-1025 memory leak in routing manager
    15. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

    16. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

    17. RIC-1015 e2t too High default message size. → Nokia

    18. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

    19. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

    20. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
    21. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
    22. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    23. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
    24. RIC-915 dms_cli for installing xapp not working (raised by James)
    25. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    26. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    27. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    28. RIC-894 long idle period (days) causes RMR connection breaks
    29. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    30. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    31. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
    32. RIC-837 RMR is not forwarding messages from E2T to E2M
    33. RIC-835 → 2021-12-07 no news from Viktor
    34. fixed: 
  4. James: updates?
    1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
    2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
    3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
    4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
    5. 2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.
    6. 2024-03-26: Unavailable today.
    7. 2024-04-23:
    8. 2024-05-07: Updated on ORANSC summit. It was well received.
    9. 2024-05-21: No new updates this time.
    10. 2024-07-16: Moved to different group.
  5. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
    2. 2024-02-13,2024-03-12,2024-03-26,2024-04-09,2024-04-23,2024-05-07, 2024-05-21,2024-07-16: no news
  6. Sunil updates (subteam-h)?
    1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
    2. 2023-11-07: Not in the call today
    3. 2023-11-21: no updates. Difficult to find engineers working on this.
    4. 2024-01-16: demo of xApp project additions in I release → Next time
    5. 2024-01-16: re-evaluating RIC platform Jira items
    6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
    7. 2024-02-13: working on RIC subscription delete testing 
    8. 2024-03-12: Implementation completed, facing issues in code submission.
    9. 2024-03-26: Working on RIC-1049, documentation will also be made - Done
    10. 2024-03-09: Absent
    11. 2024-04-23: Not much updates.
    12. 2024-05-07: RIC-1045/RIC-1049 /RIC-1052/RIC-837 are completed. RIC-829 needs code commit.
    13. 2024-05-21:  unavailable
    14. 2024-07-16: Sunil asked on the future spec integrations in RIC side. need to do "K" release planning.
  7. Subhash/Naman updates (subteam-s) ?
    1. 2023-12-05: Naman gave an update on status of Samsung items
    2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
    3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
    4. 2024-03-12: RIC-1031 - Needs more time to complete, To start working on  A1 mediator integration with Non RealTime RIC
    5. 2024-03-26:  Continuing on RIC-1031, Working on RIC-1048 (analysis on RMR scaling, design to be worked upon)
    6. 2024-03-09,2024-04-23,2024-05-07,2024-05-21,2024-06-04: Not available
    7. 2024-07-02: Working on RIC-1027
    8. 2024-07-16: Not present
  8. Abhijit updates (subteam-ag) ?
    1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
    2. 2024-01-16, 2024-01-30: No news.
    3. 2024-02-13: continues work on xapp framework rust, incl. metric support
    4. 2024-03-12: No news.
    5. 2024-03-26: Implementation done , testing pending for xapp framework rust, incl. metric support
    6. 2024-03-09: Not available.
    7. 2024-03-23: Interested to work on 1056,1057 in coming weeks, after rust framework is tested. RIC-1006 done, RIC-1007 move to K, RIC-1028- will be taken up next. To give demo on rust-framework 07-05-2024.
    8. 2024-05-07:  RIC-1041 is done. Demo was given for metrics support in xapp-frame-rust that has default RMR Rx/Tx counters.
    9. Video for the demo added.
    10. 2024-05-21,2024-06-04: Unavailable
    11. 2024-07-02: Integration testing of xapp-rust fwk and other issues(feature parity go fwk)
    12. 2024-07-16: unavailable
  9. Cap Gemini updates (subteam-cg)? 
    1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
    2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
    3. 2024-03-26,2024-03-09,2024-04-23,2024-05-07,2024-05-21,2024-06-04:2024-07-16 unavailable.
  10. Himanshu (subteam-gs) would like to work on RIC-963
    1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
    3. 2024-03-12:  Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working,   length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr. Good to raise JIRA.
    4. 2024-03-26: Assigned RIC-1043,1044,1047. Will provide updates next week.  length of IE > 1024 in RIC_ACTION_DEFINITION causing issue in submgr - Sandeep to check if Jira needs to be raised. RIC-1051- Himanshu looking into it.
    5. 2024-03-09:  No updates on RIC-1043,1044,1047. Amit will contribute to this project.
    6. 2024-04-23: Not present
    7. 2024-05-07: RIC-1044 code committed, to be merged.RIC-1047 WIP, issue not reproducible. Possible issue identified, but need to reproduce. e2sim has some dependency on ubuntu 18.04 version(gcc) Issue to be raised for this also. Another Issue : Himanshu to raise issue related to RIC-1052
    8. 2024-05-21: Issue with e2sim identified and corrected (SIM-117), Issue related to 1052 , additional steps added by Amit and now stands closed.
    9. 2024-07-16: unavailable
  11. Dhiraj:
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.
    3. 2024-01-26, 2024-04-09,2024-04-23: no news.
    4. 2024-05-07: Dhiraj not representing Rakuten anymore.
    5. 2024-05-21,2024-06-04: Unavailable
  12. Alexandre (subteam-utfpr)
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
    3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
    4. 2024-03-26,2024-04-09,2024-04-23: No news.
    5. 2024-05-07: Via mail responded to working on bug fixes in xapp-frame's. xapp-frame-cpp working well, still to make it work on xapp-frame(go) and xapp-frame-py
    6. 2024-05-21,2024-06-04: Unavailable
    7. 2024-07-02: Working on xapp-frame-cpp(changes in subscrition,sdl registrations), current RMR issues take a back seat as they are low prio.
    8. 2024-07-16: unavailable
  13. Nokia (subteam-n)
    1. RIC-997 postponed to J
    2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
  14. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
    1. 2024-03-26: New nomination awaited from TOC.
    2. 2024-04-09: The presentation of NEAR RT RIC would be handled by someone else(not James)
    3. “Analysis of Opensource Near-RT RICs – A comparative study”. Mainly, Intern will take the Specs, and analyse the available opensources of Near-RT RICs and prepare a report. I wanted to know your thoughts and interest in mentoring this activity. 
    4. 2024-07-02: Interns from Brazil already workin on it. Preliminary reports are available in Portugese language. This is WIP.
  15. J release
    1. 2024-02-13: Naman's input
      1. no Jira tickets yet, but woudl like to focus on 
        1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
    2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
      1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
    3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
      1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
      2. committed items only: all teams (committed) and all teams (committed + tentative).
      3. items that are known to require work, but are currently not in J release: link,  to include k8s version upgrade, ubuntu OS version, clean up of pending issues.
    1. input for release candidates: leftovers and generally open items, RSAC
    2. Sprint dates
      1. Sprint J release dev sprint 1: Feb-19 to Mar-10
      2. Sprint J release dev sprint 2: Mar-11 to Mar-31
      3. Sprint J release dev sprint 3: Apr-1 to Apr-21
      4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
      5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
  16. RICAPP agenda: RICAPP Meetings.

2024-07-16

Recording:  zoom meeting

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. Compliant
  2. every second time: Review code coverage stats and blocker code smells
    1. We take a look at the two links in the beginning of this page: Code coverage reports..
    2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
    3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link

    1. RIC-1062 Error while running hw-go and Bouncer xApps 04-06: Sunil to check

    2. RIC-1057 gNB unable to connect during high amount of Subscription Requests - Assigned to Amit Mishra - able to reproduce this issue, some timing issue to reduce to 2s. AbdulWahid to check with Aditya on the 10s timer in E2Manager. 02-07: Review request raised.
    3. RIC-1056 Crashing e2mgr after sending high amount of Subscription Requests - Assigned to Dhiraj
    4. RIC-1055 Unrestricted Registration of RMR Routing Information by xApp
    5. RIC-1054 Kong pod is in crash loopback due to Ingress controller container is not coming up in 1.28 k8s installation- mostly needs kongversion upgrade. Abhijit provided hints.
    6. RIC-1051 Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - hwgo is gettong onboarded, still some issues with kpimon-go. 04-06: No issues seen with latest version of xapps.
    7. RIC-1047 crash in E2T metric increment code - WIP- Unable to reproduce the issue. 04-06:possible solution identified. Amit can raise the review issue.
                      02-07: Still unable to reproduce. Will commit the possible solution.
    8. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
    9. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  - code already committed. Wahid to check with Aditya for merging. 02-07: Followup with Aditya to give +1.
    10. RIC-1043 Crash in E2T buildPrometheusList Function  - WIP - 02-07:  Unable to reproduce the issue.
    11. RIC-1042 Can't register xApp
    12. RIC-1031 Data model is not compliant with latest A1 spec → Naman (02-07: planned to start work in next week, )
    13. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
    14. RIC-1025 memory leak in routing manager
    15. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

    16. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

    17. RIC-1015 e2t too High default message size. → Nokia

    18. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

    19. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

    20. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
    21. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
    22. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    23. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
    24. RIC-915 dms_cli for installing xapp not working (raised by James)
    25. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    26. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    27. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    28. RIC-894 long idle period (days) causes RMR connection breaks
    29. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    30. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    31. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
    32. RIC-837 RMR is not forwarding messages from E2T to E2M
    33. RIC-835 → 2021-12-07 no news from Viktor
    34. fixed: 
  4. James: updates?
    1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
    2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
    3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
    4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
    5. 2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.
    6. 2024-03-26: Unavailable today.
    7. 2024-04-23:
    8. 2024-05-07: Updated on ORANSC summit. It was well received.
    9. 2024-05-21: No new updates this time.
    10. 2024-07-16: Moved to different group.
  5. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
    2. 2024-02-13,2024-03-12,2024-03-26,2024-04-09,2024-04-23,2024-05-07, 2024-05-21,2024-07-16: no news
  6. Sunil updates (subteam-h)?
    1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
    2. 2023-11-07: Not in the call today
    3. 2023-11-21: no updates. Difficult to find engineers working on this.
    4. 2024-01-16: demo of xApp project additions in I release → Next time
    5. 2024-01-16: re-evaluating RIC platform Jira items
    6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
    7. 2024-02-13: working on RIC subscription delete testing 
    8. 2024-03-12: Implementation completed, facing issues in code submission.
    9. 2024-03-26: Working on RIC-1049, documentation will also be made - Done
    10. 2024-03-09: Absent
    11. 2024-04-23: Not much updates.
    12. 2024-05-07: RIC-1045/RIC-1049 /RIC-1052/RIC-837 are completed. RIC-829 needs code commit.
    13. 2024-05-21:  unavailable
    14. 2024-07-16: Sunil asked on the future spec integrations in RIC side. need to do "K" release planning.
  7. Subhash/Naman updates (subteam-s) ?
    1. 2023-12-05: Naman gave an update on status of Samsung items
    2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
    3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
    4. 2024-03-12: RIC-1031 - Needs more time to complete, To start working on  A1 mediator integration with Non RealTime RIC
    5. 2024-03-26:  Continuing on RIC-1031, Working on RIC-1048 (analysis on RMR scaling, design to be worked upon)
    6. 2024-03-09,2024-04-23,2024-05-07,2024-05-21,2024-06-04: Not available
    7. 2024-07-02: Working on RIC-1027
    8. 2024-07-16: Not present
  8. Abhijit updates (subteam-ag) ?
    1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
    2. 2024-01-16, 2024-01-30: No news.
    3. 2024-02-13: continues work on xapp framework rust, incl. metric support
    4. 2024-03-12: No news.
    5. 2024-03-26: Implementation done , testing pending for xapp framework rust, incl. metric support
    6. 2024-03-09: Not available.
    7. 2024-03-23: Interested to work on 1056,1057 in coming weeks, after rust framework is tested. RIC-1006 done, RIC-1007 move to K, RIC-1028- will be taken up next. To give demo on rust-framework 07-05-2024.
    8. 2024-05-07:  RIC-1041 is done. Demo was given for metrics support in xapp-frame-rust that has default RMR Rx/Tx counters.
    9. Video for the demo added.
    10. 2024-05-21,2024-06-04: Unavailable
    11. 2024-07-02: Integration testing of xapp-rust fwk and other issues(feature parity go fwk)
    12. 2024-07-16: unavailable
  9. Cap Gemini updates (subteam-cg)? 
    1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
    2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
    3. 2024-03-26,2024-03-09,2024-04-23,2024-05-07,2024-05-21,2024-06-04:2024-07-16 unavailable.
  10. Himanshu (subteam-gs) would like to work on RIC-963
    1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
    3. 2024-03-12:  Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working,   length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr. Good to raise JIRA.
    4. 2024-03-26: Assigned RIC-1043,1044,1047. Will provide updates next week.  length of IE > 1024 in RIC_ACTION_DEFINITION causing issue in submgr - Sandeep to check if Jira needs to be raised. RIC-1051- Himanshu looking into it.
    5. 2024-03-09:  No updates on RIC-1043,1044,1047. Amit will contribute to this project.
    6. 2024-04-23: Not present
    7. 2024-05-07: RIC-1044 code committed, to be merged.RIC-1047 WIP, issue not reproducible. Possible issue identified, but need to reproduce. e2sim has some dependency on ubuntu 18.04 version(gcc) Issue to be raised for this also. Another Issue : Himanshu to raise issue related to RIC-1052
    8. 2024-05-21: Issue with e2sim identified and corrected (SIM-117), Issue related to 1052 , additional steps added by Amit and now stands closed.
    9. 2024-07-16: unavailable
  11. Dhiraj:
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.
    3. 2024-01-26, 2024-04-09,2024-04-23: no news.
    4. 2024-05-07: Dhiraj not representing Rakuten anymore.
    5. 2024-05-21,2024-06-04: Unavailable
  12. Alexandre (subteam-utfpr)
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
    3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
    4. 2024-03-26,2024-04-09,2024-04-23: No news.
    5. 2024-05-07: Via mail responded to working on bug fixes in xapp-frame's. xapp-frame-cpp working well, still to make it work on xapp-frame(go) and xapp-frame-py
    6. 2024-05-21,2024-06-04: Unavailable
    7. 2024-07-02: Working on xapp-frame-cpp(changes in subscrition,sdl registrations), current RMR issues take a back seat as they are low prio.
    8. 2024-07-16: unavailable
  13. Nokia (subteam-n)
    1. RIC-997 postponed to J
    2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
  14. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
    1. 2024-03-26: New nomination awaited from TOC.
    2. 2024-04-09: The presentation of NEAR RT RIC would be handled by someone else(not James)
    3. “Analysis of Opensource Near-RT RICs – A comparative study”. Mainly, Intern will take the Specs, and analyse the available opensources of Near-RT RICs and prepare a report. I wanted to know your thoughts and interest in mentoring this activity. 
    4. 2024-07-02: Interns from Brazil already workin on it. Preliminary reports are available in Portugese language. This is WIP.
  15. J release
    1. 2024-02-13: Naman's input
      1. no Jira tickets yet, but woudl like to focus on 
        1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
    2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
      1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
    3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
      1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
      2. committed items only: all teams (committed) and all teams (committed + tentative).
      3. items that are known to require work, but are currently not in J release: link,  to include k8s version upgrade, ubuntu OS version, clean up of pending issues.
    1. input for release candidates: leftovers and generally open items, RSAC
    2. Sprint dates
      1. Sprint J release dev sprint 1: Feb-19 to Mar-10
      2. Sprint J release dev sprint 2: Mar-11 to Mar-31
      3. Sprint J release dev sprint 3: Apr-1 to Apr-21
      4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
      5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
  16. RICAPP agenda: RICAPP Meetings.

2024-07-02

Recording:  zoom meeting

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. Compliant
  2. every second time: Review code coverage stats and blocker code smells
    1. We take a look at the two links in the beginning of this page: Code coverage reports..
    2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
    3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link

    1. RIC-1062 Error while running hw-go and Bouncer xApps 04-06: Sunil to check

    2. RIC-1057 gNB unable to connect during high amount of Subscription Requests - Assigned to Amit Mishra - able to reproduce this issue, some timing issue to reduce to 2s. AbdulWahid to check with Aditya on the 10s timer in E2Manager. 02-07: Review request raised.
    3. RIC-1056 Crashing e2mgr after sending high amount of Subscription Requests - Assigned to Dhiraj
    4. RIC-1055 Unrestricted Registration of RMR Routing Information by xApp
    5. RIC-1054 Kong pod is in crash loopback due to Ingress controller container is not coming up in 1.28 k8s installation- mostly needs kongversion upgrade. Abhijit provided hints.
    6. RIC-1051 Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - hwgo is gettong onboarded, still some issues with kpimon-go. 04-06: No issues seen with latest version of xapps.
    7. RIC-1047 crash in E2T metric increment code - WIP- Unable to reproduce the issue. 04-06:possible solution identified. Amit can raise the review issue.
                      02-07: Still unable to reproduce. Will commit the possible solution.
    8. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
    9. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  - code already committed. Wahid to check with Aditya for merging. 02-07: Followup with Aditya to give +1.
    10. RIC-1043 Crash in E2T buildPrometheusList Function  - WIP - 02-07:  Unable to reproduce the issue.
    11. RIC-1042 Can't register xApp
    12. RIC-1031 Data model is not compliant with latest A1 spec → Naman (02-07: planned to start work in next week, )
    13. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
    14. RIC-1025 memory leak in routing manager
    15. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

    16. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

    17. RIC-1015 e2t too High default message size. → Nokia

    18. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

    19. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

    20. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
    21. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
    22. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    23. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
    24. RIC-915 dms_cli for installing xapp not working (raised by James)
    25. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    26. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    27. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    28. RIC-894 long idle period (days) causes RMR connection breaks
    29. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    30. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    31. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
    32. RIC-837 RMR is not forwarding messages from E2T to E2M
    33. RIC-835 → 2021-12-07 no news from Viktor
    34. fixed: 
  4. James: updates?
    1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
    2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
    3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
    4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
    5. 2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.
    6. 2024-03-26: Unavailable today.
    7. 2024-04-23:
    8. 2024-05-07: Updated on ORANSC summit. It was well received.
    9. 2024-05-21: No new updates this time.
  5. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
    2. 2024-02-13,2024-03-12,2024-03-26,2024-04-09,2024-04-23,2024-05-07, 2024-05-21: no news
  6. Sunil updates (subteam-h)?
    1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
    2. 2023-11-07: Not in the call today
    3. 2023-11-21: no updates. Difficult to find engineers working on this.
    4. 2024-01-16: demo of xApp project additions in I release → Next time
    5. 2024-01-16: re-evaluating RIC platform Jira items
    6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
    7. 2024-02-13: working on RIC subscription delete testing 
    8. 2024-03-12: Implementation completed, facing issues in code submission.
    9. 2024-03-26: Working on RIC-1049, documentation will also be made - Done
    10. 2024-03-09: Absent
    11. 2024-04-23: Not much updates.
    12. 2024-05-07: RIC-1045/RIC-1049 /RIC-1052/RIC-837 are completed. RIC-829 needs code commit.
    13. 2024-05-21:  unavailable
  7. Subhash/Naman updates (subteam-s) ?
    1. 2023-12-05: Naman gave an update on status of Samsung items
    2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
    3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
    4. 2024-03-12: RIC-1031 - Needs more time to complete, To start working on  A1 mediator integration with Non RealTime RIC
    5. 2024-03-26:  Continuing on RIC-1031, Working on RIC-1048 (analysis on RMR scaling, design to be worked upon)
    6. 2024-03-09,2024-04-23,2024-05-07,2024-05-21,2024-06-04: Not available
    7. 2024-07-02: Working on RIC-1027
  8. Abhijit updates (subteam-ag) ?
    1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
    2. 2024-01-16, 2024-01-30: No news.
    3. 2024-02-13: continues work on xapp framework rust, incl. metric support
    4. 2024-03-12: No news.
    5. 2024-03-26: Implementation done , testing pending for xapp framework rust, incl. metric support
    6. 2024-03-09: Not available.
    7. 2024-03-23: Interested to work on 1056,1057 in coming weeks, after rust framework is tested. RIC-1006 done, RIC-1007 move to K, RIC-1028- will be taken up next. To give demo on rust-framework 07-05-2024.
    8. 2024-05-07:  RIC-1041 is done. Demo was given for metrics support in xapp-frame-rust that has default RMR Rx/Tx counters.
    9. Video for the demo added.
    10. 2024-05-21,2024-06-04: Unavailable
    11. 2024-07-02: Integration testing of xapp-rust fwk and other issues(feature parity go fwk)
  9. Cap Gemini updates (subteam-cg)? 
    1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
    2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
    3. 2024-03-26,2024-03-09,2024-04-23,2024-05-07,2024-05-21,2024-06-04: unavailable.
  10. Himanshu (subteam-gs) would like to work on RIC-963
    1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
    3. 2024-03-12:  Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working,   length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr. Good to raise JIRA.
    4. 2024-03-26: Assigned RIC-1043,1044,1047. Will provide updates next week.  length of IE > 1024 in RIC_ACTION_DEFINITION causing issue in submgr - Sandeep to check if Jira needs to be raised. RIC-1051- Himanshu looking into it.
    5. 2024-03-09:  No updates on RIC-1043,1044,1047. Amit will contribute to this project.
    6. 2024-04-23: Not present
    7. 2024-05-07: RIC-1044 code committed, to be merged.RIC-1047 WIP, issue not reproducible. Possible issue identified, but need to reproduce. e2sim has some dependency on ubuntu 18.04 version(gcc) Issue to be raised for this also. Another Issue : Himanshu to raise issue related to RIC-1052
    8. 2024-05-21: Issue with e2sim identified and corrected (SIM-117), Issue related to 1052 , additional steps added by Amit and now stands closed.
  11. Dhiraj:
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.
    3. 2024-01-26, 2024-04-09,2024-04-23: no news.
    4. 2024-05-07: Dhiraj not representing Rakuten anymore.
    5. 2024-05-21,2024-06-04: Unavailable
  12. Alexandre (subteam-utfpr)
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
    3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
    4. 2024-03-26,2024-04-09,2024-04-23: No news.
    5. 2024-05-07: Via mail responded to working on bug fixes in xapp-frame's. xapp-frame-cpp working well, still to make it work on xapp-frame(go) and xapp-frame-py
    6. 2024-05-21,2024-06-04: Unavailable
    7. 2024-07-02: Working on xapp-frame-cpp(changes in subscrition,sdl registrations), current RMR issues take a back seat as they are low prio.
  13. Nokia (subteam-n)
    1. RIC-997 postponed to J
    2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
  14. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
    1. 2024-03-26: New nomination awaited from TOC.
    2. 2024-04-09: The presentation of NEAR RT RIC would be handled by someone else(not James)
    3. “Analysis of Opensource Near-RT RICs – A comparative study”. Mainly, Intern will take the Specs, and analyse the available opensources of Near-RT RICs and prepare a report. I wanted to know your thoughts and interest in mentoring this activity. 
    4. 2024-07-02: Interns from Brazil already workin on it. Preliminary reports are available in Portugese language. This is WIP.
  15. J release
    1. 2024-02-13: Naman's input
      1. no Jira tickets yet, but woudl like to focus on 
        1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
    2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
      1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
    3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
      1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
      2. committed items only: all teams (committed) and all teams (committed + tentative).
      3. items that are known to require work, but are currently not in J release: link,  to include k8s version upgrade, ubuntu OS version, clean up of pending issues.
    1. input for release candidates: leftovers and generally open items, RSAC
    2. Sprint dates
      1. Sprint J release dev sprint 1: Feb-19 to Mar-10
      2. Sprint J release dev sprint 2: Mar-11 to Mar-31
      3. Sprint J release dev sprint 3: Apr-1 to Apr-21
      4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
      5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
  16. RICAPP agenda: RICAPP Meetings.

2024-06-04

Recording:  zoom meeting

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. Compliant
  2. every second time: Review code coverage stats and blocker code smells
    1. We take a look at the two links in the beginning of this page: Code coverage reports..
    2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
    3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link

    1. RIC-1062 Error while running hw-go and Bouncer xApps 04-06: Sunil to check

    2. RIC-1057 gNB unable to connect during high amount of Subscription Requests - Assigned to Amit Mishra - able to reproduce this issue, some timing issue to reduce to 2s. AbdulWahid to check with Aditya on the 10s timer in E2Manager.
    3. RIC-1056 Crashing e2mgr after sending high amount of Subscription Requests - Assigned to Dhiraj
    4. RIC-1055 Unrestricted Registration of RMR Routing Information by xApp
    5. RIC-1054 Kong pod is in crash loopback due to Ingress controller container is not coming up in 1.28 k8s installation- mostly needs kongversion upgrade. Abhijit provided hints.
    6. RIC-1051 Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - hwgo is gettong onboarded, still some issues with kpimon-go. 04-06: No issues seen with latest version of xapps.
    7. RIC-1047 crash in E2T metric increment code - WIP- Unable to reproduce the issue. 04-06:possible solution identified. Amit can raise the review issue ??
    8. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
    9. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  - code already committed. Wahid to check with Aditya for merging.
    10. RIC-1043 Crash in E2T buildPrometheusList Function  - WIP - Unable to reproduce the issue.
    11. RIC-1042 Can't register xApp
    12. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
    13. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
    14. RIC-1025 memory leak in routing manager
    15. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

    16. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

    17. RIC-1015 e2t too High default message size. → Nokia

    18. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

    19. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

    20. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
    21. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
    22. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    23. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
    24. RIC-915 dms_cli for installing xapp not working (raised by James)
    25. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    26. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    27. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    28. RIC-894 long idle period (days) causes RMR connection breaks
    29. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    30. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    31. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
    32. RIC-837 RMR is not forwarding messages from E2T to E2M
    33. RIC-835 → 2021-12-07 no news from Viktor
    34. fixed: 
  4. James: updates?
    1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
    2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
    3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
    4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
    5. 2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.
    6. 2024-03-26: Unavailable today.
    7. 2024-04-23:
    8. 2024-05-07: Updated on ORANSC summit. It was well received.
    9. 2024-05-21: No new updates this time.
  5. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
    2. 2024-02-13,2024-03-12,2024-03-26,2024-04-09,2024-04-23,2024-05-07, 2024-05-21: no news
  6. Sunil updates (subteam-h)?
    1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
    2. 2023-11-07: Not in the call today
    3. 2023-11-21: no updates. Difficult to find engineers working on this.
    4. 2024-01-16: demo of xApp project additions in I release → Next time
    5. 2024-01-16: re-evaluating RIC platform Jira items
    6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
    7. 2024-02-13: working on RIC subscription delete testing 
    8. 2024-03-12: Implementation completed, facing issues in code submission.
    9. 2024-03-26: Working on RIC-1049, documentation will also be made - Done
    10. 2024-03-09: Absent
    11. 2024-04-23: Not much updates.
    12. 2024-05-07: RIC-1045/RIC-1049 /RIC-1052/RIC-837 are completed. RIC-829 needs code commit.
    13. 2024-05-21:  unavailable
  7. Subhash/Naman updates (subteam-s) ?
    1. 2023-12-05: Naman gave an update on status of Samsung items
    2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
    3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
    4. 2024-03-12: RIC-1031 - Needs more time to complete, To start working on  A1 mediator integration with Non RealTime RIC
    5. 2024-03-26:  Continuing on RIC-1031, Working on RIC-1048 (analysis on RMR scaling, design to be worked upon)
    6. 2024-03-09,2024-04-23,2024-05-07,2024-05-21,2024-06-04: Not available
  8. Abhijit updates (subteam-ag) ?
    1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
    2. 2024-01-16, 2024-01-30: No news.
    3. 2024-02-13: continues work on xapp framework rust, incl. metric support
    4. 2024-03-12: No news.
    5. 2024-03-26: Implementation done , testing pending for xapp framework rust, incl. metric support
    6. 2024-03-09: Not available.
    7. 2024-03-23: Interested to work on 1056,1057 in coming weeks, after rust framework is tested. RIC-1006 done, RIC-1007 move to K, RIC-1028- will be taken up next. To give demo on rust-framework 07-05-2024.
    8. 2024-05-07:  RIC-1041 is done. Demo was given for metrics support in xapp-frame-rust that has default RMR Rx/Tx counters.
    9. Video for the demo added.
    10. 2024-05-21,2024-06-04: Unavailable
  9. Cap Gemini updates (subteam-cg)? 
    1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
    2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
    3. 2024-03-26,2024-03-09,2024-04-23,2024-05-07,2024-05-21,2024-06-04: unavailable.
  10. Himanshu (subteam-gs) would like to work on RIC-963
    1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
    3. 2024-03-12:  Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working,   length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr. Good to raise JIRA.
    4. 2024-03-26: Assigned RIC-1043,1044,1047. Will provide updates next week.  length of IE > 1024 in RIC_ACTION_DEFINITION causing issue in submgr - Sandeep to check if Jira needs to be raised. RIC-1051- Himanshu looking into it.
    5. 2024-03-09:  No updates on RIC-1043,1044,1047. Amit will contribute to this project.
    6. 2024-04-23: Not present
    7. 2024-05-07: RIC-1044 code committed, to be merged.RIC-1047 WIP, issue not reproducible. Possible issue identified, but need to reproduce. e2sim has some dependency on ubuntu 18.04 version(gcc) Issue to be raised for this also. Another Issue : Himanshu to raise issue related to RIC-1052
    8. 2024-05-21: Issue with e2sim identified and corrected (SIM-117), Issue related to 1052 , additional steps added by Amit and now stands closed.
  11. Dhiraj:
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.
    3. 2024-01-26, 2024-04-09,2024-04-23: no news.
    4. 2024-05-07: Dhiraj not representing Rakuten anymore.
    5. 2024-05-21,2024-06-04: Unavailable
  12. Alexandre (subteam-utfpr)
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
    3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
    4. 2024-03-26,2024-04-09,2024-04-23: No news.
    5. 2024-05-07: Via mail responded to working on bug fixes in xapp-frame's. xapp-frame-cpp working well, still to make it work on xapp-frame(go) and xapp-frame-py
    6. 2024-05-21,2024-06-04: Unavailable
  13. Nokia (subteam-n)
    1. RIC-997 postponed to J
    2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
  14. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
    1. 2024-03-26: New nomination awaited from TOC.
    2. 2024-04-09: The presentation of NEAR RT RIC would be handled by someone else(not James)
    3. “Analysis of Opensource Near-RT RICs – A comparative study”. Mainly, Intern will take the Specs, and analyse the available opensources of Near-RT RICs and prepare a report. I wanted to know your thoughts and interest in mentoring this activity. 
  15. J release
    1. 2024-02-13: Naman's input
      1. no Jira tickets yet, but woudl like to focus on 
        1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
    2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
      1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
    3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
      1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
      2. committed items only: all teams (committed) and all teams (committed + tentative).
      3. items that are known to require work, but are currently not in J release: link,  to include k8s version upgrade, ubuntu OS version, clean up of pending issues.
    1. input for release candidates: leftovers and generally open items, RSAC
    2. Sprint dates
      1. Sprint J release dev sprint 1: Feb-19 to Mar-10
      2. Sprint J release dev sprint 2: Mar-11 to Mar-31
      3. Sprint J release dev sprint 3: Apr-1 to Apr-21
      4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
      5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
  16. RICAPP agenda: RICAPP Meetings.

2024-05-21

Recording:  zoom recording

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. Last checked on (end of I release)
      1. TODO
  2. every second time: Review code coverage stats and blocker code smells
    1. We take a look at the two links in the beginning of this page: Code coverage reports..
    2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
    3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-1057 gNB unable to connect during high amount of Subscription Requests - Assigned to Amit Mishra - needs steps to reproduce this.
    2. RIC-1056 Crashing e2mgr after sending high amount of Subscription Requests - Assigned to Dhiraj
    3. RIC-1055 Unrestricted Registration of RMR Routing Information by xApp
    4. RIC-1054 Kong pod is in crash loopback due to Ingress controller container is not coming up in 1.28 k8s installation- mostly needs kongversion upgrade. Abhijit provided hints.
    5. RIC-1051 Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - hwgo is gettong onboarded, still some issues with kpimon-go
    6. RIC-1047 crash in E2T metric increment code - WIP- Unable to reproduce the issue.
    7. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
    8. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  - code already committed. Wahid to check with Aditya for merging.
    9. RIC-1043 Crash in E2T buildPrometheusList Function  - WIP - Unable to reproduce the issue.
    10. RIC-1042 Can't register xApp
    11. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
    12. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
    13. RIC-1025 memory leak in routing manager
    14. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

    15. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

    16. RIC-1015 e2t too High default message size. → Nokia

    17. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

    18. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

    19. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
    20. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
    21. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    22. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
    23. RIC-915 dms_cli for installing xapp not working (raised by James)
    24. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    25. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    26. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    27. RIC-894 long idle period (days) causes RMR connection breaks
    28. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    29. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    30. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
    31. RIC-837 RMR is not forwarding messages from E2T to E2M
    32. RIC-835 → 2021-12-07 no news from Viktor
    33. fixed: 
  4. James: updates?
    1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
    2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
    3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
    4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
    5. 2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.
    6. 2024-03-26: Unavailable today.
    7. 2024-04-23:
    8. 2024-05-07: Updated on ORANSC summit. It was well received.
    9. 2024-05-21: No new updates this time.
  5. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
    2. 2024-02-13,2024-03-12,2024-03-26,2024-04-09,2024-04-23,2024-05-07, 2024-05-21: no news
  6. Sunil updates (subteam-h)?
    1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
    2. 2023-11-07: Not in the call today
    3. 2023-11-21: no updates. Difficult to find engineers working on this.
    4. 2024-01-16: demo of xApp project additions in I release → Next time
    5. 2024-01-16: re-evaluating RIC platform Jira items
    6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
    7. 2024-02-13: working on RIC subscription delete testing 
    8. 2024-03-12: Implementation completed, facing issues in code submission.
    9. 2024-03-26: Working on RIC-1049, documentation will also be made - Done
    10. 2024-03-09: Absent
    11. 2024-04-23: Not much updates.
    12. 2024-05-07: RIC-1045/RIC-1049 /RIC-1052/RIC-837 are completed. RIC-829 needs code commit.
    13. 2024-05-21:  unavailable
  7. Subhash/Naman updates (subteam-s) ?
    1. 2023-12-05: Naman gave an update on status of Samsung items
    2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
    3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
    4. 2024-03-12: RIC-1031 - Needs more time to complete, To start working on  A1 mediator integration with Non RealTime RIC
    5. 2024-03-26:  Continuing on RIC-1031, Working on RIC-1048 (analysis on RMR scaling, design to be worked upon)
    6. 2024-03-09,2024-04-23,2024-05-07,2024-05-21: Not available
  8. Abhijit updates (subteam-ag) ?
    1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
    2. 2024-01-16, 2024-01-30: No news.
    3. 2024-02-13: continues work on xapp framework rust, incl. metric support
    4. 2024-03-12: No news.
    5. 2024-03-26: Implementation done , testing pending for xapp framework rust, incl. metric support
    6. 2024-03-09: Not available.
    7. 2024-03-23: Interested to work on 1056,1057 in coming weeks, after rust framework is tested. RIC-1006 done, RIC-1007 move to K, RIC-1028- will be taken up next. To give demo on rust-framework 07-05-2024.
    8. 2024-05-07:  RIC-1041 is done. Demo was given for metrics support in xapp-frame-rust that has default RMR Rx/Tx counters.
    9. Video for the demo added.
    10. 2024-05-21: Unavailable
  9. Cap Gemini updates (subteam-cg)? 
    1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
    2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
    3. 2024-03-26,2024-03-09,2024-04-23,2024-05-07,2024-05-21: unavailable.
  10. Himanshu (subteam-gs) would like to work on RIC-963
    1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
    3. 2024-03-12:  Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working,   length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr. Good to raise JIRA.
    4. 2024-03-26: Assigned RIC-1043,1044,1047. Will provide updates next week.  length of IE > 1024 in RIC_ACTION_DEFINITION causing issue in submgr - Sandeep to check if Jira needs to be raised. RIC-1051- Himanshu looking into it.
    5. 2024-03-09:  No updates on RIC-1043,1044,1047. Amit will contribute to this project.
    6. 2024-04-23: Not present
    7. 2024-05-07: RIC-1044 code committed, to be merged.RIC-1047 WIP, issue not reproducible. Possible issue identified, but need to reproduce. e2sim has some dependency on ubuntu 18.04 version(gcc) Issue to be raised for this also. Another Issue : Himanshu to raise issue related to RIC-1052
    8. 2024-05-21: Issue with e2sim identified and corrected (SIM-117), Issue related to 1052 , additional steps added by Amit and now stands closed.
  11. Dhiraj:
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.
    3. 2024-01-26, 2024-04-09,2024-04-23: no news.
    4. 2024-05-07: Dhiraj not representing Rakuten anymore.
    5. 2024-05-21: Unavailable
  12. Alexandre (subteam-utfpr)
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
    3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
    4. 2024-03-26,2024-04-09,2024-04-23: No news.
    5. 2024-05-07: Via mail responded to working on bug fixes in xapp-frame's. xapp-frame-cpp working well, still to make it work on xapp-frame(go) and xapp-frame-py
    6. 2024-05-21: Unavailable
  13. Nokia (subteam-n)
    1. RIC-997 postponed to J
    2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
  14. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
    1. 2024-03-26: New nomination awaited from TOC.
    2. 2024-04-09: The presentation of NEAR RT RIC would be handled by someone else(not James)
    3. “Analysis of Opensource Near-RT RICs – A comparative study”. Mainly, Intern will take the Specs, and analyse the available opensources of Near-RT RICs and prepare a report. I wanted to know your thoughts and interest in mentoring this activity. 
  15. J release
    1. 2024-02-13: Naman's input
      1. no Jira tickets yet, but woudl like to focus on 
        1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
    2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
      1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
    3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
      1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
      2. committed items only: all teams (committed) and all teams (committed + tentative).
      3. items that are known to require work, but are currently not in J release: link,  to include k8s version upgrade, ubuntu OS version, clean up of pending issues.
    1. input for release candidates: leftovers and generally open items, RSAC
    2. Sprint dates
      1. Sprint J release dev sprint 1: Feb-19 to Mar-10
      2. Sprint J release dev sprint 2: Mar-11 to Mar-31
      3. Sprint J release dev sprint 3: Apr-1 to Apr-21
      4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
      5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
  16. RICAPP agenda: RICAPP Meetings.

2024-05-07

Recording:  zoom recording

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. Last checked on (end of I release)
      1. TODO
  2. every second time: Review code coverage stats and blocker code smells
    1. We take a look at the two links in the beginning of this page: Code coverage reports..
    2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
    3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-1057 gNB unable to connect during high amount of Subscription Requests
    2. RIC-1056 Crashing e2mgr after sending high amount of Subscription Requests
    3. RIC-1055 Unrestricted Registration of RMR Routing Information by xApp
    4. RIC-1054 Kong pod is in crash loopback due to Ingress controller container is not coming up in 1.28 k8s installation- mostly needs kongversion upgrade. Abhijit provided hints.
    5. RIC-1051 Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - To be checked by Himanshu
    6. RIC-1047 crash in E2T metric increment code - WIP
    7. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
    8. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
    9. RIC-1043 Crash in E2T buildPrometheusList Function  - WIP
    10. RIC-1042 Can't register xApp
    11. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
    12. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
    13. RIC-1025 memory leak in routing manager
    14. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

    15. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

    16. RIC-1015 e2t too High default message size. → Nokia

    17. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

    18. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

    19. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
    20. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
    21. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    22. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
    23. RIC-915 dms_cli for installing xapp not working (raised by James)
    24. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    25. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    26. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    27. RIC-894 long idle period (days) causes RMR connection breaks
    28. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    29. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    30. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
    31. RIC-837 RMR is not forwarding messages from E2T to E2M
    32. RIC-835 → 2021-12-07 no news from Viktor
    33. fixed: 
  4. James: updates?
    1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
    2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
    3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
    4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
    5. 2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.
    6. 2024-03-26: Unavailable today.
    7. 2024-04-23:
    8. 2024-05-07: Updated on ORANSC summit. It was well received.
  5. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
    2. 2024-02-13,2024-03-12,2024-03-26,2024-04-09,2024-04-23,2024-05-07: no news
  6. Sunil updates (subteam-h)?
    1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
    2. 2023-11-07: Not in the call today
    3. 2023-11-21: no updates. Difficult to find engineers working on this.
    4. 2024-01-16: demo of xApp project additions in I release → Next time
    5. 2024-01-16: re-evaluating RIC platform Jira items
    6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
    7. 2024-02-13: working on RIC subscription delete testing 
    8. 2024-03-12: Implementation completed, facing issues in code submission.
    9. 2024-03-26: Working on RIC-1049, documentation will also be made - Done
    10. 2024-03-09: Absent
    11. 2024-04-23: Not much updates.
    12. 2024-05-07: RIC-1045/RIC-1049 /RIC-1052/RIC-837 are completed. RIC-829 needs code commit.
  7. Subhash/Naman updates (subteam-s) ?
    1. 2023-12-05: Naman gave an update on status of Samsung items
    2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
    3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
    4. 2024-03-12: RIC-1031 - Needs more time to complete, To start working on  A1 mediator integration with Non RealTime RIC
    5. 2024-03-26:  Continuing on RIC-1031, Working on RIC-1048 (analysis on RMR scaling, design to be worked upon)
    6. 2024-03-09,2024-04-23,2024-05-07: Not available
  8. Abhijit updates (subteam-ag) ?
    1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
    2. 2024-01-16, 2024-01-30: No news.
    3. 2024-02-13: continues work on xapp framework rust, incl. metric support
    4. 2024-03-12: No news.
    5. 2024-03-26: Implementation done , testing pending for xapp framework rust, incl. metric support
    6. 2024-03-09: Not available.
    7. 2024-03-23: Interested to work on 1056,1057 in coming weeks, after rust framework is tested. RIC-1006 done, RIC-1007 move to K, RIC-1028- will be taken up next. To give demo on rust-framework 07-05-2024.
    8. 2024-05-07:  RIC-1041 is done. Demo was given for metrics support in xapp-frame-rust that has default RMR Rx/Tx counters.
    9. Video for the demo added.
  9. Cap Gemini updates (subteam-cg)? 
    1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
    2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
    3. 2024-03-26,2024-03-09,2024-04-23,2024-05-07: unavailable.
  10. Himanshu (subteam-gs) would like to work on RIC-963
    1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
    3. 2024-03-12:  Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working,   length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr. Good to raise JIRA.
    4. 2024-03-26: Assigned RIC-1043,1044,1047. Will provide updates next week.  length of IE > 1024 in RIC_ACTION_DEFINITION causing issue in submgr - Sandeep to check if Jira needs to be raised. RIC-1051- Himanshu looking into it.
    5. 2024-03-09:  No updates on RIC-1043,1044,1047. Amit will contribute to this project.
    6. 2024-04-23: Not present
    7. 2024-05-07: RIC-1044 code committed, to be merged.RIC-1047 WIP, issue not reproducible. Possible issue identified, but need to reproduce. e2sim has some dependency on ubuntu 18.04 version(gcc) Issue to be raised for this also. Another Issue : Himanshu to raise issue related to RIC-1052.
  11. Dhiraj (subteam-r)
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.
    3. 2024-01-26, 2024-04-09,2024-04-23: no news.
    4. 2024-05-07: Dhiraj not representing Rakuten anymore.
  12. Alexandre (subteam-utfpr)
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
    3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
    4. 2024-03-26,2024-04-09,2024-04-23: No news.
    5. 2024-05-07: Via mail responded to working on bug fixes in xapp-frame's. xapp-frame-cpp working well, still to make it work on xapp-frame(go) and xapp-frame-py
  13. Nokia (subteam-n)
    1. RIC-997 postponed to J
    2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
  14. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
    1. 2024-03-26: New nomination awaited from TOC.
    2. 2024-04-09: The presentation of NEAR RT RIC would be handled by someone else(not James)
    3. “Analysis of Opensource Near-RT RICs – A comparative study”. Mainly, Intern will take the Specs, and analyse the available opensources of Near-RT RICs and prepare a report. I wanted to know your thoughts and interest in mentoring this activity. 
  15. J release
    1. 2024-02-13: Naman's input
      1. no Jira tickets yet, but woudl like to focus on 
        1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
    2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
      1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
    3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
      1. committed (90% sure) and tentative (90...30% sure) items: subteam-n,