...
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 |
Authors and maintainers of the Use Case.
Use Case Lead, Key Use Case members and code contributors.
Preconditions
A list of conditions that are assumed to be true before the Use Case is invoked
Includes description of Information Consumed
Triggers / Begins when
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 |
Interaction diagrams may be included or referenced
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 |
List of any tools or reference material associated with this Use Case as well as any JIRA trace-ability.
List of any associated diagrams or modelling artifacts associated with the Use CaseJira tickets: R7 requirement:
ArchCom:
SDC:
VNFRQTS:
Documentation: |
Testing
Current Status
End to End flow to be Tested
...