|
|
|
| |||||||||||||
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 | Proposed Ownership
| ||||||
VNF/PNF commitment (ownership) | Commitment for work done per specific modules (company names | Integration/testing owner | Work leader (either specific project or person taking a leadership over set of requirements) | |||||||||||||
R1 | Support for PNF - Onboarding | 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 | 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://wiki.onap.org/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 |
|
|
| |||||||||||
R27 | DNS name configuration | ? |
|
|
| |||||||||||
R28 | 2 | https://wiki.onap.org/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 |
|
|
| |||||||||
R30 | 1 | Change management | Ability to stitch together functionality provided by ONAP components to achieve an E2E management task. | Change Management |
|
|
| |||||||||
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. | 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
| 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… | ? |
|
|
|
| |||||
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. |
|
|
| |||||||
R47 | VNF manual scaling (in/out) | VoLTE | New | Manual scaling triggered from portal. |
|
|
| |||||||||
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 |
|
|
|
| |||||||
Overview
Content Tools