Table of Contents

Presenter(s)/Contact(s)

Onboard ETSI SOL004  compliant VNF packages (ETSI Package Management)

Executive Summary - Enable a vendor provided ETSI SOL004 compliant VNF package including an ETSI SOL001 VNF Descriptor to  be onboarded into ONAP for composition into an ONAP Service

• Support for onboarding ETSI v2.7.1 SOL004 CSAR Packages (Link to ETSI SOL004 v2.7.1 )
• Support for onboarding ETSI v2.7.1 SOL001 VNF Descriptor (Link to ETSI SOL001 v2.7.1)
• Support for mapping of ETSI v2.7.1 SOL001 VNF Descriptor into SDC AID Data Model
• Support for using an ETSI v2.7.1 VNF in an ONAP Service

Business Impact - Enables operators and service providers to use same ETSI compliant VNF packages with ONAP and existing NFVO. Industry compatibility.

Business Markets - All operators that are currently using ETSI packages to deploy VNFs

Funding/Financial Impacts - Reduction in operations expense from using industry standard VNF packaging.  Reduction in capital expense from vendors using a single packaging methodology.

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. 

Onboard ETSI SOL007  compliant Network Service Descriptor packages  (ETSI Package Management)

Executive Summary - Onboard an ETSI SOL007 v2.7.1 compliant (Link to ETSI SOL007 v2.7.1)  Network Service Descriptor package including an ETSI version 2.7.1 SOL001 Network Service Descriptor (NSD) to  be onboarded into ONAP for composition into an ONAP Service or deployment using an ETSI compliant NFVO.

• Support for Cataloging and Preserving the original SOL007 package
• Support for mapping of ETSI v2.7.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model
• Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using VF-C as the NFVO
• Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using an external NFVO

Business Impact - Enables operators and service providers to use vendor provided and internally designed Network Service Descriptors with ONAP and existing NFVO. Industry compatibility.

Business Markets - All operators and service providers that are developing ETSI compatible Network Services

Funding/Financial Impacts - Reduction in operations expense from using industry standard NSD packaging.

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. 

Design ETSI SOL007  compliant Network Service Descriptor packages  (ETSI Package Management)

Executive Summary - Design, catalog and distribute  an ETSI SOL007 v2.7.1 compliant (Link to ETSI SOL007 v2.7.1)  Network Service Descriptor package including an ETSI version 2.7.1 SOL001 Network Service Descriptor (NSD) for deployment using an ETSI compliant NFVO.

• Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using VF-C as the NFVO
• Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using an external NFVO

Business Impact - Enables operators and service providers to use vendor provided and internally designed Network Service Descriptors with ONAP and existing NFVO. Industry compatibility.

Business Markets - All operators and service providers that are developing ETSI compatible Network Services

Funding/Financial Impacts - Reduction in operations expense from using industry standard NSD packaging.

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. 

Support for Nested/Hierarchical ETSI SOL001 v2.7.1 Network Service Descriptor

Executive Summary - Onboard an ETSI SOL007 v2.7.1 compliant (Link to ETSI SOL007 v2.7.1)  Network Service Descriptor package including an ETSI version 2.7.1 SOL001 Network Service Descriptor (NSD) that includes references to other Network Service Descriptors for composition into an ONAP Service or deployment using an ETSI compliant NFVO.

Business Impact - Enables operators and service providers to use vendor provided and internally designed Network Service Descriptors with ONAP and existing NFVO. Industry compatibility.

Business Markets - All operators and service providers that are developing ETSI compatible Network Services especially for 5G Slicing where each Slice Subnet is associated with a Network Service 

Funding/Financial Impacts - Reduction in operations expense from using industry standard NSD packaging.

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. 

Support for ETSI SOL003 v2.7.1 Or-Vnfm Interface from ONAP to external VNF Manager(s)

Executive Summary - Provide an interface adapter from ONAP Service Orchestrator to external VNF Manager(s) using  ETSI SOL003 v2.7.1 (Link to ETSI SOL003 v2.7.1) compliant Interface 

