<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>F. E. Pani and C. Repetto. Smart mobility and public transport:
Opportunities and challenges in rural and urban areas. Journal of Trafic and Transportation
Engineering</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.1038/s41928-018-0195-9</article-id>
      <title-group>
        <article-title>Analysing IoT Applications with DISSECT-CF-Fog in Simulated Fog and Cloud Environments</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Andras Markus</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mate Biro</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Attila Kertesz</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Software Engineering Department, University of Szeged</institution>
          ,
          <country country="HU">Hungary</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2019</year>
      </pub-date>
      <volume>7</volume>
      <fpage>4</fpage>
      <lpage>5</lpage>
      <abstract>
        <p>The latest services of the Internet are expanded to the edge of the network, which led to the emergence of Internet of Things (IoT), where sensors, actuators and smart devices are connected in order to interoperate with each other. IoT services often deal with a vast amount of raw data, therefore they collaborate by exploiting cloud resource capabilities. However, the abilities of Cloud Computing make it suitable to process and store the IoT data, real time applications or low latency services have stricter requirements. As a result, Cloud Computing was extended towards Fog Computing to resolve issues such as overloaded communication channels or minimal delay of a service. In order to develop, research or evaluate such complex IoT-Fog-Cloud systems, stakeholders often use simulation tools, because these simulators usually deal with realistic models and behaviour. They also provide reasonable alternatives to the high operation and purchase costs of real equipment, or system failures. In this paper, we present the DISSECT-CF-Fog simulator, which aims to model IoT-Fog-Cloud systems and ensures various configuration options. Its usability is presented through representative IoT use cases. The broad functionalities make the software a proper decision for investigating trade-ofs of modern networks in terms of energy, utilisation cost or computational power.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Simulation</kwd>
        <kwd>Fog Computing</kwd>
        <kwd>Internet of Things</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        The Fourth Digital Revolution has created numerous challenges in the fields of Cloud Computing,
