Use Case Name
| xNF License Management |
Business Driver
This section describes Business Drivers needs.
Executive Summary - Continue 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. These will be reflected as multiple, optional solutions for ONAP. The use cases we started with include xNF onboarding, PNF introduction/ONAP PnP, VNF instantiation. Further use cases to be analyzed, eg. usage monitoring for the purpose of invoicing. Based on agreed use cases review relevant ONAP xNF requirements. Possible SW contributions, eg. in SDC, as well as enhancement of ONAP architecture sequence diagrams.
Business Impact - xNF License Management is a critical business function. Agreed use cases should allow ONAP to flexibly support commercial licensing models.
Business Markets - The requirement applies to any domain (wireless, transport, optical, wireline) that ONAP will manage. It is not a market specific function.
Funding/Financial Impacts - The use case is fundamental for supporting efficiently business agreements between the operator and the vendor.
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.
Development Status
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | |||
| AAF | |||
| APPC | |||
| CLAMP | |||
| CC-SDK | |||
| DCAE | |||
| DMaaP | |||
| External API | |||
| MODELING | |||
Multi-VIM / Cloud | |||
| OOF | |||
| POLICY | |||
| PORTAL | |||
| SDN-C | |||
| SDC | |||
| SO | |||
| VID | |||
| VNFRQTS | |||
| VNF-SDK | |||
| CDS |
List of PTLs:Approved Projects
Use Case Diagram
On this xNF Licensing Management solution use cases (xNF onboarding, PNF introduction/ONAP PnP and VNF instantiation), there are no related ONAP user interactions.
Use Case Functional Definitions
Use Case Title | xNF Licensing Management |
Actors (and System Components) | No actors participate in this use case. Participating System Components: xNF and License Service (external to ONAP) |
Description | This xNF Licensing Management use case aims to support various types (simple, complex, vendor specific) commercial licensing models. In this particular solution, this achieved by support of ONAP-external License Service. |
Points of Contact | |
Preconditions | The PNF or VNF/CNF needs to be bootstrapped or instantiated; the ONAP-external License Service needs to be operational and reachable by the xNF. |
Triggers / Begins when | The use case can begin at any time after PNF or VNF/CNF bootstrapping or instantiation has happened. |
Steps / Flows (success) | See the sequence diagrams, slides 4,5,6 in the ArchCom presentation: https://jira.onap.org/secure/attachment/15986/ONAP%20license%20mgmt%20-%20ArchCom%20Guilin.pptx |
Post-conditions | The xNF has successfully obtained licenses from the external License Service. |
Alternate / Exception Paths | - |
Related Use Cases | - |
Assumptions | Existence of ONAP-external License Service which is reachable for the xNF. |
Tools / References / Artifacts | Jira tickets: R7 requirement: REQ-353 - Getting issue details... STATUS ArchCom: ONAPARC-577 - Getting issue details... STATUS SDC: SDC-3103 - Getting issue details... STATUS VNFRQTS: VNFRQTS-893 - Getting issue details... STATUS Documentation: |
Testing
Current Status
End to End flow to be Tested
Test Cases and Status
| 1 | There should be a test case for each item in the sequence diagram | NOT YET TESTED |
| 2 | create additional requirements as needed for each discreet step | COMPLETE |
| 3 | Test cases should cover entire Use Case | PARTIALLY COMPLETE |
| 4 | Test Cases should include enough detail for testing team to implement the test | FAILED |
Reference
- ONAP Wiki page Template: Template page in R7