• Support for Create, Instantiate, Query of a VNF using an external VNF Manager
• Support for Grant request from an external VNF Manager
• Support for ModifyVnfInfo using an external Manager
• Support for VNF Heal
• Support for VNF Scale (out, in, level)
• Support for Grant with Incremental resource allocation and HPA support using OOF
• Support for received VNF Life Cycle Notifications (LCN) from a VNF Manager and translation into DCAE Events
• Oauth2 based authentication support between ONAP and VNFM(s)

Business Impact - Enables operators and service providers to use vendor provided or internally developed ETSI compliant VNF Manager(s).  Industry compatibility.

Business Markets - All operators and service providers that are using ETSI SOL003 compliant VNF Managers

Funding/Financial Impacts - Reduction in operations expense from using industry standard Interfaces.

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. 

E2E Network Slicing

Executive Summary: 5G Network Slicing is one of the key features of 5G. The essence of Network Slicing is in sharing network resources (PNFs, VNFs, CNFs) while satisfying widely varying and sometimes seemingly contradictory requirements to different customers in an optimal manner. Same network is expected to provide different Quality of Experience to different consumers, use case categories and industry verticals including factory automation, connected home, autonomous vehicles, smart cities, remote healthcare, in-stadium experience and rural broadband. An End-to-End Network Slice consists of RAN, Transport and Core network slice sub-nets. This Use Case intends to demonstrate the modeling, orchestration and assurance of a simple network slice (e.g. eMBB). While 3GPP standards are evolving and 5G RAN and core are being realized, this Use Case will start with realizing an E2E Network Slice with a simple example of a 5G RAN, Core and Transport Network Slice sub-nets. It will also align with relevant standard bodies (e.g., 3GPP, ETSI, TM Forum) as well as other open initiatives such as O-RAN where relevant, w.r.to both interfaces as well as the functional aspects.

Business Impact: Network Slicing is a feature that almost every service provider will leverage. It allows a service provider to improve their network efficiency by maximizing the network throughput more tailored to each user's use of the network. It is seen as an imperative for efficient and optimal use of their network. This will be particularly relevant as 5G is expected to have upwards of 10,000x the traffic load over 4G and 20GB peak data rates.

Business Markets: Network Slicing, for this use case, is specifically aimed at a 5G access, core and transport. In the future, this might be extended to other domains or applications such as fixed-wireless convergence, Wi-Fi access, all aspects of transport including fronthaul, or unified network management orchestration. Network Slicing functionality is what almost every wireless service provider will inevitably find valuable. The concepts and modeling work being done for Network Slicing will find applications in other areas as well. (Industries) Some applications and industries such as smart cities, remote maintenance, video streaming vs life-saving first-responder type applications will demand different requirements from Network slicing. (Markets/Regions) There are no regional specific aspects to Network Slicing.

Funding/Financial Impacts: Network slicing engenders the optimal use of resources for a Network. Thus, this represents OPEX savings for a service provider.

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.

Support xNF Software Upgrade in association to schema updates

Executive Summary: A schema update in relation to a xNF software upgrades is a routine for network upgrade to support new xNF features, improve efficiency or increase xNF capacity on the field, and to  eliminate bugs.  This use case provides to ONAP an advantage in orchestrating and managing the Life Cycle of a Network Services in-line with business and service objectives.

Business Impact: Deployment and orchestration of new services over CNFs,  VNFs and PNFs in a model and software driven way simplifies the network management. Enables operators and service providers to manage the Life Cycle of a Network Service. Assuring continuity of operation of services is crucial for production and carrier grade environments. The actualization or upgrades of software and in consequence required changes in the service model is a natural part of service instance life cycle. Without the support of ONAP service update with schema change, service life cycle management by ONAP can be very difficult which can impact the quality and continuity of services.

Business Markets: All operators and service providers that are using ONAP for service and network function Life Cycle Management

Funding/Financial Impacts: Reduction in operations expense from using industry standard Interfaces.

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. 

ONAP components support for native CNAs artifacts and cloud native service models distribution and management

Executive Summary – Today new emerging infrastructures based on kubernetes are becoming very popular. ONAP components shall support CNAs artifacts and 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 developments will focuse only on aspects not covered by K8s. The envisioned scenario is based on both CNFs (deployed on kubernetes infrastructure) and PNFs.

