...
| Ctgry | Item | Who | Notes | ||||||||||
Pltfm | PLATFORM TOPICS: Controller to NF Association | R5/R6 Topic See Slides Nov 6, 2018. Development of Controller to NF assignment association S/W. CDS, VF-C, APP-C, SDN-R, SDN-C; will the CCSDK "merging" of controllers happen in R6? | |||||||||||
| Pltfm | PLATFORM TOPICS: Data Persistency, RunTime DB | STATUS: Work for RunTime DB completed, not merged in R4 Dan Timoney moved to R5, one Jira for RunTime DB. One issue about merging. ONAP code added can take a test ONAP deployment to have the ConfigDB work. USE CASE REALIZATION MEETING (Notes 2019-01-30) U/C Cross-Interaction, Persistency | |||||||||||
| Pltfm | PLATFORM TOPICS: Controller LCM API Evolution | Goals (Architecture Evolution)
Present at the Arch S/C Apr 9 (Tue) second presentation. | |||||||||||
| 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: Licensing Management | New U/C added to the 5G Use Cases for Licensing Management Use case Wiki: LICENSING MANAGEMENT | |||||||||||
| Use Cases | USE CASE/5G: OOF / SON | PoC U/C will happen in WinLab. To meet time lines do those parts in Windriver focusing on DCAE, Policy and OOF. Jira SDN-C (Dan Timoney) pushed El Alto (the Maintenance Release). | |||||||||||
| Use Cases | USE CASES: BBS U/C Evolution | BBS Evolution - Slide set linked in R6 proposed U/C. List of proposals & functional requirements.
| |||||||||||
| Use Cases | USE CASES/5G: PM Dictionary/FM MD GUI | FM META DATA & PM DICTIONARY in R5 | |||||||||||
| Use Cases | USE CASES/5G: PNF S/W Upgrade | PNF software upgrade in R6 Frankfurt | |||||||||||
| Use Cases | USE CASES/5G: Preonboarding/Onboarding | PNF PREONBOARDING / ONBOARDING in R5 | |||||||||||
| Use Cases | USE CASES: IoT Service Creation | IoT Create Services on 5G June 19, 2019 | |||||||||||
| Use Cases | USE CASES: Modeling gNB/5G RAN | Align, harmonize, reconcile various information models to ONAP model: Expand & verify model and harmonize with the 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 that need transport models need some model consistency. - Try a Use Case with extended ONAP model & real equipment. | |||||||||||
| Use Cases | 5G NRM (Network Resource Model) Configuration | wangyaoguang | Presented at the 2019 June LFN DDF, titled as '5G Provisioning management service to NRM' Presentation scheduled for Aug 8, 2019 | ||||||||||
| Arch | Architecture S/C PNF POB/OB Flow | Arch S/C Information Flows: New Information flow for Preonboarding/Onboarding xNF packages/resources. | |||||||||||
| Pltfm | A&AI | A&AI updates | |||||||||||
| TSC | TSC: PoC Definition | POC definition | |||||||||||
| TSC | TSC/USE CASES: Test Automation Progress | Use Case Test Automation Action Items: Use case subcommittee to reach the Dublin use case owner to provide the following information. what's the current percentage of testing automation regarding your use case and functional requirements; what will be the plan to be 100% and constraints (resources availability etc.) | |||||||||||
| R6 Frankfurt / M0 | Need the U/C teams to fill out the Dev. Impacts. More Generalized Use Case Template (discussed w/ Model team): | ||||||||||||
| VID: Service Models Browser Orchestration | VID: Service Models browser - display orchestration type (macro / a`la carte) use-case. This use-case requires us to extend the AAI data-model, with an additional field, related to Service Model. This field will be used later on to indicate in VID the Service Model orchestration type. A&AI Epic 2594
| ||||||||||||
VID IMPACTING USE CASES
| USE CASE | IMPACTS |
|---|---|
| PNF / Preonboarding Onboarding | No Impact |
| PNF / Plug and Play | Migration of existing PNF PnP sub-workflows to a new BB approach (probably we will be creating 4-5 new BBs). VID Impact: Within “old” VID macro orchestration pages, a special field to provide a pnf-id parameter (shall be actually called “correlationID” or “PNF correlationID”) has been displayed under the following conditions:
When we migrate to BB approach, we`d keep the possibility to provide this parameter to the SO API call as input. How this will change with SO/BB approach, and with new VID GUI targeted at macro (GR) flows – we`d see exactly, after we execute some tests with VID. We`d have to check, what capabilities and conditions could be applied to display and process this “PNF Correlation ID parameter”. Can the same BBs could be re-used in “standard” vCPE use-case. We`re looking at a generic solution, and we`d probably display this additional field, when we figure out, that there is a PNF resource used in a Service Model. |
| PNF / Software Upgrade | trigger PNF Sw upgrade workflow, providing corresponding parameter values |
| PNF / Configuration with NetConf | No Impact |
| 5G / 5G Service Modeling | No Impact |
| 5G / Bulk PM | No Impact |
| 5G / PM Dictionary | Will Generic Artifact Browser be available in VID? |
| 5G / 5G Meta Data | Will Generic Artifact Browser be available in VID? |
| 5G / OOF SON (PCI) | Display VID updates to support Cell management? Not listed in Wiki, need to discuss w/ Ittay. |
| 5G / E2E Network Slicing | ??? |
5G / RAN ORAN 3GPP Standards Harmonization | No Impact |
| 5G / Runtime DB | Display of RunTime DB information; Design Time view of Run Time DB info Need to discuss w/ Ittay |
| 5G / NRM CM w/ RESTful HTTPS | No Impact ??? |
| 5G / Licensing Management | No Impact |
| SERVICE RESOLVER | No Impact ??? |
| SCALING | Listed as Impact on R6 Release Page But No impact stated on Wiki. |
| Mobile Service Chaining & Service Selection | No Impact ??? |
| BBS | No Impact ??? |
| CCVPN | No Impact ??? |
| Control Loop | No Impact |
| Multi Domain Optical Service L0/L1 Orchestration | No Impact ??? |
| CHANGE MANAGEMENT | IMPACT (but not described), None Listed but eMail response said potential |
| HPA | No Impact ??? |
| RUN TIME SECURITY | No Impact ??? |
| K8S Based Cloud Region Support | No Impact ??? |
| DAaaS | GUI/CLI based configuration of stack ?? (will this be VID change??) |
| 3rd Party Operational Domain Manager | IMPACT (but not described) |
KEY PRESENTATIONS & OVERVIEWS & RECORDINGS
...