<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" 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?output=omeka-xml&amp;page=672&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-07-02T02:48:29+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>672</pageNumber>
      <perPage>20</perPage>
      <totalResults>16481</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="18152" public="1" featured="0">
    <collection collectionId="15">
      <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="44496">
                  <text>Book Chapter</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="27">
      <name>Book Chapter</name>
      <description>Faculty Publications- Book Chapter</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="150130">
                <text>Secure and Private Federated Learning through Encrypted Parameter Aggregation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="150131">
                <text>This chapter is dedicated to cross-silo private parameter aggregation. ML/DL has demonstrated promising results in a variety of application domains, especially when vast volumes of data are collected in one location, such as a data center or a cloud service. The goal of FL is to improve the quality of ML/DL models while minimizing their drawbacks. Participating devices in an FL task could range in size from a single smartphone or watch to a global corporation housing multiple data centers. It was originally believed that just a little amount of information about the original training data would be carried over into subsequent model updates as FL interactions occurred. The differential privacy framework is concerned with restricting the release of private information while sharing the outcomes of computations or queries performed on a dataset. Recently, many researchers have begun to employ differential privacy while training models in a federated setting.  2024 Saravanan Krishnan, A. Jose Anand, R. Srinivasan, R. Kavitha and S. Suresh.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="150132">
                <text>Vijayalakshmi K.; Sitharselvam P.M.; Thamarai I.; Ashok J.; Sathish G.; Mayakannan S.</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="150133">
                <text>Handbook on Federated Learning: Advances, Applications and Opportunities, pp. 80-105.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="150134">
                <text>CRC Press</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="150135">
                <text>2024-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="150136">
                <text>&lt;a href="https://doi.org/10.1201/9781003384854-4" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1201/9781003384854-4&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85179282227&amp;amp;doi=10.1201%2F9781003384854-4&amp;amp;partnerID=40&amp;amp;md5=59abf2775fcdf01df2776ae412f0cc85" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85179282227&amp;amp;doi=10.1201%2f9781003384854-4&amp;amp;partnerID=40&amp;amp;md5=59abf2775fcdf01df2776ae412f0cc85&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="150137">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="150138">
                <text>ISBN: 978-100383750-3; 978-103247162-4</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="150139">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="150140">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="150141">
                <text>Book chapter</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="150142">
                <text>Vijayalakshmi K., Department of Electrical and Communication Engineering, College of Engineering, National University of Science and Technology, Muscat, Oman; Sitharselvam P.M., RVS Educational Trusts Group of Institutions, Tamilnadu, Dindigul, India; Thamarai I., Department of Computer Science and Engineering, Panimalar Engineering College, Chennai City Campus, Tamil Nadu, Chennai, 600029, India; Ashok J., School of Business and Management, CHRIST (Deemed to be University), Karnataka, Bengaluru, India; Sathish G., Department of Information Technology, St. Martins Engineering College, Telangana, Secunderabad, India; Mayakannan S., Department of Mechanical Engineering, Vidyaa Vikas College of Engineering and Technology, Tiruchengode, Namakkal, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="13087" public="1" featured="0">
    <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="80154">
                <text>Secure approach to sharing digitized medical data in a cloud environment</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="80155">
                <text>Attribute-based encryption; Authentication; Cloud computing; Data privacy; Electronic medical records</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="80156">
                <text>Without proper security mechanisms, medical records stored electronically can be accessed more easily than physical files. Patient health information is scattered throughout the hospital environment, including laboratories, pharmacies, and daily medical status reports. The electronic format of medical reports ensures that all information is available in a single place. However, it is difficult to store and manage large amounts of data. Dedicated servers and a data center are needed to store and manage patient data. However, self-managed data centers are expensive for hospitals. Storing data in a cloud is a cheaper alternative. The advantage of storing data in a cloud is that it can be retrieved anywhere and anytime using any device connected to the Internet. Therefore, doctors can easily access the medical history of a patient and diagnose diseases according to the context. It also helps prescribe the correct medicine to a patient in an appropriate way. The systematic storage of medical records could help reduce medical errors in hospitals. The challenge is to store medical records on a third-party cloud server while addressing privacy and security concerns. These servers are often semi-trusted. Thus, sensitive medical information must be protected. Open access to records and modifications performed on the information in those records may even cause patient fatalities. Patient-centric health-record security is a major concern. End-to-end file encryption before outsourcing data to a third-party cloud server ensures security. This paper presents a method that is a combination of the advanced encryption standard and the elliptical curve Diffie-Hellman method designed to increase the efficiency of medical record security for users. Comparisons of existing and proposed techniques are presented at the end of the article, with a focus on the analyzing the security approaches between the elliptic curve and secret-sharing methods. This study aims to provide a high level of security for patient health records.  2023 Xi'an Jiaotong University</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="80157">
                <text>Pradeep Kumar K.; Prathap B.R.; Thiruthuvanathan M.M.; Murthy H.; Jha Pillai V.</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="80158">
                <text>Data Science and Management, Vol-7, No. 2, pp. 108-118.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="80159">
                <text>KeAi Communications Co.</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="80160">
                <text>2024-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="80161">
                <text>&lt;a href="https://doi.org/10.1016/j.dsm.2023.12.001" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1016/j.dsm.2023.12.001&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85187784810&amp;amp;doi=10.1016%2Fj.dsm.2023.12.001&amp;amp;partnerID=40&amp;amp;md5=3d6432b9a87fd65606ef2d17453224b5" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85187784810&amp;amp;doi=10.1016%2fj.dsm.2023.12.001&amp;amp;partnerID=40&amp;amp;md5=3d6432b9a87fd65606ef2d17453224b5&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="80162">
                <text>All Open Access; Gold Open Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="80163">
                <text>ISSN: 26667649</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="80164">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="80165">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="80166">
                <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="80167">
                <text>Pradeep Kumar K., Department of Computer Science and Engineering, CHRIST (Deemed to be University), Karnataka, Bengaluru, 560074, India; Prathap B.R., Department of Computer Science and Engineering, CHRIST (Deemed to be University), Karnataka, Bengaluru, 560074, India; Thiruthuvanathan M.M., Department of Computer Science and Engineering, CHRIST (Deemed to be University), Karnataka, Bengaluru, 560074, India; Murthy H., Department of Electronics and Communication Engineering, CHRIST (Deemed to be University), Karnataka, Bengaluru, 560074, India; Jha Pillai V., Department of Electronics and Communication Engineering, CHRIST (Deemed to be University), Karnataka, Bengaluru, 560074, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="20325" public="1" featured="0">
    <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="180130">
                <text>Secure Authenticated Communication Via Digital Signature And Clear List In VANETs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="180131">
                <text>Vehicular ad hoc network (VANET) plays a vital role in the intelligent transportation system(ITS), When a vehicle receives a message through network, the CRL (certificate revocation list) checking process will operate before certificate and signature verification. After successful authentication,a CRL list is created based on authentication. This CRL is used to verify whether a vehicle node can be permitted for communication in the VANET network. But when using CRL, a huge amount of storage space and checking time is needed. So we proposed a method without CRL list, but mentions a key management list to overcome large storage space and checking time even it reduce the access delay too. For the access permission we can do an authentication system based digital novel signature authentication(DNSA) for each vehicles in the vanet with the RSU unit or with other participant node vehicles in the communication as per the Topology.So we can perform an efficient and secured communication in VANET.  The Electrochemical Society</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="180132">
                <text>Deljo D.; Kumar K.P.</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="180133">
                <text>ECS Transactions, Vol-107, No. 1, pp. 20065-20071.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="180134">
                <text>Institute of Physics</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="180135">
                <text>2022-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="180136">
                <text>&lt;a href="https://doi.org/10.1149/10701.20065ecst" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1149/10701.20065ecst&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85134001069&amp;amp;doi=10.1149%2F10701.20065ecst&amp;amp;partnerID=40&amp;amp;md5=de363854ae31480c5d5282f2b286d3d3" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85134001069&amp;amp;doi=10.1149%2f10701.20065ecst&amp;amp;partnerID=40&amp;amp;md5=de363854ae31480c5d5282f2b286d3d3&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="180137">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="180138">
                <text>ISSN: 19386737; ISBN: 978-160768539-5</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="180139">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="180140">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="180141">
                <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="180142">
                <text>Deljo D., Department of Computer Science and Engineering, Christ university, Banglore, 560029, India; Kumar K.P., Department of Computer Science and Engineering, Christ university, Banglore, 560029, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="12010" public="1" featured="0">
    <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="65122">
                <text>61000048</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65123">
                <text>Secure authentication frame work for cloud  </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65124">
                <text>Computer Science</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65125">
                <text>The growing popularity of cloud based services is prompting organizations to consider shifting applications and data onto cloud. However, organizations dealing with highly sensitive information are apprehensive of moving its applications and data to public cloud owing to concern about security of its information. It is hence incumbent on service providers that only legitimate Users will access its services and resources in cloud. newlineVerifying authenticity of remote users is a necessary pre-requisite in a cloud environment before allowing access to secure resources/services/ applications. The simplest and most commonly used user authentication mechanism is password based authentication. However, Users tend to choose easy to remember password, and many a times use same password for multiple accounts, which makes it often the weakest link in security. Furthermore, service providers authenticating Users on the basis of password, stores password verification information in their databases and such authentication schemes with verification table are known to be vulnerable to various attacks. newlineFrom the perspective of authentication requirements, service providers in a cloud environment can be broadly categorized into two. Those service providers dealing with highly sensitive information and working in a regulated environment can be grouped into category one as in those offering services for sectors like health care, finance. These providers require a strong and secure authentication mechanism to authenticate its users, without any additional functionality. Similarly, there is a second category of service providers dealing with secure information but operate in a collaborative environment as providers providing their applications bundled through a web portal. To provide the Users with a seamless authentication experience, while accessing multiple services during a session, the second category of service providers prefer to have Single Sign-on functionality.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65126">
                <text>Binu,Sumitra</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="65127">
                <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="65128">
                <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="65129">
                <text>2016-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="65130">
                <text>Raj, Pethuru</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65131">
                <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="65132">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65133">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65134">
                <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="65135">
                <text>&lt;a href="http://hdl.handle.net/10603/118831" target="_blank" rel="noreferrer noopener"&gt;http://hdl.handle.net/10603/118831&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1504" public="1" featured="1">
    <fileContainer>
      <file fileId="1358">
        <src>https://archives.christuniversity.in/files/original/72023227f75fc1cd63a2f0b7def1a38a.pdf</src>
        <authentication>acfa5e5a937d2e4840e429355e96c4fb</authentication>
      </file>
    </fileContainer>
    <collection collectionId="23">
      <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="64989">
                  <text>MPHIL</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="18">
      <name>Mphil</name>
      <description>Mphil 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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7033">
                <text>Secure authentication framework for

 cloud

