<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="23722" 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/23722?output=omeka-xml" accessDate="2026-06-19T10:40:11+00:00">
  <collection collectionId="7">
    <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="3139">
                <text>Faculty Publications</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="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="227142">
              <text>Babu, K.; Mohammed, Mustfa; Fallah, Mohammed; Vichitra, R.; Ahila, R.; Radhamani, R.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="227143">
              <text>Performance Evaluation of Hybrid Lifi-Wifi Internet Systems</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="227144">
              <text>01-01-2025</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="227145">
              <text>Journal of Internet Services and Information Security;Volume;15;Issue;4;pp.633-646</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="227146">
              <text>&lt;a href="https://doi.org/10.58346/JISIS.2025.I4.046" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.58346/JISIS.2025.I4.046&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105025118538?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105025118538?origin=resultslist&lt;/a&gt;</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="227147">
              <text>Babu K., Department of Computational Intelligence, SRM Institute of Science &amp;amp; Technology, Tamil Nadu, India; Mohammed M., College of Engineering Technique, Al-Farahidi University, Baghdad, Iraq; Fallah M., Department of Computers Techniques Engineering, College of Technical Engineering, The Islamic University, Najaf, Iraq, Department of Computers Techniques Engineering, College of Technical Engineering, The Islamic University of Al Diwaniyah, Al Diwaniyah, Iraq; Vichitra R., School of Business and Management, Christ (Deemed to be University), Bangalore, India; Ahila R., Department of CSE, New Prince Shri Bhavani College of Engineering and Technology, Tamil Nadu, Chennai, India; Radhamani R., Department of Electrical and Electronics Engineering, K.S. Rangasamy College of Technology, Tiruchengode, India</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="227148">
              <text>The rapid development of wireless technology made Light Fidelity, or LiFi, leave the laboratory and move onto the list of the next big thing, alongside everyday WiFi. WiFi also provides freedom of movement, but once everyone in a large area is streaming video, the signal becomes like a traffic jam. LiFi is going another way: data is sent via the rays of LED lights, meaning it can push files at light speed. The only problem is that the connection will not last forever, as soon as you leave the arc of the lamp or walk too far. In this paper, we explore what would happen when you combine the wide coverage of WiFi with the high speed of Li-Fi to form a hybrid system that avoids the weaknesses of both. Various test-based classrooms, halls, and open laboratories measured the speed of bit movement, the consistency of the beams, and the responsiveness of the games, and the mixed environment performed better in nearly all tests than the technology alone. It even figured out which to use as people entered and left the building, alternating between LiFi and WiFi, increasing uptime and doubling peak throughput. Hospitals, campuses, airports, and factories in need of constant, high-speed connections now have a better roadmap for using this blend so machines keep running smoothly and users remain engaged. The paper itself contains the unraveling of the hardware, the explanation of the test setup, and the weighing of the numbers, accompanied by some thought on what this combination can offer the future of wireless worlds. The findings justify integrating LiFi with WiFi as an innovative, scalable solution to ensure it keeps up with the massive data volumes generated by modern phones, tablets, and smart devices.  2025, Innovative Information Science and Technology Research Group. All rights reserved.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="227149">
              <text>Data Transmission; Hybrid Wireless Networks; LiFi; Network Latency; Performance Evaluation; Signal Stability; WiFi</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="227150">
              <text>Innovative Information Science and Technology Research Group</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="227151">
              <text>ISSN: 21822069;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="227152">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="227153">
              <text>Article</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="227154">
              <text>All Open Access; Gold 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="227155">
              <text>online</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
