5G  - general

5G  - network slicing specific, service based/vertical industry

xNF (PNF, VNF, ANF, CNF ...) Related

ETSI compliancy

Generic capabilities extension

(Template Cut & Paste for your Use Case/Requirement)

R8 PRESENTATION:

Executive Summary - (Give a short description of your Use Case, the "Executive 2 min elevator pitch", this describes the "WHAT")

Business Impact - (This is the Business Impact which describes why this use case is important from a business perspective, this describes the "WHY").

Business Markets - (This is the marketing analysis, which can include but not limited to applicable markets, domains, marketing projections, this can describe the "WHERE").

Funding/Financial Impacts - (The Funding requirements and Financial impacts can describe the financial savings, or CAPEX, OPEX impacts for a Use Case).

Organization Mgmt, Sales Strategies - (It is suggested that you use the following wording): 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. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)

CONFIGURATION PERSISTENCE SERVICE

R8 PRESENTATION:

Executive Summary - The Configuration Persistence Service (CPS) is a real-time service that is designed to serve as a data repository for Run-time Network Element (configuration) data that needs to be persistent applicable to multiple domain (RAN, Transport, and Core). This was explored as a R7 PoC.  Focus on storing run-time DATA RELATED to NETWORK ELEMENT instances. In R8, this is being proposed as a stand-alone project.

Business Impact - The ability for service operators to visualize and manage network element data in a 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 requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 

R8 5G PNF SERVICE MODEL INTRODUCTION

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.

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 v3.3.1 SOL004 CSAR Packages (Link to ETSI SOL004 v3.3.1 ) with CNF enhancements

• Support for onboarding ETSI v3.3.1 SOL001 VNF Descriptor (Link to ETSI SOL001 v3.3.1) with CNF enhancements

• Support for mapping of ETSI v3.3.1 SOL001 VNF Descriptor with CNF enhancements into SDC AID Data Model

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. 

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

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

• Support for designing an ETSI SOL001 v3.3.1 compliant Network Service that can be deployed with an ETSI compliant NFVO

• Composed of one or more VNFs and the Virtual Links that connect them.
• Support for using VNFs with CNF enhancements

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 and deploying 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 Nested/Hierarchical ETSI SOL001 v3.3.1 Network Service Descriptor

Executive Summary - Design an ETSI SOL007 v3.3.1 compliant (Link to ETSI SOL007 v3.3.1)  Network Service Descriptor package including an ETSI v3.3.1 SOL001 Network Service Descriptor (NSD) that includes references to other Network Service Descriptors for composition into an ONAP Service and deployment using an ETSI compliant NFVO.

• Composed of zero or more VNFs or zero or more nested Network Services and the Virtual Links that connect them.
• Support for using VNFs with CNF enhancements

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 v3.3.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 v3.3.1 (Link to ETSI SOL003 v3.3.1) compliant Interface with CNF enhancements

• Support for Create, Instantiate, Query, terminate and Delete of a VNF or a prototype CNF using an external VNF Manager

• Support for Grant request from an external VNF Manager

• Support for ModifyVnfInfo using an external VNF Manager

• Support for receiving VNF Life Cycle Notifications (LCN) from a VNF Manager

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. 

Support for ETSI SOL005 v3.3.1 Os-Ma-nfvo Interface between ONAP SO and NFVO

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

• Support for Create, Upload, Update, Query, Delete of an ETSI NS Descriptor using an ETSI v3.3.1 SOL005 compliant NFVO

• Support for Create, Instantiate, Terminate and Delete of a ETSI NS using an ETSI compliant NFVO

• Support for receiving NS Notifications (LCN) from an NFVO
• Support for ModifyVnfInfo operation.

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. 

Onboard Prototype Package and VNF Descriptor based on  ETSI IFA011 v4.1.1 supporting containerized VNF (CNF) packages (ETSI Package Management)

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

• Support for onboarding Prototype v4.1.1 CSAR Packages

• Support for onboarding Prototype v4.1.1 VNF Descriptor

• Support for mapping of Prototype v4.1.1 VNF Descriptor into SDC AID Data Model

