ETSI GS NFV-IFA 009-2016 Network Functions Virtualisation (NFV) Management and Orchestration Report on Architectural Options (V1 1 1)《网络功能虚拟化(NFV) 管理和协调 架构选项报告(V1 1 1)》.pdf

《ETSI GS NFV-IFA 009-2016 Network Functions Virtualisation (NFV) Management and Orchestration Report on Architectural Options (V1 1 1)《网络功能虚拟化(NFV) 管理和协调 架构选项报告(V1 1 1)》.pdf》由会员分享，可在线阅读，更多相关《ETSI GS NFV-IFA 009-2016 Network Functions Virtualisation (NFV) Management and Orchestration Report on Architectural Options (V1 1 1)《网络功能虚拟化(NFV) 管理和协调 架构选项报告(V1 1 1)》.pdf（31页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI GS NFV-IFA 009 V1.1.1 (2016-07) Network Functions Virtualisation (NFV); Management and Orchestration; Report on Architectural Options Disclaimer The present document has been produced and approved by the Network Functions Virtualisation (NFV) ETSI Industry Specification Group (ISG) and represe

2、nts the views of those members who participated in this ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS NFV-IFA 009 V1.1.1 (2016-07) 2 Reference DGS/NFV-IFA009 Keywords architecture, management, NFV, orchestration ETSI 650 Route des Lu

3、cioles 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: http:/www.etsi.org/stan

4、dards-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 perceived difference in conten

5、ts 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 or change of status.

6、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/CommiteeSupportStaff.aspx Copyr

7、ight 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 authorization of ETSI. The

8、copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ET

9、SI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI GS NFV-IFA 009 V1.1.1 (2016-07) 3 Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31 Scop

10、e 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 NFV Architecture Framework - Release 1 . 7g34.0 introduction 7g34.1 Functional Blocks . 7g34.2 Reference Points . 9g34.3 Interfaces 9g35 K

11、ey rationales driving clarification of Architectural Options 9g36 Architectural Options . 10g36.1 Overview 10g36.2 Architectural options related to VNFM 11g36.2.1 Architectural Option with generic VNFM 11g36.2.1.1 Overview . 11g36.2.1.2 Resource management 11g36.2.1.3 VNF management . 12g36.2.1.4 Cr

12、oss-domain operation 12g36.2.1.5 FCAPS management . 12g36.2.2 Architectural Option with Multiple VNFM(s) 12g36.2.2.0 Introduction . 12g36.2.2.1 Overview . 12g36.2.2.2 Resource management 13g36.2.2.3 VNF management . 13g36.2.2.4 Cross-domain operation 13g36.2.2.5 FCAPS management . 13g36.3 Architectu

13、ral options related to VNF related resource management 14g36.3.1 Architectural option where VNF related resource management done by VNFM . 14g36.3.1.1 Introduction . 14g36.3.1.2 Resource management 14g36.3.1.3 VNF management . 14g36.3.2 Architectural option where VNF related resource management done

14、 by NFVO . 15g36.3.2.1 Introduction . 15g36.3.2.2 Resource management 15g36.3.2.3 VNF management . 16g36.4 Architectural Options related to the split of NFVO 16g36.4.1 Use Case #1- Network Service Orchestrator and Resource Orchestrator . 16g36.4.1.1 Description 16g36.4.1.2 Network Service Orchestrat

15、ion . 17g36.4.1.3 Resource Orchestration . 17g36.4.2 Use Case #2- Service Control and Virtual Network Platform Control . 17g36.4.2.1 Description 17g36.4.2.2 Service Control Functions . 19g36.4.2.3 Virtual Network Platform Control Functions 19g36.4.3 Use Case #3- Network Services offered by a separat

16、e admin domain 19g36.4.3.1 Description 19g36.4.3.2 Umbrella NFVO 20g3ETSI ETSI GS NFV-IFA 009 V1.1.1 (2016-07) 4 6.4.3.3 NFVO in admin domain 21g36.5 Architectural options related to EM functions deployment 21g36.5.1 Introduction. 21g36.5.2 Non-MANO related options . 21g36.5.3 MANO related options 2

