<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="26062" 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/26062?output=omeka-xml" accessDate="2026-06-18T13:32:12+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="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="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258882">
              <text>Sadasivam, Boobalakrishnan; Rajamohan, Kavitha</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258883">
              <text>Integrating LLMs into Smart Home Architecture: Design, Implementation, and Experimental Insights</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="258884">
              <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="258885">
              <text>5th IEEE International Conference on Mobile Networks and Wireless Communications, ICMNWC 2025;</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="258886">
              <text>&lt;a href="https://doi.org/10.1109/ICMNWC66779.2025.11354247" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/ICMNWC66779.2025.11354247&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105033689042?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105033689042?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="258887">
              <text>Sadasivam B., Christ (Deemed to be University), Department of Computer Science, Bangalore, India; Rajamohan K., Christ (Deemed to be University), Department of Computer Science, Bangalore, India</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258888">
              <text>Smart home systems are a key application of the Internet of Things (IoT) paradigm. These devices are either directly or indirectly connected to a network in order to perceive actions based on user willingness or sensing. As Information and Communication Technology (ICT) advances, Large Language Models (LLMs) are growing increasingly potent. Agents with LLM capabilities could be very supportive for smart home systems because of their natural language comprehension. In this paper, we introduce an LLM-powered smart home agent with real-time connectivity to smart home devices. This proposal has been experimented with and evaluated with typical smart home use cases. This experimental architecture illustrates a realtime scenario of a standard smart home, where sensors, lights, and switches are interconnected in a multi-tiered environment. The sensor, gateway, and switch modules are connected to the smart home edge server via a Web of Things (WoT) interface. The experiment has been conducted with various types of smart home use case prompts, including status requests, control requests, automation requests, and reasoning requests. The outcome of the experiment indicates that the addition of LLM to smart homes excels in natural conversational patterns compared to keywordbased agents. The prompt response time, which is unsuitable for time-sensitive tasks like anomaly detection, is a drawback, and edge LLMs could be a solution.   2025 IEEE.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258889">
              <text>Agents; Large Language Model; Sensors; Smart Home; Web of Things</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="258890">
              <text>Institute of Electrical and Electronics Engineers Inc.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="258891">
              <text>ISBN: 979-833155664-8;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258892">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258893">
              <text>Conference paper</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258894">
              <text>Restricted Access; Hardcopy may be available in the library</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="258895">
              <text>online</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
