Note that the links to the recordings before 2021-03-16 where mp4 files. They broke when copying the text into this archive page. You can still find them as attachments to the original meetings page Project meetings -> click on the three dots in the upper right corner and select “Attachments” from the menu.

2023-10-24

Recording: link to zoom recording

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/alarm-go/+/11149 OK, go version update only~~
  2. ~~https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/11234 OK, test case added for IPv6 tests~~
  3. ~~https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11324 OK, test case updated~~
  4. ~~https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11733 OK, generated code from API~~
  5. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 ok, (not yet merged)
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
Every time: Check if there are new bug reports in JIRA: link
1. ~~RIC-1019 xapp-frame - incorrect removal of transmitted rmr message in unsuccessful case (Juha) →~~ DONE
2. RIC-1017 xapp-frame - xapp-frame may not be able to successfully subscribe to messages
3. RIC-1016 e2t sctp_params structure may not be initialized properly
4. RIC-1015 e2t too High default message size.
5. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads.
6. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption
7. ~~RIC-1012 RMR not working in A1 mediator →~~ ~~DONE (Thoralf also released fixed image in ric-dep recipe of h-release)~~
8. RIC-1009 E2Mgr API can be improperly invoked → convert to bigger Epic?
9. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
10. RIC-1001 RMR service should verify route tables - Alexandre will take a look
11. RIC-991 RMR related (not a duplicate) - Alexandre will take a look
12. RIC-989 RMR (minor) security issue - Alexandre will take a look
13. RIC-972 (Naman) URL for A1 mediator to align with spec.
14. RIC-965 RMR wormhole connections uses stale endpoints to make connections
15. 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)
16. RIC-915 dms_cli for installing xapp not working (raised by James)
17. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
18. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
19. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
20. RIC-894 long idle period (days) causes RMR connection breaks
21. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
22. RIC-857 sporadically RMR takes multiple minutes before being "ready"
23. 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.
24. RIC-837 RMR is not forwarding messages from E2T to E2M
25. RIC-835 → 2021-12-07 no news from Viktor
26. fixed: RIC-1019, RIC-1012
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)
Prashant's work in near-RT RIC(subteam-p)
1. 2023-08-22, 2023-09-26 : could not participate
Sunil updates (subteam-h)?
1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
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.
Abhijit updates (subteam-ag) ?
1. ~~2023-08-22: next release item discussed and RIC-979~~
2. ~~2023-08-29:~~
  1. ~~created RIC-1004 for release I item.~~
  2. ~~still working on RIC minimal implementation (demo coming once ready, might take still weeks)~~
    1. ~~once it's somewhat usable, pls. place into subdirectory under ric-plt/ric-dep~~
3. 2023-09-12:
  1. changes related to registration API needed in xapp-frame (problem still to be thought of)
  2. ~~something not working in github: IT-25974 - again related to github replication.~~
4. ~~2023-09-26~~
  1. ~~Abhijit presented his work on a single near RT RIC helm chart and bringing up the platform on minikube on Ubuntu 22.04. We decided to proceed with this.~~
  2. ~~github action problem with master vs g release for replication → ticket → DONE~~
  3. ~~Abhijit wanted to provide a video for new way of ric deployment (2023-10-24: did not find time to finally do this)~~
5. 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.
Cap Gemini updates (subteam-cg)?
1. ~~Conflict detection and management. Presentation by Gunja on Sep-12 link-to-slideset~~
  1. ~~Ashish S. (CapGemini) presented this.~~
  2. ~~Thoralf will initiate a new repo for this: ric-plt/conflictmgr~~
    1. ~~this might become an optional or mandatory (but default-disabled) component of thr near-rt ric platform.~~
    2. ~~todo-cap-gemini: align usage of UE ID with wg3 discussion on this.~~
    3. ~~additional latency comes only from guidance request~~
    4. ~~xapp-framework could be extended to automatically do E2 guidance requests~~
2. 2~~023-09-26:~~
  1. ~~first step of new repo created, but still issues with initial files in repo. Thoralf raised request to LF: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26015~~
3. 2023-10-10:
  1. conflictmgr repo is now ready for commits: https://gerrit.o-ran-sc.org/r/admin/repos/ric-plt/conflictmgr,general
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".
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
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
Nokia (subteam-n)
1. ...
I release content

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.
RICAPP agenda: RICAPP Meetings.

2023-10-10

no meeting as neither Thoralf nor Sunil were available to host the call

2023-09-26