</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7034">
                <text>Binu Sumitra</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="7035">
                <text>2016</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="7036">
                <text>Computer science</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7037">
                <text>The growing popularity of cloud based services is prompting organizations to consider shifting applications and data onto cloud. However, organizations dealing with highly sensitive information are apprehensive of moving its applications &amp;amp; data to public cloud owing to concern about

security of its information. It is hence incumbent on service providers that only legitimate Users will access its services and resources in cloud. Verifying authenticity of remote users is a necessary pre-requisite in a cloud environment before allowing access to secure resources/services/ applications. The simplest &amp;amp; most commonly used user authentication mechanism is password based authentication. However, Users tend to choose

easy to remember password, and many a times use same password for multiple accounts, which makes it often the weakest link in security. Furthermore, service providers authenticating Users on the basis of

password, stores password verification information in their databases and such authentication schemes with verification table are known to be vulnerable to various attacks.

From the perspective of authentication requirements, service providers in a cloud environment can be broadly categorized into two. Those service providers dealing with highly sensitive information and working in a

regulated environment can be grouped into category one ?? as in those offering services for sectors like health care, finance. These providers require a strong and secure authentication mechanism to authenticate its users,

without any additional functionality. Similarly, there is a second category of service providers dealing with secure information but operate in a collaborative environment ?? as providers providing their applications bundled through a web portal. To provide the Users with a seamless

