<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="13143" 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/13143?output=omeka-xml" accessDate="2026-05-30T14:53:42+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="80935">
              <text>Additively Composite Model Objective Function for Routing Protocol for Low-Power and Lossy Network Protocol</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="80936">
              <text>bottleneck routing; IoT; load balancing; metrics; objective function; RPL</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="80937">
              <text>The Internet of Things (IoT) networks always operate within the context of diverse and constrained characteristics of the devices. Low-Power and Lossy Networks (LLNs) constitute a network architecture commonly utilized in IoT application deployments, facilitating networking and the establishment of paths for data transmission. The Routing Protocol for Low-Power and Lossy Networks (RPL) demonstrates promising capabilities for LLN network operations, supporting IPv4 and IPv6-enabled services. The RPL protocol constructs a Destination Oriented Directed Acyclic Graph (DODAG) logical routing topology based on defined Objective Function (OF) metrics. Routing operations within the DODAG utilize these metrics and constraints to select parent nodes and calculate optimal routes between two nodes. Standardized OFs have traditionally focused on either parent node selection or routing objectives within the DODAG, often treating load balancing and bottleneck optimization separately. However, their combined impact on RPL's effectiveness has been overlooked. This paper introduces an Adaptively Composite Objective Function (AC-OF) approach that considers the combined objectives of DODAG load balancing and optimized routing operations. Through simulation evidence, the paper presents improved network parameters. The AC-OF implementation brings out significant results in the form of a balanced DODAG topology and it has good impacts on data transmission, control overhead messages, parent switching, delay, energy consumption, and node lifetime.  2024 Totem Publisher, Inc. 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="80938">
              <text>Poorana Senthilkumar S.; Wilfred Blessing N.R.; Subramani B.; Rajesh Kanna R.</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="80939">
              <text>International Journal of Performability Engineering, Vol-20, No. 5, pp. 300-311.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="80940">
              <text>Totem Publisher Inc.</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="80941">
              <text>2024-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="80942">
              <text>&lt;a href="https://doi.org/10.23940/ijpe.24.05.p5.300311" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.23940/ijpe.24.05.p5.300311&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85207487433&amp;amp;doi=10.23940%2Fijpe.24.05.p5.300311&amp;amp;partnerID=40&amp;amp;md5=38e25d24db663efffff51e2b7756dd53" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85207487433&amp;amp;doi=10.23940%2fijpe.24.05.p5.300311&amp;amp;partnerID=40&amp;amp;md5=38e25d24db663efffff51e2b7756dd53&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="80943">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="80944">
              <text>ISSN: 9731318</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="80945">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="80946">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="80947">
              <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="80948">
              <text>Poorana Senthilkumar S., Department of Computer Applications, Dr. N.G.P. Arts and Science College, Tamil Nadu, India; Wilfred Blessing N.R., College of Computing and Information Sciences, University of Technology and Applied Sciences, Ibri, Oman; Subramani B., Department of Computer Science, SNMV College of Arts and Science, Tamil Nadu, India; Rajesh Kanna R., Department of Computer Science, Christ University, Karnataka, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