• Support for using a Prototype v4.1.1 VNF in an ETSI Network Service

Business Impact - Enables operators and service providers to use same ETSI aligned containerized VNF (CNF) packages with ONAP and existing NFVO. Industry compatibility.

Business Markets - All operators that are currently using ETSI packages to deploy containerized VNFs (CNFs)

Funding/Financial Impacts - Reduction in operations expense from using industry standard containerized VNF (CNF)  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. 

PLUG AND PLAY IN R8

R8 PRESENTATION:

Executive Summary - This requirement will introduce VID work to complement the work-flow to building block management work in SO for Plug and Play. The continues the work started in R6 and R7 where the SO work-flow to building block work was finished. The description of the "base" work was done in R6/R7 and can be found in the PnP pages for those releases. In R8, VID software "front end" will be added to allow for a user to more easily use the SO Building Blocks.

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. It is not a market or geographical specific capability.

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 requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 

CMP v2 in R8

R8 PRESENTATION:

Executive Summary - The CMPv2 work in R8 will develop (1) DCAE further integration and (2) Integration with Cert-Manager (certificate enrollment solution recommended by OOM). 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. Changes in Cert Service as DCAE wanted output artifacts in different configurable formats. SDN-C was completed in R6, In R7, the OOM software completed (in R6) and was merged in R7, and DCAE interoperation with CMPv2 was the focus in R7.

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 requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 

R8 HARMONIZATION:  ONAP/3GPP & O-RAN ALIGNMENT–STANDARDS DEFINED NOTIFICATIONS OVER VES (REQ-433)

R8 PRESENTATION:

Key Contacts - marge.hillis Oskar Malm damian.nowak

EXECUTIVE SUMMARY -

• This is a continuation of the https://jira.onap.org/browse/REQ-327

• This contribution introduces enhancements (mainly to DCAE platform) to support better the standard-defined openAPI onboarding (at least as a K8S configMap in DCAE)
• This contribution introduces openAPI onboarding capabilities (openAPI as an onboarding package artifact, distribution to relevant ONAP modules, ingesting in interested ONAP modules)

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 Honolulu, provides the necessary capability for ONAP to onboard the standards-defined event definitions using openAPI format.

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.

5G OOF SON use case

R8 PRESENTATION:

Executive Summary

SON (Self-Organizing Networks) functionality is an essential part of existing 4G mobility 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 (new name for OOF-PCI) use case 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, then added some centralized Automated Neighbor Relations (ANR) aspects in Dublin. For Frankfurt, we will address gaps such as PCI assignment during new cell addition, alignment with RAN inventory, etc., In addition, we aim to have enhancements such as: additional optimization functionality (e.g. include the use of AI/ML), use of control loop co-ordination in Policy, and alignment with industry trends for open interfaces and open models for the RAN interactions.

Business Impact

SON is an essential feature in mobility 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.

End-to-end Network Slicing use case

R8 PRESENTATION:

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.

Smart Operator Intent Translation in UUI based on IBN - R8 5G Slicing Support

R8 PRESENTATION:

Key Contacts - Dong Wang Xin Zhang Huang ZongHe

Executive Summary - Intent-based network (IBN) is a self-driving network that uses decoupling network control logic and closed-loop orchestration techniques to automate application intents. An IBN is an intelligent network, which can automatically convert, verify, deploy, configure, and optimize itself to achieve target network state according to the intent of the operators, and can automatically solve abnormal events to ensure the network reliability. In R8, the smart operator intent translation function is proposed to support the 5G slicing selection of current E2E usecase in UUI.

Business Impact - In 5G networks, dozens of slice templates will be created to support different SLA requirements. It is difficult for the operators to select the target slice and create the slice instance manually. The IBN based smart operator intent translation function is applied to select the target slice automatically and accurately.

Business Markets - Currently, the smart operator intent translation function is developed to support the 5G slice selection. In the further releases, it will be improved to support multiple network configurations in ONAP.

Funding/Financial Impacts - This function will have OPEX savings by selecting more accurately slices to save the network resources, and decreasing the labor cost using automation technology.

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. 