Business Impact – Today, many ONAP components (e.g. SDC, SO and AAI) are not able to manage CNA artifact/service models in a native way that bring to unnecessary complexity in service orchestration. It is expected that ONAP modeling and LCM support services composed of PNFs and CNFs to be future proof. ONAP developments will focuse only on LCM aspects not covered by K8s (e.g. mainly on service orchestration rather than resource orchestration, resource splitting among different k8s clusters, PNF, etc.).

Business Markets - All operators and service providers that are using ONAP for service and network function Life Cycle Management

Funding/Financial Impacts – Native support of Cloud native Apps artifacts/service models allow workforce skills reduction and hence OPEX reduction requires custom development before introducing ONAP in production environment with CAPEX expenditure

Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service provider "normal" ONAP deployment and its attendant organizational resources from a service provider.

Support for a declarative approach in the SO engine

Executive Summary - Emerging cloud infrastructures based on kubernetes provide a declarative approach to the orchestration of many problems such as resource provisioning, resource discovery, resource scaling networking (SDN) and resiliency.Furthermore, k8s cloud infrastructure may 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. It is required that Service Orchestration (SO) functional module adopts a declarative approach and native support for CNAs artifacts to avoid time to market bottlenecks.

Business Impact – Today, ONAP service orchestrator requires specialized skills to implement unforeseen orchestration patterns or to modify implemented workflows. A declarative SO engine enables opex savings.

Business Markets - All operators and service providers that are using ONAP for service and network function Life Cycle Management

Funding/Financial Impacts – The usage of declarative engine allows to reduce the workforce skills required to manage the platform and reduce the time to market for service introduction. That ends up in OPEX reduction

Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service provider "normal" ONAP deployment and its attendant organizational resources from a service provider.

Support for hitless A&AI schema modification for new services/CNFs (e.g. no A&AI pods restart)

Executive Summary - Emerging cloud infrastructures based on kubernetes provide a comprehensive toolset for managing cloud native resources in a fast and efficient way. ONAP shall have to be fast and efficient at the same pace. That means that every bottleneck should be avoided in the introduction of a new service and therefore it is expected that inventory schema could be changed easily and hitless (from both the platform and the service point of view) every time it is required.

Business Impact – Today, ONAP A&AI schema changes requires to restart A&AI services. That requires high operational expertise because of the impacts on the whole platform with high operational costs.

Business Markets - All operators and service providers that are using ONAP for service and network function Life Cycle Management

Funding/Financial Impacts – The usage of solutions that enable easily A&AI schema changes allows to reduce the workforce skills required to manage the platform and reduce the time to market for service introduction. That ends up in OPEX reduction

Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service provider "normal" ONAP deployment and its attendant organizational resources from a service provider.

Support for A&AI and k8s alignment about instance details that need to be kept in A&AI

Executive Summary – Today new emerging infrastructures based on kubernetes are becoming very popular. ONAP inventory shall support the representation of instances information related to such new infrastructures. Nevertheless, such cloud infrastructures likely do not require a detailed instance representation in the inventory because of the native orchestration capabilities and hence a detailed investigation is required because the solution may differ from the one used for Openstack based infrastructure

Business Impact – Today, ONAP A&AI is not able to correctly represent instances information related to kubernetes infrastructures so limiting the actual usage of ONAP for cloud native infrastructures.

Business Markets - All operators and service providers that are using ONAP for service and network function Life Cycle Management

Funding/Financial Impacts – Lack of such functionality requires custom development before introducing ONAP in production environment with CAPEX expenditure

Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service provider "normal" ONAP deployment and its attendant organizational resources from a service provider.

Support for Test Topology Auto Design （NFV Testing Automatic Platform）

Executive Summary – To achieve a more flexible NFV automated test platform, ONAP-based NFV automatic testing platform provides a quick test service(topology) design composed of tested VNF and test environment, as well as  supports the import and reuse test service(topology) between different test environments. 

