You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Table of Contents


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 

Click here to get: E2E Network Slicing High level requirements report on Mar 2nd Requirement Subcommittee Call.

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

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. The envisioned scenario is based on both CNFs deployed on kubernetes 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.

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.

 


  • No labels