| Table of Contents |
|---|
TABLES OF REQUIREMENTS
STANDARDS Alignment
...
| TOPIC | CONTACTS |
|---|---|
| E2E Network Slicing | |
| OOF-SON: 5G Self-Organizing Network (SON) using ONAP Optimization Framework (OOF) | |
| Intent-based Network | |
| R7 5G PNF SERVICE MODEL INTRODUCTION | |
| 76875890 | |
xNF (PNF, VNF, ANF, CNF ...) Related
| TOPIC | CONTACTS |
|---|---|
| R7PNFPLUG&PLAYBUILDINGBLOCK/WORK-FLOWMANAGEMENT | |
| 76875890 | |
| 76875890 | |
| Support xNF Software Upgrade in association to schema updates | |
| ONAP high level design requirements NOTE: These relate both xNF and 5G Table | |
Run Time Configuration Database / Data Persistency Service ProjectConfiguration&PersistencyServiceProject | |
Support for Containerized Network Function orchestration through ONAP service orchestrator | |
| PM Data Control Extension | Michela Bevilacqua, @Mark Scott |
...
ONAP high level design requirements
Key Contacts - Alessandro Gerardo D'Alessandro, ceciliamaria.corbi@telecomitalia.it
Executive Summary – Today new emerging infrastructures based on kubernetes are becoming very popular. ONAP components shall support CNAs/CNFs artifacts, cloud native service models and relevant distribution/management. Given the fact that K8s has its own orchestration capabilities that partially overlap with ONAP capabilities, it is expected that ONAP development focuses first on aspects not covered by K8s. The envisioned scenario is based on both CNFs and PNFs. Moreover kubernetes provide a declarative approach to the orchestration of many aspects such as resource provisioning, resource scaling and resiliency and can be enhanced with many add-ons that seamlessly provide other features such as application control, communication robustness etc (e.g service mesh by Istio). ONAP provides a good level of flexibility in service orchestration (e.g. a la carte, Macro and E2E orchestration approaches) but the framework requires specialized skills to implement unforeseen orchestration patterns that may slow down new service design and deployment. It is therefore required that ONAP functional module adopts a declarative approach and native support for CNAs artifacts to avoid time to market bottlenecks. Link 20200512.ONAP.relG.TIM.functional.requirements.pptx
Business Impact – Today, many ONAP components (e.g. SDC, SO and AAI) are not able to manage CNA/CNF artifact/service models in a native way that bring to unnecessary complexity in service orchestration. It is expected that ONAP modeling and LCM support be future proof. ONAP developments shall focus first on LCM aspects not covered by K8s (e.g. on service orchestration rather than resource orchestration, on resource splitting among different k8s clusters rather than on single k8s cluster, on PNFs LCM aspects , etc.). Moreover it is required that ONAP be designed in a way that it can be easily be customized with general programming skill personel.
...
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
xNF License Management
Key Contacts - Timo Perala, Samuli Kuusela
Executive Summary - Continue use case analysis for xNF License Management and derive any requirements to ONAP. The aim is for ONAP to support various types (simple, complex, vendor specific) commercial licensing models and use cases. These will be reflected as multiple, optional solutions for ONAP. The use cases we started with include xNF onboarding, PNF introduction/ONAP PnP, VNF instantiation. Further use cases to be analyzed, eg. usage monitoring for the purpose of invoicing. Based on agreed use cases review relevant ONAP xNF requirements. Possible SW contributions, eg. in SDC, as well as enhancement of ONAP architecture sequence diagrams.
...
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
5G Network Resource
...
Model (NRM) Configuration
Key Contacts - yaoguang wang
Executive Summary - x
Business Impact - x.
Business Markets - x.
This requirement enhances the Network Resource Management (NRM) configuration management provided in R6. NRM configuration management allows the service providers to control and monitor the actual configuration on the Network Resources. They may be used within the first PNF or VNF instantiation or routine operations after PNFs or VNFs are running. Planned enhancements for R7 include checking SO BBs (ConfigDeplyBB) applicability on NRM Configuration, CDS SS gRPC API with RestfultExecutor, full automation for integration test (CIST).
Business Impact - Network resources are the fundamental resources to the mobility networks. Only the network resource are ready then the service like eMBB service can be instantiated. Better service quality can be achieved by suitable NRM configuration management.
Business Markets - Considering the Network Resources are basic for mobility network, New 5G deployments as well as legacy 4G systems should be considered as target markets. Both radio and core and other sub-network domains could also benefits from it.
Funding/Financial Impacts -Orchestrating and Controlling the network resources could reduce the OPEXFunding/Financial Impacts - x.
Organization Mgmt, Sales Strategies - xThere is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
Anchor ccvpnTransportSlicing ccvpnTransportSlicing
CCVPN - Transport Slicing
| ccvpnTransportSlicing | |
| ccvpnTransportSlicing |
...