Business Impact – There are a large number of cross-department and cross-organization communications during the traditional network element, system or equipment network access test. And the manual errors are inevitable, the knowledge in test field cannot be solidified. The cost of each test is high and the test cycle is always long. After introducing NFV, because network element software and hardware equipment are layered decoupled, the introduction of a large number of open source components as well as the frequent upgrade of the software itself, make network access test become more complicated and frequent. Testing has become a bottleneck during the introduction and iteration of new technologies. Therefore, it is urgent to introduce automated test tools. By introducing test topology auto design and corresponding enhancements, it can solidify domain knowledge, and help reduce labor costs, shorten test cycle, improve test efficiency , optimize test accuracy.

Business Markets - CSPs can accelerate new network services deployment cycle, improve interoperability and software quality, and reduce in-house testing effort and reduce costs. Vendor can leverage it to deduce the cost of VNF developing, and improve time to revenue for new product offerings, achieve greater alignment with customer requirements from service provider, and demonstrate product quality through open ecosystem testing. Instrument manufacturers can integrate their test tools and test capabilities into this platform, and demonstrate product quality through open ecosystem testing. Integrators can refer to the open source implementation of this platform and provide solutions for their commercial products. At the same time, the realization of this requirement can be combined with OVP's existing processes to accelerate the testing and certification of OVP NFV commercial products.

Funding/Financial Impacts – The test topology auto design tool can help reduce the labor costs in traditional NFV test process and the R & D costs of NFV commercial products, as well as shorten the benefit reaping period of new products, and improve test efficiency. 

Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service provider "normal" ONAP deployment and its attendant organizational resources from a service provider.

Support for Test Environment Auto Deploy（NFV Testing Automatic Platform）

Executive Summary – To achieve a more flexible NFV automated test platform, ONAP-based NFV automatic testing platform provides test case execution optimization orchestration capability to reduce unnecessary replicated deployment between different test case executions.

Business Impact – There are a large number of cross-department and cross-organization communications during the traditional network element, system or equipment network access test. And the manual errors are inevitable, the knowledge in test field cannot be solidified. The cost of each test is high and the test cycle is always long. After introducing NFV, because network element software and hardware equipment are layered decoupled, the introduction of a large number of open source components as well as the frequent upgrade of the software itself, make network access test become more complicated and frequent. Testing has become a bottleneck during the introduction and iteration of new technologies. Therefore, it is urgent to introduce test environment auto deploy tool. By introducing test environment auto deploy tool and corresponding enhancements, can we optimize orchestration capabilities and provide flexible and automated deployment of test environments for NFV testing. This can also help reduce labor costs, improve test efficiency and test accuracy.

Business Markets - CSPs can accelerate new network services deployment cycle, improve interoperability and software quality, and reduce in-house testing effort and reduce costs. Vendor can leverage it to deduce the cost of VNF developing, and improve time to revenue for new product offerings, achieve greater alignment with customer requirements from service provider, and demonstrate product quality through open ecosystem testing. Instrument manufacturers can integrate their test tools and test capabilities into this platform, and demonstrate product quality through open ecosystem testing. Integrators can refer to the open source implementation of this platform and provide solutions for their commercial products. At the same time, the realization of this requirement can be combined with OVP's existing processes to accelerate the testing and certification of OVP NFV commercial products. 

Funding/Financial Impacts –  The optimized test case execution orchestration capability can reduce the labor costs in traditional NFV test process and the R & D costs of NFV commercial products, as well as shorten the benefit reaping period of new products, and improve test efficiency. 

Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service provider "normal" ONAP deployment and its attendant organizational resources from a service provider.

Support for Test Task Auto Execution （NFV Testing Automatic Platform）

Executive Summary – To achieve a more flexible NFV automated test platform, ONAP-based NFV automatic testing platform provides a flexible testing framework for testers, and enables output customized test reports (e.g. XML, Json, etc.). 

Business Impact – There are a large number of cross-department and cross-organization communications during the traditional network element, system or equipment network access test. And the manual errors are inevitable, the knowledge in test field cannot be solidified. The cost of each test is high and the test cycle is always long. After introducing NFV, because network element software and hardware equipment are layered decoupled, the introduction of a large number of open source components as well as the frequent upgrade of the software itself, make network access test become more complicated and frequent. Testing has become a bottleneck during the introduction and iteration of new technologies. Therefore, it is urgent to introduce the test task auto execution framework. By introducing test task auto execution framework and corresponding enhancements, it can realize the automatic execution of NFV test tasks, reduce labor costs, and improve test efficiency. 