Fog Computing and Internet of Things [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. These paradigms are often associated as the
Cloud-toThing Continuum [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], where vast amounts of IoT data are analysed and stored in a multi-layered
Fog-Cloud topology, in which geographically separated nodes are responsible for data processing.
In such systems, nodes are typically resource constrained and, in case of overloaded resources,
data can be forwarded to a higher level for processing. At the top of the topology, cloud resources
ensure the needed computing power at the expense of increased response time [3].
      </p>
      <p>Such systems afect human life positively by ofering various real time IoT applications in the
ifelds of healthcare, transportation, parking and many more [ 4]. Nevertheless, by executing these
applications, we have to consider the primary trade-ofs of energy consumption, computational
power usage, utilisation cost and other secondary resource metrics such as time and latency.</p>
      <p>The emergence of simulation tools allows us to analyse such complex IoT-Fog-Cloud systems
thoroughly, however the eficiency and comprehensive observation may require accurate and
realistic models used in a simulation environment. In this paper, we introduce the open-source
DISSECT-CF-Fog simulator as a solution for investigating the most challenging problems arising
from the management of these modern network systems. We also describe the usability of
DISSECT-CF-Fog in a comprehensive manner by representative IoT use cases. In the first use
case a logistics application is simulated, where mobile devices are on the move continuously, and
the system has to take into account the handover of devices, in order to foster service availability
and reduce the overall latency of the data. The second scenario is a European-wide weather
forecasting scenario, where IoT sensors (for instance humidity or temperature detectors) sample
the local environment conditions and send the sensed data for further processing. To avoid the
bottleneck efect of cloud resources and IoT application delays, they can be aided by resource
constrained fog nodes.</p>
      <p>The reminder of this paper is the following: in Section 2 we introduce the simulator and its
related works, in Section 3 we present the use cases for exemplifying its utilisation, and finally,
in Section 4 we conclude our work.</p>
    </sec>
    <sec id="sec-2">
      <title>2. The DISSECT-CF-Fog Simulator</title>
      <p>In an IoT-Fog-Cloud system the aforementioned trade-ofs must be handled carefully in order
to create an efective service, therefore the following major issues [ 5] are usually considered:
(i) connectivity problem means the selection of a dedicated fog node for an IoT device.
This decision has a heavy impact on the performance, when dozens of IoT devices enter
into the system from a certain area. (ii) Computation offloading distributes the IoT data
located in resource constrained nodes in order to facilitate the data processing. Overwhelmed
nodes can make the system inefective easily. (iii) Billing is also a key aspect, since for
sustainable IoT-Fog-Cloud services we need to consider the business model as well, therefore
both IoT and cloud/fog side costs must be considered. Finally, (iv) resource management,
provisioning and discovery aim at proper allocation of services, which is particularly
important for device mobility. Metrics such as latency, storage and free computing power can
change continuously according to the actual load of the moving devices.</p>
      <p>Hereby we present the DISSECT-CF-Fog simulator [6], which provides detailed models with
various parameters for IoT device and application behaviour, as well as data centre management
with realistic network settings. The simulation tool is also capable of considering diferent
algorithms for ofloading tasks from the computational nodes by taking into account the energy
consumption of system entities, IoT device mobility, and pricing schemes of real providers and
network properties as well. DISSECT-CF-Fog can also be a reasonable choice for large-scale
experiments, especially if the number of active entities exceeds tens of thousands.</p>
      <p>DISSECT-CF-Fog is essentially a Discrete Event Simulation (DES) framework, therefore
it supports decision making for complex time-related scenarios. The software is capable of
simulating internal processes of distributed systems by supporting the simulation of parallel
and distributed computing despite having a sequential execution.</p>
      <p>DISSECT-CF-Fog consists of seven major subsystems implemented in a layered fashion. The
core of the simulator attempts to provide a comprehensive implementation for a particular
concept or task independently. DISSECT-CF-Fog does not use an existing DES framework,
but rather defines its own. The Event System is responsible for managing the behaviour
of recurring and irregular events as well as controlling the state of the system throughout
the simulation hence it is the foundation of the previously mentioned self implemented DES
model. The Energy Modelling subsystem allows the monitoring of energy resources of every
simulation resoruces. The Unified Resource Sharing subsystem implements a resource
spreader components. The main concept of this part of the system is to manage a central resource
provider that is able to share behaviour among other, lower-level computing concepts. Modelling
virtual machines, networking, physical machines and storage is happening in Infrastructure
Simulation subsystem. A layer above is the Cost Modelling which establish modules to
calculate IoT and Cloud side pricing of diferent providers in highly detailed manner. The
Infrastructure Management provides IaaS components such as PM and VM schedulers
that simulate the management of users request with a detailed level of abstraction. Finally, the
highest layer is the Fog Logical Management subsystem, that contains Fog and IoT related
components exclusively. It encompasses essential logical controllers to manage the function of
IoT applications, actuators or mobile devices. It typically gives a comprehensive overview of
possible strategies applied to these components.</p>
      <p>The base components may not be altered or replaced in the simulator as they are well tested
and have been validated. Also they could not be decoupled from the logic of the system easily.
However, the higher layers of the system allows experienced programmers to introduce new
components into the simulator if needed, such as IoT task scheduling or IoT workflow modelling.
One of the main advantages of the DES simulators is the relatively fast simulation, therefore
certain components like routers or switches would slow down the simulation time unnecessarily.
In such cases low level network simulators could be a more promising choice for the evaluation.</p>
      <sec id="sec-2-1">
        <title>2.1. Related Work</title>
        <p>Utilising diferent simulation tools for analysing related problems is a common and acceptable
practise among researchers, because simulators can model the behaviour of complex
IoTFog-Cloud systems realistically. The accuracy of a simulator depends on its detailedness: (i)
fine-grained tools simulate the internal behaviour of the system focusing on a certain level
of network operation and virtualisation abilities. The high level of accuracy has serious efects
on the run time of the software, typically for the large scale experiments where the number of
simulated entities may dramatically increase. (ii) Coarse-grained models are inflating the
system behaviour while the inner representation is simplified in order to perform large scale
scenarios. These kind of simulators are considered less efective and punctual.</p>
        <p>Nevertheless, by using such software, individuals can avoid the high operation costs of service
providers and the investment into equipment such as sensors, IoT devices and computational
nodes. Over the past years, many simulation approaches were published, however most of
the tools are typically heterogeneous and restricted to manage just certain tasks of a complex
system, which makes the concrete software inadequate for investigating diferent types of
problems. Furthermore, configuration or scenario migration among them are not provided at
all.</p>
        <p>Simulator</p>
        <p>Programming Language</p>
        <p>Granularity</p>
        <p>Last modified
Java
C++
Java
Java
Java</p>
        <p>Java
Python</p>
        <p>Java</p>
        <p>Coarse-grained</p>
        <p>Fine-grained
Fine-grained
Fine-grained
Fine-grained</p>
        <p>Fine-grained
Coarse-grained</p>
        <p>Fine-grained</p>
        <p>Considering the publicly available IoT-Fog-Cloud simulators, for instance in FogTorchPI1 [7],
researchers seek solutions for the deployment of application components on a fog architecture
with the Monte Carlo algorithm, however this simulator lacks detailed fog and IoT models.</p>
        <p>YAFS2 [8] is one of the latest simulators with various functionality and possible research
goals such as application module placement and message routing policies, but its model omits
the virtualisation layer completely.</p>
        <p>Similarly, FogNetSim++3 [9] has also no layer dedicated to model virtualised resources and
actuators. This simulator focuses on the very detailed network operations and its characteristics.
It is a typical network simulator which deals with communication protocols (e.g. HTTP, MQTT).</p>
        <p>Bunch of simulators are built upon the well-known CloudSim simulator. As these simulators
are utilising diferent versions of CloudSim and extending various types of modules,
interoperation among them are impossible. The most representative tools are iFogSim4 [10], MobFogSim5
[11], EdgeCloudSim6 [12] and IoTSim-Edge7 [13].</p>
        <p>Although DISSECT-CF-Fog8 is not fully equipped yet, it is still able to represent a broad array
of functionalities. Besides usability, we should consider other metrics such as maintainability.
However the previously mentioned simulators are commonly accepted by the research
community, some of them have been untouched for years, therefore these tools do not follow the latest
trends of IoT-Fog-Cloud systems and easily become irrelevant in the near future. Contrariwise
DISSECT-CF-Fog is being developed constantly with the help of a dedicated research group and
implements new features and improvements on a regular basis.</p>
        <p>Table 1 summarises the related simulation tools. For the comparison we listed the used
programming language, the granularity of the simulator, and we also noted the year when the
simulators were last modified.</p>
        <p>1FogTorchPI: https://github.com/di-unipi-socc/FogTorchPI/. Accessed in September, 2021
2YAFS: https://github.com/acsicuib/YAFS/. Accessed in September, 2021
3FogNetSim++: https://github.com/rtqayyum/fognetsimpp/. Accessed in September, 2021
4iFogSim: https://github.com/Cloudslab/iFogSim/. Accessed in September, 2021
5MobFogSim: https://github.com/diogomg/MobFogSim/. Accessed in September, 2021
6EdgeCloudSim: https://github.com/CagataySonmez/EdgeCloudSim/. Accessed in September, 2021
7IoTSim-Edge: https://github.com/DNJha/IoTSim-Edge/. Accessed in September, 2021
8DISSECT-CF-Fog: https://github.com/andrasmarkus/dissect-cf/. Accessed in September, 2021</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Evolution of the Simulator Software</title>
        <p>DISSECT-CF-Fog has had four major development stages. (i) IoT module explicitly aims
to develop an environment in which the modelling of a concrete IoT infrastructure is easily
feasible and its configuration is convenient. (ii) Fog module introduces the physical and logical
components of a fog-based infrastructure to the simulator. (iii) Actuator and Mobility
module introduces the bidirectional communication channels from the nodes back to the
IoT actuators and adds the ability of mobile features to physical entities with the help of
geographic coordinate system and diferent moving policies. Finally, (iv) Energy metering
module extends the IoT model with an energy metering facility with the help of microcontroller
modelling. The modules of the core simulator and the extended DISSECT-CF-Fog are strongly
built upon each other, therefore in the following subsections, the tables also highlight the most
important characteristics of the concrete module for creating IoT-Fog-Cloud simulations.</p>
        <sec id="sec-2-2-1">
          <title>2.2.1. DISSECT-CF</title>
          <p>DISSECT-CF-Fog is the extension of the core simulator DISSECT-CF (DIScrete event baSed
Energy Consumption simulaTor for Clouds and Federations) [14]. It is a versatile, event-based
simulation framework that focuses mainly on research on infrastructure cloud schedulers.
Compared to most similar simulation tools, DISSECT-CF ofers two considerable benefits: a
unified resource sharing model, and a more advanced IaaS stack simulation, which includes
for instance physical and virtual machines, storage and in-data-centre networking. Table 2
and 3 show the related Virtual Appliance for representing virtual machine images and
Resource Constraints for defining the resource need of a virtual machine.</p>
          <p>The storage capacity of the repository
Network bandwidth for the incoming data</p>
          <p>Network bandwidth for the outgoing data</p>
          <p>The bandwidth between repositories located in the same node
The service ensures the physical machines to create virtualised objects</p>
          <p>The physical position of the object</p>
          <p>The physical position of the object</p>
          <p>The covered physical neighbourhood of the node from where it accepts data</p>
        </sec>
        <sec id="sec-2-2-2">
          <title>2.2.2. IoT Extension</title>
          <p>Connected devices are part of an ecosystem in which every device communicates with other
related devices and nodes in an environment to automate their corresponding task, hence the
IoT extension of DISSECT-CF-Fog emphasises the modelling of interconnected smart devices.
The Device component ensures an abstraction for various types of IoT devices with the most
frequent attributes. Considering that each IoT device has a physical location regardless of
their static or mobile nature, this extension represents the geographical position of the device.
Due to the paradigm of IoT, each device has network and storage capabilities, therefore this
abstract component defines a networking model which generates a local Repository with
given network settings shown in Table 4.</p>
          <p>The realisation of the Device entity operates on sensor data generating activities. Based on
the measuring frequency, the component saves the data in its local storage and then with the help
of its network settings it forwards it to the corresponding fog/cloud application which is selected
by the installation strategy of the device. Currently, there are five installation strategies defined
in this module: (i) Runtime-aware strategy selects the least loaded application based on
the ratio of connected devices and the number of physical machines, (ii) Distance-aware
strategy always installs the device to the nearest application, (iii) Cost-aware strategy
prefers the cheapest application and (iv) Fuzzy strategy where application selection happens
based on fuzzy algorithm, that predicts which fog node would be the best for the given IoT
devices. The algorithm considers various normalised properties of the system and it utilises
Sigmoid and Kappa function, lastly conjunction, disjunction or aggregation operators finalise
the decision. Finally, (v) the Random strategy chooses one of the available nodes randomly.</p>
        </sec>
        <sec id="sec-2-2-3">
          <title>2.2.3. Fog Extension</title>
          <p>The development of the fog extension and the IoT extension occurred simultaneously.
Regarding real world scenarios, there are two major constituents upon defining a fog computation
node: a physical and a logical part. The physical component of fog nodes (represented by
ComputingApplicance in the simulator and shown in Table 5) utilises IaaS service to ensure
physical machines to create virtualised IoT applications. Likewise IoT devices, fog nodes have
real physical locations. Due to the fact that fog infrastructures are rather heterogeneous the
IaaS service of the sytem is highly configurable.</p>
          <p>The ComputingAppliance component does not only serve the physical attributes of a fog,
but also defines the connection between distinct computing nodes. The connected physical
machines define a hierarchical structure in which computing nodes can communicate with one
another. Exclusively cloud nodes can take place at the top layer of this hierarchy, while both
fog and cloud nodes can be placed on any lower level. Each node can communicate with nodes
in higher layers (parents) or with nodes on the same level (neighbours). A possible structure is
shown in Figure 1.</p>
          <p>Virtual machines are responsible for processing data generated by sensors. Virtual machines
are managed by a separate, complex logical component in the system (Application) - the
detailed configuration options are shown in Table 6. This component allocates the incoming
data among the available virtual machines to be processed, furthermore it starts or shuts them
down depending on the actual load. The Application component also provides an ofloading
mechanism determined by the capacity of a node: if the load exceeds a certain threshold, the
residue data is forwarded to a diferent node. Currently the following application strategy
available for ofloading: (i) Hold Down strategy only allows horizontal data forwarding,
which means only the neighbours are considered. (ii) Push Up strategy is the opposite,
where only vertical communication channels are utilised (meaning child-parent connections).
(iii) Load-aware strategy tries to find the less loaded computing resources with the best
latency. (iv) Fuzzy strategy also tries to predict the optimal node for the unprocessed data
similarly to the Fuzzy-based device strategy. Finally, (v) we can apply the Random strategy
as well to simulate a more chaotic scenario if needed.</p>
        </sec>
        <sec id="sec-2-2-4">
          <title>2.2.4. Actuator and Mobility Extension</title>
          <p>To satisfy a well-detailed and versatile simulator, the actuator module completes the IoT layer
by adding actuator functionalities, which means the actuator component is equipped with basic
network features (e.g. latency). This development stage focuses mainly on the implementation
of software driven actuator behaviours due to their increasing prevalence in the field of IoT,
while preserving the key functionalities of ordinary physical actuators. Due to the necessity
of feedback data to the actuator interface the simulator extended its communication to be
multi-directional.</p>
          <p>Applying mobility models to mimic the movements of IoT devices is hardly any other than
mandatory in fog computing simulation tools, since it undoubtedly afects the proximity of fog
nodes to end users. Previous extensions of DISSECT-CF-Fog considered IoT devices as immobile
static entities. The mobile features are handled with two diferent movement policies in the
system. (i) In the Nomadic model entities move along predefined points, visiting each location
once. (ii) The Random model tries to mimic the movements of devices with unforeseen mobile
behaviour by changing the direction of the movement randomly.</p>
        </sec>
        <sec id="sec-2-2-5">
          <title>2.2.5. Energy Extension</title>
          <p>Considering the energy usage of complex IoT-Fog-Cloud systems is also a key aspect for
the development and maintenance. The energy model of the DISSECT-CF-Fog takes three
parameters into consideration: (i) the Minimum power if the device or node is turned of, but
still plugged into the wall socket. (ii) The Maximum power if the CPU is fully utilised and
ifnally, the (iii) Idle power if the device/node is running without executing any computational
task. At this moment the simulator deals with two behaviour: firstly, (i) Dynamic Power
Draining model uses linear interpolation between idle and maximum power values, secondly
(ii) Constant Power Draining behaviour can consider any power value (e.g. minimum
power consumption).</p>
          <p>The energy measurement of both physical nodes and mobile devices are required. The
DISSECT-CF core simulator has already dealt with modules related to monitoring the energy
consumption of IaaS services, but by introducing the Microcontroller class to the simulator,
DISSECT-CF-Fog is now fully able to measure the whole energy usage of any IoT-Fog-Cloud
system. The previously mentioned draining behaviours are attached to states, which can indicate
a fully turned of device with static energy consumption (minimum power value), or it can
represent a high energy consumption state, where the actual power consumption can change
dynamically (idle and maximum power values), for instance events when high power spikes
appear (e.g. the IoT device activate the sensor for a measurement). Table 7 and 8 present the
exhaustive descriptions of the Microcontroller and Device classes.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. The IoT Use Cases</title>
      <p>The field of IoT has been growing and evolving continuously in the last decade, which fosters
diferent areas of human life. The very first attempt of creating an IoT system was in the field
of weather forecasting. In weather forecasting, a collection of IoT sensors is installed around
the world, in order to predict weather events, e.g. [15]. Such systems can generate billions of
IoT data measurements, which require the presence of fog nodes located geographically close
to the data sources for pre-processing and ofloading. Temperature, humidity, pressure, light
intensity and wind information are typically monitored and collected.</p>
      <p>IoT transportation is a more complex scenario, where we have to deal with smart mobility
issues of travellers, suppliers and drivers [16]. In the contrary of the previous case, both fixed
and mobile IoT objects may utilise the fog nodes, and in order to provide low latency services
by fog nodes, the system should manage the handover process of IoT devices. In both urban and
the rural contexts trafic, vehicle and air quality data can be measured to support this process.</p>
      <p>In the following section, we present two scenarios to cover both previously mentioned cases.</p>
      <sec id="sec-3-1">
        <title>3.1. Evaluation</title>
        <p>In the first scenario, we simulate a one-week-long operation of a courier service in Germany
during an intense service schedule. We consider five fog nodes in five big cities (Berlin, Hamburg,
Cologne, Munich, Bremen) and a cloud node in Frankfurt. We define 120 devices connected
to the courier service in each city. Third of the smart devices are immobile static devices
generating 50 bytes of data every minute having the Runtime-aware strategy, while the
rest of the devices are implementing the Random mobility policy with the Distance-aware
strategy, generating 150 bytes of data each minute. Three out of five fog nodes use the Random
strategy and the rest of the fog applications, as well as the cloud application, use the Hold
Down strategy. These strategies are defined in DISSECT-CF-Fog (mentioned in Section
2.2.2 and 2.2.3), and we also set up energy measurement and IoT pricing for the simulated
infrastructure.</p>
        <p>The second scenario defines a weather forecast infrastructure within Hungary. We represent
four major weather stations in four diferent locations/cities (Budapest, Kalocsa, Kecskemet,
Debrecen). Each station has 30 sensors generating data every 30 minutes and forwarding it
with the Cost-aware strategy and the Random strategy (in 1:3 ratio). We define one
fog per station with the Push Up strategy and the Load-aware strategy (in 1:1 ratio)
and a cloud node in Budapest. Once again we set up energy measurement and IoT pricing
functionalities for this scenario. The simulation models seven days of work time.</p>
        <p>In both use cases, a fog node deals with 16 CPU cores and 64 GB of RAM, whilst a cloud
node utilises 32 CPU cores and 64 GB of RAM. The virtual machines running on the fog and
cloud nodes require 4 and 8 CPU cores with 4 GB of memory, respectively. This means that the
maximum size of an IoT task takes exactly five minutes to be fully executed on the stronger
virtual machine. For the node cost we apply the Amazon Web Services’ pricing schema and
for the IoT cost four schemes of the most popular providers were considered. The energy
consumption of the nodes was based on real cloud services9 and the IoT devices appearing
during the simulation mimic the energy model of Raspberry Pi10.</p>
        <p>The evaluation results are presented in Table 9 and 10. To compare the results, we list the
number of utilised virtual machines, the costs of the providers and the amount of the used
energy power as well. We also note how many megabytes of data were generated during the
simulation, and how many minutes the final application delay has, which reflects the time
interval between the last data generation and the last task computation ended. Finally, we
also show the duration of the simulation itself, but it depends on the performance of the used
PC. Concerning the results, it can be seen how the computing resources try to process the
unforeseen data to keep the application delay as low as possible. However, neither the first
nor the second case can process all the data in real time, the total delay 5.12 and 16.42 minutes,
respectively. The unit price of a virtual machine was 15.49 Euro in the first use case, but it
dramatically increased in the second case, with 56.3 Euro. In summary, it is clearly visible that
in the second scenario the choice of the computing resources were inadequate both concerning
the paid costs and performed computation time.</p>
        <p>We modelled and simulated two possible real life scenarios with the help of DISSECT-CF-Fog
to showcase its capabilities. Beyond the basic functionalities of the software (e.g. physical
machine scheduling, virtual machine managing or data generation and processing) we aimed
9LPDS Cloud of MTA SZTAKI website is available at: https://www.sztaki.hu/en/science/departments/lpds/.
Accessed in September, 2021</p>
        <p>10Raspberry Pi website is available at: https://www.raspberrypi.org/. Accessed in September, 2021
to give a brief review on the fog related features such as device mobility or fog and device
strategies. The evaluation section sums up the most important results which can be measured
in the simulator.</p>
        <p>Unfortunately, the comparison in details of the previous scenarios with other simulator
solutions discussed in Section 2.1 requires strong limitations as it presented in [17], due to the
incostence in design and modelling approach of DISSECT-CF-Fog and other simulators. In some
cases the absolute absence of several functionalities in the related simulators makes it impossible
to evaluate their results on the same level of detailedness. Despite these dificulties, a future
work contains a thorough comparison of the most relevant fog simulators and DISSECT-CF-Fog.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Conclusion</title>
      <p>In this paper we introduced and demonstrated a simulation solution called DISSECT-CF-Fog
for modelling various IoT-Fog-Cloud systems. First we discussed the basic parameters of the
software, which can be used for fine-tuning its behaviour. Then, we evaluated two diferent
IoT use cases to show its versatile usability as well. The presented evaluation results can be
enhanced by performing further analysis regarding the trade-ofs of energy, utilisation cost and
computational power by using diferent device and application strategies. Such strategies can be
easily extended by diverse optimising algorithms by overwriting the corresponding interfaces.
As a future work, we plan to develop additional AI-based algorithms for analysing application
and system behaviour.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Software Availability</title>
      <p>The DISSECT-CF-Fog simulator is available at: https://github.com/andrasmarkus/dissect-cf/</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgments</title>
      <p>The research leading to these results is partially supported by the European COST programme
under action identifier CA19135 (CERCIRAS), by the UNKP-21-2 and UNKP-21-3 New National
Excellence Program of the Ministry for Innovation and Technology, and by the National Research,
Development and Innovation Ofice within the framework of the Artificial Intelligence National
Laboratory Programme.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>R.</given-names>
            <surname>Mahmud</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Ramamohanarao</surname>
          </string-name>
          and
          <string-name>
            <given-names>R.</given-names>
            <surname>Buyya</surname>
          </string-name>
          .
          <article-title>Fog Computing: A Taxonomy, Survey</article-title>
          and
          <string-name>
            <given-names>Future</given-names>
            <surname>Directions</surname>
          </string-name>
          . Internet of Everything: Algorithms, Methodologies, Technologies and Perspectives,
          <volume>103</volume>
          -
          <fpage>130</fpage>
          ,
          <year>2018</year>
          . DOI:
          <volume>10</volume>
          .1007/
          <fpage>978</fpage>
          -981-10-5861-
          <issue>5</issue>
          _
          <fpage>5</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>M.</given-names>
            <surname>Bendechache</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Svorobej</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. Takako</given-names>
            <surname>Endo</surname>
          </string-name>
          and
          <string-name>
            <given-names>T.</given-names>
            <surname>Lynn</surname>
          </string-name>
          .
          <article-title>Simulating Resource Management across the Cloud-to-Thing Continuum: A Survey and Future Directions</article-title>
          .
          <source>Future Internet 12</source>
          ,
          <year>2020</year>
          . DOI:
          <volume>10</volume>
          .3390/fi12060095
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>