...
Benjamin Cheung (Nokia)
- Andy Mayer (AT&T)
- Ranny Haiby (Samsung)
- William DIEGO (Orange) (Orange)
- Tracy Van Brakle
- Fei Zhang (Ericsson)
- Timo Perala (Nokia)
- wangyaoguang
- Michael Salmon (VZW)
- Xin Miao (Unlicensed)
- x
DISCUSSION ITEMS LOG
Ctgry | Item | Who | Notes |
Meeting Notes Discussion |
...
ONAP/3GPP & O-RAN Alignment:
Standards Defined Notifications over VES
WIKI PAGE: ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES
...
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
IMPACT:
Key Contact - Marge Hillis
The Generic Information Modeling Template:
ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES#INFORMATIONMODELDETAILS
Is there any descoping happening with this feature towards M2 since REQ-327 at M2/M3 is status Yellow.
...
Configuration &
Persistency Service
WIKI PAGE: Configuration & Persistency Service R7
...
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
IMPACT:
C&PS PoC based on CC-SDK/SDN-C repo
Key Contacts: Benjamin Cheung Tony Finnerty & Toine Siebelink
...
...
WIKI PAGE: R7 5G Service Modeling
...
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
IMPACT: Key Contact Benjamin Cheung
The Generic Information Modeling Template: R7 5G Service Modeling#GENERICINFORMATIONMODELFOR5GSERVICE
...
Try to use the A&AI database Schema when trying to build resource info-model & align.
Import the schema, or use to take UML model to extract part and use in info-model ; auto generate papyrus
complete papyrus model generated from A&AI schema.
A&AI needs: bugs out of UML generation, to import. need support because structures in A&AI not suited to info-model relationship list central to A&AI implementation but not info oriented. Review a papyrus model, what parts are relevant and what can be ignored.
Is this generation done in A&AI mSvc today? Ans: it was a spin-off of graphgraph.
GraphGraph A&AI schema visualizer demo: Use Case Realization Call: May 1, 2019 given by pavel.paroulek@orange.com (Bill R now in charge)
Where is this UML model stored. Need an A&AI development expert. Need a roadmap.
Code should exist, need to modify it to get additional descriptors.
ACTION: William Reehil is leading GraphGraph, can bring to A&AI team. Effort? Ongoing? Ans: once it works it should be self-sustaining, may need to run it once per release. A&AI schema into UML once, and extract new portions once added. Mostly a 1-time effort.
...
Samuli scheduled a meeting for Licensing Management
(No expected licensing management modeling work)
Q: U/C & Non-functional Req. U/C help out on NFRs. U/C owner should contribute to some NFRs for components they are working on (TSC guidance). Need resources for "must have" DCAE NFRs. should allocate some space/work to help out.
...
See non-functional requirements R7 page;
Guilin Impact View per Component
COMPONENT IMPACTS TABLE
The following table shows the impacts of each requirement/use case per component
See also the Release: Guilin Impact View per Component
Use Case | A&AI | AAF | CLAMP | CCSDK | DCAE | EXT API | MODEL | MVIM | OOF | POLICY | PORTAL | SDN-C | SDC | SO | UUI | VID | VNF REQTS | VNF SDK | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
OOF SON | YES C&PS Depend | YES | YES | YES | YES | 5G Svce | YES | SD VES | YES | YES | YES | A1Adap | YES | Possible | YES | NRM | YES | Possible | E2ESlice | YES | YES C&PS Depend | YES | YES | YES | YES | YES | YES | YES | YES | PM Ctrl | YES | PnP | CMPv2 Depend | YES | YES | POB | YES | SW Upg | YES | YES | YES | C&PS | TEST | YES | Depend | Possible | YES | YES | CMPv2 | YES | YES | License Mgmt | Need input | YES double check | MDONS | Need input from team | IBN | YES | YES | YES | YES | YES | YES | AAI | AAF | CLAMP | CCSDK | DCAE | Ext API | Model | M-VIM | OOF | Policy | Portal | SDN-C | SDC | SO | UUI | VID | VNF REQTS | VNF SDK |
| ||
Use Cases | USE CASE/5G: RAN (ORAN-3GPP) Standards Harmonization with ONAP |
Use Case WIKI: MOBILITY STANDARDS HARMONIZATION WITH ONAP | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Use Cases | USE CASE/5G: OOF / SON / PCI | PoC for December 2019? SDN-R south-bound NetConf I/F w/ model and also integration with Runtime DB work. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Use Cases | USE CASES/5G: PNF S/W Upgrade | R7 Support xNF Software Upgrade in association to schema updates | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Use Cases | USE CASES/5G: Preonboarding/Onboarding | R7 PNF Pre-onboarding / (onboarding) VNF-SDK Artifact package security | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Use Cases | USE CASES: Modeling gNB/5G RAN | Align & harmonize information models to ONAP model and ONAP internal information & data model: ETSI SOL001 ... 007 with ONAP internal Model, PNFD modeling (Model S/C), 5G Model (3GPP, RAN), ORAN (WGs, RAN), Open ROADM (reconfig optical add/drop multiplexer, Optical), ONF (Optical), ISOMII (Optical), OTCC (Optical transport config & control) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Use Cases | USE CASES: 5G NRM (Network Resource Model) Configuration | wangyaoguang | June 2019 LFN DDF, titled as '5G Provisioning management service to NRM' Presentation: 5G Network Resource Model (NRM) Configuration in R6 Frankfurt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Use Cases | USE CASES: PNF / Plug and Play | Benjamin Cheung | PNF Plug and Play | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
TSC | TSC/USE CASES: Test Automation Progress | Use Case Test Automation Action Items: Use case subcommittee to provide current percentage of testing automation regarding your use case and functional requirements | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Release Tracking | R7 Frankfurt | All Team Members | Need the U/C teams to fill out the Dev. Impacts. More Generalized Use Case Template (discussed w/ Model team): | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Demos Plug- fest | Demo Plugfest | POC & Plugfest in September 2020 WINLAB? A1/O1 ORAN & ONAP Joint Plugfest Panel Discussion - Setup. Bronze Release. / Slicing, Heart Beat-Health Check | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Architecture Topics | Architecture Topics | All Team Members | Architecture Component Descriptions and Architecture Flows: https://safratech.net/onapdocs/ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Use Cases | Read the Docs | All members | DOCUMENTATION - Documentation (Read the Docs) - M1 - M4
"Are you referring to MS1 and the preliminary documentation? https://wiki.onap.org/display/DW/Frankfurt+Documentation Multiple Repo / Use Cases are under Integration Repo VNFREQ has Repo / Verified U/C in Integration Repo Andreas Geissler - Discussed should put docs on the readthedocs (not in wiki) should have own Repo for Use Cases or Req sub-committee own repo | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Use Cases | Req / Use Case Way of Working Process (WoW) | All members | ONAP Use Case / Requirements Teams Process Way of Working (WoW) |
DCA&E Use Case Analysis
DCA&E impacts w/ use cases and requirements
R7 Release tracking PER component impact: Guilin Impact View per Component
R7 Cross-interaction table: Guilin (R7) - Use Cases (and Requirements in Use Cases)
...
USE CASE
REQUIREMENTS
...
E2E Network Slicing
...
WIKI PAGE: E2E Network Slicing Use Case in R7 Guilin
JIRA: Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-342
IMPACT: Key contact: Swaminathan Seetharaman Sandeep Shah guochuyi
NSSM / E2E Network Slicing Use Case in R7 Guilin#GENERICINFORMATIONMODELFORE2ENetworkSlicing
...
A1 Policy Adaptor
ORAN/ONAP/3GPP
Harmonization
WIKI PAGE: ONAP/3GPP & ORAN Alignment: A1 Adapter extensions
...
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
IMPACT: Key Contact Michela Bevilacqua John Keeney
Exchanging Policies across API (external to ONAP), investigate to see if it necessary to model policies.
Ben has John to present on U/C realization call on A1 adaptor policy.
| |||
SUPPORTING DOCUMENTATION
Document | File | ||||
---|---|---|---|---|---|
Presentation slides name | ONAP_Transport_Slicing_briefing.pptx | height | 250 | ||
RECORDING for U/C Realization
...