Business Markets – After enabling Test Task Auto Execution, CSPs can leverage it to accelerate time to deployment for new network services, improve interoperability and software quality, and reduce in-house testing effort and reduce costs. Vendor can leverage it to deduce the cost of VNF developing, and improve time to revenue for new product offerings, achieve greater alignment with customer requirements from service provider, and demonstrate product quality through open ecosystem testing. Instrument manufacturers can integrate their test tools and test capabilities into this platform, and demonstrate product quality through open ecosystem testing. Integrators can refer to the open source implementation of this platform and provide solutions for their commercial products. At the same time, the realization of this requirement can be combined with OVP's existing processes to accelerate the testing and certification of OVP NFV commercial products.

Funding/Financial Impacts –  The test task auto execution capability can reduce the labor costs in traditional NFV test process and the R & D costs of NFV commercial products, as well as shorten the benefit reaping period of new products, and improve test efficiency.

Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service provider "normal" ONAP deployment and its attendant organizational resources from a service provider.

Support for Test Result Auto Analysis & Certification （NFV Testing Automatic Platform）

Executive Summary – To achieve a more flexible NFV automated test platform, Test Result Auto Analysis & Certification capability support integration with 3^rd party test & certification systems, and provide certified product release markets. 

Business Impact – There are a large number of cross-department and cross-organization communications during the traditional network element, system or equipment network access test. And the manual errors are inevitable, the knowledge in test field cannot be solidified. The cost of each test is high and the test cycle is always long. After introducing NFV, because network element software and hardware equipment are layered decoupled, the introduction of a large number of open source components as well as the frequent upgrade of the software itself, make network access test become more complicated and frequent. Testing has become a bottleneck during the introduction and iteration of new technologies. Therefore, it is urgent to introduce test result auto analysis & certification capability. By introducing test result auto analysis & certification capability and corresponding enhancements, it can provide one-stop service for test certification and issuance, reduce labor costs, improve test efficiency and test accuracy.

Business Markets - After enabling test result auto analysis & certification capability, CSPs can leverage it to accelerate time to deployment for new network services, improve interoperability and software quality, and reduce in-house testing effort and reduce costs. Vendor can leverage it to deduce the cost of VNF developing, and improve time to revenue for new product offerings, achieve greater alignment with customer requirements from service provider, and demonstrate product quality through open ecosystem testing. Instrument manufacturers can integrate their test tools and test capabilities into this platform, and demonstrate product quality through open ecosystem testing. Integrators can refer to the open source implementation of this platform and provide solutions for their commercial products. At the same time, the realization of this requirement can be combined with OVP's existing processes to accelerate the testing and certification of OVP NFV commercial products.

Funding/Financial Impacts –  The test result auto analysis & certification capability can reduce the labor costs in traditional NFV test process and the R & D costs of NFV commercial products, as well as shorten the benefit reaping period of new products, and improve test efficiency.

Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service provider "normal" ONAP deployment and its attendant organizational resources from a service provider.

OOF-SON: 5G Self-Organizing Network (SON) using ONAP Optimization Framework (OOF)

Executive Summary: SON (Self-Organizing Networks) functionality is an essential part of 4G networks, and will be even more critical for 5G. SON enables automation to improve network performance and efficiency, improve user experience, and reduce operational expenses and complexity. The objective of the OOF SON use cases is to develop an ONAP-based SON platform using the ONAP Optimization Framework (OOF). We have taken a phased approach since SON is complex, and SON for 5G is still evolving. We started with the Physical Cell Identity (PCI) optimization SON use case in Casablanca, and added centralized Automated Neighbor Relations (ANR) aspects in Dublin. In Frankfurt, we included adaptive SON functionality, took initial steps in O-RAN alignment and collaborated with Policy Control Loop Co-ordination (CLC). For Guilin, we will align with ORAN interfaces, be the early adopter of the new Runtime Config DB (e.g. generate DB schemas and APIs based on yang models), cover SON-related workflow for new cell addition, introduce another SON use case to add new platform capabilities, and collaborate on further extensions to  CLC. We will also pursue alignment with industry trends for open interfaces & open models for RAN interactions, in particular with O-RAN.

