ETSI GS MEC 002-2016 Mobile Edge Computing (MEC) Technical Requirements (V1 1 1)《移动边缘计算(MEC) 技术要求(V1 1 1)》.pdf

《ETSI GS MEC 002-2016 Mobile Edge Computing (MEC) Technical Requirements (V1 1 1)《移动边缘计算(MEC) 技术要求(V1 1 1)》.pdf》由会员分享，可在线阅读，更多相关《ETSI GS MEC 002-2016 Mobile Edge Computing (MEC) Technical Requirements (V1 1 1)《移动边缘计算(MEC) 技术要求(V1 1 1)》.pdf（40页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI GS MEC 002 V1.1.1 (2016-03) Mobile Edge Computing (MEC); Technical Requirements 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 this ISG. It d

2、oes not necessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS MEC 002 V1.1.1 (2016-03) 2 Reference DGS/MEC-002TechReq Keywords MEC, requirements ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 1

3、6 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 and/or in pri

4、nt. 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 print of the P

5、ortable 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 at https:/po

6、rtal.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 means, electro

7、nic 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. European Teleco

8、mmunications 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 Partners. GSM an

9、d the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI GS MEC 002 V1.1.1 (2016-03) 3 Contents Intellectual Property Rights 6g3Foreword . 6g3Modal verbs terminology 6g31 Scope 7g32 References 7g32.1 Normative references . 7g32.2 Informative references 7g33 Definitions a

10、nd abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 Generic principles 9g34.1 Introduction 9g34.2 NFV alignment . 9g34.3 Mobility support . 9g34.4 Deployment independence . 9g34.5 Simple and controllable APIs . 10g34.6 Smart application location 10g34.7 Representation of features 10g35

11、 Generic requirements . 11g35.1 Requirements on the framework 11g35.2 Application lifecycle 11g35.3 Applications environment 11g35.4 Support of mobility 12g36 Services requirements. 12g36.1 General . 12g36.2 Platform essential functionality 12g36.2.1 Mobile edge services 12g36.2.2 Connectivity 13g36

12、.2.3 Storage 13g36.2.4 Traffic routing . 13g36.2.5 DNS support . 14g36.2.6 Timing 14g36.3 Features 15g36.3.1 Feature UserApps 15g36.3.2 Feature SmartRelocation . 15g36.3.3 Feature RadioNetworkInformation . 16g36.3.4 Feature LocationService . 16g36.3.5 Feature BandwidthManager 17g36.3.6 Feature UEIde

13、ntity 17g37 Operation and management requirements 17g38 Security, regulation, charging requirements . 17g3Annex A (informative): Use cases . 18g3A.1 Use case categorization 18g3A.2 Mobile video delivery optimization using throughput guidance for TCP 19g3A.2.1 Description . 19g3A.2.2 Use of Mobile Ed

14、ge Computing . 19g3A.2.3 Related requirements 19g3A.3 Local content caching at the mobile edge 20g3A.3.1 Description . 20g3A.3.2 Use of Mobile Edge Computing . 20g3ETSI ETSI GS MEC 002 V1.1.1 (2016-03) 4 A.3.3 Related requirements 20g3A.4 Security, safety, data analytics . 20g3A.4.1 Description . 20

15、g3A.4.2 Use of Mobile Edge Computing . 21g3A.4.3 Related requirements 21g3A.5 Augmented reality, assisted reality, virtual reality, cognitive assistance . 21g3A.5.1 Description . 21g3A.5.2 Use of Mobile Edge Computing . 22g3A.5.3 Related requirements 23g3A.6 Gaming and low latency cloud applications

16、 . 23g3A.6.1 Description . 23g3A.6.2 Use of Mobile Edge Computing . 24g3A.6.3 Related requirements 24g3A.7 Active device location tracking 25g3A.7.1 Description . 25g3A.7.2 Use of Mobile Edge Computing . 25g3A.7.3 Related requirements 25g3A.8 Application portability . 25g3A.8.1 Description . 25g3A.8