authentication experience, while accessing multiple services during a session, the second category of service providers prefer to have Single Signon functionality.

Two-factor authentication technology overcomes the limitations of password authentication and decreases the probability that the claimant is presenting

false evidence of its identity to verifier. If different service providers set up their own two-factor authentication services, Users have to do registration

and login process repeatedly. Also, Users accessing multiple cloud services may be required to hold multiple authentication tokens associated with

various service providers.

Authentication factors such as crypto-tokens and smart cards with cryptographic capabilities have been vastly used as a second authentication factor. However, Users are required to always carry these authentication

tokens which make it cumbersome from practical usability perspective. Also its usage involves cost thus restricting its adoption to corporate environments. The authentication process can be made more user-convenient

if the authentication factor chosen is such that it is commonly used by all types of Users. Leveraging the use of mobile phone as an authentication

factor can help address issue of user convenience at no extra cost while improving the security of authentication schemes. Though, there has been an increasing focus on strengthening the authentication methods of cloud service users, there is no significant work

that discusses an authentication scheme that can be adopted by the two categories of cloud Service Providers. Taking cognizance of aforesaid issues related to secured authentication in cloud environment, this research focused on designing secure Two-Factor authentication schemes that can be adopted by the two categories of service

providers. This research carried out in different levels, proposes authentication architecture and protocols for the two categories of service

providers. At the first level, research proposes Direct Authentication architecture for cloud Service Providers who prefer to authenticate its users by using a strong

authentication mechanism and does not require Single Sign-On (SSO) functionality. For those Providers who prefer to provide its user with a SSO

functionality the research proposes Brokered Authentication architecture. The next level of research focuses on proposing User Authentication

Protocols for both Direct Authentication Service Providers (DASPs) and Brokered Authentication Service Providers (BASPs). The research proposes

use of strong, Two-Factor Authentication Protocols without Verifier Table. The suggested protocols, provides Users with flexibility of using a Password

and either a Crypto-token or a Mobile-token to authenticate with Service Providers. The proposed approach eliminates the requirement of the User to remember multiple identities to access multiple services and provides the

benefit of a higher level of security on account of second authentication factor and non-maintenance of verifier table at server. Access to different services offered by multiple service providers using a single authentication token requires interoperability between providers. Also,

the Service Providers will have to address the task of issuing the second authentication factor to Users. As a result, the research intends to propose the

utilization of proposed two-factor authentication scheme within a specific environment which includes a trusted entity called an Identity Provider (IdP), with whom Users and Service Providers will be registered. The IdP is

responsible for issuing and managing the second authentication factor. In brokered authentication, the IdP playing the role of an authentication

broker also provides Single Sign-on functionality. The Security Assertion Markup Language (SAML) is used by BASPs and the IdP to exchange authentication information about Users. A major objective of this research is to propose an authentication model that can be adopted by both categories of service providers. Hence, this research

proposes an authentication framework for cloud which supports an integrated authentication architecture that provides the service providers with the flexibility to choose between direct and brokered authentication. The

integrated two-factor authentication protocol, which does not require the server to maintain a verifier table, supported by the frame work allows users to do a single registration and access services of both direct &amp;amp; brokered

authentication service providers using the same crypto-token/mobile-token. To verify claims about security strengths of the proposed authentication

protocols, security analysis is done using theoretical intuition. The proposed protocols are found to offer desirable security features such as resistance to

replay attack, stolen verifier attack, guessing attack, user impersonation attack etc. To verify the efficiency of the proposed protocols, the communication and computation costs are compared with similar schemes and it is seen that the costs are comparable. To validate the resistance of protocols to authentication attacks, they are analyzed using automated verification tool called ????Scyther??? and the protocol strength is verified by ???no attacks??? results.

