1、 ETSI GS MEC 003 V1.1.1 (2016-03) Mobile Edge Computing (MEC); Framework and Reference Architecture 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 who participated in
2、this ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS MEC 003 V1.1.1 (2016-03) 2 Reference DGS/MEC-003Arch Keywords architecture, MEC ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4
3、 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 versions an
4、d/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 is the pri
5、nt 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 available a
6、t 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 by any mea
7、ns, 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 media. Euro
8、pean 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 ETSI registered for the benefit of its Members and of the 3GPP Organizational Partn
9、ers. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI GS MEC 003 V1.1.1 (2016-03) 3 Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 De
10、finitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Overview 7g35 Mobile Edge Computing framework 8g36 Reference architecture 9g37 Functional elements and reference points 10g37.1 Functional elements 10g37.1.1 Mobile edge host . 10g37.1.2 Mobile edge platform 10g37.1.3 Mobil
11、e edge application 10g37.1.4 Mobile edge system level management 11g37.1.4.1 Mobile edge orchestrator . 11g37.1.4.2 Operations Support System (OSS) 11g37.1.4.3 User application lifecycle management proxy 11g37.1.5 Mobile edge host level management . 11g37.1.5.1 Mobile edge platform manager . 11g37.1
12、.5.2 Virtualisation infrastructure manager 12g37.1.6 User equipment application 12g37.1.7 Customer facing service portal . 12g37.2 Reference points . 12g37.2.1 Reference points related to the mobile edge platform. 12g37.2.2 Reference points related to the mobile edge management 12g37.2.3 Reference p
13、oints related to external entities . 13g38 Mobile edge services 13g38.1 General . 13g38.2 Radio Network Information . 13g38.3 Location 14g38.4 Bandwidth Manager . 14g3Annex A (informative): Key concepts . 15g3A.1 Mobile edge host selection . 15g3A.2 DNS support . 15g3A.3 Application traffic filterin
14、g and routing . 16g3A.4 Support of application and UE mobility . 16g3A.4.1 Background: UE mobility 16g3A.4.2 Mobile edge application scenarios for UE mobility . 16g3A.4.2.1 Mobile edge applications not sensitive to UE mobility 16g3A.4.2.2 Mobile edge applications sensitive to UE mobility 16g3A.4.2.2
15、.1 Maintaining connectivity between UE and mobile edge application instance 16g3A.4.2.2.2 Application state relocation . 16g3A.4.2.2.3 Application instance relocation within the mobile edge system . 17g3ETSI ETSI GS MEC 003 V1.1.1 (2016-03) 4 A.4.2.2.4 Application instance relocation between the mob
16、ile edge system and an external cloud environment 17g3A.5 Integrating MEC and NFV in the same network deployment 17g3History 18g3ETSI ETSI GS MEC 003 V1.1.1 (2016-03) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The in
17、formation 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 ETSI standards“, which is available from t
18、he 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 IPRs not referenced in ETSI SR 000 314 (or
19、the updates on the ETSI Web server) which are, 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) Mobile Edge Computing (MEC). Modal verbs terminology In the present document “shall“, “shall
20、 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 Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct
21、citation. ETSI ETSI GS MEC 003 V1.1.1 (2016-03) 6 1 Scope The present document provides a framework and reference architecture for Mobile Edge Computing that describes a mobile edge system that enables mobile edge applications to run efficiently and seamlessly in a mobile network. The present docume
22、nt also describes the functional elements and the reference points between them, and a number of mobile edge services that comprise the solution. It finally presents a number of key concepts related to the mobile edge architecture. 2 References 2.1 Normative references References are either specific
23、 (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. Referenced documents which are not fou
24、nd to be publicly available in the expected location might be found at http:/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 a
25、pplication of the present document. 1 ETSI GS MEC 002: “Mobile Edge Computing (MEC); Technical Requirements“. 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
26、 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 the time of publication, ETSI cannot guarantee their long term validity. The following referenced document
27、s 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 MEC 001: “Mobile-Edge Computing (MEC); Terminology“. i.2 ETSI GS NFV 002: “Network Functions Virtualisation (NFV); Architectural Framework“. i.3 “OpenStack+
28、for Cloudlet Deployment“. NOTE: Available at http:/reports-archive.adm.cs.cmu.edu/anon/2015/CMU-CS-15-123.pdf. i.4 “Adaptive VM Handoff Across Cloudlets“. NOTE: Available at http:/reports-archive.adm.cs.cmu.edu/anon/2015/CMU-CS-15-113.pdf. i.5 ETSI GS MEC 017: “Mobile-Edge Computing (MEC); Deploymen
29、t of Mobile Edge Computing in an NFV environment“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI GS MEC 001 i.1 apply. ETSI ETSI GS MEC 003 V1.1.1 (2016-03) 7 3.2 Abbreviations For the purposes of the present documen
30、t, the abbreviations given in ETSI GS MEC 001 i.1 and the following apply: CFS Customer Facing Service NFVI-PoP Network Functions Virtualisation Infrastructure Point of Presence OSS Operations Support System 4 Overview The present document presents a framework and a reference architecture to support
31、 the requirements defined for Mobile Edge Computing in ETSI GS MEC 002 1. The framework described in clause 5 shows the structure of the Mobile Edge Computing environment. The reference architecture described in clause 6 shows the functional elements that compose the mobile edge system, including th
32、e mobile edge platform and the mobile edge management, as well as the reference points between them. The functional elements and reference points listed in clause 7 describe the high-level functionality of the different functional elements and reference points. Clause 8 describes the high-level func
33、tionality of a number of mobile edge services, comprising the solution for Mobile Edge Computing. Annex A describes at a high-level a number of key concepts that underlie the principles used to develop the framework and reference architecture described in the present document. ETSI ETSI GS MEC 003 V
34、1.1.1 (2016-03) 8 5 Mobile Edge Computing framework Mobile Edge Computing enables the implementation of mobile edge applications as software-only entities that run on top of a virtualisation infrastructure, which is located in or close to the network edge. The Mobile Edge Computing framework shows t
35、he general entities involved. These can be grouped into system level, host level and network level entities. Figure 5-1: Mobile Edge Computing framework Figure 5-1 illustrates the framework for Mobile Edge Computing consisting of the following entities: mobile edge host, including the following: - m
36、obile edge platform; - mobile edge applications; - virtualisation infrastructure; mobile edge system level management; mobile edge host level management; external related entities, i.e. network level entities. Mobile edge hostMobile edge platformMobile edge app3rdpartyMobile edge host level manageme
37、ntMobile edge applicationsMobile edge appMobile edge appVirtualisation infrastructure (e.g. NFVI)UE3GPPnetworkExternalnetworkLocal networkMobile edge system level managementMobile edge appMobile edgesystemlevelMobileedgehostlevelNetworksETSI ETSI GS MEC 003 V1.1.1 (2016-03) 9 6 Reference architectur
38、e The reference architecture shows the functional elements that comprise the mobile edge system and the reference points between them. Figure 6-1 depicts the mobile edge system reference architecture. There are three groups of reference points defined between the system entities: reference points re
39、garding the mobile edge platform functionality (Mp); management reference points (Mm); and reference points connecting to external entities (Mx). Figure 6-1: Mobile edge system reference architecture The mobile edge system consists of the mobile edge hosts and the mobile edge management necessary to
40、 run mobile edge applications within an operator network or a subset of an operator network. The mobile edge host is an entity that contains a mobile edge platform and a virtualisation infrastructure which provides compute, storage, and network resources, for the purpose of running mobile edge appli
41、cations. The mobile edge host is further described in clause 7.1.1. The mobile edge platform is the collection of essential functionality required to run mobile edge applications on a particular virtualisation infrastructure and enable them to provide and consume mobile edge services. The mobile edg
42、e platform can also provide services. The mobile edge platform is further described in clause 7.1.2. Mobile edge applications are instantiated on the virtualisation infrastructure of the mobile edge host based on configuration or requests validated by the mobile edge management. Mobile edge applicat
43、ions are further described in clause 7.1.3. The mobile edge management comprises the mobile edge system level management and the mobile edge host level management. Mobile edge hostVirtualisation infrastructureData planeOperations Support SystemUE appVirtualisation infrastructure managerUser app LCM
44、proxyOther mobile edgeplatformMobile edge platformMobile edge platform managerMobile edge orchestratorMm3Mm1Mm4Mx2Mm8Mm9Mp2Mp1Mm7Mm6ME appMEappMm2Mm5Traffic rulescontrolME serviceService registryDNS handlingME platform element mgmtCFS portalMx1Other mobile edge hostMobile edgesystemlevelMobile edgeh
45、ostlevelME app rules receiving traffic rules from the mobile edge platform manager, applications, or services, and instructing the data plane accordingly. When supported, this includes the translation of tokens representing UEs in the traffic rules into specific IP addresses; receiving DNS records f
46、rom the mobile edge platform manager and configuring a DNS proxy/server accordingly; hosting mobile edge services, possibly including services that are described in clause 8; providing access to persistent storage and time of day information. 7.1.3 Mobile edge application Mobile edge applications ar
47、e running as virtual machines (VM) on top of the virtualisation infrastructure provided by the mobile edge host, and can interact with the mobile edge platform to consume and provide mobile edge services (described in clause 8). In certain cases, mobile edge applications can also interact with the m
48、obile edge platform to perform certain support procedures related to the lifecycle of the application, such as indicating availability, preparing relocation of user state, etc. Mobile edge applications can have a certain number of rules and requirements associated to them, such as required resources
49、, maximum latency, required or useful services, etc. These requirements are validated by the mobile edge system level management, and can be assigned to default values if missing. 7.1.4 Mobile edge system level management 7.1.4.1 Mobile edge orchestrator The mobile edge orchestrator is the core functionality in mobile edge system level management. The mobile edge orchestrator is responsible for the following functions: maintaining an overall view of the mobile edge system based on deployed mobile edge hosts, available resources, av