Business Impact: SON is an essential feature in mobile networks, and relevant to every operator. Any ONAP-based network deployment for 5G will benefit from an ONAP-based SON solution, which provides a disaggregation of SON functions into modules aligned with the ONAP architecture. Operators and vendors will both benefit from the ability of vendors to bring best-in-class solutions to each module, while leveraging the benefits of a community-supported open platform. This will enable faster development of innovative solutions. The approach taken could very well be evolved to address SON use cases whose scope extends beyond just the RAN.

Business Markets: SON for 5G is relevant to all 5G operators and markets.

Funding/Financial Impacts: SON functions reduce OPEX since the automated self-organizing functions are an efficient approach to continuously optimize network configurations to improve performance and respond to network conditions.

Organization Mgmt, Sales Strategies: There are no additional organizational management or sales strategies for this beyond whatever is required for ONAP deployment to support 5G.

Run Time Configuration Database / Data Persistency Service Project

KEY CONTACTS - Benjamin Cheung , Joanne Liu Rudel

EXECUTIVE SUMMARY - The RunTime Configuration Database / Data Persistency Service is a new platform component that is designed to serve as a data repository for Run-time data that needs to be persistent. As a stand-alone ONAP component, this project provides data layer services to other ONAP platform components and use cases that require persistent configuration or operational data. The R6 development will be enhanced as well.      

BUSINESS IMPACT - The ability for service operators to visualize and manage data in a RAN network (PNFs, VNFs, and logical constructs) with ONAP is a critical business function because they are key Life Cycle Management (LCM) and OA&M operations. The project has business impacts to enhance the operation of data-handling within ONAP by providing efficient data layer services.

BUSINESS MARKETS - This project applies to any domain (wireless, transport, optical, and wireline) that ONAP may manage. It is not a market or geographical specific capability. It is expected that scaled ONAP installations such as Edge & Core ONAP deployments will also deploy the database across each installation.

FUNDING/FINANCIAL IMPACTS - This project represents a large potential Operating Expense (OPEX) savings for operators because of the ability to configure networks saving time and expenses.

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.

Support for ETSI SOL005 v2.7.1 Os-Ma-nfvo Interface between ONAP and NFVO

Executive Summary - Provide an interface adapter from ONAP Service Orchestrator to NFVO(s)  using  ETSI SOL005 v2.7.1 (Link to ETSI SOL005 v2.7.1) compliant Interface 

• Support for Create, Upload, Update, Query, Delete of an ETSI NS Descriptor using VF-C
• Support for Create, Upload, Update, Query, Delete of an ETSI NS Descriptor using an external NFVO
• Support for Create, Instantiate, Terminate of a ETSI NS using VF-C
• Support for Create, Instantiate, Terminate of a ETSI NS using an external NFVO
• Support for Scale, Heal, Update of an ETSI NS using VF-C
• Support for Scale, Heal, Update of an ETSI NS using an external NFVO
• Support for receiving NS Notifications (LCN) from an NNFVO and translation into DCAE Events
• Oauth2 based authentication support between ONAP and NFVO(s)

Business Impact - Enables operators and service providers to use vendor provided or internally developed ETSI compliant NFVO(s).  Industry compatibility.

Business Markets - All operators and service providers that are using ETSI SOL005 compliant NFVOs

Funding/Financial Impacts - Reduction in operations expense from using industry standard Interfaces.

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. 

Support for Containerized Network Function orchestration through ONAP service orchestrator

Executive Summary - Provide CNF orchestration support through integration of K8s adapter in ONAP SO

• Support for provisioning CNFs using an external K8s Manager
• Support the Helm based orchestration
• leverage the existing functionality of Multi cloud in SO
• Bring in the advantages of the K8s orchestrator and
• Set stage for the Cloud Native functioanl scenarios to be demosntarted through ONAP

