ETSI GS MEC 037 V3.2.1 (2024-04)

Multi-access Edge Computing (MEC); Application Package Format and Descriptor Specification

RGS/MEC-0037v321PKGFORMAT

General Information

• Status: Not Published
• Technical Committee: MEC - Multi-access Edge Computing
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Due Date: 15-Apr-2024
• Completion Date: 12-Apr-2024

Standards Content (Sample)

GROUP SPECIFICATION
Multi-access Edge Computing (MEC);
Application Package Format and Descriptor Specification
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.

2 ETSI GS MEC 037 V3.2.1 (2024-04)

Reference
RGS/MEC-0037v321PKGFORMAT
Keywords
MEC
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from:
https://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
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or governmental
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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 2024.
All rights reserved.
ETSI
3 ETSI GS MEC 037 V3.2.1 (2024-04)
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 Definition of terms, symbols and abbreviations . 9
3.1 Terms . 9
3.2 Symbols . 9
3.3 Abbreviations . 9
4 Introduction . 9
5 MEC application descriptor . 10
5.1 MEC application descriptor content . 10
5.2 MEC application descriptor based on TOSCA specification . 10
5.2.1 Overview of TOSCA model . 10
5.2.2 Introduction of TOSCA based AppD model . 10
5.2.3 General requirements . 12
5.2.3.1 Service template design . 12
5.2.3.2 Import statement . 13
5.2.3.3 Requirements on application specific AppD node type . 15
5.2.3.4 Requirements on AppD service templates . 16
5.2.4 Node type definitions . 16
5.2.4.1 tosca.nodes.mec.MecApp . 16
5.2.4.1.1 Description . 16
5.2.4.1.2 Properties . 17
5.2.4.1.3 Attributes . 19
5.2.4.1.4 Requirements . 19
5.2.4.1.5 Capabilities . 19
5.2.4.1.6 Definition. 19
5.2.4.1.7 Additional Requirements . 20
5.2.4.1.8 Example . 20
5.2.4.2 tosca.nodes.nfv.Vdu.Compute . 22
5.2.4.2.1 Description . 22
5.2.4.2.2 Additional Requirements . 22
5.2.4.2.3 Example . 23
5.2.4.3 tosca.nodes.nfv.Vdu.VirtualBlockStorage . 23
5.2.4.3.1 Description . 23
5.2.4.3.2 Example . 23
5.2.4.4 tosca.nodes.nfv.Vdu.VirtualObjectStorage . 23
5.2.4.4.1 Description . 23
5.2.4.4.2 Example . 24
5.2.4.5 tosca.nodes.nfv.Vdu.VirtualFileStorage . 24
5.2.4.5.1 Description . 24
5.2.4.5.2 Example . 24
5.2.4.6 tosca.nodes.nfv.VduCp . 24
5.2.4.6.1 Description . 24
5.2.4.6.2 Example . 25
5.2.4.7 tosca.nodes.nfv.Vdu.OsContainer . 25
5.2.4.7.1 Description . 25
5.2.4.7.2 Example . 25
5.2.4.8 tosca.nodes.nfv.Mciop . 26
5.2.4.8.1 Description . 26
5.2.4.8.2 Example . 26
ETSI
4 ETSI GS MEC 037 V3.2.1 (2024-04)
5.2.5 Data type definitions . 27
5.2.5.1 Introduction . 27
5.2.5.2 tosca.datatypes.mec.ServiceDependency . 27
5.2.5.2.1 Description . 27
5.2.5.2.2 Properties . 27
5.2.5.2.3 Definition. 28
5.2.5.2.4 Example . 29
5.2.5.2.5 Additional Requirements . 29
5.2.5.3 tosca.datatypes.mec.ServiceDescriptor . 29
5.2.5.3.1 Description . 29
5.2.5.3.2 Properties . 29
5.2.5.3.3 Definition. 30
5.2.5.3.4 Example . 30
5.2.5.3.5 Additional Requirements . 30
5.2.5.4 tosca.datatypes.mec.FeatureDependency . 30
5.2.5.4.1 Description . 30
5.2.5.4.2 Properties . 30
5.2.5.4.3 Definition. 31
5.2.5.4.4 Example . 31
5.2.5.4.5 Additional Requirements . 31
5.2.5.5 tosca.datatypes.mec.TransportDependency. 31
5.2.5.5.1 Description . 31
5.2.5.5.2 Properties . 31
5.2.5.5.3 Definition. 32
5.2.5.5.4 Example . 32
5.2.5.5.5 Additional Requirements . 32
5.2.5.6 tosca.datatypes.mec.TrafficRuleDescriptor . 34
5.2.5.6.1 Description . 34
5.2.5.6.2 Properties . 34
5.2.5.6.3 Definition. 35
5.2.5.6.4 Example . 35
5.2.5.6.5 Additional Requirements . 35
5.2.5.7 tosca.datatypes.mec.DNSRuleDescriptor . 36
5.2.5.7.1 Description . 36
5.2.5.7.2 Properties . 36
5.2.5.7.3 Definition. 36
5.2.5.7.4 Example . 37
5.2.5.7.5 Additional Requirements . 37
5.2.5.8 tosca.datatypes.mec.LatencyDescriptor . 37
5.2.5.8.1 Description . 37
5.2.5.8.2 Properties . 37
5.2.5.8.3 Definition. 37
5.2.5.8.4 Example . 37
5.2.5.8.5 Additional Requirements . 38
5.2.5.9 tosca.datatypes.mec.UserContextTransferCapability . 38
5.2.5.9.1 Description . 38
5.2.5.9.2 Properties . 38
5.2.5.9.3 Definition. 38
5.2.5.9.4 Example . 38
5.2.5.9.5 Additional Requirements . 38
5.2.5.10 tosca.datatypes.mec.AppNetworkPolicy . 39
5.2.5.10.1 Description . 39
5.2.5.10.2 Properties . 39
5.2.5.10.3 Definition. 39
5.2.5.10.4 Example . 39
5.2.5.10.5 Additional Requirements . 39
5.2.5.11 tosca.datatypes.mec.CategoryRef . 40
5.2.5.11.1 Description . 40
5.2.5.11.2 Properties . 40
5.2.5.11.3 Definition. 40
5.2.5.11.4 Example . 40
5.2.5.11.5 Additional Requirements . 40
ETSI
5 ETSI GS MEC 037 V3.2.1 (2024-04)
5.2.5.12 tosca.datatypes.mec.Permission . 41
5.2.5.12.1 Description . 41
5.2.5.12.2 Properties . 41
5.2.5.12.3 Definition. 41
5.2.5.12.4 Example . 41
5.2.5.12.5 Additional Requirements . 41
5.2.5.13 tosca.datatypes.mec.TransportSerializerDescriptor . 42
5.2.5.13.1 Description . 42
5.2.5.13.2 Properties . 42
5.2.5.13.3 Definition. 42
5.2.5.13.4 Example . 42
5.2.5.13.5 Additional Requirements . 43
5.2.5.14 tosca.datatypes.mec.TransportDescriptor . 43
5.2.5.14.1 Description . 43
5.2.5.14.2 Properties . 43
5.2.5.14.3 Definition. 43
5.2.5.14.4 Example . 44
5.2.5.14.5 Additional Requirements . 44
5.2.5.15 tosca.datatypes.mec.SecurityInfo . 44
5.2.5.15.1 Description . 44
5.2.5.15.2 Properties . 44
5.2.5.15.3 Definition. 44
5.2.5.15.4 Example . 45
5.2.5.15.5 Additional Requirements . 45
5.2.5.16 tosca.datatypes.mec.TrafficFilter . 45
5.2.5.16.1 Description . 45
5.2.5.16.2 Properties . 45
5.2.5.16.3 Definition. 46
5.2.5.16.4 Example . 47
5.2.5.16.5 Additional Requirements . 47
5.2.5.17 tosca.datatypes.mec.InterfaceDescriptor . 47
5.2.5.17.1 Description . 47
5.2.5.17.2 Properties . 48
5.2.5.17.3 Definition. 48
5.2.5.17.4 Example . 48
5.2.5.17.5 Additional Requirements . 49
5.2.5.18 tosca.datatypes.mec.TunnelInfo . 49
5.2.5.18.1 Description . 49
5.2.5.18.2 Properties . 49
5.2.5.18.3 Definition. 49
5.2.5.18.4 Example . 49
5.2.5.18.5 Additional Requirements . 49
5.2.6 Capability type definitions . 50
5.2.7 Relationship type definitions . 50
5.2.8 Policy type definitions . 50
5.2.9 Artifact type definitions . 50
5.2.10 Interface type definitions . 50
5.2.11 Group type definitions . 50
5.3 MEC application descriptor based on YANG specification . 50
6 MEC application package . 51
6.1 MEC application package structure and format . 51
6.2 MEC application package file contents . 51
6.2.1 General . 51
6.2.2 MEC application package manifest file . 51
6.2.3 Certificate file . 53
6.2.4 Non-MANO artifact sets in a MEC application package . 53
6.3 Adding security to MEC application package . 53
Annex A (informative): Example for AppD . 54
Annex B (normative): Type definition files . 58
ETSI
6 ETSI GS MEC 037 V3.2.1 (2024-04)
Annex C (normative): Conformance . 59
C.1 Purpose . 59
C.2 ETSI MEC TOSCA YAML service template . 59
C.3 TOSCA processor . 60
Annex D (informative): Change History . 61
History . 63

