ETSI GS NFV-IFA 004-2017 Network Functions Virtualisation (NFV) Release 2 Acceleration Technologies Management Aspects Specification (V2 3 1).pdf

《ETSI GS NFV-IFA 004-2017 Network Functions Virtualisation (NFV) Release 2 Acceleration Technologies Management Aspects Specification (V2 3 1).pdf》由会员分享，可在线阅读，更多相关《ETSI GS NFV-IFA 004-2017 Network Functions Virtualisation (NFV) Release 2 Acceleration Technologies Management Aspects Specification (V2 3 1).pdf（25页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI GS NFV-IFA 004 V2.3.1 (2017-08) Network Functions Virtualisation (NFV) Release 2; Acceleration Technologies; Management Aspects Specification 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 SPECIFICATION ETSI ETSI GS NFV-IFA 004 V2.3.1 (2017-08) 2 Reference RGS/NFV-IFA004ed231 Keywords acceleration, management, NFV, NFVI, virtualisation E

3、TSI 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: htt

4、p:/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 perceived

5、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 o

6、r 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/CommiteeSup

7、portStaff.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 authori

8、zation 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 ben

9、efit 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 GS NFV-IFA 004 V2.3.1 (2017-08) 3 Contents 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 . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Overview 8g34.0 Introduction 8g34.1 Problem statement 9g34.2 Management of acceleration resources . 9g34.2.

11、1 Overview 9g34.2.2 Feature discovery 10g34.2.2.0 Introduction . 10g34.2.2.1 Acceleration resources discovery . 10g34.2.2.1.1 Discovery mechanism . 10g34.2.2.1.2 Acceleration resources features . 10g34.2.2.2 Feature discovery in NFV acceleration management 11g34.2.3 Lifecycle management of accelerat

12、ion resources . 11g34.2.3.1 Introduction . 11g34.2.3.2 Functionalities . 11g34.2.3.3 Functional requirements 12g35 NFV acceleration management impact on VIM . 13g35.1 General . 13g35.1.1 Impact documented in ETSI GS NFV-IFA 010 13g35.2 Role of SDN controllers . 13g36 NFV acceleration management impa

13、ct on reference points . 15g36.0 Introduction 15g36.1 General Impact on Or-Vi and Vi-Vnfm . 15g36.2 Impact on Or-Vi . 15g36.3 Impact on Vi-Vnfm 15g36.4 Impact on Nf-Vi . 16g3Annex A (informative): Acceleration management information flows 17g3A.1 Introduction 17g3A.2 Acceleration resource allocation

14、 17g3A.3 Acceleration resource release . 19g3Annex B (informative): An implementation example for the acceleration resource management architecture 20g3B.1 Introduction 20g3B.2 Architecture Description 20g3B.2.1 Overview 20g3B.2.2 Information flows . 20g3B.2.2.0 Introduction. 20g3B.2.2.1 Acceleratio

15、n resource allocation example 21g3B.2.2.2 Acceleration resource discovery . 22g3ETSI ETSI GS NFV-IFA 004 V2.3.1 (2017-08) 4 Annex C (informative): Authors Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest up

16、dates 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 IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web se

17、rver) 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 ownership of these except for any which are indicated as being the property of E

18、TSI, 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 those trademarks. Foreword This Group Specification (GS) has been produc

19、ed by ETSI Industry Specification Group (ISG) Network Functions Virtualisation (NFV). Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI D

20、rafting 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 004 V2.3.1 (2017-08) 6 1 Scope The present document specifies functional requirements for both the Virtualised Infrastru

21、cture Manager (VIM) and the NFV Infrastructure (NFVI), for NFV acceleration from an infrastructure management perspective. This includes the controlling and management of acceleration resources, e.g. allocation, release and discovery of acceleration resources. The present document also identifies th

22、e corresponding impacts on VIM related specifications regarding functional requirements ETSI GS NFV-IFA 010 4 and reference points (ETSI GS NFV-IFA 005 2 and ETSI GS NFV-IFA 006 3). 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition

23、 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. Referenced documents which are not found to be publicly available in the expected locati

24、on 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 following referenced documents are necessary for the application of the present document. 1 ETSI GS NF

25、V 003: “Network Functions Virtualisation (NFV); Terminology for main concepts in NFV“. 2 ETSI GS NFV-IFA 005: “Network Functions Virtualisation (NFV); Management and Orchestration; Or-Vi reference point - Interface and Information Model Specification“.g33 ETSI GS NFV-IFA 006: “Network Functions Virt

26、ualisation (NFV); Management and Orchestration; Vi-Vnfm reference point - Interface and Information Model Specification“. 4 ETSI GS NFV-IFA 010: “Network Functions Virtualisation (NFV); Management and Orchestration; Functional Requirements Specification“. 5 ETSI GS NFV-IFA 002: “Network Functions Vi

27、rtualisation (NFV); Acceleration Technologies; VNF Interfaces Specification“. 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 applies. For non-specif

28、ic 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 necessary for the appl

29、ication of the present document but they assist the user with regard to a particular subject area. i.1 Recommendation ITU-T Y.3300 (2014-06): “Framework of software-defined networking“. i.2 ETSI GS NFV-INF 005: “Network Functions Virtualisation (NFV); Infrastructure; Network Domain“. i.3 ETSI GS NFV

30、-MAN 001: “Network Functions Virtualisation (NFV); Management and Orchestration“. ETSI ETSI GS NFV-IFA 004 V2.3.1 (2017-08) 7 i.4 OpenStack Project. NOTE: Available at http:/www.openstack.org/. i.5 ETSI GS NFV-EVE 005: “Network Functions Virtualisation (NFV); Ecosystem; Report on SDN Usage in NFV Ar

31、chitectural Framework“. i.6 ETSI GS NFV-IFA 001: “Network Functions Virtualisation (NFV); Acceleration Technologies; Report on Acceleration Technologies Accelerator chaining; Traffic offload. In the description of these scenarios, the term Network Controller ETSI GS NFV 003 1 is used as per ETSI GS

32、NFV-INF 005 i.2 and encompasses SDN controllers. NFVIMANONFVOVNFCIVIMVNFMHostInfrastructurenetworkNetwork Attached AcceleratorNetworkControllerHW deviceVirtualisationLayerFigure 5.2-1: VNF and accelerator interconnection VNF and accelerator interconnection scenario is illustrated in figure 5.2-1. Fo

33、r accelerators that are accessible through the network, (i.e. network-attached accelerator), SDN is used to provide connectivity between VNF and accelerators. Upon receiving a request for accelerator resource allocation, the VIM shall be able to establish connectivity in the NFVI infrastructure netw

34、ork through a network controller to enable the communication between the VNFCI and the network attached accelerator. Note that the SDN controller being located in the VIM is one of the options described in ETSI GS NFV-EVE 005 i.5. ETSI ETSI GS NFV-IFA 004 V2.3.1 (2017-08) 14 NOTE 1: Generally, the v

35、irtual network ETSI GS NFV 003 1 for communication between the VNFCI and the accelerator is not different from the virtual network for communication between VNFCIs. The network controller simply configures the forwarding rules to attach the accelerator to the internal network of the VNF. If certain

36、constraints are needed (e.g. separate data and control channel) and provided (e.g. via request parameters, VNFD, VIM settings, etc.), the network controller should apply those constraints and configure the VNF internal networks forwarding rules accordingly. Figure 5.2-2: Accelerator chaining Figure

37、5.2-2 illustrates the accelerator chaining scenario. The network controller can chain different accelerators to provide an acceleration service for a certain VNF. The function provided by the network controller is similar to the one provided in the VNF and accelerator interconnection scenario. Figur

