<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="26242" 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/26242?output=omeka-xml" accessDate="2026-06-18T14:24:48+00:00">
  <collection collectionId="7">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3139">
                <text>Faculty Publications</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="28">
    <name>Conference Paper</name>
    <description>Faculty Publications- Conference Papers</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="261393">
              <text>Raj, E. Babu; Padmalal, S.; Ram Mohan, N.R.; Shaji, B.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="261394">
              <text>CCIR: The Next Frontier in Mobile Network Evolution - Integrating Communication and Computing for Enhanced Services</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="261395">
              <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="261396">
              <text>16th International Conference on Advances in Computing, Control, and Telecommunication Technologies, ACT 2025;Volume;1;pp.4318-4324</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="261397">
              <text>&lt;a href="https://www.scopus.com/pages/publications/105034172713?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105034172713?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="261398">
              <text>Raj E.B., Department of Computer Science and Engineering, CHRIST University, Bengaluru, India; Padmalal S., Department of Computer Science and Engineering, Mangalam College of Engineering, Kottayam, Kerala, Ettumanoor, India; Ram Mohan N.R., Department of Computer Science and Engineering, Royal College of Engineering and Technology, Akkaikavu, Kerala, Thrissur, India; Shaji B., Department of Computer Science and Engineering, Nehru College of Engineering and Research Centre, Pampady, Kerala, Thrissur, India</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="261399">
              <text>The mobile RAN is the bridge and enabler between end users and application services, and fortunately, the computational capacity of base stations in RANs[1] has experienced tremendous growth accompanied by increasingly stringent service requirements from emerging applications such as AR/VR. These two trends imply an unprecedented opportunity that the abundant computing resources in base stations could be leveraged to host latency-sensitive applications if being managed properly, thereby giving rise to a new vision named Communication and Computing Integrated RAN (CCIR), where not only communication but also computing services are delivered by RANs in a coherent way[2]. In fact, CCIR implies an even more radical departure of designing future mobile networks-going beyond regarding the role of RANs as connecting links. This article provides an elaboration on the fundamental design philosophies and principles of CCIR, the logical architecture. We will explore further on key tech-nologies toward realizing our vision. Specifically, we provide a thorough view on what CCIR really means - it involves different integration granularities between communication and computing functions; meanwhile it keeps evolving until approaching real-time joint scheduling and holistic resource management based on one unified infrastructure. To assess the feasibility and advantages brought by CCIR, several field experiments were carried out where computing resources are migrated within different base stations. In conclusion, CCIR is a prospective evolution direction for future mobile networks dealing with communication-computation-converged requirements in new service use scenarios[3]. Using current infrastructure more intelligently and efficiently will facilitate better user experience, greener mobile networks as well as serve as better platform for future advancements in wireless technology.  Grenze Scientific Society, 2025.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="261400">
              <text>Grenze Scientific Society</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="261401">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="261402">
              <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="261403">
              <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="261404">
              <text>online</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