17、1g36.5.3.1 Overview . 21g36.5.3.2 EM functions as VNFCs . 21g36.5.3.3 EM functions as VNFs 21g36.5.3.4 EM functions as other Virtualised elements 22g36.6 Architectural options related to VNF lifecycle operation granting 22g36.6.1 Architectural option with bulk granting 22g36.6.1.1 Introduction . 22g

18、36.6.1.2 Pre-requisite conditions for applying bulk granting 23g36.6.1.3 Permission of bulk granting by the NFVO 23g36.6.1.4 Revocation of bulk granting by the NFVO . 23g36.6.1.5 Co-existence with the existing NS level policies at the NFVO . 23g36.6.1.6 Evaluation on bulk granting 24g3Annex A (infor

19、mative): Operational Flows 25g3A.1 Architectural option related to VNF related resource management . 25g3A.1.1 VNF related resource management done by VNFM 25g3A.1.2 VNF related resource management done by NFVO . 26g3A.2 Architectural option related to bulk granting . 26g3A.2.1 Permitting bulk grant

20、ing in pull mode 26g3A.2.2 Permitting bulk granting in push mode 27g3Annex B (informative): Bibliography . 29g3Annex C (informative): Authors Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are ava

21、ilable 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 IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which a

22、re, or may be, or may become, essential to the present document. Foreword This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Network Functions Virtualisation (NFV). Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “

23、may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be 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. ETSI ETSI GS NFV-IFA 0

24、09 V1.1.1 (2016-07) 6 1 Scope The present document is an informative architectural study that identifies different viable architectural and functional options for the partitioning/distribution/consolidation of functionality amongst NFV-MANO functional blocks defined in NFV architectural document ETS

25、I GS NFV 002 i.2 and further refined in NFV-MANO architectural framework ETSI GS NFV-MAN 001 i.4, as well as the potential impact in each case on reference points, on interfaces associated with the reference points, and on information elements exchanged over those interfaces. 2 References 2.1 Normat

26、ive references References are either specific (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) ap

27、plies. Referenced documents which are not found to be publicly available in the expected location might be found at https:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The followin

28、g referenced documents are necessary for the application of the present document. Not applicable. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version app

29、lies. 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 the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not ne

30、cessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI GS NFV 001 (V1.1.1): “Network Functions Virtualisation (NFV); Use Cases“. i.2 ETSI GS NFV 002 (V1.1.1): “Network Functions Virtualisation (NFV); Architectural Framework“. i

31、.3 ETSI GS NFV 003: “Network Functions Virtualisation (NFV); Terminology for Main Concepts in NFV“. i.4 ETSI GS NFV-MAN 001: “Network Functions Virtualisation (NFV); Management and Orchestration“. ETSI ETSI GS NFV-IFA 009 V1.1.1 (2016-07) 7 3 Definitions and abbreviations 3.1 Definitions For the pur

32、poses of the present document, the terms and definitions given in ETSI GS NFV 003 i.3 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI GS NFV 003 i.3. bulk granting: action of giving permission to the VNFM for perf

33、orming associated VNF lifecycle management operations without asking explicit granting from the NFVO 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ETSI GS NFV 003 i.3 apply. An abbreviation defined in the present document takes precedence over the definition

34、of the same abbreviation, if any, in ETSI GS NFV 003 i.3. 4 NFV Architecture Framework - Release 1 4.0 introduction The present document references the NFV-MANO functional blocks, reference points, interfaces and information elements defined in ETSI GS NFV-MAN 001 i.4. 4.1 Functional Blocks The NFV-

35、MANO functional blocks and reference points are illustrated in figure 4.1-1, representing the main architectural diagram in ETSI GS NFV-MAN 001 i.4. ETSI ETSI GS NFV-IFA 009 V1.1.1 (2016-07) 8 Figure 4.1-1: The NFV-MANO architectural framework with reference points The following NFV-MANO functional