Recording: link to zoom recording

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/alarm-go/+/11149 OK, go version update only
  2. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/11234 OK, test case added for IPv6 tests
  3. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11324 PK, test case updated
  4. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11733 OK, generated code from API
  5. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 ok, (not yet merged)
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
Every time: Check if there are new bug reports in JIRA: link
1. ~~RIC-1011 (Nokia fixes) E2 error with cause duplicate-error for all subscriptions requests after resource-limit failure - FIXED~~
2. RIC-1009 E2Mgr API can be improperly invoked → convert to bigger Epic?
3. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
4. RIC-1001 RMR service should verify route tables - Alexandre will take a look
5. RIC-991 RMR related (not a duplicate) - Alexandre will take a look
6. RIC-989 RMR (minor) security issue - Alexandre will take a look
7. ~~RIC-979 (Abhijit will close this one) Decode Error with e2sim on e2term Pod - 2023-08-22: Abhijit still looking into this, but with latest Ubuntu packages this seems not to cause the problem anymore.~~
8. RIC-972 (Naman) URL for A1 mediator to align with spec.
9. RIC-965 RMR wormhole connections uses stale endpoints to make connections
10. 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)
11. RIC-915 dms_cli for installing xapp not working (raised by James)
12. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
13. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
14. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
15. RIC-894 long idle period (days) causes RMR connection breaks
16. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
17. RIC-857 sporadically RMR takes multiple minutes before being "ready"
18. 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.
19. RIC-837 RMR is not forwarding messages from E2T to E2M
20. RIC-835 → 2021-12-07 no news from Viktor
21. fixed: RIC-1011, RIC-979
James: updates?
1. ~~2023-08-01:~~
  1. ~~O2 integration with OSC RIC is still pending with WR.~~
  2. ~~OAI was discussed in last week's TOC, and it seems OAI license is not blocker for using OAI in OSC-labs.~~
2. ~~2023-08-22:~~
  1. ~~Can we do pair-wise testing, e.g., between (1) xapp and RIC, (2) non-RT RIC ↔ near-RT RIC testing (only A1) ?~~
    1. ~~E.g., KPIMON or bouncer xApp could be used. Sunil might be able to help.~~
    2. ~~e.g., existing discussion with John~~
3. ~~2023-08-29: no news~~
4. 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.
5. 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 coudl be done with OSC.
Prashant's work in near-RT RIC(subteam-p)
1. 2023-08-22, 2023-09-26 : could not participate
Sunil updates (subteam-h)?
1. ~~2023-07-18, 2023-08-01, 2023-08-22, 2023-08-29: no news~~
2. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
Subhash/Naman updates (subteam-s) ?
1. ~~2023-08-01:~~
  1. ~~E2AP v3.0 → we took a look at what changes are coming~~
  2. ~~A1 enhancements~~
  3. ~~considering upgrade of ubuntu and k8s~~
  4. ~~deploying RIC and xapps using k8S operator I_Release_Proposal_Samsung_Naman.pptx~~
  5. ~~DMS delete PI~~
  6. ~~E2 reset from ric to e2 node~~
2. ~~2023-08-22: we discussed Jira item priority.~~
3. 2023-08-29: no news, other than Naman working on the operator implementation.
4. 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
5. 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.
Abhijit updates (subteam-ag) ?
1. ~~2023-05-23~~
  1. 1. ~~hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe~~
    2. ~~testing of subscriptions using hw-rust (facing the E2T problem)~~
2. ~~2023-07-18: no news~~
3. ~~2023-08-01: got logs from Subhash. Now ran into issues with Dockerfile in E2T (gcc related differences between ubuntu 20 and 22)~~
4. 2023-08-22: next release item discussed and RIC-979
5. 2023-08-29:
  1. created RIC-1004 for release I item.
  2. still working on RIC minimal implementation (demo coming once ready, might take still weeks)
    1. once it's somewhat usable, pls. place into subdirectory under ric-plt/ric-dep
6. 2023-09-12:
  1. changes related to registration API needed in xapp-frame (problem still to be thought of)
  2. something not working in github: IT-25974 - again related to github replication.
7. 2023-09-26
  1. Abhijit presented his work on a single near RT RIC helm chart and bringing up the platform on minikube on Ubuntu 22.04. We decided to proceed with this.
  2. github action problem with master vs g release for replication → ticket.
  3. Abhijit wanted to provide a video for new way of ric deployment
Cap Gemini updates (subteam-cg)?
1. ~~2023-08-01~~
  1. ~~Gunja to present conflict management design~~
  2. ~~thinking about adding support for DU in E2T/E2M/RNIB in I release~~
2. 2023-08-22:
  1. ~~Gunja provided reviews for DU support. Nokia to reviewed and merged~~
    1. ~~https://gerrit.o-ran-sc.org/r/q/topic:%22Multiple+E2+Node+support%22 and https://gerrit.o-ran-sc.org/r/q/topic:Multi_E2_Node~~
  2. Conflict detection and management. Presentation by Gunja on Sep-12 link-to-slideset
    1. Ashish S. (CapGemini) presented this.
    2. Thoralf will initiate a new repo for this: ric-plt/conflictmgr
      1. this might become an optional or mandatory (but default-disabled) component of thr near-rt ric platform.
      2. todo-cap-gemini: align usage of UE ID with wg3 discussion on this.
      3. additional latency comes only from guidance request
      4. xapp-framework could be extended to automatically do E2 guidance requests
3. 2023-09-26:
  1. first step of new repo created, but still issues with initial files in repo. Thoralf raised request to LF: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26015
