Cloudlet.
The cloudlet that structure is typically accessed through Wi-Fi connections.
Inside, we have virtual machines,
which are the main features of cloud computing technology.
What is done here,
is shown in this example in which we have a cloud server,
which is a local server,
and a modem device together,
which may be separate devices interconnected,
or they may be on one device, one unit together.
They join the network as a local cloud support system.
However, of course, they do not have
the full capacity and storage memory that the main cloud would have,
so we call them cloudlets.
Inside, they can support virtual machines
to various devices that are local, that request it.
The cloudlet that definition is based on mobility and has
small-scale cloud data center techniques.
They are located at the edge of the Internet,
nearby the mobile devices.
In some cases, some mobile devices could be programmed to be cloudlets.
cloudlets support resource intensive and interactive mobile applications,
and provide powerful computing resources to mobile devices with low latency.
These cloudlets are used between the UE and cloud device, somewhere in the middle.
A cloudlet is a data center in a box type concept,
that brings the cloud closer to the UE.
So, this is really like a cloud,
although it does not have all the features and capacity that a cloud will have,
it is like a miniature device that has additional communication techniques,
wireless and wire, brought closer to device,
such that it is effectively used.
Cloudlet's use virtual machine to provision resources
for use in real time over Wi-Fi networks.
So, therefore, direct one-hop cloud access is enabled,
and that is why latency becomes so small and they become much more reliable.
The architecture is based on three layers,
and the cloudlet that has a cloudlet layer,
which is a group of co-located nodes and it's managed by a Cloudlet Agent.
Then there's a node layer,
where multiple execution environments running on
top of the operating system is what enables this.
This is managed by a Node Agent.
Once again, on top was a Cloudlet Agent,
on here is a Node Agent.
Then there's the component layer.
This includes a set of services that interface to the higher layers,
as in terms of their execution environment, which is right here.
Then comparing these three,
Fog Computing, Mobile Edge Computing,
MEC, and Cloud Computing in terms of mobile device wise.
Well, Fog Computing, routers,
switches, access points and gateways,
whereas Mobile Edge Computing are servers running in the base station,
mobile communication base station.
Something like an eNode B,
or Gnode B in the near future.
Data center in a box concept is what a cloudlet is.
The Node location is in Fog Computing,
it varies between N devices and the cloud,
whereas in MEC, the radio network controller as well
as the base stations are where the MEC needs to be located.
When you look at cloudlets,
these are local or outdoor installations.
Software architecture are based on the fog abstraction layer and Fog Computing.
The mobile orchestrator in the mobile communication network is what controls the MEC,
and in cloudlets, it is the Cloudlet Agent.
Of course, there's the node agent as well assisting the Cloudlet Agent.
In terms of context awareness,
Fog Computing is medium,
however, Mobile Edge Computing is high.
Relatively, Cloudlet Computing is low,
as the necessary virtual machines that are going to be distributed
are already prepared and delivered first, in advace.
Proximity is based on the structure of the network,
where Fog Computing can be one or multiple hops.
When it comes to MEC,
you're talking about one hop.
This is because your smartphone is one hop away from the base station.
The MEC is located right next to the base station,
that is why a one-hop.
Although this one hop is a little bit of a longer one-hop,
compared to the cloudlet one hop,
because these one-hops are wireless local area network based.
Normally, they are wireless LAN, Wi-Fi based.
So, therefore, cloudlets are typically supposed to
be closer compared to where the macro base station is,
in your mobile communication network.
Then comes access mechanisms.
When you go to Fog Computing,
it is Bluetooth, Wi-Fi,
or it could be the mobile network and
other wireless personal area network techniques, such as ZigBee.
When it comes to MEC,
it is the mobile network primarily.
However, you could use Wi-Fi techniques.
When you're looking into cloudlet,
Wi-Fi is the primary access type.
However, other components could be used to connect.
The Internode communication, here in Fog Computing is supported,
in Mobile Edge Computing it's partial,
and also Cloudlet Computing it is partial as well.
Looking at these categories and their characteristics.
Their physical proximity, for Fog Computing and cloudlet that it is high,
for MEC, it is relatively low.
When looking at the power consumed,
Mobile Edge Computing consumes more power because you need to send your signal to
the base station and that is why the physical proximity being low,
results in a higher power consumption.
When it comes to Fog Computing or Cloudlet Computing,
you're talking about advice that most likely is very,
very close and therefore,
the power consumption is low.
Computation time, well, Fog Computing here will take
higher longer periods whereas
Mobile Edge Computing and Cloudlet Computing are expected to be faster.
Context Awareness.
Mobile Edge Computing has more knowledge,
more prediction, more fetching of relevant contents,
so therefore it is going to be more sensible to what is going to be communicated.
That means that the overall Context Awareness is
high whereas Fog Computing and Cloudlet Computing are relatively lower.
The logical proximity is in ways such that Cloudlet Computing is in short,
whereas Fog Computing and MEC are maybe.
Then we have Non-IP support.
This is also important because not all techniques and devices use a IP-based protocols.
Looking into Fog Computing,
it is a yes or as Mobile Edge Computing and Cloudlet Computing,
it is a no.
However, Mobile Edge Computing and Cloudlet Computing can be designed in
special ways such that they can support Non-IP devices and Non-IP services.
These are the references that I used and I recommend them to you. Thank you.