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

Mobile Edge Computing (MEC); Mobile Edge Management; Part 2: Application lifecycle, rules and requirements management

DGS/MEC-0010-2AppLcRulesReqMgm

General Information

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

Standards Content (Sample)

GROUP SPECIFICATION
Mobile Edge Computing (MEC);
Mobile Edge Management;
Part 2: Application lifecycle, rules and requirements
management
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 010-2 V1.1.1 (2017-07)

Reference
DGS/MEC-0010-2AppLcRulesReqMgm
Keywords
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 010-2 V1.1.1 (2017-07)
Contents
Intellectual Property Rights . 7
Foreword . 7
Modal verbs terminology . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 8
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 9
4 Specification level requirements . 9
4.1 Requirements . 9
4.1.1 Requirements for reference point Mm1 . 9
4.1.1.1 General requirements . 9
4.1.1.2 Interface requirements . 10
4.1.1.2.1 Application package management interface requirements . 10
4.1.1.2.2 Application lifecycle management interface requirements . 10
4.1.2 Requirements for reference point Mm3 . 10
4.1.2.1 General requirements . 10
4.1.2.2 Interface requirements . 11
4.1.2.2.1 Application package management interface requirements . 11
4.1.2.2.2 Application lifecycle management interface requirements . 11
4.1.2.2.3 Application lifecycle change notification interface requirements . 11
4.1.3 Requirements for application package . 12
4.1.3.1 General requirements . 12
4.1.3.2 Application descriptor requirements . 13
5 Message flows to support application lifecycle management . 13
5.1 General . 13
5.2 Application package on-boarding . 13
5.2.1 General . 13
5.2.2 On-board application package . 14
5.2.3 Query application package . 14
5.2.4 Disable application package . 15
5.2.5 Enable application package. 15
5.2.6 Delete application package . 16
5.3 Application instantiation . 17
5.4 Application termination . 18
6 Information models and interfaces . 19
6.1 Applicable reference points . 19
6.2 Information models . 19
6.2.1 Application descriptor information model . 19
6.2.1.1 Introduction . 19
6.2.1.2 Type: Application descriptor . 19
6.2.1.2.1 Description . 19
6.2.1.2.2 Attributes . 19
6.2.1.3 Type: VirtualComputeDescription . 21
6.2.1.3.1 Description . 21
6.2.1.3.2 Attributes . 21
6.2.1.4 Type: SwImageDescriptor . 21
6.2.1.4.1 Description . 21
6.2.1.4.2 Attributes . 21
6.2.1.5 Type: VirtualStorageDescriptor . 21
6.2.1.5.1 Description . 21
ETSI
4 ETSI GS MEC 010-2 V1.1.1 (2017-07)
6.2.1.5.2 Attributes . 21
6.2.1.6 Type: AppExternalCpd . 21
6.2.1.6.1 Description . 21
6.2.1.6.2 Attributes . 22
6.2.1.7 Type: ServiceDescriptor . 22
6.2.1.7.1 Description . 22
6.2.1.7.2 Attributes . 22
6.2.1.8 Type: FeatureDependency . 22
6.2.1.8.1 Description . 22
6.2.1.8.2 Attributes . 22
6.2.1.9 Type: TrafficRuleDescriptor . 23
6.2.1.9.1 Description . 23
6.2.1.9.2 Attributes . 23
6.2.1.10 Type: TrafficFilter . 23
6.2.1.10.1 Description . 23
6.2.1.10.2 Attributes . 23
6.2.1.11 Type: InterfaceDescriptor . 24
6.2.1.11.1 Description . 24
6.2.1.11.2 Attributes . 24
6.2.1.12 Type: TunnelInfo . 24
6.2.1.12.1 Description . 24
6.2.1.12.2 Attributes . 24
6.2.1.13 Type: DnsRuleDescriptor . 25
6.2.1.13.1 Description . 25
6.2.1.13.2 Attributes . 25
6.2.1.14 Type: LatencyDescriptor . 25
6.2.1.14.1 Description . 25
6.2.1.14.2 Attributes . 25
6.2.1.15 Type: TerminateAppInstanceOpConfig . 25
6.2.1.15.1 Description . 25
6.2.1.15.2 Attributes . 25
6.2.1.16 Type: ChangeAppInstanceStateOpConfig . 26
6.2.1.16.1 Description . 26
6.2.1.16.2 Attributes . 26
6.2.1.17 Type: ServiceDependency . 26
6.2.1.17.1 Description . 26
6.2.1.17.2 Attributes . 26
6.2.1.18 Type: TransportDependency . 26
6.2.1.18.1 Description . 26
6.2.1.18.2 Attributes . 26
6.2.1.19 Type: TransportDescriptor . 27
6.2.1.19.1 Description . 27
6.2.1.19.2 Attributes . 27
6.3 Interfaces . 28
6.3.1 Application lifecycle management interface . 28
6.3.1.1 Description . 28
6.3.1.2 Create application instance identifier operation . 28
6.3.1.2.1 Description . 28
6.3.1.2.2 Input parameters . 29
6.3.1.2.3 Output parameters . 29
6.3.1.2.4 Operation results . 29
6.3.1.3 Application instantiation operation . 29
6.3.1.3.1 Definition. 29
6.3.1.3.2 Input parameters . 29
6.3.1.3.3 Output parameters . 30
6.3.1.3.4 Operation results . 30
6.3.1.4 Change application instance operational state operation . 30
6.3.1.4.1 Description . 30
6.3.1.4.2 Input parameters . 31
6.3.1.4.3 Output parameters . 32
6.3.1.4.4 Operation results . 32
6.3.1.5 Query application instance information operation . 33
ETSI
5 ETSI GS MEC 010-2 V1.1.1 (2017-07)
6.3.1.5.1 Description . 33
6.3.1.5.2 Input parameters . 33
6.3.1.5.3 Output parameters . 33
6.3.1.5.4 Operation results . 33
6.3.1.6 Query application lifecycle operation status . 34
6.3.1.6.1 Description . 34
6.3.1.6.2 Input parameters . 34
6.3.1.6.3 Output parameters . 34
6.3.1.6.4 Operation results . 34
6.3.1.7 Application instance terminate operation . 34
6.3.1.7.1 Description . 34
6.3.1.7.2 Input parameters . 35
6.3.1.7.3 Output parameters . 36
6.3.1.7.4 Operation results . 36
6.3.1.8 Delete application instance identifier operation . 36
6.3.1.8.1 Description . 36
6.3.1.8.2 Input parameters . 36
6.3.1.8.3 Output parameters . 36
6.3.1.8.4 Operation results . 36
6.3.2 Application lifecycle change notification interface . 37
6.3.2.1 Description . 37
6.3.2.2 Subscribe operation . 37
6.3.2.2.1 Description . 37
6.3.2.2.2 Input parameters . 37
6.3.2.2.3 Output parameters . 37
6.3.2.2.4 Operation results . 37
6.3.2.3 Notify operation . 38
6.3.2.3.1 Description . 38
6.3.3 Application package management interface . 38
6.3.3.1 Fetch on-boarded application package operation . 38
6.3.3.1.1 Definition. 38
6.3.3.1.2 Input parameters . 38
6.3.3.1.3 Output parameters . 39
6.3.3.1.4 Operation results . 39
6.3.3.2 Query application package operation . 39
6.3.3.2.1 Definition. 39
6.3.3.2.2 Input parameters . 39
6.3.3.2.3 Output parameters . 39
6.3.3.2.4 Operation results . 40
6.3.3.3 Subscribe operation . 40
6.3.3.3.1 Definition. 40
6.3.3.3.2 Input parameters . 40
6.3.3.3.3 Output parameters . 40
6.3.3.3.4 Operation results . 40
6.3.3.4 Notify Application Package operation . 40
6.3.3.4.1 Definition. 40
6.3.3.5 Onboarding operation. 41
6.3.3.5.1 Definition. 41
6.3.3.5.2 Input parameters . 41
6.3.3.5.3 Output parameters . 41
6.3.3.5.4 Operation results . 42
6.3.3.6 Enable operation . 42
6.3.3.6.1 Definition. 42
6.3.3.6.2 Input parameters . 42
6.3.3.6.3 Output parameters . 42
6.3.3.6.4 Operation results . 42
6.3.3.7 Disable operation . 42
6.3.3.7.1 Definition. 42
6.3.3.7.2 Input parameters . 43
6.3.3.7.3 Output parameters . 43
6.3.3.7.4 Operation results . 43
6.3.3.8 Query operation . 43
ETSI
6 ETSI GS MEC 010-2 V1.1.1 (2017-07)
6.3.3.8.1 Definition. 43
6.3.3.8.2 Input parameters . 43
6.3.3.8.3 Output parameters . 44
6.3.3.8.4 Operation results . 44
6.3.3.9 Delete operation . 44
6.3.3.9.1 Definition. 44
6.3.3.9.2 Input parameters . 44
6.3.3.9.3 Output parameters . 44
6.3.3.9.4 Operation results . 44
6.3.3.10 Abort application package deletion operation . 45
6.3.3.10.1 Description . 45
6.3.3.10.2 Input parameters . 45
6.3.3.10.3 Output parameters . 45
6.3.3.10.4 Operation results . 45
Annex A (normative): Application package state model . 46
A.1 Introduction . 46
A.2 State model . 46
Annex B (informative): Bibliography . 47
History . 48

