You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Current »
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/-mqwupc/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 | - O-RAN-SC ToC
- OSFG
- CVE and how to process them....
- on agenda for next meeting: Demos for O-RAN f2f Oct28+
- K-Release planning
- use case driven implementation
- demonstrator in Montreal (O-RAN f2f Oct 17?)
- A1 controller from ONAP
- NBI is now spec in O-RAN → backward compatibility is affected
- team is thinking about how to address it.
- bug fix will be available soon - for ONAP Montreal and New Delhi
- focus more on integration → to help Bimo
- bootstrapping service manager in smo-install
- doc for R1 based policy management
- by Subhash (AIMLFW)
- add AI to the NonRtRic/NearRtRic integration
- needs to be architect-ed
- init on a wiki
- SMO deployment vs RAN deployment
- OAM: Martin Skorupski
- K-Release
- YANG analysis: https://lf-o-ran-sc.atlassian.net/wiki/spaces/OAM/pages/37912577/O-RAN+YANG+published+in+2024-06
- will be translated into CRs to WG5 adn WG10
- What do you want?
![(smile)](/s/-mqwupc/8804/xgjkrn/_/images/icons/emoticons/smile.svg) - WG11 Security updates
- WG10 OAM updates
- Topology? RAN, Transport, Cloud, ....
- 3GPP → ?
- ietf-network-topology → yang
- O-RAN? → yang!!?!
- onf:tapi→ yang
- TMForum → OpenApiSpec
- How to link/relationship between model/nodes?
- externalizing the relationships!!!
- What should be demoed in October O-RAN f2f?
- hybrid vs hierarchical all at the same time via on O-DU....
- definition of init O-RU configuration for SIM
- stndDefined newAlarms and clearedAlarms should be consumed by SDN-R from kafka - input from O-DU team
- SMO: Seshu Kumar Mudiganti
- by John Keeney: topo and inventory efforts
- should be model driven but tests are impacted
- aligned with 3GPP and enhanced → pre-spec
- rough cloud-topo model (pre-spec)
- concept of grouping topos - already in API
- concept of tagging topo entries (decorators) - supporting queries
- references:
- Minutes & Meeting: Meeting notes
- J Release planning
- integration point OAI, Nephio, O-RAN-SC
|
|
00:20 |
| Q/A | @Deena: Non-RT-RIC and keyclock details: - Question about CAPIF & Keycloak integration
- When Service Manger performs a discovery request, how is it checked which APIs the invoker can access?
- If invoker is registered - All registered services are returned (depending on filter passed to query)
- Currently, our ServiceManager/SME implementation does not perform any authorization or access control check. Basically, all services are discoverable right now. The only requirement is that the invoker is actually registered.
However, authentication, authorization and access control is needed in any real deployment. We delegate this to the Service Mesh and API Gateway – to do RBAC at least. We show an assortment of options of how to enforce service/data exposure & access on: ONAP takes a similar approach: We feel that the OSC SMO deployment is not intended for commercial use or real-world deployments, so we don’t think the OSC deployments needs/should-have this AAA/exposure enforcement enabled. - John Keeney (Ericsson EST) unlikley to work more on this in this release
- Can 3GPP & ORAN stuff be reused commercially - Is there a license issue
- "IANAL" - Just make sure not to redistribute any 3GPP or O-RAN copyrighted material. Be prepared to FRAND license any IPR from copyright & IPR owners. OSC code however is Apache 2, so reuse should not be difficult.
|
|
00:25 | Demo how to bootstrap SME Service Manager with existing SMO platform service. | | NonRTRic Demo - (See recording at 0:22:50)
- Demo how to bootstrap SME Service Manager with existing SMO platform service.
- Services can be described in a yaml file and bulk loaded by a script at SMO deployment startup time
- https://gerrit.o-ran-sc.org/r/gitweb?p=it/dep.git;a=tree;f=servicemanager-preload
- Sample yaml files for SMO, NONRTRIC-only and the script to use them.
- Tricky dealing with Services where URL has a path parameter
- URI will have regex patterns/capture groups - and returned/registered/queried URI segments need to be post-processed to remove these.
- Not sure how CAPIF supports path parameters - so this may not be spec-compliant - TBC
- No security enforcement (See AOB below) - that needs to be done separately depending on commercial/field deployment scenarios - e.g. in Service Mesh.
- Trade-off how detailed a Service/API registration should be
- e.g. coarse grained, where just the 'root' resource is registered, so likely some operations/paths may fail when invoked (e.g. not found, operation not supported, unauthorized, invalid requests, etc)
- e.g. very fine-grained, where all paths are individually registered, and their allowed operations (reasonable expectation invoke will be able to invoke discovered service/resource/operation results)
- Script can be called any time - e.g. at runtime - with new different config/yaml files
- REST API is still available for any operation to be performed any time.
|
|
01:10 | Meeting ends |
|
|
|
Action items