ETSI GS MEC-DEC 032-1 V2.1.1 (2020-12)

Multi-access Edge Computing (MEC); API Conformance Test Specification; Part 1: Test Requirements and Implementation Conformance Statement (ICS)

DGS/MEC-DEC32-1APIConformance

General Information

• Status: Not Published
• Technical Committee: MEC DECODE - Deployment and ECOsystem DEvelopment
• Current Stage: 12 - Completion
• Due Date: 15-Dec-2020
• Completion Date: 21-Dec-2020

Standards Content (Sample)

ETSI GS MEC-DEC 032-1 V2.1.1 (2020-12)






GROUP SPECIFICATION
Multi-access Edge Computing (MEC);
API Conformance Test Specification;
Part 1: Test Requirements and
Implementation Conformance Statement (ICS)
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-DEC 032-1 V2.1.1 (2020-12)



Reference
DGS/MEC-DEC32-1APIConformance
Keywords
API, conformance, MEC, testing

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-DEC 032-1 V2.1.1 (2020-12)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Introduction . 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 Conformance requirement concerning ICS . 9
Annex A (normative): MEC ICS Pro forma . 10
A.0 The right to copy . 10
A.1 Guidance for completing the ICS Pro forma . 10
A.1.1 Purpose and structure . 10
A.1.2 Instructions for completing the ICS pro forma . 10
A.2 Identification of the implementation . 10
A.2.1 Introduction . 10
A.3 Identification of the ETSI MEC APIs . 13
A.4 Global statement of conformance . 13
A.4.1 Introduction . 13
A.4.2 Functional entities and Reference Points . 14
A.4.3 API Resources and Reference Points . 14
A.5 Requirements and ICS tables . 15
A.5.1 ETSI GS MEC 010-1 . 15
A.5.1.1 Test Requirements . 15
A.5.1.2 ICS . 16
A.5.2 ETSI GS MEC 010-2 . 17
A.5.2.1 Test Requirements . 17
A.5.2.2 ICS . 22
A.5.3 ETSI GS MEC 011 . 30
A.5.3.1 Test Requirements . 30
A.5.3.2 ICS . 31
A.5.4 ETSI GS MEC 012 . 33
A.5.4.1 Test Requirements . 33
A.5.4.2 ICS . 35
A.5.5 ETSI GS MEC 013 . 38
A.5.5.1 Test Requirements . 38
A.5.5.2 ICS . 40
A.5.6 ETSI GS MEC 014 . 42
A.5.6.1 Test Requirements . 42
A.5.6.2 ICS . 43
A.5.7 ETSI GS MEC 015 . 44
A.5.7.1 Test Requirements . 44
A.5.7.2 ICS . 45
A.5.8 ETSI GS MEC 016 . 46
A.5.8.1 Test Requirements . 46
ETSI

---------------------- Page: 3 ----------------------
4 ETSI GS MEC-DEC 032-1 V2.1.1 (2020-12)
A.5.8.2 ICS . 47
A.5.9 ETSI GS MEC 021 . 48
A.5.9.1 Test Requirements . 48
A.5.9.2 ICS . 50
A.5.10 ETSI GS MEC 028 . 54
A.5.10.1 Test Requirements . 54
A.5.10.2 ICS . 54
A.5.11 ETSI GS MEC 029 . 54
A.5.11.1 Test Requirements . 54
A.5.11.2 ICS . 56
A.5.12 ETSI GS MEC 030 . 58
A.5.12.1 Test Requirements . 58
A.5.12.2 ICS . 58
Annex B (informative): Change History . 59
History . 60


ETSI

