ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)

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

RGS/MEC-DEC32-1v321ApiTest

General Information

• Status: Not Published
• Technical Committee: MEC DECODE - Deployment and ECOsystem DEvelopment
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Due Date: 28-Aug-2023
• Completion Date: 11-Aug-2023

Standards Content (Sample)

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.

2 ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)

Reference
RGS/MEC-DEC32-1v321ApiTest
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 - 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 2023.
All rights reserved.
ETSI
3 ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)
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 . 9
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 . 17
A.5.2 ETSI GS MEC 010-2 . 17
A.5.2.1 Test Requirements . 17
A.5.2.2 ICS . 24
A.5.3 ETSI GS MEC 011 . 38
A.5.3.1 Test Requirements . 38
A.5.3.2 ICS . 39
A.5.4 ETSI GS MEC 012 . 43
A.5.4.1 Test Requirements . 43
A.5.4.2 ICS . 45
A.5.5 ETSI GS MEC 013 . 48
A.5.5.1 Test Requirements . 48
A.5.5.2 ICS . 50
A.5.6 ETSI GS MEC 014 . 54
A.5.6.1 Test Requirements . 54
A.5.6.2 ICS . 55
A.5.7 ETSI GS MEC 015 . 55
A.5.7.1 Test Requirements . 55
A.5.7.2 ICS . 56
A.5.8 ETSI GS MEC 016 . 58
A.5.8.1 Test Requirements . 58
ETSI
4 ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)
A.5.8.2 ICS . 59
A.5.9 ETSI GS MEC 021 . 60
A.5.9.1 Test Requirements . 60
A.5.9.2 ICS . 62
A.5.10 ETSI GS MEC 028 . 66
A.5.10.1 Test Requirements . 66
A.5.10.2 ICS . 67
A.5.11 ETSI GS MEC 029 . 70
A.5.11.1 Test Requirements . 70
A.5.11.2 ICS . 71
A.5.12 ETSI GS MEC 030 . 74
A.5.12.1 Test Requirements . 74
A.5.12.2 ICS . 75
A.5.13 ETSI GS MEC 033 . 78
A.5.13.1 Test Requirements . 78
A.5.13.2 ICS . 79
A.5.14 ETSI GS MEC 040 . 81
A.5.14.1 Test Requirements . 81
A.5.14.2 ICS . 83
Annex B (informative): Change History . 84
History . 85

