ETSI GS MEC 016 V1.1.1 (2017-09)

Mobile Edge Computing (MEC); UE application interface

DGS/MEC-0016UEAppInterface

General Information

• Status: Published
• Publication Date: 04-Sep-2017
• Technical Committee: MEC - Multi-access Edge Computing
• Current Stage: 12 - Completion
• Due Date: 03-Sep-2017
• Completion Date: 05-Sep-2017

Standards Content (Sample)

ETSI GS MEC 016 V1.1.1 (2017-09)






GROUP SPECIFICATION
Mobile Edge Computing (MEC);
UE application interface
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.

---------------------- Page: 1 ----------------------
2 ETSI GS MEC 016 V1.1.1 (2017-09)



Reference
DGS/MEC-0016UEappInterface
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 trademarks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are trademarks 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 trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI GS MEC 016 V1.1.1 (2017-09)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Overview . 7
5 Description of the service (informative). 8
5.1 Sequence diagrams . 8
5.1.1 Introduction. 8
5.1.2 User application look-up . 8
5.1.3 Application context create . 8
5.1.4 Application context delete . 9
5.1.5 Application context update . 9
5.1.6 Receiving notification events . 10
6 Data model . 10
6.1 Introduction . 10
6.2 Resource data types . 11
6.2.1 Introduction. 11
6.2.2 Type: ApplicationList . 11
6.2.3 Type: AppContext . 12
6.3 Subscription data types . 12
6.4 Notification data types . 13
6.4.1 Introduction. 13
6.4.2 Type: NotificationEvent . 13
6.5 Referenced structured data types . 13
7 API definition . 13
7.1 Introduction . 13
7.2 Global definitions and resource structure . 13
7.3 Resource: meAppList . 14
7.3.1 Description . 14
7.3.2 Resource definition . 14
7.3.3 Resource Methods . 14
7.3.3.1 GET . 14
7.3.3.2 PUT . 15
7.3.3.3 PATCH . 15
7.3.3.4 POST . 15
7.3.3.5 DELETE . 15
7.4 Resource: all ueAppContexts . 16
7.4.1 Description . 16
7.4.2 Resource definition . 16
7.4.3 Resource Methods . 16
7.4.3.1 GET . 16
7.4.3.2 PUT . 16
7.4.3.3 PATCH . 16
7.4.3.4 POST . 16
7.4.3.5 DELETE . 17
7.5 Resource: individual ueAppContext . 17
ETSI

---------------------- Page: 3 ----------------------
4 ETSI GS MEC 016 V1.1.1 (2017-09)
7.5.1 Description . 17
7.5.2 Resource definition . 17
7.5.3 Resource Methods . 17
7.5.3.1 GET . 17
7.5.3.2 PUT . 18
7.5.3.3 PATCH . 18
7.5.3.4 POST . 18
7.5.3.5 DELETE . 18
8 Authentication, authorization and access control . 19
Annex A (informative): Complementary material for API utilization . 20
History . 21

ETSI

---------------------- Page: 4 ----------------------
5 ETSI GS MEC 016 V1.1.1 (2017-09)
Intellectual Property Rights
Essential patents
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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership 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 those trademarks.
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

---------------------- Page: 5 ----------------------
6 ETSI GS MEC 016 V1.1.1 (2017-09)
1 Scope
The present document contains the specification for the lifecycle management of the user applications over the UE
application interface. This interface is over the Mx2 reference point between the UE application in the UE and the user
application lifecycle management proxy in the mobile edge system.
The present document covers the following lifecycle management operations: user application look-up, request for the
user application instantiation, and the request for the user application termination. In addition, a mechanism is specified
for the exchange of lifecycle management related information between the mobile edge system and the UE application.
The intended key audience of the present document are the application developers for the mobile edge system.
NOTE: User application mobility related lifecycle management operations are not covered by the present
document.
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 010-2: "Mobile Edge Computing (MEC); Mobile Edge Management;
Part 2: Application lifecycle, rules and requirements management".
[2] IETF RFC 2818: "HTTP Over TLS".
NOTE: Available at https://tools.ietf.org/html/rfc2818.
[3] IETF RFC 5246: "The Transport Layer Security (TLS) Protocol Version 1.2".
NOTE: Available at https://tools.ietf.org/html/rfc5246.
[4] ETSI GS MEC 009: "Mobile Edge Computing (MEC); General principles for Mobile Edge
Service APIs".
[5] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
NOTE: Available at https://tools.ietf.org/html/rfc6749.
[6] IETF RFC 6750: "The OAuth 2.0 Authorization Framework: Bearer Token Usage".
NOTE: Available at https://tools.ietf.org/html/rfc6750.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI GS MEC 016 V1.1.1 (2017-09)
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] ETSI GS MEC 001: "Mobile Edge Computing (MEC); Terminology".
[i.2] ETSI GS MEC 002: "Mobile Edge Computing (MEC); Technical Requirements".
[i.3] 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 [i.1] and the following
apply:
user application lifecycle management proxy: system level functional element that allows specific and authorized
requests from the UE application for the user application lifecycle management
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GS MEC 001 [i.1] apply.
4 Overview
The present document specifies the API for the UE application interface to support the corresponding requirements
defined for the Mobile Edge Computing in ETSI GS MEC 002 [i.2].
Clause 5 describes how the UE application interface can be used by the UE application and by the mobile edge system.
It describes the information flows for the procedures over the UE application interface.
The information that is exchanged over the UE application interface is described in clause 6, providing detailed
description of all information elements available on that interface.
Clause 7 describes the actual API of the UE application interface, providing detailed information how the information
elements map into the RESTful API design of the interface.
Clause 8 describes the authentication, authorization and access control for the UE application interface.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI GS MEC 016 V1.1.1 (2017-09)
5 Description of the service (informative)
5.1 Sequence diagrams
5.1.1 Introduction
The following clauses describe how the UE application interacts with the user application lifecycle management proxy
over the UE application interface. The sequence diagrams that are relevant for the UE application interface are
presented.
5.1.2 User application look-up
The user application look-up is the procedure for requesting the list of available user applications in the mobile edge
system to the requesting UE application. The user application look-up procedure is illustrated in figure 5.1.2-1.

Figure 5.1.2-1: User application look-up
1) The UE application submits the GET request to the user application lifecycle management proxy. The user
application lifecycle management proxy authorizes the request from UE application. The mobile edge system
retrieves the list of user applications available to the requesting UE application.
2) The user application lifecycle management proxy returns the 200 OK response to the UE application, with the
message body containing the data structure for the list of available user applications.
5.1.3 Application context create
The application context create is the procedure to request either to join with an available user application or to
instantiate a new user application. The application context create procedure is illustrated in figure 5.1.3-1.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI GS MEC 016 V1.1.1 (2017-09)

Figure 5.1.3-1: Application context create
1) The UE application submits the POST request to the user application lifecycle management proxy. The
message body contains the data structure for the application context to be created.
The user application lifecycle management proxy authorizes the request from the UE application. The request
is forwarded to the OSS. The OSS makes the decision on granting the cont
...