Business Impact -Enables operators and service providers to orchestrate CNFs based services along with the VNFs and PNFs

Business Markets - All operators and service providers that are intended to use the CNFs along with PNFs / VNFs

Funding/Financial Impacts - Reduction in the footprint of the ONAP for CNF support by reusing the existing components.

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. 

Support for ETSI SOL002 v2.7.1 Ve-Vnfm Interface from ONAP to external VNF Manager(s)

Executive Summary - Provide an interface adapter from ONAP Service Orchestrator (EMS) to external VNF Manager(s) using  ETSI SOL002 v2.7.1 (Link to ETSI SOL002 v2.7.1) compliant Interface 

• Support for receiving VNF Life Cycle Notifications (LCN) from a VNF Manager and translation into DCAE Events
• Oauth2 based authentication support between ONAP and VNFM(s)

Business Impact - Enables operators and service providers to use leverage ONAP's EMS like capabilities to monitor VNFs through a vendor provided or internally developed ETSI compliant VNF Manager(s).  Industry compatibility.

Business Markets - All operators and service providers that are using ETSI SOL002 compliant VNF Managers

Funding/Financial Impacts - Reduction in operations expense from using industry standard Interfaces.

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. 

Container Network Function Test Platform (CNTP)

Executive Summary - In ONAP, as part of Container Network Function (CNF) support, its mandatory to add enable the following testing/validation to make sure the given CNF is as per the need.

1. Design Time validation: When Operator on-board CNF as VSP in SDC, Operator  wants to check the given CNF is confromance to their Operator Specific compliance such as security policies

2. Run time  validation: Once CNF is provisioned in ONAP,  it needs to be validated for sanity check and required functioanlity check.
3. Support LFN OVP 2.0 to support CNF conformance and CNF on-boarding vadlidations. (pre-on-boarding time)

More Details: OVP 2.0 CNF support in ONAP

Business Impact - Enables Vendors to perform the OVP tasks and helps to levrage to same to Operator to enhance the ONAP production with required additional validation of CNF and its service

Business Markets - All operators that are currently using CNF based Network service. All Vendors seekins for OVP 1.0 badging

Funding/Financial Impacts - Helps Vendors for getting OVP badgings while for Operators, it reduce the manual/offline check invovled during designtime/run-time..

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. 

R7 PNF PLUG & PLAY BUILDING BLOCK / WORK-FLOW MANAGEMENT

Key Contacts - Benjamin Cheung  damian.nowak

EXECUTIVE SUMMARY - This requirement will augment the work-flow to building block management within SO for Plug and Play operation. The continues the work started in R6. The description of the "base" work which will be enhanced is shown in the wiki: PNF PLUG and PLAY in R6 Frankfurt

BUSINESS IMPACT - The enhancement to Plug and Play operation in ONAP is a critical business function because they enhance installation and commissioning activities.

BUSINESS MARKETS - This project applies to any domain (wireless, transport, optical, and wireline) that ONAP may manage.

FUNDING/FINANCIAL IMPACTS - The plug and play project has Operating Expense (OPEX) savings for operators because of the ability to saving time and expenses during installation and commissioning and contributes towards ZTM (Zero touch management).

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.

R7 ONAP SECURITY - CMPv2 SERVER/CLIENT INTEGRATION

Key Contacts - Benjamin Cheung  Pawel Baniewski

EXECUTIVE SUMMARY - This requirement improves ONAP Security with CMPv2. CMP is used by multiple operations including Plug and Play, and NetConf operation. In R6 CMPv2 Certificate Service and basic development was implemented. Integration with server & client to the certificate service will be completed. There are also two ONAP boardering clients to integrate with the certificate service with interfaces to SDN-C and DCAE. DCAE interoperation with CMPv2.

BUSINESS IMPACT - The enhancement to CMPv2 operation will improve security management within ONAP and affects multiple ONAP functions and use cases, including Plug and Play (PNF registration) and NetConf. As with all security functionality within ONAP, Security is a fundamental aspect of FCAPS, being the "S" for security management.

BUSINESS MARKETS - This project applies to any domain (wireless, transport, optical, and wireline) that ONAP may manage.