Himanshu (subteam-gs) would like to work on RIC-963
1. ~~code changes, but difficult to test as difficult to change order of IEs in message.~~
2. ~~2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.~~
3. ~~2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.~~
4. ~~2023-08-22: feedback from Anssi on submgr received and incorporating these changes, but not yet in review.~~
5. 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".
Dhiraj (subteam-r)
1. ~~2023-07-18: IPv6 changes to come as review~~
2. ~~2023-08-01: working on it.~~
3. 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).
4. 2023-08-29:
  1. got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes
Alexandre (subteam-utfpr)
1. ~~2023-08-22: Alexandre couldn't participate, but informed after the meeting by e-mail: "My plan for the next two weeks is to fix both RIC-989 and RIC-991 issues."~~
2. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
3. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
Nokia (subteam-n)
1. ~~2023-08-22: want to work on RIC-997~~
2. 2023-09-12: Thoralf did changes to readthedocs in all near-RT RIC repos. LF informed (link) these changes are needed because some configuration parameters are being removed. No further changes needed due to this. Example: https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11747. Note, though, that some repos don't currently generate read-the-docs documention. For the "A1" example, though you see a new documentation version in this URL: https://readthedocs.org/projects/o-ran-sc-ric-plt-a1/builds/
3. Thoralf on holiday on Oct-10. Sunil?
I release content

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. ~~E2 enhancements, incl. conflict mgmt.~~
    1. ~~RIC-993 (CG): Near-RT RIC conflict management (*)~~
    2. ~~RIC-933 (CG) : Adding support for DU in E2T/E2M/RNIB~~
    3. ~~RIC-967 (CG) xApp-facing interface for subscription delete required (added on 2023-08-23)~~
    4. ~~RIC-994 (S): Support for E2APv3.0~~
    5. ~~RIC-995 (S): Support for RIC Query~~
    6. ~~RIC-996 (S) Support for Subscription modifications (dhiraj interested as reviewer)~~
    7. ~~RIC-387 (S): Support for E2 reset from RIC to RAN (completes also RIC-383) (prio1) (Dhiraj interested as reviewer, but we had earlier discussion on this)~~
    8. ~~RIC-997 (N): Handling of RIC Error indication _during_ E2 setup~~
    9. ~~RIC-963 (GS) modify src code to be more lenient in ordering of IEs in ASN.1~~
  3. ~~Other~~
    1. ~~RIC-998 (S): K8S operators for deploying/undeploy xApps(*(1))~~
    2. ~~RIC-999 (S): A1 alignment with A1AP (still under investigation. Minimum is using correct URL) (*(1))~~
    3. ~~RIC-954 (S): DMS Rest API support for deleting/undeploy xApps (DMS REST is 2nd ifc addressing same space as dmscli) (1)~~
    4. ~~Already in H: RIC-985 (UTFPR) IPv6 support for RMR~~
    5. ~~RIC-1000 (R): Support for only-IPv6 in RIC-internal interfaces~~
    6. ~~RIC-1004 (AG): Xapp Rust Framework enhancement after initial basic Xapp Framework Support~~
RICAPP agenda: RICAPP Meetings.

2023-09-12

Recording: link to zoom recording

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-04-11
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/10923 OK, module version updates only
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
Every time: Check if there are new bug reports in JIRA: link
1. RIC-1011 (Nokia fixes) E2 error with cause duplicate-error for all subscriptions requests after resource-limit failure
2. RIC-1009 E2Mgr API can be improperly invoked → convert to bigger Epic?
3. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
4. RIC-1001 RMR service should verify route tables - Alexandre will take a look
5. RIC-991 rmr related (not a duplicate) - Alexandre will take a look
6. RIC-989 rmr (minor) security issue - Alexandre will take a look
7. RIC-979 (Abhijit will close this one) Decode Error with e2sim on e2term Pod - 2023-08-22: Abhijit still looking into this, but with latest Ubuntu packages this seems not to cause the problem anymore.
8. RIC-972 (Naman) URL for A1 mediator to align with spec.
9. RIC-965 RMR wormhole connections uses stale endpoints to make connections
10. 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)
11. RIC-915 dms_cli for installing xapp not working (raised by James)
12. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
13. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
14. ~~RIC-897 SCTP connection fails with Viavi // update with workaround → Thoralf changed this into an Epic (problem was on simulator side. But some useful extension on E2T comes from this as well)~~
15. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
16. RIC-894 long idle period (days) causes RMR connection breaks
17. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
18. RIC-857 sporadically RMR takes multiple minutes before being "ready"
19. 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.
20. RIC-837 RMR is not forwarding messages from E2T to E2M
21. RIC-835 → 2021-12-07 no news from Viktor
22. fixed: ...
James: updates?
1. 2023-08-01:
  1. O2 integration with OSC RIC is still pending with WR.
  2. OAI was discussed in last week's TOC, and it seems OAI license is not blocker for using OAI in OSC-labs.