17、.2 Use of Mobile Edge Computing . 25g3A.8.3 Related requirements 25g3A.9 SLA management . 26g3A.9.1 Description . 26g3A.9.2 Related requirements 26g3A.10 MEC edge video orchestration . 26g3A.10.1 Description . 26g3A.10.2 Use of Mobile Edge Computing . 26g3A.10.3 Related requirements 26g3A.11 Mobile

18、backhaul optimization 27g3A.11.1 Description . 27g3A.11.2 Use of Mobile Edge Computing . 27g3A.11.3 Related requirements 27g3A.12 Direct interaction with Mobile edge application 27g3A.12.1 Description . 27g3A.12.2 Use of Mobile Edge Computing . 28g3A.12.3 Related requirements 28g3A.13 Traffic dedupl

19、ication 29g3A.13.1 Description . 29g3A.13.2 Use of Mobile Edge Computing . 29g3A.13.3 Related requirements 29g3A.14 Vehicle-to-infrastructure communication 29g3A.14.1 Description . 29g3A.14.2 Use of Mobile Edge Computing . 30g3A.14.3 Related requirements 30g3A.15 Location-based service recommendatio

20、n . 30g3A.15.1 Description . 30g3A.15.2 Use of Mobile Edge Computing . 31g3A.15.3 Related requirements 31g3A.16 Bandwidth allocation manager for applications . 31g3A.16.1 Description . 31g3A.16.2 Use of Mobile Edge Computing . 31g3A.16.3 Related requirements 31g3A.17 Mobile edge platform consuming i

21、nformation from operator trusted mobile edge application . 32g3ETSI ETSI GS MEC 002 V1.1.1 (2016-03) 5 A.17.1 Description . 32g3A.17.2 Use of Mobile Edge Computing . 33g3A.17.3 Related requirements 33g3A.18 Video caching, compression and analytics service chaining 33g3A.18.1 Description . 33g3A.18.2

22、 Use of Mobile Edge Computing . 33g3A.18.3 Related requirements 33g3A.19 Radio access bearer monitoring . 34g3A.19.1 Description . 34g3A.19.2 Use of Mobile Edge Computing . 34g3A.19.3 Related requirements 34g3A.20 Mobile edge host deployment in dense-network environment . 34g3A.20.1 Description . 34

23、g3A.20.2 Use of Mobile Edge Computing . 34g3A.20.3 Related requirements 35g3A.21 Radio network information generation in aggregation point . 35g3A.21.1 Description . 35g3A.21.2 Use of Mobile Edge Computing . 35g3A.21.3 Related requirements 35g3A.22 Unified enterprise communications 35g3A.22.1 Descri

24、ption . 35g3A.22.2 Use of Mobile Edge Computing . 36g3A.22.3 Related requirements 37g3A.23 Application computation off-loading . 37g3A.23.1 Description . 37g3A.23.2 Value proposition . 37g3A.23.3 Use of Mobile Edge Computing . 38g3A.23.4 Related requirements 38g3Annex B (informative): Operator trust

25、ed mobile edge applications . 39g3History 40g3ETSI ETSI GS MEC 002 V1.1.1 (2016-03) 6 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETS

26、I 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 the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ip

27、r.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 are, or may be, or may become, essential

28、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 not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “ca

29、nnot“ 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 MEC 002 V1.1.1 (2016-03) 7 1 Scope The present document spec

30、ifies the requirements for Mobile Edge Computing with the aim of promoting interoperability and deployments. It contains normative and informative parts. The present document also contains an annex describing example use cases and their technical benefits, for the purpose of deriving requirements. 2

31、 References 2.1 Normative 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 (includ

32、ing any amendments) applies. 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

33、 validity. The following 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, onl

34、y 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 the time of publication, ETSI cannot guarantee their long term validity. The following referenc

35、ed 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 MEC 001: “Mobile Edge Computing (MEC); Terminology“. i.2 Mobile-Edge Computing - Introductory Technical White Paper. Sept. 2014. NOTE: Available a

