ETSI GS MEC 011 V1.1.1 (2017-07)

Mobile Edge Computing (MEC); Mobile Edge Platform Application Enablement

DGS/MEC-0011Plat.App.Enablemen

General Information

• Status: Published
• Publication Date: 02-Jul-2017
• Technical Committee: MEC - Multi-access Edge Computing
• Current Stage: 12 - Completion
• Due Date: 08-May-2017
• Completion Date: 03-Jul-2017

Standards Content (Sample)

GROUP SPECIFICATION
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 participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.

2 ETSI GS MEC 011 V1.1.1 (2017-07)

Reference
DGS/MEC-0011Plat.App.Enablemen
Keywords
API, MEC
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture 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 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
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 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 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 all media.

© ETSI 2017.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit 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 Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI GS MEC 011 V1.1.1 (2017-07)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Overview . 9
5 Description of the services (informative) . 9
5.1 Introduction . 9
5.2 Sequence diagrams . 10
5.2.1 General . 10
5.2.2 Mobile edge application start-up . 10
5.2.3 Mobile edge application graceful termination/stop . 12
5.2.4 Service availability update and new service registration . 12
5.2.5 Service availability query . 14
5.2.6 Service availability notification subscription . 14
5.2.6.1 Introduction . 14
5.2.6.2 Subscribing to service availability event notifications . 14
5.2.6.3 Unsubscribing from service availability event notifications . 15
5.2.7 Traffic rule activation/deactivation/update . 15
5.2.8 DNS rule activation/deactivation . 16
5.2.9 Transport information query . 16
5.2.10 Time of Day (TOD) . 17
5.2.10.1 Introduction . 17
5.2.10.2 Get platform time . 17
5.2.10.3 Timing capabilities query flow . 18
6 Data model . 18
6.1 Introduction . 18
6.2 Resource data types . 18
6.2.1 Introduction. 18
6.2.2 Type: ServiceInfo . 18
6.2.3 Type: TransportInfo . 19
6.2.4 Type: TrafficRule . 19
6.2.5 Type: DnsRule . 20
6.2.6 Type: TimingCaps . 20
6.2.7 Type: CurrentTime . 21
6.3 Subscription data types . 22
6.3.1 Introduction. 22
6.3.2 Type: SerAvailabilityNotificationSubscription . 22
6.3.3 Type: AppTerminationNotificationSubscription . 22
6.3.4 Type: Mp1SubscriptionLinkList . 22
6.4 Notification data types . 23
6.4.1 Introduction. 23
6.4.2 Type: ServiceAvailabilityNotification . 23
6.4.3 Type: AppTerminationNotification . 23
6.5 Referenced structured data types . 24
6.5.1 Introduction. 24
6.5.2 Type: CategoryRef . 24
6.5.3 Type: EndPointInfo. 24
ETSI
4 ETSI GS MEC 011 V1.1.1 (2017-07)
6.5.4 Type: SecurityInfo . 24
6.5.5 Type: LinkType . 25
6.5.6 Type: TrafficFilter . 25
6.5.7 Type: DestinationInterface. 26
6.5.8 Type: TunnelInfo . 26
6.6 Referenced simple data types and enumerations . 27
6.6.1 Introduction. 27
6.6.2 Type: Simple data types . 27
6.6.3 Enumeration: SerializerTypes . 27
6.6.4 Enumeration: TransportTypes . 27
7 API definition . 28
7.1 Introduction . 28
7.2 Global definitions and resource structure . 28
7.3 Resource: individual meService . 30
7.3.1 Description . 30
7.3.2 Resource definition . 30
7.3.3 Resource methods . 31
7.3.3.1 GET . 31
7.3.3.2 PUT . 31
7.3.3.3 PATCH . 32
7.3.3.4 POST . 33
7.3.3.5 DELETE . 33
7.4 Resource: a list of meServices . 33
7.4.1 Description . 33
7.4.2 Resource definition . 33
7.4.3 Resource methods . 33
7.4.3.1 GET . 33
7.4.3.2 PUT . 34
7.4.3.3 PATCH . 34
7.4.3.4 POST . 34
7.4.3.5 DELETE . 35
7.5 Resource: individual meMp1Subscription . 36
7.5.1 Description . 36
7.5.2 Resource definition . 36
7.5.3 Resource methods . 36
7.5.3.1 GET . 36
7.5.3.2 PUT . 37
7.5.3.3 PATCH . 37
7.5.3.4 POST . 37
7.5.3.5 DELETE . 37
7.6 Resource: all meMp1Subscriptions . 38
7.6.1 Description . 38
7.6.2 Resource definition . 38
7.6.3 Resource methods . 38
7.6.3.1 GET . 38
7.6.3.2 PUT . 39
7.6.3.3 PATCH . 39
7.6.3.4 POST . 39
7.6.3.5 DELETE . 40
7.7 Resource: meTimingCaps . 40
7.7.1 Description . 40
7.7.2 Resource definition . 40
7.7.3 Resource methods . 41
7.7.3.1 GET . 41
7.7.3.2 PUT . 41
7.7.3.3 PATCH . 42
7.7.3.4 POST . 42
7.7.3.5 DELETE . 42
7.8 Resource: meCurrentTime. 42
7.8.1 Description . 42
7.8.2 Resource definition . 42
ETSI
5 ETSI GS MEC 011 V1.1.1 (2017-07)
7.8.3 Resource methods . 42
7.8.3.1 GET . 42
7.8.3.2 PUT . 43
7.8.3.3 PATCH . 43
7.8.3.4 POST . 43
7.8.3.5 DELETE . 43
7.9 Resource: list of transports . 43
7.9.1 Description . 43
7.9.2 Resource definition . 43
7.9.3 Resource methods . 44
7.9.3.1 GET . 44
7.9.3.2 PUT . 44
7.9.3.3 PATCH . 45
7.9.3.4 POST . 45
7.9.3.5 DELETE . 45
7.10 Resource: all meTrafficRule. 45
7.10.1 Description . 45
7.10.2 Resource definition . 45
7.10.3 Resource methods . 45
7.10.3.1 GET . 45
7.10.3.2 PUT . 46
7.10.3.3 PATCH . 46
7.10.3.4 POST . 46
7.10.3.5 DELETE . 46
7.11 Resource: individual meTrafficRule . 46
7.11.1 Description . 46
7.11.2 Resource definition . 46
7.11.3 Resource methods . 47
7.11.3.1 GET . 47
7.11.3.2 PUT . 47
7.11.3.3 PATCH . 49
7.11.3.4 POST . 49
7.11.3.5 DELETE . 49
7.12 Resource: all meDNSRule . 49
7.12.1 Description . 49
7.12.2 Resource definition . 49
7.12.3 Resource methods . 49
7.12.3.1 GET . 49
7.12.3.2 PUT . 50
7.12.3.3 PATCH . 50
7.12.3.4 POST . 50
7.12.3.5 DELETE . 50
7.13 Resource: individual meDNSRule. 50
7.13.1 Description . 50
7.13.2 Resource definition . 50
7.13.3 Resource methods . 51
7.13.3.1 GET . 51
7.13.3.2 PUT . 51
7.13.3.3 PATCH . 53
7.13.3.4 POST . 53
7.13.3.5 DELETE . 53
Annex A (informative): Complementary material for API utilisation . 54
History . 55

