ETSI GS MEC 021 V2.1.1 (2020-01)

Multi-access Edge Computing (MEC); Application Mobility Service API

DGS/MEC-0021AppMobility

General Information

• Status: Published
• Publication Date: 20-Jan-2020
• Technical Committee: MEC - Multi-access Edge Computing
• Current Stage: 12 - Completion
• Due Date: 31-Jan-2020
• Completion Date: 21-Jan-2020

Standards Content (Sample)

ETSI GS MEC 021 V2.1.1 (2020-01)






GROUP SPECIFICATION
Multi-access Edge Computing (MEC);
Application Mobility Service API
Disclaimer
The present document has been produced and approved by the Multi-access 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 021 V2.1.1 (2020-01)



Reference
DGS/MEC-0021AppMobility
Keywords
application, MEC, mobility

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 prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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 2020.
All rights reserved.

DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI GS MEC 021 V2.1.1 (2020-01)
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 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Specification level requirements . 9
4.1 Introduction . 9
4.2 Functional requirements . 9
5 Description of the services (informative) . 10
5.1 Introduction . 10
5.2 End to end application mobility information flows . 10
5.3 Application mobility enablement . 11
5.4 Application relocation initiation . 12
5.4.1 Overview . 12
5.4.2 MEC assisted application mobility information flow . 13
5.4.2.1 S-MEP triggered application mobility using RNIS . 13
5.5 Application relocation verification and validation . 14
5.6 User context transfer . 14
5.6.1 Introduction. 14
5.6.2 Application self-controlled user context transfer . 14
5.6.3 Device application assisted user context transfer . 14
5.6.4 MEC assisted user context transfer . 15
5.7 Application traffic path update . 15
5.8 Application relocation completion . 15
6 Sequence diagrams . 15
6.1 Introduction . 15
6.2 Register to application mobility service . 16
6.3 Deregister to application mobility service . 16
6.4 Update application mobility service . 17
6.5 User context transfer completion . 17
6.6 Subscribe to notifications of application mobility service . 18
6.7 Unsubscribe to notifications of application mobility service . 18
6.8 Update subscription to application mobility service notifications . 19
7 Data Models . 19
7.1 Introduction . 19
7.2 Registration data types . 19
7.2.1 Introduction. 19
7.2.2 Type: RegistrationInfo . 19
7.2.3 Type: AdjacentAppInstanceInfo . 20
7.3 Subscription data types . 20
7.3.1 Introduction. 20
7.3.2 Type: MobilityProcedureSubscription . 20
7.3.3 Type: AdjacentAppInfoSubscription . 21
7.3.4 Type: SubscriptionLinkList . 21
7.4 Notification data types . 22
7.4.1 Introduction. 22
ETSI

---------------------- Page: 3 ----------------------
4 ETSI GS MEC 021 V2.1.1 (2020-01)
7.4.2 Type: MobilityProcedureNotification . 22
7.4.3 Type: AdjacentAppInfoNotification . 22
7.4.4 Type: ExpiryNotification . 23
7.4.5 Type: AppMobilityServiceLevel . 23
7.5 Referenced structured data types . 24
7.5.1 Introduction. 24
7.5.2 Type: CommunicationInterface . 24
8 API Definition . 24
8.1 Introduction . 24
8.2 Global definitions and resource structure . 24
8.3 Resource: application mobility services . 26
8.3.1 Description . 26
8.3.2 Resource definition . 26
8.3.3 Resource methods . 26
8.3.3.1 GET . 26
8.3.3.2 PUT . 27
8.3.3.3 PATCH . 27
8.3.3.4 POST . 27
8.3.3.5 DELETE . 28
8.4 Resource: individual application mobility service . 28
8.4.1 Description . 28
8.4.2 Resource definition . 29
8.4.3 Resource methods . 29
8.4.3.1 GET . 29
8.4.3.2 PUT . 30
8.4.3.3 PATCH . 31
8.4.3.4 POST . 31
8.4.3.5 DELETE . 31
8.5 Resource: deregister application mobility service task. 32
8.5.1 Description . 32
8.5.2 Resource definition . 32
8.5.3 Resource methods . 33
8.5.3.1 GET . 33
8.5.3.2 PUT . 33
8.5.3.3 PATCH . 33
8.5.3.4 POST . 33
8.5.3.5 DELETE . 34
8.6 Resource: subscriptions . 34
8.6.1 Description . 34
8.6.2 Resource definition . 34
8.6.3 Resource methods . 35
8.6.3.1 GET . 35
8.6.3.2 PUT . 35
8.6.3.3 PATCH . 35
8.6.3.4 POST . 36
8.6.3.5 DELETE . 37
8.7 Resource: individual subscription . 37
8.7.1 Description . 37
8.7.2 Resource definition . 37
8.7.3 Resource methods . 37
8.7.3.1 GET . 37
8.7.3.2 PUT . 38
8.7.3.3 PATCH . 40
8.7.3.4 POST . 40
8.7.3.5 DELETE . 40
8.8 Resource: adjacent application instances . 41
8.8.1 Description . 41
8.8.2 Resource definition . 41
8.8.3 Resource methods . 41
8.8.3.1 GET . 41
8.8.3.2 PUT . 43
ETSI

