1、 ETSI GR NFV-EVE 008 V3.1.1 (2017-12) Network Function Virtualisation (NFV) Release 3; Charging; Report on Usage Metering and Charging Use Cases and Architectural Study Disclaimer The present document has been produced and approved by the Network Functions Virtualisation (NFV) ETSI Industry Specific
2、ation Group (ISG) and 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 008 V3.1.1 (2017-12)2Reference DGR/NFV-EVE008 Keywords charging, management, MANO, NFV, orchestration
3、 ETSI 650 Route des Lucioles F-06921 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: h
4、ttp:/www.etsi.org/standards-search 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 perceive
5、d difference in contents between such 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
6、 or change of status. Information on 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/CommiteeS
7、upportStaff.aspx Copyright Notification 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 autho
8、rization of ETSI. The copyright and 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 b
9、enefit of its Members and of the 3GPP 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 008 V3.1.1 (2017-12)3Contents Intellectual Property Rights 5g3Foreword . 5g3Mo
10、dal verbs terminology 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Charging Concepts in NFV 7g34.1 High Level Expectations 7g34.2 Resources in NFV 7g34.3 Chargeable Events 8g
11、34.3.0 Introduction. 8g34.3.1 Usage Events 8g34.3.2 Management and Orchestration Events 8g34.4 Charging Scenarios. 9g35 Use Cases for Usage Metering and Charging Triggers 9g35.1 General . 9g35.2 Actors, Roles and Domains 9g35.2.0 introduction . 9g35.2.1 Actors and Business Relationships . 10g35.3 Us
12、e Case #1: Charging for NFV Infrastructure as a Service 11g35.3.1 Actors 11g35.3.2 Motivation. 11g35.3.3 Summary . 11g35.3.4 Pre-Condition 12g35.3.5 Begins When . 12g35.3.6 Description 12g35.3.7 Ends When 13g35.3.8 Post-Conditions . 13g35.3.9 Exceptions. 13g35.4 Use Case #2: Charge For VNF as a Serv
13、ice . 14g35.4.1 Actors 14g35.4.2 Motivation. 14g35.4.3 Summary . 14g35.4.4 Pre-Conditions 14g35.4.5 Begins When . 14g35.4.6 Description 14g35.4.7 Ends When 16g35.4.8 Post-Conditions . 16g35.4.9 Exceptions. 16g36 Charging Triggers in an NFV Architectural Framework . 16g36.1 Online Charging Architectu
14、re for NFV 16g36.1.1 Online Charging Architecture for NFV Infrastructure as a Service 16g36.1.1.0 introduction . 16g36.1.1.2 New Architectural Functional Capabilities . 17g36.1.1.2.1 Charging Quota Tracker 17g36.1.1.2.2 Charging Trigger Point 17g36.1.1.3 Direct Approach: Charging Triggering Point to
15、 Charging Function . 17g36.1.1.4 Relay Approach: Charging Triggering Point to Charging Function . 18g36.1.1.5 Basic Flow. 19g3ETSI ETSI GR NFV-EVE 008 V3.1.1 (2017-12)46.1.2 Online Charging Architecture for VNF as a Service 19g36.2 Offline Charging Architecture for NFV . 20g36.2.1 Offline Charging I
16、mpact on NFV Architecture 20g36.2.2 Offline Charging Overlay Architecture 21g36.2.2.1 Introduction . 21g36.2.2.2 Relayed CDR Delivery Scenario . 21g36.2.2.3 Direct CDR Delivery Scenario 22g37 Recommendation 23g3Annex A: Authors Essential, or potentially Essential, IPRs notified to ETSI in respect of
17、 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 of other
18、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 no ownersh
19、ip 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 associated with
20、 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 be interpre
21、ted 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. ETSI ETSI GR NFV-EVE 008 V3.1.1 (2017-12)61 Scope The present document studies use cases and char
22、ging triggers for usage metering of virtualised resources. It proposes new functional blocks for: 1) the collection and provision of accounting information; and 2) the triggering of charging requests. The interfaces (and information flows) between the proposed functional blocks and the current NFV A
23、rchitectural Framework are part of the study. The following models have been taken into account: Infrastructure as a Service (IaaS), and VNF as a Service (VNFaaS). The present document includes recommendations to either modify existing or new specifications, or both. While management and orchestrati
24、on event charging for VNFaasS is part of the present work, usage event charging for VNFaaS is for further study. 2 References 2.1 Normative references Normative references are not applicable in the present document. 2.2 Informative references References are either specific (identified by date of pub
25、lication 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 included in this clause were valid at
26、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 ETSI GS NFV 003: “Network Functions Virtualisation (NFV); T
27、erminology for Main Concepts in NFV“. i.2 TM Forum GB989 Impact of SDN/NFV on Charging and Billing R15.5.1 Standard. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI GS NFV 003 i.1 and the following apply: resource moni
28、tor: agent within the resource that monitors resource usage and reports to Charging Function ETSI ETSI GR NFV-EVE 008 V3.1.1 (2017-12)73.2 Abbreviations For the purposes of the present document, the abbreviations given in ETSI GS NFV 003 i.1 and the following apply: BSS Business Support Systems CDR
29、Call Detail RecordCPU Central Processing Unit CTP Charging Triggering Point CTQ Charging Quota Tracker IaaS Infrastructure as a Service MANO Management and Orchestration MNO Mobile Network Operator MVNO Mobile Virtual Network Operator OSS Operations Support Systems QT Quota Tracker SaaS Software as
30、a Service VIM Virtualised Infrastructure Manager 4 Charging Concepts in NFV 4.1 High Level Expectations The high-level expectations for usage metering and charging in NFV are: to provide charging information for all charges incurred and requiring settlement between the different roles (e.g. NFV Infr
31、astructure Provider, VNF Provider, VNF Service Provider, Consumer, etc.); to produce sufficient charging information to allow for the following: - revenue assurance on NFV resource usage; - fraud detection and mitigation; - itemized billing for all NFV resource usage by the charged party; - cost con
32、trol of NFV resource usage by the charged party; - to support for a charged party to prepay for NFV resources; to support NFV management and orchestration lifecycle events to be mapped to chargeable events; to provide real-time usage information. 4.2 Resources in NFV Below is a list of resources (se
33、e clause 3.1 for definitions) that are deemed to be of value for users and operators, and thus chargeable for consumption of those resources. Hardware resources are not taken into consideration in this clause. Virtualisation Layer Virtualisation Container Virtualised Resources: - Virtualised CPU inc
34、luding processor and memory - Virtualised Storage including volumes of storage at either block or file-system level - Virtual Network including networks, subnets, ports, addresses, links and forwarding rules, for the purpose of ensuring intra- and inter-VNF connectivity ETSI ETSI GR NFV-EVE 008 V3.1
35、.1 (2017-12)8 Virtualised Accelerator: An accelerator is a software or hardware component (as stated above hardware resources are not taken into consideration) intended to improve the NFVI performance or to enable VNFs to offload some portion of their processing VNF Instance: A VNF is considered as
36、a composite resource consisting of a number of Virtualised Compute, Virtual Network and Virtualised Storage resources Network Service Instance The list of resources and corresponding functional blocks that provide information on resource consumption is presented in table 1. Table 1: Mapping resource
37、s to functional blocks Resources in NFV Functional Block Virtualisation Layer VIM Virtualisation Container VIM Virtual Resources VIM Virtualised Accelerators VIM VNF Instance NFVO/VNFM Network Service Instance NFVO 4.3 Chargeable Events 4.3.0 Introduction Chargeable events are those events that prov
38、ide Charging and Billing functions with information for rating and billing purposes. Information can be related to usage of resources or management tasks, such as reservation, instantiation, scaling, and termination of virtual resources (see clause 4.1). Therefore, chargeable events can be classifie
39、d into these two categories: Usage Events Management and Orchestration Events 4.3.1 Usage Events In the perspective of NFV MANO Usage Events are those events which provide usage information of NFV resources (as defined in clause 4.2) in volume/duration or combination of both. For example, a usage ev
40、ent representing the “Peak or average number of CPU cores used in the last one hour duration by a running VNF instance“. 4.3.2 Management and Orchestration Events “Management and Orchestration“ event is a unique action performed by NFV MANO through one or more function or API calls to achieve the de
41、sired output such as (not a complete list): Create/Delete VNF Instance Create/Delete Virtualisation Container Scale VNF Instance Create/Delete Network Service Instance ETSI ETSI GR NFV-EVE 008 V3.1.1 (2017-12)94.4 Charging Scenarios The charging scenarios that are relevant to real-time charging of c
42、hargeable items: Event based charging model is applicable for management and orchestration events and involves an immediate charging action in a single charge request: - In this charging scenario, the chargeable item is immediately charged in a single transaction. For example, instantiation of a VNF
43、. Continuous based charging model is applicable for resource consumption and will be based on sessions: In this charging method, the consumption of data traffic (or CPU time or storage) by virtual resources is the chargeable item. So examples are volume and the length of time. Continuous charging st
44、arts when a resource consumption begins, for example, at the start of data transfer and ends on resource termination or lack of funds/credit limit for consumption. Continuous charging flow involves an initial quota request, followed by one or more intermediate quota requests, and finally followed by
45、 a stop charging request. 5 Use Cases for Usage Metering and Charging Triggers 5.1 General Table 2 summarizes the two use cases described in this clause for charging triggers. Table 2: Summary of Use Cases Use Case # Use Case Name 1 Charging for NFV Infrastructure as a Service 2 Charging for VNF as
46、a Service Each use case is described using the following items: Motivation Summary Pre-Condition Begins When Description End When Post-Condition Exception 5.2 Actors, Roles and Domains 5.2.0 introduction This item introduces the concepts of actors, roles and domains used in the use cases description
47、. Table 3 provides the list of Actors that have been identified. ETSI ETSI GR NFV-EVE 008 V3.1.1 (2017-12)10Table 3: Definition of Actors Actor Definition NFV Infrastructure Provider The entity that owns the infrastructure and provides infrastructure as a service NFV Infrastructure Consumer The user
48、 of Infrastructue as a Service VNF Provider The entity that sells VNF Software VNF Service Provider The entity that offers VNF as a service to an End User VNF Consumer The user of VNF as a service Consumer The user of the service offered Mobile Network Operator The entity that provides hosted VNFs t
49、o its MVNO customers 5.2.1 Actors and Business Relationships Many actors are involved in the end-to-end service delivery within an NFV framework. Aligned with the TM Forum proposal (TMF GB989) i.2 and through an example, the possible actors and their business relationships are highlighted. The example considered in the present document is of an intelligent lighting system for the streets of a city. The system consists of connected street lights and ensures energy efficiency by offering optimal light intensity. It al
