Introduction

The forthcoming emergence of Internet over Everything is driven by the evolution of 5G communication, rapid growth of cloud, social media, and mobile computing, the use of Data Science to generate smart analytics value. This evolution brings to the forefront new type of communications such as Machine to Machine and Person to Machine [1]. According to RCR wireless, more than 50 Billion Internet of Things (IoT) devices will be interconnected by 2020 [2]. In this new environment, there is a need to manage, process and store the huge amount of data generated at the network edges. Cloud computing frees the enterprise and the end users from many details. As an effect, computational and network overhead at central cloud increases. This creates problems with real-time applications where latency is a crucial factor. Edge Cloud (EdgeC) Computing has been introduced to reduce network stress (i.e. latency) by shifting resources at the edge of network to proximity of mobile users and IoT while providing services and seamlessly processing the contents. As it implies, the idea of EdgeC has emanated from Cloud Computing (CC) leading towards to Mobile Cloud Computing (MCC). It offers cloud resources at the edge of network with low latency and high bandwidth. Mobile Edge Computing (MEC) started to gain attention of research community in last few years with preliminary research contributions so far such as: standardization of some key interfaces for mobile edge computing [3], building super-short applications requiring a low response time and latency [4,5,6] and modeling hyper-scale datacentres with micro datacentres at the edge of networks [7]. Executing the computing-intensive applications consume lots of power at the mobile device. The advances in EdgeC have made it possible to provide infrastructure, platform, and software as a service for the end-users from any computer with a fixed or wireless Internet connection. EdgeC can extend such services to mobile devices. Since there are several billions of mobile subscribers world-wide, EdgeC has the potential to have far-reaching impacts in the wireless industry and in our society. The delivery of demanding applications (e.g. streaming, augmented reality, on-line gaming etc) to/from the cloud to the mobile users relies on wireless networks (e.g., WiFi, 3G, 4G, 5G etc) for data and control between the cloud and mobile devices. Compared with fixed networks, wireless networks have limited bandwidth, latency due to network congestion, and connectivity. Moreover, under the presence of more mobile devices, the bandwidth available to each device will be further reduced, and network latency can go up and response time for mobile users can be higher. The main objectives of this paper are to present use case scenarios associated with Edge Cloud Computing, describe the latest advances in different standardization fora related to Edge Cloud Computing, discuss future research challenges. In remainder of this paper, section “Motivation” describes the application scenarios and motivation; section “Edge Cloud Computing Standardization and Fora” describes different approaches for Edge Cloud computing and section “Comparative Analysis of Existing Frameworks” describes the classification and comparison of existing frameworks. The section “Open issues and challenges” presents the open research challenges and issues and paper is finally concluded in section “Conclusion”.

Motivation

As an effect, the initial objective of EdgeC is to adapt cloud computing to the mobile environment in anywhere and anytime manner, where data are stored and processed outside mobile devices [8, 9]. Some of the most critical issues related to EdgeC include: network latency and limited network bandwidth and user mobility. Despite the advances in smartphones, they still have limited processing capability and limited battery life, especially with the growing demand for energy-hungry applications, such as video streaming and 3D gaming. In Ref. [10] described MEC as an emerging paradigm that provides computing, storage and networking resources within the edge of mobile Radio Access Network (RAN). The preparation for deployment of 5G network and tactile Internet sparked conversations about issues that need to be solved to increase the QoE of applications based on this platform. These applications require low latency and real-time data to effectively utilize its functionalities. Research done by [11] observed that the existing cloud infrastructure cannot resolve this issue. In Ref. [12] explained the key issue mobile edge computing aims to solve is to reduce the network bandwidth and latency in other to improve QoE. This would be done by bringing cloud infrastructure closer to the user. In Ref. [13] demonstrated that deploying cloudlets in close proximity with the end user improves the execution of latency-critical applications.

The trend of pushing cloud computing to the edge of mobile networks are expected to continue to accelerate in years to come. According to [10] the challenges and open issues associated with MEC includes data interoperability, resource management, and orchestration, service discovery and security.

This section present scenarios are highlighted in the following section where MEC can be beneficial in terms of performance improvements [5].

Augmented Reality (AR)

Augmented reality (AR) merges the view of real world and computer generated sensory inputs such as graphics, GPS data, sound and video [5]. AR allows the user to see the real world, with virtual objects superimposed upon or composited with the real world so that the information about the surrounding real world of the user becomes interactive and digitally manipulable. EdgeC can be used for generation of rendering. Required processing can be performed on EdgeC instead of the main server due to requirement of high processing speed and low latency.