---------------------- Page: 4 ----------------------
5 ETSI GS MEC 021 V2.1.1 (2020-01)
8.8.3.3 PATCH . 43
8.8.3.4 POST . 43
8.8.3.5 DELETE . 43
Annex A (informative): Key concepts . 44
A.1 Application mobility. 44
A.1.1 Introduction . 44
A.1.2 Application availability in the target host . 45
A.1.3 User context transfer . 45
A.2 Mapping of permissions for RESTful API and resources . 45
History . 47

ETSI

---------------------- Page: 5 ----------------------
6 ETSI GS MEC 021 V2.1.1 (2020-01)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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) Multi-access 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: 6 ----------------------
7 ETSI GS MEC 021 V2.1.1 (2020-01)
1 Scope
The present document provides a specification for end-to-end MEC application mobility support in a multi-access edge
system. The present document describes information flows, required information and operations. The present document
also specifies the necessary API with the data model and data format.
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: "Multi-access Edge Computing (MEC); Terminology".
[2] ETSI GS MEC 002: "Multi-access Edge Computing (MEC); Phase 2: Use Cases and
Requirements".
[3] ETSI GS MEC 003: "Multi-access Edge Computing (MEC); Framework and Reference
Architecture".
[4] ETSI GS MEC 009: "Multi-access Edge Computing (MEC); General principles for MEC Service
APIs".
[5] ETSI GS MEC 011: "Multi-access Edge Computing (MEC); Edge Platform Application
Enablement".
[6] ETSI GS MEC 012: "Multi-access Edge Computing (MEC); Radio Network Information API".
[7] ETSI GS MEC 010-2: "Multi-access Edge Computing (MEC); MEC Management;
Part 2: Application lifecycle, rules and requirements management".
[8] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
NOTE: Available at https://tools.ietf.org/html/rfc6749.
[9] IETF RFC 6750: "The OAuth 2.0 Authorization Framework: Bearer Token Usage".
NOTE: Available at https://tools.ietf.org/html/rfc6750.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI GS MEC 021 V2.1.1 (2020-01)
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 016: "Multi-access Edge Computing (MEC); UE application interface".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI GS MEC 001 [1].
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GS MEC 001 [1], and the following apply:
AMS Application Mobility Service
API Application Programming Interface
GTP GPRS Tunnelling Protocol
HTTP HyperText Transfer Protocol
IETF Internet Engineering Task Force
IP Internet Protocol
JSON JavaScript Object Notation
RFC Request For Comments
RNIS Radio Network Information Service
S-App Source - Application instance
S-DP Source - Data Plane
S-MEP Source - MEC Platforms
S-MEPM Source - MEC Platform Manager
T-App Target - Application instance
T-DP Target - Data Plane
T-MEP Target - MEC Platforms
T-MEPM Target - MEC Platform Manager
TEID Tunnel End point IDentifier
URI Uniform Resource Indicator
VIM Virtualization Infrastructure Manager
ETSI

---------------------- Page: 8 ----------------------
9 ETSI GS MEC 021 V2.1.1 (2020-01)
4 Specification level requirements
4.1 Introduction
Application mobility is a unique feature of MEC system, which supports relocation of user context and/or application
instance from one MEC host to another, or between a MEC host and a Cloud, especially when the MEC host is attached
to mobile operator's networks. As a mobile device connected to a mobile network moves around within the network, it
can result in the device connecting to the network entity associated to a different MEC host from the serving host.
Consequently, there is necessity of relocating the application instance and/or user context associated to the device to a
new MEC host to continue offering the best performance of service.
ETSI GS MEC 002 [2] describes some use cases related to application mobility or smart relocation, and associated
requirements for MEC system to relocate the application instance and/or context to the "right" MEC host for optimizing
the performance.
Application mobility may involve multiple MEC functional entities to relocate application instances and transfer user
and application specific information within or between the MEC systems. Relocation decisions may be based on device
mo
...