Req Id | Functional Requirement | Priority as initially submitted | Agreed priority for R2 | Summary | Source / Use Case | New Component / Enhancement | Related components / Comments | Comments | Proposed Grouping / Harmonization | Commitment | |||
People/companies willing to work on the requirement | |||||||||||||
R1 | Support for PNF - Onboarding | https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Summary+of+Functional+Platform+Requirements+arising+from+5G+Use+Case | 5G | New | SDC, AAI | Modeling / On-boarding | |||||||
R2 | Support for PNF - Data Collection & Monitoring | 5G | New | SDC, DCAE, Portal | Modeling / On-boarding Monitoring | ||||||||
R3 | Support for PNF - Configuration & Control | 5G | New | SDC, SO, SDN-C, APP-C, AAI, Portal | Modeling / On-boarding | ||||||||
R4 | Slice Management - Orchestration & Control | 5G | SDC, SO, SDN-C, APP-C, Portal | Applicable to slicing subcase only | ? | ||||||||
R5 | Slice Management - Definition | 5G | SDC, AAI | Applicable to slicing subcase only | ? | ||||||||
R6 | Slice Management - Data Collection & Monitoring | 5G | SDC, DCAE, Portal | Applicable to slicing subcase only | Modeling / On-boarding - Monitoring | ||||||||
R7 | Slice Management - Composition | 5G | SDC, Portal | Applicable to slicing subcase only | Slice management | ||||||||
R8 | Optimization - Configuration & Control | 5G | SDC, SO, SDN-C, APP-C, Policy, Portal | Slice management | |||||||||
R9 | Optimization - Data Collection & Monitoring | 5G | SDC, DCAE, Policy, Portal | Modeling / On-boarding - Monitoring | |||||||||
R10 | Optimization - Onboarding | 5G | SDC | Modeling / On-boarding - Optimization | |||||||||
R11 | Optimization - Conflict Resolution | 5G | New ?, SDC, Policy | Modeling / On-boarding - Optimization | |||||||||
R12 | OOF - Optimization | 5G | OOF | Optimization | |||||||||
R13 | OOF - Multi-cloud | 5G | OOF | Optimization | |||||||||
R14 | SDWAN service onboarding | 1 | https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Summary+of+Functional+Platform+Requirements+arising+from+SDWAN+Use+Case | SDWAN | Enhancement | SDC, SO, AAI, DCAE, Policy | Modeling / On-boarding | ||||||
R15 | Support for selecting external or home brewed SDWAN controller | 1 | SDWAN | Enhancement | Resource Orchestrator, AAI | ? | |||||||
R16 | Plugin/s for interaction with external system/s | 1 | SDWAN | New | specificSdwanDriver, OOM, RO | ? | |||||||
R17 | Service Creation of SDWAN branch | 1 | SDWAN | Enhancement | VID, Resource Orchestrator, specificSdwanDriver, AAI, ESR | Modeling / On-boarding | |||||||
R18 | Overlay data collection | 2 | SDWAN | Enhancement | specificSdwanDriver, DCAE | Modeling / On-boarding - Monitoring | |||||||
R19 | Correlations between overlay and underlay | 2 | SDWAN | Enhacement | DCAE - Holmes | ? | |||||||
R20 | Dynamic Bandwidth Management for SDWAN | 2 | SDWAN | Enhacement | DCAE-holmes, Policy, specificSdwanDriver, Resource Orchestrator, AAI | ? | |||||||
R21 | Lifecycle management of External SDWAN controller in Data Center | 1 | SDWAN | Enhancement | VID, AAI, SDNC, VF-C | External system registration | ? | ||||||
R22 | Life Cycle management for multi vendor VNF, integration with SDWAN | 2 | SDWAN | Enhancement | VID, AAI, SO, RO, SDNC, VF-C | Manage Life cycle and service integration for 3rd party VNFs | ? | ||||||
R23 | Residential vCPE Multi-cloud support | https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Missing+Platform+capabilities | R-vCPE | Modeling/Onboarding | |||||||||
R24 | Support real-world service design in SDC with standard based TOSCA model | R-vCPE | Modeling / On-boarding | ||||||||||
R25 | Unify all design tools (DG, Policy, DCAE Template, CLAMP, Holmes, A&AI schema, etc) and make them as integral part of service design | 1 |
| Modeling / On-boarding | |||||||||
R26 | VNF image management | Change Management | AT&T | ||||||||||
R27 | DNS name configuration | ? | |||||||||||
R28 | 2 | https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Missing+Platform+capabilities | Performance | The capability orchestrate and configure VNFs with EPA requirements. | Modeling / On-boarding - EPA | ||||||||
R29 | 4 | Change management | Support of locking mechanism that can prevent different parts of ONAP from accessing | Change Management | AT&T | ||||||||
R30 | 1 | Change management | Ability to stitch together functionality provided by ONAP components to achieve an E2E management task. | Change Management | AT&T | ||||||||
R31 | 1 | Support PNF modeling and associated workflow design in SO. | Modeling / On-boarding | ||||||||||
R32 | 4 | The capability to model and orchestrate services which are composed of other services, recursively | Modeling / On-boarding | ||||||||||
R33 | 5 | The capability to model and orchestrate chains of connected services. | Modeling / On-boarding – Service chaining | ||||||||||
R34 | 2 | The capability to modify existing services | Modeling / On-boarding – service chaining | ||||||||||
R35 | 4 | Allow services to have set of owners. | ? | ||||||||||
R36 | 1 | The capability to model complex VNFs composed of VNFCs which are scaled independently. | Modeling / On-boarding – VNF control | ||||||||||
R37 | 2 | Proposed in ONAP-OF HAS. | Homing functionality for choosing the appropriate MultiCloud instance for ONAP components and VNFs in a Distributed DC deployment | Optimization | |||||||||
R38 | 3 | The capability scale-out a VNF or VNFC by adding vServers. Also refer to this Scale Out Use Case Page for more details | Modeling / On-boarding – VNF control | ||||||||||
R39 | 3 | The capability to scale-up a VNF or VNFC by adding resources. | Modeling / On-boarding – VNF Control | ||||||||||
R40 | vCPE-Enterprise service onboarding
|
1
| https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Summary+of+Functional+Platform+Requirements+arising+from+E-vCPE+Use+Case | E-vCPE |
Enhancement
|
SDC, SO, AAI, DCAE, Policy
| Modeling / On-boarding | ||||||
R41 |
vCPE service data collection
|
2
| E-vCPE |
Enhancement
|
SDN-C, DCAE?A&AI
|
Statistics collection on vCPE/ link connection/ topology /delay/traffic utilization/jitter, etc.
| Monitoring | ||||||
R42 |
Path Selection
|
2
| E-vCPE |
New
|
SDN-C,DCAE, A&AI,PCE
|
Do the selection of different access SPs networks or different core networks( MPLS/Internet) within one SP
| Routing | ||||||
R43 |
Overlay connection type selection
|
1
| E-vCPE |
Enhancement
|
Portal, SO, SDN-C
|
IPsec/vxlan selection
| ? | ||||||
R44 |
Order management
|
2
| E-vCPE |
New
|
A&AI, SO
| Deal with the order received from BSS, and manage different types of ongoing orders | ? | ||||||
R45 |
Intelligent path analysis
|
3
| E-vCPE |
New
|
NAI
| Data detection, prescription and prediction; Provide traffic pre-scheduling, policy pre-setting… | ? | ||||||
Atomic Capability Management | 1 | E-vCPE | New | SO | China Telecom | ||||||||
VNF onboarding | 1 | E-vCPE | Enhancement | SDC,SO,AAI,APPC/VF-C,Policy | vNAT onboarding(vCPE,vAAA,vDHCP,vFW have been realized) | ||||||||
| VNF instantiation | 1 | E-vCPE | Enhancement | Portal,SO,AAI,VF-C,MULTI-VIM | vNAT instantiation (vCPE,vAAA,vDHCP,vFW have been realized) | ||||||||
| VNF Configuration | 1 | E-vCPE | Enhancement | SO ,VF-C,MULTI-VIM | vNAT configuration(vCPE,vAAA,vDHCP,vFW have been realized) | ||||||||
R46 | VNF autoscaling (in/out) | 3 | https://wiki.onap.org/pages/viewpageattachments.action?pageId=6593603&metadataLink=true | VoLTE | Enhancement | Merged from Capacity based scaling and Policy driven scaling. Also refer to this Scale Out Use Case Page for more details | |||||||
R47 | VNF manual scaling (in/out) | VoLTE | New | Manual scaling triggered from portal. Also refer to this Scale Out Use Case Page for more details | |||||||||
R48 | Configuration audit | 3 | VoLTE | Enhancement | |||||||||
R49 | Resource dedication | 3 | VoLTE | Enhancement | This came out of one of the other use cases. It’s the capability to specify constrains on VNFs (e.g. this VNF needs to be on it’s own dedicated server) | ||||||||
R50 | Policy driven/optimal VNF placement | 3 | VoLTE | Enhancement | |||||||||
R51 | Framework for integration with OSS/BSS | 3 | VoLTE | Enhancement | |||||||||
R52 | Provide powerful test and debug environment/tools | 1 | |||||||||||
R53 | Enhance SDC capabilities | 2 | |||||||||||
R54 | Enhance SO Capabilities? | 2 | |||||||||||
R55 | Dynamic Update of Cloud Resources in Multi-Vim | 2 | |||||||||||
R56 | Standard/Generic Process to Pass Configuration Data to APPC | 2 | |||||||||||
R57 | Is there a need to consolidate VID and UUI? | 2 | |||||||||||
R58 | ONAP service provision and activation system/function | How ONAP achieve the service provision and activation for the specified customer(residential vCPE customer or enterprise vCPU customer) when ONAP receives an order ticket from BSS | New | SO, SDC, and other new components such as Service Provisioning, Service Activation, or Workforce Scheduling | Support service provisioning and activation for every customer | Service Orchestration | TBD. | ||||||
| R59 | SDNC support for automated IP assignments | Have SDNC to rely on an opensource IP Address Manager like “Netbox” to make automated IP assignments based on the TOSCA VF model. E.g., The SDC TOSCA model could represent each VM-type with a Connection Point to a network-role, specifying a count of fixed IPs to be requested by SDN-C from the IP Address Manager from the IP address plan name specified. | R-vCPE | New (e.g., Netbox) | SDC - modeling impacts SDNC - run time impacts | ||||||||
| R60 | SO Generic Service-Level Flow to Support PNFs and Allotted Resources | Have SO support model-driven decomposition and orchestration of Services that contain PNF and/or Allotted Resource type SDC Resources (where the term "SDC Resource" is being used in the sense of a VNF, PNF, Allotted Resource, or Network). Orchestration sequencing of the various Resources should be based on relationships captured in the SDC TOSCA model. The data is to be passed by the SO Service-level flow to the Resource-level sub-flows orchestration, to Homing, SDNC, AppC, and Multi-VIM, and the source of that data, would also be driven from information captured in the SDC Model. "Model-driven" implies that no Service-specific workflows, code, or scripts need to be created in SO, at the Service or Resource level, in order for the Service to be fully decomposed, homed, and orchestrated to existence. If this is too challenging for a single Release then divide across multiple releases with a clear path to this goal. Simplifying assumptions in Release 2 include that we can focus on relatively "simple" Services such as vCPE. Particularly, can assume that all creation/destruction operations of a given Resource instance (in the set "instantiate" and "activate") are successfully executed prior to start of any operation on the next Resource instance in the dependency chain. Also assume in Release 2 that the "assign" operation of a given Resource instance is successfully executed prior to creation of any other Resource instance. Specifically, no "assignments" for any Resource will depend upon the instantiation of another Resource within the same Service type. I.e., none of the run-time realized Resource instances within a given Service instance will be providing output data that must be used as input to the "assignments" of another Resource instance in that same Service instance. The above does not preclude the possibility that the output of an "assign" operation of a not-yet realized (i.e., not yet "instantiated") Resource instance may provide input to the "assign" operation of another not-yet realized Resource instance. In fact, it is a Release 2 requirement that the Service model and SO support just that. See the attached diagram for how this capability is specifically needed for the Residential vCPE Use Case, such as the vG VNF needing as input the "VNI" value which was an output of the "assign" operation on the TunnelXConn Allotted Resource. | R-vCPE | Enhance | SDC - modeling impacts SO - run time impacts | ||||||||
Page Comparison
General
Content
Integrations