<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="13428" 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/13428?output=omeka-xml" accessDate="2026-05-03T03:09:26+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="84910">
              <text>Energy-efficient and secure routing strategy for opportunistic data transmission in WSNs</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="84911">
              <text>attackers; energy consumption; opportunistic; security; WSN</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="84912">
              <text>Driven by the critical importance of routing in Wireless Sensor Networks (WSNs) and the security vulnerabilities present in existing protocols, this research aims to address the key challenges in securing WSNs. Many current routing protocols focus on computational efficiency but fall short of providing strong security measures, leaving them vulnerable to malicious attacks. Reactive protocols, often preferred for their reduced bandwidth usage, heighten security concerns due to their limited resources for maintaining network routes, while proactive alternatives require more resources. Additionally, the ad hoc nature and energy limitations of WSNs make traditional security models, designed for wired and wireless networks, impractical. To overcome these limitations, this paper introduces the Secured Energy-Efficient Opportunistic Routing Scheme for sustainable WSNs. The proposed protocol is designed to enhance security by continuously updating neighbor information and verifying the validity of routing parameters, while also being power-aware, a critical factor given the energy constraints of WSNs. The protocol has been evaluated through simulation experiments, measuring key performance indicators such as throughput, average end-to-end delay (E2 delay), energy consumption, and network lifetime. The results demonstrate that the proposed protocol effectively strengthens WSN security while addressing the unique operational constraints of these networks.  2024 The Author(s). Published by Informa UK Limited, trading as Taylor &amp;amp; Francis Group.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="84913">
              <text>Narayana P.; Keerthi K.; Khalaf O.I.; Chithaluru P.; Patil M.A.; Tumula S.; Jayaram D.; Sharif M.S.</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="84914">
              <text>Journal of Cyber Security Technology</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="84915">
              <text>Taylor and Francis Ltd.</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="84916">
              <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="84917">
              <text>&lt;a href="https://doi.org/10.1080/23742917.2024.2431355" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1080/23742917.2024.2431355&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85210908911&amp;amp;doi=10.1080%2F23742917.2024.2431355&amp;amp;partnerID=40&amp;amp;md5=c712710194fe1e0390cf46c537de15fb" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85210908911&amp;amp;doi=10.1080%2f23742917.2024.2431355&amp;amp;partnerID=40&amp;amp;md5=c712710194fe1e0390cf46c537de15fb&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="84918">
              <text>All Open Access; Hybrid Gold Open Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="84919">
              <text>ISSN: 23742917</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="84920">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="84921">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="84922">
              <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="84923">
              <text>Narayana P., Department of Computer Science and Engineering, Stanley College of Engineering and Technology for Women, Hyderabad, India; Keerthi K., Department of Computer Science and Engineering, Methodist College of Engineering and Technology, Hyderabad, India; Khalaf O.I., Department of Solar, Al-Nahrain Research Center for Renewable Energy, Al-Nahrain University, Baghdad, Iraq; Chithaluru P., School of Computer Science and Engineering (SCOPE), VIT-AP University, Andhra Pradesh, Amaravati, India; Patil M.A., Department of Computer Science and Engineering, Christ (Deemed to be University, School of Engineering and Technology, Bengaluru, Kengeri, India, Department of Computer Science and Engineering, G. Narayanamma Institute of Technology and Science, Hyderabad, Shaikpet, India; Tumula S., Department of Computer Science and Engineering, G. Narayanamma Institute of Technology and Science, Hyderabad, Shaikpet, India; Jayaram D., Department of Information Technology, Chaitanya Bharathi Institute of Technology (A), Hyderabad, India; Sharif M.S., Intelligent Technologies Research Group, Computer Science and DT, ACE, UEL, University Way, London, United Kingdom</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
