<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="15670" 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/15670?output=omeka-xml" accessDate="2026-05-13T16:05:43+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="116116">
              <text>IoT-based traffic prediction and traffic signal control system for smart city</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="116117">
              <text>Improved beetle swarm optimization (IBSO); Intel 80,286 microprocessor; Internet of Things (IoT); Optimized weight elman neural network (OWENN); Smart city</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="116118">
              <text>Because of the population increasing so high, and traffic density remaining the same, traffic prediction has become a great challenge today. Creating a higher degree of communication in automobiles results in the time wastage, fuel wastage, environmental damage, and even death caused by citizens being trapped in the middle of traffic. Only a few researchers work in traffic congestion prediction and control systems, but it may provide less accuracy. So, this paper proposed an efficient IoT-based traffic prediction using OWENN algorithm and traffic signal control system using Intel 80,286 microprocessor for a smart city. The proposed system consists of 5 phases, namely IoT data collection, feature extraction, classification, optimized traffic IoT values, and traffic signal control system. Initially, the IoT traffic data are collected from the dataset. After that, traffic, weather, and direction information are extracted, and these extracted features are given as input to the OWENN classifier, which classifies which place has more traffic. Suppose one direction of the place has more traffic, it optimizes the IoT values by using IBSO, and finally, the traffic is controlled by using Intel 80,286 microprocessor. An efficient OWENN algorithm for traffic prediction and traffic signal control using a Intel 80,286 microprocessor for a smart city. After extracting the features, the classification is performed in this step. Hereabout, the classification is done by using the optimized weight Elman neural network (OWENN) algorithm that classifies which places have more traffic. OWENN attains 98.23% accuracy than existing model also its achieved 96.69% F-score than existing model. The experimental results show that the proposed system outperforms state-of-the-art methods.  2021, The Author(s), under exclusive licence to Springer-Verlag GmbH Germany, part of Springer Nature.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="116119">
              <text>Neelakandan S.; Berlin M.A.; Tripathi S.; Devi V.B.; Bhardwaj I.; Arulkumar N.</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="116120">
              <text>Soft Computing, Vol-25, No. 18, pp. 12241-12248.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="116121">
              <text>Springer Science and Business Media Deutschland GmbH</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="116122">
              <text>2021-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="116123">
              <text>&lt;a href="https://doi.org/10.1007/s00500-021-05896-x" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/s00500-021-05896-x&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85107334797&amp;amp;doi=10.1007%2Fs00500-021-05896-x&amp;amp;partnerID=40&amp;amp;md5=204cec12651367d9360b723b4f87c7c8" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85107334797&amp;amp;doi=10.1007%2fs00500-021-05896-x&amp;amp;partnerID=40&amp;amp;md5=204cec12651367d9360b723b4f87c7c8&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="116124">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="116125">
              <text>ISSN: 14327643</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="116126">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="116127">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="116128">
              <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="116129">
              <text>Neelakandan S., Department of IT, Jeppiaar Institute of Technology, Chennai, India; Berlin M.A., Department of CSE, R.M.D Engineering College, Chennai, India; Tripathi S., Department of Computer Science &amp;amp; Engineering, Birla Institute of Applied Sciences, Bhimtal, India; Devi V.B., Department of Information Technology, Sri Sai Ram Institute of Technology, Chennai, India; Bhardwaj I., Galgotias University, Greater Noida, India; Arulkumar N., Department of CS, CHRIST (Deemed To Be University), Banglore, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