Connected vehicles

The number of connected vehicles has been increased to support Vehicle-to-everything (V2X) communication, e.g. inform vehicles about road conditions through image/video analysis route prediction, collision warning applications such as safety, infotainment and communication or any other information that may affect the vehicle. Furthermore, the use of Roadside Units is intended to increase efficiency, and convenience of the V2X applications [14]. As the number of connected vehicles increases and use cases evolve, the volume of data will continue to increase along with the need to minimize latency and optimize QoE. EdgeC can be very useful to push V2X applications, data, and services from central cloud to the edge of network (e.g. Roadside units), this would help in bringing data and analytics applications closer to the vehicles at the roadside units, enabling applications acceleration over the vehicles [15]. The Mobile Edge Computing application can operate as a highly distributed roadside unit to support vehicle-to-everything (V2X) communication. Thus helps in sending the useful information to the nearby cars without any delay. This Instant communication can help drivers to react in timely fashion in order to avoid accidents and improve road safety.

Internet of Things (IoT)

IoT is a network that connects physical devices, sensors, vehicles and everyday electronic objects embedded with software, actuators and sensors to collect and exchange data, but also goes beyond this to include connections and networking between transport services, community services and much more of societies infrastructure [16]. The IoT is the latest technology and it is as important as the Internet. It is a network that connects all things to the Internet for exchanging information and communication through devices with agreed protocols by identifying, locating, monitoring and managing things [17]. In other words, the Internet is no longer bound by the desktop, but goes out into the world of other things [16]. The enormous amounts of data generated by this process would be best stored on a cloud. Moving IoT application data to the cloud can reduce the cost and complexity that relates to hardware management [18]. There is a need to aggregate various IoT device messages using mobile cloud computing closer to the device users to improve latency and response time. Various devices are connected over different forms of connectivity, such as 3G, 4G, 5G, Wi-Fi or other radio technologies [19]. In general, the messages are small, encrypted and come in different forms of protocols (e.g. MQTT, CoAP etc). There is a need for a low latency aggregation point to manage the various protocols, distribution of messages and for the processing of analytics from data collected from different IoT deployments [20]. The EdgeC server provides the capability to resolve these challenges.

Edge cloud media optimization

The distributed Edge Clouds have been designed and developed to support the media services across heterogeneous wireless and converged networks. The EdgeC provides support to the immersive applications to handle challenges such as user mobility and scarce network resources. It also helps in developing cloud-based workflow management for media applications, intelligently serving the end users through the available communication capacity and end-user device capabilities. This necessitates carrying media related functionalities such as rate adaptation/transcoding, rendering and caching as shown in Fig. 1.

Fig. 1
figure 1

Edge cloud media optimization

Full size image

This use case aims to optimize QoE for video applications over radio access network. This can be accomplished by estimating throughput at the radio downlink interface from radio analytics information. EdgeC can be used to enhance QoE for the users by to adopting a video using application-level coding (e.g. transcoding, rate control) to matches the estimated capacity at the radio downlink [21].

The adoption of Edge Cloud could be adopted by network operators either at the access networks (e.g. evolved Node B (eNB), Wireless APs) or at the aggregation points that are interconnected to the core networks via backhauling. A major challenge is that the user mobility may affect the entire operation when he/she is associated in an AP where the network operator has not deployed. In this case, the operator may seek for on-the-fly computing resources by requesting the available computing resources in an on-demand fashion from third parties. Such third parties could be any foreign cloud provider with enough/available computing resources that could be ‘rented’ on demand by the network operator. This necessitates the establishment of an agreement between the involved parties through a federation scheme. An immense volume of resources possibly with different specifications need to be managed under a unified and federated framework in terms of physical nodes and their accompanying physical and virtual resources. Once the requested computing resources are transferred to the network operator, another task is to manage computing resources. Due to mobility, the user may be associated (using handover management) to an area where neither the AP nor the aggregated node has EdgeC resources. In this case, the computing resources that will be requested by the third party can be established. After this establishment, cloud computing resources must be transferred from the old EdgeC to the new one. This scenario is illustrated in the Fig. 2.

Fig. 2
figure 2

Distributed cloud federation and service brokerage model

Full size image

Edge cloud computing standardization and Fora

In this section, some relevant approaches presenting similar concept are comprehensively elaborated. These approaches are broadly categorized into (1) MEC based approaches (2) Cloudlets based approaches and (3) Open Fog Consortium.

