You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
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 Q: Shall we move the meeting to an earlier time slot? - to be discussed next week. Doodle for days and times - Mon 14:00 UTC (conflict o1 interface meeting)
- Tues 14:00 UTC
- Wed 16:00 UTC as now
|
|
00:15 | O-RAN-SC | O-RAN-SC PTLs | - Continuing as per last week : No specific update this week
- Alot of work in JDK 17 & Springboot 3 updates
- Consolidating PM data exposure in new repo for RAN PM functions
- (R1) Service Exposure & Management
- CAPIF Aligned Service Registry
- Secured/Sandbox execution environment
- Controlled access & exposure of service to/from rApps
- 2023-04-19: good progress - maybe a demo in a couple of weeks.
(R1) Data Management & Exposure - File-based PM data → InfluxDB
- Previous focus on PM data - but will extend to other use cases too
- Aim to work with AIML project for Training (and Inference ?) data access
rApp Management - Built on ONAP “Automation Composition” model & platform to implement rApp use cases
- Inference Services in rApps
- Added a 'KServe Participant'
- rApp-specific extensions needed
- Packaging, Onboarding & Orchestration of rApps
- rApp-specific packaging & Onboarding
- Aim to align with / inform ongoing work in O-RAN (& OSC) about Common App packaging & Onboarding.
- (rApps with & without µService)
- Overlap with Service Exposure work to examine role of an rApp Manager to support controlled exposure & LCM of µService and non-µService parts of an rApp
Continued A1-Policy & A1-Enrichment-Information evolution (& R1-A1) - A1 Spec evolution
- A1-Policy work in ONAP (continues in ONAP London) - candidate for R1-A1(P)
- A1-EI management as part of DME - candidate for how to include A1-EI in R1-DME
- 2023-04-19: fine grain access control
- Sample use cases (rApps)
- Requirements Drivers for rApp/R1 development
- High degree of cross-project integration activity
Testing, Maintenance & Housekeeping - Function Test & Integration Test environment,
- Support integration, deployment & configuration of SMO/Non-RT-RIC related functions & usecases in OSC Integration env.
- Project coordination, Documentation, Delivery, Reporting, Cross-project alignment, Community demos, O-RAN Standardization support, etc.
- test deployments
- SIM: Alex Stancu
- WG4 OFHM - supervision in NTS (O-RU function)
- available for NTS-O1 1.6.3
- PM File generation
- update for the stndDefined fileReady → 3GPP REL-18
- John Keeney Alex Stancu : req: file ready event - template for 3gpp-xml file → timestamps - generated provided by John
- same certs for FTPes
- each sim instance will create its own file (file per node)
- OAM: Martin Skorupski
- stndDefined examples for
- 3GPP based FM, CM
- OFHM based FM, CM
- OFHM supervision mechanism.
- O-DU: @Vidhu
- Discussion: about PM VES Streaming
- SMO: Seshu Kumar Mudiganti
- next item
- working on logistics
- merger of ONAP SO and O-RAN-SC SMO
- separation for business logic and deployment
- SMO disaggregation on next weeks agenda - same as RSAC meeting
- working with nephio - for integration with O-RAN Specs
- INT: James Li(CMTI)
- h-release - add more automation - using x-testing
- near-rt-ric: deployment with xApps - using existing robot also from it/test
- different flavours of deployments
|
|
00:55 | O-RAN SMO | | Presentation in the O-RAN-SC SMO meeting today - Demo (add link here)
- potential discussion item: multiple orchestration technologies?
- answered by: separation for business logic and deployment (see SMO section above)
- related to k8s operators
|
|
00:00 | ONAP SON/slicing Use case | | - 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
|
|
| Meeting ends |
|
|
|
00:00 | ONAP/O-RAN-SC Cooperation/Alignment | | - N.K. Shankaranarayanan Presentation of slides discussed in past weeks at RSAC call today. See above.
- Slides:
- 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.
|
|
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