<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD with MathML3 v1.1 20151215//EN"
"https://jats.nlm.nih.gov/publishing/1.1/JATS-journalpublishing1.dtd">
<article article-type="research-article" xml:lang="en" dtd-version="1.1" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">
    <front>
        <journal-meta>
            <journal-id journal-id-type="doi">https://doi.org/10.7906</journal-id>
            <journal-title-group>
                <journal-title xml:lang="en">Interdisciplinary Description of Complex Systems</journal-title>
            </journal-title-group>
            <issn pub-type="ppub">13344676</issn>
            <issn pub-type="epub">13344684</issn>
            <publisher>
                <publisher-name xml:lang="hr">Hrvatsko intedisciplinarno društvo</publisher-name>
                <publisher-name xml:lang="en">Croatian Interdisciplinary Society</publisher-name>
                <publisher-loc>I. Lučića 1, 10000 Zagreb
                    <email xlink:href="davorka.horvatic@indecs.eu">davorka.horvatic@indecs.eu</email>
                    <ext-link xlink:href="idd.com.hr">idd.com.hr</ext-link>
                </publisher-loc>
            </publisher>
        </journal-meta>
        <article-meta>
            <article-id pub-id-type="doi">10.7906/indecs.20.1.1</article-id>
            <article-categories>
                <subj-group subj-group-type="heading" xml:lang="hr">
                    <subject>izvorni znanstveni članak</subject>
                </subj-group>
                <subj-group subj-group-type="heading" xml:lang="en">
                    <subject>Original scientific article</subject>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title xml:lang="en">Challenges of LoRaWAN technology in smart city solutions</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="yes">
                    <name>
                        <surname>Döníz</surname>
                        <given-names>Borsos</given-names>
                    </name>   
                    <xref ref-type="corresp" rid="cor1">*</xref>
                    <xref ref-type="aff" rid="aff1"></xref>
                </contrib>
                    <contrib contrib-type="author"> 
                    <name>
                        <surname>Lajos</surname>
                        <given-names>Berek</given-names>
                    </name> 
                    <xref ref-type="aff" rid="aff1"></xref>
                </contrib>                    
                <aff id="aff1">
                    <label></label>
                    <institution xml:lang="en">Óbuda University, Doctoral School of Safety and Security Sciences</institution>
                    <addr-line>Budapest, Hungary</addr-line>
                </aff>
            </contrib-group>
            <author-notes>
                <corresp id="cor1"><label>*</label>Döníz Borsos, Óbuda University, Doctoral School of Safety and Security Sciences, Budapest, Hungary<email
                    xlink:href="email@email.com">borsos.doniz@kvk.uni-obuda.hu</email>
                </corresp>
            </author-notes>
            <pub-date>
                <!--Datum izdavanja -->
                <day>21</day>
                <month>2</month>
                <year>2022</year>
            </pub-date>
            <volume>20</volume>
            <issue>1</issue>
            <fpage>1</fpage>
            <lpage>10</lpage>
            <history>
               <date date-type="received">
                    <day>27</day>
                    <month>11</month>
                    <year>2020</year>
                </date>
                <date date-type="accepted">
                    <day>20</day>
                    <month>6</month>
                    <year>2021</year>
                </date>
            </history>
            <permissions>
                <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>CC BY 4.0</license-p>
                </license>
                <license license-type="open-access" xml:lang="hr">
                    <license-p>Puni tekst objavljenih radova besplatno se smije koristiti za osobne, edukacijske ili istraživačke svrhe uz poštovanje autorskih prava autora i izdavača. Korisnici radove smiju besplatno čitati, preuzimati, kopirati, distribuirati, tiskati, prerađivati ili koristiti ih na druge zakonite načine, uz ispravno navođenje izvornika i nekomercijalnu svrhu uporabe.</license-p>  
                </license>               
                <license license-type="open-access" xml:lang="en">
                    <license-p>The usage of full-text of the articles can be used exclusively for personal, research-related or educational purposes, with regard to the authors' and publishers' rights. The users are allowed to read, download, copy, distribute, print and transform or use them for any other lawful purpose as long as they attribute the source in an appropriate manner and for the non-commercial purpose of the usage.</license-p>
                </license>
            </permissions>
            <abstract xml:lang="en">
                <p>A number of technological application factors can be highlighted in smart city solutions, where small data transmission and long range are of primary considerations. These include monitoring energy consumption, operating a smart waste management system, monitoring and tracking traffic, having smart parking systems, monitoring public lighting, and even detecting various malfunctions. Such smart city systems use IoT technology for data collection. An essential aspect of urban solutions is to ensure the coverage of large areas, both outdoors and indoors, low energy consumption, as well as modularity and mobility. LPWAN technologies can meet these conditions. LPWAN technologies include LTE-M, NB-IoT, LoRaWAN, and Sigfox. Using LoRaWAN technology can be the right solution for these cases. As with any application, it is crucial to clarify the challenges of the application with LoRaWAN. The present study addresses the categorization of LoRaWAN devices and the challenges of technology in smart city solutions. LoRaWAN products used in smart city solutions can be grouped according to several aspects. This article deals with the creation of classifications that facilitate further testing. Smart city application challenge studies are applied to the specified categories. The challenges of the solutions cover several areas. These include technological aspects, aspects of specifications, and aspects of the nature of the application. Another area represents the information security aspects; which is, however, not addressed by this invention. Based on these aspects, the article describes the challenges of LoRaWAN technology in smart cities.</p>
            </abstract>
            <kwd-group xml:lang="en">
                <kwd>LoRa, LoRaWAN, smart city, applications, device categories</kwd>
            </kwd-group>
            <funding-group>
                <award-group>
                    <funding-source source-type="acronym">MZO</funding-source>
                </award-group>
            </funding-group>
        </article-meta>
    </front>
    <body>
        <sec sec-type="INTRODUCTION">
            <label>INTRODUCTION</label>
            <p>If we consider IoT trends, they show that there are a lot more IoT devices than predicted. Based on 2019 data, there are 9,5 billion IoT assets, compared to the estimated 8,3 billion. The number of IoT devices could reach an estimated 28 billion by 2025 <xref ref-type="bibr" rid="r1">[1]</xref>. Surveys show that the vast majority of these devices are related to smart city applications. Researchers among the ten most relevant trends are also among the smart city solutions in 2020 <xref ref-type="bibr" rid="r2">[2]</xref>. LoRaWAN is also one of the IoT, LPWAN communication technologies <xref ref-type="bibr" rid="r3">[3]</xref>.
                LoRaWAN technology is wireless, low-power, long-range radio communication that works reliably even in weak signal propagation conditions <xref ref-type="bibr" rid="r2">[2]</xref> <xref ref-type="bibr" rid="r4">[4]</xref>. Because of these properties, they are preferred for use in smart city solutions. With the help of LoRaWAN devices, which are connected to the network, large areas, especially cities, can be easily covered. The following conclusion addresses LoRaWAN devices that are suitable for smart city solutions. The grouping of smart city solutions and areas is possible from several aspects. Six core areas can be distinguished: environment, life, people, mobility, economy, and government <xref ref-type="bibr" rid="r5">[5]</xref> <xref ref-type="bibr" rid="r6">[6]</xref> <xref ref-type="bibr" rid="r7">[7]</xref>. These include, for example, trackers, consumption meters, environment sensors, and parking sensors with LoRaWAN technology.
                LoRaWAN communication is one of the most significant technologies used in smart city solutions. This is shown by the presence of available LoRaWAN networks in 162 countries <xref ref-type="bibr" rid="r8">[8]</xref>. Numerous research and development projects deal with LoRaWAN due to its topicality. An important aspect when applying a new technology is the set of requirements and challenges it has to meet and the issues it may need to solve. Each technology has its own limitations that need to be considered in such studies; this is also true for LoRaWAN. In addition, similar, competing LPWAN technologies also present challenges. The LoRa Alliance is responsible for the LoRaWAN specification, which is constantly being developed, improved, and upgraded with newer versions <xref ref-type="bibr" rid="r8">[8]</xref> <xref ref-type="bibr" rid="r9">[9]</xref>. These specifications also raise some issues. The application environment of a LoRaWAN solution (indoor, outdoor, fixed, mobile) presents additional challenges. In addition, it is important to highlight that certified LoRaWAN products can be categorized by functionality. The categories contribute to research and findings.
                The structure of the article is as follows: The introduction is followed by a description of LoRaWAN technology. Next is a summary of the grouping of certified LoRaWAN products, as well as the significant challenges arising from the technology, followed by a discussion of the aspects of LoRaWAN specifications. The challenges posed by the nature of the application are also summarized. The review ends with a conclusion, which includes the possibility of additional study areas.                
            </p>            
        </sec>
        <sec sec-type="BASICS OF LORAWAN TECHNOLOGY">
            <label>BASICS OF LORAWAN TECHNOLOGY</label>
            <p>LoRaWAN network technology is based on LoRa technology developed by Semtech <xref ref-type="bibr" rid="r4">[4]</xref> <xref ref-type="bibr" rid="r10">[10]</xref>. The first issued tool appeared around 2013-2014. The name LoRa is an abbreviation of ‘long-range’, which refers to the long data transmission distance that the technology is capable of. The LoRa Alliance was founded in 2015 to regulate the network operation of this technology <xref ref-type="bibr" rid="r11">[11]</xref>. The essence of the technology is to be able to build large-scale wireless networks, even in unfavourable field conditions, all with low energy consumption. Considering that we are talking about IoT technology, we must not forget about mobility and that it is possible to establish secure two-way communication. The standard, which is continuously updated by the LoRa Alliance, allows developers and users flexible networking and use. The essential features of LoRa and LoRaWAN communications related to the topic are highlighted.
                The long range of LoRa technology is due to the use of special frequency modulation, called chirp spread spectrum (CSS) modulation. The LoRaWAN specification defines the lower two layers of the OSI model: the physical layer and the MAC sublayer of the data link layer; and the application layer. Communication in Europe takes place at 868 MHz and 433 MHz, but 868 MHz is typical. Communication is two-way, with multiple channels. The devices are characterized by low power consumption; 10-year operating time is also available with a button cell. The data transmission distance in the city is a few kilometres, but it can be up to 10-15 km in less populated areas. The data transfer rate is relatively low, at a maximum of around 50 kbps. During communication, the messages are encrypted. The communication uses AES-128 encryption <xref ref-type="bibr" rid="r11">[11]</xref> <xref ref-type="bibr" rid="r12">[12]</xref>.
                The features can be summarized as:
                •	chirp spread spectrum (CSS) modulation,
                •	868 MHz and 433 MHz frequencies in Europe,
                •	wireless radio two-way communication,
                •	low consumption,
                •	1 % transmission time,
                •	low consumption,
                •	10-15 km bridgeable distance,
                •	0,3-50 kbps data transfer rate,
                •	AES-128 encryption,
                •	star-of-stars network topology.
                Network participants include end-devices, gateways, the network server, and application servers <xref ref-type="bibr" rid="r12">[12]</xref>. Communication between nodes and gateways takes place via LoRa. The connection between a gateway, a network server, and an application server is IP based. Nodes are usually simple devices equipped with LoRaWAN communication capability and some sensors. Gateways are connected to end-devices. There can be multiple nodes and gateways within a network. Gateways, in addition to network end-nodes, communicate with network servers. The application server and the network server are connected to each other and can be physically present on one device. The network server is responsible for monitoring and managing the network format. The application server decodes the data and displays it in a way that the user can understand. Depending on usage, multiple applications can be connected to a network. This classic network architecture is based on the 1,0 specification; other LoRaWAN specifications may result in a different network architecture <xref ref-type="bibr" rid="r13">[13]</xref> <xref ref-type="bibr" rid="r14">[14]</xref> <xref ref-type="bibr" rid="r15">[15]</xref> <xref ref-type="bibr" rid="r16">[16]</xref>.
                Nodes can be divided into three classes according to their operation mode: Class A, Class B, or Class C. In all three cases, two-way communication is supported. Class A operation is optimized for consumption, with Class A devices having the lowest power consumption. Class A devices can only receive messages after they are sent, after which they open two reception windows. It is possible to send messages to the end-devices from the network server side at any time, but they can only be received after the end-device transmission period. Class B nodes operate with extra, scheduled reception windows in addition to the previous ones. In the case of Class C devices, no waiting time is to be expected; they are capable of continuous reception. This type has the highest consumption. There are uplink and downlink messages regarding the direction of data communication. An uplink message transmits from the end-device to the network server; the downlink message’s direction is the opposite. The uplink message can be an unconfirmed data message or confirmed data message <xref ref-type="bibr" rid="r12">[12]</xref>.
                Identifiers and keys are used during network communication. The most significant of these are the following. Device Address is a 32-bit identifier used to identify devices <xref ref-type="bibr" rid="r12">[12]</xref>. This ID is unique within each network and is part of the messages. Also worth mentioning the Network Session Key and the Application Session Key, which are 128-bit AES encryption keys for encrypting and decrypting data and messages <xref ref-type="bibr" rid="r12">[12]</xref>. The connection procedure is essential for the network operation of the nodes. This can be ABP (Activation by Personalization) or OTAA (Over-the-Air Activation) <xref ref-type="bibr" rid="r12">[12]</xref> <xref ref-type="bibr" rid="r17">[17]</xref>. In the case of ABP connection mode, a request is received from the end-devices to the network server once before starting the network operation. If the IDs and keys match, the connection is established. In OTAA connection mode, after a successful connection, a handshake connection is established between the nodes and the network server. The keys are exchanged continuously, ensuring a much more secure connection <xref ref-type="bibr" rid="r17">[17]</xref>.                
            </p>   </sec>       
        <sec sec-type="GROUPING OF CERTIFIED LORAWAN PRODUCTS BY FUNCTIONALITY">
            <label>GROUPING OF CERTIFIED LORAWAN PRODUCTS BY FUNCTIONALITY</label>
            <p>The LoRa Alliance is responsible for the certification of LoRaWAN products. The
                number of certified devices published on their website was 177 at the time of
                writing the review <xref ref-type="bibr" rid="r18">[18]</xref>. If LoRaWAN products are categorized, additional tests can
                be performed. Besides, it is necessary to describe the specific categories. There
                are eight categories based on the function categorization of certified LoRaWAN
                devices. These are as follows: • module: a PCBA card, a basic circuit set that
                complies with the LoRaWAN specification and features long-range, low-power,
                bidirectional, wireless communication. The LoRaWAN module is not a finished product,
                and it is the main chip of LoRaWAN application development and finished product
                production <xref ref-type="bibr" rid="r18">[18]</xref> <xref ref-type="bibr" rid="r19">[19]</xref>, • development board: a printed circuit board that fundamentally
                contains a LoRaWAN module and the necessary additional logic associated with it,
                used for learning and prototyping <xref ref-type="bibr" rid="r18">[18]</xref> <xref ref-type="bibr" rid="r20">[20]</xref>. The LoRaWAN development board can
                include a microcontroller or can be connected to microcontroller development boards
                via a typical connection line, • sensor node: a finished product which consists of
                three central units: a sensor unit, a processing unit and a LoRaWAN module <xref ref-type="bibr" rid="r18">[18]</xref>. The
                sensor node can detect specific changes in the environment, react to them and
                transmit the processed data over the LoRaWAN network <xref ref-type="bibr" rid="r21">[21]</xref> <xref ref-type="bibr" rid="r22">[22]</xref>, • actuator node: a
                finished product which consists of three central units: an actuator unit, a
                processing unit and a LoRaWAN module <xref ref-type="bibr" rid="r18">[18]</xref>. The actuator can make a specific change
                in its environment <xref ref-type="bibr" rid="r23">[23]</xref>, depending on the messages received on the LoRaWAN network,
                • sensor interface unit: a finished product which consists of three central units: a
                sensor connection, a processing unit and a LoRaWAN module. The sensor interface unit
                connects to sensor devices <xref ref-type="bibr" rid="r18">[18]</xref>. It can collect data from them and then transmit the
                data on the LoRaWAN network after processing <xref ref-type="bibr" rid="r24">[24]</xref>, • meter interface unit: a
                finished product which consists of three central units: a standard meter connector
                or a standard communication interface, a processing unit and a LoRaWAN <xref ref-type="bibr" rid="r18">[18]</xref>. The
                meter interface unit can be connected to consumption meters and can collect data
                from them and then transmit them on the LoRaWAN network after processing, • tracker:
                a finished product which consists of three central units: a locating unit, a
                processing unit and a LoRaWAN module <xref ref-type="bibr" rid="r18">[18]</xref>. The tracker is suitable for tracking
                persons/animals/objects, and the location data are transmitted via the LoRaWAN
                network <xref ref-type="bibr" rid="r25">[25]</xref>, • tester: a complex device that monitors and diagnoses the LoRaWAN
                network parameters, especially for end-devices and gateways. Another feature may be
                RF power testing. <xref ref-type="bibr" rid="r18">[18]</xref> It is also possible to create categories according to other
                logic. By this logic, the ninth group would be gateways, but there is no
                authentication procedure for these. The formed groups can be further divided into
                subgroups according to further aspects. Table 1 shows the grouping of LoRaWAN
                products by functionality <xref ref-type="bibr" rid="r18">[18]</xref>. There may be devices with properties that fit
                several groups. In these cases, the main functionality applies.  </p>
                    <table-wrap>         
                        <caption>
                            <title>Table 1. Categorization of certified LoRaWAN devices <xref ref-type="bibr" rid="r18">[18]</xref>.</title>
                        </caption> 
                    <table border="0" style="border-collapse:  collapse;width:432pt" width="576">
                        <col width="64"/>
                        <tbody>
                            <tr>
                                <td rowspan="1" colspan="1">Category</td>
                                <td rowspan="1" colspan="1">Module</td>
                                <td rowspan="1" colspan="1">Development board</td>
                                <td rowspan="1" colspan="1">Sensor node</td>
                                <td rowspan="1" colspan="1">Actuator node</td>
                                <td rowspan="1" colspan="1">Sensor interface unit</td>
                                <td rowspan="1" colspan="1">Meter interface unit</td>
                                <td rowspan="1" colspan="1">Tracker</td>
                                <td rowspan="1" colspan="1">Tester</td>
                            </tr>
                            <tr>
                                <td rowspan="1" colspan="1">Number of devices</td>
                                <td rowspan="1" colspan="1">33</td>
                                <td rowspan="1" colspan="1">15</td>
                                <td rowspan="1" colspan="1">83</td>
                                <td rowspan="1" colspan="1">3</td>
                                <td rowspan="1" colspan="1">6</td>
                                <td rowspan="1" colspan="1">24</td>
                                <td rowspan="1" colspan="1">11</td>
                                <td rowspan="1" colspan="1">2</td>
                            </tr>
                        </tbody>
                    </table>          
                </table-wrap>
            <p>For a smart city, the additional findings apply to the following categories: sensor node, actuator node, sensor interface unit, measuring interface unit and tracker. These categories represent a total of 127 different products. The study does not consider devices that use LoRaWAN technology but are not on the list of certified devices. These devices can be directly or indirectly part of smart city solutions.</p>         
        </sec>
        <sec sec-type="TECHNOLOGICAL ASPECTS OF THE CHALLENGES">
            <label>TECHNOLOGICAL ASPECTS OF THE CHALLENGES</label>
            <p>Considering the challenges of LoRaWAN technology, the following three main issues can
                be highlighted: competing technologies, technological limitations and network
                operation. Closely related to these are the aspects of the specifications, which are
                discussed in a separate section. LoRaWAN technology belongs to LPWA networks; there
                are many other technologies in this area. If we highlight two major LPWAN
                technologies – Sigfox, and NB-IoT – the LoRaWAN technology performs below regarding
                the following features. The properties of the three technologies are summarized in
                Table 2.</p>
            <table-wrap>         
                <caption>
                    <title>Table 2. LoRaWAN, Sigfox, NB-IoT properties <xref ref-type="bibr" rid="r3">[3]</xref> <xref ref-type="bibr" rid="r12">[12]</xref> <xref ref-type="bibr" rid="r26">[26]</xref> <xref ref-type="bibr" rid="r27">[27]</xref>.</title>
                </caption> 
                <table border="0" style="border-collapse:  collapse;width:192pt" width="256">
                    <col width="64"/>
                    <tbody>
                        <tr>
                            <td rowspan="1" colspan="1"> </td>
                            <td rowspan="1" colspan="1">LoRaWAN</td>
                            <td rowspan="1" colspan="1">Sigfox</td>
                            <td rowspan="1" colspan="1">NB-IoT</td>
                        </tr>
                        <tr>
                            <td rowspan="1" colspan="1">Modulation</td>
                            <td rowspan="1" colspan="1">CSS</td>
                            <td rowspan="1" colspan="1">BPSK</td>
                            <td rowspan="1" colspan="1">QPSK</td>
                        </tr>
                        <tr>
                            <td rowspan="1" colspan="1">Frequency</td>
                            <td rowspan="1" colspan="1">868 MHz – ISM</td>
                            <td rowspan="1" colspan="1">868 MHz – ISM</td>
                            <td rowspan="1" colspan="1">LTE-licensed</td>
                        </tr>
                        <tr>
                            <td rowspan="1" colspan="1">Private network</td>
                            <td rowspan="1" colspan="1">Allowed</td>
                            <td rowspan="1" colspan="1">Not allowed</td>
                            <td rowspan="1" colspan="1">Not allowed</td>
                        </tr>
                        <tr>
                            <td rowspan="1" colspan="1">Maximum data rate</td>
                            <td rowspan="1" colspan="1">50 kbps</td>
                            <td rowspan="1" colspan="1">100 bps</td>
                            <td rowspan="1" colspan="1">200kbps</td>
                        </tr>
                        <tr>
                            <td rowspan="1" colspan="1">Maximum payload</td>
                            <td rowspan="1" colspan="1">12 bytes</td>
                            <td rowspan="1" colspan="1">243 bytes</td>
                            <td rowspan="1" colspan="1">1600 bytes</td>
                        </tr>
                        <tr>
                            <td rowspan="1" colspan="1">Data direction</td>
                            <td rowspan="1" colspan="1">Limited bidirectional</td>
                            <td rowspan="1" colspan="1">Bidirectional</td>
                            <td rowspan="1" colspan="1">Bidirectional</td>
                        </tr>
                        <tr>
                            <td rowspan="1" colspan="1">Message number</td>
                            <td rowspan="1" colspan="1">Unlimited</td>
                            <td rowspan="1" colspan="1">40 daily</td>
                            <td rowspan="1" colspan="1">Unlimited</td>
                        </tr>
                        <tr>
                            <td rowspan="1" colspan="1">Maximum range</td>
                            <td rowspan="1" colspan="1">15 km</td>
                            <td rowspan="1" colspan="1">40 km</td>
                            <td rowspan="1" colspan="1">20 km</td>
                        </tr>
                        <tr>
                            <td rowspan="1" colspan="1">Interference immunity</td>
                            <td rowspan="1" colspan="1">Very high</td>
                            <td rowspan="1" colspan="1">Very high</td>
                            <td rowspan="1" colspan="1">Low</td>
                        </tr>
                        <tr>
                            <td rowspan="1" colspan="1">Encryption</td>
                            <td rowspan="1" colspan="1">AES 128</td>
                            <td rowspan="1" colspan="1">Not supported</td>
                            <td rowspan="1" colspan="1">LTE encryption</td>
                        </tr>
                    </tbody>
                </table>      
            </table-wrap>
            <p>The maximum data rate of LoRaWAN technology is not the lowest, at 50 kbps. The length of the payload is 1600 bytes for NB-IoT and 243 bytes for LoRaWAN. It belongs to the middle field in terms of range (5-15 km). It is outstanding that LoRaWAN technology is actively immune to interference and uses AES-128 encryption during communication; the adaptive data rate is implemented, and built-in positioning is used. These technological characteristics affect the areas of application. It should be emphasized that a great advantage of LoRaWAN technology, compared to similar technologies, is that private networks can be implemented with it. The private network avoids dependence on the service provider. Also, the cost of LoRaWAN network equipment and the spectrum is the lowest.
                Some of the technology limits measured above have been presented. LoRaWAN end-devices implement at least Class A operation options, in addition to which Class B and C operations are optional <xref ref-type="bibr" rid="r13">[13]</xref>. The operation mode is vital in the case of bi-directional communication. Class A operation results in the nodes being able to receive only for a limited time after transmission. This way, messages sent to the end-device only arrive after the transmission period of the end-device, which can reduce the application areas. This problem does not exist for Class C operation. Communication takes place at 868 MHz or 433 MHz in Europe, in the ISM band <xref ref-type="bibr" rid="r13">[13]</xref>. As a result, the transmission time is also limited.
                The classic LoRaWAN network consists of end-devices, gateway(s), network- and application server(s) <xref ref-type="bibr" rid="r13">[13]</xref>. End-devices communicate with servers through gateways. It follows that the gateway is the weakest point in the network. There can be multiple gateways in a network, which increases the robustness of the communication. In addition to the implementation of private networks, it is also possible to use a service provider network and a network service.
                The conclusions to be drawn for smart city solutions are as follows. This technology is not the right choice in cases:
                •	at high data rates,
                •	in case of transmission of large data,
                •	in case of transmission of large amounts of data,
                •	continuous two-way communication is essential,
                •	and any combination thereof.
                In the case of collecting small measurement data that needs to be transmitted continuously but at infrequent intervals, this technology can be the right choice. A typical area of application is consumption metering. Unfortunately, developers also have to deal with changing user needs. Previously, it was appropriate to have meter readings taken monthly. In the case of a consumption meter with wireless communication, there are demands that users want to see the data continuously. Comparing the monthly meter readings with the continuous data provision, this seems unreasonable. Of course, the technology allows data to be provided more frequently than monthly.
            </p>
        </sec>
        <sec sec-type="ASPECTS OF THE CHALLENGES RELATED TO LORAWAN SPECIFICATIONS">
            <label>ASPECTS OF THE CHALLENGES RELATED TO LORAWAN SPECIFICATIONS</label>
            <p>The LoRa Alliance is responsible for LoRaWAN specifications and certification. Newer
                specifications are issued mainly for improvements, to correct bugs, and for
                clarifications <xref ref-type="bibr" rid="r28">[28]</xref> The specifications include everything that the LoRaWAN devices
                and networks must comply with. Compared to the 1,0 specification published in 2015,
                the next version (1.0.1) was released in early 2016 <xref ref-type="bibr" rid="r12">[12]</xref> <xref ref-type="bibr" rid="r14">[14]</xref>. This version mostly
                includes spelling corrections and clarifications. The next version, 1.0.2, was
                released in mid-2016 with some minor changes and fixes <xref ref-type="bibr" rid="r15">[15]</xref>. Subsequently,
                specification 1.1 was released in 2017, which resulted in significant changes <xref ref-type="bibr" rid="r15">[15]</xref>.
                In addition to clarifications, it contained several functional modifications. The
                changes that appeared were related to the following areas: frame counters, device
                classes, activation modes, keys and server structure. Version 1.0.3 was released in
                2018 and took over the parts for Class B devices from Specification 1.1. Previously,
                Class B (beacon) operations could only be encountered on a theoretical level <xref ref-type="bibr" rid="r13">[13]</xref>. 
                <table-wrap>         
                    <caption>
                        <title>Table 3. Number of smart city LoRaWAN devices in terms of specifications <xref ref-type="bibr" rid="r18">[18]</xref>.</title>
                    </caption> 
                    <table border="0" style="border-collapse:  collapse;width:336pt" width="448">
                        <col width="64"/>
                        <tbody>
                            <tr>
                                <td rowspan="1" colspan="1">LoRaWAN specification</td>
                                <td rowspan="1" colspan="1">1.0</td>
                                <td rowspan="1" colspan="1">1.0.1</td>
                                <td rowspan="1" colspan="1">1.0, 1.0.2</td>
                                <td rowspan="1" colspan="1">1.0.2</td>
                                <td rowspan="1" colspan="1">1.0.3</td>
                                <td rowspan="1" colspan="1">1.sij</td>
                            </tr>
                            <tr>
                                <td rowspan="1" colspan="1">Number of devices</td>
                                <td rowspan="1" colspan="1">6</td>
                                <td rowspan="1" colspan="1">38</td>
                                <td rowspan="1" colspan="1">0</td>
                                <td rowspan="1" colspan="1">82</td>
                                <td rowspan="1" colspan="1">1</td>
                                <td rowspan="1" colspan="1">0</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
            </p> 
            <p>Due to several innovations in the 1.1 specification, it is not popular with
                developers and operators. It is less understandable compared to the 1.0.x series
                <xref ref-type="bibr" rid="r28">[28]</xref>. If we look at the comparison tables (Table 3 and Table 4), it turns out that
                most of the products that meet the 1.0.2 specification are in all categories. Only
                one product meets the latest specification (1.0.3). Of course, the specifications
                are backwards compatible with each other. The conclusion is that using the latest
                specifications can avoid bugs and misunderstandings that can be found in older
                versions. It is recommended to use the 1.0.3 specification.
                <table-wrap>         
                    <caption>
                        <title>Table 4. Number of smart city LoRaWAN devices in terms of specifications and classification <xref ref-type="bibr" rid="r18">[18]</xref></title>
                    </caption> 
                    <table border="0" style="border-collapse:  collapse;width:288pt" width="384">
                        <col width="64"/>
                        <tbody>
                            <tr>
                                <td rowspan="1" colspan="1">Specification</td>
                                <td rowspan="1" colspan="1">Sensor node</td>
                                <td rowspan="1" colspan="1">Actuator node</td>
                                <td rowspan="1" colspan="1">Sensor interface unit</td>
                                <td rowspan="1" colspan="1">Meter interface unit</td>
                                <td rowspan="1" colspan="1">Tracker</td>
                            </tr>
                            <tr>
                                <td rowspan="1" colspan="1">1.0</td>
                                <td rowspan="1" colspan="1">5</td>
                                <td rowspan="1" colspan="1">0</td>
                                <td rowspan="1" colspan="1">0</td>
                                <td rowspan="1" colspan="1">1</td>
                                <td rowspan="1" colspan="1">0</td>
                            </tr>
                            <tr>
                                <td rowspan="1" colspan="1">1.0.1</td>
                                <td rowspan="1" colspan="1">22</td>
                                <td rowspan="1" colspan="1">1</td>
                                <td rowspan="1" colspan="1">2</td>
                                <td rowspan="1" colspan="1">7</td>
                                <td rowspan="1" colspan="1">6</td>
                            </tr>
                            <tr>
                                <td rowspan="1" colspan="1">1.0 and 1.0.2</td>
                                <td rowspan="1" colspan="1">0</td>
                                <td rowspan="1" colspan="1">0</td>
                                <td rowspan="1" colspan="1">0</td>
                                <td rowspan="1" colspan="1">0</td>
                                <td rowspan="1" colspan="1">0</td>
                            </tr>
                            <tr>
                                <td rowspan="1" colspan="1">1.0.2</td>
                                <td rowspan="1" colspan="1">55</td>
                                <td rowspan="1" colspan="1">2</td>
                                <td rowspan="1" colspan="1">4</td>
                                <td rowspan="1" colspan="1">16</td>
                                <td rowspan="1" colspan="1">5</td>
                            </tr>
                            <tr>
                                <td rowspan="1" colspan="1">1.0.3</td>
                                <td rowspan="1" colspan="1">1</td>
                                <td rowspan="1" colspan="1">0</td>
                                <td rowspan="1" colspan="1">0</td>
                                <td rowspan="1" colspan="1">0</td>
                                <td rowspan="1" colspan="1">0</td>
                            </tr>
                            <tr>
                                <td rowspan="1" colspan="1" align="right">1.sij</td>
                                <td rowspan="1" colspan="1">0</td>
                                <td rowspan="1" colspan="1">0</td>
                                <td rowspan="1" colspan="1">0</td>
                                <td rowspan="1" colspan="1">0</td>
                                <td rowspan="1" colspan="1">0</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap></p>
            <sec sec-type="ASPECTS OF THE CHALLENGES OF THE APPLICATION NATURE">
                <label>ASPECTS OF THE CHALLENGES OF THE APPLICATION NATURE</label>
                <p>Due to the nature of the application, we can group the devices according to
                    several aspects. One way of grouping comes from the place of use. According to
                    this, we can distinguish two groups: indoor devices and outdoor devices. Also,
                    it should be mentioned that there are devices that are used both indoors and
                    outdoors. Based on the installation of the devices, two groups can be
                    distinguished: fixed installation and mobile. These groupings are shown in Table
                    5 [29. The examined device groups cover several smart city application areas.
                    In the sensor node category, there are mostly simple sensor devices such as a
                    temperature meter, a humidity meter, a light sensor, an air pollution meter, and
                    a soil moisture meter. These devices can be used both outdoors and indoors,
                    mostly with a fixed installation. These statements are also valid for sensor
                    interface units. The actuator node category includes mainly devices related to
                    lighting control; they can be indoor and outdoor and have a fixed installation.
                    The metering interface units are mostly water consumption meter-, gas meter-,
                    and electricity meter interfaces; this means that there can be both indoor and
                    outdoor versions with fixed installation. Trackers are mostly used for outdoor
                    positioning, but some devices are used indoors. Trackers are specifically for
                    mobile applications. In the case of outdoor equipment, physical protection
                    should be provided, and it is important to take weather factors into account.
                    The physical protection is not specifically a LoRaWAN technology issue; the
                    technology is less sensitive to external disturbances and environmental factors.
                    However, for mobile applications, device movement can be a problem. In other
                    words, the movement of the device causes a change in the radio parameters, so it
                    is recommended to turn on the adaptive data rate (ADR) when the device is not in
                    motion, which often happens in mobile applications <xref ref-type="bibr" rid="r13">[13]</xref>. 
                    <table-wrap>         
                        <caption>
                            <title>Table 5. Categorization of certified LoRaWAN smart city devices by applications [29.</title>
                        </caption> 
                        <table border="0" style="border-collapse:  collapse;width:288pt" width="384">
                            <col width="64"/>
                            <tbody>
                                <tr>
                                    <td rowspan="1" colspan="1"> </td>
                                    <td rowspan="1" colspan="1">Sensor node</td>
                                    <td rowspan="1" colspan="1">Actuator node</td>
                                    <td rowspan="1" colspan="1">Sensor interface unit</td>
                                    <td rowspan="1" colspan="1">Meter interface unit</td>
                                    <td rowspan="1" colspan="1">Tracker</td>
                                </tr>
                                <tr>
                                    <td rowspan="1" colspan="1">Typical applications</td>
                                    <td rowspan="1" colspan="1">Temperature measurement, humidity
                                        measurement, motion detection, light intensity measurement,
                                        soil moisture measurement, consumption measurement, parking
                                        sensor</td>
                                    <td rowspan="1" colspan="1">Lighting control</td>
                                    <td rowspan="1" colspan="1">Temperature measurement, humidity
                                        measurement, motion detection, light intensity measurement,
                                        soil moisture measurement</td>
                                    <td rowspan="1" colspan="1">Electricity consumption measurement,
                                        water consumption meter, gas consumption meter, heat
                                        quantity measurement</td>
                                    <td rowspan="1" colspan="1">Person tracking, vehicle tracking,
                                        package tracking, animal tracking</td>
                                </tr>
                                <tr>
                                    <td rowspan="1" colspan="1">Indoor/ Outdoor</td>
                                    <td rowspan="1" colspan="1">Indoor/ Outdoor</td>
                                    <td rowspan="1" colspan="1">Mostly indoor</td>
                                    <td rowspan="1" colspan="1">Indoor/ Outdoor</td>
                                    <td rowspan="1" colspan="1">Indoor/ Outdoor</td>
                                    <td rowspan="1" colspan="1">Mostly outdoor</td>
                                </tr>
                                <tr>
                                    <td rowspan="1" colspan="1">Installation</td>
                                    <td rowspan="1" colspan="1">Mostly fixed</td>
                                    <td rowspan="1" colspan="1">Fixed</td>
                                    <td rowspan="1" colspan="1">Mostly fixed</td>
                                    <td rowspan="1" colspan="1">Fixed</td>
                                    <td rowspan="1" colspan="1">Mobile</td>
                                </tr>
                            </tbody>
                        </table>
                    </table-wrap></p>
                <p>As LoRaWAN end-devices are mainly battery-operated, special attention must be paid to monitoring the supply voltage and selecting the appropriate battery. Also, different antennas may be required for the same products, depending on the installation <xref ref-type="bibr" rid="r17">[17]</xref>.</p>
    </sec>
            <sec sec-type="CONCLUSION">
                <label>CONCLUSION</label>        
                <p>It is not news that there are many products in smart city solutions that use LoRaWAN technology. These products can be generally used for a wide variety of purposes, but especially, for data collection tasks. The technology also makes it possible to create private networks, which further increases its use. In addition to the current use cases, new directions are conceivable, which no longer provide a convenience function, but become necessary. In light of all this, there is a need for technology-related studies, measurements, and analyzes.
                    The study examined products that have LoRaWAN certification. The certified devices were categorized into eight groups, of which five groups were further examined: sensor node, sensor interface node, sensor interface unit, measuring interface unit and tracker. Of the application challenges, three main groups were identified: technology aspects, specification aspects and application nature aspects. The study does not address information security aspects. It can be stated that LoRaWAN technology also has several positively outstanding features compared to competing technologies. In addition, there are technology limitations (data rate, payload size, limited receive- and transmit time) that limit the scope of applicability. The results of the classification based on the LoRaWAN specification show that most of the certified devices conforming to the 1.0.2 specification. There is only one product that meets the 1.0.3 specification. A challenge is to meet the latest specifications for LoRaWAN smart city devices and complete the authentication process. For the application, the outdoor/indoor devices and the challenges of the installation method were identified. From a technological point of view, the main focus is on mobile applications, as they have to meet regularly changing environmental and radio parameters.
                    Future research work can be pursued in several directions. The areas currently considered can be further examined about the identified groups. Newer certified LoRaWAN products and new specifications should also be considered during reviews. The area of investigation aspects can be expanded with information security issues, examining this for network participants. By expanding the study areas and aspects, we can get a more comprehensive picture of the challenges related to LoRaWAN smart city solutions. If we know the challenges, recommendations can be made for LoRaWAN smart city applications.
                </p>  </sec>
        </sec>       
    </body>
    <back>        
       <ref-list>
           <ref id="r1">
               <label>1</label>
               <mixed-citation publication-type="data" publication-format="electronic">
                   <collab>IoT Analytics: IoT 2019 in Review</collab>.
                   <data-title>The 10 Most Relevant IoT Developments of the Year</data-title>.
                   (<date>
                       <year>2019</year>
                   </date>)
                   <date-in-citation content-type="access-date">
                       <year>10th January 2020</year>.
                   </date-in-citation>
                   <ext-link ext-link-type="uri">http://iot-analytics.com/iot-2019-in-review</ext-link>                 
               </mixed-citation>
           </ref>
           <ref id="r2">
               <label>2</label>
               <mixed-citation publication-type="data" publication-format="electronic">
                   <collab>Loriot</collab>.
                   <data-title>10 relevant IoT trends in 2020</data-title>.
                   (<date>
                       <year>2019</year>
                   </date>)
                   <date-in-citation content-type="access-date">
                       <year>10th January 2020</year>.
                   </date-in-citation>
                   <ext-link ext-link-type="uri">http://loriot.io/blog/IoT-trends-2020.html</ext-link>                 
               </mixed-citation>
           </ref>
           <ref id="r3">
               <label>3</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Bajica</surname><given-names>E.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2019</year></date>. <article-title>A comparative study of LPWAN technologies for large-scale IoT deployment</article-title>.
                   <source>ICT Express</source>,
                   <volume>5</volume>,
                   <issue>1</issue>
                   <fpage>1</fpage>-<lpage>7</lpage>. <pub-id pub-id-type="doi">10.1016/j.icte.2017.12.005</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.1016/j.icte.2017.12.005"/>
               </mixed-citation>
           </ref>
           <ref id="r4">
               <label>4</label>
               <mixed-citation publication-type="data" publication-format="electronic">
                   <collab>Semtech</collab>.
                   <data-title>What is LoRa?</data-title>.      
                   <date-in-citation content-type="access-date">
                       <year>9th January 2020</year>.
                   </date-in-citation>
                   <ext-link ext-link-type="uri">http://www.semtech.com/lora/what-islora#:~:text=The%20LoRaWAN%20open%20specification
                       %20is%20a%20low%20power%2C,in%20the%20Industrial%2C%20Scientific%20and%20Medical%20%28ISM%29%20band
                   </ext-link>                 
               </mixed-citation>
           </ref>
           <ref id="r5">
               <label>5</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Alalouch</surname><given-names>C.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2019</year></date>. <article-title>Towards smart sustainable cities: A review of the role digital citizen participation could play in advancing social sustainability</article-title>.
                   <source>Sustainable Cities and Society</source>,
                   <volume>50</volume>,
                   <fpage>1</fpage>-<lpage>15</lpage>. <pub-id pub-id-type="doi">10.1016/j.scs.2019.101627</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.1016/j.scs.2019.101627"/>
               </mixed-citation>
           </ref>
           <ref id="r6">
               <label>6</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Alba</surname><given-names>E.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2019</year></date>. <article-title>Smart City and information technology: A review</article-title>.
                   <source>Cities</source>,
                   <volume>93</volume>,
                   <fpage>84</fpage>-<lpage>94</lpage>. <pub-id pub-id-type="doi">10.1016/j.cities.2019.04.014</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.1016/j.cities.2019.04.014"/>
               </mixed-citation>
           </ref>
           <ref id="r7">
               <label>7</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Almehmadi</surname><given-names>A.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2019</year></date>. <article-title>A survey of privacy enhancing technologies for smart cities.</article-title>.
                   <source>Pervasive and Mobile Computing</source>,
                   <volume>55</volume>,
                   <fpage>76</fpage>-<lpage>95</lpage>. <pub-id pub-id-type="doi">10.1016/j.pmcj.2019.03.001</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.1016/j.pmcj.2019.03.001"/>
               </mixed-citation>
           </ref>
           <ref id="r8">
               <label>8</label>
               <mixed-citation publication-type="data" publication-format="electronic">
                   <collab>LoRa Alliance</collab>.
                   <data-title>LoRa Alliance</data-title>.      
                   <date-in-citation content-type="access-date">
                       <year>10th January 2020</year>.
                   </date-in-citation>
                   <ext-link ext-link-type="uri">http://lora-alliance.org</ext-link>                 
               </mixed-citation>
           </ref>
           <ref id="r9">
               <label>9</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Mroue</surname><given-names>H.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2020</year></date>. <article-title>LoRa+: An extension of LoRaWAN protocol to reduce infrastructure costs by improving the Quality of Service</article-title>.
                   <source>Internet of Things</source>,
                   <volume>9</volume>,
                   <fpage>1</fpage>-<lpage>13</lpage>. <pub-id pub-id-type="doi">10.1016/j.iot.2020.100176</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.1016/j.iot.2020.100176"/>
               </mixed-citation>
           </ref>
           <ref id="r10">
               <label>10</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Carvalho</surname><given-names>D.F.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2019</year></date>. <article-title>A test methodology for evaluating architectural delays of LoRaWAN implementations</article-title>.
                   <source>Pervasive and Mobile Computing</source>,
                   <volume>56</volume>,
                   <fpage>1</fpage>-<lpage>17</lpage>. <pub-id pub-id-type="doi">10.1016/j.pmcj.2019.03.002</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.1016/j.pmcj.2019.03.002"/>
               </mixed-citation>
           </ref>
           <ref id="r11">
               <label>11</label>
               <mixed-citation publication-type="data" publication-format="electronic">
                   <collab>LoRa Alliance</collab>.
                   <data-title>About LoRa Alliance</data-title>.      
                   <date-in-citation content-type="access-date">
                       <year>12th January 2020</year>.
                   </date-in-citation>
                   <ext-link ext-link-type="uri">http://lora-alliance.org/about-lora-alliance</ext-link>                 
               </mixed-citation>
           </ref>
           <ref id="r12">
               <label>12</label>
               <mixed-citation publication-type="data" publication-format="electronic">
                   <collab>LoRa Alliance</collab>.
                   <data-title>LoRaWAN Specification V1.0.</data-title>.
                   (<date>
                       <year>2015</year>
                   </date>)
                   <date-in-citation content-type="access-date">
                       <year>10th January 2020</year>.
                   </date-in-citation>
                   <ext-link ext-link-type="uri">http://lora-alliance.org/sites/default/files/2018-05/2015_-_lorawan_specification_1r0_611_1.pdf</ext-link>                 
               </mixed-citation>
           </ref>
           <ref id="r13">
               <label>13</label>
               <mixed-citation publication-type="data" publication-format="electronic">
                   <collab>LoRa Alliance</collab>.
                   <data-title>LoRaWAN Specification V1.0.3</data-title>.
                   (<date>
                       <year>2018</year>
                   </date>)
                   <date-in-citation content-type="access-date">
                       <year>10th January 2020</year>.
                   </date-in-citation>
                   <ext-link ext-link-type="uri">http://lora-alliance.org/sites/default/files/2018-07/lorawan1.0.3.pdf</ext-link>                 
               </mixed-citation>
           </ref>
           <ref id="r14">
               <label>14</label>
               <mixed-citation publication-type="data" publication-format="electronic">
                   <collab>LoRa Alliance</collab>.
                   <data-title>LoRaWAN Specification V1.0.1</data-title>.
                   (<date>
                       <year>2016</year>
                   </date>)
                   <date-in-citation content-type="access-date">
                       <year>10th January 2020</year>.
                   </date-in-citation>
                   <ext-link ext-link-type="uri">http://lora-alliance.org/sites/default/files/2018-05/lorawan1.0.1final_05apr2016_1099_1.pdf</ext-link>                 
               </mixed-citation>
           </ref>
           <ref id="r15">
               <label>15</label>
               <mixed-citation publication-type="data" publication-format="electronic">
                   <collab>LoRa Alliance</collab>.
                   <data-title>LoRaWAN Specification V1.0.2</data-title>.
                   (<date>
                       <year>2016</year>
                   </date>)
                   <date-in-citation content-type="access-date">
                       <year>10th January 2020</year>.
                   </date-in-citation>
                   <ext-link ext-link-type="uri">http://lora-alliance.org/sites/default/files/2018-05/lorawan1_0_2-20161012_1398_1.pdf</ext-link>                 
               </mixed-citation>
           </ref>
           <ref id="r16">
               <label>16</label>
               <mixed-citation publication-type="data" publication-format="electronic">
                   <collab>LoRa Alliance</collab>.
                   <data-title>LoRaWAN Specification V1.1</data-title>.
                   (<date>
                       <year>2017</year>
                   </date>)
                   <date-in-citation content-type="access-date">
                       <year>10th January 2020</year>.
                   </date-in-citation>
                   <ext-link ext-link-type="uri">http://lora-alliance.org/sites/default/files/2018-04/lorawantm_specification_-v1.1.pdf</ext-link>                 
               </mixed-citation>
           </ref>
           <ref id="r17">
               <label>17</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Hatoum</surname><given-names>T.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2020</year></date>. <article-title>LoRaWAN security survey: Issues, threats and possible mitigation techniques</article-title>.
                   <source>Internet of Things</source>,
                   <volume>12</volume>,
                   <fpage>1</fpage>-<lpage>37</lpage>. <pub-id pub-id-type="doi">10.1016/j.iot.2020.100303</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.1016/j.iot.2020.100303"/>
               </mixed-citation>
           </ref>
           <ref id="r18">
               <label>18</label>
               <mixed-citation publication-type="data" publication-format="electronic">
                   <collab>LoRa Alliance</collab>.
                   <data-title>Certified Products</data-title>.
                   <date-in-citation content-type="access-date">
                       <year>20th April 2020</year>.
                   </date-in-citation>
                   <ext-link ext-link-type="uri">http://lora-alliance.org/showcase/search?is_certified=1&#38;categories_single=All&#38;a=</ext-link>                 
               </mixed-citation>
           </ref>
           <ref id="r19">
               <label>19</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Muthanna</surname><given-names>M.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2021</year></date>. <article-title>Cognitive control models of multiple access IoT networks using LoRa technology</article-title>.
                   <source>Cognitive Systems Research</source>,
                   <volume>65</volume>,
                   <fpage>62</fpage>-<lpage>73</lpage>.<pub-id pub-id-type="doi">10.1016/j.cogsys.2020.09.002</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.1016/j.cogsys.2020.09.002"/>
               </mixed-citation>
           </ref>
           <ref id="r20">
               <label>20</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Centelles</surname><given-names>R.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2021</year></date>. <article-title>LoRaMoto: A communication system to provide safety awareness among civilians after an earthquake</article-title>.
                   <source>Future Generation Computer Systems</source>,
                   <volume>115</volume>,
                   <fpage>150</fpage>-<lpage>170</lpage>. <pub-id pub-id-type="doi">10.1016/j.future.2020.07.040</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.1016/j.future.2020.07.040"/>
               </mixed-citation>
           </ref>
           <ref id="r21">
               <label>21</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Takamure</surname><given-names>K.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2021</year></date>. <article-title>Development of a self-powered wireless sensor node to measure the water flowrate by using a turbine flowmeter</article-title>.
                   <source>Internet of Things</source>,
                   <volume>13</volume>,
                   <fpage>1</fpage>-<lpage>13</lpage>. <pub-id pub-id-type="doi">10.1016/j.iot.2020.100327</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.1016/j.iot.2020.100327"/>
               </mixed-citation>
           </ref>
           <ref id="r22">
               <label>22</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Mohammed</surname><given-names>S.L.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2020</year></date>. <article-title>Accurate fall detection for patients with Parkinson’s disease based on a data event algorithm and wireless sensor nodes</article-title>.
                   <source>Measurement</source>,
                   <volume>156</volume>,
                   <fpage>1</fpage>-<lpage>18</lpage>. <pub-id pub-id-type="doi">10.1016/j.measurement.2020.107573</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.1016/j.measurement.2020.107573"/>
               </mixed-citation>
           </ref>
           <ref id="r23">
               <label>23</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Sahoo</surname><given-names>B.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2018</year></date>. <article-title>Sensing and Actuation as a Service Delivery Model in Cloud Edge centric Internet of Things</article-title>.
                   <source>Future Generation Computer Systems</source>,
                   <volume>86</volume>,
                   <fpage>281</fpage>-<lpage>296</lpage>. <pub-id pub-id-type="doi">10.1016/j.future.2018.04.015</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.1016/j.future.2018.04.015"/>
               </mixed-citation>
           </ref>
           <ref id="r24">
               <label>24</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Heinssen</surname><given-names>S.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2018</year></date>. <article-title>Design for reliability of generic sensor interface circuits</article-title>.
                   <source>Microelectronics Reliability</source>,
                   <volume>80</volume>,
                   <fpage>184</fpage>-<lpage>197</lpage>. <pub-id pub-id-type="doi">10.1016/j.microrel.2017.11.029</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.1016/j.microrel.2017.11.029"/>
               </mixed-citation>
           </ref>
           <ref id="r25">
               <label>25</label>
               <mixed-citation publication-type="data" publication-format="electronic">
                   <collab>Smallbon V.</collab>.
                   <data-title>Energy efficient LoRa GPS tracker for dementia patients</data-title>.
                   (<date>
                       <year>2017</year>
                   </date>)
                   <date-in-citation content-type="access-date">
                       <year>10th November 2020</year>.
                   </date-in-citation>
                   <ext-link ext-link-type="uri">http://ieeexplore.ieee.org/abstract/document/8036938</ext-link>                 
               </mixed-citation>
           </ref>
           <ref id="r26">
               <label>26</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Bourennane</surname><given-names>E.M.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2020</year></date>. <article-title>A study of LoRaWAN protocol performance for IoT applications in smart agriculture.</article-title>.
                   <source>Computer Communications</source>,
                   <volume>164</volume>,
                   <fpage>148</fpage>-<lpage>157</lpage>. <pub-id pub-id-type="doi">10.1016/j.comcom.2020.10.009</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.1016/j.comcom.2020.10.009"/>
               </mixed-citation>
           </ref>
           <ref id="r27">
               <label>27</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Giannoulis</surname><given-names>S.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2018</year></date>. <article-title>Modelling the energy consumption for over-the-air software updates in LPWAN networks: SigFox, LoRa and IEEE 802.15.4g</article-title>.
                   <source>Internet of Things</source>,
                   <volume>3-4</volume>,
                   <fpage>104</fpage>-<lpage>119</lpage>. <pub-id pub-id-type="doi">10.1016/j.iot.2018.09.010</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.1016/j.iot.2018.09.010"/>
               </mixed-citation>
           </ref>
           <ref id="r28">
               <label>28</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Pereira</surname><given-names>N.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2019</year></date>. <article-title>Security Risk Analysis of LoRaWAN and Future Directions</article-title>.
                   <source>Future Internet</source>,
                   <volume>11</volume>,
                   <issue>3</issue>
                   <fpage>1</fpage>-<lpage>22</lpage>. <pub-id pub-id-type="doi">10.3390/fi11010003</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.3390/fi11010003"/>
               </mixed-citation>
           </ref>
           <ref id="r29">
               <label>29</label>
               <mixed-citation publication-type="journal">
                   <person-group person-group-type="author">
                       <name><surname>Yoo</surname><given-names>S.G.</given-names></name>
                   </person-group>
                   <date date-type="pub"><year>2019</year></date>. <article-title>A Comprehensive Study of the Use of LoRa in the Development of Smart Cities.</article-title>.
                   <source>Applied Science</source>,
                   <volume>19</volume>,
                   <fpage>1</fpage>-<lpage>39</lpage>. <pub-id pub-id-type="doi">10.3390/app9224753</pub-id>
                   <ext-link ext-link-type="url" xlink:href="http://dx.doi.org/10.3390/app9224753"/>
               </mixed-citation>
           </ref>
        </ref-list>
    </back>
</article>
