1 Ocak 2022 Dergi makalesi Açık Erişim

Dilek, Selma; Irgan, Kerem; Guzel, Metehan; Ozdemir, Suat; Baydere, Sebnem; Charnsripinyo, Chalermpol

MARC21 XML

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <controlfield tag="001">254013</controlfield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="a">Creative Commons Attribution</subfield>
    <subfield code="u">http://www.opendefinition.org/licenses/cc-by</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="4">
    <subfield code="v">35</subfield>
    <subfield code="p">INTERNATIONAL JOURNAL OF COMMUNICATION SYSTEMS</subfield>
    <subfield code="n">10</subfield>
  </datafield>
  <controlfield tag="005">20230728201146.0</controlfield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">The vast number of smart cloud applications that communicate with the "things" over a variety of physical networks and communication protocols contribute to the rise of complexity in Internet of Things (IoT) systems. The diversity of end-user requirements related to the volume of generated data, its variety, and the velocity of its transmission makes quality of service (QoS) provisioning even more crucial and challenging in IoT. This paper provides a comprehensive and up-to-date survey of QoS support in IoT networks and communication protocols. An analysis of the QoS-aware IoT architectures, layer-dependent QoS metrics, and network resource optimization methods utilized in IoT systems are given. The limitations of the current state-of-the-art studies for efficient delivery of QoS metrics are discussed. The paper concludes with future research directions on end-to-end QoS provisioning in IoT.</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">QoS-aware IoT networks and protocols: A comprehensive survey</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">user-tubitak-destekli-proje-yayinlari</subfield>
    <subfield code="o">oai:aperta.ulakbim.gov.tr:254013</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">Hacettepe Univ, Dept Comp Engn, Ankara, Turkey</subfield>
    <subfield code="a">Dilek, Selma</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-tubitak-destekli-proje-yayinlari</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="z">md5:f54254f6b533d63fbc231a10ee52cd52</subfield>
    <subfield code="s">203</subfield>
    <subfield code="u">https://aperta.ulakbim.gov.trrecord/254013/files/bib-117f4fe2-3ca9-41cd-9ca6-9f9a9c36ec04.txt</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="2">doi</subfield>
    <subfield code="a">10.1002/dac.5156</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Yeditepe Univ, Dept Comp Engn, Istanbul, Turkey</subfield>
    <subfield code="a">Irgan, Kerem</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Gazi Univ, Dept Comp Engn, Ankara, Turkey</subfield>
    <subfield code="a">Guzel, Metehan</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Hacettepe Univ, Dept Comp Engn, Ankara, Turkey</subfield>
    <subfield code="a">Ozdemir, Suat</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Yeditepe Univ, Dept Comp Engn, Istanbul, Turkey</subfield>
    <subfield code="a">Baydere, Sebnem</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Natl Sci &amp; Technol Dev Agcy Thailand, Bangkok, Thailand</subfield>
    <subfield code="a">Charnsripinyo, Chalermpol</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">article</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2022-01-01</subfield>
  </datafield>
</record>