ETSI
5 ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)
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).
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
6 ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)
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
7 ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)
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: MEC system, host and platform management as
specified in ETSI GS MEC 010-1 [3]; Application Package Management and Application Lifecycle Management as
specified in ETSI GS MEC 010-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];
• ETSI GS MEC 028 [12];
• ETSI GS MEC 029 [13];
• ETSI GS MEC 030 [14];
• ETSI GS MEC 033 [15]; and
• ETSI GS MEC 040 [16]
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] Void.
[2] ETSI GS MEC 002 (V2.2.1) (01-2022): "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 (V3.1.1) (06-2023): "Multi-access Edge Computing (MEC); MEC
Management; Part 2: Application lifecycle, rules and requirements management".
[5] ETSI GS MEC 011 (V3.1.1) (09-2022): "Multi-access Edge Computing (MEC); Edge Platform
Application Enablement".
ETSI
8 ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)
[6] ETSI GS MEC 012 (V2.2.1) (02-2022): "Multi-access Edge Computing (MEC); Radio Network
Information API".
[7] ETSI GS MEC 013 (V3.1.1) (01-2023): "Multi-access Edge Computing (MEC); Location API".
[8] ETSI GS MEC 014 (V2.1.1) (03-2021): "Multi-access Edge Computing (MEC); UE Identity API".
[9] ETSI GS MEC 015 (V2.2.1) (12-2022): "Multi-Access Edge Computing (MEC); Traffic
Management APIs".
[10] ETSI GS MEC 016 (V2.2.1) (04-2020): "Multi-access Edge Computing (MEC); Device
application interface".
[11] ETSI GS MEC 021 (V2.2.1) (02-2022): "Multi-access Edge Computing (MEC); Application
Mobility Service API".
[12] ETSI GS MEC 028 (V2.3.1) (07-2022): "Multi-access Edge Computing (MEC); WLAN Access
Information API".
[13] ETSI GS MEC 029 (V2.2.1) (01-2022): "Multi-access Edge Computing (MEC); Fixed Access
Information API".
[14] ETSI GS MEC 030 (V2.2.1) (05-2022): "Multi-access Edge Computing (MEC); V2X Information
Service API".
[15] ETSI GS MEC 033 (V3.1.1) (12-2022): "Multi-access Edge Computing (MEC); IoT API".
[16] ETSI GS MEC 040 (V3.1.1) (02-2023): "Multi-access Edge Computing (MEC); Federation
enablement APIs".
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".
[i.2] ETSI GR MEC 001 (V3.1.1) (01-2022): "Multi-access Edge Computing (MEC); Terminology".
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.2] 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.
ETSI
9 ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GR MEC 001 [i.2] and the following apply:
AMS Application Mobility Service
ATS Abstract Test Suite
FAI Fixed Access Information
GR Group Report
GS Group Specification
ICS Implementation Conformance Statement
IUT Implementation Under Test
SUT System Under Test
TP Test Purpose
TSS Test Suite Structure
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
10 ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)
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
11 ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)
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
12 ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)
Additional information:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
...............................................................................................................................................................................................
A.2.6 Client (if different from product supplier)
Name:
...............................................................................................................................................................................................
Address:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
...............................................................................................................................................................................................
Telephone number:
...............................................................................................................................................................................................
Facsimile number:
...............................................................................................................................................................................................
E-mail address:
...............................................................................................................................................................................................
Additional information:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
...............................................................................................................................................................................................
A.2.7 ICS contact person
(A person to contact if there are any queries concerning the content of the ICS.)
Name:
...............................................................................................................................................................................................
Telephone number:
...............................................................................................................................................................................................
Facsimile number:
...............................................................................................................................................................................................
ETSI
13 ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)
E-mail address:
...............................................................................................................................................................................................
Additional information:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
...............................................................................................................................................................................................
A.3 Identification of the ETSI MEC APIs
This ICS pro forma applies to the following standards:
• ETSI GS MEC 010-2 (V3.1.1) (06-2023): "Multi-access Edge Computing (MEC); MEC Management;
Part 2: Application lifecycle, rules and requirements management".
• ETSI GS MEC 011 (V3.1.1) (09-2022): "Multi-access Edge Computing (MEC); Edge Platform Application
Enablement".
• ETSI GS MEC 012 (V2.2.1) (02-2022): "Multi-access Edge Computing (MEC); Radio Network Information
API".
• ETSI GS MEC 013 (V3.1.1) (01-2023): "Multi-access Edge Computing (MEC); Location API".
• ETSI GS MEC 014 (V2.1.1) (03-2021): "Multi-access Edge Computing (MEC); UE Identity API".
• ETSI GS MEC 015 (V2.2.1) (12-2022): "Multi-access Edge Computing (MEC); Traffic Management API".
• ETSI GS MEC 016 (V2.2.1) (04-2020): "Multi-access Edge Computing (MEC); Device application interface".
• ETSI GS MEC 021 (V2.2.1) (02-2022): "Multi-access Edge Computing (MEC); Application Mobility Service
API".
• ETSI GS MEC 028 (V2.3.1) (07-2022): "Multi-access Edge Computing (MEC); WLAN Information API".
• ETSI GS MEC 029 (V2.2.1) (01-2022): "Multi-access Edge Computing (MEC); Fixed Access Information
API".
• ETSI GS MEC 030 (V2.2.1) (05-2022): "Multi-access Edge Computing (MEC); V2X Information Service
API".
• ETSI GS MEC 033 (V3.1.1) (12-2022): "Multi-access Edge Computing (MEC); IoT API".
• ETSI GS MEC 040 (V3.1.1) (02-2023): "Multi-access Edge Computing (MEC); Federation enablement APIs".
A.4 Global statement of conformance
A.4.1 Introduction
Clause A.4 provides a template for a global statement of conformance.
Are all mandatory capabilities implemented? (Yes/No) .
NOTE: Answering "No" to this question indicates non-conformance to the MEC API standard specification.
Non-supported mandatory capabilities are to be identified in the ICS, with an explanation of why the implementation is
non-conforming, on pages attached to the ICS pro forma.
ETSI
14 ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)
A.4.2 Functional entities and Reference Points
Table A.4.2-1
Item Entity type Mnemonic Reference Condition Support
1 MEC Platform MEC_PLAT ETSI GR MEC-DEC 025, C.1 O Yes O No
clause 6.1.3
2 Other component of the MEC_SYSTEM ETSI GR MEC-DEC 025, C.1 O Yes O No
MEC System clause 6.1
3 MEC Service provider SERVICES C.1 O Yes O No
C.1: At least one shall be supported.

