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 | - Non-RT-RIC: John Keeney
- Service Exposure Manager - progress!
- O-RAN Spec API compliance for R1-SME, R1-DME (spec vs code), R1-A1(spec vs code?), A1 (looks good)
- Mostly same as last week:
- SIM: Alex Stancu
- ONF deployed NearRtRic - to be considered?
- OAM: Martin Skorupski
- ongoing work on a "planned" O-RAN
- py format, lint, test
- handover areas between cells
- 5G-Core per SMO instance
- O-DU: @Vidhu
- INT: James Li(CMTI)
- pairwise testing
- sync with Taiwan lab - work with Bimo
- joint effort between INT and OSC Taiwan Lab - THANKS!!!!
|
|
00:20 | OAI / O-RAN-SC Workshop | | Chat ![(smile)](/s/z10khv/8804/xgjkrn/_/images/icons/emoticons/smile.svg) - excellent workshop
- good potential for collaboration between OAI and O-RAN-SC
- impact on OSFG Blueprint based on the workshop
- synergies
- option for end-to-end testing and demos
|
|
00:30 | Energy Saving | | - definition of rApp
- call flows → please keep N.K. Shankaranarayanan in the loop as he has all the flows "under control"
![(smile)](/s/z10khv/8804/xgjkrn/_/images/icons/emoticons/smile.svg) - as inspiration see demo below... (What is an rApp?)
|
|
00:38 | Demo | Aravindhan Ayyanathan | - life circle control of rApp
- integration with ONAP components.
- Slides:
![](/rest/documentConversion/latest/conversion/thumbnail/199295116/1) - Video:
20231121 - NONRTRIC - rApp manager.HiRes.mp4
- Makes a lot of use of ONAP ACM to support rApps that contain a composition of K8s microservices, ML Models, Policies, Workflows, Configuration, A1 Policy, etc
- Multiple rApp instances for rApp types
- rApp is Lifecycle Managed as a single composition of App elements
- Different Element types are handled by pluggable 'Participants'/Handlers
- Current Participants: K8s/Helm, A1 policy, ONAP Policy, KServe (ML), HTTP configurator, DME, others
- Adds Service Management & Exposure - SME (Not already supported in ACM)
- All produced & Consumed services are described in App package, so Service Registration & Service Discovery needs to be handled.
- Uses NONRTRIC CAPIF Core function
- R1-SME aligned
- Add Data Management & Exposure - DME (Not already supported in ACM)
- All produced & consumed Data Types are described in App package, so Data Producer Registration & Data Type Discovery & Data Job creation needs to be handled.
- Uses NONRTRIC Information Coordinator Service
- Similar to R1-DME
- Prototype rApp Package presented - Not yet Stable!
- rApps, rApp instances have well-defined state models
- Call sequences for various rApp & rApp Instance workflows presented.
- Demo:
- Show a sample rApp package
- Deploy & prime the rApp
- Create one instance - showing all its constituent parts configured, started & running. Service & Data types registed & discovered, Data Jobs created.
- Delete the created instance - showing all its constituent parts stopped & removed
- Delete the rApp & its definition - showing rApp environment cleaned up
|
|
00:76 | Meeting ends |
|
|
|
| LNF DTF | John Keeney
| Feedback |
|
00:00 | "flows" | N.K. Shankaranarayanan
| of "Project report" - SMO architecture evolving
- attraction by WG2
|
|
| PM Event Streaming | | Link to the plantUml code under version control: Jira: https://jira.o-ran-sc.org/browse/OAM-349 |
|
00: | ONAP SON/slicing Use case | | - No Update this week
- Details of using CPS is still ongoing
- Quite complex ...
- How to interact/integrate SDNR & CPS, e.g. mounted netconf device models, CM notifications
- VES vs Netconf id mapping is very tricky & must be maintained.
- Decision: CM handle in CPS is same as Netconf server ID in RANSIM & same of NF ID & same as sourceID in VES message.
- Also relevant for O-RAN SMO sequence flow work (N.K. Shankaranarayanan )
- 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)
- Next Update on CPS:
|
|
00: | SMO Deployment (Taiwan lab) | | - Ref: RSAC meeting 20/Sep - Slides & video @ RSAC Meetings
- Still very unclear how it/dep deployment works & if it is maintained.
- Work from Taiwan Lab should / could be reusable hopefully.
- Meeting with ONAP OOM team last week to iron out technicalities of deploying ONAP functions
- There have been updates since OAM function version in it/dep / ONAP worked
- e.g. VES collector needs to be built (3gpp)
- e.g. OAM gateway (sdnc, keycloak, dmaap, ves collector are now behind gateway for ease of addressing)
- SIM / topology ... still pretty similar - but very use case specific
- NONRTRIC ... Charts in it-dep/nontric directory are up to date. Charts/configurations in it-dep/smo-intall are a little dated, but not too bad.
- Main question is where does platform stop & use case start .. A lot of the charts/deployment is use case specific.
|
|
00:00 | Disaggregated SMO Flows | | - PM flows
- PM Streaming above as an example of SMOS mapped into WG10 SMO sketches/proposals
- Short update from last week:
- Discussion continue in WG1 re AI-ML inclusion in flows.
- Include service Orchestration function?
- Include Service Assurance?
- Will come back to TOC this week Oct 12
- Mapping work in O-RAN WG1 (Disaggregated SMO) to related opensource projects
- Strawman for architecture - driven by some candidate usecase flows.
- Aim for alignment across projects and across diff specs.
- Aim for common vocabulary etc.
- N.K. Shankaranarayanan working on slides now. See draft slides from previous weeks:
|
|
| Q/A | | None this week |
|
00:50 | 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