ETSI
7 ETSI GS MEC 010-2 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).
The present document is part 2 of a multi-part deliverable covering Mobile Edge Management, as identified below:
Part 1: "System, host and platform management";
Part 2: "Application lifecycle, rules and requirements management".
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
8 ETSI GS MEC 010-2 V1.1.1 (2017-07)
1 Scope
The present document provides information flows for lifecycle management of applications running on a mobile edge
host, and describes interfaces over the reference points to support application lifecycle management. It also describes
application rules and requirements, application-related events and mobility handling. The present document specifies
the necessary data model, data format and operation format when applicable.
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 NFV-IFA 011 (V2.1.1): "Network Functions Virtualisation (NFV); Management and
Orchestration; VNF Packaging Specification".
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] ETSI GS NFV-IFA 007 (V2.1.1): "Network Functions Virtualisation (NFV); Management and
Orchestration; Or-Vnfm reference point - Interface and Information Model Specification".
[i.4] ETSI GS MEC 011: "Mobile Edge Computing (MEC); Mobile Edge Platform Application
Enablement".
[i.5] ETSI GS NFV 003 (V1.2.1): "Network Functions Virtualisation (NFV); Terminology for Main
Concepts in NFV".
[i.6] ETSI GS MEC 009: "Mobile Edge Computing (MEC); General principles for Mobile Edge
Service APIs".
ETSI
9 ETSI GS MEC 010-2 V1.1.1 (2017-07)
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:
application descriptor: descriptor provided by the application provider, and describes the application rules and
requirements of a mobile edge application
application package: bundle of files provided by application provider, on-boarded into mobile edge system and used
by the mobile edge system for application instantiation, including an application descriptor, a VM image or a URL link
to a VM image, a manifest file, and other optional files
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GS MEC 001 [i.1], ETSI NFV 003 [i.5] and
the following apply:
CPD Connection Point Descriptor
DNS Domain Name System
FQDN Fully Qualified Domain Name
FTP File Transfer Protocol
GRE Generic Routing Encapsulation
GTP GPRS Tunnelling Protocol
GTP-U GPRS Tunnelling Protocol for User plane
IP Internet Protocol
MAC Media Access Control
ME Mobile Edge
MEO Mobile Edge Orchestrator
MEPM Mobile Edge Platform Manager
QCI QoS Class Identifier
RNIS Radio Network Information Service
URL Uniform Resource Locator
4 Specification level requirements
4.1 Requirements
4.1.1 Requirements for reference point Mm1
4.1.1.1 General requirements
The Mm1 reference point between the Mobile Edge Orchestrator and the OSS is used for on-boarding application
packages, triggering the instantiation and the termination of mobile edge applications in the mobile edge system.
Table 4.1.1.1-1 specifies requirements related to application lifecycle management applicable to the Mm1 reference
point. Those requirements are derived from table 5.2-1 of ETSI GS NFV-IFA 007 [i.3].
Table 4.1.1.1-1: Mm1 reference point requirements
Numbering Functional requirement description
Mm1.001 The Mm1reference point shall support the application package management interface
produced by the Mobile Edge Orchestrator.
Mm1.002 The Mm1reference point shall support the application lifecycle management interface
produced by the Mobile Edge Orchestrator.

