<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="12416" 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/12416?output=omeka-xml" accessDate="2026-04-15T07:11:19+00:00">
  <collection collectionId="24">
    <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="64990">
                <text>PHD</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="22">
    <name>PhD</name>
    <description>PhD Thesis</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="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="70806">
              <text>61000370</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70807">
              <text>Vanet Framework for Optimal Target Selection in Handoff using machine Learning   </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70808">
              <text>Computer Science</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70809">
              <text>The impact of mobile networking has been far-reaching and has transformed many technologies for the better. Among the more pioneering technologies of recent times, autonomous vehicles (AV) are being touted as the future of transportation. AVs are featured prominently due to their ability to provide services across the implementations concerning smart-city applications. Since the newlinenodes (AV) involved are highly mobile, it is important to keep the device connected and adapt the dynamic topology change. The network should be capable of switching AV between access points (AP s) dynamic and must take place without much delay. Handoff is the process where a node switches between APs depending on the changes in the network topology. Various studies have claims that the use of Machine Learning or Deep Learning improves the efficiency of decision making in mobile networks. In this research work a dynamic handoff framework, inspired by the traditional Indian game of Kho-Kho is proposed. It selects the most optimal AP for newlinecommunication in a mobile environment. Initially the nodes within an AP are newlinecategorized as sticking and steering nodes. Identifying the nodes list for executing newlinethe Kho-Kho based handoff for the steering nodes. The framework makes use of Artificial Neural Networks (ANN) to perform the operation of handoff and selects the most optimal AP once the handoff trigger occurs. ANN is designed for multiple parameters, including signal strength, noise, and direction to make its decisions regarding handoff. The proposed Kho-Kho model has been newlineimplemented and analyzed using the NS3 simulator. Simulation results have indicated a higher performance of the proposed Kho-Kho approach when compared to the existing standard implemented for vehicular ad hoc newlinecommunications in IEEE </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70810">
              <text>Thomas, Libin</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="70811">
              <text>Author's Submission</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="70812">
              <text>Christ(Deemed to be University)</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="70813">
              <text>2024-01-01</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="37">
          <name>Contributor</name>
          <description>An entity responsible for making contributions to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70814">
              <text>J, Sandeep</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70815">
              <text>Open Access</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="70816">
              <text>PDF</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70817">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70818">
              <text>PhD</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="70819">
              <text>&lt;a href="http://hdl.handle.net/10603/586403" target="_blank" rel="noreferrer noopener"&gt;http://hdl.handle.net/10603/586403&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