A.4.3 API Resources and Reference Points
The IUT provider shall fill Table A.4.3-1 to express more specific capabilities of the IUT. By checking "Yes" in the
support column, the IUT provider expresses the intention to be tested for conformance on all endpoints and operations
defined in the related Table identified in the "Reference" column.
The mnemonic column contains an identifier for the group of capabilities, used in the definition of Test Purposes and
Test Cases. The Mnemonic identifier is not provided for all groups, and when not defined the related cell shall contain
"na" (not available).
Table A.4.3-1 specifies two types of items:
• Level 1 items, identified by a singular digit (e.g. 1), which identify base specification; and
• Level 2 items, identified by a two digits separated by a dot (e.g. 1.1), which identify sub elements of the base
specification for more detailed statements.
To express that an IUT that does not support any of the Level 2 items for a certain certification, the IUT provider shall
check "No" in the support column for the related Level 1 item. The related Level 2 items may be left unchecked and
they will be assume not to be tested.
To express that an IUT does support some (or all) of the Level 2 items for a certain specification, the IUT provider shall
check "Yes" in the support column for the related Level 1 item and mark all Level 2 items according to the IUT
implementation capabilities.
Table A.4.3-1
Item Entity type Mnemonic Reference Condition Support
1 ETSI GS MEC 010-2 na Clause A.5.2 C.1 O Yes O No
>1.1 Application package APP_PACKAGE_MANAGEMENT_ Table A.5.2.2-1 C.1 O Yes O No
management (Mm1) MM1
>1.2 Application package APP_PACKAGE_MANAGEMENT_ Table A.5.2.2-2 C.1 O Yes O No
management (Mm3) MM3
>1.3 App Package APP_PACKAGE_NOTIFICATIONS Table A.5.2.2-3 C.1 O Yes O No
Management
notification callback
>1.4 Application life cycle APP_LCM_MANAGEMENT_MM1_ Table A.5.2.2-4 C.1 O Yes O No
management (Mm1 MM3
and Mm3)
>1.5 Application life cycle APP_LCM_NOTIFICATIONS Table A.5.2.2-5 C.1 O Yes O No
management
notification call-backs
(Mm1, Mm3 and
Mm3*)
>1.6 Granting for GRANTS_MANAGEMENT Table A.5.2.2-6 C.1 O Yes O No
application life cycle
management
operations (Mm3)
>1.7 Application life cycle APP_LCM_MANAGEMENT_MM3* Table A.5.2.2-7 C.1 O Yes O No
management (Mm3*)
ETSI
15 ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)
Item Entity type Mnemonic Reference Condition Support
2 ETSI GS MEC 011 na Clause A.5.3 C.1 O Yes O No
>2.1 MEC Application APP_SUPPORT Table A.5.3.2-1 C.1 O Yes O No
Support
>2.2 Service Management SERVICE_MANAGEMENT Table A.5.3.2-2 C.1 O Yes O No
3 ETSI GS MEC 012 na Clause A.5.4 C.1 O Yes O No
>3.1 RNIS simple queries RNIS_QUERY Table A.5.4.2-1 C.1 O Yes O No
>3.2 All subscriber's RNIS_ALL_SUBSCRIPTIONS Table A.5.4.2-2 C.1 O Yes O No
subscriptions
>3.3 Individual RNIS_SPECIFIC_SUBSCRIPTION Table A.5.4.2-3 C.1 O Yes O No
subscriptions
>3.4 Notification callback RNIS_NOTIFICATIONS Table A.5.4.2-4 C.1 O Yes O No
4 ETSI GS MEC 013 na Clause A.5.5 C.1 O Yes O No
>4.1 Simple queries na Table A.5.5.2-1 C.1 O Yes O No
>4.2 Manage a specific na Table A.5.5.2-2 C.1 O Yes O No
item
5 ETSI GS MEC 014 na Clause A.5.6 C.1 O Yes O No
>5.1 Manage a specific na Table A.5.6.2-1 C.1 O Yes O No
item
6 ETSI GS MEC 015 na Clause A.5.7 C.1 O Yes O No
>6.1 Bandwidth BANDWIDTH_MANAGEMENT Table A.5.7.2-1 C.1 O Yes O No
Management
>6.2 Multi-access Traffic TRAFFIC_STEERING Table A.5.7.2-2 C.1 O Yes O No
Steering
7 ETSI GS MEC 016 na Clause A.5.8 C.1 O Yes O No
>7.1 Simple queries na Table A.5.8.2-1 C.1 O Yes O No
>7.2 Manage a specific na Table A.5.8.2-2 C.1 O Yes O No
item
8 ETSI GS MEC 021 na Clause A.5.9 C.1 O Yes O No
>8.1 AMS APIs AMS Table A.5.9.2-1 C.1 O Yes O No
>8.2 Notification callback AMS_NOTIFICATIONS Table A.5.9.2-2 C.1 O Yes O No
9 ETSI GS MEC 028 na Clause A.5.10 C.1 O Yes O No
>9.1 Simple queries WAIS_QUERY Table A.5.10.2-1 C.1 O Yes O No
>9.2 Subscriptions and WAIS_SUBSCRIPTIONS_NOTIFI Table A.5.10.2-2 C.1 O Yes O No
notifications CATIONS
>9.3 Measurements WAIS_MEASUREMENTS Table A.5.10.2-3 C.1 O Yes O No
10 ETSI GS MEC 029 na Clause A.5.11 C.1 O Yes O No
>10.1 Simple queries na Table A.5.11.2-1 C.1 O Yes O No
>10.2 Manage a specific na Table A.5.11.2-2 C.1 O Yes O No
item
11 ETSI GS MEC 030 na Clause A.5.12 C.1 O Yes O No
>11.1 VIS APIs VIS_APIS Table A.5.12.2-1 C.1 O Yes O No
>11.2 Notification callback VIS_ NOTIFICATIONS Table A.5.12.2-2 C.1 O Yes O No
12 ETSI GS MEC 033 na Clause A.5.13 C.1 O Yes O No
>12.1 IoT APIs IOTS_APIS Table A.5.13.2-1 C.1 O Yes O No
13 ETSI GS MEC 040 na Clause A.5.14 C.1 O Yes O No
>13.1 MEC FE APIs FE_APIS Table A.5.14.2-1 C.1 O Yes O No
C.1: At least one shall be supported.