ETSI
10 ETSI GS MEC 010-2 V1.1.1 (2017-07)
4.1.1.2 Interface requirements
4.1.1.2.1 Application package management interface requirements
Table 4.1.1.2.1-1 specifies requirements applicable to the application package management interface produced by the
Mobile Edge Orchestrator on the Mm1 reference point. Those requirements are derived from clause 5.2 of ETSI
GS MEC 002 [i.2].
Table 4.1.1.2.1-1: Application package management interface requirements
Numbering Functional requirement description
Mm1.AppPkgm.001 The Application Package Management interface produced by the MEO on the Mm1
reference point shall support on-boarding an Application Package.
Mm1.AppPkgm.002 The Application Package Management interface produced by the MEO on the Mm1
reference point shall support querying Application Package information.
Mm1.AppPkgm.003 The Application Package Management interface produced by the MEO on the Mm1
reference point shall support deleting an Application Package.
The Application Package Management interface produced by the MEO on the Mm1
Mm1.AppPkgm.004
reference point shall support enabling an application package.
The Application Package Management interface produced by the MEO on the Mm1
Mm1.AppPkgm.005
reference point shall support disabling an application package.

4.1.1.2.2 Application lifecycle management interface requirements
Table 4.1.1.2.2-1 specifies requirements applicable to the application lifecycle management interface produced by the
Mobile Edge Orchestrator on the Mm1 reference point.
Table 4.1.1.2.2-1: Application lifecycle management interface requirements
Numbering Functional requirement description
Mm1.AppLcm.001 The Application Lifecycle Management interface produced by the MEO on the Mm1 reference
point shall support instantiating an Application instance.
Mm1.AppLcm.002 The Application Lifecycle Management interface produced by the MEO on the Mm1 reference
point shall support terminating an Application instance.
Mm1.AppLcm.003 The Application Lifecycle Management interface produced by the MEO on the Mm1 reference
point shall support requesting to change the state of an application instance (see note).
NOTE: Changing the state of an application instance refers to starting or stopping an application instance. These
operations are complementary to instantiating or terminating an application.

