<!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>Evaluation of the impact on energy consumption of MQTT protocol over TLS</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Edgaras Baranauskas</string-name>
          <email>edgaras.baranauskas@ktu.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jevgenijus Toldinas</string-name>
          <email>eugenijus.toldinas@ktu.lt</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Borisas Lozinskis</string-name>
          <email>borisas.lozinskis@ktu.lt</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computer Sciences, Kaunas University of Technology</institution>
          ,
          <addr-line>Kaunas</addr-line>
          ,
          <country country="LT">Lithuania</country>
        </aff>
      </contrib-group>
      <fpage>56</fpage>
      <lpage>60</lpage>
      <abstract>
        <p>- Message Queuing Telemetry Transport (MQTT) protocol is widely used in device-to-device communications. While MQTT has three quality of service (QoS) levels, it does not integrate security mechanisms. Transport Layer Security (TLS) is the standard protocol on top of the Transmission Control Protocol (TCP) to secure data in communications. In this paper, we evaluate the impact on energy consumption of MQTT protocol using its QoS levels over TLS.</p>
      </abstract>
      <kwd-group>
        <kwd>IoT</kwd>
        <kwd>MQTT</kwd>
        <kwd>TLS</kwd>
        <kwd>battery energy consumption</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>INTRODUCTION</title>
    </sec>
    <sec id="sec-2">
      <title>RELATED WORK</title>
      <p>
        In [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] authors declare the user’s responsibility to address
security issues for MQTT, MQTT-SN protocols and suggests
enabling security for them by envisaging SSL/TLS, but due to
IoT heterogeneity it is cumbersome to manage certificates and
keys. Thus, authors [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] propose attribute based encryption for
secure MQTT that augments security feature for the existing
MQTT protocol and its variants. Use of Datagram Transport
Layer Security (DTLS) for securing data communications
over User Datagram Protocol (UDP) adds at least 33 bytes to
the original packet header, and while IoT devices run on
batteries, efficient secure communication scheme is needed
[6].
© 2019 for this paper by its authors. Use permitted under Creative
Commons License Attribution 4.0 International (CC BY 4.0)
A novel security mechanism introduced for MQTT
environments is based on AugPAKE via a secure side channel,
where authentication and authorization tokens are transported
in the same field [7] of the topic name. In [8] the most known
application layer protocols are compared: CoAP, MQTT,
XMPP, HTTP, AMQP and WebSocket, All the protocols
mentioned above use TCP as transport layer (CoAP uses
UDP) and TLS/SSL as security layer (CoAP uses DTLS). In
terms of Message Oriented Approach (MOA), MQTT stands
out [8]. Requirements for authentication, authorization, data
integrity, and confidentiality do not included in the MQTT
specification. Authors [9] argue that the lack of security
requirements in the MQTT protocol standard is related to:
      </p>
      <p>MQTT focuses only on message dispatching.</p>
      <p>Reducing the overhead that is related to security
features is used to keep the protocol as light as
possible.</p>
      <p>Historical implementations of MQTT were based on
private networks.</p>
      <p>Significantly different security functionalities
required while MQTT is used from IoT devices to
Facebook messenger mobile application.</p>
      <p>The authors [9] are inclined to believe that a good
midterm solution to large-scale MQTT security problems could be
represented by implementation of TLS. Current open-source
MQTT implementations compared in table I.</p>
      <p>OPEN-SOURCE MQTT IMPLEMENTATION</p>
      <p>MQTT implementation property</p>
      <p>
        MQTT
implementation
Mosquitto [
        <xref ref-type="bibr" rid="ref7">10</xref>
        ]
eMQTTC [
        <xref ref-type="bibr" rid="ref8">11</xref>
        ]
Apollo [
        <xref ref-type="bibr" rid="ref9">12</xref>
        ]
Artemis [
        <xref ref-type="bibr" rid="ref10">13</xref>
        ]
      </p>
      <p>Definition
Most commonly used
implementation
Asynchronous Erlang
MQTT Client
Requires Erlang
R17+
Is a faster, more
reliable, easier to
maintain messaging
broker built from the
foundations of the
original ActiveMQ
Implementation
arising from
ActiveMQ</p>
      <p>Security
