# 5G-MEC Testbeds for V2X Applications
## 5 Summary of Available Tools
### Mep  
The ETSI architecture can be customized to build an MEC system in which the MEP plays a pivotal role in delivering MEC applications hosted on an MEH. The MEP provides the necessary MEC services for MEC applications. The MEC ecosystem comprises a list of ETSI-compliant MEC development tools, many of which are still in development. The implementations are classified based on the ETSI MEC-compliant architecture. The MEH encompasses the MEP and MEC applications running on the VI. The **5 GCity SDK**[32] MEC system builds a customized MEP on virtualized infrastructure compliant with the ETSI architecture. To deploy the 5 GCity MEC system, VMs are required, and the specifications are listed in Table 4. The 5 GCity MEP facilitates MEC application notifications and enables the creation, deletion, and discovery of new services required by the MEC system. Furthermore, the 5 GCity MEP manages the DNS platform and DNS rules within the MEH. The 5 GCity MEP can also communicate with third-party applications and manage the life cycle of the MEC applications. The 5 GCity MEC system implements the Mp1 and Mm5 interfaces in a proprietary manner. The Low-Latency MEC (**LL-MEC**) [87] platform is partially compliant with the ETSI MEC architecture. The LL-MEP aligns the Mp1 interface with the MEC application and the Mp2 interface with the virtual infrastructure to support low-latency MEC applications. The Mp1 interface uses a REST API to enable MEC services and the Mp2 interface focuses on DNS rules and traffic routing. The LL-MEP also allows for the separation of the userplane functions from the control plane functions using SDN principles and the OpenFlow protocol. Additionally, LL-MEP includes the RNIS MEC service standardized by the ETSI for deriving RAN information. LL-MEP is mainly implemented using C++ on an x86 Linux system. The **EdgeX foundry**[38] MEP is an industrialized solution developed by the Linux foundation. EdgeX is an open source edge platform that is non-compliant with the ETSI architecture. It uses Docker for containerized MEC applications, and to manage these applications, EdgeX uses docker-compose running on an x86 Linux system. EdgeX supports virtual device services that simulate user devices, allowing for device and data management using the MQTT broker. **OpenNESS**[88] is an Intel smart-edge open source MEC SDK that is compliant with the ETSI architecture. It has an MEP and an MEP manager that allow for building, deploying, and managing MEC applications. OpenNESS includes different SDKs depending on the requirement, such as on-premises, access edge, and near-the-edge experience kits. It provides support for high-performance data planes and the management of virtual infrastructure. However, OpenNESS has two dissemination kits: one is open source and the other is an Intel-licensed distribution. OpenNESS has Intel-based hardware requirements to optimize the solution and run the experiments. In addition, it provides an interface and the possibility to integrate with the orchestration VIM tools such as OSM, OpenBaton, OpenStack, and K8s. OpenNESS allows for exploring resource allocation and management using edge multi-cluster orchestration (EMCO). It has an easy way of handling new application onboarding [89]. **LightEDGE**[90] is an open source lightweight MEP solution that is compliant with the ETSI architecture. It includes an MEP manager that is non-compliant with the ETSI architecture. LightEDGE utilizes a microservice architecture and operates on a K8s cluster. The LightEDGE MEP includes several MEC services specified by the ETSI, including the RNIS service. It also includes a UPF microservice, and 5G-EmPOWER is used to incorporate the RNIS services to extract RAN information. LightEDGE [91] supports 4G and 5G environments and can integrate with the Open5 GS and srsRAN solutions. LightEDGE was developed to integrate with OSM to ensure seamless orchestration. **AdvantEDGE**[92] is a mobile edge emulation platform (MEEP) that was developed by Inter-digital.