<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="12395" 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/12395?output=omeka-xml" accessDate="2026-04-04T15:25:54+00:00">
  <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="70512">
              <text>61000349</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70513">
              <text>Optimal Benchmarking of Quality of Service and Quality of Experience Metrics for Telecom Service Providers Using A Slack Based, Measure in Data Envelopment Analysis   </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70514">
              <text>Computer Science</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70515">
              <text>With new devices and new network technologies coming up, it has become an inevitable task to provide services of a minimum quality. Setting feasible Service Level Agreements (SLAs) is the need of the hour. This, being a part of network provisioning and providing the best possible Quality of Service (QoS) is very vital and helps improve user perceived quality or the Quality of Experience (QoE). QoE evaluation helps Internet Service Providers (ISPs) understand their user satisfaction better and this goes hand in hand with providing adequate network QoS. Moreover, in this era of competition, the ISPs themselves will have to be evaluated based on their QoE and QoS metrics to know their true position in the market in terms of performance against their peers/competitors. This evaluation is usually done on a per-metric basis. However, we see from current performance data that all the ISPs fare well on some metrics and need improvement in the others. It is a fact that no ISP fares bad on all given metrics and leads to an understanding that per-metric based evaluation may be a biased form of newlineevaluating performance. Hence, this research has attempted to use an intelligent, robust newlinemathematical technique called the Data Envelopment Analysis (DEA) with its Slack newlineBased Measure (SBM) approach. DEA is a proven, tested and tried technique that is in newlineuse in major industries even today. Being a multiple criterion evaluation methodology newlinebased on linear programming, it works well on multiple outputs and multiple inputs. DEA gives the overall, relative efficiency of the ISPs which gives us the true position of the provider against its peers. The Slack Based Measure provides the Output Slacks that show the potential improvement that the lagging ISPs can make to be in par with their peers/competitors. The Output targets that are provided by the technique can be used as benchmarks for SLAs.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70516">
              <text>S,Gracia</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="70517">
              <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="70518">
              <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="70519">
              <text>2024-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="70520">
              <text>Beaulah, Soundarabai P</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70521">
              <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="70522">
              <text>PDF</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70523">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="70524">
              <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="70525">
              <text>&lt;a href="http://hdl.handle.net/10603/575083" target="_blank" rel="noreferrer noopener"&gt;http://hdl.handle.net/10603/575083&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
