Anda di halaman 1dari 8

See

discussions, stats, and author profiles for this publication at: https://www.researchgate.net/publication/308767796

Mobile-Edge Computing Architecture: The role


of MEC in the Internet of Things.

Article October 2016


DOI: 10.1109/MCE.2016.2590118

CITATIONS READS

5 383

5 authors, including:

Fabio Giust
NEC Laboratories Europe
16 PUBLICATIONS 184 CITATIONS

SEE PROFILE

Some of the authors of this publication are also working on these related projects:

Open DMM View project

MEDIEVAL View project

All content following this page was uploaded by Fabio Giust on 11 November 2016.

The user has requested enhancement of the downloaded file. All in-text references underlined in blue are added to the original document
and are linked to publications on ResearchGate, letting you access and read them immediately.
Mobile Edge Computing Architecture
The role of MEC in the Internet of Things

Dario Sabella, Alessandro Vaillant Pekka Kuure, Uwe Rauschenbach Fabio Giust
TIM, Telecom Italia group, Nokia Networks NEC Laboratories Europe
Italy Finland, Germany Germany

AbstractMobile Edge Computing (MEC) is an emerging While 4G networks have been driven by the need to deliver
technology currently recognized as key enabler for 5G networks. video contents, the next years will also witness the explosion of
Being compatible with current 4G networks, MEC will address Machine-to-machine (M2M) connections [1] due to the
also many key use cases for 5G system, motivated by the massive increase of IoT traffic and services, that will be dominated by
diffusion of Internet of Things (IoT). This paper aims to give a several new vertical business segments [2], e.g. automotive and
tutorial on MEC technology and an overview of the MEC mobility, factories of the future (sometimes referred also as
framework and architecture recently defined by ETSI MEC ISG Industry 4.0), healthcare, media and entertainment, energy.
standardization group. We provide some examples of MEC
deployment, with special reference to IoT use cases, since With this view, the emerging scenario (depicted in Fig. 1)
Internet of Things is recognized as a main driver for 5G. Finally will be characterized by heterogeneous terminals and devices,
we discuss main benefits and challenges for MEC toward 5G. and also contents and traffic types (including legacy voice and
data traffics, but also those generated by emerging M2M
Keywords 5G, Mobile Edge Computing, MEC, IoT connections), all with different Quality-of-Experience (QoE)
requirements. In this 5G scenario, both research projects and
I. INTRODUCTION standardization bodies are currently considering MEC with
The path toward defining 5G systems encompasses all the increasing attention, especially as a key enabler for new
requirements of the communication network to cope with emerging use cases that will need to be properly managed at
traffic needs, so as to allow operators to offer services and the edge of the network.
provide contents efficiently and profitably.

Fig. 1. Mobile Edge Computing and the reference 5G scenario

MEC technology, recently introduced by ETSI Industry and data centers close to the radio network (e.g. located at
Specification Group (ISG) on Mobile Edge Computing (MEC) aggregation points). Operators can open their RAN edge to
[3] (i.e. ETSI MEC ISG), offers cloud-computing capabilities authorized third-parties, allowing them to deploy innovative
within the RAN and an IT service environment at the edge of applications and services towards mobile subscribers,
the mobile network, close to mobile subscribers. This enterprises and vertical segments, flexibly and rapidly. MEC
environment is characterized by ultra-low latency, high will bring significant benefits not only for Operators but also
bandwidth, and real-time access to radio network information third parties and OTT (Over-The-Top) companies that will
that can be leveraged by applications and QoE optimization have the opportunity to run their applications at the edge of the
platforms. Edge may refer to both the base stations mobile network, close to mobile subscribers (with related new
themselves (e.g. eNodeB, Radio Network Controller, etc), business opportunities). Finally, also to the common consumer
will gain the possibility to experience improved performances
and new services offered by the MEC system.
The content of this paper reflects the work done by the
authors as members of the ETSI MEC ISG and their own
expertise gained in the field of Mobile Edge Computing. The
aim of the present paper is thus to provide an (hopefully useful)
overview of MEC framework and architecture (section 2) as
they have been currently introduced by ETSI, together with a
description of some selected MEC use cases especially relevant
for IoT (in section 3). Then we will give some examples of
MEC deployment in section 4 and discuss in section 5 the main
benefits and challenges for MEC in the view of future 5G
systems. Finally section 6 will conclude the paper.

II. MEC FRAMEWORK AND ARCHITECTURE