2. 2023-08-22:
  1. Can we do pair-wise testing, e.g., between (1) xapp and RIC, (2) non-RT RIC ↔ near-RT RIC testing (only A1) ?
    1. E.g., KPIMON or bouncer xApp could be used. Sunil might be able to help.
    2. e.g., existing discussion with John
3. 2023-08-29: no news
4. 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.
Prashant's work in near-RT RIC(subteam-p)
1. 2023-08-22 : could not participate
Sunil updates (subteam-h)?
1. 2023-07-18, 2023-08-01, 2023-08-22, 2023-08-29: no news
2. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
Subhash/Naman updates (subteam-s) ?
1. 2023-08-01:
  1. E2AP v3.0 → we took a look at what changes are coming
  2. A1 enhancements
  3. considering upgrade of ubuntu and k8s
  4. deploying RIC and xapps using k8S operator I_Release_Proposal_Samsung_Naman.pptx
  5. DMS delete PI
  6. E2 reset from ric to e2 node
2. 2023-08-22: we discussed Jira item priority.
3. 2023-08-29: no news, other than Naman working on the operator implementation.
4. 2023-09-12:
  1. We had a meeting with John and Denis on non-rt RIC compatibilty. 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
  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
Abhijit updates (subteam-ag) ?
1. 2023-05-23
  1. 1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
    2. testing of subscriptions using hw-rust (facing the E2T problem)
2. 2023-07-18: no news
3. 2023-08-01: got logs from Subhash. Now ran into issues with Dockerfile in E2T (gcc related differences between ubuntu 20 and 22)
4. 2023-08-22: next release item discussed and RIC-979
5. 2023-08-29:
  1. created RIC-1004 for release I item.
  2. still working on RIC minimal implementation (demo coming once ready, might take still weeks)
    1. once it's somewhat usable, pls. place into subdirectory under ric-plt/ric-dep
6. 2023-09-12:
  1. changes related to registration API needed in xapp-frame (problem still to be thought of)
  2. something not working in github: IT-25974 - again related to github replication.
Cap Gemini updates (subteam-cg)?
1. 2023-08-01
  1. Gunja to present conflict management design
  2. thinking about adding support for DU in E2T/E2M/RNIB in I release
2. 2023-08-22:
  1. Gunja provided reviews for DU support. Nokia to reviewed and merged
    1. https://gerrit.o-ran-sc.org/r/q/topic:%22Multiple+E2+Node+support%22 and https://gerrit.o-ran-sc.org/r/q/topic:Multi_E2_Node
  2. Conflict detection and management. Presentation by Gunja on Sep-12 link-to-slideset
    1. Ashish S. (CapGemini) presented this.
    2. Thoralf will initiate a new repo for this: ric-plt/conflictmgr
      1. this might become an optional or mandatory (but default-disabled) component of thr near-rt ric platform.
      2. todo-cap-gemini: align usage of UE ID with wg3 discussion on this.
      3. additional latency comes only from guidance request
      4. xapp-framework could be extended to automatically do E2 guidance requests
Himanshu (subteam-gs) would like to work on RIC-963
1. code changes, but difficult to test as difficult to change order of IEs in message.
2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
3. 2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
4. 2023-08-22: feedback from Anssi on submgr received and incorporating these changes, but not yet in review.
5. 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".
Dhiraj (subteam-r)
1. 2023-07-18: IPv6 changes to come as review
2. 2023-08-01: working on it.s
3. 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).
4. 2023-09-29:
  1. got clarity on license issues and now waiting for internal approval.
Alexandre (subteam-utfpr)
1. 2023-08-22: Alexandre couldn't participate, but informed after the meeting by e-mail: "My plan for the next two weeks is to fix both RIC-989 and RIC-991 issues."
2. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
Nokia (subteam-n)
1. 2023-08-22: want to work on RIC-997
2. 2023-09-12: Thoralf did changes to readthedocs in all near-RT RIC repos. LF informed (link) these changes are needed because some configuration parameters are being removed. No further changes needed due to this. Example: https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11747. Note, though, that some repos don't currently generate read-the-docs documention. For the "A1" example, though you see a new documentation version in this URL: https://readthedocs.org/projects/o-ran-sc-ric-plt-a1/builds/
I release content

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. E2 enhancements, incl. conflict mgmt.
    1. RIC-993 (CG): Near-RT RIC conflict management (*)
    2. RIC-933 (CG) : Adding support for DU in E2T/E2M/RNIB
    3. RIC-967 (CG) xApp-facing interface for subscription delete required (added on 2023-08-23)
    4. RIC-994 (S): Support for E2APv3.0
    5. RIC-995 (S): Support for RIC Query
    6. RIC-996 (S) Support for Subscription modifications (dhiraj interested as reviewer)
    7. RIC-387 (S): Support for E2 reset from RIC to RAN (completes also RIC-383) (prio1) (Dhiraj interested as reviewer, but we had earlier discussion on this)
    8. RIC-997 (N): Handling of RIC Error indication _during_ E2 setup
    9. RIC-963 (GS) modify src code to be more lenient in ordering of IEs in ASN.1
  2. Other
    1. RIC-998 (S): K8S operators for deploying/undeploy xApps(*(1))
    2. RIC-999 (S): A1 alignment with A1AP (still under investigation. Minimum is using correct URL) (*(1))
    3. RIC-954 (S): DMS Rest API support for deleting/undeploy xApps (DMS REST is 2nd ifc addressing same space as dmscli) (1)
    4. Already in H: RIC-985 (UTFPR) IPv6 support for RMR
    5. RIC-1000 (R): Support for only-IPv6 in RIC-internal interfaces
    6. RIC-1004 (AG): Xapp Rust Framework enhancement after initial basic Xapp Framework Support
