ETSI GR MEC 017-2018 Mobile Edge Computing (MEC) Deployment of Mobile Edge Computing in an NFV environment (V1 1 1).pdf

《ETSI GR MEC 017-2018 Mobile Edge Computing (MEC) Deployment of Mobile Edge Computing in an NFV environment (V1 1 1).pdf》由会员分享，可在线阅读，更多相关《ETSI GR MEC 017-2018 Mobile Edge Computing (MEC) Deployment of Mobile Edge Computing in an NFV environment (V1 1 1).pdf（32页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI GR MEC 017 V1.1.1 (2018-02) Mobile Edge Computing (MEC); Deployment of Mobile Edge Computing in an NFV environment Disclaimer The present document has been produced and approved by the Mobile Edge Computing (MEC) ETSI Industry Specification Group (ISG) and represents the views of those members

2、 who participated in this ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP REPORT ETSI ETSI GR MEC 017 V1.1.1 (2018-02) 2 Reference DGR/MEC-0017MECinNFV Keywords MEC, NFV ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00

3、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 The present document may be made available in electronic v

4、ersions 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 such versions and/or in print, the only prevailing document

5、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 on the current status of this and other ETSI documents is a

6、vailable 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 Notification No part may be reproduced or utilized in any form or

7、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 the foregoing restriction extend to reproduction in all m

8、edia. ETSI 2018. 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 3GPP Organizational Partners. oneM2M logo is protected for t

9、he benefit of its Members. GSM and the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI GR MEC 017 V1.1.1 (2018-02) 3 Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informati

10、ve references 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Introduction 8g35 Reference Architecture . 8g35.1 Overview and assumptions . 8g35.2 MEC reference architecture in NFV environments 9g35.3 Realization of the mobile edge platform as a VNF 10g35.4 Realiza

11、tion of the Data Plane . 11g36 Key issues . 12g36.1 Issue #1: Mapping of ME app VNFs to Network Services 12g36.1.1 Problem description 12g36.1.2 Solution(s). 12g36.1.3 Evaluation . 13g36.1.4 Proposal 13g36.2 Issue #2: Usage of NFV Network Service 13g36.2.1 Problem description 13g36.2.2 Solution(s).

12、14g36.2.3 Evaluation . 14g36.2.4 Proposal 14g36.3 Issue #3: Communication between MEAO and NFVO via Mv1 . 14g36.3.1 Problem description 14g36.3.2 Solution(s). 14g36.3.3 Evaluation . 16g36.3.4 Proposal 16g36.4 Issue #4: Communication between VNFM and MEPM-V via Mv2 16g36.4.1 Problem description 16g36

13、.4.2 Solution(s). 16g36.4.3 Evaluation . 17g36.4.4 Proposal 17g36.5 Issue #5: Communication between VNFM and ME app instance via Mv3 18g36.5.1 Problem description 18g36.5.2 Solution(s). 18g36.5.3 Evaluation . 18g36.5.4 Proposal 19g36.6 Issue #6: AppD vs. VNFD for ME app VNFs 19g36.6.1 Problem descri

14、ption 19g36.6.2 Solution(s). 19g36.6.3 Evaluation . 20g36.6.4 Proposal 20g36.7 Issue #7: VNF Package vs. MEC application package . 21g36.7.1 Problem description 21g36.7.2 Solution(s). 21g36.7.3 Evaluation . 21g36.7.4 Proposal 21g36.8 Issue #8: VNF package onboarding 21g3ETSI ETSI GR MEC 017 V1.1.1 (

15、2018-02) 4 6.8.1 Problem description 21g36.8.2 Solution(s). 21g36.8.3 Evaluation . 22g36.8.4 Proposal 22g36.9 Issue #9: Managing traffic redirection 22g36.9.1 Problem description 22g36.9.2 Solution(s). 23g36.9.3 Evaluation . 23g36.9.4 Proposal 24g36.10 Issue #10: Comparison of AppD and VNFD data str

16、uctures 24g36.10.1 Problem description 24g36.10.2 Solution(s). 24g36.10.3 Evaluation . 25g36.10.4 Proposal 25g36.11 Issue #11: NFV construct that corresponds to Mobile Edge Host 25g36.11.1 Problem description 25g36.11.2 Solution(s). 26g36.11.3 Evaluation . 26g36.11.4 Proposal 26g36.12 Issue #12 : ME