---------------------- Page: 4 ----------------------
5 ETSI GS MEC-DEC 032-1 V2.1.1 (2020-12)
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).
The present document is part 1 of a multi-part deliverable covering Conformance Test Specification for MEC APIs as
identified below:
Part 1: "Test Requirements and Implementation Conformance Statement (ICS)";
Part 2: "Test Purposes (TP)";
Part 3: "Abstract Test Suite (ATS)".
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-DEC 032-1 V2.1.1 (2020-12)
Introduction
The development of standardized conformance test specifications is considered as a validation activity and is an integral
part of the ETSI strategy for ensuring interoperability. The MEC Conformance Testing methodology consists of:
• Selection of Implementations Under Test (IUT).
• Identification of reference points.
• Development of test specifications, which includes:
- Development of "Implementation Conformance Statements" (ICS).
- Development of "Test Suite Structure and Test Purposes" (TSS&TP).
- Development of "Abstract Test Suite" (ATS).
The present document focuses on ICS development.

ETSI

---------------------- Page: 6 ----------------------
7 ETSI GS MEC-DEC 032-1 V2.1.1 (2020-12)
1 Scope
Based on the testing methodology guidelines and framework specified in ETSI GR MEC-DEC 025 [i.1], the present
document specifies part 1 of a multi-part deliverable test specification. Part 1 (the present document) provides the Test
requirements and Implementation Conformance Statement (ICS) for: Application Package Management and
Application Lifecyle Management as specified in ETSI GS MEC 10-2 [4]; MEC Application Enablement as specified
in ETSI GS MEC 011 [5]; and the MEC service APIs. The MEC service APIs in scope of the present document are
specified in:
• ETSI GS MEC 012 [6];
• ETSI GS MEC 013 [7];
• ETSI GS MEC 014 [8];
• ETSI GS MEC 015 [9];
• ETSI GS MEC 016 [10];
• ETSI GS MEC 021 [11]; and
• ETSI GS MEC 029 [13];
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 (V2.1.1) (01-2019): "Multi-access Edge Computing (MEC); Terminology".
[2] ETSI GS MEC 002 (V2.1.1) (10-2018): "Multi-access Edge Computing (MEC); Phase 2: Use
Cases and Requirements".
[3] ETSI GS MEC 010-1 (V1.1.1) (10-2017): "Mobile Edge Computing (MEC); Mobile Edge
Management; Part 1: System, host and platform management".
[4] ETSI GS MEC 010-2 (V2.1.1) (11-2019): "Multi-access Edge Computing (MEC); MEC
Management; Part 2: Application lifecycle, rules and requirements management".
[5] ETSI GS MEC 011 (V2.1.1) (11-2019): "Multi-access Edge Computing (MEC); Edge Platform
Application Enablement".
[6] ETSI GS MEC 012 (V2.1.1) (12-2019): "Multi-access Edge Computing (MEC); Radio Network
Information API".
[7] ETSI GS MEC 013 (V2.1.1) (09-2019): "Multi-access Edge Computing (MEC); Location API".
[8] ETSI GS MEC 014 (V1.1.1) (02-2018): "Mobile Edge Computing (MEC); UE Identity API".
ETSI

---------------------- Page: 7 ----------------------
8 ETSI GS MEC-DEC 032-1 V2.1.1 (2020-12)
[9] ETSI GS MEC 015 (V1.1.1) (10-2017): "Mobile Edge Computing (MEC); Bandwidth
Management API".
[10] ETSI GS MEC 016 (V2.1.1) (04-2019): "Multi-access Edge Computing (MEC); UE application
interface".
[11] ETSI GS MEC 021 (V2.1.1) (01-2020): "Multi-access Edge Computing (MEC); Application
Mobility Service API".
[12] ETSI GS MEC 028 (V2.1.1) (06-2020): "Multi-access Edge Computing (MEC); WLAN
Information API".
[13] ETSI GS MEC 029 (V2.1.1) (07-2019): "Multi-access Edge Computing (MEC); Fixed Access
Information API".
[14] ETSI GS MEC 030 (V2.1.1) (04-2020): "Multi-access Edge Computing (MEC); V2X Information
Service API".
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-DEC 025 (V2.1.1) (06-2019): "Multi-access Edge Computing (MEC); MEC
Testing Framework".
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] and the following apply:
conformance testing: purpose of conformance testing is to determine to what extent a single implementation of a
particular standard conforms to the individual requirements of that standard
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AMS MEC App Mobility Service
API Application Programming Interface
ATS Abstract Test Suite
DNS Domain Name Service
FAI Fixed Access Information
GR Group Report
HTTP HyperText Transfer Protocol
ICS Implementation Conformance Statement
ETSI

