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:

• Join from PC, Mac, Linux, iOS, or Android: https://zoom.us/j/9644759813
• Meeting ID for dial-in: 9644759813

2023-11-07

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 2023-09-26
      
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 ok, (not yet merged)
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-05-23:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   2. RIC-1016 e2t sctp_params structure may not be initialized properly

   3. RIC-1015 e2t too High default message size.

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

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

   6. RIC-1009 E2Mgr API can be improperly invoked → convert to bigger Epic?
   7. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   8. RIC-1001 RMR service should verify route tables - Alexandre will take a look
   9. RIC-991 RMR related (not a duplicate) - Alexandre will take a look
   10. RIC-989 RMR (minor) security issue - Alexandre will take a look
   11. RIC-972 (Naman) URL for A1 mediator to align with spec.
   12. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   13. 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)
   14. RIC-915 dms_cli for installing xapp not working (raised by James)
   15. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   16. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   17. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   18. RIC-894 long idle period (days) causes RMR connection breaks
   19. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   20. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   21. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
       1. 2021-12-21: Trying to get bandwidth for this during F release.
   22. RIC-837 RMR is not forwarding messages from E2T to E2M
   23. RIC-835 → 2021-12-07 no news from Viktor
   24. fixed:
       
4. James: updates?
   1. 2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.
   2. 2023-09-26: This was presented in TOC (See link). Cases relevant for near-RT RIC:
      1. ODU-high and near-RT RIC (currently using stub).
      2. near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)
      3. near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)
      4. James will check with Sunil on issues he has with the test cases
      5. ArgoCD used by Taiwan lab in some ONAP SMO  case and the engineers there where wondering if something similar could be done with OSC.
   3. 2023-10-24
      1. updates from O-RAN f-2-f:
         1. nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)
         2. OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.
            1. see demo "oai-osc-ric-demo.mp4" in link and the demo session recording on the O-RAN web site (thoralf-todo)
            2. more discussion coming at the joint OSC/OAI workshop in Boston
         3. session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.
      2. OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26 : could not participate
6. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
7. Subhash/Naman updates (subteam-s) ?
   1. 2023-08-29: no news, other than Naman working on the operator implementation.
   2. 2023-09-12:
      1. We had a meeting with John and Denis on non-rt RIC compatibility. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.
      2. Thoralf to figure out a way to start A1 mediator standalone for CI testing
         1. Thoralf sent instructions to John → DONE
      3. current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.
      4. Naman also works on the operator implementation
   3. 2023-09-26:
      
      1. kubernetes operator new repo needed or not?
         1. xapp deployment → appmgr or ricdms
         2. ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.
      2. What happened to kserve adapter? → Subhash can check.
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
         
      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 
      3. Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it.
9. Cap Gemini updates (subteam-cg)? 
   1. 2023-10-10:
      1. conflictmgr repo is now ready for commits: https://gerrit.o-ran-sc.org/r/admin/repos/ric-plt/conflictmgr,general
   2. 2023-11-07: after discussions on the topic we would like to proceed with

      1. Phase1: Conflict Manager (running as a platform component) without E2SM parsing which means that Conflict Manager feature will work only for Conflict Aware xApps. Interface between Conflict Aware xApp and Conflict Manager will be gRPC.

      2. Phase2: E2SM xApp support so that the Conflict Manager feature works for Conflict Unaware xApps as well. TODO-discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation

10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. 2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".
11. Dhiraj (subteam-r)
    
    1. 2023-08-22:
       1. checking compliance/license issues
       2. How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).
    2. 2023-08-29:
       1. got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes
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
13. Nokia (subteam-n)
    1. ...
14. I release content

1. 1. we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I 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.
   2. input for release candidates: left overs and generally open items, RSAC
   3. Sprint dates
      1. Sprint I release dev sprint 1: Aug-21 to Sep-10
      2. Sprint I release dev sprint 2: Sep-11 to Oct-1
      3. Sprint I release dev sprint 3: Oct-2 to Oct-22
      4. Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
      5. Sprint I release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
   4. Plan (v03 as of 2023-08-18):
      1. I release plan moved to I release page.
2. RICAPP agenda: RICAPP Meetings.

Older meeting minutes

check from here: Project meetings (old)