PM Data Collection Control: Subscription update

Key Contacts - Mark Scott, Zu Qiang, Michela Bevilacqua

Executive Summary - PM data collection control provides network operators with a dynamic and more efficient way to configure performance measurement collection on a selected subset of  PNFs/VNFs in the network and complements the existing PM data collection and processing capabilities in ONAP/DCAE. An initial version has been delivered in Rel 6 (REQ-129) then enhanced in Rel 7 (REQ-381). Planned enhancements for Rel 8 intend to improve the (PMSH) subscription management about subscription update.

Business Impact - PM control is a critical business function because it is vital to enable the PM data collection in ONAP.

Business Markets - All operators and service providers that want to use ONAP for PM data collection.

Funding/Financial Impacts - PM data collection control can provide OPEX savings for operators due to increased automation of a critical function. 

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. 

PNF Software Upgrade enhancement

Key Contacts -  Zu Qiang

Executive Summary - In Rel 6 (REQ-84) and Rel 7 (REQ-324), PNF sw upgrade requirement in ONAP has progressed covering both with/without schema updates. 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. In Rel 8, the feature will be enhanced with PNF sw version management during sw upgrade procedure.

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. 

A1 Adapter and Policy Management Extension (ORAN/ONAP/3GPP Harmonization)

Key Contacts -  John Keeney, Michela Bevilacqua

Executive Summary - This requirement enhances the A1 interface capabilities provided in Rel 6 as part of  5G/ORAN & 3GPP Standards Harmonization requirement ( REQ-38) and extended in Rel 7 with the introduction of A1 policy management.   O-RAN has defined A1 interface specification in the context of the management of 5G RAN elements to provide intent based policies for optimization of the RAN network performance. Planned enhancements for Rel 8 include support of new A1 interface version in alignment to O-RAN alliance and common logging/audit.

Business Impact - Continuing the convergency between ONAP and ORAN for A1 interface to used by all service providers and avoid duplicate development efforts.

Business Markets - Enhanced A1 capabilities, once developed, will be useable by any service provider deploying and using ONAP.

Funding/Financial Impacts -  A1 interface provides a flexible way for the operator to manage wide area RAN network optimization, reducing capex investment needs.

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 Vertical Industry 

Key Contacts -  Cheng Huang,wangyaoguang

Executive Summary - Vertical Industry is one of the greatest potential 5G markets. In order to deploy 5G network in an efficient way, vertical industry may choose to rent the network resources from the service operators. Therefore, the service operators should provide O&M capabilities for multiple vertical industries. When one specific operator manages multiple vertical industry networks, its OM system needs to distinguish vertical industry’s resources. This requirement propose to help operators to manage multiple vertical industry networks using ONAP. In R8, it will start with managing the relations between providers and consumers (vertical industry) of network resources..

Business Impact - Vertical industry networks contain various combinations of resources, such as VNFs, PNFs, and edge computing resources. Providing one unified OM platform is the most efficient way to satisfy various vertical industry’s requirements. ONAP can be a great automation management platform for 5G vertical industry.

Business Markets - All operators and service providers that want to use ONAP to support the management of vertical industry networks.

Funding/Financial Impacts - Reduce the operation expense while providing Network O&M service for different vertical industries.

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 

Intent Framework and Intent Modeling in R8 

Key Contacts - wangyaoguang , Xianming Li, Dong Wang, Huang ZongHe

Executive Summary -  In R7, Intent technology was proposed as a proof-of-concept (REQ-329). It can be viewed as one of most promising solutions for towards autonomous network. This requirement propose to enhance ONAP with intent framework, which may contains intent translation, intent execution and intent decision etc. We would like to provide more POCs around it, and propose to be one of ONAP component or sub-component in the future. In R8, the requirement will provide the internal reference architecture and interacting with other ONAP components, and also introduce intent modeling for specific use cases.

Business Impact - It is a valuable business function that can furthermore reduce the operation expense in terms of automation management.

Business Markets - All operators and service providers that want to use ONAP for network management.

Funding/Financial Impacts - Reduction in operations expense from using procedural while complex operations to using intent-driven declarative operations.

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.