<?xml version="1.0" encoding="UTF-8"?>
<collection 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">
 <record>
  <leader>00000ctm a22000004a 4500</leader>
  <controlfield tag="001">UP-99796217610949819</controlfield>
  <controlfield tag="003">Buklod</controlfield>
  <controlfield tag="005">20230215105418.0</controlfield>
  <controlfield tag="006">m    |o  d |      </controlfield>
  <controlfield tag="007">ta</controlfield>
  <controlfield tag="008">130920s        xx     d     r    |||| u|</controlfield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(iLib)UPD-00205806052</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
   <subfield code="a">DENGII</subfield>
   <subfield code="e">rda</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
   <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="042" ind1=" " ind2=" ">
   <subfield code="a">DMLUC</subfield>
  </datafield>
  <datafield tag="090" ind1=" " ind2=" ">
   <subfield code="a">LG 996 2013 E643</subfield>
   <subfield code="b">M33</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
   <subfield code="a">Macabale, Nemesio Jr.,A.</subfield>
   <subfield code="e">author.</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
   <subfield code="a">CLAW</subfield>
   <subfield code="b">channel load aware routing metric for wireless mesh networks</subfield>
   <subfield code="c">Nemesio A. Macabale Jr.</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="1">
   <subfield code="a">Quezon City</subfield>
   <subfield code="b">College of Engineering, University of the Philippines Diliman</subfield>
   <subfield code="c">2013.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
   <subfield code="a">xviii, 127 leaves</subfield>
   <subfield code="b">illustrations</subfield>
   <subfield code="c">28 cm</subfield>
  </datafield>
  <datafield tag="336" ind1=" " ind2=" ">
   <subfield code="a">text</subfield>
   <subfield code="2">rdacontent</subfield>
  </datafield>
  <datafield tag="337" ind1=" " ind2=" ">
   <subfield code="a">unmediated</subfield>
   <subfield code="2">rdamedia</subfield>
  </datafield>
  <datafield tag="338" ind1=" " ind2=" ">
   <subfield code="a">volume</subfield>
   <subfield code="2">rdacarrier</subfield>
  </datafield>
  <datafield tag="502" ind1=" " ind2=" ">
   <subfield code="a">Thesis (Ph.D. Electrical Engineering)--University of the Philippines, Diliman.</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">Despite advances in the field, many research challenges remain in optimally routing traffic within a wireless mesh network. Due to the shared nature of the wireless channel, routing based on metrics traditionally used in wired networks such as hop counts do not take into account load, interference and ocntention within the channel shared among neighboring mesh nodes. As a result, routing algorithms that use such &quot;load-agnostic&quot; metrics tend to direct multiple traffic flows naively along known best paths, eventually congesting wireless channels along path and causing significant drops in network throughput.  To address this issue, we designed a new channel-load aware routing metric called CLAW that takes into consideration traffic load, contention and interference within the channel. In contrast with other load aware routing metrics that need to collect region-wide information to assess region-wide channel load, the CLAW routing metric is based on node-local information and simple computation. It uses available functions from a wireless node's MAC layer to monitor the state of the MAC and physical layers. Consequently, CLAW provides accurate estimates of channel busyness and contention as fractions of time, simplifying computations. Although CLAW is designed to replace hop count routing metrics, during the course of our investigation we found that directly replacing a hop count routing metric with a load-aware one would not immediately improve performance. This is due to the fact that the load estimates used to choose routes are themselves affected by the route choices with feedback effects that cause routing oscillation and instability. To handle these issues, CLAW treats the routing process in a manner analogous to a control system with a feedback control. By addressing these issues, CLAW significantly improves network performance in both throughput and delay against hop count and other competing load-aware routing metrics found in the literature.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
   <subfield code="a">Wireless communication systems.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
   <subfield code="a">Routing (Computer network management).</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
   <subfield code="a">Wireless mesh networks.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
   <subfield code="a">Routing metric.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
   <subfield code="a">Congestion awareness.</subfield>
  </datafield>
  <datafield tag="842" ind1=" " ind2=" ">
   <subfield code="a">Thesis</subfield>
  </datafield>
  <datafield tag="905" ind1=" " ind2=" ">
   <subfield code="a">FI</subfield>
  </datafield>
  <datafield tag="905" ind1=" " ind2=" ">
   <subfield code="a">UP</subfield>
  </datafield>
  <datafield tag="852" ind1="0" ind2=" ">
   <subfield code="a">UPD</subfield>
   <subfield code="b">DARCHIVES</subfield>
   <subfield code="h">LG 996 2013 E643</subfield>
   <subfield code="i">M33</subfield>
  </datafield>
  <datafield tag="852" ind1="0" ind2=" ">
   <subfield code="a">UPD</subfield>
   <subfield code="b">DENG-II</subfield>
   <subfield code="h">LG 996 2013 E643</subfield>
   <subfield code="i">M33</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
   <subfield code="a">Thesis</subfield>
  </datafield>
 </record>
</collection>