4.1.2 Requirements for reference point Mm3
4.1.2.1 General requirements
The Mm3 reference point between the Mobile Edge Orchestrator and the Mobile Edge Platform Manager is used for the
management of the application lifecycle, application rules and requirements and keeping track of available mobile edge
services, etc. Table 4.1.2.1-1 specifies requirements related to application lifecycle management applicable to the Mm3
reference point.
Table 4.1.2.1-1: Mm3 reference point requirements
Number Functional requirement description
Mm3.001 The Mm3 reference point shall support the application package management interface
produced by the Mobile Edge Orchestrator.
Mm3.002 The Mm3 reference point shall support the application Lifecycle Management interface
produced by the Mobile Edge Platform Manager.
Mm3.003 The Mm3 reference point shall support the application Lifecycle Change Notification
interface produced by the Mobile Edge Platform Manager.

ETSI
11 ETSI GS MEC 010-2 V1.1.1 (2017-07)
4.1.2.2 Interface requirements
4.1.2.2.1 Application package management interface requirements
Table 4.1.2.2.1-1 specifies requirements applicable to the Application Package Management interface produced by the
MEO on the Mm3 reference point.
Table 4.1.2.2.1-1: Application Package Management interface requirements
Numbering Functional requirement
Mm3.AppPkgm.001 The Application Package Management interface produced by the MEO on the Mm3 reference
point shall support querying application package information (see note).
Mm3.AppPkgm.002 The Application Package Management interface produced by the MEO on the Mm3 reference
point shall support providing notifications as a result of changes on application package states.
Mm3.AppPkgm.003 The Application Package Management interface produced by the MEO on the Mm3
...