August 26, 2019 Use Case Sub-Committee License Management Use Cases Frankfurt release Samuli Kuusela, Ericsson Timo Perälä, Nokia For the reader: slides 10-15 are the newest with most details August 26, 2019 Use Case Sub-Committee

xNF License Management and ONAP 2018-02-21 xNF License Management and ONAP Background Purpose Definitions Principles Use Cases

Background There are already License Management related contributions in ONAP including a draft model proposal. This presentation aims to refocus the discussion starting with use case analysis and derive any actions that may be required within ONAP.

Purpose To provide xNF License Management input in the ONAP Community. To enable a solution that easily supports simple or complex, vendor specific Commercial Licensing Models and Use Cases.

2018-02-21 Definitions License (License key or License key file): gives the legal rights to use a xNF function in accordance with terms and conditions specified by the xNF licensor. License format is vendor specific. Commercial Licensing Model: Reflects the vendor specific price & sales models and other properties of a contract between vendor and operator. Commercial License Models are vendor specific. License Support Service: is the vendor specific support application reachable by the vendor’s xNF instances, to manage vendor specific licenses in each individiual xNF in accordance with the agreed Commercial Licensing Model.

VNF and PNF Licensing Principles 2018-02-21 VNF and PNF Licensing Principles xNF License Management support is optional in ONAP Not all the Commercial Licensing Models need to be supported in MANO (ETSI IFA034) Licenses are obtained from vendor License Support Service by the xNF or Licenses are logically allocated to xNF by License Support Service. xNF License Support Service is vendor specific and deployed in the customer NW, independently of ONAP Advanced Commercial Licensing Models may be provided by vendors

Use Cases with license management aspects added PNF introduction / ONAP PnP VNF instantiation ....

Use Case: PNF introduction with ONAP Plug and Play 2018-02-21 Use Case: PNF introduction with ONAP Plug and Play The Licenses should be obtained by the PNF or Licenses are logically allocated to PNF before or after the PNF registration takes place It is out of the scope of ONAP how Licenses are obtained by the PNF or how Licenses are logically allocated to PNF Licensing issues are resolved without interfering with ONAP processes or interrupting in-service xNFs.  

Use Case: VNF instantiation 2018-02-21 Use Case: VNF instantiation The Licenses can be obtained by the VNF or licenses can be logically allocated to VNF before or after the ONAP O&M connectivity with the VNF takes place. It is a VNF choice whether it is before or after (no need for both alternatives) It is outside the ONAP scope when and how VNF obtains licenses or how licenses are allocated to VNF. Licensing issues are resolved without interfering with ONAP processes or interrupting in-service xNFs.  

ONAP Frankfurt goals: License Management Use Cases 2018-02-21 ONAP Frankfurt goals: License Management Use Cases Define the license management principles wrt the key UCs: xNF onboarding, PNF introduction / ONAP PnP, VNF instantiation Eg: is license mgmt service part of ONAP, or outside of ONAP Based on the approved UCs: review/update the ONAP License Management VNF requirements Possibly minor update of ONAP architecture Notes: No impacts to ONAP SW components foreseen in Frankfurt Status & way forward as of 2019-09-26 Presented already once in: Use Case SC, Modeling SC, Use Case Realization mtg Development of the Use Cases will continue in the Use Case SC Agreed to present in Architecture SC Agreed to align with the on-going license mgmt model draft work in Modeling SC

xNF licence management and ONAP For ONAP subcommittees F2F, Antwerp, 2019-09-26

xNF Licensing Principles (1/3) 2018-02-21 xNF Licensing Principles (1/3) Principle 1) xNF capacity and feature license management is outside of ONAP scope Motivations: Any kind of vendor specific, more advanced or tailored xNF Commercial Licensing Models need to be supported. It is necessary to enable innovation on new Commercial Licensing Models. It is not realistic that ONAP implementation could support all of those. The SW delivery flow, and capacity and feature licenses delivery flow are separate. Side-note: For Nokia and Ericsson xNFs, the number of VNF instances is not license controlled. If this type of license control needs to be supported in ONAP, the interested parties in the community should drive the use cases.

xNF Licensing Principles (2/3) 2018-02-21 xNF Licensing Principles (2/3) Principle 2) Licenses are obtained from vendor License Support Service by the xNF or Licenses are logically allocated to xNF by License Support Service. Principle 3) xNF License Support Service is vendor specific and deployed in the customer NW, independently of ONAP.

xNF Licensing Principles (3/3) 2018-02-21 xNF Licensing Principles (3/3) Usage measurement based models - The Commercial Licensing Model of xNF may require usage data measurements - Measured data may be related to eg. capacity or feature usage - xNF vendor may have implemented a mechanism which enables verification of the integrity of the collected usage data Principle 4) ONAP may be also utilized for collecting xNF usage data from the xNFs. Principle 5) The collected xNF usage data shall be transported to xNF vendor, using a mechanism trusted by the vendor.

xNF Licensing: Additional ONAP Use Cases 2018-02-21 xNF Licensing: Additional ONAP Use Cases Use Case: xNF SW Upgrade Nokia and Ericsson xNFs From ONAP pov, this use case is disconnected from xNF capacity and feature license management. This is because: - licensing issues are resolved without interfering with ONAP processes or interrupting in-service xNFs - the number of xNF instances is not controlled by licenses Other vendors No information