SSL/TLS
support
TCP/SSL
Socket
Support
SSL/TLS
Support</p>
      <p>SSL
support</p>
      <p>QoS
QoS0,
QoS1,
QoS2
QoS0,
QoS1,
QoS2
QoS0,
QoS1,
QoS2
QoS0,
QoS1,
QoS2</p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref11">14</xref>
        ] proposed potential methodologies to extend the
Common Architectures and Network services found in the
IEEE 1451 Family of Standard into applications that utilize
MQTT. The authors installed the Mosquitto MQTT client
onto ESP-32s, MQTT broker onto Raspberry Pi 3 and
experimentally conclude that MQTT is an effective
communication protocol when it comes to small-scale
systems, security is a major area for future investigation.
MQTT has its downsides in security but is being greatly
adapted in the world of IoT today and the hope is extend that
adaptation to the IEEE 1451 Family of standards [
        <xref ref-type="bibr" rid="ref11">14</xref>
        ].
      </p>
      <p>
        MQTT is a simple protocol designed for devices with low
processing power and it tries to minimize the processing
needed to exchange messages, which means that serious
security problems arise such as lack of: authentication,
authorization, confidentiality and integrity [
        <xref ref-type="bibr" rid="ref12">15</xref>
        ].
      </p>
      <p>
        The security challenges of the IoT industry with focus on
standardized communication protocols explored and
implementation details for the security levels mandated by the
Constrained Application Protocol provided in [
        <xref ref-type="bibr" rid="ref13">16</xref>
        ]. MQTT
implementations also offer out of the box the security
certificates mode that could be achieved in the Java Paho
library or as part of the Mosquitto framework. In fact, the
MQTT broker also offers the possibility to maintain a list of
revoked certificates that can be used to disable rogue
endpoints [
        <xref ref-type="bibr" rid="ref13">16</xref>
        ].
      </p>
      <p>
        The most critical issues with the aim of guiding future
research directions on the IoT security panorama highlighted
[
        <xref ref-type="bibr" rid="ref14">17</xref>
        ]. According to the author conclusion, the most vulnerable
level of the IoT system model is the perception layer due to
the physical exposure of IoT devices, to their constrained
resources and to their technological heterogeneity. Thus, it is
crucial, in the next future, to start working on the critical issues
of this level implementing lightweight security solutions that
can adapt to the heterogeneous environments with
resourceconstrained devices.
      </p>
      <p>
        Smart city solutions have to be energy-efficient,
costefficient, reliable, secure, to do that IoT devices should
operate in a self-sufficient way without compromising QoS in
order to enhance the performance with uninterrupted network
operations. Therefore, the energy efficiency and life span of
IoT devices are key to next generation smart city solutions
[
        <xref ref-type="bibr" rid="ref15">18</xref>
        ]. With the increase in IoT applications for smart cities,
energy-efficient solutions are also evolving for low-power
devices. Energy-efficient solutions such as Lightweight
Protocols, Scheduling Optimization, and Predictive Models
for Energy Consumption, Cloud-Based Approach,
LowPower Transceivers, and Cognitive Management Framework
can reduce energy consumption or optimize resource
utilization. Possible future directions for energy management
in smart cities are [
        <xref ref-type="bibr" rid="ref15">18</xref>
        ]:




      </p>
      <p>Energy-efficient mechanisms for software-defined
IoT solutions, which can provide scalable and
context-aware data and services.</p>
      <p>Directional energy transmission from dedicated
energy sources for wireless power transfer.</p>
      <p>Energy efficiency and complexity of security
protocols are crucial aspects for their practical
implementation in IoT; thus, it is important to
investigate robust security protocols for energy
constraint IoT devices.</p>
      <p>Fog computing can lead to energy saving for most of
the IoT applications; therefore, it is important to study
energy consumption of fog devices for IoT
applications.</p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref16">19</xref>
        ] authors evaluate MQTT (QoS0) vs HTTPS, send