ETSI
6 ETSI GS MEC 011 V1.1.1 (2017-07)
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 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 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 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
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" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI
7 ETSI GS MEC 011 V1.1.1 (2017-07)
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 with 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 operations,
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 version 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, 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: "Mobile 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 Over 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.ietf.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 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
8 ETSI GS MEC 011 V1.1.1 (2017-07)
[12] IETF RFC 6455: "The WebSocket Protocol".
NOTE: Available at https://tools.ietf.org/html/rfc6455.
[13] IETF RFC 6749: "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 (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.
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 present document but they assist the
user with regard to a particular subject area.
[i.1] IETF RFC 5905: "Network Time Protocol Version 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://developers.google.com/protocol-buffers/docs/proto3.
[i.4] MQTT Version 3.1.1, OASIS Standard, 29 October 2014.
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://github.com/OAI/OpenAPI-Specification.
NOTE 2: OpenAPI Specification version 2.0 is recommended as it is the official release at the time of publication.
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 Application Programming Interface
DSCP Differentiated Services Code Point
FQDN Fully Qualified Domain Name
GRE Generic Routing Encapsulation
ETSI
9 ETSI GS MEC 011 V1.1.1 (2017-07)
GTP GPRS Tunnelling Protocol
HTTP HyperText Transfer Protocol
IETF Internet Engineering Task Force
JSON Javascript Object Notation
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
TC Traffic Class
TLS Transport Layer Security
TOD Time of Day
URI Uniform Resource Indicator
UTC Coordinated Universal Time
XML eXtensible Markup Language
4 Overview
The present document specifies the Mobile Edge Platform Application Enablement API to support the requirements
defined for Mobile Edge 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 described 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, advertise, consume and offer mobile edge services. Upon receipt of update, activation or deactivation of
traffic rules from the mobile edge platform manager, applications or services, the mobile edge platform instructs the
data plane accordingly. The mobile edge platform also receives DNS records from the mobile edge platform manager
and uses them to configure a DNS proxy/server.
Via Mp1 reference point between the mobile edge platform and the mobile edge applications, as defined in ETSI
GS MEC 003 [3], the basic functions are enabled, such as:
• mobile edge service assistance:
- authentication and authorization of producing and consuming mobile edge services;
- a means for service producing mobile edge applications to register towards the mobile edge platform the
mobile edge services they provide, and to update the mobile edge platform about changes of the mobile
edge service availability;
- a means to notify the changes of the mobile edge service availability to the relevant mobile edge
application;
ETSI
10 ETSI GS MEC 011 V1.1.1 (2017-07)
- discovery of available mobile edge services;
• mobile edge application assistance:
- mobile edge application start-up procedure;
- mobile edge application graceful termination/stop;
• traffic routing:
- traffic rules update, activation and deactivation;
• DNS rules:
- DNS rules activation and deactivation;
• timing:
- providing access to time of day information;
• transport information:
- providing information about available transports.
5.2 Sequence diagrams
5.2.1 General
Clauses 5.2.2 to 5.2.10 describe how mobile edge applications may be supported by the mobile edge platform via Mp1
reference point. The related sequence diagrams are presented.
5.2.2 Mobile edge application start-up
Figure 5.2.2-1 shows a scenario where after a mobile edge application is instantiated the mobile edge platform
configures the mobile edge application and registers it internally. The related information about this mobile edge
application instance is then stored in the mobile edge platform, including the required and the optional services, the
services to be offered by this application instance and the associated transport dependency, the traffic rules and DNS
rules associated with this application instance, etc. Additional authorization and authentication of the mobile edge
rd
application instance may take place based on operator's policies and/or 3 party service providers' requirements. For
rd
party service provider may need to be sure that the app is running on a legitimate/permitted host in a
example, the 3
correct physical territory (e.g. for video content copyright issues).
NOTE 1: This procedure applies to the mobile edge application that either producing mobile edge services, or
consuming mobile edge services, or both.
ETSI
11 ETSI GS MEC 011 V1.1.1 (2017-07)

