Costa Rica face-to-face (and remote)
Time zone: UTC-06:00
Table of Contents |
---|
Oct14 -10:15 to 11:45: Session with WG2
Lead: Dhruv Gupta
IM for A1:
Kevin Scaggs
https://gerrit.o-ran-sc.org/r/admin/repos/scp/oam/modeling
A broader scope of the IM work
The O-RAN common information model should align the different WGs in terms of modeling, terminology, definitions, … avoiding different modeling and solutions for the same functionalities.
- A serial number is a serial number is a serial number
- SW management is SW management is SW management
In addition, the IM work aligns the work with 3GPP (not relevant for A1 as A1 is a pure O-RAN exercise) and addresses gaps from the operator's point of view.
What are the expected deliverables, and expectations from WG2?
WG1 IM would need input from WG2 for the object and attributes to be modeled and related use case descriptions and workflows.
PM data according to WG1 Architecture and Interface specification should be streamed via VES to SMO. Are there gaps in the VES format for PM data?
Oct15 -16:30 to 18:15: Session with O-RAN-SC ToC
Status, roadmap, use cases: 2019-10-15-ORAN-OSC_rel_A-B_WG1_OAM_O1_OIM.pptx
Oct16 -16:30 to 18:15: Session with WG1
Lead: Kevin Scaggs(Information modeling part, Papyrus); Martin Skorupski(yang)
Alignment across UML Information models
- Wednesday, October 16, 2019
- Alignment across UML Information models and YANG data models
- [16:30 – 17:00] SA: Information Modeling – 30 minutes
[sko] between the UMLs
-> Common and submodules
I can take:
Alignment between UML IM and YANG Data models
-> IISOMI has a process an tooling, but it would require that UML modules follow the exact guidelines, which is problematic.
Reconcile O-RAN IM with
otheropen source project models
[sko] May statement on this is:
- VES -> 100% reused missing functions from O-RAN point of view are contributed to ONAP VES
- It is good that Kevin is active in O-RAN and ONAP modeling groups;
- We are in a process to add missing functions of 3GPP into the O-RAN IM – but this work just started:
-- identifications, names,
-- lifecycle management
-- required vs actual equipment
…
[kevin] can certainly touch on the Ves model, not sure what all is intended here. Maybe we can cover this jointly?
- Inputs for O-RAN Information Model Specification v1.0
[sko] I think this is your right? I’m not sure what is meant in details?!?!
[kevin] Not sure what all is intended here. Certainly we can touch on the A1P spec, the O1 spec, possible material on O1 / O1*, 3GPP foundational material??? Maybe this is another joint item.
- [17:00 – 18:00] SA: Information Modeling tutorial – 60 minutes + ad hoc /spare
- YANG modeling and Papyrus tool
Can you take the papyrus tool?
[sko] I can take yang modeling:
Why YANG?
What is YANG?
How is the process from UML to yang.
[kevin] I am prepared for the tutorial. Have a light deck that will define an information model, some model sample diagrams, some IISOMI guidelines, and then an outline of things that will be covered in the tutorial (getting around, creating a diagram, creating a class, creating an attribute, creating a comment, applying filters, applying an IISOMI stereotype, modifying an item’s appearance, creating a datatype, creating an association, finding stuff…). This will have to be pretty fast and simple to cover the outline.
Should be recorded and upload to wiki for study
As O1 is concerned the VES format is developed and maintained in the open source project ONAP. Now 3GPP and therefore also O-RAN IM is looking into it. Please see https://wiki.onap.org/display/DW/VES+7.1.
For the configuration part there are several information model and data models available from different SDOs and/or open-source projects: IETF, MEF, TMF, IEEE, ITU-T, ONF, OpenROADM, OpenBackhaul, ...
Also 3GPP specifies yang modules - WG1 and WG5 are contributing feedback to 3GPP: Contribution to 3GPP TS 28.541 V16.1.0
[18:00 – 18:15] Coffee Break