5G RELATED TOPICS

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

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 )

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

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

• Support for using an ETSI v3.3.1 VNF in an ETSI Network 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. 

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 deploying a service that contains an ETSI SOL001 v3.3.1 compliant Network Service 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

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.

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 

• 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 receiving VNF Life Cycle Notifications (LCN) from a VNF Manager

• Support for VNF Heal

• Support for VNF Scale (out, in, level)

• Support for Grant with Incremental resource allocation and HPA support using OOF

• 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. 

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 of a ETSI NS using an external NFVO

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

• Support for Scale, Heal, Update of an ETSI NS using an external NFVO

• 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. 

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 ONAP Service

• Support for onboarding Prototype v4.1.1 SOL004 CSAR Packages

• Support for onboarding Prototype v4.1.1 SOL001 VNF Descriptor

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

• Support for using an 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 onboardig 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.