nctionality of: Application enablement platform (API framework) (MEC009); Specific service-related APIs; Management and orchestration-related APIs. Such APIs are designed to be application-developer-friendly and easy to implement SO as to stimulate innovation and foster the development of different applications (GSS+18, GCA17) and ultimately the emergence of a MEC application market, SO that it would be possible to deploy MEC applications from different vendors on MEC platforms from other vendors. Furthermore, ETSI ISG MEC specifies a set of RESTful APIs as standardized interfaces, which can be used by application developers, in order to access radio network informa- tion (RNI API) (MEC012), location information (Location API) (MEC013), UE identity (UE identity API) (MEC014), as well as information for bandwidth management (MEC015) and other types of data pre-processed either by the MEC platform or by instantiated MEC applications. In particular, thanks to the RNI API, context information from the RAN can be provided to user-level applications or other services for network performance and QoS improvements. It is worth mentioning that while RNI provides a standardized API to an application to access RAN-related information, the retrieval of this information from RAN is not standardized and is left for vendor-specific implementations. Recently, ETSI ISG MEC has expanded the scope of its activities to include additional access technologies besides cellular, as well as support for IoT deployments with low-energy support (ZZM+16) and connected cars. To reflect this change the term MEC was updated from mobile edge computing to multi-access edge computing. This is aimed at strengthening the engagement with original equipment manufacturers (OEMs) and service providers as key stakeholders exploiting MEC for their added-value product propositions. As an example of such activity, ETSI ISG MEC is introducing a "V2X Information Service API" to assist the MEC system in exposing information to applications allowing developers, 