MEC approach

ETSI introduced Mobile Edge Computing (MEC) in ETSI [3] which is designed to push resources closer to the radio access networks in 4G and 5G. It brings cloud-computing capabilities and IT service environment at the edge of the mobile network. This environment is characterized by ultra-low latency and high bandwidth as well as real-time access to radio network information that can be leveraged by applications. Since 2017, the ETSI MEC industry group has renamed “Mobile Edge Computing” to “Multi-Access Edge Computing” to better reflect the growing interest in MEC from non-cellular operators. MEC has the aim to reduce network stress by moving resources from cloud to mobile edge [22, 23]. Fully virtualized MEC infrastructure is proposed in [23]. A distributed computation offloading algorithm is presented in [24]. SEcS (Scalable Edge computing Services) framework is presented to build and deploy Edge computing Services to address the challenge of scalability, high availability, fault tolerance and robustness [25]. Multi-access MEC architecture is designed to addresses latency and bandwidth issues for the video analytics location services, Internet-of-Things (IoT), augmented reality, optimized local content distribution and data caching and many other use cases and application scenarios for Smart Cities, Healthcare, Disaster Management and Smart farming. A scheme is proposed in [26] to deal with unpredictability of computation availability at the edge, where task execution performed on idle edge resources. In [27], it argues that autonomic computing techniques are fundamental element for dynamic management of edge servers. MEC architecture is proposed in [28] to reduce latency. To migrate running application from VM or container for mobile edge cloud environment, a layered solution is proposed in [29]. A WiCloud is proposed in [30] that is based on NFV/SDN concepts to provide edge networking. Some frameworks are given in [31] for mobile application execution in MCC and their comparative study are also given. Seamless application execution frameworks in MCC are also highlighted in [32] with detailed comparisons and analysis.

Cloudlets based approach

The term “cloudlet” was coined by researcher at Carnegie Mellon University, where its prototype is developed as part of a research project [33]. The Cloudlets are designed to support applications for mobile devices those are resource hungry and interactive e.g. Augmented reality applications, Cloud games, Wearable cognitive assistance system Google Glass, Apple Siri and Google Now and many other applications those require offloading of resource intensive task from cloud to the mobile device to achieve the required quality of experience. This helps in reducing communication latency and perform faster execution for application intends to perform resource intensive tasks. The main motivation of cloudlet comes from the Internet community to handle the resource constraint on the mobile devices.

A cloudlet represents the middle tier of a 3-tier hierarchy i.e. Mobile device, Cloudlet, Cloud. Cloudlets can be considered as a local data centre in a box to enable localized cloud services, offer high performance and faster access to cloud resources by multiple users simultaneously [34]. Moreover, it deals with large WAN latency, less bandwidth, and high utilization cost issues [34]. Cloudlet, through the interest of key industrial players (e.g. Nokia, Intel, Vodafone) have formed the open source banner of Open Edge Computing (OEC) Initiative. OEC has offered cloudlets open-source code APIs as an extension to OpenStack to promote cloudlet as an enabling technology [35]. The main goal is to, engage with wider IT and Telecoms industry to Synchronize the work with other efforts includes ETSI ISG MEC and OPNFV. The cloudlet pioneering Elijah project at Carnegie Mellon University has been extended to OpenStack++: to provide a cloudlet library based on a modified QEMU with integration into the OpenStack platform. A mesh cloud architecture is proposed in [34], which is composed of cloudlet, Internet cloud and wireless mesh networks. An experimental framework is designed in [36], in which private cloudlet and wireless mesh network is implemented. It is capable of establishing and maintaining mesh connectivity among multiple nodes automatically and is featured with adaptivity and self-recovery in case of network failures.

Cloudlet architecture presented in [37], manages applications at the component level. Cloudlet based MCC system is introduced in [38] for reduction of power consumption and network delay. A Performance Enhancement Framework for Cloudlet (PEFC) is proposed for MCC [39] to improve the cloudlet performance. Centralized cloudlet architecture is proposed in [40]. In [37], a new cloudlet architecture is proposed where applications are dealt on a component level where components are distributed among dynamic cloudlets letting users to join and leave cloudlets at runtime. However, cloudlet performance relies upon user mobility [41]. In [42], two migration models have been compared cloudlet network design i.e. VM bulk migration and VM live migration. In order to access discoverable cloudlet server for mobile users for resource provision and services on demand, a cloudlet system is proposed in [43]. These cloudlets may be deployed at various public places where users can connect cloudlet through a mobile network provider [43].

