...
| Ctgry | Item | Who | Notes |
| Meeting Notes Discussion |
| ||
| 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 | yaoguang wang | 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
ADCA&AI 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 | DESCRIPTION & DISCUSSION | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| CMPv2 ENHANCEMENTS | WIKI PAGE: R7 Certificate Management Protocol (CMPv2) JIRA: IMPACT: | ||||||||||
| OOF SON PCI USE CASE | WIKI PAGE: R7 OOF SON Use Case JIRA: IMPACT: x | ||||||||||
| STANDARD DEFINED VES EVENT | WIKI PAGE: ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES JIRA: IMPACT: New Standard Defined (stndDef) VES event for DCAE VES Collector. Uses VES 7.2 standard. | ||||||||||
E2E Network Slicing | WIKI PAGE: E2E Network Slicing Use Case in R7 Guilin JIRA: IMPACT: IMPACT: (see Jiras) Impacts to mS to extract fields from SDC. Need to investigate. E2E Slicing. Key contact: Swaminathan Seetharaman | ||||||||||
Configuration & Persistency Service | WIKI PAGE: Configuration & Persistency Service R7 JIRA: IMPACT: Test Only
IMPACT: X | ||||||||||
| Bulk PM / PM CONTROL Extensions | WIKI PAGE: Bulk PM/ PM Data Control Extension JIRA: IMPACT: X | ||||||||||
| Intent Based Networking | WIKI PAGE: Intent-Based Network JIRA: IMPACT: INVESTIGATION. Identified A&AI. Contact Huang ZongHe . Presented at the Architecture S/C. Possibly moved to POC status: Linked to: Arch S/C recordings: ONAPARC 2020 Meetings (Copy) Presentation https://jira.onap.org/secure/attachment/16127/16127_ONAP_Proposal_IBN+V1.7.pptx | CC VPN Transport Slicing | WIKI PAGE: Guilin release - functional requirements proposed list#ccvpnTransportSlicingCCVPN-TransportSlicing An End-to-End 5G Network Slice consists of RAN, Transport and Core network slice sub-nets. This requirement is devoted to the realization Transport Slice sub-nets. It implements TN NSSMF, of which the functionality includes the modeling, orchestration and assurance of a Transport Slice. While TN NSSMF is a self-contained entity and thus this requirement can be independent, ensuring the integration with the E2E Network Slicing is an important aspect of this requirement. Standards-based interfaces and architectural framework (e.g., ETSI ZSM, IETF) are used by this requirement. Storing Slice ID, and which Element participating in the Slice. Swaminathan Seetharaman ; https://wiki.lfnetworking.org/display/LN/2020+June+Virtual+Recordings JIRA: IMPACT: | ||||||||
| PNF Software Upgrade | WIKI PAGE: Support xNF Software Upgrade in association to schema updates JIRA: IMPACT: Lead: Zu Qiang (Ericsson) , Support xNF Software Upgrade in association to schema updates. VNF S/W version into A&AI. Done in eComp? ported to ONAP (confirmed) (from Chris Rapposelli-Manzo). Email sent from Lukasz to Zu Qiang (Ericsson) Generic-VNF object in A&AI will have software-version attribute. It should be optional and should be of string type. Exemplary values are: "1.0", "1.0.1", "2.0.0" It is in the S/W but Not in Swagger file yet (version 19). Perhaps swagger not generated yet. How is the swagger file updated? Targeted for V20? still needs to generated and published. (will be other changes too) | CNF Orchestration | |||||||||
| ETSI Alignment | WIKI PAGE: Guilin release - functional requirements proposed list and model planning page: ONAP R7 Modeling High Level Requirements JIRA: IMPACT: Note: if AAI needs some minor schema changes for ETSI modeling, one of the ETSI-Alignment participating companies will update the AAI schema. It is part of the user stories. Fernando Oliveira leading this work. Byung-Woo Jun | ||||||||||
. | |||||||||||
MDONS EXTENSION | WIKI PAGE: (NONE) JIRA: | Multi-Tenancy | WIKI PAGE: ff JIRA: How to support multiple ONAP components on same cluster. Access Control. Can't tag PNFs.IMPACT: Lead Olivier Phénix , Mike Elliott (AMdocs OOM) schema, multiple tenant pointing to same A&AI instance. Retreive operate on their own PNFs. (not available in A&AI yet). X. |
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" A&AI DCAE NFRs. should allocate some space/work to help out.
| NFRs | Description |
|---|---|
| Guilin release - non-functional requirements proposed list#ONAPmustcompleteupdateofthejavalanguage(fromv8-%3Ev11) |
...
See non-functional requirements R7 page; | |
COMPONENT IMPACTS TABLE
The following table shows the impacts of each requirement/use case per component
...