Figure 5.2.2-1: Flow of Mobile Edge application start up
Mobile edge application start up procedure, following the mobile edge application instantiation procedure (as defined in
ETSI GS MEC 010-2 [4]), consists of the following steps:
1) After instantiation, the mobile edge application instance informs the mobile edge platform that it is
up-running. This step is not to be further specified in the present document.
NOTE 2: It is out of scope how an APP instance discovers a ME platform. In practise, this may be statically
configured or dynamically discovered via e.g. DNS.
2) When required, the mobile edge platform provide necessary information to authorize and authenticate this
rd
party service providers' requirements. This step is
application instance based on operator's policies and/or 3
not to be further specified in the present document.
NOTE 3: As an example, when additional authorization and authentication of the ME application is required by the
rd
3 party service provider, the needed information may be provided via Mp1 from the ME platform to the
ME application.
3) It is assumed that the mobile edge system pre-configures (not through Mp1) the mobile edge application
instance with necessary parameters, for example:
- the information needed to access the required services;
- the availability of the optional services;
- the information needed to access the available optional services.
The additional procedures via Mp1 that are related to this step include, when required, "Traffic rule
activation/deactivation/update" as defined in clause 5.2.7, and "DNS rule activation/deactivation" as defined in
clause 5.2.8. And the mobile edge application instance may update the mobile edge platform with the
information about the available produced mobile edge services as defined in clause 5.2.4.
4) Mobile edge platform then registers this application instance internally with related information including the
required and optional services, the services to be offered by this application instance and the associated
transport dependency, the traffic rules and DNS rules associated with this application instance, etc. This step is
not to be further specified in the present document.
ETSI
12 ETSI GS MEC 011 V1.1.1 (2017-07)
5.2.3 Mobile edge application graceful termination/stop
Figure 5.2.3-1 shows a flow for mobile edge application graceful termination/stop (as defined in ETSI
GS MEC 010-2 [4]). After the mobile edge platform receives a request to terminate or stop a mobile edge application
instance the mobile edge platform notifies the mobile edge application instance that it will be terminated or stopped
soon if graceful termination/stop is required. The mobile edge platform may also indicate to the mobile edge application
instance the length of a time interval during which the application may perform application-specific termination/stop.
When the timer expires, the mobile edge platform continues the termination flow of the mobile edge application
instance or stop application instance flow by, e.g. deactivating the traffic rules and DNS rules, removing the application
instance from the list of instances to be notified about service availability, removing the services provided by the
application instance from the service registry, sending service availability notification to the mobile edge applications
that consumes the services produced by the terminating mobile edge application instance, etc.

Figure 5.2.3-1: Flow of Mobile Edge application graceful termination/stop
5.2.4 Service availability update and new service registration
When a mobile edge service is registered by the service producing mobile edge application, the authorized relevant
applications (e.g. the applications
...