ETSI MEC ISG was launched in December 2014 and
tasked to produce a set of specifications to enable hosting of
3rd party provided applications in a multi-vendor environment.
Ever since, the ISG has been working on specifications starting
from the use cases to define the requirements and followed by
the definitions for the architecture. The work has been tasked to Fig. 2. Mobile Edge Computing framework
last for 2 years the ISG MEC has already published the
foundation specifications on technical requirements and B. MEC reference architecture
reference architecture. The ISG has proceeded to next stage to
More thorough understanding on mobile edge system can
specify the Application enablement platform, the mobile edge
be obtained from the reference architecture (depicted in Fig. 3
services and the needed APIs that the mobile edge applications
below), which defines the functional entities in more detail
can use to provide a whole new range of services with
with their relations to each other. The reference architecture
enhanced end user experience.
has the same split to system level and host level as the
The work on architecture has thus been finalized and the framework. The network level is not visible in the reference
ISG has defined the framework and reference architecture architecture as there are no Mobile Edge Computing specific
[7] for MEC, as described in the following. reference points needed to access those entities.
The Mobile edge host (ME host) is an entity consisting of
A. MEC framework mobile edge platform and the virtualization infrastructure that
The Mobile Edge Computing framework, as presented in provides compute, storage and network resources for the
Fig. 2, shows the high level functional entities that are mobile edge applications. In addition, ME host can provide
involved. The entities are further grouped in the system level, persistent storage and time of day information for the
host level and the network level entities. applications. The virtualization infrastructure includes a data
Mobile edge host level consists of the mobile edge host (i.e. plane that executes the forwarding rules received by the mobile
ME host) and the corresponding mobile edge host level edge platform and routes the traffic between the applications,
management entity. The ME host is further split to include the services and the networks.
mobile edge platform, the mobile edge applications and the Mobile edge platform (ME platform) represents a
virtualization infrastructure. collection of baseline functionalities that are required to run
The networks level consists of related external entities that applications on a particular ME host and to enable mobile edge
are the 3GPP cellular network, the local networks and the applications to discover, advertise offer and consume the ME
external networks. This layer represents the connectivity to services. Mobile edge services can be provided by the platform
local area networks, cellular networks and to external networks and by the applications and both the platform and applications
such as Internet. may consume ME services. The essential baseline
functionalities of ME platform are needed to steer the traffic
On top of everything is the mobile edge system level between the applications, services and networks. The ME
management which by definition has the overall visibility to platform receives the traffic forwarding rules from the mobile
the whole mobile edge system. The mobile edge system edge platform manager, mobile edge applications and ME
consists of the ME hosts and the mobile edge management services and, based on those as well as on policies, it provides
necessary to run mobile edge applications within an operator the instructions to the forwarding plane. In addition, the ME
network or a subset of an operator network. platform supports configuring the local DNS proxy/server,
which can be used to direct the user traffic to desired mobile
edge applications. ME platform can communicate with other
ME platforms over Mp3 reference point, which is intended for
control plane procedures. Using this interface several platforms information on the whole ME system as it knows all the
may be grouped together and can form a communications grid. deployed ME hosts, the services and resources available in
each host, the applications that are instantiated and the
Mobile edge applications (ME applications) are running as topology of the network. The orchestrator is also responsible of
virtual machines on top of virtualization infrastructure provided managing the ME applications and the related procedures by
by the ME host. The applications interact with the ME platform supporting on-boarding the applications, checking the integrity
over Mp1 reference point to consume the services offered by and authenticity of the application, validating the policies for
the platform. Applications can also offer to provide services to the applications and maintaining a catalog of the applications
the platform which can further provide those to other that are available. The MEO also prepares the instantiation
applications. Mp1 reference point is also used for additional procedures by providing instructions to virtualization
support procedures such as to indicate the application infrastructure managers how to treat the applications. The ME
availability or to prepare to relocate the application-state for the applications may indicate their requirements e.g. for the
user in case of handover events. ME applications may indicate resources, services, location and performance, such as
requirements on their needed resources or services, and in maximum allowed latency, and it is the MEO whose
addition indicate their constraints on maximum allowed responsibility is to ensure that the requirements are met. The
latencies. These requirements are validated in the system level
orchestrator uses the requirements received from the
and the selection of target mobile edge host(s) is performed applications in the selection process for the target ME host. In
based on the requirements. case that application needs to be relocated, the MEO is the
entity that triggers the procedure. The orchestrator has a
reference point with the Operations Support Systems (OSS)
that is intended for triggering the instantiation and termination
of mobile edge applications in the ME systems. The reference
point towards VIM is used to manage the virtualized resources
of the ME host and to manage the application images that are
provided for instantiation. It is further used for maintaining
status information on available resources. Operations Support
System (OSS) of an operator is a function that is widely used to
manage various services and subsystems in the operators
network. From ME system point of view, the OSS is the
highest level management system to assist in getting the mobile
edge applications running in the desired location of the
network. OSS receives requests to instantiate and terminate the
mobile edge applications from the Customer Facing Service
portal and from the clients in the user equipment. As being on
Fig. 3. Mobile Edge Computing reference architecture
the boundary between the external world and operators
Mobile edge platform manager (MEPM) is a host level network, the OSS checks the integrity and authenticity of the
entity which is further split into mobile edge platform element application package and authorizes the request. The requests
management, Mobile edge application lifecycle management that are granted by the OSS are forwarded further to MEO for
and mobile edge application rules and requirements further processing. OSS can also have the capabilities to
management functions. The application lifecycle management relocate the applications between different cloud systems.
consists of application instantiation and termination procedures The Customer Facing Service portal (CFS) acts as an
as well as providing indication to mobile edge orchestrator on entry point for the 3rd parties. This portal can be used for
application related events. The rules and requirements operations to manage the provisioning, selection and ordering
management includes authorizations, traffic rules, DNS of the mobile edge applications. Developer parties can use the
configurations and resolving issues when set of rules are in portal to make their created ME applications available in the
conflict. The reference point between the ME platform and the operators ME system. Other customers such as enterprise
MEPM is used to configure the platform and the rules, to clients may use the portal to select the applications that are of
provision the traffic filtering rules, to manage the application interest for them and to provide instructions when and where
relocation and to support the lifecycle procedures of they wish to use the selected application. The CFS portal can
applications. The reference point towards the OSS is used for also provide business related information for customers for
the fault-, configuration and performance management of the example related to SLA or billing. CFS is connected to OSS
ME platform. The reference point between the mobile edge over the reference point between the entities.
orchestrator and the MEPM provides support for application
lifecycle management, application-related policies and to The User application lifecycle management proxy (User
maintain up to date information on available ME services in the app LCM proxy) is a function that the mobile edge related
ME system. clients and applications use to request services related to on-
boarding, instantiation and termination of the applications.
Mobile edge orchestrator (MEO) is the central function in Further, this proxy can be used to request to relocate the
the ME system as it has the visibility over the resources and application out from the ME system to the external cloud or in
capabilities of the entire mobile edge network. MEO maintains to the ME system from the external cloud. The access portal
authorizes all the requests prior proceeding with forwarding (person, specific object), create rules for observation areas of
actions towards the OSS or the MEO. The User app LCM interest, define and use event based rules (entering/exiting
proxy can be only accessed from the mobile network. It area, leaving/removing object, loitering) and counting objects
exposes a reference point towards the applications and the (number of people, objects). The analytics can be further
clients in the user equipment. enhanced by sound analytics and additional information from
The Virtualization Infrastructure Manager (VIM) is external sources and sensors. MEC enables automated,
responsible of managing the virtualized resources for the flexible, scalable and cost-efficient solution for security.
mobile edge applications. The management tasks consist of Analytics function can provide flexible extensions to 3rd
allocating and releasing virtualized compute, storage and parties through plug-in integration. The solution is flexible to
network resources provided by the virtualization infrastructure. deploy by enabling the video processing and analytics
VIM also prepares the virtualization infrastructure to run application running at optimum location based on technical
software images and the software images can be also stored by and business parameters.
VIM for faster application instantiation procedure. As
virtualized resources may also run out of capacity or fail in
operation, it is important to monitor those. VIM provides B. Use case: Vehicle-to-Infrastructure communication
support for fault and performance monitoring by collecting and Digitalization of the services is progressing with enormous
reporting information on virtualized resources and providing speed and automotive sector is one area where the new
the information further to server and system level management technologies are shaping the whole industry. Self-driving cars
entities. VIM has a reference point towards the Virtualization have been already demonstrated by both traditional
Infrastructure to manage the virtualized resources. The automotive and new internet players and it is anticipated to
reference point between the MEO and VIM is used for have the first autonomous cars commercially available by
management of the application images and the virtualized 2020. The work on future 5G system is being currently
resources as well as for monitoring the availability of the conducted by various organizations globally and the
resources. The reference point between MEPM and VIM is
digitalization in the automotive industry is clearly reflected in
used to manage the virtualized resources for the mobile edge
the use cases and the requirements. IoT is a key driver for the
applications during their lifecycle.
next generation technology and the most of the use cases
appear to focus on connected cars.
III. KEY USE CASES FOR MOBILE EDGE COMPUTING AND Connected cars is not only about self-driving capability, but
INTERNET OF THINGS (IOT) many other use cases exist. More in general, all use cases
As anticipated, the MEC ecosystem is likely to bring related to smart transportation are of course in strict relation
significant benefit not only for the Mobile Operator (e.g. with the already mentioned Internet of Things paradigm.
introducing QoE platforms and agile service provisioning) and These use cases are not only considered from a theoretical
third parties/OTT (for new business opportunities) but also to point, of view, but early experimental activities are already
the common consumer that, at the end, will be able to taking place in these years. One example is road safety
experience services that need to rely on very accurate service, where traffic alerts can be also used both by human
localization, or high performance in terms of latency and drivers and autonomous cars. Traffic alert service has been
available throughput. In other words MEC will be able to demonstrated in Germany at Digital A9 Motorway test bed1
provide in advance new IoT services that would be not where the live LTE network from Deutsche Telekom was used
technically/nor economically feasible before the launch of 5G- to carry alert messages between vehicles in the same area. The
like networks (possibly playing the role of an vanguard player exercise was enabled by MEC solution to achieve below 20
for the exploration of tomorrows services). ms latencies vehicle-to-vehicle via the cellular infrastructure.
Several use cases are addressed by MEC, and also currently With the next generation system the latency requirements are
considered in NGMN and 3GPP [5] toward 5G networks. The set to 1 ms range to allow wide range of use cases. MEC is the
following part describes a selection of use cases identified by ideal solution and has been identified as a key component to
ETSI MEC ISG [6], and relevant for IoT scenarios. support these ultra-low latency scenarios as it enables hosting
applications close to the users at the edge cloud and therefore
A. Use case: Security, safety, data analytics
providing the shortest path between the applications.
Security and safety has become one of the most important
verticals for IoT. The developments in technology with ever C. Use case: Computation offload into the edge cloud
increasing amount of data from sensors and high resolution Applications running on mobile terminals may want to offload
video cameras create the need for scalable, flexible and cost- parts of the computations into the cloud for various reasons,
economic solution to analyze the content in real time. MEC such as availability of more computing power or of specific
can host the analytics applications close to the source and hardware capabilities, reliability, joint use of the resources in
enable increased reliability, better performance and significant collaborative applications, or saving bitrate on the air
savings by processing huge amounts of data locally. Enhanced interface. The computation offload is particularly suitable for
video analytics enables creating and using rules for different IoT applications and scenarios where terminals have limited
events to trigger alerts and forwarding actions. Real time
video analysis can be used to identify and classify objects 1
https://www.telekom.com/media/company/293064
computing capabilities, i.e. in those cases where M2M devices above use case is further developed in the following and
have severe low power requirements, in order to guarantee illustrated in Fig. 4.
high batteries lifetime. Such offload may happen statically
(server components are deployed by the service provider
proactively in advance) or dynamically (server components
are deployed on demand by request from UE). Also in this use
case, applications benefit from low delay provided by MEC.
D. Requirements
In order to realize the MEC use cases (and in particular those Fig. 4. MEC-based video surveillance. S1-U deployment option.
listed above), a number of requirements need to be fulfilled by
a ME system, and have been identified [6]. Namely, a ME A local network of IoT sensor devices, e.g., video cameras,
system needs to provide the following capabilities: is connected to the broadband mobile network (e.g., an LTE
Route network traffic from and to applications that may network) through the local IoT gateway. The video streams are
inspect and modify it (authorization required), and conveyed to the ME host, where the IoT application for video
influence DNS resolution accordingly; surveillance is running. There, the real time video processing is
Provide up-to-date radio network information; carried out, so that, when an anomaly in the recorded video is
Allow ME applications to provide and consume ME detected, the IoT surveillance application sends a trigger to the
services, including service registration, service central station located in the Internet. This configuration
subscription and service announcement, and support the prevents to deploy costly dedicated equipment and connectivity
authorization per application to provide and consume infrastructure, by simply leveraging the radio access network
and ME system from the mobile network operator.
information and services;
Support bandwidth management;
B. MEC for IoT devices capabilities offload
Support user identity mapping;
Provide support for mobility procedures; Similarly to the one described above, many other scenarios
involve mainly static nodes, where mobility support is not a
Provide support for running a ME application in a place
primary need. Some examples embrace smart meters for water
that is optimal w.r.t. resource usage and delay figures; and electricity supply monitoring, sensors for home and
Provide a virtualization environment in order to run industrial automation, as well as others, that, even if they may
mobile edge applications; communicate using a wireless link, are installed in fixed
Allow instantiating a mobile edge application per request locations. Given the constrained capabilities of such devices,
from a handset (UE). the data processing entities and the controllers are deployed on
Note that not all MEC deployments have to fulfill all the the ME host and running as Mobile edge applications. By
requirements defined above. As a consequence, MEC leveraging the rich features offered by the Mobile edge
performances will be tailored on the specific deployment management system, such applications can be easily
scenario in order to meet the requirements of the different use instantiated, relocated and upgraded when necessary.
cases to be supported.
From the deployment perspective, the ME platform hosting
the IoT applications, described in this and in the previous
IV. HOW TO USE MEC FOR IOT USE CASES paragraph, may sit on an entity in the RAN (e.g., eNB, RNC),
A ME host is a privileged location to run applications with or on a RAN user plane interface (e.g., S1-U). In this
sensitive real-time requirement, given its proximity to where deployment option, the ME platform shall be able to divert data
relevant part data traffic is generated and delivered. This traffic from the standard RAN user plane to the Mobile edge
feature is foreseen to be hugely exploited in the context of the applications, without major impact on the rest of the mobile
IoT ecosystem, as By 2018, 40% of IoT-created data will be network elements. As an example, in an EPS-based mobile
stored, processed, analyzed, and acted upon close to, or at the network, the above deployment option would imply to re-route
edge, of the network [4]. A ME system enables IoT part of the GTP-encapsulated packets flowing through S1-U
applications to be installed in an operators radio access interface to the desired ME applications, as illustrated in Fig. 4.
premises, benefitting from broadband mobile radio access, as
well as from reduced latency. C. MEC for connected vehicles and moving IoT devices
Other relevant IoT use cases require the devices to connect
A. MEC in a IoT deployment for surveillance and safety to the broadband mobile network, and also to be able to move
The interplay between MEC and IoT concepts finds a across different cells with mobility and session continuity
straightforward application when it comes to use cases that support. This can be the case of IoT systems utilizing drones,
require intensive computational load, e.g., video surveillance road vehicles, and trains, just to mention a few. Under such
and object recognition. Compute-hungry algorithms for image circumstances, the MEC deployment option illustrated before
processing can leverage the ME hosts computing resources poses some additional challenges in terms of backward
and low communication delay to meet the overall latency compatibility with legacy mobile network entities. In fact,
budget imposed by real time automated surveillance. The mobility and session management is usually performed by the
core network functions, e.g., implemented by the Mobility other spectrum. In general the messages are small, encrypted
Management Entity (MME), the Serving Gateway (SGW) and and come in different forms of protocols.
the Serving GPRS Support Node (SGSN) in the current 3G/4G
networks. Bringing mobility support functions to the ME So what about MEC? As recognized by ETSI MEC can be
platform may have a dramatic impact on the existing regarded as a key technology and architectural concept for
architecture, as legacy components should include non- enabling the transformation towards 5G [3]. The mobile
standard mechanisms to interact with the ME platform to network edge environment can provide ultralow latency,
convey the appropriate control plane information. proximity, high bandwidth, realtime insight into radio network
and context information and location awareness enabling early
Nevertheless, the industry is currently looking with more 5G use cases. With regards to the IoT services scenario, MEC
interest at distributing gateways and core functions in the can play a relevant low latency aggregation point to manage
network edge. Present virtualized EPC solutions enable the various protocols, distribution of messages and for the
lightweight and tailored deployment of core network functions processing of analytics, combining in this way high
in proximity of the networks edge to support MEC-based IoT performance with availability of local computing, thus
systems. In such a deployment option, the ME platform sits on anticipating the 5G concept.
the user plane interface connecting the mobile network to the
rest of packet data networks, e.g., the SGi interface in the EPS On the other hand, there are coming challenges also
architecture (see Fig. 5). ME applications for IoT would not associated to the success of MEC in the framework of 5G.
require complex traffic filtering and manipulation in order to From this point of view, MEC standardization work is still at
receive the desired traffic, and the ME platform can leverage an early stage, and a tight coordination with ETSI NFV
on legacy network entities to carry out consistent control plane (Network Function Virtualization) is needed in order to ensure
operations, e.g., for mobility, as well as other crucial aspects harmonization of MEC deployment inside an NFV
associated to gating, QoS enforcement, charging, etc. environment (and coherence for the definition of orchestration
functions in the two ISGs). This aspect is very important not
only from a standard point of view, but also for the operators
that are going to evaluate the opportunity to deploy MEC
inside their infrastructure (whether the network is already
virtualized or not). From this perspective, MEC ISG is already
working in close collaboration to NFV, and it is establishing
liaisons also with 3GPP and other relevant SDOs that will have
an impact on the definition of 5G systems.