RICAPP agenda: RICAPP Meetings.

2023-08-29 (back to normal week, therefore only 1 week after previous meeting)

Recording: link to zoom recording

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-04-11
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/10923 OK, module version updates only
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
Every time: Check if there are new bug reports in JIRA: link
1. RIC-1002 Abnormal signaling process cause E2Term crash (this could be a security issue)
2. RIC-1001 RMR service should verify route tables.
3. RIC-991 rmr related (not a duplicate) - Alexandre will take a look
4. RIC-989 rmr (minor) security issue - Alexandre will take a look
5. RIC-979 Decode Error with e2sim on e2term Pod - 2023-08-22: Abhijit still looking into this, but with latest Ubuntu packages this seems not to cause the problem anymore.
6. RIC-972 URL for A1 mediator to align with spec.
7. RIC-965 RMR wormhole connections uses stale endpoints to make connections
8. 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)
9. RIC-915 dms_cli for installing xapp not working (raised by James)
10. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
11. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
12. ~~RIC-897 SCTP connection fails with Viavi // update with workaround → Thoralf changed this into an Epic (problem was on simulator side. But some useful extension on E2T comes from this as well)~~
13. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
14. RIC-894 long idle period (days) causes RMR connection breaks
15. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
16. RIC-857 sporadically RMR takes multiple minutes before being "ready"
17. 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.
18. RIC-837 RMR is not forwarding messages from E2T to E2M
19. RIC-835 → 2021-12-07 no news from Viktor
20. fixed: ...
James: updates?
1. 2023-08-01:
  1. O2 integration with OSC RIC is still pending with WR.
  2. OAI was discussed in last week's TOC, and it seems OAI license is not blocker for using OAI in OSC-labs.
2. 2023-08-22:
  1. Can we do pair-wise testing, e.g., between (1) xapp and RIC, (2) non-RT RIC ↔ near-RT RIC testing (only A1) ?
    1. E.g., KPIMON or bouncer xApp could be used. Sunil might be able to help.
    2. e.g., existing discussion with John
3. 2023-08-29: no news
Prashant's work in near-RT RIC(subteam-p)
1. 2023-08-22 : could not participate
Sunil updates (subteam-h)?
1. 2023-07-18, 2023-08-01, 2023-08-22, 2023-08-29: no news
Subhash/Naman updates (subteam-s) ?
1. 2023-08-01:
  1. E2AP v3.0 → we took a look at what changes are coming
  2. A1 enhancements
  3. considering upgrade of ubuntu and k8s
  4. deploying RIC and xapps using k8S operator I_Release_Proposal_Samsung_Naman.pptx
  5. DMS delete PI
  6. E2 reset from ric to e2 node
2. 2023-08-22: we discussed Jira item priority.
3. 2023-08-29: no news, other than Naman working on the operator implementation.
Abhijit updates (subteam-ag) ?
1. 2023-05-23
  1. 1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
    2. testing of subscriptions using hw-rust (facing the E2T problem)
2. 2023-07-18: no news
3. 2023-08-01: got logs from Subhash. Now ran into issues with Dockerfile in E2T (gcc related differences between ubuntu 20 and 22)
4. 2023-08-22: next release item discussed and RIC-979
5. 2023-08-29:
  1. created RIC-1004 for release I item.
  2. still working on RIC minimal implementation (demo coming once ready, might take still weeks)
    1. once it's somewhat usable, pls. place into subdirectory under ric-plt/ric-dep
Cap Gemini updates (subteam-cg)?
1. 2023-08-01
  1. Gunja to present conflict management design
  2. thinking about adding support for DU in E2T/E2M/RNIB in I release
2. 2023-08-22:
  1. Gunja provided reviews for DU support. Nokia to reviewed and merged
    1. https://gerrit.o-ran-sc.org/r/q/topic:%22Multiple+E2+Node+support%22 and https://gerrit.o-ran-sc.org/r/q/topic:Multi_E2_Node
  2. Conflict management status? Thoralf checked by e-mail after the meeting. Presentation by Gunja planned for Sep-12
Himanshu (subteam-gs) would like to work on RIC-963
1. code changes, but difficult to test as difficult to change order of IEs in message.
2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
3. 2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
4. 2023-08-22: feedback from Anssi on submgr received and incorporating these changes, but not yet in review.
5. 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".
Dhiraj (subteam-r)
1. 2023-07-18: IPv6 changes to come as review
2. 2023-08-01: working on it.
3. 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).
4. 2023-09-29:
  1. got clarity on license issues and now waiting for internal approval.
