Formatting review

The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding but are not required for conformance to the present document.

<span id="_ref_i.1"></span><a name="_ref_i.1">[i.1]</a> [ETSI MEC Sandbox: ](https://labs.etsi.org/rep/mec/mec-sandbox-scenarios/tree/master/Software-Architecture) "ETSI MEC Sandbox – Software Architecture".

<span id="_ref_i.2"></span><a name="_ref_i.2">[i.2]</a> [3GPP TS 23.222: ](https://www.etsi.org/deliver/etsi_ts/123200_123299/123222/18.06.00_60/ts_123222v180600p.pdf) "LTE; 5G; Common API Framework for 3GPP Northbound APIs  (3GPP TS 23.222 version 18.6.0 Release 18)".

<span id="_ref_i.3"></span><a name="_ref_i.3">[i.3]</a> [3GPP TS 29.222: ](https://www.etsi.org/deliver/etsi_ts/129200_129299/129222/18.07.00_60/ts_129222v180700p.pdf) "LTE; 5G; Common API Framework for 3GPP Northbound APIs (3GPP TS 29.222 version 18.7.0 Release 18)

Common API Framework for 3GPP Northbound APIs".

<span id="_ref_i.3"></span><a name="_ref_i.3">[i.3]</a> [3GPP TS 29.222: ](https://www.etsi.org/deliver/etsi_ts/129200_129299/129222/18.07.00_60/ts_129222v180700p.pdf) "LTE; 5G; Common API Framework for 3GPP Northbound APIs (3GPP TS 29.222 version 18.7.0 Release 18) Common API Framework for 3GPP Northbound APIs".

<span id="_ref_i.4"></span>"<a name="_ref_i.4">[i.4]</a> [3GPP TS 33.122: ](https://www.etsi.org/deliver/etsi_ts/133100_133199/133122/18.04.00_60/ts_133122v180400p.pdf) "Security aspects of Common API Framework (CAPIF) for 3GPP northbound APIs".

<span id="_ref_i.5"></span><a name="_ref_i.5">[i.5]</a> [3GPP TR 23.946: ](https://www.etsi.org/deliver/etsi_tr/123900_123999/123946/18.02.00_60/tr_123946v180200p.pdf) "LTE; 5G; Guidelines for CAPIF Usage (3GPP TR 23.946 version 18.2.0 Release 18) Guidelines for CAPIF Usage".

<span id="_ref_i.6"></span><a name="_ref_i.6">[i.6]</a> [ETSI MEC 011: ](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/04.01.01_60/gs_MEC011v040101p.pdf) "Multi-access Edge Computing (MEC); Edge Platform Application Enablement

Edge Platform Application Enablement".

<span id="_ref_i.6"></span><a name="_ref_i.6">[i.6]</a> [ETSI MEC 011: ](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/04.01.01_60/gs_MEC011v040101p.pdf) "Multi-access Edge Computing (MEC); Edge Platform Application Enablement Edge Platform Application Enablement".

<span id="_ref_i.7"></span><a name="_ref_i.7">[i.7]</a> [ETSI SDG OpenCAPIF: ](https://ocf.etsi.org).

<span id="_ref_i.8"></span><a name="_ref_i.8">[i.8]</a> [3GPP Forge 5G_APIs: ](https://forge.3gpp.org/rep/all/5G_APIs).

# 3 Definition of terms, symbols and abbreviations

### 4.2.3 Conclusion

The criterions for choosing the solution are:

- Make the codebase of the onboarding/offboarding of the MEC services common for automatic and custom MEC services;

- Make the process of onboarding/offboarding processed by only one module;

- Make the process of onboarding/offboarding easy to deploy.

## 6.1 Introduction

The purpose is to rebrand the ETSI MEC Sandbox into EdgeNative-X. This branding has an impact on:

- The MEC Sandbox GUI;

- The MEC Sandbox documentation;

- The MEC Sandbox codebase;

## 6.2 The MEC Sandbox GUI branding

The MEC Sandbox GUI will be rebranded into EdgeNative-X GUI. This branding has an impact on:

- All .js files;

- All .java files.

## 6.3 The MEC Sandbox documentation branding

The MEC Sandbox documentation will be rebranded into EdgeNative-X GUI. This branding has an impact on:

- All .md files;

- All LICENSE files;

- All README files;

## 6.4 The MEC Sandbox codebase branding

The MEC Sandbox documentation will be rebranded into EdgeNative-X GUI. This branding has an impact on:

- All .sh files;

- All .py files;

- All .go files.

## 6.5 The MEC Sandbox examples branding

The MEC Sandbox examples will be rebranded into EdgeNative-X GUI. This branding has an impact on:

- All .sh files;

- All .py files;

- All .go files.

## 6.6 The MEC Sandbox configuration branding

The MEC Sandbox configuration will be rebranded into EdgeNative-X GUI. This branding has an impact on:

- All .yaml files;

- All .json files.