VI. CONCLUSIONS AND FUTURE WORKS


Fig. 5. MEC-based mobile IoT scenario. SGi Deployment option
In this paper we provided a tutorial on MEC technology
and an overview of the MEC framework and architecture
Moreover, the emerging and growing maturity of
recently defined by ETSI MEC ISG standardization group. We
virtualization technologies opens to new research directions
described some examples of MEC deployment, with special
aiming at integrate in the same virtualization infrastructure the
radio signal processing (e.g., the Cloud RAN scenario), reference to IoT use cases, since Internet of Things is
network functions (e.g., EPC entities) and applications (e.g., recognized as a main driver for 5G. After having discussed also
IoT control systems) under the umbrella of the NFV paradigm. benefits and challenges for MEC toward 5G, we can say that
MEC has definitely a window of opportunity to contribute to
the creation of a common layer of integration for the IoT
V. THE ROLE OF MEC TOWARD 5G: world. One of the main question still open is: how this
BENEFITS AND CHALLENGES technology will coexists with LTE advanced pro and future 5G
5G will bring an extremely flexible and programmable network? For this aspect we foresee the need of a very strong
system able to combine computing capabilities with high cooperation between 3GPP and ETSI (e.g. NFV, and possibly
diversity types of communications (i.e. Human & Machine). other SDOs) in order to avoid unnecessary duplicate in the
The resulting network will be faster and smarter, allowing for standard. In this sense MEC could pave the way and be
higher magnitudes of connected objects consuming less energy natively integrated in the network of tomorrow.
than today. Thus the industry expects that 5G will provide a
unified framework of reference for Internet of Things. ACKNOWLEDGMENT
Coming back to nowadays, we can observe that the Internet We gratefully recognize the great contributions of many
of Things phenomenon is still at an early stage of deployment colleagues, who in fruitful cooperation, contributed with
and, probably, one of the main challenge, is not (only) related valuable insight, surveys and vision. We would like also to
to the technological maturity of the ecosystem but also to the thank our colleagues and delegates in ETSI MEC ISG for their
lack of integration. The current actors of the IoT industry are, support and interesting technical discussions around MEC.
in fact, typically building their own devices with a low level of
integration/interoperability with the ones of the other REFERENCES
companies: the various devices are getting connected over
[1] Cisco White Paper, Cisco Visual Networking Index: Forecast and
different forms of connectivity, such as 3G, LTE, Wi-Fi or Methodology, 2014-2019, May 2015, Available:
http://www.cisco.com/c/en/us/solutions/collateral/service-provider/ip- https://www.idc.com/getdoc.jsp?containerId=prUS25291514, last
ngn-ip-next-generation-network/white_paper_c11-481360.pdf. checked April 2016
[2] 5G Infrastructure Association: Vision White Paper, Feb.2015. http://5g- [5] 3GPP TR 22.891 V14.0.0 (2016-03): Feasibility Study on New
ppp.eu/wp-content/uploads/2015/02/5G-Vision-Brochure-v1.pdf Services and Markets Technology Enablers; Stage 1, (Release 14)
[3] ETSI white paper: Mobile Edge Computing: A key technology towards [6] ETSI GS MEC 002 V1.1.1 (2016-03): Mobile Edge Computing
5G, September 2015; (MEC); Technical Requirements
www.etsi.org/images/files/ETSIWhitePapers/etsi_wp11_mec_a_key_tec [7] ETSI GS MEC 003 V1.1.1 (2016-03): Mobile Edge Computing
hnology_towards_5g.pdf (MEC); Framework and Reference Architecture
[4] International Data Corporation (IDC), IDC Reveals Worldwide Internet
of Things Predictions for 2015 Press release, available at

View publication stats

Anda mungkin juga menyukai