Another cloudlet based system is proposed in [39], with focus on performance improvement in mobile cloud computing. Cloudlet is installed along with AP to allow mobile devices to access it. These mobile devices connect to nearby cloudlet using Wi-Fi [38]. To minimize, delay and power costs of mobile user, cloudlet infrastructure is proposed in [44]. In [45], an energy management approach is introduced for mobile/pocket cloudlet. Researchers and Marine Corps are working together on the concept of “tactical cloudlet” to implement distributed cloud computing concept in a remote and mobile battlefield scenario, especially in a more hostile environments e.g. during a war mission or disaster recovery where the requirements for communication changes quickly and requires higher power for computing [46]. Tactical cloudlets are proposed in [47] to support tactical edge and cyber-foraging where resource intensive tasks are offloaded to cloudlets. A strategy is proposed in [48], to reduce multi-resource allocation problem between cloudlet and mobile devices that will enhance Quality of Service (QoS).

Open fog consortium

Fog Computing is a concept introduced by Cisco in 2011 to meet the demands from different segments of Internet of Things (IoT), Internet of Everything (IoE) or Internet of Me (IoM) start to take off, e.g., consumer, wearable, industrial, enterprise, automobile, healthcare, building, energy. Classical cloud computing paradigm can hardly satisfy low latency, mobility support and location awareness. To address these problem, fog computing paradigm is introduced which improves quality of services (QoS) for real time applications and streaming, provides low latency and location awareness [49] in the field of wireless sensor networks, industrial automation and transportation systems. The main motivation is to alleviate the disadvantages of cloud computing: Long WAN latencies is a big obstacle in the critical path of user interaction and can deteriorate usability, traffic to central cloud increases computational and network overhead at central cloud. Fog computing introduces decentralized computing infrastructures so that computing resources and applications services are distributed in the most logical, efficient places, at any point along the continuum from the data source to the cloud. The main emphasis of the open fog consortium is to define a system-level horizontal architecture that distributes resources and services of computing, storage, control and networking anywhere along the continuum from Cloud to Things [50]. It’s put data close to the end user [51] which reduce latency and improve QoS [52]. It also enables localization, context awareness and mobility support [49]. The Decoy Information techniques are used to detect malicious attacks those cannot be addressed using traditional security measures such an attack by an insider by seeding data into a system which appears genuine but actually it is fact spurious. Using Decoy information technology, you can implement security in fog computing [52]. Fog provide high quality streaming through access points and proxies to mobile nodes including moving vehicles [53]. It is suitable for those applications that require predictable and low latency such as video conferencing and gaming [54]. Fog architecture is given in [55] and radio access network (F-RAN) based fog is presented in [56].

In fog computing, cloud resources such as compute and storage etc. are migrating to the edge of the network where routers themselves may become the virtualized infrastructure [8] and services can be hosted at end devices such as set-top-boxes or access points [49]. In addition, multiple heterogeneous decentralized and ubiquitous devices communicate and cooperate with each other and can perform processing and storage tasks using network without the interference of third-parties [8]. It provides highly virtualized platform that offers storage, computing and networking services between the main cloud data centers and end devices [9]. It supports multiple services and applications where low latency is required. Fog/ edge nodes have sufficient computing power to facilitate user’s task that are received from their end devices. This edge computing concept is introduced within cloud to reduce end-to-end response time between multiple devices. Although cloud computing provides lot of benefits to users in terms of cost reduction, system administrative tasks eliminations, flexibility increase, and improve reliability etc. but it also suffers some limitations including unpredictable network latencies and security issues etc. To overcome these limitations, fog computing is introduced where cloud system is located at the edge of network [57]. Fog computing will be helpful for emerging network paradigm which requires faster processing with less delay [57]. It is able to provide high quality streaming to mobile users through access points or proxies [53]. It is suitable for video streaming, gaming and augmented reality where low latency is required [53]. Fog computing not only reduces latency but also improves the QoS [51]. In fog computing paradigm, data is distributed and moved closer to the end-user and also support for data streaming and mobile computing [52]. Fog is considered to address services and applications that not well fit in cloud, e.g. video conferencing and gaming applications that need predictable and low latency, fast mobile applications, smart grid and smart traffic light system etc. [54]. In short, the aim of fog computing is to place cloud resources, close to mobile users [55]. A FSDN is proposed in [58], which combines the Software Defined Networking (SDN) and Fog computing.