17、 App VNF Instance Relocation 26g36.12.1 Problem description 26g36.12.2 Solution(s). 26g36.12.3 Evaluation . 26g36.12.4 Proposal 26g36.13 Issue #13: Application instantiation . 27g36.13.1 Problem description 27g36.13.2 Solution(s). 27g36.13.3 Evaluation . 27g36.13.4 Proposal 27g36.14 Issue #14: Appli

18、cation instance termination. 27g36.14.1 Problem description 27g36.14.2 Solution(s). 28g36.14.3 Evaluation . 28g36.14.4 Proposal 28g37 Recommendation 28g37.1 Way forward . 28g37.2 Architecture impact 29g37.3 Needed normative work . 29g37.3.1 General 29g37.3.2 Normative work suggested to be performed

19、in ETSI NFV . 29g37.3.3 Normative work suggested to be performed in ETSI MEC 30g37.4 Items that require further study 30g38 Conclusion 31g3History 32g3ETSI ETSI GR MEC 017 V1.1.1 (2018-02) 5 Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverab

20、les may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of

21、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 I

22、PRs 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 ownershi

23、p 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

24、those trademarks. Foreword This Group Report (GR) has been produced by ETSI Industry Specification Group (ISG) Mobile Edge Computing (MEC). Modal verbs terminology In the present document “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as descr

25、ibed 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 MEC 017 V1.1.1 (2018-02) 6 1 Scope The present document describes solutions that allow the deplo

26、yment of MEC in a NFV environment. For each solution, it describes the motivation for the solution, its architectural impacts and the necessary work to enable it. The document provides recommendations as for where the specification work needs to be done. 2 References 2.1 Normative references Normati

27、ve references are not applicable in the present document. 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-specific references, the l

28、atest 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 application of the prese

29、nt document but they assist the user with regard to a particular subject area. i.1 ETSI GS NFV-MAN 001: “Network Functions Virtualisation (NFV); Management and Orchestration“. i.2 ETSI GS NFV-INF 003: “Network Functions Virtualisation (NFV); Infrastructure; Compute Domain“. i.3 ETSI GS NFV-INF 004:

30、“Network Functions Virtualisation (NFV); Infrastructure; Hypervisor Domain“. i.4 ETSI GS NFV-INF 005: “Network Functions Virtualisation (NFV); Infrastructure; Network Domain“. i.5 ETSI GS MEC 003: “Mobile Edge Computing (MEC); Framework and Reference Architecture“. i.6 ETSI GS NFV-IFA 013: “Network

31、Functions Virtualisation (NFV); Management and Orchestration; Os-Ma-Nfvo reference point - Interface and Information Model Specification“. i.7 ETSI GS NFV-IFA 011: “Network Functions Virtualisation (NFV); Management and Orchestration; VNF Packaging Specification“. i.8 3GPP TR 32.842: “Telecommunicat

32、ion management; Study on network management of virtualised networks“. i.9 ETSI GS NFV-IFA 009: “Network Functions Virtualisation (NFV); Management and Orchestration; Report on Architectural Options“. i.10 ETSI GS MEC 010-2: “Mobile Edge Computing (MEC); Mobile Edge Management; Part 2: Application li

33、fecycle, rules and requirements management“. i.11 ETSI GS NFV-IFA 014: “Network Functions Virtualisation (NFV); Management and Orchestration; Network Service Templates Specification“. i.12 ETSI GS NFV-IFA 008: “Network Functions Virtualisation (NFV); Management and Orchestration; Ve-Vnfm reference p

34、oint - Interface and Information Model Specification“. ETSI ETSI GR MEC 017 V1.1.1 (2018-02) 7 i.13 ETSI GS MEC 010-1: “Mobile Edge Computing (MEC); Mobile Edge Management; Part 1: System, host and platform management“. i.14 ETSI GS NFV-SOL 002: “Network Functions Virtualisation (NFV); Protocols and

35、 Data Models; RESTful protocols specification for the Ve-Vnfm Reference Point“. i.15 IETF RFC 6241: “Network Configuration Protocol (NETCONF)“. i.16 IETF RFC 8040: “RESTCONF Protocol“. i.17 ETSI GS MEC 002: “Mobile Edge Computing (MEC); Technical Requirements“. i.18 ETSI GS NFV-IFA 006: “Network Fun