36、blocks are the main focus of the present document with respect to potential composition or de-composition in order to realize a specific architectural option: NFV Orchestrator (NFVO) is a functional block with two main responsibilities: - the orchestration of NFVI resources across multiple VIMs, ful

37、filling the Resource Orchestration (RO) functions described in clause 4.2 of ETSI GS NFV-MAN 001 i.4; - the lifecycle management of Network Services (NS), fulfilling the Network Service Orchestration functions described in clause 4.4 of ETSI GS NFV-MAN 001 i.4. VNF Manager (VNFM) is a functional blo

38、ck with the main responsibility for the lifecycle management of VNF instances as described in clause 4.3 of ETSI GS NFV-MAN 001 i.4. Virtualised Infrastructure Manager (VIM) is a functional block with the main responsibility for controlling and managing the NFVI compute, storage and network resource

39、s. The following functional blocks may also be considered in order to provide a more complete architectural option: OSS/BSS is a functional block representing the combination of the operators other operations and business support functions that are not otherwise explicitly captured in the architectu

40、ral diagram. EM is a functional block with the main responsibility for FCAPS management functionality for a VNF. NFVI is a functional block representing all the hardware (e.g. compute, storage, and networking) and software (e.g. hypervisors) components that together provide the infrastructure resour

41、ces where VNFs are deployed. VNF is a functional block representing the Virtualised Network Function. VNF Manager (VNFM) NFVI Execution reference points Main NFV reference points EM VNF Catalogue Or-Vi Ve-Vnfm-vnf Os-Ma-nfvo Ve-Vnfm-em Nf-Vi Vn-Nf OSS/BSS NFV-MANO NFVI ResourceOr-Vnfm Vi-Vnfm NFV In

42、stanceNFV Service Other reference points Virtualised Infrastructure Manager (VIM) VNF NFV Orchestrator (NFVO) ETSI ETSI GS NFV-IFA 009 V1.1.1 (2016-07) 9 4.2 Reference Points The following reference points illustrated in figure 4.1-1 are explored in the present document: Os-Ma-nfvo, a reference poin

43、t between OSS/BSS and NFVO. Ve-Vnfm-em, a reference point between EM and VNFM. Ve-Vnfm-vnf, a reference point between VNF and VNFM. Or-Vnfm, a reference point between NFVO and VNFM. Or-Vi, a reference point between NFVO and VIM. Vi-Vnfm, a reference point between VIM and VNFM. The following referenc

44、e points not illustrated in figure 4.1-1 are explored in the present document: reference point between NFVO and NFVO; reference point between NSO and RO. 4.3 Interfaces The following interfaces are discussed in the present document: Virtualised resources capacity management. VNF lifecycle management

45、. VNF lifecycle change notification. Network Service lifecycle management. Network Service lifecycle change notification. VNF lifecycle operation granting. Interfaces related to bulk granting (such as Bulk granting command, Request/Revoke/Update bulk granting). Interfaces related to new identified r

46、eference points. For additional details applicable to each interface (e.g. specific operations) see ETSI GS NFV-MAN 001 i.4. 5 Key rationales driving clarification of Architectural Options The NFV-MANO architectural framework ETSI GS NFV-MAN 001 i.4 describes functional blocks, reference points, int

47、erfaces associated with the reference points, information elements exchanged over those reference points and a number of operational flows. The deliberate and stated intent of ETSI GS NFV-MAN 001 i.4 was to create an NFV management architecture framework that would allow for multiple possible archit

48、ectural options to emerge. There are some key rationales for continuing to study in more detail the NFV-MANO architecture framework, in order to identify, clarify and document the most viable architectural options, and the impact of pursuing the different architectural options identified. ETSI ETSI

49、GS NFV-IFA 009 V1.1.1 (2016-07) 10 A non-exhaustive list of key rationales driving the need for further analysis and clarification of the different architectural options includes: distribution of functionality between NFVO, VNFM and VIM; in operational flows, the existence of several alternatives for some operations; the potential processing of VNFD content by various functional blocks; the multiple possible interpretations of ownership and access paths to information managed by the diffe