ETSI-MEC consortium is developed to unite the IT Cloud and Telecommunication industry on MEC standards to providing IT and cloud-computing capabilities within the RAN through Mobile Orchestrator APIs for provisioning and monitoring virtual resources, targeting especially network function visualizations. Considering the overlapping interests in MEC and Cloudlets, a few on the other hand, Cloudlet/OEC have been motivated by the Internet community to optimize Internet demanding applications over resource-constrained mobile devices. Fog computing is mainly driven by IoT and the need for data processing and interoperability at the edge. All these three approaches presented have been compared in terms of different quality parameters in [35] are presented in Table 1.

Table 1 Comparison of cloudlets, fog and MEC approaches [35]
Full size table

Comparative analysis of existing frameworks

We have compared existing frameworks on the basis of various properties. Caching is used to store data locally to reduce the delay [32]. In case of cloudlet, it improves the latency by minimizing delay. Mirroring is also used to cache data at the mirror during uploading and downloading which also reduce the delay [59]. It reduces the operational overhead and optimizes response time but it increases the cloud storage cost [32]. Parallel execution improves the execution time of an application but it increases power consumption and hardware cost [32]. Pre-installations improves runtime data transmission but it increases the cloud resource consumption and maintenance overhead [32]. The optimize VM migration enables migration for only relevant applications instead of whole VM migration which reduces transfer overhead and improves the transmission time [32]. Fault tolerance provides a transparent mechanism to failure detection which requires a continuous monitoring but can create high complexity [32]. The reduction in the number of hop distance results in improved latency, jitter and response time. CloneCloud, a flexible application partitioner is proposed in [60]. It automatically distributes the computation tasks from single mobile device to multiple machines. It significantly improves task processing and reduce the energy of smart mobile devices. Although it provides optimal execution time for computation environment but it increases the data transfer overhead on multiple machines. A framework is proposed in [61], to perform the optimal dynamic partitioning and execution of applications. It provides high performance with low operational cost but it also increases the data transfer overhead. Another solution is proposed in [62], for dynamic adaptive deployment of applications to enhance the quality of service. It offers optimal deployment of applications but it depends on nearby servers. Hyrax, a platform to support mobile devices is derived from MapReduce [63] and provide infrastructure for mobile computing. It improves utilization of mobile resource but execution of MapReduce jobs on mobile phones results in high overhead for devices with limited resources. The work presented in [64] offers infrastructure deployment through CloneCloud architecture for smartphones applications to boost the mobile applications via cloning by using multiple computing platforms. It overcomes the limitations of mobile resources and the clone can be used as a recovery processing but it increases computation transformation overhead. The work presented in [65] provides highly dynamic and energy saving solution and is optimal for latency sensitive applications but has high profiling overhead. VM based cloudlets with one-hop access to improve the response time of applications is presented in [66]. Two types of algorithms, ALL and K-step are proposed in [67] to improve the static and dynamic partitioning of cloud applications. It provides an optimal and transparent solution for distribution of different application modules and significantly improves the performance of cloud applications but it is not highly flexible yet. A framework is proposed in [68], to execute the mobile applications on the cloud virtualization environment where the user can control the deployment and execution of the application. Cloudlet Aided Cooperative Terminals Service Environment (CACTSE) is proposed in [69] for mobile content delivery service where Mobile terminals are connected with each other via Service Manager (SM) which acts like a cloudlet module to improve the user experience. Cloudlet based dictionary for mobile devices is proposed in [70] with support for translation of 6 languages. It is easily configurable and extensible but requires high processing power for fast computation. The work presented in [37], offers a dynamic cloudlets concepts. A virtual mobile cloud computing provider proposed in [71] is a resource friendly architecture. To reduce the computational workload on smartphones, mirroring approach is proposed in [59] that takes a mirror against each smartphone and virtually expand smartphones resources. COMET (Code Offload by Migrating Execution Transparently), a runtime offloading environment towards augmenting smartphones is proposed in [72] to improve computation speed but it consumes more bandwidth. A framework is proposed in [73], to support seamless mobile cloud applications execution that significantly reduces latency and power consumption. Cuckoo, a dynamic runtime system for computation offloading [74] is suitable for compute intensive operations. MOCHA (Mobile Cloud Hybrid Architecture) with mobile-cloudlet-cloud architecture is proposed in [75] for real time face recognition that gives the minimum response time. AIOLOS, a mobile middleware is proposed in [76] which improves the mobile application performance via cyber foraging and optimize execution time and energy consumption. To enable the seamless and transparent usage of cloud resources, an elastic application platform is proposed in [77] that will augment the computing capabilities of mobile devices and provides elasticity between cloud and resource constrained devices. ThinkAir is an ondemand resource allocation framework with dynamic scaling [78] where users can migrate mobile applications to the cloud and it optimizes execution time and energy consumption. Pocket Cloudlets is proposed in [79] that replicates the search and advertisement based on personalized user behaviour and improve mobile user experience. Misco, a MapReduce framework is proposed in [80] for mobile devices. It supports any device with network connectivity and support for python. XMPP-based architecture is proposed for dynamic partitioning of mobile applications deployment between cloud and mobile devices and it offers flexible and extensible architecture [81]. Mobile Augmentation Cloud Services (MACS) middleware is presented in [82] which enables adaptive application partitioning of Android services and computation offloading. It reduces local execution time. A lightweight secure cyber foraging is implemented in [83] which are useful for resource, constrained devices. It enables new applications without a new hardware investment. Cloudlet based network is proposed in [84], It considers the impact of cloudlet in interactive mobile cloud computing applications and reduces data transfer delay. Later, further comparisons of existing frameworks based on different parameters are given in Tables 2, 3, 4, 5.

