<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02846ntm a2200265 a 4500</leader>
  <controlfield tag="001">vtls000085197</controlfield>
  <controlfield tag="003">KUKTEM</controlfield>
  <controlfield tag="005">20251117113252.0</controlfield>
  <controlfield tag="008">150203t2014    my a   f m    000 0 eng d          </controlfield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">THE0001883(Local)</subfield>
  </datafield>
  <datafield tag="039" ind1=" " ind2="9">
    <subfield code="a">201905131514</subfield>
    <subfield code="b">yusri</subfield>
    <subfield code="y">201502031216</subfield>
    <subfield code="z">ariffin</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">UMP</subfield>
  </datafield>
  <datafield tag="090" ind1=" " ind2=" ">
    <subfield code="a">QA76.76.D47 Z38 2014 r Bc.</subfield>
  </datafield>
  <datafield tag="100" ind1="0" ind2=" ">
    <subfield code="a">Nik Zatizzahraa  Nik Zamry</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Experimental analysis on active bandwidth estimation tools for clink, bing, stab for mesh wireless local area network /</subfield>
    <subfield code="c">Nik Zatizzahraa  Nik Zamry</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">Kuantan, Pahang :</subfield>
    <subfield code="b">UMP,</subfield>
    <subfield code="c">2014</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">xiii, 66 p. :</subfield>
    <subfield code="b">ill. (some col.) ;</subfield>
    <subfield code="c">30 cm. +</subfield>
    <subfield code="e">1 CD-ROM</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Faculty of Computer System and Software Engineering</subfield>
  </datafield>
  <datafield tag="502" ind1=" " ind2=" ">
    <subfield code="a">Project paper (Bachelor of Computer Science ( Computer Systems and Networking)) -- Universiti Malaysia Pahang - 2014</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
    <subfield code="a">Bibliography : p. 61</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
    <subfield code="a">Available bandwidth &#x2013; as well as capacity or achievable bandwidth &#x2013; on a path or a link is one of the very important parameters to measure or estimate in a network: it is of high interest for many networking functions (routing, admission and congestion control, load balancing, etc). The bandwidth measurement techniques can be divided into two type which were active and passive measurement technique. Active measurement techniques provide the easiest and the more flexible approach, for estimating available bandwidth. In addition, they can be used for different network technologies or structures. Many techniques and tools for available bandwidth estimation appeared recently, but little attention has been given to the accuracy of the estimated values in the real Internet, most of previous studies focusing on validating the accuracy of these tools on local platform. WLAN offers wireless network communication over short distances using radio or infrared signals instead of using traditional network cabling. Therefore, this paper evaluates more about analysing bandwidth estimation in mesh wireless local area network (WLAN) using three selected active bandwidth estimation tools. This paper then discusses the results we got in different environments with different active tools. The results were discussed based on three aspects which were accuracy, consistency and failure pattern. They were tested in two different network environments: optimum network (network without external traffic) and network with external traffic. In order to carry out the testing, one access point, two access points with same bandwidth and two access points with different bandwidth were used in both network environments.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Computer software</subfield>
    <subfield code="x">Development</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Application software</subfield>
    <subfield code="x">Development</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">1</subfield>
    <subfield code="a">20000</subfield>
    <subfield code="b">20000</subfield>
    <subfield code="d">2019-09-04</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">QA76.76.D47 Z38 2014 r Bc.</subfield>
    <subfield code="p">0000091627</subfield>
    <subfield code="r">2019-09-04 00:00:00</subfield>
    <subfield code="t">1</subfield>
    <subfield code="w">2019-09-04</subfield>
    <subfield code="y">PSM</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">1</subfield>
    <subfield code="a">10000</subfield>
    <subfield code="b">10000</subfield>
    <subfield code="d">2019-09-04</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">CD 8581 | QA76.76.D47 Z38 2014 r Bc.</subfield>
    <subfield code="p">0000091628</subfield>
    <subfield code="r">2019-09-04 00:00:00</subfield>
    <subfield code="t">1</subfield>
    <subfield code="w">2019-09-04</subfield>
    <subfield code="y">PSM</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="a">VIRTUA40</subfield>
    <subfield code="c">5810</subfield>
    <subfield code="d">5816</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="a">VTLSSORT0080*0200*0400*0900*1000*2450*2600*3000*5000*5020*5040*5200*6500*6501*9992</subfield>
  </datafield>
</record>