ETSI
7 ETSI GS MEC 037 V3.2.1 (2024-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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.
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.
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
8 ETSI GS MEC 037 V3.2.1 (2024-04)
1 Scope
The present document specifies the structure and format of a MEC application package and data models of the MEC
application descriptors, fulfilling the requirements defined in ETSI GS MEC 010-2 [1].
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: "Multi-access Edge Computing (MEC); MEC Management; Part 2:
Application lifecycle, rules and requirements management".
NOTE: The data model in the present document is aligned with the information model specified in V3.2.1 of
ETSI GS MEC 010-2 [1].
[2] OASIS Standard TOSCA-Simple-Profile-YAML-v1.3-os: "TOSCA Simple Profile in YAML
Version 1.3".
[3] ETSI GS NFV-SOL 001: "Network Functions Virtualisation (NFV) Release 4; Protocols and Data
Models; NFV descriptors based on TOSCA specification".
[4] ETSI GS NFV-SOL 004: "Network Functions Virtualisation (NFV) Release 4; Protocols and Data
Models; VNF Package and PNFD Archive specification".
[5] ETSI GS MEC 009: "Multi-access Edge Computing (MEC); General principles, patterns and
common aspects of MEC Service APIs".
[6] IETF RFC 3339: "Date and Time on the Internet: Timestamps".
[7] Helm™ (V3.14.0): "Helm Charts".
[8] ETSI TS 129 214: "Universal Mobile Telecommunications System (UMTS); LTE; 5G; Policy and
charging control over Rx reference point (3GPP TS 29.214)".
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 GR MEC 001: "Multi-access Edge Computing (MEC); Terminology".
ETSI
9 ETSI GS MEC 037 V3.2.1 (2024-04)
[i.2] ETSI GR NFV 003: "Network Functions Virtualisation (NFV); Terminology for main concepts in
NFV".
[i.3] ETSI GS MEC 003: "Multi-access Edge Computing (MEC); Framework and Reference
Architecture".
[i.4] ETSI GS MEC 011: "Multi-access Edge Computing (MEC); Edge Platform Application
Enablement".
[i.5] ETSI GS MEC 012: "Multi-access Edge Computing (MEC); Radio Network Information API".
[i.6] ETSI GS MEC 013: "Multi-access Edge Computing (MEC); Location API".
[i.7] ETSI GS MEC 014: "Multi-access Edge Computing (MEC); UE Identity API".
[i.8] ETSI GS MEC 015: "Multi-Access Edge Computing (MEC); Traffic Management APIs".
[i.9] ETSI GS MEC 021: "Multi-access Edge Computing (MEC); Application Mobility Service API".
[i.10] ETSI GS MEC 028: "Multi-access Edge Computing (MEC); WLAN Access Information API".
[i.11] ETSI GS MEC 029: "Multi-access Edge Computing (MEC); Fixed Access Information API".
[i.12] ETSI GS MEC 030: "Multi-access Edge Computing (MEC); V2X Information Services API ".
[i.13] ETSI GS MEC 033: "Multi-access Edge Computing (MEC); IoT API".
[i.14] ETSI GS MEC 040: "Multi-access Edge Computing (MEC); Federation enablement APIs".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI GR MEC 001 [i.1] and ETSI GR NFV 003 [i.2]
apply.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GR MEC 001 [i.1] and ETSI
GR NFV 003 [i.2] apply.
4 Introduction
A MEC application package is a file containing the necessary information of a MEC application, used by the MEC
system for application lifecycle management.
The application package, provided by the application provider, typically contains an application descriptor, software
images and manifest file as defined in ETSI GS MEC 010-2 [1].
The MEC application package can be on-boarded by the OSS to the MEO. Or in case of MEC in NFV deployment (see
ETSI GS MEC 003 [i.3]), the MEC application package can be either on-boarded to the MEAO or to the NFVO.
To unify the MEC package format in both deployment cases, it is defined in such a way that the package can be used by
the MEAO directly, and can be on-boarded as a VNF package to the NFVO without any change.
ETSI
10 ETSI GS MEC 037 V3.2.1 (2024-04)
Therefore the MEC application package format is following these principles:
• The MEC application package format is always a valid VNF package.
• Thus the MEC application package contains a valid AppD that is also a valid VNFD.
• Some of the content of the MEC application package and of the AppD will be ignored by the NFV system in
the case of MEC in NFV deployment.
• Some of the mandatory VNFD properties and policies are not needed in the MEC system, therefore the AppD
will have some fixed default values for those to comply with the VNFD format.
This way, the application developer does not need to know whether the package will be on-boarded to MEO, MEAO or
NFVO.
Clauses 5 and 6 of the present document specify the structure and format of the AppD and of the application package
based on a TOSCA model (see clause 5.2.1) and a TOSCA YAML CSAR file format (see clause 6.1). Other formats are
out of scope of the present document.
5 MEC application descriptor
5.1 MEC application descriptor content
The MEC application descriptor (AppD), including its attributes, is defined in ETSI GS MEC 010-2 [1]. The AppD is
provided to the MEC system during on-boarding as an artifact of the MEC application package. Since the package
format is unified between NFV and MEC, this is described in ETSI GS NFV-SOL 001 [3]. The AppD format is also
unified with the VNFD format. MEC attributes that can be mapped to attributes defined by NFV are represented by
these NFV attributes, while MEC specific attributes are ignored by the NFV system in case of MEC in NFV
deployments.
The following clauses further describe how this is achieved.
5.2 MEC application descriptor based on TOSCA specification
5.2.1 Overview of TOSCA model
Topology and Orchestration Specification for Cloud Applications (TOSCA) is a modelling language for describing the
components of a cloud application and their relationships.
There are several versions of TOSCA specifications, and the present document is based on TOSCA-Simple-Profile-
yaml v1.3 [2], which describes a YAML rendering for TOSCA.
In TOSCA, the concept "service template" is used to describe the structure and orchestration behaviour of cloud
applications. The service template consists of one or multiple "nodes" which describe the components of the
application, and "capabilities" and "requirements" which model the dependency between the components. TOSCA also
defines artifact, interface, policy types, etc. to describe additional characteristics and requirements of the application.
The service template for each MEC application describes its AppD and shall include a node type which is derived from
the MecApp TOSCA node type defined in the present document.
5.2.2 Introduction of TOSCA based AppD model
The format of the AppD is defined a way so it can be used in both MEC standalone and MEC in NFV deployment, and
may be on-boarded into NFV-MANO as a VNFD in MEC in NFV deployment. The TOSCA based AppD model
specified in the present document is designed to be reusable as a VNFD unchanged, more specifically:
• AppD attributes are mapped to TOSCA VNFD types as defined in ETSI GS NFV-SOL 001 [3] where
applicable.
ETSI
11 ETSI GS MEC 037 V3.2.1 (2024-04)
• MEC specific AppD attributes are defined in a way that they will not affect NFV-MANO.
• VNFD mandatory type definitions and properties which are not applicable to AppD are specified to be filled
with default values, see clause 5.2.4.1.7 for the default values in tosca.nodes.nfv.VNF and clause 5.2.4.2.2 for
default values in other nodes.
• The present document defines an abstract node type (tosca.nodes.mec.MecApp) which is derived from the
tosca.nodes.nfv.VNF node type defined in ETSI GS NFV-SOL 001 [3].
Table 5.2.2-1 shows the mapping of the AppD attributes to TOSCA types and property names. AppD attributes that
have no corresponding VNFD TOSCA types are MEC specific attributes which are specified in the following clauses.
Table 5.2.2-1: TOSCA types for AppD attributes
AppD attributes TOSCA types Property names Notes
appDId tosca.nodes.nfv.VNF descriptor_id Content same for
MEC and NFV,
appName tosca.nodes.nfv.VNF product_name
appProvider tosca.nodes.nfv.VNF provider inherit from TOSCA
type defined in ETSI
appSoftVersion tosca.nodes.nfv.VNF software_version
GS NFV-SOL 001 [3]
appDVersion tosca.no
...