36、ctions Virtualisation (NFV); Management and Orchestration; Vi-Vnfm reference point - Interface and Information Model Specification“. i.19 ETSI GS NFV-IFA 007: “Network Functions Virtualisation (NFV); Management and Orchestration; Or-Vnfm reference point - Interface and Information Model Specificatio

37、n“. i.20 ETSI GS NFV-IFA 018: “Network Functions Virtualisation (NFV); Acceleration Technologies; Network Acceleration Interface Specification; Release 3“. i.21 OpenStack documentation, Service function chaining. NOTE: Available at: https:/docs.openstack.org/newton/networking-guide/config-sfc.html.

38、i.22 ETSI GS NFV-SOL 005: “Network Functions Virtualisation (NFV) Release 2; Protocols and Data Models; RESTful protocols specification for the Os-Ma-nfvo Reference Point“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions a

39、pply: ME app VNF: mobile edge application that appears like a VNF towards the ETSI NFV MANO components 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: DNS Domain Name System DOPFR Dynamic Optimization of Packet Flow Routing EM Element Manager ETSI Europ

40、ean Telecommunications Standards Institute GS Group Specification GTP GPRS Tunnelling Protocol HOT Heat Orchestration Template IP Internet Protocol LCM Life Cycle Management MANO Management and Orchestration ME Mobile Edge MEAO Mobile Edge Application Orchestrator MEC Mobile Edge Computing MEO Mobil

41、e Edge Orchestrator MEPM Mobile Edge Platform Manager MEPM-V Mobile Edge Platform Manager - NFV NFP Network Forwarding Path NFV Network Functions Virtualisation NFVI Network Functions Virtualisation Infrastructure NFVO Network Functions Virtualisation Orchestrator ETSI ETSI GR MEC 017 V1.1.1 (2018-0

42、2) 8 NS Network Service NSD Network Service Descriptor OASIS Organization for the Advancement of Structured Information Standards OSS Operations Support System PM Performance ManagementPNF Physical Network Function PNFD Physical Network Function Descriptor PoP Point of Presence QCI Quality Class Ind

43、icator SFC Service Function Chaining SPID Subscriber Profile ID TEID Tunnel Endpoint ID TOSCA Topology and Orchestration Specification for Cloud Applications UE User Equipment VIM Virtualised Infrastructure Manager VL Virtual Link VM Virtual MachineVNF Virtualised Network Function VNFC VNF Component

44、 VNFD VNF DescriptorVNFFG VNF Forwarding Graph VNFM Virtual Network Function Manager YAML YAML Aint Markup Language 4 Introduction Mobile network operators are expected to virtualise their networks using Network Functions Virtualisation (NFV), and want to use the introduced virtualisation infrastruc

45、ture to consolidate network elements (Virtualised Network Functions - VNFs), Mobile Edge Computing (MEC) components and Mobile Edge (ME) applications on top of that infrastructure. Sharing the introduced elements (infrastructure, but also management functions) to the maximum possible degree allows t

46、o make maximum use of the investments into virtualisation. The present document will analyse different scenarios of MEC deployments in NFV environments w.r.t. their architectural impact and the needed specification work. The present document will help to identify normative specification work to enab

47、le MEC deployments in NFV environments. It will also help operators that plan to deploy MEC and NFV feature at the same time, to make the right decision by providing detailed information around solution aspects. 5 Reference Architecture 5.1 Overview and assumptions This clause defines a reference ar

48、chitecture of how ETSI MEC can be deployed in a NFV environment. The basic assumptions are: 1) The ME platform is deployed as a VNF. For that purpose, the procedures defined by ETSI NFV are used. It is not expected that these procedures need to be modified for use with ETSI MEC. Clause 5.2 further e

49、laborates on this. 2) The ME applications appear like VNFs towards the ETSI NFV MANO components. This allows re-use of ETSI NFV MANO functionality. It is, however, expected that ETSI MEC might not use the full set of MANO functionality, and requires certain additional functionality. Such a specific ME application is denoted by the name “ME app VNF“ in the remainder of the present document. 3) The virtualisation infrastructure is deployed as a NFVI and its virtualised resources are managed by the VIM. For that purpose, the procedure