FUNDING/FINANCIAL IMPACTS - Potential OPEX savings with enhanced security to prevent breaches and prevent security compromises.

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.

R7 PNF PRE-ONBOARDING VNF-SDK VALIDATION

Key Contacts - Benjamin Cheung  damian.nowak Zu Qiang

EXECUTIVE SUMMARY - This requirement enhances the PNF Onboarding / Pre-onboarding use case. This requirement introduces package security Option2 improvements on Signature per artifact on the Vendor delivered package as defined in ETSI NFV SOL004v2.7.1. It will also validate the PNF Software versions that are onboarded. Also, validation of onboarded PM dictionary data based on schema information.

BUSINESS IMPACT - The enhancement to Onboarding & Pre-onboarding is a critical business function because they are vital to design-time operation to properly onboard vendor packages.

BUSINESS MARKETS - This project applies to any domain (wireless, transport, optical, and wireline) that ONAP may manage.

FUNDING/FINANCIAL IMPACTS - The PNF Onboarding & Pre-onboarding use case has Operating Expense (OPEX) savings for operators because of the ability to saving time and expenses during installation and commissioning of PNF resources.

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.

R7 5G PNF SERVICE MODEL INTRODUCTION

Key Contacts - Benjamin Cheung  

EXECUTIVE SUMMARY - This requirement introduces platform information model enhancements to document new ISOMII experimental classes from 3GPP TS28.541, the 5G Network Resource Model (NRM).

BUSINESS IMPACT - The requirement,  is a critical because it will serve to lay the ground-work for actually "turning on" a real 5G DU (PNF) that might be installed by a Vendor.

BUSINESS MARKETS - This project applies to any domain (wireless, transport, optical, and wireline) that ONAP may manage.

FUNDING/FINANCIAL IMPACTS - Without the groundwork laid down for information model management of a 5G Service, operators will not be able to "turn on" a real live 5G network using "live" PNF resources. No Network. No Business. High OPEX impact.

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.

R7 HARMONIZATION:  ONAP/3GPP & O-RAN ALIGNMENT–STANDARDS DEFINED NOTIFICATIONS OVER VES

Key Contacts - marge.hillis Vimal Begwani

EXECUTIVE SUMMARY -

-This contribution introduces a new domain in VES, stndDefined, which indicates that the event contains data that conforms to format/schema defined by a separate standards organization1.  In addition we propose one new field in the VES Common Header to enable further classification of such events, e g to support routing of these events to appropriate DMaaP topics.  An optional second stage validation is proposed in DCAE prior to acknowledging the event to enhance trouble shooting.

-It is proposed that the first application of this generic capability supports VES encapsulated 3GPP defined notifications as described in 28.532 version 16.3.0 Annex B (informative). The ORAN O1 specification also refers to VES-based 3GPP notifications for several management services, and in those cases is expected to further align with the approach and solution published in 3GPP in a future release.

BUSINESS IMPACT- The ability for service providers to deploy ONAP as the SMO in their O-RAN compliant network depends upon ONAP’s ability to process VES encapsulated events as defined by 3GPP and ORAN in DCAE and route these events to appropriate DMaaP topics. This proposal, in Guilin, provides the necessary capability for ONAP to process and validate events that are defined using 3GPP schema for the data. The proposal is readily extensible for the support of additional events from 3GPP, ORAN or other standards organizations adding a high degree of flexibility to the ONAP platform.

BUSINESS MARKETS - This contribution applies to any Service Provider that wants to use ONAP as an O-RAN compliant SMO or to support 3GPP compliant interfaces and can be leveraged by Service Providers wishing to support events from network functions which are aligned with other standards organizations.

FUNDING/FINANCIAL IMPACTS -This contribution helps enable ONAP to be O-RAN and 3GPP compliant which should stimulate contributions from companies that are aligned with O-RAN and 3GPP. There is no new hardware to be procured and no new licenses.

ORGANIZATION MGMT, SALES STRATEGIES - This proposal does not affect sales strategies.

1) Standards organization is intended to be interpreted in a broader sense than SDO as defined by ITU, to cover also e g joint ventures like 3GPP and open industry fora like the O-RAN Alliance.