You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 6
Next »
Please add yourself. Thanks!
See also
Goals
- share information between
- O-RAN-SC Non-RT-RIC
- O-RAN-SC OAM
- O-RAN-SC SMO
- ONAP CCSDK/SDNC/SDN-R
- LFN
![(wink)](/s/z10khv/8804/xgjkrn/_/images/icons/emoticons/wink.svg)
Recording
link to the zoom (mp4 format) - Note: the recording failed ![(sad)](/s/z10khv/8804/xgjkrn/_/images/icons/emoticons/sad.svg)
Discussion items
Time | Item | Who | Notes |
---|
00:00 | Admin | | Next meeting: 2020-11-11 |
00:05 | O-RAN-SC | O-RAN-SC PTLs | Status reports: - SMO:
- ongoing - see last weeks meeting minutes
- LNF project onboarding
- Non-RT-RIC:
- focus O-RAN-SC to use the ONAP Adapter → Doc
- testing an demos in preparation
- Licensing issues becomes now also in issue
- SIM:
- sim/o1-interface: updated code in gerrit
- working on LF Jenkins jobs for the new code
- final preparations for Cherry (INT specific tasks)
- OAM:
- ONAP SDN-R code adopted for ODL Aluminium → module tests ongoing
- RestConf to NetConf subtree filtering
- IPv6: End-to-End tests moved to Honolulu
- GuiCutThrough feature under investigations based on augmentation of ietf-systems
|
00:16 | Use Case | | Use Cases Please see page #2 for details: 5G Use Cases in R7 Guilin. - very first view - to be discussed further:
- BULK PM - PM data collection and control
- 100% aligned with O-RAN interface specification; use case was demonstrated several times
- PM collection mechanism aligned to 3GPP
proposal: Check updates of 3GPP pm xml file format and updates of VES messages
- OOF -SON PCI (5G)
- 5G SERVICE MODELING & DEFINITION (5G)
- CONFIGURATION PERSISTENCE SERVICE (CPS)
- ONAP provides a persistency data service that can be used for any XNF configuration data (Poc in Rel G, new ONAP component in Rel H)
- CPS is model driven and it may use any YANG model adopted by any xNF (e.g. 3GPP YANG models and vendor extensions)
- open: is the abstraction by 3GPP and O-RAN sufficient for all the targeted use case - how do µServices, rApps make use of C&PS, if C&PS is device model driven and not service model driven?
- Idea: Contribution of consumer view
- xNF LICENSING MANAGEMENT
- not subject of O-RAN (yet)
- proposal: defer or contribute terms, definitions, specifications to O-RAN
- ONAP/3GPP & ORAN Alignment
- O-RAN O1 data models are augmenting 3GPP data models
- A1, R1, O2 data models are subject of O-RAN only
- ONAP/ORAN Alignment -A1 adapter
- Detailed alignment/collaboration needed with O-RAN-SC Non-RT-RIC project (For details please reach-out to John Keeney)
- 5G NRM Simulator in ONAP (CM)
- CM is part of O-RAN OAM Architecture and OAM interface specification
proposal: as a staring point the 3GPP NRM yang models V16.0.5 from July 2020 should be used - for VES the version 7.2 is specified. - note: 5G NRM is not a ONAP Rel G UC
- E2E NETWORK SLICING (5G Use Case)
- Network Slicing is not part of 3GPP NRM so far
proposal: waiting for 3GPP and O-RAN specifications - V17 draft is available
- PNF sw upgrade in ONAP is aligned to ORAN O1 specification
- xNF Package and onboarding in ONAP
- xNF Package complaiant to ETSI SOL004, - additional xNF artifacts have been introduced and supported: - VES event, and PM dictionary artifacts according to VES event registration specifications - Additional artifacts (e.g. xNF YANG model) - VES specification are defined by ONAP in VNF requirement project
- Control Loop in TOSCA PoC
- A Control Loop and Control Loop components havw been defined in TOSCA and deployed
Feedback from John Keeney: Request for chat for such use cases in Honolulu. |
00:45 |
| @Mahesh | Application Package Structure Info from Michela Bevilacqua - API schema definition for YANG and VES
On the agenda for next week - thanks!!! ![(wink)](/s/z10khv/8804/xgjkrn/_/images/icons/emoticons/wink.svg) |
00:55 |
| | Questions and Answers - Non-RT-RIC: External API vs. config map
|
END
Backup |
|
|
|
00:10 |
| Mahesh | Postman scripts to interface with the SMO and in turn test O1 interface between the SMO and different parts of O-RAN instances of O-CU, O-DU, O-RU and RIC using these models. - yang modules
- framework for test and validate CM
share content in in SMO gerrit and create wiki linking to the same source - Working on a framework for vendors for OAM/YANG tests
- O-RAN-SC to host the framework
- Postman and vsCode as RestClients
- Alex about to setup a SIM in OSC lab - involve Rittwik in a O-RAN private lab
- OpenFronthaul
- 3GPP models are considered.
Feedback from Rittwik - SMO in T-Labs
- how to run Netopeer server - req to Felix (O-RAN-SC INT PTL)
- Alex asked for VMs
Init script (Postman) for O-RAN OAM FH M-Plane (o-ran-interface.yang augmenting ) interface demoed RFC8040 (RestConf by IETF) support supported by ODL |
00:25 |
| | Konrad is absent this week. The presentation will be made when Konrad is available. O-RAN Component deployment The question is: How to deploy the red colored CNFs/VNFs of the O-RAN-Architecture? - CNF for O-RAN-components
- model of CNF - how to be configured, how many components, blueprints
- CDS model needs to be created
- Network-service based on several CNFs
- CNF types
- Near-RT-RIC
- O-CU-UP
- O-CU-CP
- O-DU
For detailed discussion the following page was created:
Package - for Network Functions (priority)
- for Network Service (second step)
CNFs or VNFs - both should be considered
- let's start with CNFs first
- VNF is considered as additional option
- no CNFs and VNFs combined in a single package
- maybe not for rApps →
- VNF should take care about internal CNFs
|
Action items