1、 ETSI GS MEC 011 V1.1.1 (2017-07) Mobile Edge Computing (MEC); Mobile Edge Platform Application Enablement 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 participa
2、ted in this ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS MEC 011 V1.1.1 (2017-07) 2 Reference DGS/MEC-0011Plat.App.Enablemen Keywords API, MEC ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42
3、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/standards-search The present document may be made available in electroni
4、c 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 contents between such versions and/or in print, the only prevailing docume
5、nt 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 i
6、s 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 Copyright Notification No part may be reproduced or utilized in any form
7、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 copyright and the foregoing restriction extend to reproduction in al
8、l media. ETSI 2017. 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. oneM2M logo is protected
9、for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI GS MEC 011 V1.1.1 (2017-07) 3 Contents Intellectual Property Rights 6g3Foreword . 6g3Modal verbs terminology 6g31 Scope 7g32 References 7g32.1 Normative references . 7g32.2 Info
10、rmative references 8g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 Overview 9g35 Description of the services (informative) . 9g35.1 Introduction 9g35.2 Sequence diagrams . 10g35.2.1 General 10g35.2.2 Mobile edge application start-up 10g35.2.3 Mobile edge applicati
11、on graceful termination/stop . 12g35.2.4 Service availability update and new service registration 12g35.2.5 Service availability query . 14g35.2.6 Service availability notification subscription 14g35.2.6.1 Introduction . 14g35.2.6.2 Subscribing to service availability event notifications 14g35.2.6.3
12、 Unsubscribing from service availability event notifications . 15g35.2.7 Traffic rule activation/deactivation/update . 15g35.2.8 DNS rule activation/deactivation 16g35.2.9 Transport information query . 16g35.2.10 Time of Day (TOD) 17g35.2.10.1 Introduction . 17g35.2.10.2 Get platform time 17g35.2.10
13、.3 Timing capabilities query flow . 18g36 Data model . 18g36.1 Introduction 18g36.2 Resource data types 18g36.2.1 Introduction. 18g36.2.2 Type: ServiceInfo . 18g36.2.3 Type: TransportInfo 19g36.2.4 Type: TrafficRule . 19g36.2.5 Type: DnsRule 20g36.2.6 Type: TimingCaps 20g36.2.7 Type: CurrentTime . 2
14、1g36.3 Subscription data types . 22g36.3.1 Introduction. 22g36.3.2 Type: SerAvailabilityNotificationSubscription 22g36.3.3 Type: AppTerminationNotificationSubscription 22g36.3.4 Type: Mp1SubscriptionLinkList . 22g36.4 Notification data types 23g36.4.1 Introduction. 23g36.4.2 Type: ServiceAvailabilit
15、yNotification 23g36.4.3 Type: AppTerminationNotification 23g36.5 Referenced structured data types 24g36.5.1 Introduction. 24g36.5.2 Type: CategoryRef 24g36.5.3 Type: EndPointInfo. 24g3ETSI ETSI GS MEC 011 V1.1.1 (2017-07) 4 6.5.4 Type: SecurityInfo 24g36.5.5 Type: LinkType 25g36.5.6 Type: TrafficFil
16、ter 25g36.5.7 Type: DestinationInterface 26g36.5.8 Type: TunnelInfo 26g36.6 Referenced simple data types and enumerations 27g36.6.1 Introduction. 27g36.6.2 Type: Simple data types 27g36.6.3 Enumeration: SerializerTypes . 27g36.6.4 Enumeration: TransportTypes 27g37 API definition . 28g37.1 Introducti
17、on 28g37.2 Global definitions and resource structure . 28g37.3 Resource: individual meService . 30g37.3.1 Description 30g37.3.2 Resource definition . 30g37.3.3 Resource methods . 31g37.3.3.1 GET . 31g37.3.3.2 PUT . 31g37.3.3.3 PATCH . 32g37.3.3.4 POST . 33g37.3.3.5 DELETE . 33g37.4 Resource: a list
18、of meServices 33g37.4.1 Description 33g37.4.2 Resource definition . 33g37.4.3 Resource methods . 33g37.4.3.1 GET . 33g37.4.3.2 PUT . 34g37.4.3.3 PATCH . 34g37.4.3.4 POST . 34g37.4.3.5 DELETE . 35g37.5 Resource: individual meMp1Subscription . 36g37.5.1 Description 36g37.5.2 Resource definition . 36g3
19、7.5.3 Resource methods . 36g37.5.3.1 GET . 36g37.5.3.2 PUT . 37g37.5.3.3 PATCH . 37g37.5.3.4 POST . 37g37.5.3.5 DELETE . 37g37.6 Resource: all meMp1Subscriptions 38g37.6.1 Description 38g37.6.2 Resource definition . 38g37.6.3 Resource methods . 38g37.6.3.1 GET . 38g37.6.3.2 PUT . 39g37.6.3.3 PATCH .
20、 39g37.6.3.4 POST . 39g37.6.3.5 DELETE . 40g37.7 Resource: meTimingCaps 40g37.7.1 Description 40g37.7.2 Resource definition . 40g37.7.3 Resource methods . 41g37.7.3.1 GET . 41g37.7.3.2 PUT . 41g37.7.3.3 PATCH . 42g37.7.3.4 POST . 42g37.7.3.5 DELETE . 42g37.8 Resource: meCurrentTime 42g37.8.1 Descrip
21、tion 42g37.8.2 Resource definition . 42g3ETSI ETSI GS MEC 011 V1.1.1 (2017-07) 5 7.8.3 Resource methods . 42g37.8.3.1 GET . 42g37.8.3.2 PUT . 43g37.8.3.3 PATCH . 43g37.8.3.4 POST . 43g37.8.3.5 DELETE . 43g37.9 Resource: list of transports . 43g37.9.1 Description 43g37.9.2 Resource definition . 43g37
22、.9.3 Resource methods . 44g37.9.3.1 GET . 44g37.9.3.2 PUT . 44g37.9.3.3 PATCH . 45g37.9.3.4 POST . 45g37.9.3.5 DELETE . 45g37.10 Resource: all meTrafficRule. 45g37.10.1 Description 45g37.10.2 Resource definition . 45g37.10.3 Resource methods . 45g37.10.3.1 GET . 45g37.10.3.2 PUT . 46g37.10.3.3 PATCH
23、 . 46g37.10.3.4 POST . 46g37.10.3.5 DELETE . 46g37.11 Resource: individual meTrafficRule 46g37.11.1 Description 46g37.11.2 Resource definition . 46g37.11.3 Resource methods . 47g37.11.3.1 GET . 47g37.11.3.2 PUT . 47g37.11.3.3 PATCH . 49g37.11.3.4 POST . 49g37.11.3.5 DELETE . 49g37.12 Resource: all m
24、eDNSRule 49g37.12.1 Description 49g37.12.2 Resource definition . 49g37.12.3 Resource methods . 49g37.12.3.1 GET . 49g37.12.3.2 PUT . 50g37.12.3.3 PATCH . 50g37.12.3.4 POST . 50g37.12.3.5 DELETE . 50g37.13 Resource: individual meDNSRule 50g37.13.1 Description 50g37.13.2 Resource definition . 50g37.13
25、.3 Resource methods . 51g37.13.3.1 GET . 51g37.13.3.2 PUT . 51g37.13.3.3 PATCH . 53g37.13.3.4 POST . 53g37.13.3.5 DELETE . 53g3Annex A (informative): Complementary material for API utilisation 54g3History 55g3ETSI ETSI GS MEC 011 V1.1.1 (2017-07) 6 Intellectual Property Rights IPRs essential or pote
26、ntially essential to the present document 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
27、, 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:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can b
28、e 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 to the present document. Foreword This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Mobile Edge
29、Computing (MEC). 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 Drafting Rules (Verbal forms for the expression of provisions). “must“
30、 and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI GS MEC 011 V1.1.1 (2017-07) 7 1 Scope The present document focuses on the Mp1 reference point between mobile edge applications and mobile edge platform, which allows these applications to interact wit
31、h the mobile edge system. Service related functionality includes registration, discovery, and event notifications. Other functionality includes application availability, traffic rules and DNS, and time of day. It describes the information flows, required information, and specifies the necessary oper
32、ations, data model and API definition. 2 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 ve
33、rsion of the referenced document (including 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
34、, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. 1 ETSI GS MEC 001: “Mobile Edge Computing (MEC) Terminology“. 2 ETSI GS MEC 002: “Mobile Edge Computing (MEC) Technical Requirements“. 3 ETSI GS MEC 003: “M
35、obile Edge Computing (MEC) Framework and reference architecture“. 4 ETSI GS MEC 010-2: “Mobile Edge Computing (MEC); Application lifecycle, rules and requirements management“. 5 ETSI GS MEC 009: “Mobile Edge Computing (MEC); General principles for Mobile Edge Service APIs“. 6 IETF RFC 2818: “HTTP Ov
36、er TLS“. NOTE: Available at https:/tools.ietf.org/html/rfc2818. 7 IETF RFC 5246: “The Transport Layer Security (TLS) Protocol Version 1.2“. NOTE: Available at https:/tools.ietf.org/html/rfc5246. 8 IETF RFC 3986: “Uniform Resource Identifier (URI): Generic Syntax“. NOTE: Available at https:/tools.iet
37、f.org/html/rfc3986. 9 IETF RFC 7159: “The JavaScript Object Notation (JSON) Data Interchange Format“. NOTE: Available at https:/tools.ietf.org/html/rfc7159. 10 Extensible Markup Language (XML) 1.1 (Second Edition), W3C Recommendation 16 August 2006, edited in place 29 September 2006. NOTE: Available
38、 at https:/www.w3.org/TR/xml11/. 11 IETF RFC 7230: “HTTP/1.1 Message Syntax and Routing“. NOTE: Available at https:/tools.ietf.org/html/rfc7230. ETSI ETSI GS MEC 011 V1.1.1 (2017-07) 8 12 IETF RFC 6455: “The WebSocket Protocol“. NOTE: Available at https:/tools.ietf.org/html/rfc6455. 13 IETF RFC 6749
39、: “The OAuth 2.0 Authorization Framework“. NOTE: Available at https:/tools.ietf.org/html/rfc6749. 14 IETF RFC 6750: “The OAuth 2.0 Authorization Framework: Bearer Token Usage“. NOTE: Available at https:/tools.ietf.org/html/rfc6750. 2.2 Informative references References are either specific (identifie
40、d 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. NOTE: While any hyperlinks included in this claus
41、e 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 present document but they assist the user with regard to a particular subject area. i.1 IETF RFC 5905: “Network Time Protocol Versi
42、on 4: Protocol and Algorithms Specification“. i.2 IEEE 1588 (Version 2): “IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems“. i.3 Protocol buffers, version 3. NOTE: Available at https:/ i.4 MQTT Version 3.1.1, OASIS Standard, 29 October 2014.
43、NOTE: Available at http:/docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html. i.5 GRPC. NOTE: Available at http:/www.grpc.io/. i.6 OpenAPI Specification. NOTE 1: Available at https:/ NOTE 2: OpenAPI Specification version 2.0 is recommended as it is the official release at the time of publica
44、tion. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI GS MEC 001 1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ETSI GS MEC 001 1 and the following apply: API Applicatio
45、n Programming Interface DSCP Differentiated Services Code Point FQDN Fully Qualified Domain Name GRE Generic Routing Encapsulation ETSI ETSI GS MEC 011 V1.1.1 (2017-07) 9 GTP GPRS Tunnelling Protocol HTTP HyperText Transfer Protocol IETF Internet Engineering Task Force JSON Javascript Object Notatio
46、n MAC Media Access Control MEPM Mobile Edge Platform Manager MQTT Message Queue Telemetry Transport NTP Network Time Protocol PTP Precision Time Protocol QCI Quality Class Indicator REST Representational State Transfer RFC Request For Comments RNI Radio Network Information RPC Remote Procedure Call
47、TC Traffic Class TLS Transport Layer Security TOD Time of Day URI Uniform Resource Indicator UTC Coordinated Universal Time XML eXtensible Markup Language4 Overview The present document specifies the Mobile Edge Platform Application Enablement API to support the requirements defined for Mobile Edge
48、Computing in ETSI GS MEC 002 2. Clause 5 introduces the Mp1 reference point between mobile edge applications and mobile edge platform. It provides the high level information flows and describes the necessary operations. The information that may be exchanged over the Application Enablement API is des
49、cribed in clause 6 which provides detailed description on all attributes that are used. Clause 7 describes the actual Application Enablement API providing detailed information on how the attributes are mapped into a RESTful API design. 5 Description of the services (informative) 5.1 Introduction The mobile edge platform, as defined in ETSI GS MEC 003 3, offers an environment where mobile edge applications may discover, adverti