Alexandre (subteam-utfpr)
1. 2023-08-22: Alexandre couldn't participate, but informed after the meeting by e-mail: "My plan for the next two weeks is to fix both RIC-989 and RIC-991 issues."
2. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
Nokia (subteam-n)
1. 2023-08-22: want to work on RIC-997
I release content

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. E2 enhancements, incl. conflict mgmt.
    1. RIC-993 (CG): Near-RT RIC conflict management (*)
    2. RIC-933 (CG) : Adding support for DU in E2T/E2M/RNIB
    3. RIC-967 (CG) xApp-facing interface for subscription delete required (added on 2023-08-23)
    4. RIC-994 (S): Support for E2APv3.0
    5. RIC-995 (S): Support for RIC Query
    6. RIC-996 (S) Support for Subscription modifications (dhiraj interested as reviewer)
    7. RIC-387 (S): Support for E2 reset from RIC to RAN (completes also RIC-383) (prio1) (Dhiraj interested as reviewer, but we had earlier discussion on this)
    8. RIC-997 (N): Handling of RIC Error indication _during_ E2 setup
    9. RIC-963 (GS) modify src code to be more lenient in ordering of IEs in ASN.1
  2. Other
    1. RIC-998 (S): K8S operators for deploying/undeploy xApps(*(1))
    2. RIC-999 (S): A1 alignment with A1AP (still under investigation. Minimum is using correct URL) (*(1))
    3. RIC-954 (S): DMS Rest API support for deleting/undeploy xApps (DMS REST is 2nd ifc addressing same space as dmscli) (1)
    4. Already in H: RIC-985 (UTFPR) IPv6 support for RMR
    5. RIC-1000 (R): Support for only-IPv6 in RIC-internal interfaces
    6. RIC-1004 (AG): Xapp Rust Framework enhancement after initial basic Xapp Framework Support
RICAPP agenda: RICAPP Meetings.

2023-08-22 (exceptionally one week later than normal)

Recording: link to zoom recording

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-04-11
  1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/10923 OK, module version updates only
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
Every time: Check if there are new bug reports in JIRA: link
1. RIC-1002 Abnormal signaling process cause E2Term crash (this could be a security issue)
2. RIC-1001 RMR service should verify route tables.
3. RIC-991 rmr related (not a duplicate) - Alexandre will take a look
4. RIC-989 rmr (minor) security issue - Alexandre will take a look
5. ~~new: RIC-988 CLOSED e2 component configuration → Duplicate of fix https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/e2mgr.git;a=commit;h=d2f1a29d3f1cc779045148a82729f644e6110776~~
6. ~~RIC-986 ping-pong example xapp-frame-py needs fixes in the dockerfile DONE~~
7. RIC-979 Decode Error with e2sim on e2term Pod - 2023-08-22: Abhijit still looking into this, but with latest Ubuntu packages this seems not to cause the problem anymore.
8. RIC-972 URL for A1 mediator to align with spec.
9. RIC-965 RMR wormhole connections uses stale endpoints to make connections
10. 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)
11. RIC-915 dms_cli for installing xapp not working (raised by James)
12. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
13. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
14. RIC-897 SCTP connection fails with Viavi // update with workaround → Thoralf changed this into an Epic (problem was on simulator side. But some useful extension on E2T comes from this as well)
15. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
16. RIC-894 long idle period (days) causes RMR connection breaks
17. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
18. RIC-857 sporadically RMR takes multiple minutes before being "ready"
19. 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.
20. RIC-837 RMR is not forwarding messages from E2T to E2M
21. RIC-835 → 2021-12-07 no news from Viktor
22. fixed: RIC-986
~~Himanshu: demo on the OAI CU <--> OSC RIC integration~~
1. ~~Himanshu presented the integration of SDRAN-fork of OAI (with SDRAN E2 support added) and how the CU connects to OSC RIC~~
James: updates?
1. ~~2023-01-31:~~
  1. ~~working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.~~
  2. ~~Subhash asked for a wiki page documenting this work.~~
  3. ~~WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.~~
    1. ~~discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.~~
    2. ~~Tacker-based deployment needs to be checked.~~
2. ~~2023-03-14, 2023-03-28 : no news~~
3. ~~2023-04-11: H release test cases related O2 IMS committed into it/test. Some of these related to existing robot test cases.~~
4. ~~2023-04-25: no updates~~
5. ~~2023-05-09:~~
  1. ~~Q-to-James: summary of what you presented in TOC (1 min) and let's raise question to all for input to integration project.~~
    1. ~~Xtesting is used in integration project now (already for 6 months or so). Xtesting works also with robot test cases.~~
    2. ~~James working in this integration for the test cases that are already in it/test. Infrastructure team also contributed O2 releated robot test cases (requires o-loud).~~
    3. ~~Input from other subprojects, incl. our near-RT RIC project?~~
  2. ~~James needs some hints on how to run the existing robot test cases in it/test related to missing env variables: GLOBAL_INJECTED_E2MGR_USER and APPMGR_ENDPOINT.~~
