<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="15478" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/15478?output=omeka-xml" accessDate="2026-05-21T13:17:23+00:00">
  <collection collectionId="5">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64">
                <text>Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="113441">
              <text>Improved dhoa-fuzzy based load scheduling in iot cloud environment</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="113442">
              <text>Cloud computing; Fuzzy logic; Internet of things; Load scheduling; Metaheuristics</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="113443">
              <text>Internet of things (IoT) has been significantly raised owing to the development of broadband access network, machine learning (ML), big data analytics (BDA), cloud computing (CC), and so on. The development of IoT technologies has resulted in a massive quantity of data due to the existence of several people linking through distinct physical components, indicating the status of the CC environment. In the IoT, load scheduling is realistic technique in distinct data center to guarantee the network suitability by falling the computer hardware and software catastrophe and with right utilize of resource. The ideal load balancer improves many factors of Quality of Service (QoS) like resource performance, scalability, response time, error tolerance, and efficiency. The scholar is assumed as load scheduling a vital problem in IoT environment. There are many techniques accessible to load scheduling in IoT environments.With this motivation, this paper presents an improved deer hunting optimization algorithm with Type II fuzzy logic (IDHOA-T2F) model for load scheduling in IoT environment. The goal of the IDHOA-T2F is to diminish the energy utilization of integrated circuit of IoT node and enhance the load scheduling in IoT environments. The IDHOA technique is derived by integrating the concepts of Nelder Mead (NM) with the DHOA. The proposed model also synthesized the T2L based on fuzzy logic (FL) systems to counterbalance the load distribution. The proposed model finds useful to improve the efficiency of IoT system. For validating the enhanced load scheduling performance of the IDHOA-T2F technique, a series of simulations take place to highlight the improved performance. The experimental outcomes demonstrate the capable outcome of the IDHOA-T2F technique over the recent techniques.  2022 Tech Science Press. All rights reserved.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="113444">
              <text>Joshua Samuel Raj R.; Ilango V.; Thomas P.; Uma V.R.; Al-Wesabi F.N.; Marzouk R.; Hilal A.M.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="113445">
              <text>Computers, Materials and Continua, Vol-71, No. 2, pp. 4101-4114.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="113446">
              <text>Tech Science Press</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="113447">
              <text>2022-01-01</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="113448">
              <text>&lt;a href="https://doi.org/10.32604/cmc.2022.022063" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.32604/cmc.2022.022063&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85120801301&amp;amp;doi=10.32604%2Fcmc.2022.022063&amp;amp;partnerID=40&amp;amp;md5=0a6c802914a3da1d57738db9a03f8aed" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85120801301&amp;amp;doi=10.32604%2fcmc.2022.022063&amp;amp;partnerID=40&amp;amp;md5=0a6c802914a3da1d57738db9a03f8aed&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="113449">
              <text>All Open Access; Gold Open Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="113450">
              <text>ISSN: 15462218</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="113451">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="113452">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="113453">
              <text>Article</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="113454">
              <text>Joshua Samuel Raj R., Department of Information Science and Engineering, CMR Institute of Technology, Bengaluru, 560037, India; Ilango V., Department of Computer Application, CMR Institute of Technology, Bangalore, 560037, India; Thomas P., School of Computing, Woldia Institute of Technology, Woldia University, Ethiopia, Ethiopia; Uma V.R., Department of Commerce, School of Commerce. Finance and Accountancy, Christ University, Bangalore, 560029, India; Al-Wesabi F.N., Department of Computer Science, College of Science and Art at Mahayil, King Khalid University, Saudi Arabia, Faculty of Computer and IT, Sana'a University, Yemen, Yemen; Marzouk R., Department of Information Systems, College of Computer and Information Sciences, Princess Nourah Bint Abdulrahman University, Saudi Arabia; Hilal A.M., Department of Computer and Self Development, Preparatory Year Deanship, Prince Sattam bin Abdulaziz University, Alkharj, Saudi Arabia</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