performance, battery energy consumption and conclude that
while HTTPS is slightly more efficient in terms of establishing
connection, MQTT is much more efficient during
transmission.
      </p>
      <p>III.</p>
    </sec>
    <sec id="sec-3">
      <title>MQTT QUALITY OF SERVICE LEVELS</title>
      <p>
        MQTT provides three levels of QoS [
        <xref ref-type="bibr" rid="ref17">20</xref>
        ]:
      </p>
      <p>At most once (Fig. 1) - sometimes called "fire and forget".
The message is delivered at most once, or it is not delivered at
all.</p>
      <p>At least once (Fig. 2), it is the default mode of transfer.
The message is always delivered at least once. If the sender
does not receive an acknowledgment, the message is sent
again with the DUP flag set until an acknowledgment is
received.</p>
      <p>Exactly once (Fig. 3), the message is always delivered
exactly once. The message must be stored locally at the sender
and the receiver until it is processed. Exactly once is the
safest, but slowest mode of transfer.</p>
      <p>A general framework for evaluation of the impact on
energy consumption of MQTT protocol over TLS is shown in
Fig. 4. T-diagram is linking together three evaluation
domains: security, reliability and energy consumption.</p>
      <p>The framework also outlines a context of the selected
domains: for security domain it is SSL/TLS , the MQTT
QoS levels ensure reliability, and battery energy consumption
measurement for energy domain. Our experiments are
performed using (see Fig. 5):</p>
      <p>Access point – Wi-Fi router TP-Link.</p>
      <p>Broker – Raspberry Pi2 with Broadcom BCM2837
Arm7 Quad Core CPU, clock frequency 900MHz,
1GB RAM, 802.11b/g/n Wi-Fi communication
protocols.</p>
      <p>Subscriber/Publisher – IoT Module ESP32 with
Tensilica L106, 32-bit, RISC CPU, clock frequency
160 MHz, 802.11b/g/n Wi-Fi communication
protocols.</p>
      <p>Measuring instrument
MASTECH MS8050.</p>
      <p>–
digital
multimeter
Power supply for ESP32 – llithium
LS903052, 3.7V, 1200mAh.
battery</p>
      <p>
        The ESP32 module integrates ESP8266EX is and is
recommended for tests or for further development. For our
evaluation, we use the Mosquitto MQTT broker that
configured to use TLS. We create a simple scenario to
establish encrypted connection between broker and client
similarly as encrypted connection between web server and
web client. To create certificates we use OpenSSL v1.1.1a
software for Windows [
        <xref ref-type="bibr" rid="ref18">21</xref>
        ]. In our case, we create
Certification authority (CA) in a computer with Windows OS.
Certificate creation and installation in the Mosquitto MQTT
broker (in our case Raspberry Pi2) and in the
subscriber/publisher (in our case ESP32) is shown in Fig.6.
      </p>
      <p>Fig. 6. Certificate creation and installation in the mosquitto MQTT broker
and subscriber/publisher</p>
    </sec>
    <sec id="sec-4">
      <title>EXPERIMENTAL RESULTS The results of measurements are presented in Figs. 7-9. Fig. 7 shows the battery voltage level for MQTT “At most once” over TLS,</title>
      <p>The results of measurements are summarized in table II.
Based on these results we can evaluate the difference in
energy consumption of three MQTT protocol QoS levels over
TLS. Less energy consumes “At least once (QoS1) over TLS
– voltage drop 0.3026V. Most energy consumes “At most
once (QoS0) over TLS – voltage drop 0.3228V and “Exactly
once (QoS2)” over TLS consumes more energy than QoS1
and less than QoS0 - voltage drop 0.3176V.</p>
      <p>TABLE II.</p>
      <p>EVALUATION OF THE IMPACT ON ENERGY CONSUMPTION</p>
      <p>OF MQTT PROTOCOL OVER TLS
MQTT QoS</p>
      <p>Level
MQTT “At most
once (QoS0)” over
TLS
MQTT “At least
once (QoS1)” over
TLS
MQTT “Exactly
once (QoS2)” over
TLS</p>
      <p>Energy consumption
Voltage drop Consumed time</p>
      <p>(V) (hh:mm:ss)</p>
    </sec>
    <sec id="sec-5">
      <title>CONCLUSION</title>
      <p>The energy consumption of MQTT protocol with various