</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="21549" public="1" featured="0">
    <collection collectionId="21">
      <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="62842">
                  <text>Reviews</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="33">
      <name>Review</name>
      <description>Faculty Publications- Reviews</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="196974">
                <text>Secure Authentication Schemes for Vehicular Adhoc Networks: A Survey</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196975">
                <text>Authentication; Availability; Linkability; Message integrity; Non-repudiation; Privacy-preservation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196976">
                <text>Vehicular Adhoc Network (VANET) is based on theprinciples of Mobile Adhoc NETwork (MANET) where vehicles are considered as nodes and secure communication is established to provide asafe driving experience. Due to its unique characteristics, it has various issues and challenges. These issues can be resolved by ensuring security requirements like authentication, privacy preservation, message integrity, non-repudiation, linkability, availability etc. Authentication plays a vital role since it is the first step to establish secure communication in the vehicular network. It also distinguishes malicious vehicles from legitimate vehicles. Different authentication schemes have been proposed to establish secure vehicular communications. A survey of the existing authentication schemes is given in this paper. At first, the existing authentication schemes are broadly classified based on message signing and verification methods. Then, each category is clearly explained with its sub-categories. At last, the existing schemes in each category are compared based on security requirements, security attacks and performance parameters.  2021, The Author(s), under exclusive licence to Springer Science+Business Media, LLC, 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="196977">
                <text>Jenefa J.; Mary Anita E.A.</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="196978">
                <text>Wireless Personal Communications, Vol-123, No. 1, pp. 31-68.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="196979">
                <text>Springer</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="196980">
                <text>2022-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="196981">
                <text>&lt;a href="https://doi.org/10.1007/s11277-021-09118-3" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/s11277-021-09118-3&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85114996237&amp;amp;doi=10.1007%2Fs11277-021-09118-3&amp;amp;partnerID=40&amp;amp;md5=b68d4e35812aa7c373218d8e7e618d6a" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85114996237&amp;amp;doi=10.1007%2fs11277-021-09118-3&amp;amp;partnerID=40&amp;amp;md5=b68d4e35812aa7c373218d8e7e618d6a&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="196982">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="196983">
                <text>ISSN: 9296212; CODEN: WPCOF</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="196984">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196985">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196986">
                <text>Review</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="196987">
                <text>Jenefa J., Department of Computer Science and Engineering, Christ University, Bangalore, India; Mary Anita E.A., Department of Computer Science and Engineering, Christ University, Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="15996" public="1" featured="0">
    <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="120644">
                <text>Secure biometric authentication with de-duplication on distributed cloud storage</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="120645">
                <text>Artificial Intelligence; Cloud computing; Computer Networks and Communications; Computer Vision; Distributed and Parallel Computing; Dynamic speed scaling algorithm; Edge computing; EIoT; Energy; IoT; Security and Privacy</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="120646">
                <text>Cloud computing is one of the evolving fields of technology, which allows storage, access of data, programs, and their execution over the internet with offering a variety of information related services. With cloud information services, it is essential for information to be saved securely and to be distributed safely across numerous users. Cloud information storage has suffered from issues related to information integrity, data security, and information access by unauthenticated users. The distribution and storage of data among several users are highly scalable and cost-efficient but results in data redundancy and security issues. In this article, a biometric authentication scheme is proposed for the requested users to give access permission in a cloud-distributed environment and, at the same time, alleviate data redundancy. To achieve this, a cryptographic technique is used by service providers to generate the bio-key for authentication, which will be accessible only to authenticated users. A Gabor filter with distributed security and encryption using XOR operations is used to generate the proposed bio-key (biometric generated key) and avoid data deduplication in the cloud, ensuring avoidance of data redundancy and security. The proposed method is compared with existing algorithms, such as convergent encryption (CE), leakage resilient (LR), randomized convergent encryption (RCE), secure de-duplication scheme (SDS), to evaluate the de-duplication performance. Our comparative analysis shows that our proposed scheme results in smaller computation and communication costs than existing schemes.  2021 M et al. All Rights Reserved.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="120647">
                <text>Vinoth K.M.; Venkatachalam K.; Prabu P.; Almutairi A.; Abouhawwash M.</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="120648">
                <text>PeerJ Computer Science, Vol-7, pp. 1-20.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="120649">
                <text>PeerJ 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="120650">
                <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="120651">
                <text>&lt;a href="https://doi.org/10.7717/PEERJ-CS.569" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.7717/PEERJ-CS.569&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85112859669&amp;amp;doi=10.7717%2FPEERJ-CS.569&amp;amp;partnerID=40&amp;amp;md5=3346d10a0987add986da7ccd3627309b" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85112859669&amp;amp;doi=10.7717%2fPEERJ-CS.569&amp;amp;partnerID=40&amp;amp;md5=3346d10a0987add986da7ccd3627309b&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="120652">
                <text>All Open Access; Gold Open Access; Green Open Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="120653">
                <text>ISSN: 23765992</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="120654">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="120655">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="120656">
                <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="120657">
                <text>Vinoth K.M., Department of Computer Science and Engineering, Anna University, University College of Engineering, Dindigul, Tamilnadu, India; Venkatachalam K., Department of Computer Science and Engineering, CHRIST (Deemed to be University), Bangalore, India; Prabu P., Department of Computer Science, CHRIST (Deemed to be University), Bangalore, Bangalore, Karnataka, India; Almutairi A., School of Mathematics, Unaizah College of Sciences and Arts, Qassim University, Saudi Arabia; Abouhawwash M., Department of Mathematics, Faculty of Science, Mansoura University, Mansoura, Egypt, Department of Computational Mathematics, Science and Engineering (CMSE), Michigan State University, East Lansing, MI, United States</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="20884" public="1" featured="0">
    <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="187863">
                <text>Secure Bitcoin Transaction and IoT Device usage in Decentralized Application</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="187864">
                <text>Bitcoin; Blockchain; Distributed System; Internet of Things; Security</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="187865">
                <text>In the recent years, there has been a boom in the number of connected devices due to developments in the field of Internet of things. This has also increased the requirements of security specification. The proposed method is introducing a secure information transmission system by using Blockchain technology. Blockchain is a relatively new technology which was introduced by stoshi nakamoto, which was also the basis for developing crypto currency [bitcoin]. Crypto currencies are made transparent and secure using their network architecture, which is a combo of a decentralized and distributed network. In this paper is try to exploit the same methodology used in crypto currencies to develope an IOT network, where the devices can talk to their peers in a secure manner. They explored all the different networks and features of developing a Decentralized application that is named as Dapp.  2018 IEEE.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="187866">
                <text>Swamy S.A.; 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="187867">
                <text>Proceedings of the 3rd International Conference on Communication and Electronics Systems, ICCES 2018, pp. 271-274.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="187868">
                <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="187869">
                <text>2018-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="187870">
                <text>&lt;a href="https://doi.org/10.1109/CESYS.2018.8724077" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/CESYS.2018.8724077&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85067461898&amp;amp;doi=10.1109%2FCESYS.2018.8724077&amp;amp;partnerID=40&amp;amp;md5=cf87cfa6841754e70ac2df80d825aec5" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85067461898&amp;amp;doi=10.1109%2fCESYS.2018.8724077&amp;amp;partnerID=40&amp;amp;md5=cf87cfa6841754e70ac2df80d825aec5&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="187871">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="187872">
                <text>ISBN: 978-153864765-3</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="187873">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="187874">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="187875">
                <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="187876">
                <text>Swamy S.A., CHRIST (Deemed to Be University), Bangalore, India; Jayapandian N., CHRIST (Deemed to Be University), Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="26495" public="1" featured="0">
    <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="264501">
                <text>Asha, H.P.; Jingle, I. Diana Jeba</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264502">
                <text>Secure Communication in Fog Nodes through Quantum Key Distribution</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="264503">
                <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="264504">
                <text>Communications in Computer and Information Science;Volume;2333 CCIS;pp.32-46</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="264505">
                <text>&lt;a href="https://doi.org/10.1007/978-3-031-83783-8_2" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-3-031-83783-8_2&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105000970561?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105000970561?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="264506">
                <text>Asha H.P., Department of Computer Science and Engineering, Christ University, Bangalore, India; Jingle I.D.J., Department of Computer Science and Engineering, Christ University, Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264507">
                <text>In this intensifying era of big-data, data processing is predominant. Data processing takes place closer to devices in the fog computing, strong security measures are necessary. The Hybrid Encapsulation Mechanism (HEM), Elliptic Curve Diffie-Hellman (ECDH), and Quantum Key Distribution (QKD) are furnished in this study as a safe method for authentic data sharing between fog nodes. HEM, a special encapsulation technique that makes use of the Advanced Encryption Standard (AES), is used to encrypt the data, and ECDH is used to generate the shared and private keys. A conventional route is then used to convey the data, which may offer a compromise between efficiency and security. But, fog nodes can communicate and exchange shared keys more easily over a quantum channel, which is an efficient quantum key exchange mechanism (QKD). ECC efficiently and rapidly generates encryption keys to safeguard data and these keys are impenetrable by even the most powerful computers due to their proven security. Along with safeguarding private information, this promotes collaboration and trust across fog nodes. The efficiency of the proposed method is calculated considering the execution time, computation cost, key size, and key strength. We discovered that our proposed approach outperforms existing ones when compared to them.  The Author(s), under exclusive license to Springer Nature Switzerland AG 2025.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264508">
                <text>Advanced Encryption Standard; Cryptography; Fog nodes; Introduction; Quantum Key Distribution; Security</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="264509">
                <text>Springer Science and Business Media Deutschland GmbH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="264510">
                <text>ISSN: 18650929; ISBN: 978-303183782-1;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264511">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264512">
                <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="264513">
                <text>Restricted Access; Hardcopy may be available in the library</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="20737" public="1" featured="0">
    <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="185820">
                <text>Secure Data Processing System Using Decision Tree Architecture</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="185821">
                <text>[No abstract available]</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="185822">
                <text>Nived T.M.; Tiru J.J.; Jayapandian N.; Balachandran K.</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="185823">
                <text>New Trends in Computational Vision and Bio-Inspired Computing - Selected Works Presented at the ICCVBIC 2018, pp. 173-180.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="185824">
                <text>Springer Nature</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="185825">
                <text>2020-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="185826">
                <text>&lt;a href="https://doi.org/10.1007/978-3-030-41862-5_16" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-3-030-41862-5_16&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85125635832&amp;amp;doi=10.1007%2F978-3-030-41862-5_16&amp;amp;partnerID=40&amp;amp;md5=70777ceb92abac310a23c5f99b711917" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85125635832&amp;amp;doi=10.1007%2f978-3-030-41862-5_16&amp;amp;partnerID=40&amp;amp;md5=70777ceb92abac310a23c5f99b711917&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="185827">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="185828">
                <text>ISBN: 978-303041861-8</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="185829">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="185830">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="185831">
                <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="185832">
                <text>Nived T.M., Department of Computer Science and Engineering, CHRIST (Deemed to be University), Bangalore, India; Tiru J.J., Department of Computer Science and Engineering, CHRIST (Deemed to be University), Bangalore, India; Jayapandian N., Department of Computer Science and Engineering, CHRIST (Deemed to be University), Bangalore, India; Balachandran K., Department of Computer Science and Engineering, CHRIST (Deemed to be University), Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="19142" public="1" featured="0">
    <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="163619">
                <text>Secure Decentralization: Examining the Role of Blockchain in Network Security</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="163620">
                <text>Blockchain; Communication; Cryptographic; Decentralized; Preventing</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="163621">
                <text>Blockchain generation has emerged as a novel answer for securing decentralized networks. This technology, which was first created for use in crypto currencies, has received enormous interest in recent years because of its capability for boosting protection in various industries and community protection. The essential precept at the back of block chain technology is the decentralization of statistics garage and control. In a decentralized network, no central authority may control the statistics. Rather, the facts are shipped amongst multiple nodes, making it immune to tampering and single factors of failure. One of the most important advantages of blockchain in community protection is its capacity to offer cozy and transparent communication amongst community customers. Through cryptographic techniques, block chain can affirm the identities of network participants and ensure the authenticity of records trade. This feature is extraordinarily valuable in preventing unauthorized access and facts manipulation.  2024 IEEE.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="163622">
                <text>Monga S.; Gupta P.; Logeshwaran J.; Thamaraimanalan T.</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="163623">
                <text>2024 2nd World Conference on Communication and Computing, WCONF 2024</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="163624">
                <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="163625">
                <text>2024-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="163626">
                <text>&lt;a href="https://doi.org/10.1109/WCONF61366.2024.10692123" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/WCONF61366.2024.10692123&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85207456667&amp;amp;doi=10.1109%2FWCONF61366.2024.10692123&amp;amp;partnerID=40&amp;amp;md5=199c35b5f68e5fd9fff4ac38e0a1a8bb" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85207456667&amp;amp;doi=10.1109%2fWCONF61366.2024.10692123&amp;amp;partnerID=40&amp;amp;md5=199c35b5f68e5fd9fff4ac38e0a1a8bb&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="163627">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="163628">
                <text>ISBN: 979-835039532-7</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="163629">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="163630">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="163631">
                <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="163632">
                <text>Monga S., Chitkara University, Institute of Engineering and Technology, Chitkara University, Punjab, Rajpura, India; Gupta P., Chitkara University, Institute of Engineering and Technology, Chitkara University, Punjab, Rajpura, India; Logeshwaran J., Department of Computer Science, CHRIST (Deemed to be University, Karnataka, Bengaluru, 560029, India; Thamaraimanalan T., Department of Electronics andCommunication Engineering, Sri Eshwar College of Engineering, Tamil Nadu, Coimbatore, 641202, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="13407" public="1" featured="0">
    <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="84617">
                <text>SECURE DOMINATION IN TRANSFORMATION GRAPH Gxy+</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="84618">
                <text>Domination; line graph; secure domination; transformation graph</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="84619">
                <text>In this paper, we characterize graphs for which the secure domination number of the transformation graph Gxy+ is 1 or 2. Also we prove that for any connected graph G with at least 4 pendant vertices, the secure domination number is greater than or equal to the secure domination number of the transformation graph G-++. We also find a bound for the secure domination number of G-+ when G is a tree.  2024 Jangjeon Research Institute for Mathematical Sciences and Physics. All rights reserved.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="84620">
                <text>Theresa S.; Kureethara J.V.</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="84621">
                <text>Proceedings of the Jangjeon Mathematical Society, Vol-27, No. 4, pp. 837-848.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="84622">
                <text>Jangjeon Research Institute for Mathematical Sciences and Physics</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="84623">
                <text>2024-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="84624">
                <text>&lt;a href="https://doi.org/10.17777/pjms2024.27.4.837" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.17777/pjms2024.27.4.837&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85209919968&amp;amp;doi=10.17777%2Fpjms2024.27.4.837&amp;amp;partnerID=40&amp;amp;md5=0bc021655339396bca31ec8a36c53a62" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85209919968&amp;amp;doi=10.17777%2fpjms2024.27.4.837&amp;amp;partnerID=40&amp;amp;md5=0bc021655339396bca31ec8a36c53a62&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="84625">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="84626">
                <text>ISSN: 15987264</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="84627">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="84628">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="84629">
                <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="84630">
                <text>Theresa S., Department of Mathematics, Christ University, Bangalore, India; Kureethara J.V., Department of Mathematics, Christ University, Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="27450" public="1" featured="0">
    <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="27">
      <name>Book Chapter</name>
      <description>Faculty Publications- Book Chapter</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="276881">
                <text>Alex, Annie; Sangeetha, V.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="276882">
                <text>Secure Equitability in Chemical Networks</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="276883">
                <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="276884">
                <text>Graph Theory in Computer Science;pp.201-211</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="276885">
                <text>&lt;a href="https://doi.org/10.1002/9781394302628.ch11" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1002/9781394302628.ch11&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105028340302?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105028340302?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="276886">
                <text>Alex A., Department of Mathematics, CHRIST (Deemed to be University), Karnataka, Bengaluru, India; Sangeetha V., Department of Mathematics, CHRIST (Deemed to be University), Karnataka, Bengaluru, India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="276887">
                <text>Let G (V,E) be a simple connected graph with a set of nodes V(G) and a set of edges E(G). A secure equitable dominating set [Formula Presented] is a dominating set in which, for any vertex [Formula Presented], there exists at least one vertex [Formula Presented] such that the vertex u belongs to the equitable neighborhood of v and, if we swap the vertices u and v, then the equitable domination property of the graph does not change. A secure equitable dominating set of minimum number of nodes in G is named a [Formula Presented] -set and the cardinality of a [Formula Presented] -set is called the secure equitable domination number of G, denoted by [Formula Presented]. In this paper, we study the bounds of secure equitable domination number in certain chemical structures. Moreover, we give an application of the parameter on interconnection networks.  2026 Scrivener Publishing LLC.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="276888">
                <text>benzoid; chemical networks; Secure equitable domination; silicate</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="276889">
                <text>wiley</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="276890">
                <text>ISBN: 978-139430262-8; 978-139430259-8;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="276891">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="276892">
                <text>Book chapter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="276893">
                <text>Restricted Access; Hardcopy may be available in the library</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="23046" public="1" featured="0">
    <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="217706">
                <text>Alex, Annie; Sangeetha, V.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="217707">
                <text>Secure equitable domination in Cartesian product of graphs</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="217708">
                <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="217709">
                <text>Discrete Mathematics, Algorithms and Applications;Issue;;Article No.;2550128;</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="217710">
                <text>&lt;a href="https://doi.org/10.1142/S1793830925501289" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1142/S1793830925501289&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105017178132?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105017178132?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="217711">
                <text>Alex A., Department of Mathematics, CHRIST (Deemed to be University), Karnataka, Bangalore, 560029, India; Sangeetha V., Department of Mathematics, CHRIST (Deemed to be University), Karnataka, Bangalore, 560029, India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="217712">
                <text>In graphs, several domination parameters have been introduced by incorporating a combination of the existing ones. A secure equitable domination is a domination in which the dominating set admits the properties of both; secure as well as equitable dominating sets. An equitable dominating set D of a graph G is said to be secure equitable dominating set, if for every u ? V?D, there exists a vertex v ? D such that u and v are adjacent and {D?{v}}?{u} is an equitable dominating set of G. The minimum cardinality of a secure equitable dominating set of G is called the secure equitable domination number of G. In this paper, we study certain cases were the secure domination, the equitable domination and the secure equitable domination bounds are equal. Moreover, we establish the bounds of secure equitable domination number of the Cartesian product of graphs.  2025 World Scientific Publishing Company.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="217713">
                <text>Cartesian product; Equitable domination; secure domination; secure equitable domination</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="217714">
                <text>World Scientific</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="217715">
                <text>ISSN: 17938309;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="217716">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="217717">
                <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="217718">
                <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="217719">
                <text>online</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="12901" public="1" featured="0">
    <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="77564">
                <text>SECURE EQUITABLE SUBDIVISION NUMBER OF GRAPHS</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="77565">
                <text>Secure equitable domination; secure equitable domination subdivision number</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="77566">
                <text>In this paper, we initiate the study of a new domination parameter: the secure equitable subdivision number of graphs. Moreover, we define the secure equitable subdivision critical graphs and the secure equitable subdivision stable graphs. Furthermore, we investigate how to construct a secure equitable subdivision critical graph.  2024, Canadian University of Dubai. All rights reserved.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="77567">
                <text>Alex A.; Sangeetha V.</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="77568">
                <text>Gulf Journal of Mathematics, Vol-17, No. 2, pp. 216-225.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="77569">
                <text>Canadian University of Dubai</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="77570">
                <text>2024-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="77571">
                <text>&lt;a href="https://doi.org/10.56947/gjom.v17i2.2049" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.56947/gjom.v17i2.2049&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85206085058&amp;amp;doi=10.56947%2Fgjom.v17i2.2049&amp;amp;partnerID=40&amp;amp;md5=ce6d7eddd96dfd57b818571b024f398e" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85206085058&amp;amp;doi=10.56947%2fgjom.v17i2.2049&amp;amp;partnerID=40&amp;amp;md5=ce6d7eddd96dfd57b818571b024f398e&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="77572">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="77573">
                <text>ISSN: 23094966</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="77574">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="77575">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="77576">
                <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="77577">
                <text>Alex A., Department of Mathematics, CHRIST(Deemed to be University), Bangalore, India; Sangeetha V., Department of Statistics, CHRIST(Deemed to be University), Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="20981" public="1" featured="0">
    <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="189214">
                <text>Secure framework of authentication mechanism over cloud environment</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="189215">
                <text>Access control; Attributed-based control system; Cloud computing; Two-factor authentication (2FA); Web services</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="189216">
                <text>Cloud computing offers a cost effective virtual infrastructure management along with storage and application-oriented services to its customers. This innovation quickly turns into a generally very widely accepted worldview for conveying administrations through web. In this way, this administration expert provider must be offer the trust and information security, on the grounds that there is a most vital and profitable and most delicate information in extremely secure using cryptographic techniques to secure the data in cloud. So for ensure the privacy of essential information, it must be secured utilizing encryptions algorithms and afterward transferring to cloud. This paper presents a novel technique for electronic distributed computing administrations utilizing two-variable validation (2FA) access control framework. The prime target of the projected framework is to guarantee a optimal security for all the actors involved in the component design of proposed authentication system. Furthermore, property based control in the framework likewise authorize cloud servers to maximum the access to those clients with the same arrangement of properties while saving client privacy. At long last, we additionally do a reproduction to show the practicability of our proposed framework. The assessment work is done by utilizing expense of communication, data transfer capacity and proficiency of the framework as an execution metric.  Springer International Publishing AG 2017.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="189217">
                <text>Shahabadkar R.; Sai Satyanarayana Reddy S.; Manjunath C.; Channabasava U.; Shahabadkar K.R.</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="189218">
                <text>Advances in Intelligent Systems and Computing, Vol-575, pp. 284-291.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="189219">
                <text>Springer Verlag</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="189220">
                <text>2017-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="189221">
                <text>&lt;a href="https://doi.org/10.1007/978-3-319-57141-6_30" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-3-319-57141-6_30&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85018698489&amp;amp;doi=10.1007%2F978-3-319-57141-6_30&amp;amp;partnerID=40&amp;amp;md5=7bc3208a049cc6bc1ab1ea123668f37f" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85018698489&amp;amp;doi=10.1007%2f978-3-319-57141-6_30&amp;amp;partnerID=40&amp;amp;md5=7bc3208a049cc6bc1ab1ea123668f37f&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="189222">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="189223">
                <text>ISSN: 21945357; ISBN: 978-331957140-9</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="189224">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="189225">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="189226">
                <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="189227">
                <text>Shahabadkar R., Vardhaman College of Engineering, Kacharam, Shamshabad, Hyderabad, 500018, Telangana, India; Sai Satyanarayana Reddy S., Vardhaman College of Engineering, Kacharam, Shamshabad, Hyderabad, 500018, Telangana, India; Manjunath C., Faculty of Engineering, Christ University, Bangalore, India; Channabasava U., K S School of Engineering and Management, Bangalore, India; Shahabadkar K.R., RNS Institute of Technology Channasandra, Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="19907" public="1" featured="0">
    <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="174300">
                <text>Secure IBS Scheme for Vehicular Ad Hoc Networks</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="174301">
                <text>Conditional privacy-preservation; Identity-based authentication; Message integrity and unlinkability; Non-repudiation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="174302">
                <text>Vehicular Ad hoc Networks (VANET) havedrastically grown in recent years since they provide a better and more secure driving experience. Due to its characteristics, it is vulnerable to many security attacks. Even though many authentication schemes are proposed, their overheads are high. Hence, this study proposes a new Identity-Based Signature (IBS) for authentication with privacy-preservation. It supports secure communications with additional security features. It requires less overhead since it uses XOR operations and one-way hash functions for the signing and verification process. When the proposed schemes performance is compared to the recent schemes, it is observed that the proposed approach is more efficient in computation and communication.  2023, The Author(s), under exclusive license to Springer Nature Singapore Pte Ltd.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="174303">
                <text>Jenefa J.; Sajini S.; Anita E.A.M.</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="174304">
                <text>Smart Innovation, Systems and Technologies, Vol-313, pp. 577-585.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="174305">
                <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="174306">
                <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="174307">
                <text>&lt;a href="https://doi.org/10.1007/978-981-19-8669-7_51" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-981-19-8669-7_51&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85164962837&amp;amp;doi=10.1007%2F978-981-19-8669-7_51&amp;amp;partnerID=40&amp;amp;md5=d197da545dae14f1d6b4e8f147e51882" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85164962837&amp;amp;doi=10.1007%2f978-981-19-8669-7_51&amp;amp;partnerID=40&amp;amp;md5=d197da545dae14f1d6b4e8f147e51882&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="174308">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="174309">
                <text>ISSN: 21903018; ISBN: 978-981198668-0</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="174310">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="174311">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="174312">
                <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="174313">
                <text>Jenefa J., CHRIST (Deemed to be University), Bangalore, India; Sajini S., SRM Institute of Science and Technology, Tamil Nadu, Ramapuram, India; Anita E.A.M., CHRIST (Deemed to be University), Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="19524" public="1" featured="0">
    <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="168958">
                <text>Secure Identity Based Authentication for Emergency Communications</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168959">
                <text>Authentication; Elliptic curve cryptography; Emergency communication; Identity based signature and privacy preservation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168960">
                <text>The Vehicular Ad Hoc Network (VANET) offers secure data transmission between vehicles with the support of reliable authorities and RSUs. RSUs are fully damaged in emergency scenarios like natural catastrophes and are unable to provide the needed services. Vehicles in this scenario must communicate safely without RSUs. Hence, this study suggests a secure and reliable identity-based authentication technique for emergency scenarios. To provide secure vehicle-to-vehicle communication without RSUs, ECC-based IBS is utilized. Additionally, it offers security features like message integrity, privacy protection, and authentication. It is also resistant to attacks depending on authentication and privacy. The proposed technique performs efficiently with less communication and computing cost when its performance is compared with recent schemes.  The Author(s), under exclusive license to Springer Nature Singapore Pte Ltd. 2024.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168961">
                <text>Jenefa J.; Anita E.A.M.; Divya V.; Kandan S.R.; Vinodha D.</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="168962">
                <text>Lecture Notes in Networks and Systems, Vol-840, pp. 129-140.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="168963">
                <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="168964">
                <text>2024-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="168965">
                <text>&lt;a href="https://doi.org/10.1007/978-981-99-8451-0_11" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-981-99-8451-0_11&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85187674041&amp;amp;doi=10.1007%2F978-981-99-8451-0_11&amp;amp;partnerID=40&amp;amp;md5=bb21c725aa9bbb264d9fd38a11a895c1" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85187674041&amp;amp;doi=10.1007%2f978-981-99-8451-0_11&amp;amp;partnerID=40&amp;amp;md5=bb21c725aa9bbb264d9fd38a11a895c1&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="168966">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="168967">
                <text>ISSN: 23673370; ISBN: 978-981998450-3</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="168968">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168969">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168970">
                <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="168971">
                <text>Jenefa J., Christ (Deemed to be University), Bangalore, India; Anita E.A.M., Christ (Deemed to be University), Bangalore, India; Divya V., Christ (Deemed to be University), Bangalore, India; Kandan S.R., Christ (Deemed to be University), Bangalore, India; Vinodha D., Christ (Deemed to be University), Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2736" public="1" featured="0">
    <fileContainer>
      <file fileId="2380">
        <src>https://archives.christuniversity.in/files/original/3344b56b173ce085e73a6a52dcc67cb0.jpg</src>
        <authentication>0b6dfeeadbd8dbf97f5aef738454f6b9</authentication>
      </file>
    </fileContainer>
    <collection collectionId="9">
      <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="12354">
                  <text>Patents</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="12355">
                  <text>Patent</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="12356">
                  <text>Patent</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="23">
      <name>Patent</name>
      <description>Patents</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="18110">
                <text>Secure image retrieval and classification framework for IOT based healthcares systems using deep neural networks /</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18111">
                <text>Computer Science</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18112">
                <text>Patent Number: 202241035066, Applicant: Dr.S.Balamurugan.&#13;
Deep Learning has shown promising results in the domain of Medical Image Analysis and Image Processing. Proposed is a secure image retrieval and classification framework for IoT based healthcare systems using Deep Neural Networks. The problem of solving the error introduced by adversarial noise is considered. Back Propagation Algorithm is employed for Segmentation (localization) as well as error prediction and detection.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18113">
                <text>R, Sivakumar.</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="18114">
                <text>&lt;a href="https://drive.google.com/file/d/1VB0jQZjiG19a9G9BqvnIBsCff2HwDMfi/view" target="_blank" title="Secure image retrieval and classification framework for IOT based healthcares systems using deep neural networks /" rel="noreferrer noopener"&gt;https://drive.google.com/file/d/1VB0jQZjiG19a9G9BqvnIBsCff2HwDMfi/view&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="18115">
                <text>Intellectual Property India</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="18116">
                <text>2022-05-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18117">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18118">
                <text>Patent</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2737" public="1" featured="0">
    <fileContainer>
      <file fileId="2381">
        <src>https://archives.christuniversity.in/files/original/d29a9ba5d643019021611bb5abeecf96.jpg</src>
        <authentication>0b6dfeeadbd8dbf97f5aef738454f6b9</authentication>
      </file>
    </fileContainer>
    <collection collectionId="9">
      <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="12354">
                  <text>Patents</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="12355">
                  <text>Patent</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="12356">
                  <text>Patent</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="23">
      <name>Patent</name>
      <description>Patents</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="18119">
                <text>Secure image retrieval and classification framework for IOT based healthcares systems using deep neural networks /</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18120">
                <text>Computer Science</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18121">
                <text>Patent Number: 202241035066, Applicant: Dr.S.Balamurugan.&#13;
Deep Learning has shown promising results in the domain of Medical Image Analysis and Image Processing. Proposed is a secure image retrieval and classification framework for IoT based healthcare systems using Deep Neural Networks. The problem of solving the error introduced by adversarial noise is considered. Back Propagation Algorithm is employed for Segmentation (localization) as well as error prediction and detection.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18122">
                <text>V B, Kirubanand.</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="18123">
                <text>&lt;a href="https://drive.google.com/file/d/1VB0jQZjiG19a9G9BqvnIBsCff2HwDMfi/view" target="_blank" title="Secure image retrieval and classification framework for IOT based healthcares systems using deep neural networks /" rel="noreferrer noopener"&gt;https://drive.google.com/file/d/1VB0jQZjiG19a9G9BqvnIBsCff2HwDMfi/view&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="18124">
                <text>Intellectual Property India</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="18125">
                <text>2022-05-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18126">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18127">
                <text>Patent</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
