<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="12705" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/12705?output=omeka-xml" accessDate="2026-05-22T06:32:14+00:00">
  <collection collectionId="5">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64">
                <text>Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="74840">
              <text>Enhancing mobility management in 5G networks using deep residual LSTM model</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="74841">
              <text>5G networks; Handover optimization; LSTM; Mobility management; Resource Allocation</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="74842">
              <text>Mobility management is an essential component of 5G networks to provide mobile users with seamless connectivity and efficient cell transition. However, increasing user mobility, device density, and the diversity of service requirements all pose significant challenges to achieving optimal mobility management. This article describes a novel method for improving mobility management in 5G networks that employs a deep residual Long Short-Term Memory model. Deep learning and LSTM, a type of recurrent neural network, are used in the proposed model to identify temporal dependencies and patterns in user mobility data. The model learns to predict future user locations and mobility patterns by training on historical mobility data, allowing for proactive resource allocation and handover decisions. We incorporate residual connections into the LSTM architecture, inspired by the residual learning framework, to address the inability of traditional LSTM models to capture complex temporal dynamics. This allows the model to effectively incorporate long-term dependencies and improves prediction accuracy. Furthermore, we incorporate the mLSTM model into the mobility management framework of 5G networks. The model continuously obtains real-time user location updates and predicts future user positions, allowing for proactive handover decisions. The network can optimize resource allocation, reduce handover latency, and improve user experience by leveraging anticipated mobility patterns. We test the proposed method by simulating it extensively with real-world mobility traces. The results show that the mLSTM model accurately predicts user mobility and outperforms conventional methods in transition performance. The model is not affected by changing network conditions, user mobility patterns, or service specifications.  2024 Elsevier B.V.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="74843">
              <text>Baz A.; Logeshwaran J.; Natarajan Y.; Patel S.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="74844">
              <text>Applied Soft Computing, Vol-165</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="74845">
              <text>Elsevier Ltd</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="74846">
              <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="74847">
              <text>&lt;a href="https://doi.org/10.1016/j.asoc.2024.112103" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1016/j.asoc.2024.112103&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85202155517&amp;amp;doi=10.1016%2Fj.asoc.2024.112103&amp;amp;partnerID=40&amp;amp;md5=8e04a5aa78f775d9789c9dffbe538692" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85202155517&amp;amp;doi=10.1016%2fj.asoc.2024.112103&amp;amp;partnerID=40&amp;amp;md5=8e04a5aa78f775d9789c9dffbe538692&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="74848">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="74849">
              <text>ISSN: 15684946</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="74850">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="74851">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="74852">
              <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="74853">
              <text>Baz A., Department of Computer and Network Engineering, College of Computing, Umm Al-Qura University, Makkah, Saudi Arabia; Logeshwaran J., Department of Computer Science, CHRIST (Deemed to be University), Karnataka, Bengaluru, 560029, India; Natarajan Y., Department of Computer Science and Engineering, Sri Shakthi Institute of Engineering and Technology, Tamil Nadu, Coimbatore, 641062, India; Patel S.K., Department of Computer Engineering, Marwadi University, Gujarat, Rajkot, 360003, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
