1、 ETSI GR NFV-EVE 010 V3.1.1 (2017-12) Network Functions Virtualisation (NFV) Release 3; Licensing Management; Report on License Management for NFV Disclaimer The present document has been produced and approved by the Network Functions Virtualisation (NFV) ETSI Industry Specification Group (ISG) and
2、represents the views of those members who participated in this ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP REPORT ETSI ETSI GR NFV-EVE 010 V3.1.1 (2017-12)2 Reference DGR/NFV-EVE010 Keywords license schemes, management, NFV ETSI 650 Route des Lucioles F-0692
3、1 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search
4、The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between su
5、ch versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information o
6、n the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notifica
7、tion No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and
8、 the foregoing restriction extend to reproduction in all media. ETSI 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are trademarks of ETSI registered for the benefit of its Members and of the 3G
9、PP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSM and the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI GR NFV-EVE 010 V3.1.1 (2017-12)3 Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g3Introduct
10、ion 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 NFV licenses 8g34.1 NFV licenses scope 8g34.2 NFV licenses categorization . 8g34.2.1 Introduction. 8g34.2.2 Open Source softw
11、are licenses . 9g34.2.3 Proprietary software licenses 9g34.2.4 Declarative software licenses 10g34.3 VNF licenses 10g34.4 Enforcement of VNF licenses 11g35 NFV Licenses use cases . 11g35.1 Use Case 1: On-demand instantiation and termination of Virtual Firewall (vFirewall) . 11g35.1.1 Introduction. 1
12、1g35.1.2 Business Value 11g35.1.3 Actors and roles 12g35.1.4 Pre-conditions . 12g35.1.5 Post-conditions . 12g35.1.6 Flow description . 12g35.2 Use Case 2: VNF licenses implications for sharing of vFirewall VNFs instances across NFVI-PoPs 13g35.2.1 Introduction. 13g35.2.2 Business Value 14g35.2.3 Act
13、ors and roles 14g35.2.4 Pre-conditions . 14g35.2.5 Post-conditions . 14g35.2.6 Flow description . 15g35.3 Use Case 3: Applying revised license terms to an on-boarded VNF Package . 15g35.3.1 Introduction. 15g35.3.2 Business Value 16g35.3.3 Actors and roles 16g35.3.4 Pre-conditions . 16g35.3.5 Post-co
14、nditions . 16g35.3.6 Flow description . 17g35.4 Use Case 4: Applying VNF license to enable or disable VNF functionalities . 17g35.4.1 Introduction. 17g35.4.2 Business Value 17g35.4.3 Actors and roles 17g35.4.4 Pre-conditions . 18g35.4.5 Post-conditions . 18g35.4.6 Flow description . 18g35.5 Use Case
15、 5: License event reporting 19g35.5.1 Introduction. 19g3ETSI ETSI GR NFV-EVE 010 V3.1.1 (2017-12)4 5.5.2 Business Value 19g35.5.3 Actors and roles 19g35.5.4 Pre-conditions . 20g35.5.5 Post-conditions . 20g35.5.6 Flow description . 20g35.6 Use Case 6: Identifying the need of additional license . 20g3
16、5.6.1 Introduction. 20g35.6.2 Business Value 20g35.6.3 Actors and roles 20g35.6.4 Pre-conditions . 20g35.6.5 Post-conditions . 21g35.6.6 Flow description . 21g35.7 Use Case 7: Use of declarative licenses for vEPC-VNF 21g35.7.1 Introduction. 21g35.7.2 Business value 21g35.7.3 Actors and roles 22g35.7
17、.4 Pre-conditions . 22g35.7.5 Post-conditions . 22g35.7.6 Flow description . 23g36 Use case analysis 23g36.1 VNF license recommendations . 23g37 NFV license final report . 29g37.1 Management and operational aspects . 29g3Annex A: Authors Essential, or potentially Essential, IPRs notified to ETSI in
18、respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence
19、 of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims
20、no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations assoc
21、iated with those trademarks. Foreword This Group Report (GR) has been produced by ETSI Industry Specification Group (ISG) Network Functions Virtualisation (NFV). Modal verbs terminology In the present document “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to b
22、e interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. Introduction Today there is huge diversity of license management mechanisms across VNF
23、Providers which makes service provisioning and license renewing operations more complex, error prone and time consuming. It also makes it difficult to deal with VNF license usage information for settlement between the Service Provider and the VNF Provider. These issues can be resolved by establishin
24、g a standard NFV license management architecture which will have the following benefits: Speed up provision of VNF service without customizing the license management procedure for each VNF-type or VNF Provider. Simplifying acquisition of VNF license usage information. Reduce licensing errors. Simpli
25、fied license management operations independent of the underlying VNF solution. A guiding principle is to minimize the impact on the existing NFV specifications by identifying the minimum features needed to implement any commercial license management framework typically residing in a separate or high
26、er layer system (e.g. OSS/BSS). In order to provide a standardized licensing mechanism, it is necessary to identify the functional blocks, interfaces, and flows impacted by the requirement to implement any commercial license management framework. ETSI ETSI GR NFV-EVE 010 V3.1.1 (2017-12)6 1 Scope Th
27、e present document studies the features needed within the NFV-MANO framework to support license management for NFV. In this version of the document, a focus is made on the software licenses for VNFs. A set of use cases related to VNF licenses in the NFV environment are described, analyzed and used t
28、o understand the issues and produce recommendations regarding support for license management within the NFV architectural and NFV-MANO frameworks. 2 References 2.1 Normative references Normative references are not applicable in the present document. 2.2 Informative references References are either s
29、pecific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks incl
30、uded in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 TM Forum IG1143 Release 1
31、6.5.1: “Frameworx Exploratory Report - License Management“. i.2 ISO/IEC 19770-5:2015: “Information technology - IT asset management - Part 5: Overview and vocabulary“. NOTE: Available at https:/www.iso.org/standard/68291.html. i.3 ETSI GS NFV 003: “Network Functions Virtualisation (NFV); Terminology
32、 for Main Concepts in NFV“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in i.3 and the following apply: NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in i.3. li
33、cense key: identifier key or activation code associated with VNF, made available by VNF Provider to Service Provider for operating a VNF instance license pool: pool of licenses containing licenses to be processed on-demand without need for real-time interaction with the VNF Provider NOTE: The Servic
34、e Provider could maintain a real-time view of all licenses available in the license pools. ETSI ETSI GR NFV-EVE 010 V3.1.1 (2017-12)7 VNF license: legal rights to use a VNF in accordance with terms and conditions specified by the VNF licensor NOTE 1: “Using a VNF“ can include: accessing, copying, di
35、stributing, installing and executing the VNF software, depending on the licenses terms and conditions. NOTE 2: Specified license terms and conditions can include VNF components license information if different than the one of the VNF. NOTE 3: This definition has been specialized from the term “softw
36、are license“ as defined in International Standard ISO/IEC 19770-5 i.2. VNF license entitlement: VNF license use rights as defined through agreements between a VNF licensor and a VNF licensee NOTE 1: Effective use rights take into account any contracts and all applicable licenses, including full lice
37、nses, upgrade licenses and maintenance agreements. NOTE 2: A commonly used synonym for this term is “VNF license terms“. NOTE 3: This definition has been specialized from the term “software entitlement“ as defined in International Standard ISO/IEC 19770-5 i.2. VNF licensee: person or organization gr
38、anted a license to use a specific VNF NOTE: This definition has been specialized from the term “software licensee“ as defined in International Standard ISO/IEC 19770-5 i.2. VNF licensor: person or organization who owns or holds the rights to issue a VNF license for a specific VNF package NOTE 1: Thi
39、s entity might or might not create the VNF software. NOTE 2: This definition has been specialized from the term “software licensor“ as defined in International Standard ISO/IEC 19770-5 i.2. VNF usage: consumption against a VNF license entitlement measured as defined by the terms and conditions of th
40、at entitlement NOTE 1: Depending on the specific terms and conditions, usage can include accessing, copying, distributing, installing and executing the VNF software. NOTE 2: This definition has been specialized from the term “software usage“ as defined in International Standard ISO/IEC 19770-5 i.2.
41、3.2 Abbreviations For the purposes of the present document, the abbreviations given in i.3 and the following apply: NOTE: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any in i.3. BSD Berkeley Software Distribution BSS Business Supp
42、ort System CAPEX Capital Expenditures CI/CD Continuous Integration / Continuous Development EM (Network) Element Manager EPC Evolved Packet Core EULA End-User License Agreement FOSS Free and Open Source Software GPL General Public License IMS IP Multimedia Subsystem LGPL Lesser General Public Licens
43、e LM License Management MIT Massachusetts Institute of Technology MPL Mozilla Public License ETSI ETSI GR NFV-EVE 010 V3.1.1 (2017-12)8 NFVI Network Functions Virtualisation Infrastructure NFVO NFV Orchestrator OPEX Operational Expenditure OSS Operation Support System PAYG Pay As You Go/Grow RGW Res
44、idential GateWay SAM Software Asset Management SAU Simultaneous Active Users VNF Virtual Network Function VNFC Virtualised Network Function Component 4 NFV licenses 4.1 NFV licenses scope Generally speaking (see note) the software licenses differ according to the rights that are actually granted to
45、the licensee by the licensor. The scope of those rights covers all what the licensee could do with the licensed software in his business processes and which may be subject to authorization by the licensor. Usually, the licensee might copy the software, possibly modify for internal development purpos
46、e, resell the derived software and by the way sublicense the acquired licensed software, distribute it as such or simply deploy and use it to provide services to his customers. The rights can be granted for a delimited period, i.e. subscription-based license or without time limit, i.e. perpetual lic
47、ense. NOTE: This is not limited to NFV software. 4.2 NFV licenses categorization 4.2.1 Introduction Different types of software licenses exist today and many of them can be reused in the context of NFV. A classification is generally made according to the entitlement regarding the reproduction (i.e.
48、copy), distribution and use of the software, which can be different depending on the process of software production and motivations of the licensor, which can be, for example a software editor or an open source community. Table 1 gives a high level classification of software licenses. Table 1: Overa
49、ll classification of software licenses Rights Public domain Free and Open Source Software (FOSS) Proprietary Trade secret Open Source (Without copyleft) Open Source (Weak copyleft) Open Source (Strong copyleft) Freeware, Shareware, Freemium Examples SQLite, ImageJ Apache, BSD, MIT GNU LGPL, MPL GNU GPL, GNU Affero Irfanview, Winamp Windows World of warcraft Copyright retained No Yes Yes Yes Yes Yes Yes Right to use Yes Yes Yes Yes Yes Yes No Right to copy Yes Yes Yes Yes Often No No Right to modify Yes Yes Yes Yes No No No Right to distribute
