<!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 />
    <article-meta>
      <title-group>
        <article-title>Information Logistics and Fog Computing: The DITAS Approach</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Pierluigi Plebani</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>David Garcia-Perez</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Maya Anderson</string-name>
          <email>mayaag@il.ibm.com</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>David Bermbach</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Cinzia Cappiello</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ronen I. Kat</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Frank Pallas</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Barbara Pernici</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Stefan Tai</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Monica Vitali</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Atos Spain SA Pere IV</institution>
          ,
          <addr-line>08018 Barcelona</addr-line>
          ,
          <country country="ES">Spain</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Haifa Haifa University Campus, Mount Carmel</institution>
          ,
          <addr-line>Haifa, 3498825</addr-line>
          ,
          <country country="IL">Israel</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>IBM Research</institution>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Politecnico di Milano</institution>
        </aff>
      </contrib-group>
      <fpage>129</fpage>
      <lpage>136</lpage>
      <abstract>
        <p>Data-intensive applications are usually developed based on Cloud resources whose service delivery model helps towards building reliable and scalable solutions. However, especially in the context of Internet of Things-based applications, Cloud Computing comes with some limitations as data, generated at the edge of the network, are processed at the core of the network producing security, privacy, and latency issues. On the other side, Fog Computing is emerging as an extension of Cloud Computing, where resources located at the edge of the network are used in combination with cloud services. The goal of this paper is to present the approach adopted in the recently started DITAS project: the design of a Cloud platform is proposed to optimize the development of data-intensive applications providing information logistics tools that are able to deliver information and computation resources at the right time, right place, with the right quality. Applications that will be developed with DITAS tools live in a Fog Computing environment, where data move from the cloud to the edge and vice versa to provide secure, reliable, and scalable solutions with excellent performance.</p>
      </abstract>
      <kwd-group>
        <kwd>Fog Computing</kwd>
        <kwd>Edge Computing</kwd>
        <kwd>Data movement</kwd>
        <kwd>Cloud Computing</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>http://www.ditas-project.eu/</p>
    </sec>
    <sec id="sec-2">
      <title>Introduction</title>
      <p>
        Fog Computing [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], often also referred to as Edge Computing [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], is an
