antly reduced using the MEC platform, which is a key enabling factor for many 5G services such as the tactile Internet. MEC supports different deployment scenar- ios, and the MEC servers can be located at different locations within the radio access net- work depending on technical and business requirements. Applications and analytics at the MEC server will not be impacted by congestion in other parts of the network. By perform- ing analytics or caching content at the MEC server, the volume of data transmitted to the core network for processing is reduced, and the impact on the data traffic through the net- work is minimized, resulting in more efficient use of existing network bandwidth. This establishes an ultra-low-latency environment capable of providing mission-critical and real-time services. The user location information can be used by applications and services hosted by the MEC server to offer location/context-related services to the subscribers. Since these applications and services are found at the edge of the network instead of within a centralized cloud, responsiveness can be improved, resulting in an enriched qual- ity of experience for the user. 5G Network Architecture Routing control network capability exposure platform management Mobile core network Mobile edge computing Radio access network Mobile terminal Figure 1.44 Conceptual MEC architecture [48]. Established in December 2014, the ETSI Industry Specification Group (ISG) 53 on MEC has produced normative specifications that enable the hosting of third-party applications in a multi-vendor environment. The initial scope of the ISG MEC was to focus on use cases, and to specify the requirements and the reference architecture, including the components and functional elements that were the key enablers for MEC solutions. The work has contin- ued on platform services, APIs, and interfaces. The MEC platform API is application- agnostic and allows smooth porting of value-creating applications on every mobile-edge server with guaranteed service-level agree