Description

Start from use case analysis for xNF License Management and derive any requirements to ONAP. The aim is for ONAP to support various types (simple, complex, vendor specific) commercial licensing models and use cases. The use cases to start with include xNF onborading, PNF introduction/ONAP PnP, VNF instantation. Based on agreed use cases review relevant ONAP xNF requirements. No impacts to ONAP components foreseen in R6 Frankfurt, potentially minor update of ONAP architecture.

BUSINESS DRIVER

Executive Summary -

Start from use case analysis for xNF License Management and derive any requirements to ONAP. The aim is for ONAP to support various types (simple, complex, vendor specific) commercial licensing models and use cases. The use cases to start with include xNF onborading, PNF introduction/ONAP PnP, VNF instantation. Based on agreed use cases review relevant ONAP xNF requirements. No impacts to ONAP components foreseen in R6 Frankfurt, potentially minor update of ONAP architecture.

Business Impact - xNF License Management is a critical business function. Agreed use cases should allow ONAP to flexibly support commercial licensing models.

Business Markets - This use case applies to any domain (wireless, transport, optical, wireline) that ONAP will manage. It is not a market specific function.

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)

Use Case Contacts & Team

Timo Perala

Samuli Kuusela

DEVELOPMENT IMPACTS

List of PTLs:Approved Projects

*Each Requirement should be tracked by its own User Story in JIRA 

Test Cases and Status