6. ~~2023-05-23 → no news~~
7. ~~2023-07-18: James' focus is currently on OSC & OAI cooperation. Current thinking is to use Taiwan lab to host OAI -based installation over E2AP (2.0). See also https://openairinterface.org/mosaic5g/~~
  1. ~~usage of robot test cases (from it/test) is still something that James is thinking about.~~
  2. ~~Himanshu commented that he tried OAI CU/DU with OSC RIC and KPM xApp.~~
8. 2023-08-01:
  1. O2 integration with OSC RIC is still pending with WR.
  2. OAI was discussed in last week's TOC, and it seems OAI license is not blocker for using OAI in OSC-labs.
9. 2023-08-22:
  1. Can we do pair-wise testing, e.g., between (1) xapp and RIC, (2) non-RT RIC ↔ near-RT RIC testing (only A1) ?
    1. E.g., KPIMON or bouncer xApp could be used. Sunil might be able to help.
    2. e.g., existing discussion with John
Prashant's work in near-RT RIC(subteam-p)
1. 2023-08-22 : could not participate
Sunil updates (subteam-h)?
1. 2023-07-18, 2023-08-01, 2023-08-22: no news
Subhash/Naman updates (subteam-s) ?
1. ~~2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).~~
  1. ~~Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),~~
    1. ~~2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link~~
      1. ~~Thoralf to create JIRA item for this~~
      2. ~~Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.~~
      3. ~~2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later~~
      4. ~~https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114~~
    2. ~~Integration with AI/ML project: kserve_adapter~~
      1. ~~data pipeline (Hoejoo's e-mail)~~
        ~~2023-01-31 not discussed in today's meeting~~
2. ~~2023-03-14:~~
  1. ~~E2 Reset E2mgr changes done. submgr change and notification to xapp still open.~~
  2. ~~A1 mediator nanobot integration still under work~~
3. ~~2023-03-28: work continues~~
4. ~~2023-04-11: E2 reset work in submgr is now under work.~~
5. ~~2023-04-25: Naman working on E2 reset (submgr part), ricdms not too much progress. no update on kserve~~
6. ~~2023-05-09:~~
  1. ~~E2 reset done, but still one more review coming on submgr to block subscriptions fo0r E2 nodes under reset.~~
  2. ~~A1 bug fixes being almost ready.~~
  3. ~~A1 mediator nanobot might be delayed.~~
  4. ~~AI/ML adapter work is still ongoing - ricdms changes still coming during next 1-2 weeks.~~
7. ~~2023-05-23~~
  1. ~~E2 reset (from E2 node): done~~
  2. ~~KServe adapter still being worked on.~~
  3. ~~nanobot integration still being worked on.~~
8. ~~2023-07-18: no news, planning for I release~~
9. 2023-08-01:
  1. E2AP v3.0 → we took a look at what changes are coming
  2. A1 enhancements
  3. considering upgrade of ubuntu and k8s
  4. deploying RIC and xapps using k8S operator I_Release_Proposal_Samsung_Naman.pptx
  5. DMS delete PI
  6. E2 reset from ric to e2 node
10. 2023-08-22: we discussed Jira item priority.
Abhijit updates (subteam-ag) ?
1. ~~Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.~~
  1. ~~Thoralf raised support request to LF. Reminders sent. Still no solution.~~
2. 2023-03-14:now has access to hw-rust, but not yet xapp-frame-rust (no need to escalate yet). CI for xapp-frame-rust works now.
3. ~~2023-03-28: working on RIC-969 and part of RIC-957~~
4. ~~2023-04-11:~~
  ~~RIC-969 first set of APIs (SDL) implemented. RNIB not yet (also under RIC-969).~~
  ~~hw world xApp should grow with the implementation of xapp-frame-rust. Initial hw-rust xapp will show use of SDL/RNIB.~~
5. ~~2023-04-25~~
  ~~working on RNIB support in rust (https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10906) and next step hw-rust.~~
6. ~~2023-05-09~~
  ~~RIC-977 (subscription API) - pls. merge.~~
  ~~RIC-978 pls. try to complete during this week.~~
  ~~issues with E2 simulator → to get in contact with Naman and Subhash~~
7. 2023-05-23
  hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
  testing of subscriptions using hw-rust (facing the E2T problem)
8. 2023-07-18: no news
9. 2023-08-01: got logs from Subhash. Now ran into issues with Dockerfile in E2T (gcc related differences between ubuntu 20 and 22)
10. 2023-08-22: next release item discussed and RIC-979
Cap Gemini updates (subteam-cg)?
~~2023-03-14~~
~~RIC-851 done~~
RIC-967 (RIC subscription delete required related changes in xApp communication) added to H release. We discussed this in a meeting and decided to implement pre and post notifications aligned with RICARCH.
~~2023-03-28, 2023-04-11, 2023-04-25, 2023-05-23: no news.~~
~~2023-05-23: presentation on RIC SUBSCRIPTION DELETE REQUIRED and communication between xApps and submgr. → DONE~~
~~2023-07-18: Cap Gemini (Gunja) conflict management presentation planned for end of July~~
2023-08-01
Gunja to present conflict management design
thinking about adding support for DU in E2T/E2M/RNIB in I release
2023-08-22:
Gunja provided reviews for DU support. Nokia to reviewed and merged
https://gerrit.o-ran-sc.org/r/q/topic:%22Multiple+E2+Node+support%22 and https://gerrit.o-ran-sc.org/r/q/topic:Multi_E2_Node
conflit management status?
Himanshu (subteam-gs) would like to work on RIC-963
code changes, but difficult to test as difficult to change order of IEs in message.
2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
2023-08-22: feedback from Anssi on submgr received and incorporating these changes, but not yet in review.
Dhiraj (subteam-r)
~~2023-05-23: ipv6 - Alexandre working on this: RIC-985. Note that this requires re-creation of most container images.~~
2023-06-06: ipv6 fix is merged. Dhiraj tried with this new version. Containers start. Good. Investigation continues - most likely fix needed in routing manager ([ brackets cause issues)and E2T (crashes to be fixed).
2023-07-18: IPv6 changes to come as review
2023-08-01: working on it.
2023-08-22:
checking compliance/license issues
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).
Alexandre (subteam-utfpr)
~~2023-05-23: no news~~
~~2023-06-06:~~
~~fixed IPv6 support in RMR - works in IPv6 only case and in case of providing specific IPv6 address. Routing mgr might require additional work.~~
~~seems also to be a bug in interface name solution in RMR. Remember to create a JIRA item (RIC-987)~~
2023-08-22: Alexandre couldn't participate, but informed after the meeting by e-mail: "My plan for the next two weeks is to fix both RIC-989 and RIC-991 issues."
Nokia (subteam-n)
~~GRPC vs RMR~~
~~2023-01-17: Still working this within Nokia. WG3 also discusses this.~~
~~2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-09, 2023-05-23, 2023-07-18: no update~~
2023-08-22: want to work on RIC-997
I release content

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
  Sprint I release dev sprint 1: Aug-21 to Sep-10
  Sprint I release dev sprint 2: Sep-11 to Oct-1
  Sprint I release dev sprint 3: Oct-2 to Oct-22
  Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
  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): link
  E2 enhancements, incl. conflict mgmt.
  RIC-993 (CG): Near-RT RIC conflict management (*)
  RIC-933 (CG) : Adding support for DU in E2T/E2M/RNIB
  RIC-994 (S): Support for E2APv3.0
  RIC-995 (S): Support for RIC Query
  RIC-996 (S) Support for Subscription modifications (dhiraj interested as reviewer)
  RIC-387 (S): Support for E2 reset from RIC to RAN (completes also RIC-383) (prio1) (dhiraj interested as reviewer, but we had earlier discussion on this)
  RIC-997 (N): Handling of RIC Error indication _during_ E2 setup
  RIC-963 (GS)modify src code to be more lenient in ordering of IEs in ASN.1
  Other
  RIC-998 (S): K8S operators for deploying/undeploy xApps(*(1))
  RIC-999 (S): A1 alignment with A1AP (still under investigation. Minimum is using correct URL) (*(1))
  RIC-954 (S): DMS Rest API support for deleting/undeploy xApps (DMS REST is 2nd ifc addressing same space as dmscli) (1)
  Already in H: RIC-985 (UTFPR) IPv6 support for RMR
  RIC-1000 (R): Support for only-IPv6 in RIC-internal interfaces
  Abhijit will create issue and send e-mail
