You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
LF Antitrust
See also / Co-Located
Goals
- share information between
- O-RAN-SC Non-RT-RIC
- O-RAN-SC OAM
- O-RAN-SC O-DU
- O-RAN-SC SIM
- O-RAN-SC INT
- O-RAN-SC AI/ML
- ONAP CCSDK/SDNC/SDN-R
- ONAP Usecases
- ONAP Req & ONAP TSC committees
- LFN
![(wink)](/s/z10khv/8804/xgjkrn/_/images/icons/emoticons/wink.svg)
Recording
Discussion items
Time | Item | Who | Notes |
|
---|
00:00 | Admin | | Next meetings: Please follow the calendar |
|
00:05 | O-RAN-SC | O-RAN-SC PTLs | - Release process for ONAP and O-RAN-SC
- Please see: https://wiki.o-ran-sc.org/display/REL/H+Release#HRelease-Non-Real-timeRIC(NONRTRIC)
- Still wrapping up last bits of documentation (OSC & ONAP)
- RAN PM functions - tidying up & re-releasing in maintenance release.
- Making good progress on rApp manager. More in coming weeks
- 3PP dependency updates & addressing vulnerability
- Some changes in A1-Mediator in near-RT-RIC plt in H-Release.
- Further investigation needed re effects on A1-PMS & A1-SIM
- SIM: Alex Stancu
- integration of E2 and O1 into a single simulation
- OAM: Martin Skorupski
- documentation
- yang-schema-mount support RFC8528 as required by O1 WG5
- O-DU: @Vidhu
|
|
| Q/A |
| |
|
00: | ONAP SON/slicing Use case | | - Presented plan for proposal
- ONAP SON uses case ... & others
- Coming together well now. ... counting down to M3
![(smile)](/s/z10khv/8804/xgjkrn/_/images/icons/emoticons/smile.svg) - See links below:
- Update
- CPS - how the code can be used?
- modification of yang (subset for needed use case) to be applied and
- other configurations (dataset as json)
- yangs can be also injected based on SDNC (NF yangs - in this case unmodified yangs)
- manual steps vs automation
- CPS demo: 2023-04-04 Meeting notes - Developer Wiki - Confluence (onap.org)
Issue when deployment with OOM: - oom - strimzi >
- one option to reinstall strimzi
Preparation for the next release To be on the agenda for June 13! on the Agenda at O-RAN f2f on WED. |
|
00:00 | ONAP/O-RAN-SC Cooperation/Alignment | | - N.K. Shankaranarayanan Presentation of slides discussed in past weeks at RSAC call today. See above.
- Draft Slides: (for presentation at RSAC)
- Update: (14/06/2023)
- Following presentation at RSAC
using the term "scenario" instead of "use case" red and blue colors for the names of projects/components in the figure separate slide to capture SMO interaction scenario for ES use case - RSAC Recording/ minutes will appear here soon
- Draft Slides:
![](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB)
- Older ...
- Excellent session to make people aware / motivated about overlaps, with concrete opportunity for better alignment & engagement.
- Seshu Kumar Mudiganti We also need to concentrate on Non functional aspects, such as scalability, security, energy usage. John Keeney Those are costly. Trade off against resources available for functional aspects. Do we need to find out if there is a preference for functional vs non-functional?
- Lots of hard work to do. We will try to identify concrete follow ups.
- Lets continue on the areas we already have good alignment, & strengthen focus on newer potential areas, as described int he slides.
Was topic at ONAP TSC - more interest
- use case should drive the discussions
- end-to-end use case requires rApp - thoughts?
|
|
| Meeting ends |
|
|
|
00:00 | 3GPP copyright issue | | Still! "not ok" - how to use NETCONF YANGs from 3GPP and O-RAN Problem Statement might be not fully understood. Next step: Call with Magnus Buhrgard After the call and some emails: Magnus it preparing a call with 3GPP SA5 representatives and then another ONAP LS to 3GPP The topic is on the ONAP TSC agenda tomorrow: TSC 2022-09-08 > Magnus wont give up ![(smile)](/s/z10khv/8804/xgjkrn/_/images/icons/emoticons/smile.svg) |
|
Action items