36、t https:/portal.etsi.org/Portals/0/TBpages/MEC/Docs/Mobile-edge_Computing_-_Introductory_Technical_White_Paper_V1%2018-09-14.pdf. i.3 Flinck H. et al. (September 2015): “Mobile Throughput Guidance Inband Signaling Protocol, Internet draft, Internet Engineering Task Force“. NOTE: Available at https:/

37、tools.ietf.org/html/draft-flinck-mobile-throughput-guidance-03 (Work in progress). i.4 ETSI GS NFV 002: “Network Functions Virtualisation (NFV); Architectural Framework“. i.5 Byte Caching in Wireless Networks. NOTE: Available at http:/ i.6 A Protocol-Independent Technique for Eliminating Redundant N

38、etwork Traffic. NOTE: Available at https:/djw.cs.washington.edu/papers/spring-sigcomm00.pdf. ETSI ETSI GS MEC 002 V1.1.1 (2016-03) 8 i.7 Sprecher N. et al.: “Requirements and reference architecture for Mobile Throughput Guidance Exposure, Internet draft, Internet Engineering Task Force“, September 2

39、015. NOTE: Available at https:/tools.ietf.org/html/draft-sprecher-mobile-tg-exposure-req-arch-02 (Work in progress). i.8 Small Cells Forum White Paper SCF081: “Enterprise unified communications services with small cells“. NOTE: Available at http:/www.scf.io/en/documents/081-Enterprise_unified_commun

40、ications_services_with_small_cells.php. i.9 IEEE 1588: “IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI GS ME

41、C 001 i.1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ETSI GS MEC 001 i.1 and the following apply: API Application Programming Interface BYO Bring Your Own DSRC Digital Short-Range Communications EAB Edge Accelerated Browser GNSS Global Navigation Sa

42、tellite System GPRS General Packet Radio Service GPS Global Positioning SystemGTP GPRS Tunnelling Protocol HTTP Hyper Text Transfer Protocol IM Instant Messaging LAN Local Area Network NTP Network Time Protocol PBX Private Branch Exchange PTP Precision Time Protocol QCI Quality Class Indicator QoE Q

43、uality of Experience RAT Radio Access Technology SLA Service Level Agreement SMS Short Message Service SPID Subscriber Profile ID TCP Transmission Control Protocol TEID Tunnel Endpoint ID VNF Virtualised Network Function ETSI ETSI GS MEC 002 V1.1.1 (2016-03) 9 4 Generic principles 4.1 Introduction T

44、he following principles are important to understand in the context of Mobile Edge Computing. 4.2 NFV alignment Mobile Edge Computing uses a virtualisation platform for running applications at the mobile network edge. Network Functions Virtualisation (NFV) provides a virtualisation platform to networ

45、k functions. The infrastructure that hosts their respective applications or network functions is quite similar. In order to allow operators to benefit as much as possible from their investment, it would be beneficial to reuse the infrastructure and infrastructure management of NFV to the largest ext

46、ent possible, by hosting both VNFs (Virtual Network Functions) and mobile edge applications on the same or similar infrastructure. Subject to gap analysis, this might require a number of enhancements (e.g. regarding the sharing of resources with NFV Management and Orchestration, etc.). 4.3 Mobility

47、support Mobility is an essential functionality of 3GPP networks. Most devices connected to a 3GPP network are moving around within the mobile network. Even fixed devices can “move“, especially when located at cell edge, but also when changing RATs, etc., or during exceptional events (e.g. power cut

48、from a base station, etc.). Some mobile edge applications are state-independent and do not need to keep state information related to the UEs they are serving. For example, an application in the category “network performance and QoE improvements“ will only improve the performance of the UE traffic wh

49、en the traffic goes through that mobile edge host. When the UE moves to a different location covered by another mobile edge host, it will be the application hosted on that mobile edge host that will take care of the UE after a brief transition period. Past interaction is not useful for the application. Other mobile edge applications, notably in the category “consumer-oriented services“, are specifically related to the user activity. Either the whole application is specific to t