emerging paradigm aiming to extend Cloud Computing capabilities to fully exploit
the potential of the edge of the network where traditional devices as well as new
generations of smart devices, wearables, and mobile devices { the so-called
Internet of Things (IoT) { are considered. Especially for data-intensive applications,
since IoT is a source for enormous amounts of data that can be exploited to
provide support in a multitude of di erent domains (e.g., predictive machinery
maintenance, patient monitoring), this new paradigm has opened new frontiers.
      </p>
      <p>
        Nowadays, the typical approach for data processing relies on cloud-based
applications: data are collected and pre-processed on the edge, then they are
moved to the cloud, where a more scalable and reliable processing environment
is provided. Finally, the output of the analysis is sent to the end user, whose
devices are again on the edge. While the cloud o ers virtually unlimited
computational resources making data processing extremely e cient, the resulting data
movement could have an impact on the application performance due to possibly
signi cant latencies of the transmission. To improve this type of applications,
proper information logistics become fundamental for delivering information at
the right time, the right place, and with the right quality [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. However,
developing applications that are able to deal with these issues can be really challenging
for several reasons: heterogeneity of devices at the edge, privacy and security
issues when moving data from the edge to the cloud, or limited bandwidth.
      </p>
      <p>The goal of this paper is to introduce the recently started DITAS project
which aims to improve, through a cloud platform, the development of
dataintensive application by enabling information logistics in Fog environments where
both resources belonging to the cloud and the edge are combined. The resulting
data movement is enabled by Virtual Data Containers which provide an
abstraction layer hiding the underlying complexity of an infrastructure made of
heterogeneous devices. Applications developed using the DITAS toolkit will be
able to exploit the advantages of both cloud-based solutions about reliability
and scalability, and edge-based solutions with respect to latency and privacy.</p>
      <p>To properly discuss the relevant aspects of information logistics, Fog
computing as well as challenges that need to be faced, the rest of the paper is organized
as follow: Section 2 proposes the DITAS vision on Cloud, Fog, and Edge
computing. Details on the importance of information logistics in general, as well as
in Fog environments in particular, are discussed in Section 3. Section 4 gives an
overview of the DITAS approach with emphasis on the architectural description
of the proposed cloud platform.
2</p>
    </sec>
    <sec id="sec-3">
      <title>On the Fog, Edge, and Cloud Computing</title>
      <p>
        Cloud computing [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] has been widely adopted as a model for developing and
providing scalable and reliable applications in a cost-e cient way with minimal
infrastructure management e orts for developers. In such an environment,
computational resources as well as storage capacity can be considered unlimited,
which has boosted the proliferation of applications able to manage huge amount
of data. Nevertheless, relying only on Cloud computing or even on federated
clouds [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] could have some drawbacks especially when the data to be processed
are generated by devices located at the edge of the network. If we consider
that predictions for IoT estimate about 32 billion connected devices in 2020
that will be producing about 440 Petabytes per year (accounting for 10% of the
world data) [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], the impacts of data movement between edge-located resources
{ where data are produced { and the cloud-located resources { where data are
processed and stored { can be signi cant. In the telecommunication sector, when
Cloud resources
      </p>
      <p>Edge resources</p>
      <p>
        Fog Computing
mobile devices moved from being simple consumers of contents to being
producers of contents, the term Fog Computing has been coined to identify a platform
able \to provide compute, storage, and networking services between Cloud data
centers and devices at the edge of the network" [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The term Edge Computing
has been instead proposed by information systems engineering researchers when
IoT was recognized as a great opportunity for providing new services. It
identi es the \technologies allowing the computation to be performed at the edge of
the network, on downstream data on behalf of cloud services and upstream data
on behalf of IoT services" [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
      </p>
      <p>
        Based on these de nitions, Cloud Computing is mainly related to the core of
the network whereas Edge Computing is focused on providing to the owner of
resources the local 'in-situ' means for collecting and preprocessing data before
sending it to cloud resources (for further utilization), thus addressing typical
constraints of sensor-to-cloud scenarios like limited bandwidth and strict latency
requirements. For this reason, also in the light of the de nition proposed by the
OpenFog Consortium [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], we here after consider Fog Computing as the sum
of Cloud and Edge Computing. As shown in Figure 1, cloud resources include
physical and virtual machines which are capable of processing and storing data.
On the other side, smart devices, wearables, or smartphones belong to the set of
edge-located sources. While Cloud Computing is devoted to e ciently managing
capabilities and data in the cloud, Edge Computing is focused on providing the
means for collecting data from the environment (which will then be processed by
cloud resources) to the owner of the available resources. On this basis, Cloud and
Edge Computing are usually seen as two distinct and independent environments
that, based on the speci c needs, are connected to each other to move data
usually from the edge to the cloud.
      </p>
      <p>Exploiting the Fog Computing paradigm, in DITAS these two environments
seamlessly interoperate to provide a platform where both computation and data
can be exchanged in both downstream and upstream direction. For instance,
when data cannot be moved from the edge to the cloud, e.g., due to privacy
issues, then the computation is moved to the edge. Similarly, when there are
insu cient resources at the edge data are moved to the cloud for further
processing. With DITAS, we want to provide tools, speci cally designed for developers
of data-intensive applications, which are able to autonomously decide where to
move data and computation resources based on information about the type of
the data, the characteristics of applications as well as the available resources
at both cloud and edge locations and applicable constraints such as EU GDPR
privacay regulation 5.
3</p>
    </sec>
    <sec id="sec-4">
      <title>Information Logistics</title>
      <p>
        Since the 1990s, when interconnection of heterogeneous information systems
managed by di erent owners became easier and when the Web started managing
signi cant amounts of information, the problem of delivering such information
has become more and more relevant: the more the data are distributed, the more
di cult is it to nd the information needed. Thus, tools are required to guide
the users in this task. In this scenario, Information Logistics6 has emerged as
a research eld for optimizing the information provision and information ow
especially in networked organizations [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
      </p>
      <p>
        As discussed in [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], Information Logistics can be studied from di erent
perspectives: e.g., how to exploit the data collected and managed inside an
organization for changing the strategy of such organizations, how to deliver the right
information to decision makers in a process, or how to support supply chain
management. In our case, according to the classi cation proposed in [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], we are
interested in user-oriented Information Logistics: i.e., the delivery of
information at the right time, the right place, and with the right quality and format
to the user [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. As a consequence, user requirements can be de ned in terms
of functional aspects, i.e., content, and non-functional ones, i.e., time, location,
representation, and quality.
      </p>
      <p>
        Especially in the recent years, where data deluge has been ever increasing,
providing solutions that are able to satisfy these types of requests becomes more
5http://http://www.eugdpr.org/
6Actually, according to [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] the Information Logistics term appeared the very rst
time in Wormley P. W., Information logistics: Local distribution (delivery) of
information, Journalism Quarterly, Vol. 55 Issue 3, 1/9p, 1978, but a real interest on this
eld started only more recently.
and more challenging. Di erent sources available on the Web could provide data
of interest to the user and selecting the best source depends on non-functional
requirements. Data quality dimensions, such as timeliness or accuracy [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], can
be used to measure whether data are useful or not. Location of data sources and
the performance of the system o ering these data can in uence data quality:
e.g., data stored in the cloud will take more time to be obtained than data on
the premises of the user. Privacy aspects are also fundamental as some data
must not leave the boundaries of the organization which holds these data, be
used for speci c purposes as de ned by GDPR regulations, or may only do so in
preprocessed (pseudonymized, aggregated, etc.) form. Finally, dealing with
edgelocated resources signi cantly increases the complexity of the resulting system for
many reasons. These resources are often very heterogeneous in terms of software
platforms, storage capabilities, computational resources, and data formats. The
network connection may vary in bandwidth and, due to their nomadic nature,
there is a high rate of churn among edge-located resources.
      </p>
      <p>
        When developing data-intensive applications in a Fog Computing
environment, information logistics holds a central role and DITAS wants to simplify the
work of developers providing tools that are able to enact the proper data and
computation movements so as to satisfy user requirements. In DITAS, the
processing tasks composing the data-intensive application specify not only the
content of required data, but also the data utility which subsumes all non-functional
requirements that may vary with respect to the status and the context of the
application. In contrast to the typical approaches where data move to the
processing modules, in DITAS, computational tasks may also move to where the
data are stored whenever it is neither feasible, e.g., due to privacy issues, nor
acceptable, e.g., due to high latency, to move the data. Thus, DITAS is studying
data and computation movement strategies to decide where, when, and how to
persist data { on the cloud or on the edge of the network { and where, when, and
how to compute part of the tasks composing the application to create a
combination of edge and cloud that o ers a good balance between reliability, security,
sustainability, and cost. To ascertain whether such DITAS-based applications
actually meet their quality goals monitoring, but also experiment-driven cloud
service benchmarking [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] will be used.
4
      </p>
    </sec>
    <sec id="sec-5">
      <title>DITAS approach</title>
      <p>The objectives of DITAS discussed above will be o ered through a cloud
platform where developers can design their data-intensive applications where tasks
are linked to Virtual Data Containers that satisfy the data and application
requirements by enacting the proper information logistics.
4.1</p>
      <sec id="sec-5-1">
        <title>Virtual Data Container</title>
        <p>The concept of a Virtual Data Container (VDC) represents one of the key
elements in the DITAS proposal. Generally speaking a VDC embeds the logic to
Task 1</p>
        <p>Task 2
VDC 1</p>
        <p>Task 3</p>
        <p>VDC 2
Cloud resources
enable a proper information logistics depending on both the application to be
executed and the available data sources. On the one hand, a VDC is linked to
one or more tasks composing the data-intensive applications. Along with these
links the developers specify the needs in terms of data, including both functional
(i.e., the content) and non-functional aspects (i.e., data quality). On the other
hand, a VDC is connected to a set of data sources o ering a given information.</p>
        <p>Thus, the goal of a VDC is to provide a single virtual layer, which can
be built upon the principles of Service Oriented Computing, which abstracts
the connected data sources. This virtual layer hides from the developer the
intricacies of the underlying complex infrastructure composed by smart devices,
sensors, as well as traditional computing nodes located in the cloud. The VDC
also embeds the capabilities not only for moving the data from the data sources
to the tasks operating on them, but also between the data sources to make the
data provisioning e ective taking into account data access policies and
regulations. Finally, the de nition of data movement techniques implies the de nition
of data transmission (e.g., data stream, bulk) and data transformation (e.g.,
encryption, compression) mechanisms, provided by a VDC, to de ne which will be
the destination of the data, which is the data format to be adopted during the
transmission, and how data will be stored in the destination.</p>
        <p>Once the application is running, the application interacts only with the VDC
as designed, which, in turn, enact all the data movement strategies needed to
satisfy the posed requirements.
4.2</p>
      </sec>
      <sec id="sec-5-2">
        <title>DITAS platform</title>
        <p>The DITAS platform is a cloud-based solution which o ers to the data-intensive
application developers a set of tools for improving the design and the execution
of the applications exploiting the functionalities provided by VDCs.</p>
        <p>As shown in Figure 3 the functionalities o ered by the DITAS cloud
platform are composed of two main blocks: (i) an SDK in charge of supporting the
developers in design and deployment of the applications, and (ii) a distributed
execution environment responsible for running and controlling the behavior of the
application. About the SDK, extension of popular tools (e.g. Node-RED), will
be proposed to de ne applications in which data processing is a central element.
The key element of this tool is to allow the developer to design the applications
by specifying the VDC and constraints/preferences about the resources to be
exploited. For this reason, a communication with the cloud platform
infrastructure is required to have a complete picture about the available resources both
on the cloud and the edge. Based on the developer's instructions, and leveraging
on the degree of freedom given by the VDC while satisfying all the constraints,
the application is deployed among the selected resources.</p>
        <p>The deployment of a DITAS-enabled data-intensive application implies that
the resources selected to be involved in the execution embed a set of modules
supporting the data and computation movement. For this reason, the execution
environment is based on a distributed architecture where the execution engine
is in charge of executing the tasks assigned to the resources on which the engine
is running and of maintaining coordination with the other resources involved
in the same application. Moreover, a monitoring system is able to check the
status of the execution, track data movement, and collect all data necessary for
understanding the behaviour of the application. In case of deviation with respect
to the expected behavior, data and/or computation movements can be enacted
to move the application to an acceptable state. Finally, data collected by all
involved monitoring systems can be further analysed to provide advice to the
developers for improving the design of their application.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Conclusions</title>
      <p>This paper has presented the vision of DITAS, a recently started EU project,
which aims to simplify the development of data-intensive applications where data
and computation can be moved among resources belonging to both the core and
the edge of the network, i.e., both federated clouds and edge environments.</p>
      <p>As the project is in its infancy, future work is mainly devoted to implementing
all the concepts expressed in this paper. Two case studies, one about an Industry
4.0 scenario, and another about an e-Health scenario will be used for testing and
validating the proposed approach.</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgments</title>
      <p>DITAS project receives funding from the European Union's Horizon 2020
research and innovation programme under grant agreement RIA 731945.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Batini</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cappiello</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Francalanci</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maurino</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Methodologies for data quality assessment and improvement</article-title>
          .
          <source>ACM Comput. Surv</source>
          .
          <volume>41</volume>
          (
          <issue>3</issue>
          ),
          <volume>16</volume>
          :1{
          <fpage>16</fpage>
          :
          <fpage>52</fpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Bermbach</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wittern</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tai</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <source>Cloud Service Benchmarking: Measuring Quality of Cloud Services from a Client Perspective</source>
          . Springer Int.l Publishing (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Bonomi</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Milito</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhu</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Addepalli</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Fog computing and its role in the internet of things</article-title>
          .
          <source>In: Proceedings of the First Edition of the MCC Workshop on Mobile Cloud Computing</source>
          . pp.
          <volume>13</volume>
          {
          <fpage>16</fpage>
          .
          <string-name>
            <surname>MCC</surname>
          </string-name>
          '
          <volume>12</volume>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>D</given-names>
            <surname>'Andria</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            ,
            <surname>Field</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Kopaneli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Kousiouris</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            ,
            <surname>Garcia-Perez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Pernici</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Plebani</surname>
          </string-name>
          ,
          <string-name>
            <surname>P.</surname>
          </string-name>
          :
          <article-title>Data Movement in the Internet of Things Domain</article-title>
          .
          <source>In Service Oriented and Cloud Computing: 4th European Conf., ESOCC</source>
          <year>2015</year>
          , Taormina, Italy,
          <source>September 15-17</source>
          ,
          <year>2015</year>
          , Proc. Springer Int.l Publishing (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Haftor</surname>
            ,
            <given-names>D.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kajtazi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mirijamdotter</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <source>A Review of Information Logistics Research Publications</source>
          . Springer Berlin Heidelberg (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Kurze</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Klems</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bermbach</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lenk</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tai</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kunze</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Cloud federation</article-title>
          .
          <source>In: Proceedings of the International Conference on Clouds, Grids, and Virtualization (CLOUD COMPUTING)</source>
          . vol.
          <year>2011</year>
          , pp.
          <volume>32</volume>
          {
          <issue>38</issue>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Liu</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          , et al.:
          <article-title>NIST Cloud Computing Reference Architecture: Recommendations of the National Institute of Standards and Technology (Special Publication 500- 292)</article-title>
          . CreateSpace Independent Publishing Platform, USA (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Michelberger</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Andris</surname>
            ,
            <given-names>R.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Girit</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mutschler</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>A Literature Survey on Information Logistics</article-title>
          .
          <source>In Business Information Systems: 16th Int.l Conf., BIS</source>
          <year>2013</year>
          , Poznan, Poland, June 19-21,
          <year>2013</year>
          . Proc. Springer Berlin Heidelberg (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9. OpenFog Consortium Architecture Working Group:
          <article-title>OpenFog Architecture Overview</article-title>
          (
          <year>February 2016</year>
          ), http://www.openfogconsortium.org/ra
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Sandkuhl</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Information Logistics in Networked Organizations: Selected Concepts</article-title>
          and
          <source>Applications</source>
          . Springer Berlin Heidelberg (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Shi</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cao</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , Zhang,
          <string-name>
            <given-names>Q.</given-names>
            ,
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            ,
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <surname>L.</surname>
          </string-name>
          :
          <article-title>Edge computing: Vision and challenges</article-title>
          .
          <source>IEEE Internet of Things Journal</source>
          <volume>3</volume>
          (
          <issue>5</issue>
          ),
          <volume>637</volume>
          {646 (Oct
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Shi</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dustdar</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>The Promise of Edge Computing</article-title>
          .
          <source>Computer</source>
          <volume>49</volume>
          (
          <issue>5</issue>
          ),
          <volume>78</volume>
          {81 (May
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Turner</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reinsel</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gatz</surname>
            ,
            <given-names>J.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Minton</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <source>The Digital Universe of Opportunities. IDC White Paper (April</source>
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>