<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="19508" 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/19508?output=omeka-xml" accessDate="2026-04-08T23:40:34+00:00">
  <collection collectionId="16">
    <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="51377">
                <text>Conference Papers</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="28">
    <name>Conference Paper</name>
    <description>Faculty Publications- Conference Papers</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="168734">
              <text>A Novel Two-Step Bayesian Hyperparameter Optimization Strategy for DoS Attack Detection in IoT</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="168735">
              <text>Bayesian Optimization; Comparative analysis of Hyperparameters values in Machine Learning; Denial of Service attack in IoT; Hyperparameter Optimization; Machine Learning</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="168736">
              <text>Variations of Hyperparameter in Machine Learning (ML) algorithm effectively strikes the model's performance in terms of accuracy, loss, F1 score and many others. In the current study a two-step hyperparameter optimization approach is represented to analyse selected ML models' performance in detecting specific Denial of Service attacks in IoT. These attacks are Synchronization Flooding Attack at Transport layer, DIS Flooding attack and Sinkhole attack at Network layer. The two-step approach is a combination of Manual Hyperparameter tuning followed by Bayesian Optimization technique. The first stage manually analyses the hyperparameters of ML algorithms by considering the nature of the attack datasets. This technique is quite rigorous as it demands thorough analysis of the dependencies of the nature of datasets with hyperparameter types. At the same time this process is time consuming. The output of the first stage is the ranges of independent hyperparameter values that give maximum accuracy (minimum error rate). In the next stage Bayesian Hyperparameter tuning is used to specifically derive the single set of all hyperparameters values that give optimized accuracy faster than the BO. The input to the second stage is the ranges of individual hyperparameters that gave maximum accuracy in the first stage. The efficiency of the approach is depicted by comparative analysis of training time between the proposed and existing BO. NetSim simulator is used for generating attack datasets and Python packages are used for executing the two-step approach.   2024 IEEE.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="168737">
              <text>Sinha S.; Choudhary S.; Paul A.</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="168738">
              <text>2nd International Conference on Intelligent Data Communication Technologies and Internet of Things, IDCIoT 2024, pp. 112-119.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="168739">
              <text>Institute of Electrical and Electronics Engineers 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="168740">
              <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="168741">
              <text>&lt;a href="https://doi.org/10.1109/IDCIoT59759.2024.10467454" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/IDCIoT59759.2024.10467454&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85190147837&amp;amp;doi=10.1109%2FIDCIoT59759.2024.10467454&amp;amp;partnerID=40&amp;amp;md5=388f0ad447062e86436c1da48a8231cc" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85190147837&amp;amp;doi=10.1109%2fIDCIoT59759.2024.10467454&amp;amp;partnerID=40&amp;amp;md5=388f0ad447062e86436c1da48a8231cc&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="168742">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="168743">
              <text>ISBN: 979-835032753-3</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="168744">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="168745">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="168746">
              <text>Conference paper</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="168747">
              <text>Sinha S., CHRIST (Deemed to Be University), Department of Computer Science, Bengaluru, 560029, India; Choudhary S., Banasthali Vidyapith, Department of Computer Science, Rajasthan, 304022, India; Paul A., Banasthali Vidyapith, Department of Computer Science, Rajasthan, 304022, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