QoS over TLS levels is highly different. The main results of
this paper are as follows:</p>
      <p>1) The real time measured values for energy consumption
securing MQTT over TLS are achieved with various QoS
levels.</p>
      <p>2) The results of energy consumption measurements when
performing secure communication using MQTT protocol over
TLS can be used to reliably predict energy consumption of
three QoS levels:
</p>
      <p>QoS “At least once (QoS1)” over TLS consumes
less energy than the others two QoS levels (QoS0
over TLS and QoS2 over TLS),
QoS “At most once (QoS0)” over TLS consumes
more energy than the others two QoS levels
(QoS1 over TLS and QoS2 over TLS),
QoS “Exactly once (QoS2)” over TLS consumes
5 % more energy than QoS “At least once
(QoS=1)” over TLS”,
QoS “ At most once (QoS0)” over TLS consumes
6,7 % more energy than QoS “At least once
(QoS1)” over TLS,
QoS “Exactly once (QoS=2)” over TLS
consumes 1,7 % less energy than QoS “At most
once (QoS0) over TLS”.</p>
      <p>Available:</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>Gartner</given-names>
            <surname>Says Worldwide IoT Security Spending Will</surname>
          </string-name>
          <article-title>Reach $1.5 Billion in 2018</article-title>
          . STAMFORD,
          <string-name>
            <surname>Conn</surname>
            <given-names>.</given-names>
          </string-name>
          ,
          <source>March</source>
          <volume>21</volume>
          ,
          <year>2018</year>
          . Gartner, Inc. [Online]. Available: https://www.gartner.com/en/newsroom/pressreleases/2018-03-21
          <article-title>-gartner-says-worldwide-iot-security-spendingwill-</article-title>
          <string-name>
            <surname>reach-</surname>
          </string-name>
          1
          <string-name>
            <surname>-</surname>
          </string-name>
          point-5
          <string-name>
            <surname>-</surname>
          </string-name>
          billion-in-2018
          <source>[Accessed February 07</source>
          ,
          <year>2019</year>
          ]
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>R.</given-names>
            <surname>Giambona</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. E.C.</given-names>
            <surname>Redondi</surname>
          </string-name>
          , M. Cesana, “
          <string-name>
            <surname>Demonstrating</surname>
            <given-names>MQTT</given-names>
          </string-name>
          +
          <article-title>: An Advanced Broker for Data Filtering, Processing</article-title>
          and Aggregation”,
          <source>In 21st ACM International Conference on Modelling, Analysis and Simulation of Wireless and Mobile Systems (MSWIM '18)</source>
          ,
          <source>October 28-November 2</source>
          ,
          <year>2018</year>
          , Montreal, QC, Canada. ACM, New York, NY, USA. [Online]. Available: https://doi.org/10.1145/3242102.3243317
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>S. B.</given-names>
            <surname>Kenitar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Marouane</surname>
          </string-name>
          ,
          <string-name>
            <surname>A</surname>
          </string-name>
          . Mounir, “
          <article-title>Evaluation of the MQTT Protocol Latency over Different Gateways”</article-title>
          , SCA2018,
          <year>October 2018</year>
          , Tetuan, Morocco. [Online]. Available: https://doi.org/10.1145/3286606.3286864
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M.</given-names>
            <surname>Singh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>MA</surname>
          </string-name>
          , S. VL, and
          <string-name>
            <surname>B. P</surname>
          </string-name>
          ,
          <article-title>"Secure MQTT for Internet of Things (IoT)"</article-title>
          .
          <source>2015 Fifth International Conference on Communication Systems and Network Technologies. IEEE Computer Society</source>
          ,
          <year>2015</year>
          , pp.
          <fpage>746</fpage>
          -
          <lpage>751</lpage>
          . DOI 10.1109/CSNT.
          <year>2015</year>
          .16
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <source>[5] MQTT Version 3.1.1 Plus Errata 01. OASIS Standard Incorporating Approved Errata</source>
          <volume>01</volume>
          . [Online]. Available: http://docs.oasisM. H.
          <string-name>
            <surname>Amaran</surname>
            ,
            <given-names>M. S.</given-names>
          </string-name>
          <string-name>
            <surname>Rohmad</surname>
            ,
            <given-names>L. H.</given-names>
          </string-name>
          <string-name>
            <surname>Adnan</surname>
            ,
            <given-names>N. N.</given-names>
          </string-name>
          <string-name>
            <surname>Mohamed</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <string-name>
            <surname>Hashim</surname>
          </string-name>
          ,
          <article-title>"Lightweight Security for MQTT-SN"</article-title>
          .
          <source>International Journal of Engineering &amp; Technology</source>
          ,
          <volume>7</volume>
          (
          <issue>4</issue>
          .11) (
          <year>2018</year>
          ) pp.
          <fpage>223</fpage>
          -226
          <string-name>
            <given-names>M.</given-names>
            <surname>Calabretta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Pecori</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Veltri</surname>
          </string-name>
          ,
          <article-title>"A Token-based Protocol for Securing MQTT Communications"</article-title>
          .
          <source>26th International Conference on Software, Telecommunications and Computer Networks (SoftCOM)</source>
          ,
          <year>2018</year>
          . DOI:
          <volume>10</volume>
          .23919/SOFTCOM.
          <year>2018</year>
          .8555834
          <string-name>
            <given-names>A. L.</given-names>
            <surname>Marra</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Martinelli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Mori</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Rizos</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Saracino</surname>
          </string-name>
          ,
          <article-title>"Introducing Usage Control in MQTT"</article-title>
          . S. K. Katsikas et al. (Eds.):
          <source>CyberICPS</source>
          <year>2017</year>
          /SECPRE 2017, LNCS 10683, Springer International Publishing AG 2018, pp.
          <fpage>35</fpage>
          -
          <lpage>43</lpage>
          . https://doi.org/10.1007/978-3-
          <fpage>319</fpage>
          - 72817-
          <issue>9</issue>
          _
          <fpage>3</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <string-name>
            <given-names>G.</given-names>
            <surname>Perrone</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Vecchio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Pecori</surname>
          </string-name>
          , and
          <string-name>
            <given-names>R.</given-names>
            <surname>Giaffreda</surname>
          </string-name>
          ,
          <article-title>"The Day After Mirai: A Survey on MQTT Security Solutions After the Largest Cyberattack Carried Out through an Army of IoT Devices"</article-title>
          .
          <source>In Proceedings of the 2nd International Conference on Internet of Things, Big Data and Security (IoTBDS</source>
          <year>2017</year>
          ), p.p.
          <fpage>246</fpage>
          -
          <lpage>253</lpage>
          . DOI:
          <volume>10</volume>
          .5220/0006287302460253
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>Eclipse</given-names>
            <surname>Mosquitto</surname>
          </string-name>
          . [Online].
          <source>[Accessed February 08</source>
          ,
          <year>2019</year>
          ]
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Erlang</surname>
            <given-names>MQTT Client.</given-names>
          </string-name>
          [Online]. Available: https://github.com/emqtt/emqttc [Accessed February 08,
          <year>2019</year>
          ] http://activemq.apache.org/apollo/
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Apollo</surname>
          </string-name>
          . [Online].
          <source>Available: [Accessed February 08</source>
          ,
          <year>2019</year>
          ]
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [13]
          <string-name>
            <surname>Apache</surname>
            <given-names>ActiveMQ Artemis.</given-names>
          </string-name>
          [Online]. Available: http://activemq.apache.org/artemis/ [Accessed February 08,
          <year>2019</year>
          ]
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>J.</given-names>
            <surname>Velez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Trafford</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Pierce</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Thomson</surname>
          </string-name>
          , E. Jastrzebski, and
          <string-name>
            <given-names>B.</given-names>
            <surname>Lau</surname>
          </string-name>
          ,
          <article-title>"IEEE 1451-1-6: Providing Common Network Services over MQTT"</article-title>
          .
          <source>IEEE Sensors Applications Symposium (SAS)</source>
          .
          <year>2018</year>
          . DOI:
          <volume>10</volume>
          .1109/SAS.
          <year>2018</year>
          .8336750
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>S. H.</given-names>
            <surname>Ramos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. T.</given-names>
            <surname>Villalba</surname>
          </string-name>
          , and
          <string-name>
            <given-names>R.</given-names>
            <surname>Lacuesta</surname>
          </string-name>
          ,
          <article-title>"MQTT Security: A Novel Fuzzing Approach"</article-title>
          .
          <source>Wireless Communications and Mobile Computing. Volume</source>
          <year>2018</year>
          , Hindawi,
          <volume>11</volume>
          pages. https://doi.org/10.1155/
          <year>2018</year>
          /8261746
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>S.</given-names>
            <surname>Zamfir</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Balan</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Iliescu</surname>
          </string-name>
          , and
          <string-name>
            <given-names>F.</given-names>
            <surname>Sandu</surname>
          </string-name>
          ,
          <article-title>"A Security Analysis on Standard IoT Protocols"</article-title>
          .
          <source>2016 International Conference on Applied and Theoretical Electricity (ICATE)</source>
          .
          <source>DOI: 10.1109/ICATE</source>
          .
          <year>2016</year>
          .7754665
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>M.</given-names>
            <surname>Frustaci</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Pace</surname>
          </string-name>
          , G. Aloi, and
          <string-name>
            <given-names>G.</given-names>
            <surname>Fortino</surname>
          </string-name>
          ,
          <article-title>"Evaluating Critical Security Issues of the IoT World: Present and Future Challenges"</article-title>
          .
          <source>IEEE Internet of things journal</source>
          , vol.
          <volume>5</volume>
          , No.
          <volume>4</volume>
          ,
          <year>august 2018</year>
          , pp.
          <fpage>2483</fpage>
          -
          <lpage>2495</lpage>
          . DOI:
          <volume>10</volume>
          .1109/JIOT.
          <year>2017</year>
          .2767291
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>W.</given-names>
            <surname>Ejaz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Naeem</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Shahid</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Anpalagan</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Jo</surname>
          </string-name>
          ,
          <article-title>"Efficient Energy Management for the Internet of Things in Smart Cities"</article-title>
          . IEEE Communications Magazine,
          <year>January 2017</year>
          , pp.
          <fpage>84</fpage>
          -
          <lpage>91</lpage>
          . DOI:
          <volume>10</volume>
          .1109/
          <string-name>
            <surname>MCOM</surname>
          </string-name>
          .
          <year>2017</year>
          .1600218CM
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>J. L.</given-names>
            <surname>Espinosa-Aranda</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Vallez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Sanchez-Bueno</surname>
          </string-name>
          , D. AguadoAraujo, G. Bueno,
          <string-name>
            <given-names>O.</given-names>
            <surname>Deniz</surname>
          </string-name>
          ,
          <article-title>"Pulga, a tiny open-source MQTT broker for flexible and secure IoT deployments"</article-title>
          .
          <source>1st IEEE Workshop on Security and Privacy in the Cloud, Florence (Italy)</source>
          ,
          <year>September 30</year>
          ,
          <year>2015</year>
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [20] IBM, “
          <article-title>Qualities of service provided by an MQTT client”</article-title>
          . [Online]. Available: https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/co m.ibm.mq.dev.doc/q029090_.
          <source>htm [Accessed February 8</source>
          ,
          <year>2019</year>
          ]
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [21]
          <fpage>20</fpage>
          -Nov-2018
          <source>OpenSSL 1</source>
          .
          <article-title>1.0j is now available, including bug and security fixes [Online]</article-title>
          . Available: https://www.openssl.
          <source>org/ [Accessed January 4</source>
          ,
          <year>2019</year>
          ]
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [22]
          <string-name>
            <surname>Damaševičius</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Napoli</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sidekerskienė</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Woźniak</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          (
          <year>2017</year>
          ).
          <article-title>IMF mode demixing in EMD for jitter analysis</article-title>
          .
          <source>Journal of Computational Science</source>
          ,
          <volume>22</volume>
          ,
          <fpage>240</fpage>
          -
          <lpage>252</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>