...
| Table of Contents | ||
|---|---|---|
|
Recording
Notes:
Housekeeping:
OSC SMO Meeting Series: Reminder from previous weeks:
...
- SCCL:
- Recent "Special TOC Call" about licensing, but was not SCCL recorded
- SCCL does not address 3GPP license issue - Issue continues as before
- O-RAN Alliance will try persuade 3GPP to use SCCL ... but progress stalled.
- SCCL is currently only for O-RAN Alliance material - to be agreed to by anyone using/redistributing these specs
- OSC is a first mover to put procedures in place
- SCCL is copyright only - IPR licensing is a seperate issue and not addressed
- SCCL is not an open-source license
- We are making some progress understanding SCCL
(but we're not there yet!) - Can SCCL specs be redistributed freely?: No.
- Recent "Special TOC Call" about licensing, but was not SCCL recorded
- 3GPP:
- Surely there is potential to request a PoC/Demos/non-Commercial derogation from 3GPP
- We need to keep pushing.
- Tracy Van Brakle IIRC 3GPP does allow use for demos/poc/exhibitions ? Will check up on this! This should be enough for our requirements.
Simulators
Q&A
- N.K. Shankaranarayanan The RANSIM work in ONAP is making good progress! (Ref Krishna in SON, Slicing & OOF in ONAP)
- Tracy Van Brakle N.K. Shankaranarayanan Should all these simulators be consolidated?
- They could be more aligned, but probably should not be "merged" - they have different priorities / simplifications embedded - by design!
- But they do have some shared/shareable functions/requirements, so some alignment might be helpful.
- Tracy Van Brakle Is there something like Mininet for O-RAN/3GPP/RAN? Maybe academic contributors would be best suited to help here
- Tracy Van Brakle N.K. Shankaranarayanan Should all these simulators be consolidated?
Q&A
- Ran out of time
Copyright & Licensing
- SCCL: Any open source project can reuse SCCL artifacts - if they abide by by process for that license
- Note SCCL is not an opensource license!
- ONAP may want examine/reuse? the work in OSC for supporting SCCL?
Long discussion about 3GPP licensing: - Open/Public != OpenSource != Free
- Try to keep functions model-driven as a much as possible so loosely coupled from copyrighted specs/model, so specs are not reproduced/re-distributed.
- But this is not possible for the actual function encoding the model (e.g. a netconf server & Yang model) or function simulators/emulators, or POCs
We see no clear path forward for this very long running issue. - We need to be conservative until we have clear guidance / path forward.
- Unwilling to risk copyright or IPR infringement Likely a common-sense reuse approach is possible - with no commercial aspect involved - but we cannot assume this.