38、e 5.2-3: Traffic offload Figure 5.2-3 is an illustration of the traffic offload scenario. For fast path accelerator ETSI GS NFV-IFA 001 i.6, SDN is used to offload the traffic to the NFVI Network. NFVIVNFCIInfrastructurenetworkNetwork Attached AcceleratorNetwork AttachedAcceleratorg4g272g272g286g367

39、g286g396g258g410g286g282g3g393g258g410g346ETSI ETSI GS NFV-IFA 004 V2.3.1 (2017-08) 15 If network acceleration needs to be performed, the VIM (see steps 1 and 2 in figure 5.2-3) instantiates an SDN application and configures the SDN application and Network Controller with the necessary attributes to

40、 establish an adjacency, linking it to a specific VNFCI and Vn-Nf/N/Lx service. In step 3, the VNFCI requests changes through the API to the SDN application. In turn, the SDN application communicates with the Network Controller to offload the traffic to the Infrastructure Network. The request should

41、 be validated by the Network Controller, only endpoints included in the same Vn-Nf/N/Lx service are accepted in the request. Requests to reroute to/from non-adjacent entities should be rejected. In step 4, the Network Controller converts the requests into forwarding rules on the underlying network e

42、lements providing the Vn-Nf/N/Lx service. Step 4 also consists in programming the Infrastructure Network. NOTE 2: Vn-Nf/N/Lx stands for Vn-Nf/N/L2 and Vn-Nf/N/L3 as used per ETSI GS NFV-INF 005 i.2. 6 NFV acceleration management impact on reference points 6.0 Introduction The impact of NFV accelerat

43、ion management on VIM reference points are defined in ETSI GS NFV-IFA 005 2, ETSI GS NFV-IFA 006 3 and ETSI GS NFV-IFA 010 4. In this clause all requirements are therefore referenced from these documents to maintain consistency and clarity. 6.1 General Impact on Or-Vi and Vi-Vnfm The general functio

44、nal requirements for NFV acceleration management on Or-Vi and Vi-Vnfm are documented in clause 6.13 “Functional requirements for NFV acceleration management“ and clause 7.9 “Functional requirements for NFV acceleration management“ in ETSI GS NFV-IFA 010 4. As defined in these requirements, when NFV

45、acceleration is applied, the NFVO shall support the capability to receive and query acceleration capability information from the VIM, as well as select a VIM that has enough available acceleration capabilities to support acceleration capability requirement(s) of the VNF. The NFVO and the VNFM shall

46、support the capability to request to the VIM the allocation and release of necessary acceleration resources to meet acceleration capability requirement(s) of the VNFs when VNF-related Resource Management in indirect mode is applicable, as well as retrieve acceleration capabilities requirement(s) of

47、the VNF from the VNF deployment template. 6.2 Impact on Or-Vi The specific information element requirements on Or-Vi for NFV acceleration management are documented in clauses 8.3.3.2, 8.4.3.2.2, 8.4.3.7.2, 8.4.4.2.2, 8.4.4.6.2, 8.15.3.4.2, 8.15.3.5.2 and 8.15.5.3.2 of ETSI GS NFV-IFA 005 2 with rega

48、rd to the attribute “accelerationCapability“. The requirements mainly specify that when NFV acceleration applies for Or-Vi, if the virtualised compute resource requires resources with certain acceleration capabilities (e.g. packet acceleration library). It should be noted that the cardinality can be

49、 0, if no particular accelerationCapability is requested/provided. 6.3 Impact on Vi-Vnfm The specific information element requirements on Vi-Vnfm for NFV acceleration management are documented in clauses 8.3.2.2, 8.4.2.2, 8.4.2.7, 8.4.3.2, 8.4.3.6, 8.4.13.3 and 8.4.15.2 of ETSI GS NFV-IFA 006 3 with regard to the attribute “accelerationCapability“. The requirements mainly specify that when NFV acceleration applies for Vi-Vnfm, if the virtualised compute resource requires resources with certain acceleration