A.5 Requirements and ICS tables
A.5.1 ETSI GS MEC 010-1
A.5.1.1 Test Requirements
Table A.5.1.1-1 reports the functional requirements specified in ETSI GS MEC 010-1, classified per MEPM features.
ETSI
16 ETSI GS MEC-DEC 032-1 V3.2.1 (2023-08)
Table A.5.1.1-1: Classification of MEPM requirements per MEPM features (Mm2)
Feature Requirement ID Requirement description Reference
MEH configuration REQ-MM2-MEH-CM-3 The Mm2 reference point shall ETSI GS MEC 010-1,
management (active) support a capability allowing the clause 5.1.1.1.1
OSS to configure the MEC host.
REQ-MM2-MEH-CM-4 The Mm2 reference point shall ETSI GS MEC 010-1,
support a capability allowing the clause 5.1.1.1.1
OSS to configure the DNS rules.
REQ-MM2-MEH-CM-5 The Mm2 reference point shall ETSI GS MEC 010-1,
support a capability allowing the clause 5.1.1.1.1
OSS to configure the traffic rules.
MEH configuration REQ-MM2-MEH-CM-1 The Mm2 reference point shall ETSI GS MEC 010-1,
management (passive) support a capability allowing the clause 5.1.1.1.1
OSS to retrieve the information
model of the MEC host, or parts
thereof, from the MEC platform
manager.
REQ-MM2-MEH-CM-2 The Mm2 reference point shall ETSI GS MEC 010-1,
support a capability allowing the clause 5.1.1.1.1
MEC platform manager to notify
changes related to the
information model of the MEC
host to the OSS.
MEH fault REQ-MM2-MEH-FM-1 The Mm2 reference point shall
ETSI GS MEC 010-1,
management support a capability allowing the clause 5.1.1.1.2
MEC platform manager to send
MEC platform related alarms to
the OSS.
REQ-MM2-MEH-FM-2 The Mm2 reference point shall ETSI GS MEC 010-1,
support a capability allowing the clause 5.1.1.1.2
OSS to retrieve and manage
alarms from the MEC platform
manager.
MEC Applications REQ-MM2-MEA-CM-1 The Mm2 reference point shall ETSI GS MEC 010-1,
configuration support a capability allowing the clause 5.1.1.2.1
management (active) OSS to create managed object
instances representing MEC
application instances in the MEC
platform manager.
REQ-MM2-MEA-CM-2 The Mm2 reference point shall ETSI GS MEC 010-1,
support a capability allowing the clause 5.1.1.2.1
OSS to delete managed object
instances representing MEC
application instanc
...