<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="20002" 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/20002?output=omeka-xml" accessDate="2026-04-08T22:26:40+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="175629">
              <text>Enhanced Edge Computing Model by using Data Combs for Big Data in Metaverse</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="175630">
              <text>Augmented Reality; Big data Processing; Data Hive Architecture; Edge computing; Metaverse; Virtual Reality</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="175631">
              <text>The Metaverse is a huge project undertaken by Facebook in order to bring the world closer together and help people live out their dreams. Even handicapped can travel across the world. People can visit any place and would be safe in the comfort of their homes. Meta (Previously Facebook) plans to execute this by using a combination of AR and VR (Augmented Reality and Virtual Reality). Facebook aims to bring this technology to the people soon. However, a big factor in this idea that needs to be accounted for is the amount of data generation that will take place. Many Computer Science professors and scientists believe that the amount of data Meta is going to generate in one day would almost be equal to the amount of data Instagram/Facebook would have generated in their entire lifetime. This will push the entire data generation by at least 30%, if not more. Using traditional methods such as cloud computing might seem to become a shortcoming in the near future. This is because the servers might not be able to handle such large amounts of data. The solution to this problem should be a system that is designed specifically for handling data that is extremely large. A system that is not only secure, resilient and robust but also must be able to handle multiple requests and connections at once and yet not slow down when the number of requests increases gradually over time. In this model, a solution called the DHA (Data Hive Architecture) is provided. These DHAs are made up of multiple subunits called Data Combs and those are further broken down into data cells. These are small units of memory which can process big data extremely fast. When information is requested from a client (Example: A Data Warehouse) that is stored in multiple edges across the world, then these Data Combs rearrange the data cells within them on the basis of the requested criteria. This article aims to explain this concept of data combs and its usage in the Metaverse.   2023 IEEE.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="175632">
              <text>Mohan T.L.R.; Jayapandian 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="175633">
              <text>IDCIoT 2023 - International Conference on Intelligent Data Communication Technologies and Internet of Things, Proceedings, pp. 249-255.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="175634">
              <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="175635">
              <text>2023-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="175636">
              <text>&lt;a href="https://doi.org/10.1109/IDCIoT56793.2023.10053519" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/IDCIoT56793.2023.10053519&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85149805398&amp;amp;doi=10.1109%2FIDCIoT56793.2023.10053519&amp;amp;partnerID=40&amp;amp;md5=3223c88a647060587422cd0ec98b2f65" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85149805398&amp;amp;doi=10.1109%2fIDCIoT56793.2023.10053519&amp;amp;partnerID=40&amp;amp;md5=3223c88a647060587422cd0ec98b2f65&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="175637">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="175638">
              <text>ISBN: 978-166547451-1</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="175639">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="175640">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="175641">
              <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="175642">
              <text>Mohan T.L.R., Christ (Deemed to Be University), School of Engineering and Technology, India; Jayapandian N., Christ (Deemed to Be University), School of Engineering and Technology, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