RICAPP agenda: RICAPP Meetings.

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 12

New Version Current

Key

2023-10-24

2023-10-10

2023-09-26

2023-09-12

2023-08-29 (back to normal week, therefore only 1 week after previous meeting)

2023-08-22 (exceptionally one week later than normal)

2023-08-01

2023-07-18

2023-07-04

2023-06-20

2023-06-06

2023-05-23

2023-05-09

2023-04-25

2023-04-11

2023-03-28 (Tuesday)

2023-03-14 (Tuesday)

2023-02-28 (Tuesday)

2023-02-14 (Tuesday)

2023-01-31 (Tuesday)

2023-01-17 (Tuesday)

2023-01-03 (Tuesday)

2022-12-06 (Tuesday)

2022-11-22 (Tuesday)

2022-11-08 (Tuesday)

2022-10-25 (Tuesday)

2022-10-11 (Tuesday)

2022-09-27 (Tuesday)

2022-09-13 (Tuesday)

2022-08-30 (Tuesday)

2022-08-16 (Tuesday)

2022-08-02 (Tuesday)

2022-07-19 (Tuesday)

2022-07-05 (Tuesday)

2022-06-21 (Tuesday)

2022-06-07 (Tuesday)

2022-05-24

2022-05-11 (exceptionally Wednesday)

2022-04-26