Table 2 Comparison of existing frameworks part-1
Full size table
Table 3 Comparison of existing frameworks part-2
Full size table
Table 4 Comparison of existing frameworks part-3
Full size table
Table 5 Comparison of existing frameworks part-4
Full size table

Open issues and challenges

In this section, some issues and challenges are highlighted that are provided direction to researchers for further research in this area.

Standard protocol

MEC being a recent technology is evolving through the phases of implementation and requires standardization emanating from collaboration of industry and researchers over an agreed platform [85].

Efficient deployment

Minimizing the latencies through optimal utilization of bandwidth may be achieved with efficient deployment of MEC. However, it is difficult to optimize the spectrum usage with dependence on complex system components.

User mobility and transparency

Provision of uninterrupted services to a frequently “on-the-move” client is another challenge in MEC environment with transparent process migration and platform heterogeneity.

Heterogeneity and scalability

As edge devices uses different access technologies including 3G, 4G, 5G, Wi-Fi and Wi-Max so aspect of heterogeneity should be catered in smooth functioning of MEC operations. This further necessitates the provision of scalability for different platforms with varying number of users [60, 62, 65, 67, 68, 71].

Availability and security

The availability of resources is mostly dependent upon server capacity and wireless access medium for ensuring constant service delivery. Along availability, security of data and applications from any intruder should be catered with physical measures.

Fog-cloud interworking

When considering connectivity challenges for Gateways and/or Fog nodes, there are three different aspects to consider in any end-to-end system:

  • - Northbound connections, which are the connections between Gateways/Fog nodes and a Cloud service (public or private).

  • - Southbound connections, which are the connections between the Gateway/Fog node and the Edge devices/things/sensor networks.

  • - East/West connections, which are the connections between Gateways/Fog nodes themselves, so that they can share data without requiring, Cloud connectivity.

Data management

The data management capabilities required include (but are not limited to):

  • - Data normalization, which is ingesting, aligning and enriching the data from different sources (Things, devices and sensors) into a common data model with well understood semantics.

  • - Filtering and querying data, so that applications and analytics can efficiently access and use the data relevant to them.

  • - Integration with Edge analytics, because the whole reason for capturing these data is to be able to analyze them, create new actionable insights, make decisions and put those decisions into action. Transforming data into different representations and formats, for the purposes of integrating with the IoT ecosystem.

  • - Aggregating data and/or abstract meta-data, as preparation for local analytics or pushing it to Cloud services.

Conclusion

The paper presents a comprehensive review of the prevalent MEC frameworks along with a comparative analysis of contemporary approaches with respects to different performance parameters. Comparative analysis employs different parameters such as such as system performance, network performance, overhead of deployment and system migration overhead to measure the degree of effectiveness of different approaches. Based on our thorough investigation, it can be asserted that MEC is a way forward for achieving 1 ms latency dream. Therefore, researcher has proposed several MEC architecture to reduce the latency. While considering the state-of-the-art presented in this paper, many areas are still open for further research to investigate a comprehensive architecture design with intelligent migration mechanism for multi-access mobile edge computing.