---------------------- Page: 8 ----------------------
9 ETSI GS MEC-DEC 032-1 V2.1.1 (2020-12)
IUT Implementation Under Test
LCM Life Cycle Management
MEH MEC Host
MEO MEC Orchestrator
MEPM MEC Platform Manager
NR New Radio
OSS Operations Support System
PLMN Public Land Mobile Network
RNI Radio Network Information
RNIS Radio Network Information Service
SUT System Under Test
TP Test Purpose
UE User Equipment
URI Uniform Resource Identifier
WAIS WLAN Access Information MEC Service
WLAN Wireless Local Area Network
4 Conformance requirement concerning ICS
If it claims to conform to the present document, the actual ICS pro forma to be filled in by a supplier shall be
technically equivalent to the text of the ICS pro forma given in annex A, and shall preserve the numbering, naming and
ordering of the pro forma items.
An ICS which conforms to the present document shall be a conforming ICS pro forma completed in accordance with
the instructions for completion given in clause A.1.

ETSI

---------------------- Page: 9 ----------------------
10 ETSI GS MEC-DEC 032-1 V2.1.1 (2020-12)
Annex A (normative):
MEC ICS Pro forma
A.0 The right to copy
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that
users of the present document may freely reproduce the ICS pro forma in this annex so that it can be used for its
intended purposes and may further publish the completed ICS.
A.1 Guidance for completing the ICS Pro forma
A.1.1 Purpose and structure
The purpose of this ICS pro forma is to provide a mechanism whereby a supplier of an implementation of the
requirements defined in ETSI MEC APIs specifications may provide information about the implementation in a
standardized manner.
The ICS pro forma is subdivided into clauses for the following categories of information:
• guidance for completing the ICS pro forma;
• identification of the implementation;
• identification of the ETSI MEC API;
• global statement of conformance;
• requirements and ICS tables.
A.1.2 Instructions for completing the ICS pro forma
The supplier of the implementation shall complete the ICS pro forma in each of the spaces provided. In particular, an
explicit answer shall be entered, in each of the support or supported column boxes provided.
If necessary, the supplier may provide additional comments in space at the bottom of the tables or separately.
More detailed instructions are given at the beginning of the different clauses of the ICS pro forma.
A.2 Identification of the implementation
A.2.1 Introduction
Identification of the Implementation Under Test (IUT) and the system in which it resides (the System Under Test
(SUT)) should be communicated so as to provide as much detail as possible regarding version numbers and
configuration options.
Clause A.2 provides a template to provide such information.
The product supplier information and client information should both be filled in if they are different. A person who can
answer queries regarding information supplied in the ICS should be named as the contact person.
ETSI

---------------------- Page: 10 ----------------------
11 ETSI GS MEC-DEC 032-1 V2.1.1 (2020-12)
A.2.2 Date of the statement
.
A.2.3 Implementation Under Test (IUT) identification
IUT name:
.
.
IUT version:
.
.
A.2.4 System Under Test (SUT) identification
SUT name:
.
.
Hardware configuration:
.
.
.
A.2.5 Product supplier
Name:
.
Address:
.
.
.
Telephone number:
.
Facsimile number:
.
E-mail address:
.
ETSI

---------------------- Page: 11 ----------------------
12 ETSI GS MEC-DEC 032-1 V2.1.1 (2020-12)
Additional information:
.
.
.
A.2.6 Client (if different from product supplier)
Name:
.
Address:
.
.
.
Telephone number:
.
Facsimile number:
.
...